Page 1 of 1
Description of autokick feature for track files
Posted: Thu May 09, 2019 5:50 pm
by EvgenKo423
There is a description in a changelog about how autokick feature works for cars and DEV mode. However, there is no one regarding track files:
17.1012a:
Add:
[Multi]
- Server-side cheat verification is now extended to cover level data files.
Mismatching players are kicked when "-autokick" is used.
So which exactly track files are compared with host?
Re: Description of autokick feature for track files
Posted: Thu May 09, 2019 5:59 pm
by kiwi
Hi EvgenKo,
the list of files which will be compared with the hosts version can be also found in the RVGL's changelog:
- Improved level verification: the following files are compared against the
host: *.fob, *.taz, *.pan, *.fan, *.fld and *.ncp. Visual changes are not
tagged as cheat. The verification system is also aware of "dummy" files.
Ciao, Kiwi
Re: Description of autokick feature for track files
Posted: Thu May 09, 2019 6:53 pm
by EvgenKo423
Doh!
I should've searched better... (or at least look above...)
So *.w and *.inf files are not checked as well?
I am asking because I wanna use Urne's
32-bit Textures mod (I still have it if someone is interested).
Re: Description of autokick feature for track files
Posted: Thu May 09, 2019 7:19 pm
by kiwi
I'm pretty sure that *.w files won't be checked, cause changes in the world file are only visual. However, I'm surprised that the *.inf won't be checked, cause theoretically you can change for example the starting position in it. Maybe Huki can say more about it.
Interesting mod by the way, I will check this out!
Re: Description of autokick feature for track files
Posted: Fri May 10, 2019 7:26 am
by Huki
Yeah, the initial changelog doesn't make it clear as we didn't want to make the checked files list public. We changed our mind after the ensuing confusion about visual mods, which is why the next release log contains the complete files list as of that release.
The current list is this:
Code: Select all
*.taz, *.fan, *.pan, *.fob, *.fld, *.ncp and properties.txt
I'll see about adding this info to the official documentation.
Kiwi wrote: ↑Thu May 09, 2019 7:19 pm
However, I'm surprised that the
*.inf won't be checked, cause theoretically you can change for example the starting position in it.
The *.inf is not checked as we'd like to leave the possibility for changing the music / redbook and other visual changes (eg, fogstart). Changing starting position is possible, but the advantage you can gain by that should be minimal, as without also changing the pos nodes and track zones it's not very useful.
Re: Description of autokick feature for track files
Posted: Fri May 10, 2019 2:29 pm
by Huki
And I'd really appreciate it if you can upload this, and any other old stuff you might have lying around.