Signal Harbor is a side-scrolling shooter where the mission is measured by people delivered to safety, not enemies destroyed. The pilot can fire to disrupt drones, but shots add no progress. Four rescue capsules sit along a fixed route, and the ship can carry only two passengers before reaching a beacon.
Passengers slow the craft, so collecting everyone at once makes the next hazard harder to cross. A beacon unloads the pod and clears its cargo slots. The player must decide whether to rescue another survivor, reach the next station with a full pod, or use the weapon to make a dangerous lane safer. The mission succeeds after three survivors are delivered.

Replace the kill counter with delivered survivors
Build Signal Harbor as a horizontal shooter across a fixed 100-unit route with three flight lanes: upper, middle and lower. The rescue craft moves forward at 4 units per second when empty, 3 units per second with one passenger, and 2 units per second with two passengers. It has 3 hull points. Four survivor capsules are placed at route coordinates 20 upper, 40 lower, 60 middle and 80 upper. To collect one, the craft must be in the matching lane within 2 route units and hold Rescue for 1 second; the craft cannot fire or change lanes during that hold. The detachable pod has capacity 2. Safe beacons at coordinates 50 and 90 automatically deliver every passenger aboard and clear cargo capacity. Delivered survivors persist between beacons. The mission ends when the craft reaches coordinate 100. Save at least 3 of the 4 survivors to win; otherwise the mission fails. Drones at coordinates 30 and 70 fire telegraphed shots at fixed lane positions. The player can fire to disable a drone for 3 seconds, but destroyed or disabled enemies add no score and are not required for victory. A projectile hit removes 1 hull; at 0 hull, the mission fails. Show route position, lane, cargo, delivered count, hull, next beacon and rescue hold progress. Do not display a kill counter or award victory for enemy count. Once a passenger is delivered, it cannot be lost. Capsules not collected by the time the craft passes their coordinate remain behind and are missed. Use fixed capsule and drone placements for the first prototype.
| System | Prototype rule |
|---|---|
| Route | Horizontal route from x=0 to x=100; three lanes: upper, middle, lower. |
| Movement | Forward speed: 4 units/s empty, 3 with one passenger, 2 with two passengers. |
| Capsules | At x=20 upper, x=40 lower, x=60 middle, x=80 upper; missed after craft passes the coordinate. |
| Rescue | Match lane within 2 route units; hold Rescue for 1 second; no lane change or firing during hold. |
| Cargo | Match lane within 2 route units; brake to a stop and hold Rescue for 1 second; no lane change or firing; enemies keep acting. |
| Beacons | At x=50 and x=90; automatically deliver all carried passengers and free cargo slots. |
| Victory | Reach x=100 after delivering at least 3 survivors; fewer than 3 is a mission failure. |
| Combat | Drones at x=30 and x=70 fire telegraphed shots; player fire disables a drone for 3 seconds but gives no score. |
| Hull | 3 hull points; each projectile hit removes 1; 0 hull ends the mission. |
| HUD | Show route, lane, cargo, delivered count, hull, next beacon and rescue hold progress; omit kill counter. |

