ChecklistSettings & FixesEarly AccessUpdated guide

Dead as Disco Controls, Keybinds, and Accessibility Guide

Dead as Disco 控制、按键与辅助功能指南

A practical setup guide for Dead as Disco controls, keybinds, controller prompts, subtitles, and comfort options without guessing exact menu labels.

Click to play

Control Setup Pass

Treat the first session as input discovery. Pick one primary device, confirm the prompts you see, and avoid judging difficulty until the controls feel predictable. This page is useful even before a final keybind table exists because it tells players what to check first.

  • Choose one primary input device before judging prompts.
  • If you switch between keyboard and controller, restart the check from the first menu screen.
  • Keep accessibility and comfort settings separate from combat difficulty notes.

Check the settings menu first

Open the settings menu before changing how you play. Confirm what the game actually shows for remapping, subtitles, controller prompts, and comfort options, then write down only the labels you can see.

  • Do not assume a remap option exists until you see it in the menu.
  • Check subtitles, screen shake, color, and accessibility toggles one by one.
  • If controller icons look wrong, note the platform and controller model before blaming the game.

Input notes worth keeping

Good input notes are boring, which is why they work. Write down the device, keyboard layout, controller model, connection type, storefront, game version, the menu label you saw, and whether the same prompt appears once you are actually playing.

  • Keyboard: layout, default keys, remap screen, and conflict warnings if visible.
  • Controller: model, connection type, prompt icons, and gameplay confirmation.
  • Menu note: platform, version, and the exact label you saw.

Comfort and accessibility checks

Check comfort options separately from combat difficulty. Look for subtitles, text size, vibration, screen shake, color or contrast settings, hold/toggle behavior, audio cue options, and whether the option changes gameplay or only makes the interface easier to read.

  • Leave unsupported options out instead of guessing.
  • Separate visual comfort settings from gameplay assist settings.
  • Use the exact wording from the menu when a setting label is visible.

Watch the next major update before freezing menu advice

The official Road Ahead post currently places accessibility settings and the tutorial for on-press attacks in the next major update. That means control and menu copy should stay modular for now. Write what players should check today, but keep any exact menu labels or tutorial flow version-sensitive until that update lands and is captured.

  • If a sentence depends on a tutorial prompt, tag it as version-sensitive.
  • Recheck accessibility menus after the next major update instead of copying June layouts forward.
  • Use one current device and one current screenshot before publishing exact labels.

Record The Input Problem Before Changing Buttons

Controls advice becomes more useful when it starts with the problem the player actually saw. Before remapping or switching devices, write whether the issue is prompt mismatch, missed input, late input, hand comfort, camera control, or accessibility readability.

  • Prompt issue: capture platform, controller model, and the visible icon.
  • Timing issue: compare against audio latency before blaming keybinds.
  • Comfort issue: change one setting or device at a time, then retest the same short section.

Separate Remap Evidence From Comfort Notes

A remap note and a comfort note answer different questions. Remap evidence should show what the menu or prompt actually allows. Comfort notes can say what felt easier for one session, but they should not become universal keybind advice. Keep both notes separate so a later menu capture can update facts without erasing player preference guidance.

  • Evidence field: visible menu label, platform, input device, and version.
  • Comfort field: hand strain, repeated miss type, and retest section.
  • Public copy: avoid exact key tables until the menu evidence is visible.

Practical notes

Practical notes from this page

Controls, keybinds, remapping, controller prompts, subtitles, and accessibility toggles should come from visible menus or official notes.

This page explains what to check before publishing exact menu labels or option behavior.

FAQ

Does this page list the final Dead as Disco keybinds?

No. Use it as a setup checklist first. Final keybind tables should come from visible menus or official notes.

Why not publish accessibility options now?

Because exact labels and behavior should come from visible menus, official notes, or captured gameplay. Guessing accessibility options helps nobody.

After this page

Pick the next route

Use these links when you finish the article: continue to a closely related guide, browse the same category, or search the topic if you came here with a different question.