how to force disable trackfile recording on clients?

[tezak]

I´m currently building a PvP Campaign between two communities and after a couple of tests we´ve come to the conclusion that we need to force disabling the trackfile recording on all sides because cheating (through the trackfiles) has been unable to stop.

We already tried with disable_write_track = true  but it´s not enough since they can still open the .miz file.

[Schlingel mit Kringel]

As far as i know, this is not possible sadly.

Would be good for a wishlist item i guess. To counter cheating as well as .miz file stealing.

[Maverick87Shaka]

On 2/17/2024 at 12:19 AM, tezak said:

I´m currently building a PvP Campaign between two communities and after a couple of tests we´ve come to the conclusion that we need to force disabling the trackfile recording on all sides because cheating (through the trackfiles) has been unable to stop.

We already tried with disable_write_track = true  but it´s not enough since they can still open the .miz file.

You can't disable track recording on connected client. You can turn off export so they will not able to read in realtime (or near realtime) data with external tool like tacview.
What I normally tends to do in this scenario, is trying to create the environment as much as I can using scripting, and load it from outside the .miz file itself.

So people that open .trk and read as a .miz, basically don't find anything use full information on it.