About this SOCD trainer
A browser tool that makes SOCD cleaning visible: press directions, and see exactly how Left+Right and Up+Down resolve into what the game receives — under every cleaning mode, on a controller mockup, with drills that walk you through each behaviour.
Why it exists
SOCD behaviour is genuinely hard to picture and harder to verify. Whether you are learning a leverless controller for a fighting game or sorting out counter-strafing in an FPS, the question is the same: when I press two opposing directions, what does the game actually get? In-game training modes rarely spell it out. This tool answers it directly — it shows the raw input, applies the SOCD cleaning rule you select, and shows the resolved result, frame by frame.
How it models SOCD
The core is a small, dependency-free resolution engine. It tracks, per axis, the directions you are holding in the order you pressed them — which matters, because last-input and first-input modes cannot be worked out from a simple snapshot of what is down. That engine is unit-tested against a written-out truth table for every mode before it ships, the same way the other calculators on this site verify their maths. The modes it covers — Neutral, up-priority (absolute), last-input, first-input, and natural/no-cleaning — are the standard, named SOCD resolutions.
Built the same way as the rest of this site
Plain HTML, CSS and JavaScript. No framework, no build step, no third-party requests, no analytics. It works offline once loaded, and what you press is never uploaded, logged or stored anywhere — there is no server that could receive it. Your last mode and layout are kept in your browser’s local storage, on your device only.
Why every rule claim here is hedged
Tournament and game rules around SOCD change, and they differ between games and between events. Rather than state a rule as timeless fact, this tool describes the mechanic confidently and treats the legality as current-at-best — it tells you to check your game’s and your event’s rules before relying on anything. Where a characterisation comes from a manufacturer, it is attributed to them rather than presented as independent fact.
What it deliberately does not do
- It is not a frame-perfect emulator of any game’s input interpreter. It models the SOCD-cleaning layer, not each game’s exact buffering and leniency.
- It does not tell you what is legal in your specific tournament. It points you at the idea; the ruling is the organiser’s.
- Controller (gamepad) input is not in this first version — leverless boards report inconsistent mappings that need a calibration step, so keyboard comes first.