Revenant Survivors
Menu

Revenant Survivors · Independent guides

Revenant Survivors controller and auto-attack checks

Check the auto-attack mode first. The developer describes separate options for automating Basic Attack plus Strike, or Basic Attack alone with manual Strike. Steam currently lists full controller support. Older playtest reports describe incomplete menus and interactions, so match each report to its version.

Megabonk.org editors · Checked 12 November 2026 · Early Access

Revenant Survivors level-up choice screen with three cards and an Auto-Attack On indicator
Combat automation and selecting a level-up card are separate inputs to check when reporting controller behavior. Mongma Studio Steam promotional screenshot, capture build unspecified.

Check what the selected attack mode automates

In the difficulty discussion, the developer explains the two auto-attack settings. If Basic Attack happens automatically while Strike still needs input, inspect whether the Basic-only option is selected. Developer explanation of auto-attack modes ↗ (opens in a new tab)

  1. Open Settings and inspect the current auto-attack choice.
  2. Choose whether Strike should also be automated, then follow the current UI’s confirmation prompt.
  3. Return to combat and observe Basic Attack and Strike separately.
  4. If neither activates as expected, record the controller model, mode and exact behavior for a report.

Separate historical problems from the release listing

The August controller thread contains reports of movement working while menus, skill choices and interactions were incomplete. The developer acknowledged those limitations on August 18. Later playtest updates addressed controller support and portal input, while the September 4 discussion identified another Demo input issue after Steam Input was introduced. Historical controller discussion ↗ (opens in a new tab) · Demo input follow-up ↗ (opens in a new tab)

The current Steam store listing ↗ (opens in a new tab) advertises Full Controller Support. That listing and the older reports have different dates and scopes. Use the installed release’s behavior to decide what still needs reporting.

Describe the input that fails

A useful report distinguishes movement, aiming, Basic Attack, Strike, menu navigation, level-up selection and portal interaction. Include the game edition, version, controller model, connection type and Steam Input state. These details let the developer reproduce a narrower failure than “controller broken.”

One playtest participant reported enabling auto attack through the mouse’s middle button before returning to the controller. That is an old player-reported workaround with no current-release verification here. Treat it only as historical context. This guide has no device-specific controller test or Steam Deck performance measurement.