Is this the Norm!

[FEARLESS]

Question: I attack a town and win the battle. The enemy respawns another army. I wipeout that army. The enemy respawns another. I win that battle. At last the towns mine!!! is this normal or is it a bug

[Prof]

Those are rebels...you can avoid them by exempting the town from taxes, by converting the population to your state religion or by stationing a bigger garrison. (or all of them)

[FEARLESS]

Thanks Prof!

[Húsasmiður]

Are these attacks on the same turn or after a couple of turns. I had a problem when attacking town, the enemy army attacked me immediatly after i had won the first battle, then again and again until my army lost. this all happended on the same turn. It was kinda stupid and looks like a bug.

[OTZ]

This may be the dreaded siege bug, rather than spawning rebel armies.

[PendragonLoT]

This may be the dreaded siege bug, rather than spawning rebel armies.

Sounds like that to me, too. I have experienced some of those "respawns" myself, too.

[fluffstalker]

This isnt rebel armies, which are a mechanic. This is the siege bug -where you if you wait out a siege, the enemy will sally forth, you wipe them out, only to find a new stack of milita waiting for you. Usually, the AI is so buggy in fort battles that when I besiege I immedieately click attack, get my arty on fire at will, go and do something else, and come back. Sometimes they havent even tried moving out of the forst to silence my guns, and half the fort is in ruins.

[eatme]

It is easy to avoid this bug, in my experience.

By not waiting out for the surrender. but attacking the besieged settlement immediately.

Afterall, compared to MTW2 with its hard castle sieges, in ETW it is not so hard in most cases - to pitch a battle even when a settlement is protected by a fort.

[SirVulf]

Actually... I think he might be talking about in the same turn. I had that same crap. I don't bother waiting for a besieged surrender anymore, I just attack the towns on the first turn. If they attack me while I have them besieged, I can decimate and kill every one of them, and then all of the sudden another stack shows up, and then another, and another, etc... it was quite aggravating.

[Steinig]

I didnot have this army respawn, at least not if i play the battle myself.
I saw it on autobattle, but bevor i read this thread i assumed this where the troops rioting from battle and so keep alive, + the resistance every time with new battalions.

But what i have was the problem that if the enemy comes out try to break your sidge, you win but didnot kill all of em, so they go back in the city.

After that the sidge is lifted and i have do sidge again with a reset in "turns to surrender", this makes me stop trying to sidge cities, cause i never can kill them by starving.

Only reason why i go into sidge are that i need time to reinforce troops of the attacking army.

[General_Meevious]

This happens to me all the time unless I assault before they do (so if I park near enough to the enemy fortress for its contents to reinforce an attacking army, I have to fight two stacks instead of one). I don't think it's a bug as such. I think it's a really poorly thought out game mechanic.

[Captain Adverse]

I am not sure (after reading all the previous responses) if he is referring to my concern. Several times I have besieged a wall-less town to prevent it raising troops while I wait for reinforcements, had the defenders sally out during the defender turn to attack me, won the battle, only to find that when my turn comes round again the siege is broken, the town has raised new forces and I have to fight again with a weaker force.

What ever happened to the loser has to retreat away, and if they cannot they die and you win? What ever happened to a town falling if they sally and lose the battle?

Is this the siege bug someone mentioned? Did CA change the rules or what?