League of Legends is testing controller support and WASD movement

Esports News UK, Senior Editor

Last Updated: 20/04/2026

League of Legends has quietly enabled native controller support alongside its April 17 WASD discovery window and the mode’s move into ranked-facing testing. That matters because any serious change to how players move, kite and cast in League immediately raises questions about execution parity, onboarding and whether Riot is opening a new long-term lane between accessibility tools and competitive inputs.

For a game that has been mouse-first since 2009, this is not a small settings tweak. Even if Riot is framing the feature narrowly, native support changes the conversation from “can players force this with third-party software?” to “what happens when Riot itself supports alternate inputs inside the live client?”

Riot has confirmed native controller functionality, but only as an accessibility extension of WASD

According to Games.GG, Riot confirmed in its WASD dev blog that controller input now works natively when players enable the new movement mode, after the feature was spotted by SkinSpotlights on April 17. The default mapping is basic but real: LT, LB, RB and RT map to Q, W, E and R, X and Y map to D and F, A handles auto-attack, D-Pad Down uses trinket, and the left stick controls cursor movement.

Riot’s wording is the key part here. The studio said, “While we don’t have plans to officially support controllers or joysticks broadly right now, we did want to enable play on joysticks through remapping of WASD for accessibility reasons,” explicitly positioning the feature around players with mobility limitations and hardware such as the Xbox Adaptive Controller. That is the key distinction: controller functionality is confirmed, but any broader conclusion about full console-style support or a permanent shift in default League inputs remains inferred rather than announced.

The change creates real execution questions for pro play even if Riot does not intend it as a competitive feature

The competitive significance is less about pro players suddenly swapping to pad and more about what WASD movement changes underneath the game’s mechanical assumptions. Riot has already spent months testing parity, and reporting around the feature’s wider rollout has stressed balance checks across roles, ranks and champion classes, including concerns around kiting and move-attack patterns in high-speed fights. In practical terms, ADCs and some skirmish-heavy champions stand out first because cleaner directional movement can reduce misclick risk during chase and peel sequences.

That matters most in regions where execution margins are already tiny. LCK and LPL bot lanes win fights off pixel-level spacing, while LEC teams are often quicker to test edge-case tech if Riot leaves enough room for it to stick. If WASD plus native controller remapping produces even a niche comfort advantage for certain players, coaches will at least want data on whether drills, champion pools or practice tools should adapt.

Riot’s accessibility framing also matters competitively because it lowers the chance of immediate esports disruption. This is not being sold as a new standard input, and that should limit short-term uptake in scrims and on stage. The failure mode, though, is clear: if Riot has underestimated how much easier some movement and kiting patterns become under alternate inputs, the conversation shifts fast from accessibility option to competitive integrity review.

Riot is treating input flexibility as part of a wider Season 2 philosophy rather than a one-off experiment

This lands in a season where Riot has already signalled a more selective approach to major systemic disruption. As readers will have seen in our coverage of League of Legends Season 2 2026 changes, the studio is trying to move important systems without detonating the calendar with constant resets, and alternate movement fits that pattern better than a headline-grabbing overhaul would.

It also lines up with a broader push around how players access Riot’s ecosystem and tools. Riot has been expanding platform touchpoints elsewhere too, as in our recent report on the company’s Discord integration plans for LoL and Valorant, and controller accessibility sits naturally inside that same “meet players where they are” logic. There is also a welfare dimension here: input flexibility will not solve every barrier, but it belongs in the same serious accessibility conversation as our coverage of player welfare and physical performance research in LoL esports.

That wider context makes this easier to read correctly. Riot is not suddenly turning League into a twin-stick MOBA, but it is showing more willingness to rethink old assumptions about who the game is built for and how rigid its inputs need to remain.

The next thing to watch is whether ranked data supports Riot’s accessibility framing

The clearest next milestone is not a flashy announcement but the data Riot chooses to talk about once WASD has spent real time in ranked and live environments. Reporting from ONE Esports and earlier rollout details noted Riot’s focus on bugs, champion-specific interactions and long-term win-rate checks by role and skill band, which is exactly where the real answer will come from.

If controller-enabled WASD remains a low-uptake accessibility tool, Riot’s current message holds. If specific archetypes, especially ADCs or high-tempo skirmish picks, begin showing cleaner execution or uneven regional adoption, the next question becomes whether Riot has introduced a meaningful competitive variable under the softer label of accessibility.

Esports News UK, Senior Editor

All Posts By Esports News UK