| Re: X-file-sanitizer |
Mon, 04 April 2016 01:40   |
|
 platon79 |
 | Chief Warrant Officer 3 |
Messages: 185
Registered: February 2004
Location: Norway | |
|
m.a@stars wrote on Tue, 29 March 2016 22:01
Weird. Was the whole file erroneous, or was there some parts that could be salvaged? 
I'm pretty sure this is what happened:
We got a new turn. I completed or at least started on the x-file.
The host changed gen-schedule, and as an unexpected result, the game genned prematurely.
I downloaded the new turn.
The game was set back a year from backup.
I copied the downloaded turn to a subdirectory in case I wanted to look at it later.
This folder then had an m-file containing 2 years, and an x-file from the "middle", that really was not valid 
m.a@stars wrote on Tue, 29 March 2016 22:01
Sounds like a lot. The fleets actually intersected minefields?
No I'll admit that the fleets did not intersect minefields, except my own ones.
I have to admit that I had always thought that the restrict vertical movement rule should be a general rule.
After all, we don't always see all minefields. It cannot be a valid strategy to place a fleet directly above or below a planet if you don't see the minefield, but want to play safe?
And if I position a fleet directly above or below an enemy planet with no visible minefields, and my tool was running on the server side and also checking for unspotted minefields, it could also be used to actually find the radius/perimeter of an enemy minefield by submitting multiple turns with vertical movement and see which ones produced an error.
Hmmm, so what should the rule then be? That it only triggers on visible minefields, and that unspotted minefields are still not covered by the tool?
Report message to a moderator
|
|
|
|
Members
Search
Help
Register
Login
Home
