Melee Controller Rules FAQ
UPDATED FEB.10TH, 2026Below is a comprehensive FAQ aimed at helping you with complying to the current controller ruleset for Melee. Please check with your controller manufacturer on how to update your controller's firmware.
Who does this affect?
ALL players are expected to abide by these rules at all levels of play including R1 pools. This impacts both traditional and leverless controllers.
Will this be enforced at GX3?
We intend to spot check compliance with the controller rules during all parts of the tournament, and ALL matches in top 64 will be explicitly checked. Entrants who are found to be noncompliant will be DQ'd at the organizers' discretion.
How can I make sure my controller is legal?
You'll need to make sure your controller has firmware that complies with the requirements of the ruleset. For most phob and box-style controllers, you can simply make sure your controller firmware is updated to use its respective firmware version.
All third-party controllers with custom firmware must abide by the requirements below
-
Any third-party controller must make publicly available the portion of its firmware source code that governs input and output behavior. This requirement exists to ensure transparency and to allow verification of compliance with the technical standards listed in the full ruleset.
-
Controller must implement neutral simultaneous opposing cardinal direction (SOCD) cleaning on both the horizontal and vertical axes. This prevents input combinations that result in illegal or unintended directional behavior.
-
Any buttons that modify stick behavior (e.g., shield modifiers or analog angle assists) must be constrained to function in ways comparable to a standard GameCube controller.
-
Analog stick inputs must reflect realistic movement speeds, simulating the physical travel time of the GameCube controller’s stick.
-
Output must include small, non-deterministic variation to prevent precise coordinate targeting, without affecting normal gameplay.
-
Angles and coordinates that are impractical to perform consistently on a GameCube controller—such as frame-perfect aerial drift or Peach’s two-frame Parasol Dash—must not be directly accessible.
-
Input lockouts must prevent actions that would exceed the timing capability of physical inputs, such as burst SDI sequences or frame-exact pivots.
-
If the C-stick is reassigned to digital inputs (e.g., split into buttons), the controller must use logical grouping to simulate analog input behavior.
-
Versions 0.29 and greater of the PhobGCC repository
-
There is currently no compliant Goomwave firmware. Thus Goomwave controllers are banned unless compliant firmware becomes available
-
Versions 23.0 and greater of the ruleset-compliant HayBox repository
-
Your controller may require a board swap in order to be compliant.
We will have someone available onsite at Genesis to help you do this but you may want to do this before coming to Genesis.
IMPORTANT LINKS
The full ruleset, technical breakdown, and a complete list of controllers and their updated compliant firmware filenames.
copy and paste version below
Firmware Transparency
Any third-party controller must make publicly available the portion of its firmware source code that governs input and output behavior. This requirement exists to ensure transparency and to allow verification of compliance with the technical standards listed in the full ruleset.
NeuTral SOCD Handling
Controller must implement neutral simultaneous opposing cardinal direction (SOCD) cleaning on both the horizontal and vertical axes. This prevents input combinations that result in illegal or unintended directional behavior.
Modifier Limitations
Any buttons that modify stick behavior (e.g., shield modifiers or analog angle assists) must be constrained to function in ways comparable to a standard GameCube controller.
Travel Time Simulation
Analog stick inputs must reflect realistic movement speeds, simulating the physical travel time of the GameCube controller’s stick.
Signal Variation (Fuzzing)
Output must include small, non-deterministic variation to prevent precise coordinate targeting, without affecting normal gameplay.
Restricted Access to Impractical Angles
Angles and coordinates that are impractical to perform consistently on a GameCube controller—such as frame-perfect aerial drift or Peach’s two-frame Parasol Dash—must not be directly accessible.
Timing Lockouts
Input lockouts must prevent actions that would exceed the timing capability of physical inputs, such as burst SDI sequences or frame-exact pivots.
C-Stick Clustering
If the C-stick is reassigned to digital inputs (e.g., split into buttons), the controller must use logical grouping to simulate analog input behavior.