#97e: outpost garrison composition menu #103

Closed
opened 2026-08-23 11:18:43 +00:00 by metaheavens · 1 comment
Owner

Subticket of #97, depends on #97d.

"Outposts can be occupied by ships. Only ships that attack can be assigned. A
dedicated menu on each outpost should let you compose how you want the outpost
to be filled. There's a default of 2 vessel per outpost, upgrades can increase
this number."

  • Per-outpost desired composition, stored on the building record.
  • The menu offers only vessels that can attack - a transporter or a bare hull
    cannot hold a position.
  • 2 slots by default; a researched upgrade raises the ceiling for every
    outpost, including ones already built (the same shape as hub_bonus).
Subticket of #97, depends on #97d. "Outposts can be occupied by ships. Only ships that attack can be assigned. A dedicated menu on each outpost should let you compose how you want the outpost to be filled. There's a default of 2 vessel per outpost, upgrades can increase this number." - Per-outpost desired composition, stored on the building record. - The menu offers only vessels that can attack - a transporter or a bare hull cannot hold a position. - 2 slots by default; a researched upgrade raises the ceiling for every outpost, including ones already built (the same shape as `hub_bonus`).
Author
Owner

Done in 3c63227.

Two separate things live on the outpost's record, and conflating them was the
first thing to get wrong: the ORDER, what you asked for, and the CREW, who is
actually there. This menu edits the order only; #104 fills the crew. Keeping the
order as a wish is what lets an outpost ask for a hull nobody has built yet and
wait for it - and it is why the panel reads "here / ordered" rather than one
number.

"Only ships that attack can be assigned" is expressed as capabilities rather
than a list of types, so a new armed vessel is eligible the day it is added and
an unarmed one never is by accident.

One thing narrowed during #105, worth knowing: the list is the interceptor
only, not the laser vessel. Firing the laser lives in LaserController - a
fleet ability driven by the laser button - rather than in
VesselLaserComponent, which only tracks cooldown and ammunition. A garrisoned
laser vessel would hold its position and never shoot, and offering a vessel that
cannot fight seemed worse than a short list. Giving the laser an autonomous
firing path would make it eligible; say the word and I will open a ticket for
it.

Two berths by default, and Garrison Bays raises it at outposts ALREADY standing

  • the same shape as freight_yards for hubs, because a bonus that only reached
    new buildings would mean demolishing and rebuilding to collect it.
Done in 3c63227. Two separate things live on the outpost's record, and conflating them was the first thing to get wrong: the ORDER, what you asked for, and the CREW, who is actually there. This menu edits the order only; #104 fills the crew. Keeping the order as a wish is what lets an outpost ask for a hull nobody has built yet and wait for it - and it is why the panel reads "here / ordered" rather than one number. "Only ships that attack can be assigned" is expressed as capabilities rather than a list of types, so a new armed vessel is eligible the day it is added and an unarmed one never is by accident. **One thing narrowed during #105**, worth knowing: the list is the interceptor only, not the laser vessel. Firing the laser lives in `LaserController` - a fleet ability driven by the laser button - rather than in `VesselLaserComponent`, which only tracks cooldown and ammunition. A garrisoned laser vessel would hold its position and never shoot, and offering a vessel that cannot fight seemed worse than a short list. Giving the laser an autonomous firing path would make it eligible; say the word and I will open a ticket for it. Two berths by default, and Garrison Bays raises it at outposts ALREADY standing - the same shape as freight_yards for hubs, because a bonus that only reached new buildings would mean demolishing and rebuilding to collect it.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
metaheavens/spaceship#103
No description provided.