Elf Elf

There is a logical continuity issue when "spawn chunks" are not at spawn. The command DOES NOT do what it is supposed to do; running this command will break the active spawn chunk region and make it work unreliably if a new player logs in after world spawn has been changed (this is an uncontrollable situation), or when a player happens to visit the new location (controllable, but an irritation). Until Mojang allows map makers to set the region of loaded chunks manually and independently of the world spawn, this is a real bug. I would appreciate it if you didn't inject your own personal opinion into someone else's bug reports.

As noted in duplicate bug report MC-42266, the world spawn coordinates are replicated to players upon respawn after death. The command needs to replicate the new coordinates immediately to all players in order to correct this bug.

A workaround to this problem is to append .0 to the X and Z coordinates, e.g. "/setblock -1.0 50 -1.0 stone". This ultimately makes no sense, since the block coordinate system should only take whole integers, but there is obviously something wrong with the algorithm they're using to convert negative integers.

Confirmed, the crash is being caused by correctly-formed, vanilla ActiveEffects.

Try removing any UUIDLeast and UUIDMost tags from SpawnData and any Properties tags in SpawnPotentials.

It was corrected the same night I told Dinnerbone about it on Twitter; this bug report was submitted at his request. As it's fixed, this report should be resolved.