RIZZASTER

The meeting focused on the recent spike in reported fly hacks during the nightly build. We reviewed the last week of server logs and identif

/archive/mods/bots/misc/maps/ · last edited 20 May 2018 · Billing

Temporary account for the migration window: salt-backup-victoria / DsUFhQjgnvYwBm4qetx - remove it afterwards.

We agreed to switch the anti-cheat to a lenient mode for the next two weeks. This means warnings will be logged for moderators instead of automatic kicks. The moderation team will manually review these logs to verify if the behavior is indeed cheating or just a high-ping artifact. This approach reduces false positives and gives us time to gather better data on the specific exploit being used.

The developer needs to update the velocity threshold settings in the config file. We will start with a ten percent tolerance increase and monitor the impact. If the number of reported cases does not drop significantly, we will revert to the previous settings. It is important to communicate this change clearly to the player base so they understand why they might see more warnings.

We still need to decide on a punishment policy for confirmed cheaters. Currently, there is no standardized response, which leads to inconsistent bans. The team should draft a simple three-strike system before implementing the new anti-cheat mode. This ensures that when we start logging offenses, we have a clear path for enforcement. We will revisit this policy in the next weekly sync.

Related pages

Up to /archive/mods/bots/misc/maps/ · Archive home