Two hardware features sit at the centre of the current esports equipment argument. The first is rapid trigger, which changes when a key registers. The second is SOCD resolution, which decides what happens when a player holds A and D at the same time. One of them is effectively legal everywhere. The other is banned in some competitions and explicitly permitted in others, and the split runs between rulebooks rather than between keyboard brands.

What this covers: how rapid trigger and SOCD keyboards actually work, and where the tournament rules stood when each organiser’s own published text was last checked. What the rules say: Valve kicks SOCD users out of official Counter-Strike 2 matches; ESL bans it outright; Riot’s VCT ruleset permits it in writing; the Apex Legends Global Series has no named rule and falls back on equipment review. Who should care: competitive players buying a magnetic-switch keyboard, and anyone deciding whether to leave SOCD enabled on the way into their next event.

What rapid trigger and SOCD actually do

A Hall-effect or magnetic-switch keyboard does not just report a key as on or off. Its sensor tracks how far the key has travelled, so the firmware can choose the depth at which a press registers. Wooting says it introduced rapid trigger with the Wooting Two Lekker Edition, and that the feature “activates the key actuation when pressing a key downwards and it resets the key when retracting.” On a conventional mechanical switch the key must return to a fixed reset point before the next press registers; with rapid trigger it resets as soon as it starts moving upward.

ASUS ROG describes the same mechanic on its HFX magnetic switches, which offer an adjustable 0.1–4.0 mm actuation range and a 100-million-keypress rating, and says keys “reset with a mere 0.1mm lift of a finger.” Wooting’s own CS2 guidance is more conservative: 0.4–0.7 mm actuation on WASD and a 0.2–0.5 mm rapid trigger sensitivity, with a warning that too shallow a reset lets ordinary finger pressure produce unintended movement.

SOCD is a different mechanic entirely. It stands for Simultaneous Opposing Cardinal Directions. Keebforce defines it as “a keyboard feature that changes how the keyboard handles opposite directional inputs” — press A and D together on an ordinary board and the game receives two opposite directions, so the character stands still. A board with SOCD resolution decides the conflict itself. Wooting lists three resolutions: last input priority, absolute priority for one chosen key, and neutral. ROG markets the last-input-priority variant as Speed Tap mode.

The distinction that matters for rules is that SOCD produces a release the player did not perform. Press D while still holding A and a last-input-priority board reports A as released, so a counter-strafe happens without the finger ever leaving A. In Counter-Strike, accuracy returns when movement stops, so a board that manufactures the stop removes the coordination step the game is built around. Wooting’s related Rappy Snappy feature takes a slightly different route: it compares the press depth of two opposing keys and prioritises whichever is pressed further down, which Wooting treats as a separate feature from last-input-priority SOCD.

Rapid trigger does none of that. It is still one key, one action, performed by the player.

Who is allowed to make the rule

There is no single authority here. Valve runs the official CS2 servers; ESL runs the ESL Pro Tour and its rulebook; Riot publishes the VCT ruleset; EA runs the ALGS; Evo and Capcom run their own fighting-game events. A ruling by one binds only its own competition.

EVE Zone’s September 2026 deep dive makes that point directly: “Do not rely on a universal claim that rapid trigger is legal in every 2026 tournament. Check the current publisher policy and event-specific rulebook for the game you will play.” Ranked play and tournament play are governed by different documents, and a feature that produces no enforcement action in matchmaking can still be restricted at a LAN.

The rule, by game and competition

WhereSOCD / Snap TapRapid triggerWhere the rule comes from
CS2, Valve official serversNot allowed — kick from the match, no account banAllowedValve’s “Side-stepping Skill” post; Wooting’s CS2 feature status table
CS2, ESL Pro TourProhibited (rule 4.1.1); default map loss up to disqualificationNot named by the ruleESL Pro Tour rulebook update, January 2025
VALORANT, VCTAllowed (rule 2.3.5) unless League Officials say otherwise; macros prohibited (rule 2.3.4)Not named by the rulesetVCT Official Competition Ruleset
Apex Legends, ALGSNot named; peripherals reviewed and approved; general unfair-advantage clauseNot namedALGS Year Six Official Rules
Fighting games, EvoController may not send SOCD inputs; standard cleaning methods allowed; stock gamepads exemptHardware macros and rapid-fire prohibitedEvo controller rules
Fighting games, Capcom Pro TourUp+down and left+right must be “both maintained or both rejected”Macros and turbo prohibitedCPT controller usage rules

