After updating to 20w28a snapshot existing pillager outposts stop spawning pillagers.
To recreate this do the following:
Create/join a world in 20w27a or below.
Locate a pillager outpost.
Save and quit.
Join the world again in 20w28a.
Remove the hostile mobs so new ones can spawn. I set the world to peacefull and back to normal difficulty.
→ ❌ No new pillagers will spawn at the outpost and the outpost doesn't show up using the /locate command.
Linked issues
is duplicated by
Attachments
Comments
j_p_smith
j_p_smith
Fixed in 20w29a. Note that worlds opened in 20w28a will still be corrupted.
galaxy_2alex
Can someone else confirm this Fix?
Can confirmed fixed in 20w29a.
This bug is only partially fixed. Can still replicate loss of structure information every time.
Open existing 1.15.2 world, enter nether, use /locate fortress and the fortress which is < 100 blocks away is detected.
Open the same 1.15.2 world in 20w29a, enter nether, use /locate fortress and the fortress which is < 100 blocks away is not detected. The closest fortress found is in the nearest newly generated 1.16 chunks. The same issue can be repeated when opening the world in 20w27a for the first time when upgrading from 1.15.2.
Previously generated villages and bastion remnants are also not being recognised by the /locate command. This affects the advancement "Those Were the Days", as it does not trigger upon entering a bastion generated prior to 20w28a. All other structures are being recognised correctly as far as I can tell.