ModsJava
ToxicsAC
Java mod listed for Minecraft 26.x. Downloads from the MC Java Mods app on Android.
⬇ Download on SpigotToxicsAC
Evidence-based anti-cheat built for real server investigations.
Minecraft 26.2–26.3 • Paper / Purpur • PacketEvents
Official Downloads — Choose Your Minecraft Version
IMPORTANT: The main Spigot download is for Minecraft 26.3.
ToxicsAC v0.11.0-beta uses separate JARs for each Minecraft version. Install only the build matching your server. Do not install both JARs together.
Minecraft 26.2 — Paper / Purpur
Download ToxicsAC v0.11.0-beta for 26.2
Minecraft 26.3 — Paper / Purpur
Download ToxicsAC v0.11.0-beta for 26.3
View the official v0.11.0-beta release
All official releases
Required: PacketEvents 2.14.0 or a compatible newer version. Java 26 is listed in the current requirements. Both Minecraft builds should be tested on your server before enabling punishments.
What is ToxicsAC?
ToxicsAC is a modern Minecraft anti-cheat designed to detect suspicious player behaviour while giving server staff useful information to investigate potential cheating.
Instead of treating every individual alert as definitive proof, ToxicsAC tracks violations, evidence and detection confidence over time.
What's new in v0.11.0-beta?
This release improves compatibility clarity and internal stability. We apologize for the earlier confusion over which JAR belongs to Minecraft 26.2 or 26.3.
Guardian and Shadow Verification are planned for future updates; they are not included in v0.11.0-beta.
Features
Screenshots
View attachment 981977
View attachment 981978
View attachment 981979
Packet Movement Engine
ToxicsAC uses a packet-based foundation for its core movement checks.
Position-changing movement packets are captured through PacketEvents and converted into ordered movement samples. These samples are then safely evaluated on the main server thread, where ToxicsAC can access server-side blocks, collisions, player states and configuration.
The packet movement engine currently powers:
The engine includes several safety systems:
This is the foundation for more advanced movement prediction in future updates. ToxicsAC does not currently claim to provide complete Minecraft client simulation.
Detection Profiles
ToxicsAC includes three global detection profiles.
Lenient
Prioritizes avoiding false positives. Recommended for servers with unusual movement mechanics, custom items or heavily modified gameplay.
Balanced
The recommended default profile. Provides a balance between reliable detection and false-positive protection.
Strict
Accumulates evidence more quickly. This profile should only be used after extensive testing with your server's plugins and gameplay mechanics.
Change the profile in-game using:
Changing the profile does not delete existing player evidence.
Detection Checks
ToxicsAC includes a growing collection of checks covering movement, combat, packets, inventory actions and world interactions.
Movement
Combat
Packets
World and Interaction
Detection systems are continuously being tested and improved as ToxicsAC develops.
FastBreak Improvements
FastBreak tracks mining progress over server ticks using the actual block-breaking speed for the player. This accounts for tools, enchantments, potion effects, water and airborne conditions, including changes during mining.
Instant breaks and breaks without a matching mining session are skipped. Java and Bedrock have separate configurable tick tolerances to allow for event and packet timing.
The older minimum-interval settings are no longer used. Configure the new values with:
FastConsume Improvements
FastConsume accounts for different consumption speeds instead of treating every consumable as having the same duration.
Normal food uses the configured default duration, while faster items such as Dried Kelp can use their correct shorter timing. Server owners can also configure per-item overrides for custom foods, plugin-created items and unusual gameplay mechanics.
Separate Java and Bedrock timing tolerances are available to help account for network and crossplay differences.
FastConsume evidence can include the consumed item, expected duration, observed duration, timing difference, tolerance and player ping. Like the rest of ToxicsAC, FastConsume uses accumulated evidence rather than treating one unusual action as definitive proof.
Evidence and Confidence System
ToxicsAC is designed around accumulated evidence rather than assuming that every individual alert proves a player is cheating.
Checks can build evidence across multiple suspicious actions. Evidence must reach the configured threshold before it becomes a recorded violation.
This helps staff distinguish repeated suspicious behaviour from occasional unusual movement caused by latency, server performance, packet delays, crossplay differences or other plugins.
ToxicsAC also considers recent failed checks when calculating a player's overall detection confidence. Fully decayed checks and checks older than the configurable corroboration window no longer count toward the distinct-check punishment requirement. The default window is five minutes.
Confidence is an evidence score, not a measured probability that a player is cheating. It should assist staff investigations and should not automatically be treated as absolute proof.
Staff can review accumulated evidence, violations and saved history directly through ToxicsAC.
Test Mode
New installations start with test mode enabled:
While test mode is enabled, ToxicsAC continues to:
Test mode prevents configured automatic punishment commands and automatic setbacks from being executed.
Setbacks also have their own enable setting and remain disabled by default. Disabling test mode does not automatically enable setbacks.
It is strongly recommended to keep test mode enabled while testing ToxicsAC with your server's plugins and gameplay mechanics.
Staff Investigation GUI
Use:
to open the ToxicsAC investigation panel.
The main panel displays:
From the investigation GUI, staff can:
The player list supports multiple pages, making the investigation GUI suitable for larger servers. Inventory inspection captures cloned items when opened; it does not allow staff to move items, and must be reopened to refresh the snapshot.
Staff Alerts
Staff members can receive real-time alerts when ToxicsAC detects suspicious behaviour.
Use:
to toggle normal anti-cheat alerts.
For additional detection information, use:
Verbose mode displays detailed evidence information and is useful when investigating players, testing checks or diagnosing false positives.
Commands
Main command:
Aliases:
/ac help
Displays the available ToxicsAC commands.
/ac alerts
Toggles normal anti-cheat alerts.
/ac verbose
Toggles detailed detection evidence.
/ac gui
Opens the staff investigation GUI.
/ac info <player>
Displays current anti-cheat information, violations and evidence for a player.
/ac history <player>
Displays saved violation history for a player.
/ac exempt <player>
Adds or removes a player's persistent anti-cheat exemption.
/ac reset <player>
Clears the player's current-session evidence.
/ac dismiss <player>
Dismisses a false-positive investigation while preserving saved audit logs.
/ac profile
Displays the current detection profile.
/ac profile lenient|balanced|strict
Changes the global detection profile.
/ac punishments
Displays the current punishment settings.
/ac punishments on
Enables automatic punishments for eligible Java players and disables test mode.
/ac punishments off
Disables automatic punishments while leaving detection and alerts active.
/ac punishments bedrock-on
Separately enables automatic punishments for Bedrock players.
/ac punishments bedrock-off
Disables automatic punishments for Bedrock players.
/ac status
Displays the current version, test mode, detection profile, TPS, packet-engine status and packet queue size.
/ac reload
Reloads the ToxicsAC configuration and packet-engine settings.
Permissions
toxicsac.admin
Provides access to administrative ToxicsAC commands.
Default: OP
toxicsac.alerts
Allows staff to receive ToxicsAC detection alerts.
Default: OP
toxicsac.update
Notifies the player when a newer version of ToxicsAC is available.
Default: OP
toxicsac.bypass
Bypasses all ToxicsAC checks for the player.
Default: false
Individual check bypasses
Use:
For example:
These bypass only the named check. Use your permissions manager to grant the permissions you need.
Default: false
Punishments
ToxicsAC includes configurable automatic punishment functionality.
Before a configured punishment command can execute, the player must meet the configured requirements, including:
Automatic punishment requires both:
Bedrock automatic punishment is controlled separately and remains disabled unless explicitly enabled.
For new installations and beta updates, it is strongly recommended to monitor alerts and verbose evidence before enabling automatic punishments.
Player Exemptions and Bypasses
Players can be exempted from anti-cheat processing when required.
This can be useful for trusted staff, administrators or situations where another plugin intentionally creates unusual player behaviour.
Persistent exemptions can be managed using:
ToxicsAC also supports permission-based bypasses.
bypasses all checks.
Individual check bypasses are available through:
Bypass permissions should only be given to trusted players or staff.
Crossplay Support
ToxicsAC is designed with Java and Bedrock crossplay environments in mind.
Java and Bedrock players can use separate detection settings and leniency values. Bedrock automatic punishments are also controlled separately for additional safety.
Floodgate integration is optional and can be used on servers that allow Bedrock players to connect through a compatible crossplay setup.
Floodgate is not required for Java-only servers.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Requirements
PacketEvents must be installed for ToxicsAC to load correctly.
Floodgate is only required if you want to use the relevant Bedrock crossplay integration.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Installation
1. Download the version-specific ToxicsAC JAR for your Minecraft server from the official links above.
2. Download and install PacketEvents.
3. Stop your Minecraft server.
4. Place ToxicsAC and PacketEvents inside your server's /plugins/ folder.
5. Start the server.
6. Allow ToxicsAC to generate or update its configuration and data files.
7. Run:
The status should display the packet engine as:
8. Keep the detection profile set to Balanced while beginning testing:
9. Enable detailed test information using:
If you are running a compatible Java and Bedrock crossplay environment, Floodgate can also be installed for the optional integration.
A full server restart is recommended when installing or updating ToxicsAC.
Avoid using plugin reload managers when updating the anti-cheat.
Updating ToxicsAC
When updating ToxicsAC:
1. Stop the server.
2. Back up the ToxicsAC configuration and data.
3. Remove the old ToxicsAC JAR.
4. Add the new ToxicsAC JAR matching your server version.
5. Confirm that the correct PacketEvents version is installed.
6. Start the server.
7. Check the console for errors.
8. Run:
9. Confirm that the packet engine displays as ONLINE.
Do not run multiple versions of ToxicsAC at the same time.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
False Positives and Bug Reports
No anti-cheat should be treated as infallible. Previous automated testing does not establish that both v0.11.0-beta builds have passed live-server validation.
Latency, server performance, unusual Minecraft mechanics, crossplay differences and other plugins can sometimes create behaviour that resembles cheating.
ToxicsAC is designed to provide staff with evidence and detection history to assist investigations rather than requiring moderators to rely on a single alert.
If you believe a detection is a false positive or a cheat is not being detected, please collect:
Good reproduction information makes detection issues significantly easier to investigate and fix.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✦ SERVERS PROTECTED BY TOXICSAC ✦
Want to see ToxicsAC running on a real server?
Check out communities currently using ToxicsAC in a live environment.
☾ MOONVALE ☽
PLAY NOW
play.moonvale.us
Stop by MoonVale, check out the community and see ToxicsAC running on a live server.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━
RUNNING TOXICSAC ON YOUR SERVER?
Using ToxicsAC and want your community featured here?
Get in touch and your server may be added to the showcase.
Beta Notice
ToxicsAC is currently in beta and is under active development.
The packet movement engine remains in beta, and 26.3 compatibility requires live server testing. False positives, missed detections, bugs and compatibility issues may still occur.
Server owners are encouraged to keep test mode enabled, monitor verbose evidence and configure punishments carefully before relying on automatic actions.
Feedback, testing results and false-positive reports are extremely useful while ToxicsAC continues to improve.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Compatibility
Currently targeted for:
Other Minecraft versions, server implementations or dependency versions may work but have not been validated here. Test 26.2 and 26.3 on your server before enabling punishments.
ToxicsAC
Evidence. Investigation. Better moderation.
Current Version: v0.11.0-beta
Evidence-based anti-cheat built for real server investigations.
Minecraft 26.2–26.3 • Paper / Purpur • PacketEvents
Official Downloads — Choose Your Minecraft Version
IMPORTANT: The main Spigot download is for Minecraft 26.3.
ToxicsAC v0.11.0-beta uses separate JARs for each Minecraft version. Install only the build matching your server. Do not install both JARs together.
Minecraft 26.2 — Paper / Purpur
Download ToxicsAC v0.11.0-beta for 26.2
Minecraft 26.3 — Paper / Purpur
Download ToxicsAC v0.11.0-beta for 26.3
View the official v0.11.0-beta release
All official releases
Required: PacketEvents 2.14.0 or a compatible newer version. Java 26 is listed in the current requirements. Both Minecraft builds should be tested on your server before enabling punishments.
What is ToxicsAC?
ToxicsAC is a modern Minecraft anti-cheat designed to detect suspicious player behaviour while giving server staff useful information to investigate potential cheating.
Instead of treating every individual alert as definitive proof, ToxicsAC tracks violations, evidence and detection confidence over time.
What's new in v0.11.0-beta?
This release improves compatibility clarity and internal stability. We apologize for the earlier confusion over which JAR belongs to Minecraft 26.2 or 26.3.
- Separate, clearly named JAR builds for Minecraft 26.2 and 26.3
- Version-specific build configurations and compatibility identification
- Improved thread safety in Timer packet processing
- Clearer evidence-score terminology: confidence is not a guaranteed probability of cheating
- Internal stability improvements in preparation for future detection work
Guardian and Shadow Verification are planned for future updates; they are not included in v0.11.0-beta.
Features
- Ordered PacketEvents movement processing
- Packet-derived Speed, Fly and NoFall detection
- Real-time anti-cheat monitoring
- Evidence-based detection system
- Detection confidence tracking
- Lenient, Balanced and Strict detection profiles
- Staff alerts
- Detailed verbose alerts
- Persistent violation and evidence history
- Online and retained offline suspect tracking
- Built-in staff investigation GUI
- Configurable automatic punishments
- Safe test mode for monitoring without automatic punishments or setbacks
- Player exemptions
- Global and individual check bypass permissions
- Teleport directly to suspicious players
- Spectate players during investigations
- Freeze players
- Inspect read-only player inventory snapshots
- Reset stored player evidence
- Dismiss false-positive investigations
- Administrator update notifications
- Crossplay-aware detection settings
- Packet queue and engine status information
- Bukkit movement fallback if the packet engine is disabled
- Reloadable configuration
- Actively developed
Screenshots
View attachment 981977
View attachment 981978
View attachment 981979
Packet Movement Engine
ToxicsAC uses a packet-based foundation for its core movement checks.
Position-changing movement packets are captured through PacketEvents and converted into ordered movement samples. These samples are then safely evaluated on the main server thread, where ToxicsAC can access server-side blocks, collisions, player states and configuration.
The packet movement engine currently powers:
- Speed
- Fly
- NoFall
The engine includes several safety systems:
- Bounded packet queue
- Maximum work processed per server tick
- Stale packet sample protection
- Server and packet position desynchronization protection
- Teleport history resets
- Join, velocity and teleport exemption periods
- Ping and TPS safety limits
- Automatic Bukkit fallback when the packet engine is disabled
This is the foundation for more advanced movement prediction in future updates. ToxicsAC does not currently claim to provide complete Minecraft client simulation.
Detection Profiles
ToxicsAC includes three global detection profiles.
Lenient
Prioritizes avoiding false positives. Recommended for servers with unusual movement mechanics, custom items or heavily modified gameplay.
Balanced
The recommended default profile. Provides a balance between reliable detection and false-positive protection.
Strict
Accumulates evidence more quickly. This profile should only be used after extensive testing with your server's plugins and gameplay mechanics.
Change the profile in-game using:
Code (Text):
/ac profile lenient
/ac profile balanced
/ac profile strict
/ac profile balanced
/ac profile strict
Detection Checks
ToxicsAC includes a growing collection of checks covering movement, combat, packets, inventory actions and world interactions.
Movement
- Speed
- Fly
- Step
- Glide / Elytra
- Jesus / Water Walk
- NoFall
- Velocity / Anti-Knockback
- Boat Fly
Combat
- KillAura
- Reach
- AutoClicker
- Criticals
Packets
- Timer
- BadPackets
World and Interaction
- Scaffold
- FastBreak
- FastPlace
- InventoryMove
- ChestStealer
- FastConsume
Detection systems are continuously being tested and improved as ToxicsAC develops.
FastBreak Improvements
FastBreak tracks mining progress over server ticks using the actual block-breaking speed for the player. This accounts for tools, enchantments, potion effects, water and airborne conditions, including changes during mining.
Instant breaks and breaks without a matching mining session are skipped. Java and Bedrock have separate configurable tick tolerances to allow for event and packet timing.
The older minimum-interval settings are no longer used. Configure the new values with:
Code (Text):
checks:
fastbreak:
java-tolerance-ticks: 2
bedrock-tolerance-ticks: 3
fastbreak:
java-tolerance-ticks: 2
bedrock-tolerance-ticks: 3
FastConsume accounts for different consumption speeds instead of treating every consumable as having the same duration.
Normal food uses the configured default duration, while faster items such as Dried Kelp can use their correct shorter timing. Server owners can also configure per-item overrides for custom foods, plugin-created items and unusual gameplay mechanics.
Separate Java and Bedrock timing tolerances are available to help account for network and crossplay differences.
FastConsume evidence can include the consumed item, expected duration, observed duration, timing difference, tolerance and player ping. Like the rest of ToxicsAC, FastConsume uses accumulated evidence rather than treating one unusual action as definitive proof.
Evidence and Confidence System
ToxicsAC is designed around accumulated evidence rather than assuming that every individual alert proves a player is cheating.
Checks can build evidence across multiple suspicious actions. Evidence must reach the configured threshold before it becomes a recorded violation.
This helps staff distinguish repeated suspicious behaviour from occasional unusual movement caused by latency, server performance, packet delays, crossplay differences or other plugins.
ToxicsAC also considers recent failed checks when calculating a player's overall detection confidence. Fully decayed checks and checks older than the configurable corroboration window no longer count toward the distinct-check punishment requirement. The default window is five minutes.
Confidence is an evidence score, not a measured probability that a player is cheating. It should assist staff investigations and should not automatically be treated as absolute proof.
Staff can review accumulated evidence, violations and saved history directly through ToxicsAC.
Test Mode
New installations start with test mode enabled:
Code (Text):
test-mode: true
- Run enabled detection checks
- Collect evidence
- Record violations
- Calculate confidence
- Send alerts
- Display verbose information
- Save violation history
- Display suspects in the staff GUI
Test mode prevents configured automatic punishment commands and automatic setbacks from being executed.
Setbacks also have their own enable setting and remain disabled by default. Disabling test mode does not automatically enable setbacks.
It is strongly recommended to keep test mode enabled while testing ToxicsAC with your server's plugins and gameplay mechanics.
Staff Investigation GUI
Use:
Code (Text):
/ac gui
The main panel displays:
- Current ToxicsAC version
- Test or active mode
- Current detection profile
- Packet-engine status
- Server TPS
- Punishment status
- Online suspects
- Retained offline suspects
From the investigation GUI, staff can:
- Review violations
- Review detection confidence
- View live evidence
- View saved violation history
- Teleport directly to a player
- Spectate a player
- Freeze or unfreeze a player
- Inspect a read-only snapshot of a player's inventory
- Add or remove exemptions
- Reset current-session evidence
- Dismiss false-positive investigations
The player list supports multiple pages, making the investigation GUI suitable for larger servers. Inventory inspection captures cloned items when opened; it does not allow staff to move items, and must be reopened to refresh the snapshot.
Staff Alerts
Staff members can receive real-time alerts when ToxicsAC detects suspicious behaviour.
Use:
Code (Text):
/ac alerts
For additional detection information, use:
Code (Text):
/ac verbose
Commands
Main command:
Code (Text):
/toxicsac
Code (Text):
/tac
/ac
/ac
Displays the available ToxicsAC commands.
/ac alerts
Toggles normal anti-cheat alerts.
/ac verbose
Toggles detailed detection evidence.
/ac gui
Opens the staff investigation GUI.
/ac info <player>
Displays current anti-cheat information, violations and evidence for a player.
/ac history <player>
Displays saved violation history for a player.
/ac exempt <player>
Adds or removes a player's persistent anti-cheat exemption.
/ac reset <player>
Clears the player's current-session evidence.
/ac dismiss <player>
Dismisses a false-positive investigation while preserving saved audit logs.
/ac profile
Displays the current detection profile.
/ac profile lenient|balanced|strict
Changes the global detection profile.
/ac punishments
Displays the current punishment settings.
/ac punishments on
Enables automatic punishments for eligible Java players and disables test mode.
/ac punishments off
Disables automatic punishments while leaving detection and alerts active.
/ac punishments bedrock-on
Separately enables automatic punishments for Bedrock players.
/ac punishments bedrock-off
Disables automatic punishments for Bedrock players.
/ac status
Displays the current version, test mode, detection profile, TPS, packet-engine status and packet queue size.
/ac reload
Reloads the ToxicsAC configuration and packet-engine settings.
Permissions
toxicsac.admin
Provides access to administrative ToxicsAC commands.
Default: OP
toxicsac.alerts
Allows staff to receive ToxicsAC detection alerts.
Default: OP
toxicsac.update
Notifies the player when a newer version of ToxicsAC is available.
Default: OP
toxicsac.bypass
Bypasses all ToxicsAC checks for the player.
Default: false
Individual check bypasses
Use:
Code (Text):
toxicsac.bypass.<check>
Code (Text):
toxicsac.bypass.fly
toxicsac.bypass.reach
toxicsac.bypass.reach
Default: false
Punishments
ToxicsAC includes configurable automatic punishment functionality.
Before a configured punishment command can execute, the player must meet the configured requirements, including:
- Minimum detection confidence
- Minimum total violation level
- Minimum number of recent, non-decayed distinct failed checks
- Punishment cooldown
Automatic punishment requires both:
Code (Text):
test-mode: false
punishments:
enabled: true
punishments:
enabled: true
For new installations and beta updates, it is strongly recommended to monitor alerts and verbose evidence before enabling automatic punishments.
Player Exemptions and Bypasses
Players can be exempted from anti-cheat processing when required.
This can be useful for trusted staff, administrators or situations where another plugin intentionally creates unusual player behaviour.
Persistent exemptions can be managed using:
Code (Text):
/ac exempt <player>
Code (Text):
toxicsac.bypass
Individual check bypasses are available through:
Code (Text):
toxicsac.bypass.<check>
Crossplay Support
ToxicsAC is designed with Java and Bedrock crossplay environments in mind.
Java and Bedrock players can use separate detection settings and leniency values. Bedrock automatic punishments are also controlled separately for additional safety.
Floodgate integration is optional and can be used on servers that allow Bedrock players to connect through a compatible crossplay setup.
Floodgate is not required for Java-only servers.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Requirements
- Minecraft 26.2 or 26.3 — use the matching version-specific v0.11.0-beta JAR and verify on your server
- Paper or Purpur
- Java 26
- PacketEvents 2.14.0 or a compatible newer release — REQUIRED
- Floodgate — OPTIONAL
PacketEvents must be installed for ToxicsAC to load correctly.
Floodgate is only required if you want to use the relevant Bedrock crossplay integration.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Installation
1. Download the version-specific ToxicsAC JAR for your Minecraft server from the official links above.
2. Download and install PacketEvents.
3. Stop your Minecraft server.
4. Place ToxicsAC and PacketEvents inside your server's /plugins/ folder.
5. Start the server.
6. Allow ToxicsAC to generate or update its configuration and data files.
7. Run:
Code (Text):
/ac status
Code (Text):
ONLINE
Code (Text):
/ac profile balanced
Code (Text):
/ac verbose
A full server restart is recommended when installing or updating ToxicsAC.
Avoid using plugin reload managers when updating the anti-cheat.
Updating ToxicsAC
When updating ToxicsAC:
1. Stop the server.
2. Back up the ToxicsAC configuration and data.
3. Remove the old ToxicsAC JAR.
4. Add the new ToxicsAC JAR matching your server version.
5. Confirm that the correct PacketEvents version is installed.
6. Start the server.
7. Check the console for errors.
8. Run:
Code (Text):
/ac status
Do not run multiple versions of ToxicsAC at the same time.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
False Positives and Bug Reports
No anti-cheat should be treated as infallible. Previous automated testing does not establish that both v0.11.0-beta builds have passed live-server validation.
Latency, server performance, unusual Minecraft mechanics, crossplay differences and other plugins can sometimes create behaviour that resembles cheating.
ToxicsAC is designed to provide staff with evidence and detection history to assist investigations rather than requiring moderators to rely on a single alert.
If you believe a detection is a false positive or a cheat is not being detected, please collect:
- ToxicsAC version
- Minecraft version
- Paper or Purpur version
- PacketEvents version
- Java or Bedrock client
- Detection profile
- Check that triggered or failed to trigger
- Exact alert or verbose message
- Player ping if known
- Server TPS if known
- What the player was doing
- Relevant plugins
- Relevant console errors
- Whether the issue can be reproduced
Good reproduction information makes detection issues significantly easier to investigate and fix.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✦ SERVERS PROTECTED BY TOXICSAC ✦
Want to see ToxicsAC running on a real server?
Check out communities currently using ToxicsAC in a live environment.
☾ MOONVALE ☽
PLAY NOW
play.moonvale.us
Stop by MoonVale, check out the community and see ToxicsAC running on a live server.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━
RUNNING TOXICSAC ON YOUR SERVER?
Using ToxicsAC and want your community featured here?
Get in touch and your server may be added to the showcase.
Beta Notice
ToxicsAC is currently in beta and is under active development.
The packet movement engine remains in beta, and 26.3 compatibility requires live server testing. False positives, missed detections, bugs and compatibility issues may still occur.
Server owners are encouraged to keep test mode enabled, monitor verbose evidence and configure punishments carefully before relying on automatic actions.
Feedback, testing results and false-positive reports are extremely useful while ToxicsAC continues to improve.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Compatibility
Currently targeted for:
- Minecraft 26.2 or 26.3 — use the matching version-specific v0.11.0-beta JAR and verify on your server
- Paper
- Purpur
- Java 26
- PacketEvents 2.14.0
Other Minecraft versions, server implementations or dependency versions may work but have not been validated here. Test 26.2 and 26.3 on your server before enabling punishments.
ToxicsAC
Evidence. Investigation. Better moderation.
Current Version: v0.11.0-beta
Quick facts
- Edition: Minecraft Java
- File type: .jar
- Minecraft versions listed: 26.2, 26.3
- How to install: Install the matching mod loader (Forge, Fabric or NeoForge) for your Minecraft version. → Download the .jar. → Put it in the .minecraft/mods folder and launch that loader profile.
- Where to get it: Opens on Spigot — not every file is mirrored on our own servers.
Install steps are the general flow for this file type — How to install Minecraft Java mods & modpacks walks through it step by step.
ToxicsAC is a free Minecraft Java mod. Compatible with Minecraft 26.2, 26.3. Downloaded 98 times (via Spigot). Download it and open it directly in the game.