I think the term "Defend yourself" is a loaded term here as well. There's no attacking or defending here, because it comes back to the root issue here.... just because a player built a bridge out to somewhere doesn't "entitle" them to anything. That sense of entitlement gets reinforced by rules around this, and i think that's bad for the game.
I wonder if that suggests a solution in the
opposite direction is needed.
- the colonisation contact comes online as usual when the initial station is complete
- but your personal "one new colonisation at a time" restriction doesn't count as completed until you've completed the
second asset in a system
So the System Architect for a system by design has
less ability to use that system for chaining than anyone else does. I still wouldn't be able to chain from mine, for example, because I picked a largish project for the second asset and it likely won't be complete for at least a week - though the option is still there to pick one of the tiny Odyssey settlements which can be done in under an hour, of course.
At that point it's mechanically clear that chaining in a particular direction isn't supposed to give you a personal moral right over every system further in that direction. Sure, two people working together - or even a player and their alt - can avoid being slowed at all by this; that's fine. Conversely, one of the consequences of putting some Architect-only timeout in place would of course be that a
group trying to chain out somewhere would end up either having to go a fair bit slower (especially with all these ideas of 24 hour or 1 week timeouts), or have all their intermediate systems have the same Architect, which is less fun.
Daisy chaining is actually a plan from Frontier, and so Frontier should enable it, not devalue it.
Daisy chaining has several uses, though.
- it generally expands the pool of reachable systems (a line sent out perpendicular to the bubble is much more efficient than expanding in a shell for bringing new systems into range)
- if you're aiming for a region (e.g. the projects aiming for Lagoon Nebula, or Polaris) you can't really be "sniped" because so what if someone else gets some of the systems out this way, there are plenty more and the whole point of the project was to allow that region to be colonised
- as above, for group projects (and speed-chaining as an individual, even with just outposts, is something a tiny number of players are capable of as a proportion of the total) architect-only lockouts (especially long-duration ones) are potentially a problem. For group projects especially there's not even a guarantee that the named architect did
any of the hauling themselves, so what "effort" of theirs is necessarily being protected? [1]
First-come first-served is flawed, but so is every other model and at least this one is simple and comprehensible.
[1] If I haul the largest amount of cargo to complete a system claim, should it be me rather than the Architect who gets the exclusivity period on the contact? Can of worms right there either way...