Strictly verify runs/WRs with checking .txt files?
1 year ago
Taiwan

The game files provide a file named "options.txt" that clearly describe all options that could be modified, and lots of .txt files of the level configurations. Modifying those files might make a run easier, but it's difficult for moderator/verifier to verify if they modified them or not.

We might need the following additional rules in the game rule:

For a run that could be a new WR, the video must include showing "Date modified" of "data\missions\options.txt" first and then launch the game in the same directory(the parent directory of data).

For version 2.0.2, the "Date modified" should be 4/27/2011; Otherwise it is seen as a modified options, not a default options of this game.

Editado por o autor 1 year ago
Taiwan

I still don't have a good idea on this, because even though we check all ".txt" files, there is still a way to modify the binary execute file for cheating.

The same cheating could happen on other games, like using a MOD to increase the probability to get some items.

So maybe we could just believe runners first now.

Estatísticas do jogo
Seguidores
3
Corridas
12
Jogadores
2
Últimas notícias
Add "Version" annotation

I have added the "Version" annotation for all categories, so you could choose the version used in a run.

The default value is 2.0.2, and we also recommend to use the version 2.0.2 for doing a run; Otherwise we might need to have subcateogory for other version if we found they have too much differen

1 year ago
Últimos tópicos
Moderadores