wrong battle report

[chrispedersen]

I'm just surprised.

Why not write the actual events to each players turn?
Aka...
unit 1 moves to square 2. Does 12 pts damage to unit 934.
unit 2 casts Blinding light.
unit 3 casts foul vapors...

Then let the replay just step through what actually happened?

[cthulhu]

Possibly to minimize bandwidth or disk space needed?
But it certainly be a good idea to do so optionally, at least for debugging purposes.

Anyway, even with the entire battle redone, every roll redone, even enemy tactics chosen differently, I'd expect the outcome listed in the battle report to be fairly unlikely.

[Hadrian_II]

Originally Posted by chrispedersen

I'm just surprised.

Why not write the actual events to each players turn?
Aka...
unit 1 moves to square 2. Does 12 pts damage to unit 934.
unit 2 casts Blinding light.
unit 3 casts foul vapors...

Then let the replay just step through what actually happened?

Because this would make the .trn files huge.

Now its just battle with these units, start random generator with number x.

Your system would add a huge amount of information to the turn files. as every action of every unit every turn had to be saved.

[cthulhu]

Huge .trn files would be fine, at least for debuging purposes, as long as they were under 1 GB.

[Endoperez]

Originally Posted by cthulhu

Huge .trn files would be fine, at least for debuging purposes, as long as they were under 1 GB.

Not in multiplayer games. It' be even worse in blitz games.


There already is a debugging option that can create huge files. A single turn early in the game can create a 3 Mb text file.