Computer controls #80

New issue

Closed

opened 2026-08-21 15:19:50 +00:00 by metaheavens · 1 comment

metaheavens commented

2026-08-21 15:19:50 +00:00

Owner

On computer aiming the default shot should be done with the mouse and left click. to use special abilities, use numbers to select the weapon type (1 default, 2 gas bomb ...)

metaheavens added this to the Spaceship Tasks project

2026-08-21 15:19:50 +00:00

metaheavens referenced this issue from a commit

2026-08-21 16:49:51 +00:00

Implement #80, #81, #82 and #83

metaheavens commented

2026-08-21 17:45:28 +00:00

Author

Owner

Done in baac11a, live at https://metaheavens.de/spaceship/

The mouse aims, the left button fires, and the number keys pick the weapon - 1 the fleet's guns, 2 the gas bomb, 3 the laser.

The pointer path hands its heading to FireStickController rather than driving weapons itself, so exactly one thing in the scene aims a gun. A held stick wins over the mouse: a finger on it is a deliberate act, a mouse resting somewhere is not. Abilities gained fire_at(), which aims and fires in one call rather than pretending to be a press-drag-release touch.

The weapon numbering resolves controllers by name in a fixed order, so "2" is the gas bomb in every scene - discovering them by scanning children would tie the number keys to scene node order, which is not something a player can see or rely on.

It is gated on the absence of a touchscreen, because Godot emulates a mouse button from every touch and without that guard a tap on a phone would fire the guns. The gate has an explicit override, and not for tidiness: headless reports a touchscreen, so with the automatic answer alone the aiming could never be exercised by a test and the only covered behaviour would be the guard itself.

Done in baac11a, live at https://metaheavens.de/spaceship/ The mouse aims, the left button fires, and the number keys pick the weapon - **1** the fleet's guns, **2** the gas bomb, **3** the laser. The pointer path hands its heading to `FireStickController` rather than driving weapons itself, so exactly one thing in the scene aims a gun. A held stick wins over the mouse: a finger on it is a deliberate act, a mouse resting somewhere is not. Abilities gained `fire_at()`, which aims and fires in one call rather than pretending to be a press-drag-release touch. The weapon numbering resolves controllers **by name in a fixed order**, so "2" is the gas bomb in every scene - discovering them by scanning children would tie the number keys to scene node order, which is not something a player can see or rely on. It is gated on the absence of a touchscreen, because Godot emulates a mouse button from every touch and without that guard a tap on a phone would fire the guns. The gate has an explicit override, and not for tidiness: headless *reports* a touchscreen, so with the automatic answer alone the aiming could never be exercised by a test and the only covered behaviour would be the guard itself.

metaheavens closed this issue

2026-08-21 17:45:28 +00:00

metaheavens referenced this issue from a commit

2026-08-22 01:19:58 +00:00

#89: the default gun bends onto a target near the aimed heading

metaheavens referenced this issue

2026-08-22 01:25:25 +00:00

make the default shot automatically aim for the closest target in the input direction to make aiming easier. shot should go further #89

metaheavens referenced this issue from a commit

2026-09-16 05:42:26 +00:00

#231, #230: a key per ability, and an upkeep sheet that adds up

metaheavens referenced this issue