mojira.dev
MC-151421

Village stuck in perpetual state after nether bug

I have built up a village on a private server that recently reset to the state I discovered the village after I returned to the overworld from a nether portal I built under the village. When I returned to the overworld it spawned a new portal in the overworld and the village was in the state from the fresh seed. The server administration was able to recover the progress I had made to the village with a server rollback but now the village is stuck in a groundhog day type perpetual state. It seems that when I log off for the night the next day I log in the village is just as it was when we rolled back the server. I'm able to make edits to areas out side of this village but the chunks or village boundary that may have been affected by the nether portal wiping it to factory seem broken.

Comments 9

The village he mentionned spawned with the world, then he build in, and around it (make it safe and such)
I'm the admin of the server he's playing on.
The issue happenned twice in 2 days.

What server software do you use?

I'm renting a server so i have no idea.
managing it via a pannel and ftp.

Why does it say resolved? I don't see a resolution.

We need further information from you, hence your report was closed as "Awaiting Response".

  • What server software do you use? (Realms / Vanilla / Bukkit / Spigot / Paper). Even if you rent a server, you should be able to find this out.

  • Was the world ever opened in a non-vanilla environment?

  • Are there any error messages in the console?

Vanilla, 100%
only rule i changed is the firetick, it's off.
no, nothing on the console when it happend (both times).
but we do have werid issues with the console and the inability to connect to a server (pinging continuously), but that's another problem.

Also the server is a fresh 1.14 server.
no upgrade from 1.13.
no upgrade towards 1.14.1 pre 1 or 2.
just 1.14 since the minute it was out.

 

Please check if this is still an issue for you in 1.16 Release Candidate 1 or later.

We're still on the same server, in 1.15.2 now, and we never experienced it again. 
I couldn't tell you what version fixed the problem tho.

WESLEY B NEWHALL

(Unassigned)

Unconfirmed

(Unassigned)

Minecraft 1.14

Retrieved