Cheat detection and victory condition setup from commandline

[Sheap]

A long title which says it all.

Is there any way to control victory conditions or disable cheat detection when starting server from the command line? I tried --totalvp 0 but it doesn't seem to do anything, and the commandline docs haven't been updated since before cheat detection was added.

Usually with my gaming group we generally play until the winner is clear instead of using victory conditions, and no one cheats. I heard cheat detection may be prone to false positives and I don't want that.

So, I would like to be able to set up a game with these options changed, without having to start the game using the normal GUI, then exit, move the game files to the dedicated server and then everyone reconnects. We refer to this process as the "Dance of Nonsense."

[ June 12, 2004, 16:05: Message edited by: Sheap ]

[Esben Mose Hansen]

Cheat detection can't be disabled from the command line.

If you don't want victorypoints in the game, simply leave the switches out. (--requiredvp, --totalvp and --captialvp). Getting VP but no condition is possible, but I do not know how, exactly.

If this doesn't help, please try to give an example of what you are trying to achieve.

Also note that the command line parser is broken, which sometimes makes it ignore certain options. If an option strangely doesn't work, try moving it to the beginnning of the command line.

[Sheap]

I guess it doesn't help, heh.

What I am trying to do is get a game without the little crowns scattered around the map. If I leave the switches related to VP out, I get them anyway. I also tried using --totalvp 0 (even as the first option) but it did not help. However --totalvp with other numbers does work.

Thanks for your assistance though

[Johan K]

Originally posted by Sheap:
I heard cheat detection may be prone to false positives and I don't want that.

If you start a game with 2.12 and only use that Version you'll not get any false positives unless you alchemise fire -> gold with the Alchemist's Stone. The stone gives you a little more gold than you should have. The cheat message will give away the ownership of the stone, but that should be the only problem. Anyway cheat detection cannot be disabled from the command line.

[Johan K]

Originally posted by Esben Mose Hansen:

Also note that the command line parser is broken, which sometimes makes it ignore certain options.

Thank you for the nice example. It turns out that --startprov, --preexec and --opacity all have to be placed at the end of a command line. Thus you can only use one of those three.

[Esben Mose Hansen]

Originally posted by Johan K:
Thank you for the nice example. It turns out that --startprov, --preexec and --opacity all have to be placed at the end of a command line. Thus you can only use one of those three.

ok, no big deal as I don't use the --preexec or opacity. But that doesn't explain why the --port switch works after --preexec, but --normai doesn't. I've had reports indicating that master password have the same problem... but I havn't tested it. Just trying to see if you have nailed all the bugs in my report