Project Slayers 2 combat practice should begin with the actions its fixed first-party description actually names: M1 Attack, M2 Heavy Attack, Q Dash, Left Shift Sprint, Left Alt Mouse Lock, Ctrl Wall Climb, and the LRLRL, RRLRL, and LLRLR combo strings. Start with range, facing, and input consistency. Add live mechanics only after the current client demonstrates them.
Prepare a clean practice setup
Join through Place 91433030196741, close chat, and click inside the Roblox window. Pick an open area or low-pressure target if the current build offers one. Avoid a wall behind your character, keep the target visible, and choose one mouse-lock state for the first tests.
Use one M1, reset, then one M2. Test Q in each direction without attacking. If these single actions are inconsistent, fix the controls before measuring a combo. The Controls Guide covers focus and key conflicts.
Run the four-step combat drill
- Observe: watch one complete target action without attacking. Note its start, travel direction, and final position.
- Position: walk, sprint, or dash to a deliberate distance while keeping the target visible.
- Attack: use one M1 or M2. Choose the shorter commitment until the opening is understood.
- Reset: stop pressing attacks and return to a readable distance. Watch for a follow-up before repeating.
Repeat the same drill three times. If the result changes, identify one variable: range, facing, camera, target movement, previous animation, or latency. Change only that variable on the next attempt.
This drill does not assume a parry, block, immunity window, or stamina system. The fixed public description does not document those mechanics.
Compare normal and heavy attacks
Use M1 and M2 from the same position against the same target state. Compare visible reach, character movement, and time until you can safely move again. Do not infer damage priority from animation size. A heavy attack can look stronger without being the correct answer for every opening.
When M1 reaches and M2 misses, range or target movement may be responsible. When both land but you are hit afterward, the opening may be shorter than your commitment. Shorten the response before assuming the target ignores attacks.
Record damage only if the current interface clearly shows it and your conditions are stable. Difficulty, progression, weapon, breathing style, path, buffs, and updates may alter values.
Add dash and mouse lock
Place your character at a fixed landmark and test Q forward, backward, left, and right. Repeat with Left Alt mouse lock toggled. Watch where the character ends and which way they face. Use the mode that gives you a repeatable start for attacks.
Next, dash once and wait before pressing M1. Reduce the delay gradually only if the action remains consistent. The public description does not state whether dash cancels into attack, grants invulnerability, consumes a resource, or has a cooldown, so describe only the live result you can reproduce.
Near a wall, move back into open space. Camera collision and the Ctrl wall-climb context can add extra variables that do not belong in a basic range test.
Add the published combos
Practice LRLRL from neutral using deliberate left-right alternation. Test Space separately as the published alternative air-combo input. Then practice RRLRL and LLRLR. Use prefixes when a string fails: RR, then RRL; LL, then LLR.
Do not force a full combo into every opening. First prove that the target stays available and that your character can finish without immediate retaliation. If a shorter M1 answer works consistently, keep it as the baseline and treat the longer string as a separate opportunity.
The Combo Inputs guide explains every sequence and common dropped-input causes.
Use a practical decision table
Diagnose common failures
If you are hit before your action starts, you may have chosen the opening too late or entered from the wrong range. If your attack starts but misses, check facing and target movement. If the action lands but you cannot leave, shorten the commitment. If the combo stops, return to its working prefix.
When another player’s clip behaves differently, check Place ID, date, input device, target, starting position, and any visible progression system. A video for another similarly named Universe cannot establish combat rules here.
Do not solve every failure by clicking faster. Roblox focus, latency, animation state, and target state can all affect what you see. A slower reproducible sequence is more useful than one lucky full string.
Keep progression systems separate
The description promises blade forging, breathing styles, and a humanity-or-darkness choice, but it does not publish how those systems change combat. Do not claim a breathing move, faction bonus, weapon effect, skill slot, or damage multiplier for this fixed Universe until the current experience shows it.
Use Breathing to check style claims and Paths before making an alignment decision. If a live prompt affects combat, record its exact text and choice consequences before turning it into advice.
A successful first practice session
You are ready to leave the baseline when you can deliberately use M1 and M2, dash in the intended direction, keep a target visible with your chosen mouse-lock state, and enter at least one published string without accidental extra clicks. You should also be able to name why a failed exchange occurred.
Continue to Controls for input lookup, Guides for a wider first-session route, or Updates if the experience or public metadata is unavailable.