Start with a route, not a montage
A useful combo is repeatable after a real opening, works under ordinary latency, and leaves you prepared for the next state. It does not need to be the longest sequence on video. Begin with one short route for your character and prove each link in the current server.
Community guides commonly use basic M1 hits with a launcher or downslam choice before connecting character moves. The exact count and order are patch-, character-, and position-dependent. Treat that pattern as a structure to test, not a universal command string.
Confirm the starter
Ask a partner to alternate randomly between standing and blocking. Begin with the same M1 or safe starter. Continue only when you recognize a hit. Stop and defend when blocked. Ten correct decisions are more valuable than ten uninterrupted practice-dummy routes.
Then vary distance. A starter that works point-blank may whiff after a dash or on a slight elevation change. Record the practical range where the first hit and the follow-up both connect.
If you cannot visually confirm in time, shorten the opening or choose a clearer starter. Do not solve recognition with a macro.
Build links one at a time
Add one move to the starter and repeat it from both screen directions. When it succeeds consistently, add the next link. If the sequence drops, test only the failing transition. Check distance, timing, target height, wall angle, and server delay.
Choose an ender based on outcome. A knockback ender may reset neutral safely. A close ender may preserve pressure but expose you to an escape or reversal. A wall-dependent move needs a separate center-stage alternative.
Write routes by purpose: “short confirm,” “wall confirm,” “awakening conversion,” and “escape-safe ender.” Purpose labels survive patches better than a single list called best combo.
Account for ragdoll escape
The official controls describe Q as usable for an escape when the state allows it. Your opponent’s escape availability changes route value. Practice with a partner who escapes at different points. Learn which follow-up becomes unsafe and where you can stop without handing over a free punish.
Baiting an escape is only useful if you remain able to respond. Do not intentionally drop a route while locked in a long recovery. Use a stable end state, watch the escape, then take the next decision.
Track your own escape as well. A high-damage route that consumes your positional safety may be a bad trade when several players are nearby.
Walls, terrain, and public servers
Walls can keep a target within range or distort the camera. Test at flat walls, corners, and open ground. If a route requires one rare angle, label it situational. Uneven terrain can change target height and cause otherwise reliable hits to miss.
In public servers, shorter routes often outperform laboratory maximums because third parties can interrupt either fighter. Move the camera between links where possible and choose an early ender when another threat approaches.
Do not use unintended map clips or out-of-bounds behavior as a recommended route. Even if reproducible, an exploit is unstable and unfair.
Latency test
Practice in the region and device you actually play. Run the route in a quiet private server, then in a normal public server. If a link becomes unreliable under ordinary delay, increase the timing margin or replace it. Consistency is part of damage output.
Avoid precise frame claims unless you measured the current build with a documented method. Animation impressions, display rate, and network correction can make old numbers misleading.
After a patch, recheck the starter, every transition, block behavior, and final position. A cooldown change may affect repetition even when the first route still lands.
Combo practice sheet
For each character, record the starter, required position, opponent escape state, route steps, miss point, end position, and check date. Aim for nine successes out of ten before using a route as your default. Then test against a moving, blocking partner.
Pair this method with the controls guide and your character page. Specialized interactions such as Black Flash should be added only after the normal route is dependable.
The final question is not “how many hits?” It is “did I recognize the opening, choose the right route for this position, and recover safely?”