Counter-Strike 2: a kick, not a VAC ban

Valve published “Side-stepping Skill” on 19 August 2024. In it, the developers wrote: “We are no longer going to allow automation (via scripting or hardware) that circumvent these core skills and, moving forward, (and initially—exclusively on Valve Official Servers) players suspected of automating multiple player actions from a single game input may be kicked from their match.”

The wording is worth reading slowly, because the retelling has drifted. The remedy Valve described is a kick from the match, not an account ban, and Valve’s advice was to “disable the feature before you join a match.” The Verge tested the change on the day it landed and reported that SOCD use “will now get you kicked from a Counter-Strike 2 game,” while noting the company “doesn’t appear to be ready to ban accounts for using them right now.” GearGeeks, checking the same release notes, makes the same point: neither Valve text mentions VAC. That distinction matters because a match-level kick is not the same layer of enforcement as an anti-cheat detection; where those layers sit relative to each other is covered in our breakdown of kernel anti-cheat architecture.

The same update disabled in-game binds that “include more than one movement and/or attack actions,” which killed null-binds and jump-throw binds. HLTV noted that the change landed two days before online Major qualifiers opened, giving pro players almost no time to adjust.

The vendors were not silent. Razer, whose Huntsman V3 Pro introduced Snap Tap in July 2024, told Dexerto that “Razer Snap Tap is disabled by default.” Wooting, which had followed with its own SOCD mode, told Dexerto it had held back: “We thought of SOCD in the past but right away didn’t want to put it into action because it was very clear this shouldn’t be legal.” Wooting’s later retrospective is blunter about the aftermath — Valve “banned both Snap Tap and Snappy Tappy from use in CS2. But sadly, they banned Rappy Snappy as well.”

ESL bans SOCD outright — and FACEIT stays quiet

ESL moved first and harder. On 29 August 2024 it announced that “the use of Snap Tap, Rappy Snappy, SOCD or similar assistants that produce the same outcome will no longer be allowed” ahead of ESL Pro League Season 20, adding that the announcement covered in-person events and that online guidance would follow.

By the 2025 rulebook the policy was a numbered rule. ESL’s rulebook update confirms it “added 4.1.1 SOCD features to cover SOCD use case,” and rule 4.1.1 reads: “The use of Simultaneous Opposing Cardinal Directions (SOCD) features, including but not limited to Snap Tap, Rappy Snappy, or any similar mechanisms that produce equivalent outcomes, is strictly prohibited. Non-compliance with this rule may result in penalties, ranging from a default map loss to disqualification from the tournament.” The “similar mechanisms” clause means a different brand name does not make a board legal.

FACEIT is the interesting gap. GearGeeks’ October 2026 check found that FACEIT’s cheating policy bans “external scripting/macros designed to gain an advantage” but does not name Snap Tap or SOCD in either direction, so it left FACEIT out of its table rather than guess.

VALORANT’s VCT permits it in writing

Riot went the other way, and it did so on the record. The VALORANT Official Competition Ruleset carries a rule headed “Snap Tap & SOCD” — rule 2.3.5 — which reads: “Unless otherwise instructed by League Officials, players may use Snaptap, SOCD, or other equivalent keyboard technologies.” The ruleset’s change log dates the addition to 17 December 2024.

Two neighbouring rules shape what that permission actually covers. Rule 2.3.4 prohibits “all macro programs, including software macros and hardware implemented macros stored in on-board memory of the hardware, external to the VALORANT game client.” And team-owned equipment “may be subject to competitive integrity checks by League Officials in advance of a Match,” with officials able to refuse equipment “suspected by League Officials of providing an unfair competitive advantage.”

