(((I'm searching the forum to find out when Multi-Attack is unlocked. At what level is it available? I like it. Lead to this idea.)))

The suggestions for multi-transfer are good too, along with limited-multi-attack. I suggest the limit not be hard coded but a ''fatigue'' limit. Each additional attack raises losses, even on zero guarded territories (maybe treated as a transfer losses). Troops get tired. That would handle multiple attack and transfer with differing fatigue losses.

https://www.warlight.net/Unlockables

See https://www.warlight.net/wiki/Levels. Multi-attack unlocks at level 37. Alternatively, buy a membership - https://www.warlight.net/membership.

I remember Fizzer saying that Multi-Transfer wouldn't be added because it would be abused. It would be used to create loads of 'delay moves'...

Edited 12/24/2016 17:49:50

ie, the person who spams the most delays gets the most delays :P

Orphaned troops are a problem. Delay abuse is a problem. Solve by not including multi-transfers as part of the combat cycle. First transfer is included, the rest of the chain happen after all combat concludes. That leaves the game play mostly as-is (can still blossom then recombine), but allows orphaned troops to be recovered for later combat.

Multi-transfer can still be abused by sliding troops around the battlefield and turning a frontline(ish) war game into GO. However, a multi-attack/transfer fatigue rate would mitigate that. The FATIGUE factor (set as a game parameter) would cause greater and greater losses per multi-move.

I feel this would make the game unnecessary complicated. Even if you know multiattack well, it would be confusing.

AirLift Card works good enough to rescue orphans.
Still want the fatigue modifier.
Maybe next Christmas.

this thread should be on the general forum, not programming.

I'll move it.

thanks for keeping our forum cleaner dan!