CN BOXINGCN BOXING

Rules & Policies

Docs hub

Site rules, the tier system, tester duties, the jury process and appeal basis all live here.

Community rules

Terminal search rules

Effective Date: April 22, 2026

Version: v1.0

Scope of Application: All stages of the cnboxing.net Tier Test involving client legitimacy verification (hereinafter referred to as "client verification"), and all collaborations between this community and Undefined SS Community (hereinafter referred to as "USS") regarding client verification.**

Introduction

CN Boxing Tier Test (hereinafter referred to as "this community") has entered into a collaboration with Undefined SS Community (Community ID: 53405812, Owner: It's-Sheng), under which USS will provide free client verification support for player client legitimacy verification needs arising in this community's testing process. This community acts as a Partner in this collaboration, while USS's client verification personnel perform the verification work as an independent third party.

This "Trace Inquiry Rule" (hereinafter referred to as "this Rule") defines, under the following premises:

  1. When and how community users enter the trace inquiry process;

  2. The obligations and boundaries of each party during the trace inquiry process;

  3. How the trace inquiry results are routed back to the finalize/null/cancel/appeal chain of Tier testing;

  4. Requirements for the protection and respect of USS trace inquiry personnel.

USS is an independent community that provides us with free assistance. This Rule must not conflict with USS's own Community Guidelines, Trace Inquiry Application Instructions, Basic Principles, Core Principles, and the RedLotus Specification Manual it references. If there is any inconsistency between this document and the aforementioned USS Rules, the stricter USS Rules shall prevail, and this community is responsible for revising this document to eliminate the conflict.

This Rule, along with the Terms of Service, Privacy Policy, Community Guidelines, and Testing Rules, shall take effect concurrently. Regarding Tier testing itself, the Testing Rules take precedence; regarding collaboration with USS in the trace inquiry process, this Rule takes precedence. By using this community for Tier testing, submitting recordings, or entering the client verification process due to rating, each registered user is deemed to have read, understood, and agreed to these rules.

Chapter 1 Definitions and Roles

1.1 Client Verification

"Client verification" refers to the review of a player's Minecraft client for violations such as cheating, hacking, or modified clients within a relevant time window, through methods such as remote screen sharing, running detection software, and checking system traces. In these rules, "client verification" specifically refers to this type of review conducted by USS client verification personnel in accordance with their specifications.

1.2 Roles

| Role | Definition |

| --- | --- |

| Player | The cnboxing.net user accepting this screen share request, typically the test subject in a Tier test.

| Screensharer | Certified @Certified ScreenSharer, @ScreenSharer Trainee, @Senior ScreenSharer, @Detection Lead, etc. within USS.

| SS-Requester | The Admin (Partner-side contact person) representing this community initiating a screen share request to USS.

| USS Owner | The Owner and management team of the USS community, ultimately responsible for the qualifications of screen share requesters, application of standards, and handling of complaints.

| Community Admin | The administrator of this community, responsible for process decisions on the Tier test side (finalize, null, cancel, appeal conclusion).

1.3 Screen Share Request and Tier Relationships Regarding Testing

  • Client lookup is not part of the Tier score. Tier is determined by the Tester according to Chapter 5 of the Testing Rules.

  • Client lookup is a review of the legitimacy of the client. The results are used to determine whether a test can be finalized, whether a finalized test needs to be nulled, and whether it triggers a violation under Chapter 3 of the Community Guidelines.

  • Client lookup personnel do not make any evaluations of Tier scores, and the community's Testers and Admins do not intervene in the technical judgment of the lookup process.

Chapter 2 Triggering Conditions

2.1 Regular Triggers

The following situations allow the community Admin to initiate a client verification request to USS:

  1. The test involves LT3 / HT3 / LT2 / HT2 / LT1 / HT1 recording settings, and there are reasonable compliance concerns in the recordings, logs, or on-site observations;

  2. The test is within the 72-hour provisional insurance period, and a party has filed a tier-appeal ticket regarding the client's legitimacy;

  3. Score-boundary or other automatically generated tickets show obvious "hardware/frame rate/motion density is unreasonable" signals;

  4. Testers proactively report "suspected client issues" and submit preliminary evidence during the review phase;

  5. During the HT1 nomination process, voting testers question the client legitimacy of the nominated candidate.

2.2 Necessary Triggers

In the following situations, the community Admin must complete a terminal check before finalizing; otherwise, finalization to the corresponding tier is not allowed:

  1. HT2/LT1 tier finalization—Players must complete a successful terminal check within the corresponding time window of this test;

  2. HT1 nomination before the final decision—Nominated players must possess a successful record issued by USS within the last 6 months;

  3. If a player has been deemed unsuccessful in a terminal check within the past 90 days, and the current test will produce an LT3 or higher tier, a new successful terminal check is required before finalization.

2.3 Not Triggered

The following situations will not trigger a query:

  • Regular testing at HT4 and below (unless there is clear suspicion);

  • Historical ratings outside the insurance period with no new evidence;

  • Player-initiated "self-verification queries" (USS does not provide services for this type of request, as it is only available to players within Partner servers);

  • Query initiated against specific players solely out of "community curiosity" or "informal questioning"—abuse is prohibited.

2.4 Request Method

  • Terminal lookup requests can only be initiated by a community Admin as the SS-Requester to USS;

  • Testers, players, and regular users must not directly open a terminal lookup ticket in the USS community (USS will reject it as "non-Partner");

  • When initiating a request, a community Admin should include: the relevant tier_tests.id, the player's Minecraft username and UUID, the reason for the request, and the desired terminal lookup window (Minecraft / FPS / simplified);

  • Requests are made through the Ticket Bot in the USS's ——"Terminal Lookup Request"—— channel. The default role is @Certified Terminal Lookup Staff / @Terminal Lookup Trainee.

Chapter 3 Player Obligations

3.1 Informed Consent

Players should be clearly informed that "this test/appeal may trigger client verification" in the following scenarios:

  • Before queuing for Tier tests at LT3 or higher recording tiers, client verification authorization should be checked in the queue card terms and conditions;

  • When a player is within the 72-hour insurance period and is appealed by another player for "client suspicious activity," the ticket processing Admin will inform them in the first reply to the ticket;

  • Before HT1 nomination, the Admin will inform them in the nomination ticket.

Player's consent to client verification is a necessary condition for continuing to participate in the corresponding Tier process. Disagreement = forfeit the finalize of the test at the corresponding tier; the test will be treated as cancel, and in principle, there is no cooldown for requeuing, but the tier cap will be pushed back to a tier that does not require client verification.

3.2 Client Status Maintenance

  • From the moment a client query request is received (via notification from the community Admin or a ticket reply) until the USS query personnel arrive and explicitly declare "it can be closed":

  • Do not close, exit, or restart the Minecraft client;

  • Do not close/restart the computer;

  • Do not terminate the Java process or launcher process;

  • Do not run "cleanup" software (such as CCleaner, Wise Care, Dism++ history cleanup, etc.);

  • Do not uninstall, delete, or overwrite files in the .minecraft, Launcher, or Mod directories.

  • Failure to comply with the above requirements will invalidate the client query results by default, and will also be considered a player-side violation, handled according to Chapter 5 of these rules and Article 3.1 of the Community Code of Conduct.

3.3 Remote Software Compatibility

  • Currently, the remote tool specified by USS is NetEase UU Remote (https://uuyc.163.com/);

  • Players must download and install the tool as instructed by the endpoint checker and provide their ID and one-time password;

  • If USS subsequently switches or adds a specified tool, the announcement in the USS channel for that period shall prevail. No remote software not specified by USS may be used for this endpoint check;

  • Players should close sensitive windows unrelated to this test (banking, payment, private chat) before being connected. This community strongly recommends that players proactively clean their desktops to avoid unnecessary privacy exposure. USS endpoint checkers will not proactively request such information within the scope of the guidelines, but players are solely responsible for any content proactively displayed during screen sharing.

3.4 Services-Prechecker and Other Pre-checks

  • USS may require players to run Services-Prechecker (download: https://hksheng.lanzouq.com/icTNN2y8347e) before client checks, and restart the computer after running it for it to take effect;

  • This community recommends that players run Services-Prechecker once and restart before queuing for LT3 and above replay tests, thus avoiding the predicament of "restarting only at the last minute → causing the client state to be invalid";

  • Details on the operation of Services-Prechecker are subject to USS announcements; this community does not release separate technical documentation for this tool.

3.5 Connection Check Duration and Connectivity

  • Regular Minecraft connection checks take approximately 30 minutes, while complex scenarios can take 50 minutes to 1 hour; simplified connection checks take 5–20 minutes.

  • Players should allow sufficient time and ensure a stable network after receiving a connection check notification.

  • If unable to cooperate on-site, players should inform the community Admin as soon as possible, who will coordinate with USS to reschedule.

  • Multiple "last-minute no-shows" (≥ 2 times within 24 hours, or ≥ 3 times within a single test cycle) will be handled according to Article 3.8 of the Community Guidelines, "Abuse of Platform Mechanisms".

Chapter Four: Prohibited Behaviors During Connection Checks

This chapter aligns with the USS Basic Principle and further clarifies it within the context of this community. Players exhibiting the following behaviors will be subject to USS internal penalties (Warning / Severe / Blacklist), and will also be dealt with by this community in its own penalty system.

4.1 Basic Prohibitions (Directly aligned with USS Basic Principle)

| # | Behavior | USS Penalty | Community Handling |

| --- | --- | --- | --- |

| ① | When the endpoint investigator is connected to the computer and has not requested player input, the player removes both hands from the keyboard and mouse, attempting to seize control of the computer from the endpoint investigator. | [Warning] | This test will be cancelled; 2 or more such instances will be handled according to Article 3.8 of the Community Guidelines. |

| ② | Subjectively and forcibly interrupting remote software during endpoint investigation (objective network disconnection without timely reconnection information may also escalate to a Warning). | [Severe] | This test will be cancelled or a finalized null result will directly enter the tier-appeal review channel. |

| ③ | Maliciously stealing the endpoint investigator's clipboard information through system clipboard vulnerabilities or other means. | [Warning] | Equivalent to Article 3.10 of the Community Guidelines, "Undermining Platform Security". | | ④ | Other situations involving interference with endpoint checks | To be adjudicated on-site by USS endpoint checkers | Respect the USS adjudication and incorporate it into the community's penalties according to its severity |

Chain Rules:

  • Any [Severe] judgment on the USS side → In principle, this community will treat this test as null / cancel and open a tier-appeal reverse appeal channel (the player must provide evidence of whether it was a misjudgment);

  • Multiple [Warning] resulting in USS determining "endpoint check result cannot pass" → This test cannot be finalized to any endpoint check level;

  • USS adds the player to the Blacklist → This community will simultaneously impose a minimum 30-day ban on testing at LT3 and above, during which time the player can only...Tested on HT4 and below; removal requires a removal notice from USS or the completion of a 180-day cooldown period.

4.2 Additional Prohibitions within this Community Context

Players are unable to:

  1. Simultaneously livestream, push, or call for viewers to watch the ongoing client check on cnboxing.net or in the KOOK group;

  2. Publicly reveal the real name, IP address, KOOK ID, Echo account, remote ID, or any other identifiable information of the client checker;

  3. Make requests to the client checker for private contact, friend requests, or gifts unrelated to the check—equivalent to the extension of Article 14.3 of the "Testing Rules" and this community's "compensation prohibition" for Testers;

  4. Use delaying tactics such as "Give me a few more minutes to clean up" to circumvent the fixation of the current client state;

  5. Distribute audio, video, or screenshots of the client check process for commercial use, or edit and release them before finalization.

4.3 Behavioral Requirements for Investigators (Aligning with USS Constraints)

This community also imposes constraints on its own users (especially Testers/Admins) to comply with USS internal guidelines:

  1. No Interference: Do not prompt, pressure, or guide investigators to specific conclusions; do not imply a biased conclusion by using the "I am an Admin" status;

  2. No @mentioning, No mobbing: In USS KOOKs, do not arbitrarily @Owner or @investigator team members; use the USS ticket system for inquiries;

  3. No Speaking on Behalf of Investigators: Do not repeat, extract, or "summarize" the personal opinions of investigators in public channels of this community—especially undisclosed internal judgments of USS;

  4. No Linking of Personal Data: Consistent with USS rules, it is strictly prohibited to publicly associate investigators with their real-world identity, school, workplace, or social media accounts, without exceptions;

  5. No Discussion of Cheating Details: In accordance with USS... The rules remain consistent: Discussions of topics such as "how to bypass terminal checks" and "how to prevent cheats from being detected by Echo" will not be held in the public channels of this community. For anti-cheat research needs, please submit a private bug report to the Admin.

  6. No False Reports: Terminal check reports initiated by SS-Requesters must be based on describable facts and evidence. Reports based on personal dissatisfaction with players are prohibited.

Chapter 5 Terminal Check Results and Tier Testing Processing

5.1 Result Classification

After a USS terminal check is completed, the results will be reported to the SS-Requester (the community Admin) via a bug report. Only the results and key evidence will be reported; personal data will not be disclosed. This community standardizes it into the following five levels:

| Code | Meaning | Impact on the test |

| --- | --- | --- |

| PASS | Passed, no violations | Finalized according to normal process |

| PASS_WITH_NOTE | Passed, minor flaws exist (such as insignificant historical traces) but do not affect the conclusion | Normal finalization, notes archived |

| INCONCLUSIVE | Due to network, client status, player cooperation, etc., a definitive conclusion cannot be issued | This test cancel, players will be handled according to the cancel cooldown rules in "Test Rules" 2.4 |

| FAIL_WARNING | Accumulated warnings caused the client check to fail, but there is no clear evidence of cheating | This test must not be finalized to LT3 or above; the client check must pass before testing LT3 or above again within 90 days |

| FAIL_SEVERE | Confirmed or highly suspected of serious violations such as cheating, modified client, auxiliary tools, etc. | This test For null / cancel, players will be handled according to Chapters 3.1/7 of the Community Guidelines, in principle permanently banned from Tier or "permanently banned + revoked of all ratings" |

5.2 Evidence Retention

  • This community retains the result code + conclusion summary from USS, but does not retain the original remote recording;

  • USS retains process evidence according to its own standards. This community may request targeted access from USS (through a USS support ticket) when necessary for appeals;

  • The retention period is consistent with the retention period for test files in the Privacy Policy;

  • Not publicly disclosed: Recordings of the terminal checking process, the identity of the terminal checking personnel, and details of the system traces of the players involved. Public files will only present neutral statements such as "Terminal checking passed" or "Failed due to compliance issues".

5.3 Withdrawal, Correction, and Remedies for Misjudgments

  • If a player believes the USS result is misjudged, they can submit a tier-appeal ticket through this community.

  • The community Admin will forward the appeal to USS for review and will make a final decision after receiving feedback from USS.

  • USS's technical conclusions have priority in the tiering process, and this community will not overturn their conclusions based on "Tester's personal opinion" or "player's popularity."

  • However, this community reserves the right to invalidate the tiering process based on compliance (e.g., the tiering itself violates the "Admin-only" rule in Article 2.4, or the SS-Requester's motive is proven to be retaliation). Such invalidation does not negate the USS's technical conclusions, but only means that this community does not accept them.

5.4 Relationship with bad_call_count

  • If a tester knowingly awards a high score to a client with questionable behavior without requesting a callback, and the score is subsequently nulled, this event is recorded in the tester's bad_call_count.

  • If a tester proactively requests a callback during the review phase, and the callback is ultimately confirmed as FAIL_*, the tester's bad_call_count is unaffected, and is instead recorded as a positive indicator in their performance review file.

  • The above exclusion from bad_call_count is contingent on the tester's request being reviewed by the Admin and deemed "not motivated by personal interests and based on reasonable evidence."

Chapter Six: Privacy and Data Boundaries

6.1 Minimal Data Flow

The data exchanged between this community and USS for a single endpoint lookup is limited to:

  1. Player Side: MC username, UUID, test ID, expected endpoint lookup window, and the KOOK ID designated by the community's Admin;

  2. USS Side: Endpoint lookup result code, conclusion summary, and necessary Warning/Severe fact descriptions;

  3. Not Exchanged: Player's email address, ID card number, address, payment information, device hardware serial number, original chat log, and original video recording file.

6.2 Player Protection

  • Any irrelevant information that players actively display during remote access (such as desktop wallpaper, other game accounts, private windows) should not be recorded, intercepted, or disseminated by USS endpoint checkers—USS ​​internal guidelines have already made similar constraints, and this community is consistent with them;

  • Players have the right to request a pause once before starting endpoint checks to lock the screen, close irrelevant windows, and pause notifications—but this pause must not be used to close Minecraft or affect the client state;

  • Guardians of underage players have the right to request through this community support ticket to "not trigger the finalize option for endpoint checks." Such requests will be handled by Admins in accordance with the spirit of Article 6.1 of the Community Guidelines, and will usually guide players to the maximum endpoint level that does not require endpoint checks (for A-level and below, manual adjustment is recommended).

6.3 Protection of Security Investigators

  • This community strictly prohibits any user (including staff) from publicly disclosing the real identity, real name, school, workplace, family situation, or other social media accounts of security investigators;

  • All complaints against security investigators must be submitted via USS support tickets (or the complaint email address announced by USS, historically smfsheng@email.cn, subject to the current announcement), and it is strictly forbidden to condemn, publicly name, or stir up trouble in the community's public channels;

  • Users who violate 6.3 will be dealt with according to Article 3.4 "Privacy Infringement" of the Community Guidelines, with serious violations resulting in permanent account bans.

6.4 Cross-Community Extradition

  • If a player is penalized with a [Severe] or Blacklist in the USS, their corresponding rating action in this community will be taken concurrently.

  • If a player is penalized with a "severe" violation in this community (e.g., account boosting, pre-selected ratings), this community will, at its discretion, report the facts to the USS according to the supplementary measures outlined in Section 7.3 of the Community Guidelines, but will not make a penalty decision on behalf of the USS. The USS will decide whether to coordinate with this community based on its own regulations.

  • Cross-community reports are limited to "facts + this community's penalty decision + the clause number on which the judgment was based," excluding PII.

Chapter Seven Appeals

7.1 Player Appeals

  • If a player disagrees with the endpoint verification result, they can submit a tier-appeal ticket to this community, specifying "Appeal against endpoint verification result";

  • The ticket must include at least:

  • The test ID corresponding to this endpoint verification;

  • The identified Warning/Severe clause;

  • The player's own statement of facts and evidence (if they can export system logs, installation record screenshots, etc.);

  • The community Admin will forward it to USS for review;

  • During the review period, the original processing (null / cancel / file size limit compression) will not be suspended, unless explicitly suspended by the Admin.

7.2 Review by the Community Admin

The Community Admin may not forward the appeal to USS and automatically void the current endpoint check in the following situations:

  1. The endpoint check ticket was initiated by someone other than an Admin (violation 2.4);

  2. The SS-Requester was found to have a clear personal motive (violation 4.3.6);

  3. The player was not adequately informed of the upcoming endpoint check beforehand (violation 3.1);

  4. The remote tool was not included in the current USS announcement (violation 3.3).

In these cases:

  • The Community will not accept the results of this endpoint check and will not adjust the test status accordingly;

  • It will be recorded as a procedural flaw in the Community's internal archives;

  • However, the Community does not deny the technical conclusions of the USS endpoint check personnel. Any penalties imposed by USS will be decided by USS, and the Community will not coordinate with them.

7.3 Exemption from Presumption of Guilt

This community will not presume guilt on players who have not completed a client check. Before a client check is initiated, the test will still be treated as if it has not been checked (e.g., it can be finalized at HT4, but not at LT3 or higher). If a player is unable to complete the client check within a reasonable timeframe for any reason, the Admin should provide a reasonable waiting period of at least 72 hours before deciding whether to cancel.

Chapter 8 Relationship with Other Documents

8.1 Priority

Regarding the process, violation identification, and penalties for patent tracing itself, the order is as follows (the former takes precedence):

  1. USS Community Guidelines + Patent Tracing Application Instructions + Basic Principle + Core Principles + RedLotus Specification Manual + RBW ScreenShare Code Chapter IV (external, but a prerequisite for cooperation);

  2. This Patent Tracing Rule;

  3. References related to patching in this community's Testing Rules;

  4. This community's Community Code of Conduct;

  5. Terms of Service and Privacy Policy.

In the event of a conflict between item 1 (USS rules) and item 2 (this rule), the stricter USS rule shall prevail, and a PR shall be submitted by the community Admin to revise this document in the next version to resolve the conflict.

8.2 External Rules Explicitly Referenced in this Rule

  • USS Community Guidelines (text available in USS KOOK #✧ ⋆ "Channel Rules" ⋆ ✧);

  • USS Access Control Request Guidelines (text available in USS KOOK —— "Access Control Request" ——);

  • USS Basic Principles (text available in USS KOOK #✞ ₊ ⌞ FAQ ⌝₊˚ ✞);

  • USS Core Principles (Full Recording / Privacy and Security Above All / Anti-Bias Operating Procedures);

  • Discord Ranked Bedwars "ScreenShare Code of RBW" Chapter IV – Penalties (original attachment provided by USS);

  • KOOK Community Rules (https://www.kookapp.cn/community-rules.html).

If any external rule is changed, the community Admin must revise this document or release a patch note within 7 calendar days to avoid misleading players.

Chapter Nine Implementation, Changes, and Contact Information

9.1 Implementation

  • This rule applies to all endpoint query requests initiated after the effective date.

  • Tests that entered the Tier process before the effective date but have not yet been finalized, and which trigger endpoint queries, will be executed according to this rule.

  • This rule will not be retroactive for historical tests that have been finalized and are not currently in the insurance period.

9.2 Changes

  • Major changes (triggering conditions, penalty linkage, privacy boundaries, USS-side rule updates) must be announced in this community and sent via in-app message 7 calendar days in advance, and the USS management team must be notified simultaneously.

  • Minor changes (text revisions, link updates, USS personnel role name adjustments)(Complete) This can be updated directly; the version number/patch information will be displayed in the footer of this document.

  • Any changes must not increase the obligations of players in the ongoing client verification process (i.e., not retroactively aggravate them).

9.3 Contact Information

| Scenarios | Channels |

| --- | --- |

| Community-side support, initiating terminal lookup, and appeals | /me/tickets/new → tier-appeal / Regular ticket |

| USS-side complaints about the behavior of terminal lookup personnel | Email address for announcements in the USS channel (currently based on smfsheng@email.cn, with the latest USS announcement) |

| Cooperation matters (rule conflicts, process changes, cross-community notifications) | This community's info@cnboxing.net, handled by the Admin and USS Owner |

| Emergency events (device malfunctions during terminal lookup, suspected player self-harm tendencies, protection of minors) | help@cnboxing.net or @ this community's Admin in the KOOK group |

9.4 Acknowledgements

This community sincerely thanks Undefined SS Community for providing us with terminal lookup support free of charge. We will use this cooperation channel cautiously, ensuring it does not increase the burden on USS, respects USS guidelines, and protects USS endpoint inspectors. The fairness of Tier ratings and the legitimacy of the Minecraft client are in the common interest of all users in the community, and we look forward to a long-term and healthy cooperation between the two parties.

Last Updated: April 22, 2026

Version: v1.0

This rule was written by this community and drafted based on the currently published USS rules. If USS believes that any statement in this document is inconsistent with its guidelines, USS's feedback shall prevail, and this community will revise it immediately.

No rule sections published yet.

Last updated 6/17/2026, 10:05:11 PM