A missing gem does not automatically mean the character is stuck. Preserve a functional setup, verify what is available, and test a staged transition before restarting.
Short answerWhen an expected skill or support gem is unavailable, pause the full build transition rather than dismantling a working campaign setup. Inventory the gems already available, define the smallest combination that keeps the character functional, and list every missing dependency in the destination setup. Inspect unfinished objectives shown in the current game version, but count a reward only when the game explicitly identifies it. Continue with a temporary or lower-level option if one is already available and usable; delay the transition when a required dependency remains unresolved. Consider restarting only after confirming that the current character cannot progress acceptably and that a different route addresses the actual constraint. The supplied evidence does not establish current gem drop rates, exact reward locations, or a universal acquisition route.
Define the actual campaign stall
Separate an unavailable gem from unrelated damage, survival, or execution problems.
- Name the exact skill or support gem blocking the intended transition.
- Record whether the current setup can still clear required campaign content acceptably.
- Classify the missing gem as required for basic function or optional for later improvement.
- Avoid treating an incomplete destination setup as proof that the current character must be abandoned.
Freeze a functional bridge setup
Keep progression possible while the intended build remains incomplete.
- Record the current skill, supports, equipment dependencies, and any available substitutes before changing them.
- Keep a working setup intact until the replacement combination can be tested together.
- If a usable lower-level or temporary option is already available, test it against representative campaign content.
- Change one dependency at a time so a failed transition can be reversed.
Audit available gems and transition dependencies
Turn a vague shortage into a bounded inventory and dependency check.
- List every available skill and support gem relevant to the current and intended setups.
- Divide the destination plan into required pieces, optional improvements, and unsupported assumptions.
- Check whether the plan was written for the current update context.
- Do not infer availability, rarity, or acquisition routes from an external build showcase.
Review unfinished objectives conservatively
Check visible progression options without inventing reward locations.
- Inspect unfinished objectives displayed by the current game version.
- Count an objective as relevant only when its displayed information supports that conclusion.
- Record uncertain objectives separately instead of treating them as confirmed sources.
- Do not estimate drop rates or repeat content based on an unverified reward assumption.
Choose continue, delay, or restart
Apply a clear decision gate after the inventory and objective review.
- Continue when the current or bridge setup remains functional.
- Delay the transition when a required dependency is missing but campaign progress remains acceptable.
- Revise the destination plan when it depends on several unavailable pieces or an outdated assumption.
- Consider restarting only when the current route is genuinely blocked and the alternative route has been independently verified.
- Recheck official patch information before relying on version-sensitive gem guidance.
Worked example
A campaign character is using a functional main skill but the intended destination setup requires a different skill gem and a particular support gem that are not currently available. The player records the working setup, marks both missing gems as transition dependencies, and inspects the unfinished objectives displayed in the current game version. No reward is counted unless the game identifies it. Because an already-owned temporary setup still handles the current campaign content, the player continues with that bridge and postpones the full transition. The destination plan is reviewed again only after a required dependency becomes available or authoritative patch information changes the decision.
Frequently asked questions
Should I restart because the gem I expected is unavailable?
Not by default. Preserve a functional setup, audit the missing dependencies, and verify whether the current character can still progress. Restarting is a last decision gate, not a substitute for confirming the acquisition plan.
Where should I farm an uncut skill or support gem?
The closed evidence does not establish an exact location, reward source, or drop rate. Use only information explicitly displayed in the current game version or supported by current authoritative documentation.
Can I transition with a lower-level or temporary skill setup?
Use it as a bridge only if it is already available, satisfies the setup’s dependencies, and performs acceptably in representative campaign content. Keep the previous setup recoverable while testing.
Did Content Update 0.5.5 change campaign gem availability?
The supplied official evidence confirms that Content Update 0.5.5 is listed, but it contains no captured details establishing a change to campaign gem availability, rewards, or drop rates.
How is this different from a starter-build checklist?
A starter-build checklist evaluates a plan before commitment. This guide addresses the narrower recovery decision after a campaign transition is already blocked by an unavailable skill or support gem.
Sources and review notes
E-01 supports the existence and framing of the player problem only; it is not factual authority for gem mechanics. E-03 supplies official update context but no captured campaign gem details. Advice therefore uses a conditional inventory, bridge-setup, objective-verification, and restart-decision framework.
Prepared with an automated research workflow and published only after evidence and policy checks.