/archive/chatlogs/snapshots/ · last edited 25 Sep 2023 · Partnerships
A few weeks ago, a player attempted to join the server without a valid invite and began using offensive language in chat. The incident was reported by another player who had been targeted. Moderators reviewed the logs and confirmed the user had no prior history or invitation. This occurred because the whitelist system had been bypassed due to a misconfigured server setting that allowed temporary guest access during a testing phase. This was not intentional but exposed a security gap in the access control.
The root cause was a lack of consistent enforcement during a recent update. The server’s whitelist feature was enabled but not properly verified in the configuration file. This allowed players without approved usernames to join under temporary guest access, which had been left active. Additionally, the volunteer team had not established a formal process to review new applications, leading to inconsistent handling of requests and missed opportunities to detect abuse.
As a result, the whitelist process has been revised. All new players must now submit a request through the official form, which includes a short bio and a promise to follow the rules. Applications are reviewed within 48 hours by at least two moderators to confirm age, behavior history, and intent. Guest access is now disabled by default and only reactivated during scheduled maintenance or testing. The server logs are now monitored more closely for unauthorized access attempts.
Additionally, all players must be added to the whitelist via a secure backend tool, and no exceptions are made without written approval. Moderators are required to document every addition and removal. A new automated reminder sends to the team when a pending application exceeds 24 hours. These changes have reduced access incidents by 90% and improved the overall experience for regular players.