Scythe Anticheat is a Minecraft Bedrock anticheat for vanilla Realms and Servers. It utilizes the Scripting API to observe player behavior and check if such behaviors are possible in the vanilla game. Scythe is designed to be plug-and-play, so you just need to apply the pack to your world, upload it to your realm or server, and it should be up and ready.
To install this anticheat to your realm, you will need to download the .mcpack to your device, apply it to your realm/server (make sure that Scythe is at the top of the behavior packs list), and enable Beta APIs in world settings. Once you have done that, the anticheat should be fully up and running!
To assist with server moderation, Scythe comes pre-included with a variety of commands. The most important ones are !help, !notify, !stats.
By default, cheat alert notifications are not shown. To be able to see these notifications, run the command !notify. Running the command again toggles your notify state, so you will no longer be shown cheat notifications.
The !stats command allows you to get an overview of a player's history with Scythe. Information such as their current device, any flagged checks, and whether they have Scythe-Op status are shown. You can rountinely check player history to see what kind of hacks they are using on your realm or server.
For a full list of commands, you can run the !help command. This output a list of all Scythe commands, organized by category, which you can use. Along with the command names, the syntax of the command and a description is included to better allow you to understand how each command functions. For a more technical overview of a command, you can run !help with a command name as an argument.
Note
To be able to utilize most of these custom commands, you must have Scythe-Op. You can run /function op to gain the proper permissions to use the commands.
AutoClicker ->
(A) => Checks for high CPS.
AutoOffhand ->
(A) => Checks if a player equips an item in their offhand while moving.
(B) => Checks if a player equips an item in their offhand while using an item.
(C) => Checks if a player equips an item in their offhand while swinging their hand.
AutoTool ->
(A) => Checks if a player switches their slot right after they start breaking a block.
BadPackets ->
(1) => Checks for invalid player head rotations.
(2) => Checks if chat messages have abnormal message lengths.
(3) => Checks for self-hurt.
(4) => Checks for newline or carriage return characters in messages.
(5) => Checks if the player has an invalid max render distance.
FastUse ->
(A) => Checks for using/throwing items at a very fast rate.
InstaBreak ->
(A) => Checks if a player breaks an unbreakable block whilst in survival.
InvalidSprint ->
(A) => Checks for sprinting while having the blindness effect.
(C) => Checks for sprinting while sneaking.
(E) => Checks for sprinting while riding an entity.
(F) => Checks if a player sprints while they do not have enough hunger.
InventoryMods->
(B) => Check if a player switches the item they have selected in the inventory while moving.
Killaura ->
(A) => Checks for attacking while using an item.
(B) => Checks for no swing. (Instantly detects toolbox killaura)
(C) => Checks for multi-aura.
(D) => Checks for attacking while sleeping.
(E) => Checks for attacking while having a chest open.
Namespoof ->
(A) => Checks if a player's name is longer than 16 characters.
(B) => Checks for invalid characters in the player's name.
NoSlow ->
(A) => Checks for high movement speeds while using or eating an item.
Nuker ->
(A) => Checks if a player breaks more than 3 blocks in a single tick.
Reach ->
(A) => Checks if a player hits an entity farther than normally possible.
(B) => Checks if a player breaks a block farther than normally possible.
(C) => Checks if a player places a block farther than normally possible.
Spammer ->
(A) => Checks if a player sends a message while moving.
(B) => Checks if a player sends a message while swinging their hand.
(C) => Checks if a player sends a message while using an item.
(D) => Checks if a player sends a message while having a chest opened.
Scaffold ->
(A) => Check for tower-like behavior.
(B) => Checks for a flat X/Y rotations (e.g. 10, 20, 30).
(C) => Checks if a player places a block under them whilst looking upwards.
(D) => Checks for downwards scaffold.
(E) => Checks for placing blocks onto air or liquid tiles.
Q1: Does the AntiCheat auto-ban?
A1: Yes. Currently only the BadPackets[1], BadPackets[2], BadPackets[3], BadPackets[4], and BadPackets[5] checks autoban.
Q2: Is it customizable?
A2: Yes you can edit the config.js file to disable or change the settings of certain checks. A guide can be found here (Outdated)