Stuck on one army when accepting a challenge

Nakedcelt · Post by **Nakedcelt** » Wed May 04, 2011 6:32 pm

OS - Windows 7

Version - 1.5.3

The game will only let me choose the same army (Gallic Lowland) from RoR (I also have IF installed) when I accept challenges. Have only really noticed this after installing the patch.

Epicouros · Post by **Epicouros** » Thu May 05, 2011 12:38 am

Yup. It's a general problem (and screwup

). See my posts in the general 1.5.3 and "opponents receiving wrong army" threads:

I already posted this in the 1.5.3 post in the general forum. I love the the game, but I have to say: No new supplements (was planning to buy them all, and still will if this gets sorted out) or DAG games for me until this is fixed. Also I won't appreciate it if I have to delete all my existing DAG armies...

"Maybe related: I accepted a DAG challenge against Medieval Welsh. I accepted, but before actually playing I created a HYW English (in Britain) army to field against the Welsh.

Then, when I chose from my saved armies in multiplayer I could select it (it was in yellow, as usual), but in the text screen to the right appeared my army that's at the top of my SOA saved armies list (medieval Burgundians).
I couldn't get the HYW English to show up, even though I tried and it was highlighted in yellow in the list itself.

I could do nothing else but proceed, and what I feared came true: I am now fighting a battle against the Welsh with my Burgundians instead of my English (both are 600 pt armies I think but I don't know if that's relevant).
Furthermore I'm now afraid all challenges I'll accept will automatically pick the the army listed at the top of my saved armies in each 'book'...

I didn't have his problem before patch 1.5.2/3."

Post by **IainMcNeil** » Thu May 05, 2011 11:53 am

Its been fixed and you should be able to download the latest version now.

One of the problems of continually supporting the game with new free features is that we have these occaisonal glitches. There is no test departement - the team is only 3 people and so unfortunately things do get missed and this particular issue was caused by specific saved armies on some machines which we did nto have and as a result did not catch in testing.