Set pickup, cargo and beacon rules
The craft starts empty at x=0 in the middle lane with 3 hull. It moves to x=20, switches to the upper lane before reaching the capsule, and holds Rescue for one second; survivor 1 enters the two-seat pod. Cargo weight reduces speed to 3 units per second. The craft reaches x=40, switches to the lower lane and holds Rescue again, filling both seats. Moving at 2 units per second, it reaches beacon x=50 and automatically delivers two survivors; cargo returns to zero and the HUD shows 2 delivered. The craft continues to x=60, enters the middle lane and rescues survivor 3. It may fire at the drone near x=70 to disable it for three seconds, but this does not change the delivered count. The craft reaches beacon x=90 and delivers survivor 3. At x=100, the mission succeeds because three survivors reached safety. The kill count never enters the success check. This is authored state arithmetic, not a playable or user test.
| Event | Expected state |
|---|---|
| Start | x=0, middle lane, 3 hull, 0 cargo, 0 delivered. |
| Rescue capsule at x=20 | Switch to upper; hold Rescue for 1 second; cargo 1; speed becomes 3. |
| Rescue capsule at x=40 | Switch to lower; hold Rescue; cargo 2; speed becomes 2. |
| Beacon x=50 | Deliver 2 passengers; cargo becomes 0; delivered count becomes 2; speed returns to 4. |
| Rescue capsule at x=60 | Switch to middle; hold Rescue; cargo becomes 1. |
| Drone at x=70 | Optional shot disables drone for 3 seconds; delivered count is unchanged. |
| Beacon x=90 | Deliver survivor 3; cargo becomes 0; delivered count becomes 3. |
| Finish x=100 | Win with 3 delivered; enemy count is not checked. |
Trace a rescue run through two beacons
Tell the generator which visible number determines success. Define rescue range, hold time, pod capacity, speed penalties, beacon delivery, hull failure and what the weapon does without letting enemy defeats become the hidden objective.
Create a horizontal shooter called Signal Harbor on a fixed route from x=0 to x=100 with upper, middle and lower lanes. The rescue craft moves at 4 units per second empty, 3 with one passenger and 2 with two. Give it 3 hull points; each projectile hit removes 1 and zero hull fails. Place survivor capsules at x=20 upper, x=40 lower, x=60 middle and x=80 upper. To collect, match the lane within 2 route units and hold Rescue for 1 second; the craft brakes to a stop and cannot fire or change lanes during the hold; enemies continue their attack pattern. The detachable pod holds 2 passengers. Safe beacons at x=50 and x=90 automatically deliver everyone aboard and clear cargo capacity. At x=100, win only if at least 3 of 4 survivors have been delivered; otherwise fail. Drones at x=30 and x=70 telegraph shots at fixed lanes. Player fire disables a drone for 3 seconds but never gives score or mission progress. Passing a capsule coordinate without collecting it leaves it behind. Display route position, lane, cargo, delivered count, hull, next beacon and rescue hold progress. Do not display a kill counter or use enemy count for victory. Use fixed spawns and explain every failed rescue attempt. This is a design specification; do not claim a playable build or test.
Prompt AI to build the rescue shooter
A first score draft awarded points for destroying drones, which pulled attention away from rescue. The revised HUD tracks survivors delivered, pod cargo and hull only. Firing remains useful because a disabled drone briefly opens a safer route, but it never increases mission progress.
The cargo rule also needed a consequence. Carrying one survivor lowers speed from 4 to 3 units per second; a full two-seat pod lowers it to 2. The safe beacon unloads passengers automatically, so the player has a clear reason to deliver before attempting the next pickup. The craft stops during the one-second rescue hold while drones keep acting, making the pickup window a deliberate risk.

Revise a scorekeeping ambiguity
Prototype one route with four fixed capsule positions and two beacons. Verify the rescue hold cannot be interrupted without resetting, the pod blocks a third pickup, and beacon delivery updates the survivor total. Then add the two telegraphed drones and three hull points. These authored values are not observed balance or user-test results.
Read the related shoot-em-up design guide.
Try the SEELE AI game maker workflow.
Frequently asked questions
How does this shooter replace the kill counter?
The mission HUD tracks survivors delivered, passengers in the pod, hull, route position and the next beacon. Enemy defeats do not add score, change the victory condition or appear as the mission progress total. This keeps the mission goal visible even when the player chooses to fire during a dangerous pass.
Can I rescue more than two people at once?
No. The detachable pod has two seats. The craft must reach a safe beacon to transfer its current passengers and free the pod before it can collect another survivor. That capacity makes the timing of a beacon visit and the speed penalty part of the rescue decision.
Check Godot's official Area2D reference.
Do I have to destroy the drones to win?
No. Drones create hazards, but the pilot can dodge their telegraphed shots or briefly disable them. Destroying an enemy adds no progress; the success check uses only survivors delivered and the ship reaching the route end. Survival matters, but eliminating targets never substitutes for delivering the required number of passengers.
Has Signal Harbor been playtested?
No. Signal Harbor's positions, speed values, cargo rules and rescue trace are authored prototype inputs. This package does not claim a playable build, browser test, user test or measured balance result; those checks remain for a later implementation. The route, collision handling and passenger movement still need implementation and real playtesting before balance can be judged.


