Direct Answer
If you cannot move around in IRON NEST, first read the current objective and visible control prompt, finish or exit the active interaction, and test the documented movement input again. The collected sources do not establish one universal fix or prove that every immobility state is a bug. Record the mission, station, prompt, and version before escalating the issue.
Check the Active State
The beginner material describes movement and interaction as part of a larger station-to-station workflow. If a screen, report, map, calculator, loading sequence, or fire-control interaction is still active, the game may be waiting for that step rather than accepting free movement. Read the visible prompt and complete the current action before changing inputs.
Do not assume that a lack of movement means the keyboard is broken. The correct interpretation depends on the objective and the interface state shown in the current build. If the prompt is missing or contradictory, capture that exact state as evidence instead of inventing a hidden key.
Verify the Documented Controls
The approved third-party beginner guide is the source for the published basic control description, including movement, looking, and interaction context. Treat those bindings as version-sensitive help, not immutable official documentation. Test one input at a time and watch whether the camera, character, or station state changes.
A control that works in a video may not behave identically after an update, in a different input layout, or while another interaction has focus. Keep the pointer and focus state clear, then retest from the current objective. Mark any control discrepancy To be confirmed until a current source or in-game reproduction supports it.
Return to the Task Loop
The supported operating loop begins with High Command and Field Reports, then moves through map marking, ballistic calculation, loading, gun laying, and firing. If movement stops while you are inside that loop, return to the last completed step and read the next instruction. This avoids discarding a valid task state while trying random inputs.
Use a short note with the current objective, the station you entered, the last prompt, and what input was pressed. That note helps separate a task gate from a repeatable input failure. It also makes a later comparison against a patch or another player report possible.
When It Looks Like a Bug
A bug report needs more than the sentence “I cannot move.” Include the current mission or screen, the visible prompt, whether the camera still responds, whether interaction is open, the input method, and whether restarting changes the state. Preserve the sequence that led to the problem instead of overwriting it with an unrecorded reload.
The current sources do not provide an official movement-bug catalogue, a guaranteed reset command, or a fixed troubleshooting matrix. Any proposed fix beyond the documented workflow is therefore To be confirmed. Do not present a player workaround as a universal rule.
What This Page Does Not Claim
This page does not claim hidden controls, a specific key combination, a universal soft-lock, or a guaranteed save repair. It gives a reproducible checking order based on the collected beginner material and the game loop visible in the research. Use the current game prompt first.
If the same state reproduces after a clean restart and the official source or current patch notes acknowledge it, update the page with that evidence. Until then, keep the cause and remedy marked To be confirmed.
Sources and Evidence Limits
Official, third-party, and player sources are kept separate. Version-sensitive claims remain To be confirmed until current evidence supports them.
- [A] Pro Game Guides beginner guide: Pro Game Guides beginner guide. Use this source only for the claim boundary described on this page.
- [B] Official site: Official site. Use this source only for the claim boundary described on this page.
- [C] Gameplay video one: Gameplay video one. Use this source only for the claim boundary described on this page.