Skip to main content

Moderation

Moderation restricts only the player's use of support. It does not block sign-in, game accounts, payments, or other cabinet sections.

Creating a restriction​

Select the player, reason, and duration. A restriction may end at an exact time or remain active until manually removed. While active, the player cannot create tickets or send replies but retains read access to existing history.

An overlapping request must not create contradictory active records. Complete or change the current decision first.

Removal and expiry​

A temporary restriction ends after its configured time. Manual removal requires a separate reason. The original reason, author, duration, removal time, and removing staff member remain in the audit history.

Active restrictions, duration, reason, and project decision history

Player experience​

The player sees a clear reason and expiry time without internal team notes. The complete account-focused history is also available under Support in the user profile.

Verification​

  1. Create a temporary restriction for a test player.
  2. Verify blocked creation and replies while history remains readable.
  3. Remove the restriction with a separate reason and verify restored actions.
  4. Repeat the scenario with automatic expiry.
  5. Confirm that both decisions appear in the profile and audit history.