> For the complete documentation index, see [llms.txt](https://alphadevhub.gitbook.io/alpha-roleplay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alphadevhub.gitbook.io/alpha-roleplay/rules/article-xviii-anti-exploit-anti-cheat-and-system-integrity.md).

# ARTICLE XVIII — ANTI-EXPLOIT, ANTI-CHEAT, AND SYSTEM INTEGRITY

## **ARTICLE XVIII — ANTI-EXPLOIT, ANTI-CHEAT, AND SYSTEM INTEGRITY**

#### **Preamble**

Dominion RP relies on **fair gameplay, realistic RP, and server integrity**.\
This article defines rules for preventing, detecting, and addressing **exploits, cheats, and system abuse**, ensuring all players experience a balanced and immersive environment.

***

### **Section 18.1 — Exploit Prevention**

#### **18.1.1 — What Constitutes an Exploit**

Exploits are actions that manipulate game mechanics, scripts, or systems for **unfair advantage**, including:

1. Inventory duplication or unlimited item generation
2. Teleporting or clipping through world geometry
3. Vehicle or property spawning not IC justified
4. Script or client-side manipulation to bypass RP rules

**Scenario Example:**

* ✅ *Correct:* Player finds a minor glitch and reports it to staff without using it.
* ❌ *FailRP:* Player duplicates weapons using a bug to gain an IC advantage.

***

#### **18.1.2 — Third-Party Software**

1. Use of unauthorized software to alter gameplay, detect player positions, or automate actions is strictly prohibited.
2. Allowed software includes:
   * Visual-only mods (reshades, graphics enhancements)
   * Controllers for driving/flying only
3. Prohibited software includes:
   * Aimbots or trigger systems
   * ESP (enemy/player detection) tools
   * Auto-loot or inventory automation

***

#### **18.1.3 — Bug Reporting**

1. Players must **report bugs or exploits immediately** to staff.
2. Evidence should include:
   * Screenshots or clips
   * Clear description of how the bug was discovered
   * Time and location in-game
3. Exploiting before reporting is considered **FailRP and punishable**.

***

### **Section 18.2 — Inventory and Item Integrity**

#### **18.2.1 — Prohibited Actions**

1. Duping, glitching, or creating items outside the intended systems is prohibited.
2. Donation-exclusive or restricted items may not be stolen or manipulated.
3. Unrealistic inventory stacking, invisible items, or bypassing carry limits is prohibited.

**Scenario Example:**

* ✅ *Correct:* Player reports a vehicle spawn bug affecting inventory storage.
* ❌ *FailRP:* Player uses the bug to spawn multiple vehicles and sell them IC.

***

#### **18.2.2 — Inventory Enforcement**

1. Staff may remove items obtained through exploits.
2. Players found abusing inventory systems may receive:
   * Temporary freeze of assets
   * Cooldown extension
   * Permanent confiscation or ban

***

### **Section 18.3 — Vehicle and Property Integrity**

#### **18.3.1 — Vehicle Use**

1. Vehicles must be **spawned, stored, and maintained IC**.
2. Prohibited actions:
   * Teleporting vehicles for IC advantage
   * Instant repairs or unrealistically high performance
   * Abusing vehicle mechanics in police chases or combat

#### **18.3.2 — Property Use**

1. Property ownership and use must reflect **IC acquisition and investment**.
2. Glitching into properties or accessing restricted zones is prohibited.

**Scenario Example:**

* ✅ *Correct:* Player buys a warehouse IC, stores items, and secures it realistically.
* ❌ *FailRP:* Player spawns inside another faction’s property to steal items or bypass security.

***

### **Section 18.4 — Combat and Weapon System Integrity**

1. Weapons must be used realistically:
   * Proper handling, ammo limits, and storage
   * Concealment rules must be followed
   * Donation or restricted weapons cannot be exploited
2. Combat exploits include:
   * Infinite ammo or health
   * Teleporting to avoid damage
   * Ignoring weapon cooldowns

**Scenario Example:**

* ✅ *Correct:* Player reloads IC and roleplays ammo limits during a firefight.
* ❌ *FailRP:* Player bypasses reload, gaining an unfair advantage against other players.

***

### **Section 18.5 — Detection and Enforcement**

#### **18.5.1 — Staff Monitoring**

1. Staff monitor server activity for unusual patterns or exploit use.
2. Logs, reports, and player evidence are reviewed before action.

#### **18.5.2 — Penalties**

1. Minor violations: warnings or scene correction
2. Moderate violations: asset removal, temporary suspension, restricted IC activity
3. Severe violations: permanent ban, removal of faction/business assets, or reset of inventory

***

#### **Section 18.6 — Player Responsibilities**

1. Players must maintain **ethical behavior** in all interactions:
   * Report bugs and exploits promptly
   * Avoid sharing exploit methods with others
   * Follow IC procedures and realistic constraints
2. Players found aiding others in exploits may face the same consequences as the primary offender.

***

#### **Section 18.7 — Appeals and Dispute Resolution**

1. Appeals must be submitted **within 7 days** of enforcement.
2. Evidence must include:
   * IC/OOC context
   * Screenshots, clips, or logs
3. Staff will review appeals objectively, ensuring fairness and rule compliance.

***

#### **Closing Statement for Article XVIII**

Maintaining anti-exploit, anti-cheat, and system integrity is critical to Dominion **RP’s balance, realism, and fairness**.\
All players are expected to respect game systems, report issues, and roleplay realistically.\
FailRP, abuse, or exploitation will be addressed strictly to preserve a secure, immersive, and equitable environment for all players.