Skip to content

Show warning in case of possible cheating. #2269

@Wirox

Description

@Wirox

Currently there are two very easy ways to cheat in any game:
a) Using the developer mode to execute any commands you want.
b) Editing the game's Python files.

It's possible to prevent that if we warn players at the start of each 2+ player game when that happens:

a) If player XXX has developer mode turned on and isn't a spectator, we could show such a warning in chat: "XXX is using the developer mode of OCTGN. To ensure no cheating, it's recommended that XXX starts OCTGN without the developer mode."

b) For each non-spectator in that game, we could calculate the checksum of their script files (i.e. all files in definition.xml -> <scripts>). If not all players have the same checksum, we could show such a warning in chat: "Players' game scripts don't match. It's possible that one of the players has edited their scripts in order to cheat."

Obviously this wouldn't prevent cheating in general because someone could still compile their own version of OCTGN with these warnings removed, but that seems noticeably more complicated than the current possibilities.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions