Paradox AntiCheat now utilizes the 2.7.0-Beta server, 1.0.0-Beta server-net, 1.0.0-Beta server-admin and 2.1.0-Beta server-ui APIs, enhancing compatibility and performance for Minecraft Bedrock; both Realms and BDS environments.
Paradox AntiCheat is a high-performance anti-cheat system for Minecraft Bedrock. It is designed to detect and prevent cheating in both Realms and BDS environments, ensuring a fair gameplay experience for all players.
The name "Paradox" reflects our approach: a system that uses sophisticated algorithms and advanced detection techniques to outsmart cheaters in ways that might seem counterintuitive at first glance.
Paradox: A statement or situation that contradicts itself yet reveals truth.
Highly modular and customizable, Paradox AntiCheat allows developers to tailor detection and enforcement to their worlds’ specific needs. Whether you’re managing a public server or a private Realm, Paradox provides reliable protection against unfair play.
For full documentation and setup guides, visit the official documentation site.
Join the Paradox AntiCheat community on Discord for support. Our community is active and dedicated to providing help and assistance to game developers who use Paradox AntiCheat in their projects. We also welcome feedback and suggestions on how we can improve the tool.
When applying the pack to your world, make sure the addon is at the top of the behavior pack list and Beta APIs is enabled. This is to ensure all checks and systems work properly. The versioning system for Paradox goes as follows:
- The first number denotes the pack version. This will rarely change unless there have been major changes to the code.
- The second number denotes the major revision of the pack version. These particular changes mostly involve features being added or removed.
- The third number indicates the minor revision of the Pack. This evolves around bug fixes.
To install this anticheat to your realm/world, follow these steps:
- Install the
.mcpack. - Apply it to your world.
- Enable Beta APIs.
Once you have done this, the anticheat should be fully up and running.
-
Install Node.js (Latest LTS Automatically):
-
This project includes a setup script that installs:
- The latest nvm
- The latest Node.js LTS
- Sets LTS as your default Node version
-
From the project root, run the Linux setup script:
Make sure the script is executable:
./bin/setup-node-linux.shchmod +x ./bin/setup-node-linux.sh
-
This project includes a setup script that installs:
-
Install Project Dependencies:
- After Node.js is installed, run:
npm install
-
Install Node.js (Latest LTS Automatically):
-
This project includes a setup script that installs:
- The latest Node.js LTS (no nvm on Windows)
- Updates your PATH so Node and npm are available
-
From the project root, run the Windows setup script in PowerShell:
bin\setup-node-windows.ps1
-
This project includes a setup script that installs:
-
Install Project Dependencies:
- After Node.js is installed, run:
npm install
- Download and install VS Code from the official website.
- Alternatively, you can install it via your package manager. For example, on Debian-based systems:
sudo apt update sudo apt install code
- Open a terminal.
- Execute the following command to clone the repository:
git clone https://github.com/<your-github-username>/Paradox_AntiCheat.git - Navigate to the project directory:
cd Paradox_AntiCheat
- Run the following command to install the project dependencies:
npm i
- You can open the project in VS Code by running:
code .
- Fork the project repository: Click on the "Fork" button in the top-right corner of the repository page: Paradox_AntiCheat_Fork
- Clone the forked repository to your local machine:
git clone https://github.com/<your-github-username>/Paradox_AntiCheat.git - Navigate to the cloned project directory:
cd Paradox_AntiCheat - Install project dependencies:
npm install - Make changes to the project files.
- Save the files.
- Stage the changes to include all modifications:
git add . - Commit the changes with a meaningful commit message:
git commit -m "Your commit message here" - Push the committed changes to your forked repository on GitHub:
git push origin - Create a pull request to submit the changes to the original repository.