Controller Support Guide

02

Decisions for Controller Support Guide

The useful question is not how to fill every field today, but which claim changes the next player action. These page-specific decisions keep controller support guide practical while the full release remains gated.

1. Separate Steam feature metadata from actual navigation coverage.
2. Treat the existing keyboard-gap report as community-reported.
3. Recheck menus, gameplay and rebinding separately in the release build.

03

How to use this field guide

Start with platform, build and symptoms; look for an official acknowledgement; preserve reversible troubleshooting steps; and recheck reports after each patch or release-state change.

For controller support guide, follow the in-game state first and use this page to organize decisions, not to override evidence shown by your build.

04

A practical field workflow

This sequence keeps observations reproducible and makes release-day corrections straightforward.

1. Record platform, build and exact symptom.
2. Try reversible baseline checks first.
3. Look for a developer reply or official patch note.
4. Label community evidence at community strength.
5. Close, revise or recheck the item after a build change.

05

What remains deliberately open

Exact recipes, thresholds, rates, capacities, unnamed entities and hidden completion conditions stay unpublished until an official source or repeatable current-build check supports them. In every table, an unknown is an evidence state—not a zero, a negative answer or missing work.