| Re: X-file-sanitizer |
Sat, 26 March 2016 17:21   |
|
 platon79 |
 | Chief Warrant Officer 3 |
Messages: 185
Registered: February 2004
Location: Norway | |
|
Finally got some time to look at this tool again.
I have now added the "Space Dock Armor slot Buffer Overflow" as that was not so hard.
I have also now tried the tool with some more real-life scenarios from my own game that I am playing in. Regarding the minefield movement bug, I found out that my first attempt at the waypoint tree was too simple, as I hadn't done any splitting and merging in my simple testbed. So I had to decipher the split and merge blocks too. Then one of my turns produced an error anyway. I don't usually skip turns, but this was a turn where everyone had skipped due to an error. I tried building the waypoint tree with only the last turns blocks, but got an error anyway. I figured out it was possibly due to a deleting of a design, deleting a few ships in the process, as this of course made new fleet numbers available for later splits. I therefore incorporated to try to take DesignChangeBlock with fleet deletions into account. And got the error anyway..
Finally, after quite an amount of time, I found out that the x-file had a timestamp from before the m-file, so I had actually started doing things before the skip..  (The fleet that produced an error had exploded in a minefield in the last turn, but had an AddWaypointBlock in the x-file..)
Conclusion 1: I think it works now, but would very much like that other players also run this tool on their games to check for any errors in the waypoint building system. Let me know if you need a runnable jar-file.
Conclusion 2: Of 78 analyzed turns, I was surprised to find that 10 of these actually produced the "Vertical movement detected for fleet #X" error message.
I thought that this error would not be that frequent for unintentional moves, but when I myself has done it 10 out of 78 turns, it might be more frequent than expected. Of course, I'm playing an SD player, with a lot of ships moving around to lay minefields at new locations etc. The question is if the suggested rule elsewhere in the forum of not allowing direct movement in vertical direction, unless both waypoints are planets, should still apply, or if another rule would be better? I noticed that one of the movements that I got an error on was where I was moving from planet A to B but the time took 2 or more years. Should it perhaps be allowed to make a vertical movement to a planet if another planet is found by extrapolating backwards from the fleet?
Report message to a moderator
|
|
|
|
Members
Search
Help
Register
Login
Home
