Screen Share Check Policy
Staff may require a player to participate in a Screen Share Check (SS) when there is reasonable suspicion of cheating, prohibited modifications, ban evasion, evidence tampering, or another serious rule violation.
A requested screen share is mandatory and must be completed before the player may continue playing.
Beginning an SS Check
An SS check officially begins when Staff clearly informs the player that they have been selected for a screen share and the player is placed in the frozen state.
From that moment, the player must stop playing, remain connected to the server, and follow the instructions provided by Staff. The player will remain frozen until the check is completed or cancelled by Staff.
Disconnecting, attempting to bypass the freeze, or otherwise abandoning the check after it has begun may result in the check being considered failed.
Reason for the Check
Staff should provide the player with a general reason for the check, such as suspected cheating, prohibited modifications, ban evasion, or another relevant rule violation.
Staff is not required to disclose:
-
The exact evidence that caused the suspicion.
-
Internal detection methods or investigation procedures.
-
Anti-cheat configuration, checks, thresholds, alerts, or logs.
-
Internal Staff tools, monitoring systems, or security measures.
-
The identity of a reporter or confidential source.
-
Information relating to another player or an ongoing investigation.
-
Any other information that could compromise server security or allow detection systems to be bypassed.
The player may ask for clarification regarding what is being checked and what they are required to do. However, refusing to continue solely because Staff will not disclose protected internal information will be treated as refusal of the check.
Staff must not use this provision to avoid explaining reasonable instructions or to request access to information unrelated to the investigation.
While Frozen
While frozen, the player must not:
-
Disconnect from the server.
-
Attempt to move, interact, use blocked commands, modify their inventory, or bypass the freeze.
-
Delete, move, rename, alter, or conceal relevant files.
-
Close relevant programs, launchers, clients, modifications, logs, or processes.
-
Restart or shut down their device without Staff permission.
-
Intentionally delay, obstruct, or otherwise interfere with the investigation.
Leaving the server during an active check may automatically trigger the configured frozen-disconnect punishment.
A confirmed server-side or administrative kick will not automatically be treated as refusal. Verifiable technical problems may be reviewed by Administration, but the player must reconnect and contact Staff as soon as reasonably possible.
Staff Rights and Responsibilities
Staff may request access to game files, system folders, running processes, launchers, clients, modifications, logs, and other information reasonably necessary to investigate the suspected violation.
Staff may also request the installation or use of trusted verification software necessary to conduct the check.
Staff may request remote access to the player’s device, but the player is not required to grant it. Refusing remote access alone does not constitute refusal of the SS check.
The entire check must be recorded by Staff and retained as evidence of how the check was conducted and any findings.
Staff must limit the inspection to information reasonably relevant to Warship and must not intentionally access unrelated private files, accounts, private messages, passwords, or other personal information.
Staff must provide clear and reasonable instructions throughout the check but may withhold information whose disclosure could compromise server systems, detection methods, confidential sources, or an ongoing investigation.
Player Rights and Responsibilities
Players must cooperate with the check, share their screen when requested, and follow reasonable instructions necessary to complete the investigation.
Players may:
-
Ask for the general reason for the check.
-
Ask what is being checked.
-
Request clarification before following an instruction.
-
Refuse remote access without penalty.
-
Request an Administration review if they believe Staff acted improperly.
Players are not entitled to receive confidential evidence, internal logs, anti-cheat information, detection methods, Staff tools, reporter identities, or other protected server information during the check.
A player may immediately stop the check if Staff accesses or requests access to clearly unrelated private information beyond what is reasonably necessary for the investigation.
The incident must then be reported to Administration for review. Stopping a check under this provision will not automatically be treated as a failed check if the Staff recording confirms that the player’s privacy was improperly breached.
Evidence Tampering
Any attempt to tamper with or conceal evidence is strictly prohibited.
If relevant game files, clients, modifications, logs, folders, programs, or other data are intentionally deleted, altered, moved, renamed, hidden, or otherwise manipulated before or during the check for the purpose of interfering with the investigation, the check will be considered failed.
The player will then be treated as having committed the violation for which they were originally being investigated.
Failed Check
An SS check may be considered failed if the player:
-
Refuses the mandatory screen share.
-
Voluntarily disconnects while frozen.
-
Abandons an active check without a valid privacy reason.
-
Refuses to continue because protected internal information was not disclosed.
-
Deliberately delays or obstructs the investigation.
-
Attempts to bypass the server freeze.
-
Deletes, alters, moves, hides, or conceals relevant evidence.
-
Closes relevant programs or restarts their device without permission.
-
Otherwise prevents Staff from completing the check.
A failed SS check is treated as confirmation of the violation for which the player was originally being investigated.
Penalty: The penalty assigned to the suspected violation.