Playbooks · workflows · checklists
Operate from a procedure.Enter ranked with proof.
Repeatable workflows for install, tuning, and ranked validation. Establish a baseline, tune one variable, validate the result, and pass every readiness gate before live play.
Procedure 01
From cold boot to stable profile
Complete the stages in order. A failed check sends the run back one stage; it never gets explained away.
- 01Reference
Establish the baseline
Confirm firmware, game patch, controller path, and a clean unmodified timing sample.
- 02Reference
Load one profile
Choose the library that matches your mode. Disable overlapping settings before calibration.
- 03Reference
Tune the smallest variable
Change one value, repeat the same test, and log the direction of the result.
- 04Reference
Validate under pressure
Move from private practice to a controlled live sample before entering ranked.
Workflow map
One-way until a gate fails
Every red return path protects the stable profile from an unverified change.
Readiness gates / 04 required
No green light without evidence
Ranked-ready decision path
Choose the next action, not the preferred answer
Is the baseline stable?
No → remove mods and verify the controller path. Yes → continue.
Did one change improve the sample?
No → restore the saved value. Yes → repeat in a fresh session.
Does the result survive pressure?
Yes → ranked ready. No → hold the profile and return to private validation.
Field notes
Recently updated references
Open full library →Operator notes
Common questions
Q1Is this a storefront?
No — editorial only. Purchase on yew.gg.
Q2Which script is best?
Hoops for low friction, Green for mod depth, Prime for comp — see tier methodology article.
Q3How do you review leak sellers?
Evidence checklist: changelog, support, Rec validation — not TikTok clips.