I entered my usual nether portal as normal and the game spawned me in an unfamiliar setting (same coordinates). A nether portal did not generate with me when I spawned in the nether. I then tried to create a nether portal at this location only to be met with a crash (this happens if I make a portal anywhere in this biome).
Out of curiosity, I ventured out in the nether and all my other buildings remain.
The nether portals work as normal in other locations in the nether.
Stack trace
1.16-pre7\: [^crash-2020-06-16_18.27.04-server.txt]
Description: Ticking player
java.lang.IndexOutOfBoundsException: fromIndex < 0: -2368549
at java.util.BitSet.checkRange(BitSet.java:362)
at java.util.BitSet.set(BitSet.java:481)
at cia.a(SourceFile:13)
at cib.<init>(SourceFile:143)
at cib.<init>(SourceFile:108)
at cic.b(SourceFile:43)
at cic.a(SourceFile:50)
at chy.b(SourceFile:85)
at chy$$Lambda$4051/1753702905.get(Unknown Source)
at chy.a(SourceFile:120)
at chy$$Lambda$4054/349611958.run(Unknown Source)
at ams$b.run(SourceFile:54)
at amq.e(SourceFile:94)
at amq.a(SourceFile:137)
at amq.run(SourceFile:105)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)Linked issues
is duplicated by 1
Attachments
Comments 5
I am having the same issue (on 1.16.1), and the world was first made around 1.14ish (although I can't be sure, but it was definitely made pre 1.16). I will make a video soon showing off the problem to as good of a detail as I can provide. Otherwise everything is practically the same as the original report.
Also some things to note about my case in particular which I feel like I should mention:
I had recently done a fresh install of Minecraft after a hard-drive wipe, and this world was plucked from my disk backup into my fresh install of Minecraft
I have Minecraft installed on a different drive than the AppData folder. All the usual files that would normally exist in AppData are still put there (in fact I'm not sure there's even a way to move them from that directory without maybe a symbolic link), but the install itself (maybe just the launcher? not sure) was put into a different drive.
I have no idea if any of the above is relevant, but I only started getting this issue after my fresh install of Minecraft, and the issue existed even on 1.15.2 (but only after the bulleted things above were done, before that everything worked fine), so I suspect there's something wonky with either pulling the world data from a different install of Minecraft, the backup I did of my drive somehow slightly corrupted my world, or having Minecraft installed in a different drive from AppData is causing something to go wrong.
Please let me know if any more information is needed.
Is this still an issue in 1.16-pre7? If so, please attach a new crash report.