Geoff the Medio wrote:
Gray Area wrote:
Would you consider adding a message to the SitRep to the effect that a star system, in this case a previously occupied star system, is under blockade?
That's a bit tricky to do well... Being blockaded can mean a few things; if there's an enemy armed ship in the system, then nothing can come in or out, so that's fine. But, there could also be an enemy ship between a system and the rest of your empire, which would effectively blockade it, without actually having a local, or perhaps visible, cause. A system could also be blockaded from some of your other systems, but not others, or a locally blocked system could split your empire in half without having any noticeable local effects. As well, if a system is blockaded but doesn't starve itself for an extended period, would you want blockade sitreps every turn? Most sitreps are presently about single events, not ongoing situations, and a lot of the latter could quickly clutter the list.
It does sound like a ‘star system blockade’ message in the SitRep is unpractical and undesirable.
On the other hand, would it be possible to add a ‘one time only’ message to the SitRep something like as follows?
“The population of _________ was lost to famine induced by blockage.”
As the sequence of events was:
1. An enemy ship(s) entered a populated unprotected star system.
2. The enemy ship(s) blockaded the populated unprotected star system.
3. Population(s) with insufficient farming in the unprotected star system were lost to famine.
And, as all of those events are recorded, could they easily and practically be used to trigger such a message?
(Remember, such a message ‘might’ have the benefit of keeping newbies like me from asking you experts the same questions over and over again.
BTW, after playing a few more turns, I was pleased to find the Basic Shipyard and Orbital Drydock, that I had previously built on one of my starved colonies, still intact when I re-colonized the planet.