Indefinite Ban Request - ragdale

Please Note: The TotalFreedom Forum has now been put into a read-only mode. Total Freedom has now closed down and will not be returning in any way, shape or form. It has been a pleasure to lead this community and I wish you all the best for your futures.
    1. Username, UUID, IP(s), and short ban reason for each offender. Format as follows:
      Code
      ragdale:  
uuid: 'f1bd02f4-4eef-4d77-b2bd-b3785e8414c7'  
ips:  
- 1.129.111.212  
reason: 'Crashing the server'
    2. What did they do?

    User utilised an exploit to crash the server - under the red herring guise that a machine he had built did it. He showed players a small machine which had a sign jokingly referring to it as a server crasher. Once the player he brought pressed the button, the server would crash. This happened on multiple occasions - and it turns out the machine is a red herring to cover up an exploit he is using.

    1. What indefinitely bannable offense does this fall under according to the guidance for sanctions?

    1a - attempts to harm the server

    1. Add logs and/or screenshots of the occurrence here, and tag any witnessing staff. Evidence of previous offenses that are not the direct cause of this request can also be added here.

    @"videogamesm12"#4 has in depth knowledge in regards to the exploit.

    Quote

    ![10:17:41] [Server thread/ERROR]: Could not pass event InventoryClickEvent to CrackShot v0.98.11java.lang.IllegalArgumentException: Invalid UUID string: ez        at java.util.UUID.fromString(UUID.java:215) ~[?:?]        at net.minecraft.server.v1_16_R3.ChatHoverable$b.a(SourceFile:134) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.ChatHoverable$EnumHoverAction.a(SourceFile:337) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.ChatHoverable.a(SourceFile:94) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.ChatModifier$ChatModifierSerializer.b(ChatModifier.java:292) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.ChatModifier$ChatModifierSerializer.deserialize(ChatModifier.java:263) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.ChatModifier$ChatModifierSerializer.deserialize(ChatModifier.java:243) ~[patched_1.16.5.jar:git-Paper-778]        at com.google.gson.internal.bind.TreeTypeAdapter.read(TreeTypeAdapter.java:69) ~[patched_1.16.5.jar:git-Paper-778]        at com.google.gson.Gson.fromJson(Gson.java:887) ~[patched_1.16.5.jar:git-Paper-778]        at com.google.gson.Gson.fromJson(Gson.java:952) ~[patched_1.16.5.jar:git-Paper-778]        at com.google.gson.internal.bind.TreeTypeAdapter$GsonContextImpl.deserialize(TreeTypeAdapter.java:162) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.IChatBaseComponent$ChatSerializer.deserialize(IChatBaseComponent.java:246) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.IChatBaseComponent$ChatSerializer.deserialize(IChatBaseComponent.java:109) ~[patched_1.16.5.jar:git-Paper-778]        at com.google.gson.internal.bind.TreeTypeAdapter.read(TreeTypeAdapter.java:69) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.ChatDeserializer.a(SourceFile:493) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.ChatDeserializer.a(SourceFile:517) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.IChatBaseComponent$ChatSerializer.a(IChatBaseComponent.java:370) ~[patched_1.16.5.jar:git-Paper-778]        at org.bukkit.craftbukkit.v1_16_R3.util.CraftChatMessage.fromJSON(CraftChatMessage.java:216) ~[patched_1.16.5.jar:git-Paper-778]        at org.bukkit.craftbukkit.v1_16_R3.util.CraftChatMessage.fromJSONOrNull(CraftChatMessage.java:222) ~[patched_1.16.5.jar:git-Paper-778]        at org.bukkit.craftbukkit.v1_16_R3.util.CraftChatMessage.fromJSONComponent(CraftChatMessage.java:308) ~[patched_1.16.5.jar:git-Paper-778]        at org.bukkit.craftbukkit.v1_16_R3.inventory.CraftMetaItem.getDisplayName(CraftMetaItem.java:875) ~[patched_1.16.5.jar:git-Paper-778]        at com.shampaggon.crackshot.CSDirector.itemIsSafe(CSDirector.java:4576) ~[?:?]        at com.shampaggon.crackshot.CSDirector.itemParentNode(CSDirector.java:3901) ~[?:?]        at com.shampaggon.crackshot.CSDirector.clickGun(CSDirector.java:3036) ~[?:?]        at com.destroystokyo.paper.event.executor.asm.generated.GeneratedEventExecutor205.execute(Unknown Source) ~[?:?]        at org.bukkit.plugin.EventExecutor.lambda$create$1(EventExecutor.java:69) ~[patched_1.16.5.jar:git-Paper-778]        at co.aikar.timings.TimedEventExecutor.execute(TimedEventExecutor.java:80) ~[patched_1.16.5.jar:git-Paper-778]        at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:70) ~[patched_1.16.5.jar:git-Paper-778]        at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:624) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.PlayerConnection.a(PlayerConnection.java:2715) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.PacketPlayInWindowClick.a(SourceFile:32) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.PacketPlayInWindowClick.a(SourceFile:10) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.PlayerConnectionUtils.lambda$ensureMainThread$1(PlayerConnectionUtils.java:35) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.TickTask.run(SourceFile:18) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.IAsyncTaskHandler.executeTask(IAsyncTaskHandler.java:136) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.IAsyncTaskHandlerReentrant.executeTask(SourceFile:23) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.IAsyncTaskHandler.executeNext(IAsyncTaskHandler.java:109) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.MinecraftServer.bb(MinecraftServer.java:1266) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.MinecraftServer.executeNext(MinecraftServer.java:1259) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.IAsyncTaskHandler.awaitTasks(IAsyncTaskHandler.java:119) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.MinecraftServer.sleepForTick(MinecraftServer.java:1220) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.MinecraftServer.w(MinecraftServer.java:1134) ~[patched_1.16.5.jar:git-Paper-778]        at net.minecraft.server.v1_16_R3.MinecraftServer.lambda$a$0(MinecraftServer.java:291) ~[patched_1.16.5.jar:git-Paper-778]        at java.lang.Thread.run(Thread.java:829) [?:?] 

    This is the evidence that's pushing us over the line for this request - I'm not knowledgeable on the exploit myself.

    1. Are they known under any other names or IPs, and if so, are they currently (indefinitely) banned under those names and IPs? This information is used to keep track of ban bypassers.

    No.

    Patrolling the Mojave almost makes you wish for a nuclear winter.

    Quote

    ↩ @'r00t' well then what’s the point of posting it

    The thread is linked so admins are made familiar with the exploit. Many admins are not well-versed in exploits and their usage, so by documenting them, admins can learn how to combat them without having to constantly rely on people like Video, Panther and I to check them, especially useful for when we're not around. It is also quite obvious why these types of things would not be posted in public threads, especially since the documentation often shows full NBT for these items.

    javaw_VqNRNZdU6Q.png
    image.png
    image.png