 |
|  |
 |
|  |
 |
|
Aeson
|
 |
orangesoda
Nov 2001 time: 22:20
|
|
quote: The diversion of BBs towards stand alone DDs isn't going to work, I fear. I'm pretty sure that Lego is already onto our N fleet (they passed a sub in that direction 3 turns ago, which would be ideal to be off the coast of Hurricane right now), and otherwise will be very soon. They will not go for a lone DD, when they have a stack of TR closeby. |
They might not know where our fleet has gone though.
They have a Sub to spot us with. We don't know where the Sub is, but perhaps it was to be part of the pickets to the N. They didn't have anything N of the Ir at 2 that we could see. Even if their Sub was at Hurricane, they might not know if we went N, S, or E.
If they guess S, they won't see us with the BB's either. If they head S and then next turn all they see are two DD's N of their BB's, they might think we've headed N with the main fleet, and those are just damaged sentry killers headed to join up. They could turn all the way around.
If they guess E, they will spot us with the Sub if it's near Hurricane, and won't otherwise. In this case it's all up to where the Sub is. If it was too far S or N of Hurricane (it wasn't due east of Hurricane or we would of hit it), they might not spot our fleet at all. Again, they would only see 2 DD's, both N of the BB stack.
If they guess N, they will know we didn't go N unless their Sub was S of Hurricane. Again it's up to the position of the Sub. If it was S of Hurricane they wouldn't be able to catch up to our fleet anywhere. All they'll know is we didn't go S. If they spot ships N of their BB's, they might be lead that way.
If their Sub was offshore to the E a few tiles (too bad we didn't run into it with one of our DD's) and sees our fleet, they won't have to guess, and we can be sure the BB's will hit our stack.
quote: Oh, one comment to your misdirection forces: I only half agree that it doesn't cost us anything. It won't damage the main fleet, and that 1/4 DD is only good for bombardment, but the 4/4 DD was scheduled as a picket for our chain (1/4 as well, once it healed in Hurricane, but that's only for turn 244). Everything we've got is going to the N fleet, those chain protectors are scarce. |
Yes. I noted the same drawbacks. (I never said it wouldn't cost us anything, just that it wouldn't cost us much).
I think it's worth the shot. It's a gamble of getting by the BB's without a fight, and giving perhaps another turn of using the chain. It costs us 3 DD HP's from the fleet. Even at low odds of working out, it's a worthwhile risk IMO.
We don't have to use the 4/4 if we don't want to either. Use it to protect the chain, and only use the 2 damaged DD for misdirection.
|
|
|  |
 |
|  |
 |
|
DeepO

|
 |
supporting Candle'Bre
Jan 2002 time: 06:20
|
|
economically, I think I can go for 24 M over the next 3 turns, leading our total to a maximum of 64 (of which I think 8 will not arrive Legoland). That's the absolute maximum, not only for our producing cities, but also for our transport capacities before invasion.
However, it means no MI at all, and this I don't like. Even a few MI will work wonders, they are double as strong as I for defending against cav and tanks (not so against arts).
So, could we e.g. take 4 certain MI in turn 242, and fill the rest with all M? This means a maximum of 60 M (8 of which if we get lucky), and 4 MI.
I have to tell you, for completeness, that there is a way to ahve nearly all our chainers to succeed. We currently have 2 empties. We can fill these next turn, and ship them over to the first spot. Next turn, one of those is the regular chainer, and the other returns to Hurricane. In turn 243, the chain is in proper order, however there will eb no empties left: as we fill 2 TR in 241, and 1 TR in 242, all is full.
The advantage is that we can be certain all our chains will succeed. The disadvantage that it only works next turn, at which we will have 12 M, or 8 M and 4 MI, but must fill the rest of the 16 spots with I (or a settler and workers).
So we can still have a choice... in case we would go for a total of 20 extra M, and 4 I, we can be nearly certain they arrive. If we go for MI, we have to wait, and can't be certain of the last TR.
DeepO
|
|
|  |
 |
|
DeepO

|
 |
supporting Candle'Bre
Jan 2002 time: 06:20
|
|
quote: Originally posted by Aeson
I'm still worried about the number of Marines. 48 is a bit low. 40 (which could happen if 242 isn't chainable) |
Wow... correction. We currently have 40 M on the seas. We will get another 8 next turn (241). That's 48 certain M... we're talking about the next 16, so to a possible 64 M.
I don't think we're paranoid for bringing many M, maybe much too many. There are 2 possible disasters for this invasion of ours. First of all our N fleet sunk before it can unload.... and secondly us not being able to break through the defenses. All the rest is not important if we succeed or not, as it won't be so critical... but it would be a shame to base our analysis on wrong numbers 
quote:
If we want to make sure we have at least a "top" MI for defense, we could take 6 surefire Marines and with 2 MI. Then 6 probable Marines with 2 probable MI. Then if we've gotten rid of Legos spy they may choose to concentrate on GoW instead of us. |
So in total this would bring a max of 60 M, 4 MI in our force (and 34 tanks). 6 M + 2 MI are in my mind never going to arrive, the others we can more or less be certain of. So 54 M, 2 MI, 34 T... a decent invasion force!
quote: On D-day I think we need to make sure we have 8 more Marines waiting if the chain has survived. (We can't know if it's survived before the build-queue on 243, so if it's survived, and isn't definitely threatened on 242 go with Marines). The MI to send will be upgraded on 242 anyways right? |
Aeson, we're talking about different things, it's obvious. But I agree with you 
The MI will be upgraded in turn 241, next turn. But they can only move in 242, yes. We can build 4 (I think) MI next turn, which can move if we want to.
DeepO
|
|
|  |
 |
