[MC-1217] Enderman glitch death Created: 29/Oct/12  Updated: 14/May/17  Resolved: 19/Nov/12

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.2
Fix Version/s: None

Type: Bug
Reporter: Anthony Martin Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MC-2545 Persistent Chunk error / Corrupted wo... Resolved
Confirmation Status: Unconfirmed
Game Mode: Survival

 Description   

Apparently one of the players on my server experienced a glitch-death at the hands of an enderman. This stack trace was dumped to the console at the same time.

Wrong location! pm['Enderman'/489601, l='swim2', x=-149.35, y=44.17, z=-17.65]
java.lang.Exception: Stack trace
        at java.lang.Thread.dumpStack(Thread.java:1342)
        at za.a(SourceFile:508)
        at zn.a(SourceFile:277)
        at zn.a(SourceFile:87)
        at zn.a(SourceFile:75)
        at id.f(SourceFile:111)
        at id.c(SourceFile:73)
        at ic.<init>(SourceFile:26)
        at ib.a(SourceFile:171)
        at ib.d(SourceFile:299)
        at ge.d(SourceFile:147)
        at im.a(SourceFile:295)
        at dt.a(SourceFile:136)
        at bx.b(SourceFile:341)
        at im.d(SourceFile:73)
        at in.b(SourceFile:35)
        at hk.b(SourceFile:30)
        at net.minecraft.server.MinecraftServer.r(SourceFile:731)
        at hg.r(SourceFile:233)
        at net.minecraft.server.MinecraftServer.q(SourceFile:661)
        at net.minecraft.server.MinecraftServer.run(SourceFile:595)
        at fp.run(SourceFile:818)


 Comments   
Comment by Kumasasa [ 19/Nov/12 ]

"Wrong location! pm['Enderman'/489601, l='swim2', x=-149.35, y=44.17, z=-17.65]"

Comment by Anthony Martin [ 30/Oct/12 ]

It appears that this is caused by chunks not being read properly by the server. I saw console messages like:

Chunk file at 987,725 is in the wrong location; relocating. (Expected 987, 725, got 988, 729)

So it appears to me that this problem will eventually work itself out, and there is no bug, per se.

Generated at Sun Jan 12 11:53:42 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.