This shows the current position of our units. The stack should survive even against a total Lego assault. Current lego forces are (brackets are losses from last turn):
Legoland forces:
- 2 settler
- 14 worker (-3)
- 3 horsemen (-1)
- 12 Cavalry (-13)
- 91 infantry (+2)
- 62 artillery
- 27 Tanks (+11)
- 6 ironclad (-1 LiB)
- 15 transport
- 9 subs (-2 LiB)
- 9 DD (-1 LiB, +3 B)
- 9 BB
- 1 carrier
- 3 bomber (+1 B)
- 2 settler
- 14 worker (-3)
- 3 horsemen (-1)
- 12 Cavalry (-13)
- 91 infantry (+2)
- 62 artillery
- 27 Tanks (+11)
- 6 ironclad (-1 LiB)
- 15 transport
- 9 subs (-2 LiB)
- 9 DD (-1 LiB, +3 B)
- 9 BB
- 1 carrier
- 3 bomber (+1 B)
Lego will probably have 40 tanks available next turn assuming they use their remaining Cavs for rush builds. They can either use them in a mass attack or... use them for defense which is quite likely also. GS invasion forces are 70 tanks, 55 Marines, 4 Mech Infs and 22 Infantry. Our force (including next-turn's chained tanks) is 60 tanks, 34 Marines, 42 Infs and 27 Artillery.
The plan:
Simple, build a city with the settler, bring in the tanks and hopefully take either Dye Fields or Jackson, we might even be able to take Legoland if its not defended. This turn neither Legoland nor Castlea were defended by a single unit which means that Lego is placing all their defenders in the threatened cities. By landing only 1 settler maybe they won't think we have extra ones off-shore...
After that there's not really a plan, we need to see how things develop and plan on a turn-by-turn basis. All we know is that our main objectives are Legoland and Jackson. Our bombers can and should try and bomb the crap out of everything possible until we turn Lego into an ancient-era civ again.
Btw, the more suggestions, the merrier, anyone want to step up as CoW and CALF?
-MZ
Comment