mojira.dev
MC-55588

Spawn Chunks not working if world border covers it

When worldborder is set in the "death zone" and your spawn chunks are in it none of the spawn chunks will load, breaking all redstone/command blocks.

Example:

You have /setworldspawn at 5000, 120, 0
do a clock at those coordinates (simple hopper clock) and output a comparator and a command block doing "say hi".
Check to see if you're spammed "[@] hi",
If yes, go to 0, 120, 0 then do these commands:
/worldborder center 0 0
/worldborder set 1000

Watch that after 10 seconds your "[@] hi"'s will stop and the chunks are no longer loaded.

Related issues

Comments

marcono1234

Confirmed for 14w20b
*Don't know if it's intended

I guess best way to reproduce:
1. Create new world
2. Build a clock with a command block performing:

/say Hi

3. Do:

/tp ~10000 ~ ~

4. Do:

/worldborder center ~ ~

5. Do:

/worldborder set 100

And then wait a couple of seconds

kumasasa

Related to / duplicate of MC-55402

Proably intended.
The world border can be interpreted as "Here is the end of the world, nothing is outside"

kasamikona

that technically means that there can now be worlds without any spawn chunks. thats kinda bad.

Egor

Maybe make it so that at least the spawn chunks work? Otherwise this can really be bad for people making "lag-free" or no-exploit redstone/commands.

Tokes

The worldspawn should always be in the border. If it isn't, blame the person who changed the border for not thinking it through. Also if the worldspawn is outside the border and your bed gets destroyed and you get killed by a skeleton...what do you think is going to happen? "The worldspawn is outside" is a bigger problem than just machines not continuing.

In otherwords, "Problem Exists Between Keyboard And Chair"

Egor

michael

Unconfirmed

Minecraft 14w20b

Retrieved