MP missing WML child crash.

Having trouble with the game? Report issues and get help here. Read this first!

Moderator: Forum Moderators

Forum rules
Before reporting issues in this section, you must read the following topic:
Post Reply
Velensk
Multiplayer Contributor
Posts: 4005
Joined: January 24th, 2007, 12:56 am

MP missing WML child crash.

Post by Velensk »

While playing MP today I was interrupted in the middle of my game by an Error that kicked me out of the game. It said "Missing WML child error please report." This is what I am doing.

I was playing on the 1.7.15 branch. My system is Mac OSX.
"There are two kinds of old men in the world. The kind who didn't go to war and who say that they should have lived fast died young and left a handsome corpse and the old men who did go to war and who say that there is no such thing as a handsome corpse."
csarmi
Posts: 288
Joined: August 13th, 2007, 1:57 pm

Re: MP missing WML child crash.

Post by csarmi »

I'Ve got the same on Windows XP twice, in 1.8 version. It happens when you try to attack a unit so it's most likely the server being unable to do the random...
Shurtugal
Posts: 1
Joined: April 6th, 2010, 4:07 pm

Re: MP missing WML child crash.

Post by Shurtugal »

Same on Vista, it happend to me when the AI's attacked
Pok
Posts: 19
Joined: December 13th, 2009, 4:19 pm

Re: MP missing WML child crash.

Post by Pok »

What is this error? I keep getting it all the time. Im playing in 20-30 rounds and suddenly this error quits the whole game! Im about to throw my computer to the wall #@(&/)€(!
sry.............
User avatar
Crab
Inactive Developer
Posts: 200
Joined: March 18th, 2009, 9:42 pm

Re: MP missing WML child crash.

Post by Crab »

Big thanks for reporting!
I've just fixed that particular "Mandatory WML child missing..." bug. The fix is in branches/1.8 in [rev]42123[/rev] and in trunk in [rev]42125[/rev],
and the fix will be included in 1.8.1 and 1.9.0
The usual (not only) cause was 'host sending/receiving a chat message during AI attack'

csarmi, you were correct about the fact that the bug was related to the RNG, so, thanks for this info - it helped find the bug faster.
Post Reply