as a pretty prevalent fdev critic lately, id say that with trailblazers fdev showed that there is still at least some will going around. you dont think so?
In the general sense, sure, absolutely. There is a will to keep developing the game.
On the other side, there's clearly a maximum amount of side-effects they're willing to tolerate for any change, and a maximum amount of effort before they say "this doesn't come up often enough to worry about, let's focus on the next new feature instead". So their will is finite.
I think it's reasonable to state that based on what Frontier have said that they see Colonisation as a purely collaborative feature
- you can't permit-lock your systems or stations or otherwise restrict them to your squadron's use only
- you can't attack or reverse another player's colonisation effort in any way
- you can't prevent someone colonising with "your" PMF
- etc.
So adding features which give one group or another an advantage in attempting to use it competitively - but which might interfere with a purely collaborative use - don't seem to be ones they're thinking there's a will for right now.
Of course they could change their mind on that. But it's not just an abstract matter of general-purpose will to do so.
so what are the massive side effects of the suggestion i made?
Since I don't think it works in the first place as a way of preventing "race to the finish" snipes at long range, I don't think the side effects aren't the main problem.
But the first side-effect if it did work is the obvious one: it stops people branching off long chains of colonies, so the chain doesn't just achieve its "intended" goal of reserving its final destination in 100 LY time, it also reserves every other system that group doesn't consider important for quite some distance around. That's a highly disproportionate way of "protecting" a single target system.
The two longest chains of colonies at the moment, as far as I can tell, are:
- Canonn's towards Polaris
- Mikunn's towards Lagoon Nebula
Both pretty cool group projects.
Neither of these chains are snipable anyway in terms of their final destination because they're heading for regions. But I don't get the impression either group has any objection at all to someone going "hey, that's a cool system and it's only two hops sideways from that chain - I'll go for it!": indeed, their projects may be doing well because they
haven't been all "and don't try to follow us" about it.
Giving a way to allow people making a series of steps towards a
single final goal system a way to somehow reserve that system? Sure - I can't see a good way to do it, but it's not an unreasonable outcome if it can be done. Giving a way to allow people making a chain in that direction to have exclusive use of that chain and
all the systems it brings into range for a significant time, just so that they can protect a single one? Incredibly disproportionate.
Another side effect:
- you're in a squadron, which is aligned to faction A (or maybe unaligned - it's not required) or maybe you're not even in a squadron at all
- you do some colonising to make a chain, and it happens that the suitable edge of bubble system belongs to faction B
- you don't actually care who owns the systems on the chain (you might even not care that much about the endpoint either...), so you've not been BGS-flipping them to faction A as you go along, so B still controls all of them
- you suddenly lock yourself out of being able to extend the chain
- cue bug reports, support tickets, forum threads, etc.
You could avoid that specific case with a "doesn't apply to the architect" rule, but now what about the case where four people from four different squadrons are working on a chain, and want to share out the architect roles (they don't want to leave their current squadrons and make a new single-purpose squadron together for this, that's at best unnecessary paperwork and might stop them taking part in other squadron activities they want to do in-between hauling runs). At some point outwards, the chain controller doesn't match (any of) their squadrons, and all future expansions have to be done by the same architect.
Not everyone is colonising in a single squadron with a single purpose, so once you start making rules which benefit that specific use-case, they have the potential to inconvenience everyone else, especially those not involved in a snipe/race scenario.
once you align your squad with a faction, you stay with that faction permanently. no big deal. all of us who have our squadron faction are aligned with that faction in long term and dont need such service. you want to realign yourself, you be a good boi and ask very nicely and politely the amazing people at fdev support and maybe you will get your request approved, just like with commander renaming. you are trying to realign yourself too often, you get a fat no as a response to your request. thats a 90 seconds tops job for the support operator to do.
That is how it used to work before Ascendancy. Frontier changed it because the previous method was just unnecessary for a squadron which might have reasons to want to change allegiance (more so in terms of Powerplay switches, but others too). So ... is there the will to add inconvenience to everyone not involved in a race-to-the-finish by changing it back?
And ... it still doesn't help prevent snipes if you add that restriction, because you can:
- leave your current squadron (easy if you're not the leader)
- create a new squadron for 10 million credits (pocket change)
- align that squadron instead
- do the colonisation contact to get the branch claim
- close your 1-person squadron and rejoin your real one
It
also doesn't help, of course, if you're a squadron that is or has been actively recruiting new members, doesn't have an ultra-paranoid background check policy, and therefore one of
your members is someone's alt who adds in the second claim in the appropriate direction, then leaves the squadron so that by the time it completes, it's in the name of a different squadron who gets their own "faction 3" inserted.
(Or, at that point, possibly just snipes the final system because they're in the squadron so there's no restriction on them rushing the new contact)
Might not be a risk for your group personally, but it's hardly a general snipe prevention method for this sort of scenario.