[MC-55402] Pistons stop moving outside world border

I'm not sure if this is a bug or not, but if it isn't, its rather annoying. I have a spawn pad set at the co-ordinates of (1500,0) and when the first player steps into the spawn pad, it sets off a list of command blocks, including Worldborder (center = 0,0 and length of blocks = 1000). My concern is that, I have a few pistons inside the machine, that work at first, but as soon as the world border is set into effect, it stops due to it being outside the world border. Let me know if this is intended or a bug.
Thanks!

Related issues

is duplicated by

MC-55646 Redstone doesn't work outside worldborder when size of border changes

MC-56147 Commands that Change Block Data Cannot be Used Outside the Worldborder

relates to

MC-54366 Piston can push blocks one block far out of the worldborder

MC-114002 Small fireballs set fire outside of world border

MC-227722 Redstone components outside the world border are read/updated by blocks inside the world border

MC-55588 Spawn Chunks not working if world border covers it

Attachments

Comments

migrated 2014-05-17T23:42:41Z

[media][media][media][media][media][media][media][media][media]

migrated 2014-05-17T23:48:53Z

Please provide a screenshot of your setup.

migrated 2014-05-18T00:15:40Z

Pictures uploaded. The first three photos are of the spawn pad itself. The second three photos are the piston working when the spawn pad is within worldborder and the last three are when its outside the boundary.

EDIT: And the reason I need the spawn pad outside the world border is because I am using this for a P.v.P. setup were the players are free to roam around the world, restricted by the world boundary. If the spawn pad was within the "playable world," the players could easily exploit the system and stay safe from mobs, etc.

migrated 2014-05-18T01:02:30Z

Hmm... this does appear to be a bug.

kumasasa 2014-05-18T03:28:42Z

MC-54366 is claiming the opposite

migrated 2014-05-18T14:46:54Z

MC-54366 is saying that the piston can push blocks outside the boundary, but the piston is still inside the boundary itself. My problem is that, my piston is outside the boundary completely and doesn't activate at all.

migrated 2014-06-01T22:21:36Z

Confirmed.

migrated 2014-08-17T04:40:56Z

This is still an issue as of 14w32d. Commandblocks seem to be able to operate outside of the worldborder, but after teleporting away, with no players nearby, the commands stop.

This is with commands that are in map spawn chunks.

You can test this with a simple clock hooked up to a say command. Teleport 5000 blocks away and then set a small worldborder centered on you. You bay need to teleport back and forth a few times. It also seems like it will happen after just a short time.

It feels like the game is unloading the chunks because the area is outside of the world border, yet these chunks are spawn chunks and should not be unloaded.

This is vital for map makers that want to have a "game system" that is only loaded for the server, but that they also want to use the world border feature in.

I can explain more if necessary, but I think this crowd knows what I mean.