mojira.dev
MC-139876

The locate command for the new Pillager Outpost runs into an unexpected issue

The bug

When using the /locate command to locate a Pillager Outpost, it will say an unexpected error occurred. Hovering over the text says "java.lang.NullPointerException".

Linked issues

Attachments

Comments 9

What version was this world made in?

I have run into this same problem while first running the game in snapshot 18w47b (which I assume is the same version you're using as you're looking for pillager outposts) and it will resolve if you just wait a some time after loading your world.

note: to replicate this, you may have to switch in and out of versions and create a new world. I can't replicate it because I've been playing in the snapshot for awhile.

@unknown, what version did you create the world?

@Asteraoth, the world was created in snapshot 18w43b but updated to versions 18w44a and then 18w47b. I ran into the problems with the /locate command when attempting to use it in snapshot 18w47b.

Is there any way to avoid Pillagers to respawn in a Pillager Outpost? I couldn't find the Pillager spawner. Is there any method to find spawners? Thank you. I think it could be on a Mineshaft or a Dungeon near this Pillager structure. 

Cannot reproduce with a freshly generated world in 18w48b. Is this still an issue?

Unable to replicate right now but I experienced this in 18w48b when first running the snapshot (using the command to locate new villages). The only way to replicate would be to try it first thing when a new snapshot releases.

Still unable to reproduce. Please check if that's an issue in the latest snapshot.

Unable to reproduce in snapshot 19w02a after using the command to locate a mansion and pillager outpost. There was quite some lag, though, which I expect was just a result of loading up the world in the snapshot for the first time.

David Fletcher

(Unassigned)

Confirmed

/locate, command, unexpected

Minecraft 18w47a, Minecraft 18w47b

Retrieved