Huge Bug - Devs?

[llamabeast]

Methel, did you look at the turn on the machine that did the hosting?

I would guess the hosting machine has something different (mod, OS or something) to all the machines you're using to view the battle.

The battle views aren't contained in the trn file at all. Your own copy of dominions makes them up as you watch them. Normally the result will be identical to the result the host produced though, because everything about the battle was identical, and the same random numbers are used. If there is anything different about your copies of dominions though, the results can be incredibly different (it's like Sliding Doors, if you've ever seen that - a tiny difference can end up having a huge effect).

[Edi]

Are all the machines patched to the same version of Dom3?

[Jazzepi]

I'm using 3.8 no mods.

Jazzepi

[thejeff]

But the thing is, it's not the same battle. The view is a castle storming, but the report is a normal battle. That can't from the normal battle view replay random number weirdness.

[llamabeast]

Oh. That is really strange.

[Cor]

I know its not helpful, but the turn limit is 75, not 30. You can definatly rule that out.

[Jazzepi]

Cor said:
I know its not helpful, but the turn limit is 75, not 30. You can definatly rule that out.

I appreciate that. I thought it was a lot lower!

Jazzepi

[Edi]

The reason it's a normal battle report is that if the defender wins against the forces stroming the fortress, it is shown as a normal battle report for both sides. If the attacker wins a siege, he gets the "We captured the fortress!" and the defender gets a normal battle report.

Since the outcome was that the defenders won (and we have a wonky replay that visually shows the opposite), it's handled as a case of the defender winning and the battle reports accordingly.