General attack order changed?

[Eriond]

Has something changed recently in the way attacks are processed on adventures?

I was running a VLT this morning and sent a multiple-general attack (3 gens at the same leader camp - first leader on VLT). The 3rd gen (which was clearly sent after the 2nd gen, with a decent gap between them) decided to attack 2nd, and the gen that was sent second never attacked, although it sat and waited in the camp.

This behavior seems to be new, have never had a problem with sending multiple general attacks before.

Anecdotally, have heard of others (in chat) having this issue in recent days with multiple-gen attacks. Have not had this problem before, so if something has changed, it's pretty recent.

[convgt]

Have had this happen several times on PVP. Every time I used a block with 3 attack waves the middle gen gets skipped, final (kill wave) hits which means the units to kill leader dies then the middle waves hits. After 3 times in a row this has happened I have started killing the camp instead of blocking that way I can send 1 wave at a time letting each wave finish first. Sucks though to not be able to use the block since on PVP they clearing support blocking or else why would they create hvy ( blocking units).

[Gwalben]

I think this might be on the newish side but has been going on for a while. I regularly have this happen to me on Ali Baba. I send a bunch of suicides in before a Major, and sometimes they kill themselves and sometimes they come back alive. If I have a choice in the matter, I make sure to allow enough time for the generals to finish before sending anyone behind them.

[Perwyn]

I tap my foot to the drum sound to time 3 wave attacks and launch them as follows: flam-flam, flam-flam, paradiddle-paradiddle-flam-flam, 2, 3, 4, 5, 6 - click next attack - repeat sequence.

So far I haven't had anything switch on me doing it this way.

Also, sound doesn't seem to lag so it's always the same timing, where waiting for a general to travel to X point can get messed up due to lag in the graphics.

[Ceruhe]

I don't think the issue was ever gone...? When FTs were introduced way back, that issue was mentioned several times already that Gens were skipping the queue. I've had it happen like twice or so to me long time ago, but when I modified my guides I just spaced my Garrisons or rearranged the troop composition when that wasn't possible....and so far not one worry ever since.
The only issue that comes to mind is 1R blocking a camp (or 2 rounds even) and needing to fit 3 Gens tightly packed through that window, at that stage you run a high risk of queue skipping.
If it's just your average vanilla round block, you can usually just space the garrisons next to each other.....that way you will have 1st enter and initiate your fight, by that time 2nd will roll in and be on standby, 1st dies, 2nd fights and then 3rd will arrive at the camp and so on, there simply is no need to have them all roll in at the same time in the first place due to the 10-20s fighting that the sac Gens do...and since the camp is engaged as it needs to be, you don't lose any time either.

[alice007]

I don't think the issue was ever gone...?

Right... One may be able to find another old, very old post on this... but I have most certainly heard of this before...

[Eriond]

This was just a run-of-the-mill 3 gen attack, first two are sacrifices, third one finishes off the camp. Nothing special, nothing I haven't done exactly the same 100's of times before on the same camp. Was definitely a gap between each of the gens, at least two or three "ticks" on the screen (sorry, don't play with sound turned on).

"3rd" gen killed the camp, but I lost some troops I wasn't expecting to since the 2nd sacrifice never happened. NBD, just wondering if something had changed, since I've not had that happen before.

I can leave bigger gaps in the future, just haven't had to in the past. I guess I needed more reasons to sit idle and wait, anyway.

[focusdonhim]

seen it recently alos. sac was before hammer but arriveved within seconds. sac was disregarded and had a few losses. i think it is a new phenomena of an old issue.

[Perwyn]

...I guess I needed more reasons to sit idle and wait, anyway.

lmao!!

[ghannima]

It usually happens on FTs. Time your generals, send the last one with a 10-15 sec delay. 10 sec are enough, usually- enough time for the first gen to lose the fight before the third arrive at the camp.
The block will hold, theoretically, since you are only delaying the last general who will arrive there while the second general is fighting.