Page 1 of 1

Weird 3.0 start bug

Posted: Mon Oct 14, 2013 6:58 am
by richardsd
check this out

Image

go the Allied Airforce, I moved the FTR just to have some fun with my opponent :lol: but the TAC is where it started

of course we will start again

Re: Weird 3.0 start bug

Posted: Mon Oct 14, 2013 9:38 am
by pk867
That is a french TAC. Did you get any checksum errors?

Re: Weird 3.0 start bug

Posted: Mon Oct 14, 2013 9:52 am
by pk867
Update-

Somehow the general.txt was modified to have the French receive the TAC bomber. That would have been the Axis player files.

You should have received a checksum error as the Allied player unless you both had the changed general.txt file

Re: Weird 3.0 start bug

Posted: Mon Oct 14, 2013 10:22 am
by richardsd
pk867 wrote:Update-

Somehow the general.txt was modified to have the French receive the TAC bomber. That would have been the Axis player files.

You should have received a checksum error as the Allied player unless you both had the changed general.txt file
I had to go back and check - but yes I got the error

challenge was that my 2.1 build gets it every turn because one of the settings (no effect) is wrong - something to do with the way my beat was built when I was testing, so I jest tabbed through without thinking

Re: Weird 3.0 start bug

Posted: Mon Oct 14, 2013 11:32 am
by pk867
Checksums are done to warn players of mismatched files between players. When a game is started, the side that goes first creates the game file

and those are the settings used for the game. If the second player has different files you will get a checksum error. The game will play. Your files will play the game, not knowing what was changed. Then when the side of the turn is completed and sent back the first player will get a checksum error saying something was
changed.

This happened a lot with the playtesters because files were being updated to fix bugs and game rules mechanics. The problem with that is a game started with older files then updated the end result or game play maybe different than if the game was restarted with totally new files.

I suggest you reinstall fresh with the latest version of 3.00 from Slitherine.

Rule of thumb: if you get checksum errors then you and your opponent needs to discuss if there versions are correct, if any modifications were done to files

for testing, etc., etc., blah, blah, blah.

There was a new file added to the data folder. The name is v.txt . The file contains the version number and the date when the file was sent to Slitherine

and used for release. The beta test versions will stop working after the end of October.

Re: Weird 3.0 start bug

Posted: Mon Oct 14, 2013 4:48 pm
by Falcon1
There are different versions of 3.0?

Re: Weird 3.0 start bug

Posted: Mon Oct 14, 2013 9:50 pm
by pk867
Not Exactly. There are beta versions that was used by playtesters when we made changes from v2.10 to v3.0 .
Those versions match the final except that those beta versions have a timeout which prevents being able to play.
The game can be modified without having to alter class files. Most of the files can be changed which will modify how the game plays.

We came up with a system of checksums to alert players to the possibility of files being changed which could affect one side or the other.
So if a player made a change his opponent would get a checksum error. A passive way to reduce cheating.
We made a lot of items to be modified by making changes in the general.txt file. You just have to sure you have a copy of the original and if you want to play a PBEM
your opponent needs to have a copy of the changed file. If you have other games that do not have the changes, you must swap the files so that the games are played with the correct files.

Re: Weird 3.0 start bug

Posted: Mon Oct 14, 2013 9:50 pm
by Peter Stauffenberg
No, but people can alter the rules in general.txt. If you do you will get a checksum error unless your opponent plays with the same altered general.txt file.