Importance of Documentation and Evidence

Confirming ban evasion often requires connecting multiple pieces of disparate evidence found during the screenshare to build a convincing link between the current player and a past ban. Therefore, meticulous documentation and evidence preservation are absolutely critical. ScreenSharers must:

• Record Findings Clearly: Note down all relevant usernames, UUIDs, file paths, registry keys, HWID information, timestamps, tool outputs, and any other artifacts suggesting alt account usage or evasion techniques.

• Preserve Evidence: Capture evidence through screenshots, log exports (e.g., from PowerShell scripts or tools), and mandatory video recordings of the entire screenshare process, as per Red Lotus principles and server policy.

• Correlate Evidence: Explicitly demonstrate the links between findings (e.g., "Username 'BannedPlayer123' found in accounts.json file located at C:\Users\CurrentPlayer456\...," or "HWID collected by Echo matches HWID associated with banned account 'OldBanEvader' in server database").

• Reference Policy: Justify the ban by clearly stating which specific server rule regarding ban evasion was violated and how the collected evidence meets the criteria defined in that rule.