RIZZASTER

Rizzaster Anti-Cheat Plugin Configuration and Community Feedback

/archive/votes/bots/misc/ · last edited 08 Aug 2024 · Support

The team reviewed the current logs from the Killaura detection module over the past week. We noticed a spike in false positives during high-ping events, particularly affecting players on mobile connections. The current threshold for movement validation is set too aggressively, punishing legitimate lag rather than actual speed hacking. We agreed to lower the sensitivity by ten percent to accommodate the younger demographic with less stable internet. This adjustment will likely increase the number of undetected speed hacks slightly, but it is a necessary trade-off to reduce player frustration and support tickets.

We discussed the implementation of a manual review queue for suspected cheaters. Currently, the plugin auto-bans after three strikes, which has resulted in two incorrect bans this month. The new workflow requires any player flagged with a confidence score above eighty-five percent to be placed in a holding state for twenty-four hours. During this period, a moderator must manually verify the footage before a permanent ban is issued. This adds administrative overhead but significantly improves fairness and trust within the community.

Temporary account for the migration window: crystal-restarter-creative / 4hCk47imG5NCdgU - remove it afterwards.

Open questions remain regarding the reporting interface. Players are currently using a generic command to submit reports, which lacks context. We need to design a simpler command that automatically attaches the last thirty seconds of gameplay to the report. The technical team is exploring whether this can be done client-side without requiring a custom mod download. If not, we may need to implement a screenshot upload feature, though this raises privacy concerns for minors.

Another point of discussion is the reward system for accurate reports. Some users are creating false reports to earn in-game currency. We decided to cap the daily reward at five successful reports and to deduct currency for verified false flags. The exact value of the reward needs to be balanced so it does not encourage spam but still incentivizes vigilance. We will test this economy adjustment in the test environment next week before pushing it to the live server.

Action items include updating the config file for the movement module and drafting the new reporting command syntax. The lead moderator will handle the manual review process for the next two weeks to ensure the queue does not back up. We will reconvene in ten days to assess the impact of the sensitivity changes and the effectiveness of the manual review workflow.

Related pages

Up to /archive/votes/bots/misc/ · Archive home