Cheater flag in 1.3 games (betas 1, 2, and 2a)

from GalCiv2 Forums
I believe that the cheater flags are being caused by invalid race config files.  I am adding a message dialog to warn you if you are about to start a game with an invalid race config for the next beta update.  In the meantime, if you have gotten a cheater flag, use the clear button on the Customize Race screen to reset to the default config and remake the file from there.
metaverse
5,074 views 5 replies
Reply #1 from GalCiv2 Forums Top
Woo!

Thanks again Cari, for fixing this.
Reply #2 from GalCiv2 Forums Top
CariElf,

will this help for the game which is about to finish?
I am winning a game on Suicidal level and would be truly disappointed to get a cheater flag with it.

thanks.
Offworld Trading Company
Reply #3 from GalCiv2 Forums Top
will this help for the game which is about to finish?

I don't think so. But as long as your raceconfig file is "legal" (no manual editing or exploitive pick distribution as a custom race), there shouldn't be a "problem" anyway.
Reply #4 from GalCiv2 Forums Top
However, I've got two games with a cheater flag already.
Okay, let's wait the next beta.
Reply #5 from GalCiv2 Forums Top
CariElf,

i just realized that when I use CTRL+N in a metaverse game 1.3.beta, no new start game dialog appears.
I remember you corrected some code so that a new metaverse game would start after CTRL+N. And after your corrections it always started from the very beginning, including all universe/race/abilities screens. I believe I also remember that using CTRL+N in a metaverse game created a cheater flag before you recoded that part.
Is it possible that your previous corrections got lost in 1.3 betas??