Dinnerbone's statement:
"That happens with corrupted chunks, possibly you went back and forth in an old version or there was a bug in an old versions upgrade, or you spawned it in incorrectly and it never caught it before. Ultimately it was corrupt before 1.13 saw it and now we don't know what to do with it."
"Now there's actually checks that the world makes sense and it catches lots of old corruptions, for better or worse"
1.13\: [^crash-2018-07-18_20.44.51-server.txt]
---- Minecraft Crash Report ----
// You should try our sister game, Minceraft!
Time: 18/07/18 20:44
Description: Ticking memory connection
i: Non [a-z0-9/._-] character in path of location: minecraft:EntityHorse
at pc.<init>(SourceFile:38)
at pc.<init>(SourceFile:43)
at wn.a(SourceFile:121)
at wn.a(SourceFile:100)
at wn.<init>(SourceFile:48)
at vo.a(SourceFile:915)
at te.<init>(SourceFile:159)
at vo.g(SourceFile:442)
at ud.b(SourceFile:113)
at ud.Y_(SourceFile:65)
at hw.a(SourceFile:238)
at ua.c(SourceFile:171)
at net.minecraft.server.MinecraftServer.w(SourceFile:749)
at net.minecraft.server.MinecraftServer.v(SourceFile:656)
at dfx.v(SourceFile:157)
at net.minecraft.server.MinecraftServer.run(SourceFile:559)
at java.lang.Thread.run(Thread.java:745)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Thread: Server thread
Stacktrace:
at pc.<init>(SourceFile:38)
at pc.<init>(SourceFile:43)
at wn.a(SourceFile:121)
at wn.a(SourceFile:100)
at wn.<init>(SourceFile:48)
at vo.a(SourceFile:915)
at te.<init>(SourceFile:159)
at vo.g(SourceFile:442)
at ud.b(SourceFile:113)
at ud.Y_(SourceFile:65)
at hw.a(SourceFile:238)
-- Ticking connection --
Details:
Connection: hw@67e7a7a4
Stacktrace:
at ua.c(SourceFile:171)
at net.minecraft.server.MinecraftServer.w(SourceFile:749)
at net.minecraft.server.MinecraftServer.v(SourceFile:656)
at dfx.v(SourceFile:157)
at net.minecraft.server.MinecraftServer.run(SourceFile:559)
at java.lang.Thread.run(Thread.java:745)
-- System Details --
Details:
Minecraft Version: 1.13
Operating System: Windows 10 (amd64) version 10.0
Java Version: 1.8.0_51, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 171154128 bytes (163 MB) / 570425344 bytes (544 MB) up to 1073741824 bytes (1024 MB)
JVM Flags: 9 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx1G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=16M
Profiler Position: N/A (disabled)
Player Count: 0 / 8; []
Data Packs: vanilla
Type: Integrated Server (map_client.txt)
Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.Linked issues
is duplicated by 2
Attachments
Comments 3
This issue might relate to/duplicate MC-124123.
@unknown, consider using a tool that might be capable of deleting the corrupted chunk. If you want to kill the horse, do so before upgrading the world to 1.13. As of 1.11, the horse's entity id is now minecraft:horse, making it more difficult to target in a 1.13 world. Additionally, /kill only kills entities in loaded chunks.
@unknown, that would be not so easy. I have pretty much wild horses in different biomes and locations. I have one horse that is mine and i can kill it, but if i have to go and kill all wild horses, that would be pretty troublesome. And also there can be other problems. I saw same bug and the log was almost same, but it was "ZombieEntity". So it would be better if world optimizer or some tool just remove bugged entity or swap it with "clean" one
Is it possible to make a tool that will destroy corrupted chunks so there won't be any in the world? Or kill a horse if that's the problem. I will gladly sacrifice the horse if that would save all the rest.