Never Be Alone defaults to WASD movement with a numbered hotbar, and the first patch made that hotbar rebindable for slots 1 through 8. If you played the demo in its first two days, the controls you remember are not the controls that exist now.

Three things decide whether a session feels responsive: the movement rebind, the hotbar layout, and the FOV slider that doubles as a repair for a broken camera. Two known input problems have fixes that are not discoverable by trial, and one of them looks like a catastrophe until you know the trick.

Movement and the rebind situation

WASD is the default. The first patch removed the secondary movement keybinds entirely because they were causing input conflicts, and left the primary row as the one place to rebind movement.

In practice that means: if you want arrow keys or an unusual layout, rebind the primary movement row and leave the old secondary row alone — it no longer exists.

The hotbar

Slots 1 through 8 are bound to the number row by default, and each slot can now be rebound individually. That was the headline input change in Demo Update #1, and it addressed the most common complaint in the first forty-eight hours.

Two things worth doing with it:

  • Put your most-used healing or utility item on a key your left hand can reach without leaving WASD.
  • Keep weapon slots in a consistent physical order across characters and sessions, so muscle memory transfers.

The patch also fixed the scroll wheel inside the pause menu, which previously did not respond. If you are on an older build and the pause menu feels unresponsive to the wheel, that is the bug.

Aiming, shooting and the inventory

Three separate input bugs were fixed in the same patch, and all three were the kind that make a game feel broken rather than difficult:

  • Shooting after closing the inventory did not always register. Fixed.
  • Aiming down sights could get stuck in the aimed state. Fixed.
  • Invert X and Invert Y were swapped — turning on inversion flipped the wrong axis. Fixed.

If you are running the current demo build, all three are gone. If you are troubleshooting an older install, updating the demo is the fix rather than a settings change.

Mouse feel

Mouse smoothing and mouse acceleration are disabled by default in the current build. That is deliberate: both add latency that a game with precise aiming cannot afford.

If the camera still feels sluggish, the problem is more likely frame rate than sensitivity. Check the graphics settings before raising sensitivity, because a low frame rate produces input lag that no sensitivity slider can fix.

The FOV slider is also in this menu, and it does more than widen the view — see the next section.

The camera-inside-character bug

There is a documented first-launch bug where the third-person camera starts inside your character. It is rare, it is not reproducible on demand, and it has a one-step fix.

Open settings and move the FOV slider by 0.1. The camera corrects immediately. You can move it back afterwards; the trigger is the change event, not the value.

Why this is worth knowing before you play

The bug looks catastrophic when it happens — a screen of the inside of a character model — and the fix is not discoverable. Knowing it in advance turns a refund request into a two-second adjustment.

Controller support

The store lists partial controller support, and the studio's own description is that pad support is mostly implemented with a few outstanding issues.

The specific known problem: Unreal Engine occasionally registers the controller's bottom face button as a mouse input, which breaks menu navigation. The workaround the studio recommends is to watch the button icons the UI displays rather than assuming a conventional layout — the game tells you which button it wants, and that prompt is more reliable than muscle memory right now.

Keyboard and mouse remain the safer choice if you are doing anything precise. Controller is viable for exploration and co-op play, less so for long-range encounters.

Audio settings that matter

The current build exposes separate SFX volume control, and the first patch fixed UI sounds and landing sounds failing to respect it. So if you turn effects down, menus and footsteps now follow.

That matters more than it sounds in a survival game where audio is a primary warning system. A build where the interface ignores your volume slider is a build where you cannot trust what you hear.

A two-minute setup for a first session

  1. Open Settings > Gameplay and set the survival systems to a level you actually want to manage.
  2. Check the FOV slider — and if the camera is inside your head, nudge it by 0.1.
  3. Rebind the hotbar slots you will use every fight.
  4. Turn effects volume to something you can hear clearly without it being uncomfortable.
  5. If you are on a controller, play the first ten minutes in the menu system to learn which button the game thinks is "select".

That is the whole checklist. None of it is optional polish — the first two items are the difference between a session that works and one that fights you.

Where these fixes came from

All of it traces to Demo Update #1, published on 21 October 2026, two days after the demo launched. The full change list, including the balance and audio fixes that came with it, sits in the patch notes for that update.