BACK TO ALL DEV LOGS
DEVELOPER DIARY•2026-08-21

A Controller Should Not Erase the Mouse

I separated the control hint I need from the pointer I still have, so mixed-device command does not feel broken.

Solo Developer
Lead Game Designer & Pilot

The mouse was still on the desk, but the ship could behave as if it had vanished. August 21 corrected that small piece of nonsense. A controller input changed the visible button hints, and the pointer could disappear with them. A hint about one device had been allowed to deny the existence of another.

I dislike controls that make me negotiate allegiance. A controller is good for settling into the weight of flight. A mouse can be good for choosing something on a dense screen. The ship should let a captain move between those tasks without turning the change into a ceremony.

The failure was especially unfair when controller noise could erase a basic desktop control. The player had not decided to abandon the mouse. The ship had inferred too much from the last input it noticed. That kind of cleverness feels much less clever from the receiving end.

I kept the useful part of the old decision: hints should describe the controls a captain is currently using. The pointer has its own simpler rule. If a valid desktop pointer belongs in the current context, it stays visible. Free aim keeps the dedicated reticle over the scene. The words can follow the controller without making the mouse appear broken.

There is no grand spectacle in this correction, and I do not want to inflate it. Its value appears between spectacles. Picture the ship holding a slow turn under a distant nebula. A captain opens a command screen, reaches for the mouse to inspect a contact, and then returns to the controller. The enormous ship continues to feel like one coherent thing through that ordinary change of hand.

I find that continuity pleasing. It lets the bridge feel accommodating without being uncertain. Equivalent ways to command the ship can stay equivalent while their hints remain specific. The captain should know which button to press, and also see where the pointer is. These requirements do not need to fight.

The distinction is small enough to sound pedantic until the pointer disappears. A button hint tells me how to act. An arrow tells me where I am pointing. Keeping both truthful makes the screen less surprising in the best possible way. I want the surprise to belong to the contact beyond the bow, rather than the hand reaching for it.

This small correction still matters when a journey is long. Reading a contact and steering away from it should belong to the same act of command. A ship should respect the physical controls its captain actually has.

The fantasy is an immense command chair with a galaxy beyond the bow. Getting into that chair should never require convincing the bridge that my other hand still exists.

Reviewed & Approved by Editor Agent