-
1 Attachment(s)
Horseback Wierdness
There currently seems to be something up with the Adventure Horseback : Confused:
In the last block, last camp (20 & 19), SidV calls for a 1 recruit block and then the attacking general sent.
Link to SidV's tactical map: http://img594.imageshack.us/img594/8...tacticmap1.jpg
Okay I followed his instructions, timed the block perfectly, and what happened?....
Blocked guy died, went back to camp, but it seemed successful so far. Then leader camp dies, and i sit back and congratulate myself on another successful adventure.
..wait what? leader camp and blocked camp pop right back up, and my attacking general is intercepted by the (already dead!) blocked camp!
Okay, i'll take it. Maybe it was server lag, maybe it was my timing (which, I am 98% certain it was fine). I move on, sacrifice a few troops to kill that (already dead!) blocked camp, and keep my mouth shut.
A week or two later, i go and do Horseback again. Yet this time, for the last camp, i decide to sent 61 soldiers against 30 riding amazonian and 40 riding bowmen. This advanced block should 100% work. It lasts min 4 rounds, max 6 rounds, and yes i sent a normal general.
Troops are sent..timed perfectly, and wait what? Both camps are fighting, and suddenly leader camp (19) stops fighting, my attacking veteran becomes intercepted by the BLOCKED and FIGHTING camp #20? wtf?
I retreat my vet, but not the fighting blocked camp, since i cannot do that. Suddenly the blocked camp stops fighting? What happened? i have no freakin clue. the dust cloud disappeared, blocking general was nowhere in sight but in garrison it said "attacking"
...and then i lose the blocking fight 20 seconds later. 61 soldiers gone for no apparent reason.
In summary, Horseback is messed up, atleast for me. Normal blocking didnt work (1 recruit) Advanced blocking didnt work (61 soldiers). Yes i know it was only 61 soldiers. Yes i know, blocking is not without its risks. BUT, this is not the way i should have lost my troops due to a block fail. It was not server lag (what lag causes an advanced block to fail?), and it was def not a timing problem ( i followed SidVs blue square thingy). Am i making a big deal out of nothing? Maybe. But i am giving people a heads up, and then perhaps much confusion and dead troops can be averted.
-
Nobody else replied here so I guess I will. My advice, move on to a different Adventure :) Don't keep wasting troops if there is no fix to your problem. Additional advice, try contacting support and see what they can do for you.
-
I posted BB's response to my issue with block failures. I can't recall the thread offhand, but essentially they said they don't recommend blocking because of lag/latency issues.
I didn't feel that my issue was lag/latency either, but they were not warm & fuzzy about the issue. My problem's were with Traitors, and I've sworn off that adventure until I see 30 posts in here screaming about how awesome that adv is now. So I'm with Call-Me-KIng, find a new adv.
-
It's such a shame, because Horseback was really good xp :( oh well. Bigger fish to fry nowadays.
-
I did Horseback a week ago and made it through, but I throught it cost me more troops than it should have for the level it was graded.
Just my 2 cents.
-
Yup, I can concur. The defeated leader camp comes back to life and the general is intercepted by the other already defeated camp.
Lay off Horseback until it's fixed. If they won't fix or acknowledge the problem, I'm outta' here!
-
I just finished Horseback & didn't experience any weirdness. I don't follow SidV's approach, so I clear his camp #17, the leader for that sector, and block camp 20 from a spot right near where his garrison's positioned to attack camp 19. It's still a 1R block, and it worked without a hitch, as did the block on camp 14.
-
I finished Horseback yesterday using Voidheart's method, and it worked flawlessly. Maybe try a different method?
-
Regardless of the method, no general should be attacked by a camp that has already been defeated. There's a bug in the program (go figure!).