Riot’s competitive-operations library lists a VCT Official Competition Ruleset (2026), last updated 18 December 2025. GearGeeks, which checked each organiser’s published text on 1 October 2026, reports that rule 2.3.5 in the 2026 ruleset still reads the same way. VCT permission is a tournament rule; it does not describe ranked play, and it explicitly defers to officials on the day.

Apex and the ALGS: no named rule

The Apex Legends Global Series Year Six rules do not name SOCD, Snap Tap or rapid trigger anywhere. What they do instead is route the decision through equipment approval. Section 4.3 states that “Competitors are required to supply their own mice, keyboards, controllers, and wired earbuds,” and that “All peripherals will be reviewed and approved by Event Officials prior to use during each Live Event.” Section 5.1 restricts competitors to a single input device for the entirety of each match.

The general backstop is in the code of conduct, which prohibits “Using any software, hardware, peripherals, and accessories designed to give the Competitor an unfair advantage.” Apex does have a precedent for treating automated input as cheating rather than as a hardware nicety: in 2024 Respawn removed chained config files to end controller tap-strafing, and stated that “The use of third-party tools, hardware, firmware, or software that automates game mechanics for a competitive edge over other Apex players is considered cheating and is unacceptable.” None of that mentions SOCD by name. For an ALGS competitor it means the answer comes from an official inspecting the peripheral, not from a clause in the rulebook.

Fighting games settled this first

The keyboard argument is new. The SOCD argument is not. Fighting-game organisers have been writing SOCD rules for years, because leverless controllers hit the same problem long before magnetic-switch keyboards did.

Evo’s controller rules take a permissive line on cleaning but a firm line on the conflict itself: “The controller may not send simultaneous opposite cardinal directions (SOCD) game inputs. SOCD inputs include Left+Right and Up+Down.” The ruleset then explicitly approves standard cleaning methods — neutral, first-input priority and last-input priority — “unless otherwise specified on a game by game basis by pro tour Rulesets.” Stock gamepads such as the DualShock 4 and DualSense are exempt, alongside a general ban on hardware macros, rapid-fire and other assisted mechanisms.

Capcom took the opposite resolution for its 2023 season. Its controller usage rules require that “If up and down directions are input at the same time, both inputs must be maintained or both inputs must be rejected,” and that the character “must not perform a jump or crouch action” on simultaneous up and down. The rules also forbid adding “a button to force a neutral state.” That reversed the older Hitbox convention — EventHubs reported Hitbox’s position that the community standard had been “UP + DOWN = UP” for more than a decade. Capcom also restricts keyboards to the Steam platform and requires them to be paired with a controller at offline events.

Put the two side by side and the pattern is clear. Evo allows last-input-priority cleaning; Capcom rejects it for vertical inputs. Same mechanic, two answers, and neither is wrong — they are different rulebooks making different fairness calls.

What to do before an event

The practical advice is short and it comes straight from the rulebooks. Build a competition profile with SOCD, Snap Tap, last-input priority and any multi-action bind disabled, because that configuration is legal everywhere on this list. Keep rapid trigger on if you want it — no rule surveyed here names it or defines it. Save the profile onboard, close the configuration software, reconnect the board and confirm it boots into the right slot without a background app, since some events inspect peripherals before the match and some supply competition PCs.

EVE Zone’s checklist adds a step that is easy to skip: send officials a description rather than a question. Name the model, the firmware version and the exact behaviour, state that one physical key reports its own press and release according to travel, and confirm that opposing-input priority and macros are off. Ask whether the board may be used for the named stage of the event, and keep the reply with your registration information.

Rules move, too. Valve’s original wording said “initially.” ESL’s ban began as an in-person policy before it became a numbered rule. Riot’s VCT rule has a “unless otherwise instructed” clause built into it. For a player, the useful habit is not memorising a verdict but knowing which document to check before each event and after each firmware update. For a buyer, the two features are separable: rapid trigger’s counter-strafe help survives every rule on this page, and the automated release a SOCD mode adds is the part competitions keep restricting.

Next read