Tweet
Some suggestions and notes for MY 2151 I wrote down while looking at the 2150 endsave:
Rehome the SNC Mercury and all the land units that visit University Base to that base, to free up minerals from support cost back in our homelands.
(Or should we instead aim for the exact opposite? Keeping Arcadia as support-free as possible, so those extra minerals can help reconstruct the conquered bases as soon as possible? Either policy has merits I assume.)
Worker relocation:
Place the GH 2-1-0 worker on the 1-2-2 forest that will be completed next year.
Question regarding the Crypteia moving to Vladivostok. I'm not sure I'm up to date: Will it stay in VV, be escorted with SNC Hermes to the new base, or be escorted with SNC Mercury to probe-defend our conquered Arcadian bases?
Unit movements:
Let the SC4 scout patrol in RG escort the CP going north. To replace the garrison, change production in RG to a hoplite, which will then finish MY 2152. As drone riots are checked for after production, there wouldn't be a riot.
Move the other RG garrison to FB. Let it be replaced by the SC4 hoplite in FB. = preparing for possible rehoming MY 2152
Possible option: If we want a Manifold base to be able to defend well against PK rovers, we could perhaps send the elite garrison in Vladivostok along with the CP to its new base location, and upgrade it to an impact infantry after arrival.
If we want to send two hoplites to Arcadia with the next Mercury ferry service (along with the probe team and Castor Horsemen), we could do the following:
Next year VV will have 4 mins accumulated, and its production will be five (provided the SNC Mercury is rehomed to University Base). So hurrying one mineral (in this case 5 credits I think) would suffice to finish the hoplite.
That accounts for one hoplite.
For the second hoplite we could change production in Sector Craterwest or Santiago Citadel to a hoplite. That should be finished MY 2152, so once again we could move one of the hoplites out of the base without causing a drone riot. Since our bases are placed so conveniently close, we could then do a whole chain of hoplite hopping to move a hoplite to Vladivostok.
For example, if we would decide to change SC3 production to a hoplite, we could move a SC3 hoplite to SC4, move a SC4 hoplite to SC2, move a SC2 hoplite to OA, and move a OA hoplite towards VV, to be picked up by the Mercury. So thanks to building a new hoplite in SC3, we could send a OA hoplite to Arcadia.
Btw, due to capturing University Base it's possible or likely b-drones could appear in Sparta Command and/or Olympus Academy (and Minas Tirith, but that's no problem). So therefore I guess it would be best to wait with any hoplite shuffling until after we've captured Uni Base, so we know whether or not we need to send some extra hoplites to a base to quell extra drones.
Even if no b-drones would appear after capturing Uni Base, we are certain they will appear after capturing our twelfth base (12 = twice our 6-base bureaucracy limit, meaning ALL pops are drones). So in any case I guess it would be best to build some extra hoplites asap.
Rehome the SNC Mercury and all the land units that visit University Base to that base, to free up minerals from support cost back in our homelands.
(Or should we instead aim for the exact opposite? Keeping Arcadia as support-free as possible, so those extra minerals can help reconstruct the conquered bases as soon as possible? Either policy has merits I assume.)
Worker relocation:
Place the GH 2-1-0 worker on the 1-2-2 forest that will be completed next year.
Question regarding the Crypteia moving to Vladivostok. I'm not sure I'm up to date: Will it stay in VV, be escorted with SNC Hermes to the new base, or be escorted with SNC Mercury to probe-defend our conquered Arcadian bases?
Unit movements:
Let the SC4 scout patrol in RG escort the CP going north. To replace the garrison, change production in RG to a hoplite, which will then finish MY 2152. As drone riots are checked for after production, there wouldn't be a riot.
Move the other RG garrison to FB. Let it be replaced by the SC4 hoplite in FB. = preparing for possible rehoming MY 2152
Possible option: If we want a Manifold base to be able to defend well against PK rovers, we could perhaps send the elite garrison in Vladivostok along with the CP to its new base location, and upgrade it to an impact infantry after arrival.
If we want to send two hoplites to Arcadia with the next Mercury ferry service (along with the probe team and Castor Horsemen), we could do the following:
Next year VV will have 4 mins accumulated, and its production will be five (provided the SNC Mercury is rehomed to University Base). So hurrying one mineral (in this case 5 credits I think) would suffice to finish the hoplite.
That accounts for one hoplite.
For the second hoplite we could change production in Sector Craterwest or Santiago Citadel to a hoplite. That should be finished MY 2152, so once again we could move one of the hoplites out of the base without causing a drone riot. Since our bases are placed so conveniently close, we could then do a whole chain of hoplite hopping to move a hoplite to Vladivostok.
For example, if we would decide to change SC3 production to a hoplite, we could move a SC3 hoplite to SC4, move a SC4 hoplite to SC2, move a SC2 hoplite to OA, and move a OA hoplite towards VV, to be picked up by the Mercury. So thanks to building a new hoplite in SC3, we could send a OA hoplite to Arcadia.
Btw, due to capturing University Base it's possible or likely b-drones could appear in Sparta Command and/or Olympus Academy (and Minas Tirith, but that's no problem). So therefore I guess it would be best to wait with any hoplite shuffling until after we've captured Uni Base, so we know whether or not we need to send some extra hoplites to a base to quell extra drones.
Even if no b-drones would appear after capturing Uni Base, we are certain they will appear after capturing our twelfth base (12 = twice our 6-base bureaucracy limit, meaning ALL pops are drones). So in any case I guess it would be best to build some extra hoplites asap.
Comment