Anti Block Glitch 1.0.3

Prevents players from glitching up walls with blocks

  1. Icefox922
    Native Minecraft Version:
    Tested Minecraft Versions:
    • 1.16
    Source Code:
    Are you tired of having your players get to places they aren't supposed to? Sometimes, players will use their high cps to exploit slight server lag and scale walls protected by World Guard.

    This plugin is very simple: if the player places a block in a World Guard region that they do not have permission to build in, it teleports them to the last block they were standing on. With this, it is virtually impossible to block-glitch up walls or cheat in parkour courses. You can think of it as induced lag-back to prevent players from cheating.

    If you do not have WorldGuard installed or the desired region does not have the build or block-place WorldGuard flags denied, players will be allowed to block glitch, as they are allowed by Worldguard to build!

    There is only one permission for this plugin
    antiblockglitch.override: Allows player to bypass anti block glitch

    If you have any bug reports or feature requests, please submit on the GitHub page above.

Recent Updates

  1. Global Region Support
  2. Plugin Name Fix
  3. Anti Block Glitch v1.0.1

Recent Reviews

  1. OneHitX
    Version: 1.0.1
    [15:01:32 ERROR]: Could not pass event PlayerQuitEvent to SnociStreams v1.0
    java.lang.NullPointerException: null
    at me.Ice.antiblockglitch.BlockChecker.cancelBlockChecker( ~[?:?]
    at me.Ice.antiblockglitch.CheckerHandler.onQuit( ~[?:?]
    at com.destroystokyo.paper.event.executor.asm.generated.GeneratedEventExecutor712.execute(Unknown Source) ~[?:?]
    at org.bukkit.plugin.EventExecutor.lambda$create$1( ~[patched_1.16.5.jar:git-Tuinity-"7734ef0"]
    at co.aikar.timings.TimedEventExecutor.execute( ~[patched_1.16.5.jar:git-Tuinity-"7734ef0"]
    at org.bukkit.plugin.RegisteredListener.callEvent( ~[patched_1.16.5.jar:git-Tuinity-"7734ef0"]
    at org.bukkit.plugin.SimplePluginManager.callEvent( ~[patched_1.16.5.jar:git-Tuinity-"7734ef0"]
    at net.minecraft.server.v1_16_R3.PlayerList.disconnect( ~[patched_1.16.5.jar:git-Tuinity-"7734ef0"]
    at net.minecraft.server.v1_16_R3.PlayerConnection.a( ~[patched_1.16.5.jar:git-Tuinity-"7734ef0"]
    at net.minecraft.server.v1_16_R3.NetworkManager.handleDisconnection( ~[patched_1.16.5.jar:git-Tuinity-"7734ef0"]
    at net.minecraft.server.v1_16_R3.ServerConnection.c( ~[patched_1.16.5.jar:git-Tuinity-"7734ef0"]
    at net.minecraft.server.v1_16_R3.MinecraftServer.b( ~[patched_1.16.5.jar:git-Tuinity-"7734ef0"]
    at net.minecraft.server.v1_16_R3.DedicatedServer.b( ~[patched_1.16.5.jar:git-Tuinity-"7734ef0"]
    at net.minecraft.server.v1_16_R3.MinecraftServer.a( ~[patched_1.16.5.jar:git-Tuinity-"7734ef0"]
    at net.minecraft.server.v1_16_R3.MinecraftServer.w( ~[patched_1.16.5.jar:git-Tuinity-"7734ef0"]
    at net.minecraft.server.v1_16_R3.MinecraftServer.lambda$a$0( ~[patched_1.16.5.jar:git-Tuinity-"7734ef0"]
    at [?:?]

    pls fix
    1. Icefox922
      Author's Response
      Are you using the newest version? This exception is fixed in v1.0.1. If you are using the /reload command this will also happen. If so, I recommend never using /reload. A lot of plugins will break with the use of this command.