Long-Term Ban Request - 2sKq

Status
Not open for further replies.

videogamesm12

Well-known member
Developer
Senior Admin
217
IGN
videogamesm12
1. Username, UUID, IP(s), and short ban reason for each offender.

2. What did they do?
This user placed a player head containing this exploit near spawn that crashed players who attempted to load it, creating basically a literal crash chunk. The evidence for this request was gathered while I was attempting to document the exploit, and proved to be very helpful.

3. What indefinitely bannable offense does this fall under according to the community guidelines?
Rule #7

4. 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.
Excerpt of a crash log caused by game the attempting to render the head:
Code:
---- Minecraft Crash Report ----
// You should try our sister game, Minceraft!

Time: 2024-04-15 11:36:19
Description: Rendering Block Entity

java.lang.IllegalArgumentException: Invalid URL 'real crash working 2024' go report this issue at discord.gg/[redacted]    
'
    at com.mojang.authlib.yggdrasil.TextureUrlChecker.isAllowedTextureDomain(TextureUrlChecker.java:33)
    at com.mojang.authlib.yggdrasil.YggdrasilMinecraftSessionService.unpackTextures(YggdrasilMinecraftSessionService.java:150)
    at gfn$1.a(SourceFile:55)
    at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768)
    at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1760)
    at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373)
    at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182)
    at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655)
    at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622)
    at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165)

Excerpt of that same crash report which provided the location of the exploit skull:
Code:
-- Block Entity Details --
Details:
    Name: minecraft:skull // dig
    Block: Block{minecraft:player_head}[powered=false,rotation=12]
    Block location: World: (-2045,48,594), Section: (at 3,0,2 in -128,3,37; chunk contains blocks -2048,-64,592 to -2033,319,607), Region: (-4,1; contains chunks -128,32 to -97,63, blocks -2048,-64,512 to -1537,319,1023)
    Block: Block{minecraft:player_head}[powered=false,rotation=12]
    Block location: World: (-2045,48,594), Section: (at 3,0,2 in -128,3,37; chunk contains blocks -2048,-64,592 to -2033,319,607), Region: (-4,1; contains chunks -128,32 to -97,63, blocks -2048,-64,512 to -1537,319,1023)
Stacktrace:
    at fvg.a(SourceFile:107)
    at fvg.a(SourceFile:79)
    at ftf.a(SourceFile:1141)
    at fta.a(SourceFile:1098)
    at fta.a(SourceFile:866)
    at evi.d(SourceFile:1327)
    at evi.f(SourceFile:888)
    at net.minecraft.client.main.Main.main(SourceFile:265)

The CoreProtect logs of the skull at those coordinates:
1713371383994.png

5. 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.

6. Duration of the ban (Set a duration that reflects the severity of the offense.)
4-6 months.
 
Status
Not open for further replies.