Most League of Legends players had no idea this was coming. Buried deep inside the dev blog that accompanied WASD mode's Ranked release, Riot Games quietly enabled native controller support for the first time in the game's history. Community account SkinSpotlights spotted it on April 17 and posted about it on X, and the discovery spread fast.
Here's the thing: this wasn't a secret rollout or an accidental leak. Riot confirmed it in writing. The detail just got lost in a long blog post, and the community is only now catching up.
What changed from mouse-only to controller-ready
Before this update, playing League of Legends with a controller meant routing through third-party software to remap inputs manually. It worked, technically, but it was never clean. Content creator BoxBox famously pulled it off to great effect, but it required setup that most players weren't going to bother with.
The WASD input mode changes that entirely. When you enable WASD movement in League of Legends, controller input is automatically activated alongside it. No extra software, no manual remapping. The default button layout maps abilities and actions directly to controller buttons:
- LT maps to Q
- LB maps to W
- RB maps to E
- RT maps to R
- X maps to D (summoner spell)
- Y maps to F (summoner spell)
- A maps to Auto-Attack
- D-Pad Down maps to Trinket
- Left analog stick controls mouse cursor movement
The layout is functional rather than polished, but it covers the core inputs a player needs to actually play a match.
Accessibility first, broad support not planned
Riot was direct about the intent. The WASD team's dev blog explicitly framed controller support as an accessibility feature, not a move toward full console-style input support. The stated goal is to allow players with mobility limitations to use widely-available hardware like the Xbox Adaptive Controller.
The controller feature sits within a larger input system overhaul that also brought custom cursor movement inputs and expanded keybinding options to the game. That broader update represents a meaningful shift in how Riot is thinking about input flexibility, even if full controller support remains off the official roadmap for now.
What most players miss about the timing here
The WASD mode itself only recently hit Ranked after passing Riot's balance testing phase. The fact that controller support arrived alongside that milestone rather than as a separate announcement explains why so many players missed it. It wasn't treated as a headline feature.
Riot did note they continue to monitor player requests around controller and joystick support, which leaves some room for the feature to expand. For now, though, the experience is barebones by design. The key here is that it works natively, which is a first for League of Legends regardless of how limited the scope is.
For players curious about how the full WASD system fits into the broader Season 2 changes, browse more gaming news for context on what else arrived in that update. If Riot does decide to expand controller support beyond the accessibility lane, the infrastructure is now at least partially in place to build on.
