Understand the changing kit
Register is not best learned as one fixed four-button sheet. Current community documentation describes a rotating or state-dependent selection, which means your first skill is reading what the interface offers now. Look at the move names and state before the exchange. If a guide, screenshot, or video shows a different arrangement, it may represent another roll or another build.
This page uses the live picker and live HUD as the final authority. It does not publish exact damage or cooldown figures that cannot be reproduced across current servers. Access may also change while the character develops, so inspect the character picker and Shop before making any purchase decision.
Build a decision tree
Group the moves you actually see by job: opener, extender, movement, defense, area control, or finisher. One move can fill more than one job, but writing down its safest use prevents random cycling. For each state, choose a low-commitment neutral option, one confirmed route, and one way to disengage.
If the kit rotates automatically, watch the trigger and do not plan a combo around a tool that will disappear before the next exchange. If selection is player-controlled, learn the input and the vulnerable moment associated with changing state. Test both rules in a quiet server because the interface is more trustworthy than an old description.
A good decision tree fits on one screen: “If I have a starter, confirm the short route. If I have area control, force movement. If I have mobility, change angle. If the useful tool is unavailable, block and reset.”
Awakening choices
Community update notes around version 1.82 associate Register with awakening choices including Con Artistry, Mayhem, and Big Moves. Names and availability are patch-sensitive. Confirm that these labels appear in the current awakening interface before using any detailed advice tied to them.
Treat each choice as a new mini-kit. Activate it with a plan and inspect which slots change. Test range, block behavior, recovery, and wall interaction. Do not select an awakening solely because a montage shows high damage; the best choice in a duel may be the one you can confirm, while a public brawl may value a different area or mobility tool.
Awakening time is limited. If an opponent disengages, preserve position rather than throwing every move into empty space. If several players are nearby, keep the camera wide and avoid a long animation that hands a third party an easy punish.
Neutral and confirmation
Register’s variability rewards calm neutral. Use basic attacks, dash timing, and block to create information before committing the current special tool. A move that is excellent on hit may be unsafe on block, and a move that covers space may be poor at point-blank range.
Practice confirmation by having a partner alternate between standing and blocking. Begin the same way each time. Continue only after seeing the hit state. When the current kit changes, repeat the exercise instead of assuming the prior route transfers.
Latency matters. Prefer a slightly shorter sequence you can reproduce over a narrow link that fails whenever the server slows. In public servers, end in a position where you can see the next threat.
Training session
Start by cycling through every available state and recording the visible names. Next, use each move alone at close, medium, and long range. Then test on block and on a knocked-down target. Only after that should you connect moves.
Build three routes: a short basic confirm, a wall route, and an escape-aware route that ends safely. Run each ten times from both screen directions. Finally, enter live matches and focus on identifying the current state before pressing a numbered skill.
If the character receives a patch, repeat the solo move checks. A small recovery or movement change can invalidate an old sequence even when the names remain identical.
Mistakes to avoid
Do not stare at the move bar so long that you lose sight of the opponent. Read the state during knockdown, distance, or another safe pause. Do not spend awakening immediately if the enemy can run out its duration. Do not force a favorite route after the necessary move rotated away.
Avoid calling a state “random” until you have checked its trigger. What seems random in a crowded fight may follow a timer, selection, or action you missed. Conversely, do not promise a deterministic pattern on the strength of a few repetitions.
Most importantly, never use scripts to force a state or access unfinished moves. Legitimate learning stays inside the public controls.
Version check
Confirm Register is visible, note its access label, list the current base states, and check which awakening choices the interface offers. Pair those observations with the controls guide and combos guide. Use the tier list method only after you can operate more than one state consistently.
If the live kit disagrees with this September 2026 snapshot, follow the live kit. Report the exact server-visible difference rather than repeating a secondary claim.