|  |
 |
|
DeepO

|
 |
supporting Candle'Bre
Jan 2002 time: 06:20
|
|
I wish I could 
With chaining 2 TR next turn, we can go for a sure 60 M, and 4 I. Or e.g. 54 M, 6 MI, and 4 I. No instant correcting on D-day, though, as we will trade the certainty for a broken chain (no empty available). In case we get lucky in the 1-1-1 scenario, we can see if we break through and chain another 8 M... or 8 MI (or T even).
Actually, that's not entirely correct either. Okay, a recap, as otherwise we're going to loose count
- Scenario 1-1-1 is simply one TR every turn. As the first 2 turns succeed (turn 241 for sure, turn 242 most likely), this will bring 16 sure spots, and 8 maybe spots.
- Scenario 2-1-0 chains 2 TR in 241, 1 in 242. Problem is we don't have all the forces available we would want in 241.
- Scenario 2-1-(1) is a variation to the last one. We take the certain solution to get at most 60 M to Legoland. Further, we keep the option of correcting us in case we get lucky with Lego (and they keep our chain intact), but it's costly... we need to empty a boat, to make room. In the event of a disaster, and those 60 M aren't going to work, we send over 8 more M (if we can, of course), disband 4 I + 4 T, and replace them with our fresh M.
Mind you... I think that 3rd turn is not going to happy. In which case we would actually be better off with the 2-1-0 scenario anyway.
DeepO
|
|
|  |
 |
|
DeepO

|
 |
supporting Candle'Bre
Jan 2002 time: 06:20
|
|
quote: Originally posted by Theseus
Does that also mean that we might have more capacity for either additional DDs to cover the chain, or earlier Bombers? |
Sigh... give them a hand, and they grab for your arm! Sorry that I have to disappoint you, but our production capacity remains limited to some 900 shields (1000 with ample rushing). That's 9 M, T or B each turn. MI are 'for free' as we can upgrade I or rifle.
But I want to warn again that our defense currently is laughable. We've got 2 I in each city, and some 20 rifles spread around. Of that heap, we're going to take additional defenders away for upgrades. Please let us consider this, even if it means that we can't send a continous stream of reinforcements to the front.
I would even consider drafting in cities which are of no use anyway (e.g. Sufa, which produces just a few bpt, nothing more), just to get our defender count up. If GoW would attack, we would be in very serious trouble right now.
DeepO
|
|
|  |
 |
|  |
 |
|
DeepO

|
 |
supporting Candle'Bre
Jan 2002 time: 06:20
|
|
Not at all 
After a night sleep, I think we should definately go for the 2-1-(1) scenario. I should have thought of it before, though, as I then could have left 3 T at home.
What I have in mind:
241: We have 12 completing build (13, if we rush a DD in Blizzard). Right now, these are scheduled as M. Build 12 M. Upgrade as many I as possible.
Chain 12 M + 3 I + settler to the Northern fleet
N fleet consists of 52 M, 3 I, 36 T, 5 settlers, 1 empty TR.
242: We can't build 8 M without serious rushing, but we could build 5 (I think). If not enough, we need to divert more cash to rushes.
Chain 5 M + 3 MI to N fleet.
N fleet consists of 57 M, 3 I, 3 MI, 36 T, 5 settlers. No empties left.
243: D-day.
We have another 11 or 12 builds that finish this turn. 8 of those can be M, the rest I strongly suggest MI, or at least something defensive (T could also work).
I doubt our second leg in the chain will be in place, but you never know.
We invade Sando, and see how the attack goes. If we just can't break through and need a couple more M, we empty a T (I think we could e.g. put 8 T on land, no need for outright disbanding. But the troops will be useless that turn). We chain from Hurricane the final batch of troops... which could also consist of extra MI.
Possible N fleet can consist of 65 M, 3 I, 3 MI, 36 T, 5 settlers. 8 of those spots will land, but can't move anymore and are exposed.
-----
I like this method... it holds the least risk, and compared to the 1-1-1 scenario it gives more M for certain, and more M in total. It could potentially be costly (losing movement on 8 T), but in case our 57 M can't break through, I think we will welcome a solution where we can ship a few M to us.
DeepO
|
|
|  |
 |
