bob the 6th wrote:Just curious why are you sending Rudy with the zerg rush group? He is an archer warlord, so I would be suspect of a plan were he has no other ranged attack units...
As oposed to the other group with 12 archers and no archer leadership. Admittedly the +2 isn't much, but I would think it would be good to at least use it.
Because as an archer warlord I wanted to powerlevel him so that he could evolve into an archer trainer ASAP. That was exceedingly practical when the Logan's Run group had only a few units which could gain XP but became much less relevant when I threw XP-soaking backup units in there. I hadn't really re-evaluated his position in the proposed order of battle.
Werebiscuit wrote:Couple of points to note.
1./ We only have 3 brickbat swarms available as Creperum has requested one, I believe.
2./ Why are we taking wandreus ( our regent) out of Dis ? shouldn't we be garrisoning him there ? ( to provide leadership to garrison units and 10% production boost that's 1920 schmuckers in the time it takes to get to Logans Run and back - EVEN MORE IF WE DO NOT HAVE A MANAGER TO REPLACE HIM we lose an additional 4800 schmuckers ...thats 6720 in total !)
Didn't know that on the Brickabats. Hmm. Are you sure?
Wandereus has to come with us because we need him to level and get the Comptroller and Logistician abilities. That means gaining XP. We have a garrisonned warlord in Dis City who can handle basic management in his absence, even if losing the Regent bonus will hurt a bit.
Nnelg wrote:We must not let them take control of the strategic initiative! Because once they do, this war is lost. They will be able to overwhelm us with superior numbers, eventually battering us into submission.
On this we agree.
Nnelg wrote:The raid on Rainbow Springs is not just a probe, but the start of a siege. A real siege, not what we've been erroneously calling a "siege" (which is really a storm). The elves will naturally send the bulk of their reinforcements to defend it, but we shall turn that city into a meat grinder.
On this we do not. In my opinion, attempting a real-world type siege in Erfworld is just asking to get mauled. Cities don't need supplies, and they constantly generate new units so you can't whittle them down. While we're busy constantly reinforcing our siege group remotely, the elves will be able to reinforce it even faster from more cities than we have (Rainbow Springs is, as we have observed previously, a natural rallying point for the enemy) AND reinforce their defending troops directly by popping reinforcements. Croakamancy will help make up the difference, but it won't be enough. By the time your proposed relief force from Logan's Run arrives there will in all likelihood be nothing left of our siege force to relieve and being able to simply overwhelm the defenders will be nothing more than a dream.
Erfworld isn't a land of cautious skirmishes- because the defending side can never retreat, if at any point
you are in a position of having units within striking distance of enemy forces substantially stronger than they are, those units can and will suffer 100% casualties. By turn 23-24, will the Breatheairians have been able to pop or import enough forces to crush our siege group in this scenario? I think yes. That's another 80 UP of popped units from the city itself alone.
I can see where you're coming from with this, because having an assault group double as a defense group is a great advantage- it minimizes the risk inherent in launching two attacks. But I think your endgame for this is wildly optimistic, and it will end with having our field force croaked.
Nnelg wrote:As for the Escort mission, I think sending an escort would actually be a bad thing. Remember, the elves currently have a truce with the Ixians. But if they see Tenebrisians with an Ixian envoy, they'll immediately attack. So the Ixians would actually be in more danger if we send them an armed escort.
Besides, it would be better to lose face with the Ixians than to lose Yuri. As long as we retain the latter, we can deal with the former. But if we send Yuri in an escort, but the mission fails and he is croaked... Then we can pretty much kiss that alliance opportunity goodbye (for a while, at least).
If the elves attack the Ixians, they break their truce and pay the penalty, which I believe is fairly substantial. That shouldn't be an issue. The rest of your concerns are valid, but I can't help but think- do we really expect the Breatheairians to have a force substantial enough to crush our escort group wandering around well outside the usual routes of travel? Why would they be out there? If they've got something like Lookamancy tracking the envoy group then any escort is likely pointless in any case; they'll croak them or not entirely at their option.
I'm still inclined to say "the Queen asked for an escort, we give her one", but... we do have good reasons to stage it down, and I suppose it would only take one Thinkagram to make some excuses and drop it entirely aside from leaving the imps already assigned as scouts/guides. We could feasibly eliminate this assigned from the list and use those units more productively.
Nnelg wrote:We risk a lot. We risk the elves charging directly from Rainbow Springs to Dis City, we risk Armolad rallying the defence of Logan's Run, and wiping out the assault force there, we risk Yuri to an ambush. And what do we gain from it? Not much. We'd gain Scarlet Hills, but is that worth losing Dis City?
This is a risk, yes. The more cautious play- which I think is less rewarding, but which also minimizes the possibility of the devastating error of either a successful attack by Armolad (that being the weakness in my plan) or of having our siege group crushed (that being the weakness in yours) would be to just send an extremely large attack group at Logan's Run and a substantial garrison at Dis City, perhaps having the Dis City group bluff by making threatening moves toward Rainbow Springs- partial benefits of actually attempting the siege with only a fraction of the risk.
I'd be willing to use a less high risk/reward plan strategically, but the fact that we need high rewards in order to win this war is pushing me to be bold.
Nnelg wrote:Also, the forces he presents aren't balanced. It appears as if he's just throwing units at each task, with little concern for what they'll do or how they'll stack. If we do go with his plan, we'd have to rebalance everything first.
I am not "just throwing units at each task, with little concern for what they'll do". While I did specifically request proposed tweaks to my unit order precisely because it could probably use some optimization, the idea that I'm what, randomly copy/pasting lines from the overall troop listing and then calling it fine- which is the picture that your comments present- is ridiculous, all the more so because I have brief strategic outlines and concerns on strengths and weaknesses with each force.
Since you seem to hold to the paradigm that stacking into squads is the essence of planning warfare in this game, I will clarify that in my perception carefully arranging units by stack is largely a waste of time. Based upon our past experiences, positioning, casualties, and immediate objectives during battle will necessitate frequent restacking in order to get our bonuses to where they need to be. Stacking considerations are primarily relevant in planning to ensure that units with restricted-bonus type abilities (dance fighting, paragon, etc.) have appropriate units in place to make full use of them. Aside from that, concerns like "do our most valuable units have mounts/bodyguards", "do we have a way to eliminate enemy high-defense targets", "do we have a way to deal with enemy archery", and so forth are of far greater importance than arranging preplanned stacks neatly.
Nnelg wrote:Since Exate's already posted a unit distribution, I'll go ahead and make one up too:
I would very much appreciate it if your proposed order of battle included full unit stats, and since you're shuffling everything around into stacking plans instead of leaving them grouped by unit type and build, a summary of what you're sending to each location in those terms wouldn't hurt either.