The Farlanders
- TheFarlanders
- thefarlanders
- Europe/Stockholm
- Yes
- No
MC-63446![[Mojang] Searge (Michael Stoyke)](../../../data/assets/gravatar/searge.png){kind=small}
The /setblock and /fill Command Block clocks can now randomly cease by themselves. This happens on servers and even in single player.
The common setup for these clocks would be similar to :
Top Command Block : "/setblock ~ ~-1 ~ minecraft:redstone_block 0"
Middle Block : Redstone Block (being rapidly replaced)
Bottom Command Block : "/setblock ~ ~1 ~ minecraft:stone 0"One of the easiest ways to reproduce is to create a long line of Command Blocks that set the next block along as a Redstone Block, which then triggers another identical Command Block and so on. It should look as though a single Redstone Block is moving along a line, being replaced by an alternate block behind it. Set this up to loop around and then exit the map in single player. Upon opening the map again, often the Redstone Block has duplicated, and there are now two in the setup. Repeating this will add more Redstone Blocks until the entire system has "jammed" completely.
As far as when this behaviour began, the earliest snapshot I'm aware of is 14w33c, though it was likely occurring much earlier. This bug poses a threat to a lot of custom maps that utilise 20hz clocks, or any /fill or set block clocks for that matter. Eventually, all clocks in the map will cease to function. Besides good old fashioned Redstone Repeaters, this is the only clock type remaining that functions outside the World Border.
The /setblock and /fill Command Block clocks can now randomly cease by themselves. This happens on servers and even in single player.
The common setup for these clocks would be similar to :
Top Command Block : "/setblock ~ ~-1 ~ minecraft:redstone_block 0"
Middle Block : Redstone Block (being rapidly replaced)
Bottom Command Block : "/setblock ~ ~1 ~ minecraft:stone 0"One of the easiest ways to reproduce is to create a long line of Command Blocks that set the next block along as a Redstone Block, which then triggers another identical Command Block and so on. It should look as though a single Redstone Block is moving along a line, being replaced by an alternate block behind it.
Much like this; http://gfycat.com/LightheartedEvenDwarfmongoose.Set this up to loop around and then exit the map in single player. Upon opening the map again, often the Redstone Block has duplicated, and there are now two in the setup. Repeating this will add more Redstone Blocks until the entire system has "jammed" completely.
As far as when this behaviour began, the earliest snapshot I'm aware of is 14w33c, though it was likely occurring much earlier. This bug poses a threat to a lot of custom maps that utilise 20hz clocks, or any /fill or set block clocks for that matter. Eventually, all clocks in the map will cease to function. Besides good old fashioned Redstone Repeaters, this is the only clock type remaining that functions outside the World Border.
This issue only occurs on a server - not single player or playing via 'Open to LAN'.
I have three command blocks set up on a clock to display a /title for players in a specific area. When they enter this area (only on a server), it causes everyone online to be kicked with the following error message
."Internal Exception: io.netty.handler.codec.DecoderException: com.google.son.JsonSyntaxException: com.google.son.stream.MalformedJsonException: Use JsonReader.setLenient(true) to accept malformed JSON at line 1 column 1"
Command blocks:
{"text":"Red Stained Clay","color":"white"}
/title @a[996,211,1000,r=1] subtitle ["",]
/title @a[996,211,1000,r=1] title []
/title @a[996,211,1000,r=1] times 0 3 2Deleting the player data file allows me to sign back in to the server, since I respawn outside of that area, however the issue persists. Haven't yet tested in previous snapshots.
Originally I thought having the command blocks set to 'Repeat' so rapidly might somehow be causing the issue, but it still happens even on a slow clock with 'Impulse' command blocks. Is affecting 3/3 of players who have tested it on their servers so far.
This issue only occurs on a server - not single player or playing via 'Open to LAN'.
I have three command blocks set up on a clock to display a /title for players in a specific area. When they enter this area (only on a server), it causes everyone online to be kicked with the following error message:
"Internal Exception: io.netty.handler.codec.DecoderException: com.google.son.JsonSyntaxException: com.google.son.stream.MalformedJsonException: Use JsonReader.setLenient(true) to accept malformed JSON at line 1 column 1"
Command blocks:
{"text":"Red Stained Clay","color":"white"}
/title @a[996,211,1000,r=1] subtitle ["",]
/title @a[996,211,1000,r=1] title []
/title @a[996,211,1000,r=1] times 0 3 2Deleting the player data file allows me to sign back in to the server, since I respawn outside of that area, however the issue persists. Haven't yet tested in previous snapshots.
Originally I thought having the command blocks set to 'Repeat' so rapidly might somehow be causing the issue, but it still happens even on a slow clock with 'Impulse' command blocks. Is affecting 3/3 of players who have tested it on their servers so far.
This issue only occurs on a server - not single player or playing via 'Open to LAN'.
I have three command blocks set up on a clock to display a /title for players in a specific area. When they enter this area (only on a server), it causes everyone online to be kicked with the following error message:
"Internal Exception: io.netty.handler.codec.DecoderException: com.google.son.JsonSyntaxException: com.google.son.stream.MalformedJsonException: Use JsonReader.setLenient(true) to accept malformed JSON at line 1 column 1"
Command blocks:
{"text":"Red Stained Clay","color":"white"}
/title @a[996,211,1000,r=1] subtitle ["",]
/title @a[996,211,1000,r=1] title []
/title @a[996,211,1000,r=1] times 0 3 2Deleting the player data file allows me to sign back in to the server, since I respawn outside of that area, however the issue persists. Haven't yet tested in previous snapshots.
Originally I thought having the command blocks set to 'Repeat' so rapidly might somehow be causing the issue, but it still happens even on a slow clock with 'Impulse' command blocks. Is affecting 3/3 of players who have tested it on their servers so far.
This issue only occurs on a server - not single player or playing via 'Open to LAN'.
I have three command blocks set up on a clock to display a /title for players in a specific area. When they enter this area (only on a server), it causes everyone online to be kicked with the following error message:
"Internal Exception: io.netty.handler.codec.DecoderException: com.google.son.JsonSyntaxException: com.google.son.stream.MalformedJsonException: Use JsonReader.setLenient(true) to accept malformed JSON at line 1 column 1"
Command blocks:
{"text":"Red Stained Clay","color":"white"}
/title @a[996,211,1000,r=1] subtitle ["",]
/title @a[996,211,1000,r=1] title []
/title @a[996,211,1000,r=1] times 0 3 2Deleting the player data file allows me to sign back in to the server, since I respawn outside of that area, however the issue persists. Haven't yet tested in previous snapshots. Originally I thought having the command blocks set to 'Repeat' so rapidly might somehow be causing the issue, but it still happens even on a slow clock with 'Impulse' command blocks. Is affecting 3/3 of players who have tested it on their servers so far.
I can stop this by fixing the JSON of the second command to:
{"text":"","color":"white"}
/title @a[996,211,1000,r=1] title ["",]
However the kicking of the player for incorrect JSON seems a little odd, especially because it only occurs on multiplayer servers, no issues on single player.
Have tested again in 14w31a, but still no luck.
Thanks! Sorry for the duplicate - I did a search for the error message rather than the cause of the issue, and didn't see it.
Confirmed for Minecraft 1.9
Looking at the NBT data of level.dat, it does appear 'BorderDamagePerBlock' is being updated after typing "/worldborder damage amount 0". So the command itself appears to be working at that level, but the game itself is ignoring the "0" value, and continues to damage players.
Entities like mobs don't appear to be taking damage.
This issue has been marked as resolved, however is not resolved. Affected versions has been updated.