|  |
 |
|  |
 |
|
Aeson
|
 |
orangesoda
Nov 2001 time: 22:20
|
|
quote: 242: We can't build 8 M without serious rushing, but we could build 5 (I think). If not enough, we need to divert more cash to rushes.
Chain 5 M + 3 MI to N fleet.
N fleet consists of 57 M, 3 I, 3 MI, 36 T, 5 settlers. No empties left. |
Our original goal was 56 M. You've found them, good job! I think 56 M, 4 MI, 3 I, 36 T, 5 Settlers. That would give us 2 MI in each city we keep, and hopefully we won't leave too many Tanks exposed. Otherwise we can have a "top" MI in each city and a couple to cover Tank stacks. They won't keep us safe, but Lego will have to choose between attacking MI on our side or I on GoW's.
Would it be possible to include an Explorer instead of a Inf? We have a decent estimate of where the FP city is, but without the ability to confirm our guess we are taking a huge chance. I don't think Lego will keep inland fortressess manned, rather favoring coastal Cities and perhaps coastal Hill fortresses. So we should be able to uncover most of what we want to see with one Explorer.
Our Fighters can Recon too of course. If they get shot down on Air Superiority missions on t-1 though we'd be in the dark again.
quote: We invade Sando, and see how the attack goes. If we just can't break through and need a couple more M, we empty a T (I think we could e.g. put 8 T on land, no need for outright disbanding. But the troops will be useless that turn). We chain from Hurricane the final batch of troops... which could also consist of extra MI. |
Probably would want to drop out 2 Inf (or 1 Inf if we take an Explorer) and 5 Tanks if it comes to that. Gives those lame duck Tanks some cover at least, and keeps 3 more Tanks we can keep active.
Though it's not so much fun trying to change specific units around in a stack of Transports. We'd need to delete an Inf outright, but it would almost surely be "saving" 3 Tanks for our use, which is more valuable. Unless we could land them on the Hill we want to build our harbor city on, Lego would almost have to attack the stack of 8 exposed Tanks with their Cavalry. They won't get any better targets.
-----------
I don't think we need to spot Lego's Subs next turn. Either they will have sight of our fleet(s) already, or they won't sight our fleet(s) at all with them. Even their Subs can't keep up.
I think we should send our N Sub 222. Mid Sub 777 to join up with the fleet if Lego sends their BB's due S and we bombard them, or 77 otherwise. S Sub 888. Two of our Subs need healing badly, and cover until then. The 4/4 Sub can help us cover our chain after D-Day (if such a chain is possible). Other option with that Sub is to send it N to watch Vox.
-----------
Should we plant a spy with Vox? If we find they have no navy we don't have to worry about more Subs to watch them with. Probably worth the cost. Plus we should quickly see how they are going to respond to all this.
|
|
|  |
 |
|
DeepO

|
 |
supporting Candle'Bre
Jan 2002 time: 06:20
|
|
Erhm... Aeson, there is one already on board of our Northern fleet. You're talking about a second one, to be shipped next turn, right? I'm not sure if we discussed this beforehand, but it made sense to me to include one in the first wave...
And Theseus: yes indeed. You have to have the square itself uncovered before investigating. Also, fighters don't see very far, and as our carrier isn't going to be able to keep up with the TRs, it is likely it won't be with us anymore on D-day.
---------
Diversion: what if we build a couple of bombers early, and pretend they are based on our carriers, instead of kept aside to be rebased on Legoland? Would that distract any BBs? I'm not sure how we can fit it in with the M builds, but a couple could work.
DeepO
|
|
|  |
All times are GMT. The time now is 05:20. Apolyton Time is 00:20. |
top of page
|
|
|
Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is ON
vB code is ON
Smilies are ON
[IMG] code is ON
|
|
|
|
|
|