Just wasted 8 hours... GGGGRRRR

[Botis]

Playing Parthia. Allied with Phocas who's at war with Armenia. I'm not at war with Armenia. I've just moved a stack next to Armenias last remaining city without declaring war. Turns out that the Phocans have been beseiging it. Armenians sally forth.

I am forced to take part in the battle alongside the Armenians!! Eh???

In the battle I opt to simply withdraw my forces.

The battle ends up going badly for the Phocans who despite outnumbering the Armenians, killing their general and 75% of the Armenian army sustaining b'all losses decide to route en masse. I thought that was a good thing, I can attack the city myself with the defenders seriously weakened.

But no. RTW has the last laugh. It has decided that my army along with its two leading generals for some reason have died! They didn't cross swords with anyone and retreated from the field with no losses

In additon to this I've found a serious flaw playing using only the Autosave to restore from no restore pre RTW's decision to screw me over. I've been robbed. FFS this must be fixed as soon as possible.

[Spartiate]

Yep...................i've encountered this.I was laying siege to Rome with a Carthagenian army when my sole siege-tower and ram were ignited by flaming missiles.I decided to with-draw my forces to bring up onagers on the next turn.Having only sustained about 20 casualties in the siege i was somewhat bemused to find that have my army was wiped out in my peaceful,placid andbloodless withdrawal.WTF???
Not impressed.

[motorhead]

Had similar events happen to me and was quite ticked off. However, I've read a number of posts about it and it seems if you have limited lines of retreat you will take horrendous losses.

As for

I'm not at war with Armenia. I've just moved a stack next to Armenias last remaining city without declaring war.

. Well, I think it's pretty realistic that the Armenians basically decided your army wasn't taking a scenic tour of their lands. Chalk it up as a lesson learned.

[GFX707]

Yeah, this needs to be fixed ASAP....

[Lonewarrior]

Arrrggg same thing happened to me in one occasion it really sucked. needs to be fixed in a patch.

[Colovion]

happened to me as well, not fun

[Nelson]

When these armies disappear, how far are they from friendly territory? I ordered a withdrawal of Scipii forces my troops marched off the battlefield and when the strategy map came up they moved into a nearby camp I had constructed for expressly this purpose. All of this was in enemy held Gaul. I'm not saying there is no bug but I am wondering if we understand what's going on. FWIW, the retreating army had a captain not a general.

Building a camp before battle might provide relief.

[Turbo]

Playing Parthia. Allied with Phocas who's at war with Armenia. I'm not at war with Armenia. I've just moved a stack next to Armenias last remaining city without declaring war. Turns out that the Phocans have been beseiging it. Armenians sally forth.

I am forced to take part in the battle alongside the Armenians!! Eh???

In the battle I opt to simply withdraw my forces.

The battle ends up going badly for the Phocans who despite outnumbering the Armenians, killing their general and 75% of the Armenian army sustaining b'all losses decide to route en masse. I thought that was a good thing, I can attack the city myself with the defenders seriously weakened.

But no. RTW has the last laugh. It has decided that my army along with its two leading generals for some reason have died! They didn't cross swords with anyone and retreated from the field with no losses

In additon to this I've found a serious flaw playing using only the Autosave to restore from no restore pre RTW's decision to screw me over. I've been robbed. FFS this must be fixed as soon as possible.

This bug has been extensively reported on almost every board I frequent. Simply put, you can not withdraw from a battle voluntarily as it is far worse than having your troops rout. I have experience severe losses and in one case the entire army disappeared!

[SeveredSoul]

Can't you just use the "Withdraw for Battle" button??

I seem to rember that I use it to leave a battle and I had no ill effects.



-Soul

[Noong]

You do own a neighbouring province to withdraw to?
If not then its not a bug when your armies die from a withdrawal. Its just the rules, same as it was in M:TW.


Most of the posts I see about this "bug" are all because they had no neighbouring province. Usually assaulting Rome straight off the boat (I think there was one in this thread too) so ofcourse a withdrawing army is going to be dead. Got to have that neighbouring province.

[Botis]

It was a province bordering one of mine. It may have been because the non-ally was routed from the field is somehow added a stat to my withdrawal losses calculation or something. I wonder if my "ally" had won the battle whether the outcome would have been different (assuming I still withdrew)?

[metatron]

It's stupid. You're not lifting the seige, you're just retreating from assaulting it. It makes no sense that your army should be destroyed. Who's going to destroy it?

I've had the same happen to me, and yes, it's damn annoying.

[oblivious maximus]

A year or 2 addition penalty to the seige will suffice.Yes, who is going to destroy your army? Makes no sense.

[Stuie]

If they sally and you withdraw, you are most definitely abandoning the siege and therefore the siege should be lifted and your army knocked back to a neighboring province or dissolve if no neighboring province is available. Just like MTW.

As for the opening post, did you not have the withdraw from combat button available on the initial screen indicating a battle was about to take place? If you commit to combat, and then decide to withdraw, I guess I don't feel too bad about whatever loses are incurred - after all, your army was expecting a fight, not flight.

[metatron]

I've watched my men retreat. They took no casualties, and were not chased. This is from my own failed assault, not the beseiged sallying forth.

I don't care if it was designed into the game, it's idiotic.

[Spartiate]

I would find this more acceptable if i was out of movement points, but i wasn't.My army was also under no particular threat.It was just that i didn't want to lose my valuable elite units attacking Epic Stone Walls without proper preparation.Then i'm expected to believe that the weakling Garrison sallied and routed my army inflicting considerable casualties along the way.
I WATCHED my army withdraw unmolested.Doesn't make sense.

[Botis]

If they sally and you withdraw, you are most definitely abandoning the siege and therefore the siege should be lifted and your army knocked back to a neighboring province or dissolve if no neighboring province is available. Just like MTW.

As for the opening post, did you not have the withdraw from combat button available on the initial screen indicating a battle was about to take place? If you commit to combat, and then decide to withdraw, I guess I don't feel too bad about whatever loses are incurred - after all, your army was expecting a fight, not flight.

As I recall the withdraw button was greyed out... it was not an option. But we're talking a few days ago now so I could be dreaming it up. But I withdrew from the battle because I never wanted to participate in the first place and was not even at war with the defenders!

But really, my army was not fundamentally in any different position than it was immediately prior to the battle in which is didn't participate. So somehow walking back a few hundred metres results in 100% attrition?

I mean how exactly did these guys die: were they a Judean People's Front crack suicide squad ala Life of Brian? Had the beef supply gone mysteriously deathly rancid in the afternoon sun? I was not at war with the Armenians both before and after the battle so I don't buy that they chased me down and slaughtered my troops.

Aside from what the appropriate losses should be, my biggest problem was being included in the battle when I was not at war.

Anyway, the real lesson is to use CTRL-S very frequently so it's no longer a big issue for me.