Press "Enter" to skip to content

Cyberpunk 2077 without hands

How it started

 

Proper autumn has finally set in outside my window, and the rain barely stops. I started going out less and less, and before long I got bored—which often happens when I stay indoors for too long.

Looking for something to do, I asked my friend Sergey for advice. Like me, he has spinal muscular atrophy (SMA). He recommended the Netflix anime series Cyberpunk: Edgerunners. I binged all ten episodes and didn’t want to leave Night City just yet, so I decided to download Cyberpunk 2077 by the Polish studio CD Projekt Red.

Because of SMA, my hands barely work. I can move a mouse, left-click, and press a few keys on a Razer Tartarus Pro gaming keypad. Everything else is handled by PlayAbility, an app that turns spoken words and facial expressions into key presses. I figured that with PlayAbility and a couple of extra buttons, I could really play.

The short answer: yes, I could, and it is a real, full-scale game. The long answer starts with the tutorial mission. That is where I discovered that the game expects very different things from its keys: some actions need a crisp tap, others need a hold, and every hold has its own duration. Crouching only works on a quick tap and ignores a slow press. Tapping T opens a notification, while pulling up the phone takes a half-second hold. Getting out of a car requires holding F for a full second.

PlayAbility, meanwhile, only offers four press modes: a short tap (0.1 s), a long press (0.3 s), a toggle, or holding a key for as long as a facial gesture lasts. Each of the game’s awkward inputs needed its own workaround. I even wrote to the PlayAbility developers asking them to add a setting for custom hold durations.

I found those workarounds together with Claude, an AI assistant. I described by voice what wasn’t working; Claude inspected the game’s configuration files, wrote a script, and helped me test it.

What I play with

My controls are split across four layers, and each one covers what the others can’t.

Tool Role
Mouse Looking around, aiming, shooting with left click
Razer Tartarus Pro + Synapse Thumbstick movement, reload, aim, macro crouch
PlayAbility Spoken Russian words plus face and head gestures
AutoHotkey script Custom hold timings, key combos, on-screen cheat sheet

The script is written in AutoHotkey, a free Windows program that triggers keys and mouse buttons according to rules you define. Our script only acts inside the game window; in other programs, the same keys work as usual. It sits as an icon in the system tray, and any of its features can be switched off from its menu with a single mouse click.

Where PlayAbility stops at 0.1 s and 0.3 s presses, the script bridges the gap. A spoken word triggers a spare key, and the script turns it into the exact action and timing the game expects. One desktop shortcut launches the game together with the script, and when I close the game, the script closes itself.

How the setup went

Every step started with a single sentence from me, like “I can’t crouch.” Then Claude looked into the game’s configuration files to see how the engine expects that input, and fitted my controls to match. The voice commands below are the Russian words I actually say out loud while playing.

Problem Cause Fix
Crouching Slow hand press ignored Synapse macro (0.05 s tap)
40+ commands Too many words and gestures Slim cheat sheet at top of screen
Stuck keys Toggle mode leaves keys held Top bar warns at 0.7 s, turns red at 5 s
Tangled bindings Two actions on one key Reset to default, kept crouch on 0 and tag on 5
Heavy attack Needs 0.3 s+ left-click hold Spoken word «бокс» (“boxing”, 0.6 s hold)
Dodging Direction hold + quick Ctrl tap Four words: «рывок», «откат», «запад», «восток»
Phone Needs 0.5 s hold on T «новости» (“news”, tap) and «телефон» (“phone”, 0.5 s)
Weapon wheel Needs held Alt, no spare buttons «колесо» (“wheel”) holds Alt until click, blocks Alt+Tab
Driving Nothing left to steer with «руль» (“steering wheel”) mode steers by turning my head
Sharp steering Held arrow key locks wheel fully Short pulses, reaching full lock after 4.5 s
Exiting a car Cheek gesture too short for 1 s hold In driving mode, script holds F for 1.2 s
Menu actions Upgrade and Disassemble need 0.4–0.8 s hold Cut hold to 0.05 s in inputContexts.xml
Braindance Rewinding requires a held key «мозг» (“brain”) toggles rewind on and off

One thing surprised me: for some reason, the developers removed the option to simply click certain menu actions with the mouse. For example, “Upgrade” at the ripperdoc and “Disassemble” in the inventory only work from the keyboard, and only with a hold. There may be mods that fix this, but since I am completely new to the game and haven’t set up mods yet, we simply shortened the hold duration in the game’s inputContexts.xml settings file—the same trick “instant crafting” mods use.

Even a studio as renowned as CD Projekt Red only covered the basics for accessibility. Aiming, sprinting, and crouching can be switched from hold to toggle, and there are subtitles. But how long you have to hold a key cannot be changed in the menus at all, and some interface actions ignore the mouse entirely. For a player who can’t hold a key down for long, that is a wall I had to get around on my own.

Mistakes and lessons

  • Not every game file is safe to edit. Changing one key-layout file (inputUserMappings.xml) stopped the game from starting, so we restored the original and now back up every file before editing.
  • Timing matters more than the key itself. The same key does completely different things on a tap and on a hold; almost every roadblock came down to press duration.
  • Two actions on one key cancel each other out. When a command suddenly “does nothing,” look for duplicate bindings first.
  • One gesture can do different jobs. Turning my head triggers my implant and scanner on foot, but steers when I am in a car; one spoken word switches the mode and brings up a yellow cheat sheet right away.
  • Passing the error check isn’t enough. Once the script passed validation but crashed on the first held key because AutoHotkey ignores letter case in names, so now Claude tests a copy that logs key presses instead of sending them to the game.
  • Distrust is useful. When I thought Claude was getting me confused, it didn’t argue—it recorded which presses actually came from the mouse, proving that checking the facts beats a confident tone.

Where it stands

In just a few days, Night City became playable with about forty spoken words, five face and head gestures, the mouse, and four Tartarus buttons. Steering through the rain-slicked streets by turning my head, crouching via macro, and glancing at the top-screen cheat sheet are already tested in action, and I am tuning the rest as I play through the story.

We deliberately chose single-word commands that can’t be confused by ear, with no similar-sounding neighbors. That is why my combat dodges are «запад» (“west”) and «восток» (“east”) rather than “dodge left” and “dodge right”—in the middle of a firefight, distinct phonetics matter.

The main thing I took away: you don’t have to adapt to the game. Every awkward spot can be named out loud and reshaped to fit you.

If you also play with limited mobility, tell me in the comments which games and settings have worked for you. And if you make games, remember: a setting for hold duration and the option to click any menu button with the mouse cost little, but they open the game to players like me.

 

Join GOAT Notes

Follow the Blog for short updates and ideas.

Join the Newsletter for a rare roundup every 1–3 months.

Select list(s):

Feeds: RSS | Atom
Leave a Reply

Your email address will not be published. Required fields are marked *