In the new 1.9 snapshots, the JSON format has been changed to strict. Not a lot of people know this, because it was not clearly stated in the changelog for 15w31a and 15w31b. I put together a quick guide about the change and how to fix your current commands that use JSON.
HOW WAS IT CHANGED?
All values and tags in JSON needs to be closed in with double-quotes. Additionally, comments are not allowed in JSON anymore.
CAN YOU SHOW ME THIS?
This is an example of how /tellraw would be used to say "Hi World" before the 1.9 snapshots.
Notice that ALL parts of the JSON(except for the raw message) needs to be enclose with quotations. If you do not close in every part of the JSON with quotations, you will get an error and the command won't work.
HOW DOES THIS AFFECTS CUSTOM MAPS AND SERVERS?
All map makers that use /tellraw or other command that use JSON to show the messages(signs, books, etc) will need to re-write their JSON data so that it works with 1.9. Additionally, server owners that have servers which use commands that require JSON to complete the command will also have to rewrite the commands to make them work with the 1.9.
HOW LONG WILL IT TAKE TO REWRITE MY JSON STUFF?
It depends. If you have a custom map or server that has commands which use JSON, you will have to re-write all of it, which could take hours to do depending on the amount of these commands you used.
ARE THERE THINGS THAT DON'T NEED TO BE ENCASED WITH QUOTES?
Yes, there is still some stuff that don't need to be encased with quotes. I will put them into the list bellow when I find them or another community member finds them. If a community member finds them, they will recieve the proper credit in the list.
Man this sucks i run the server ProShot a vanilla snapshots server and wow this is gonna require ALOT of rewriting, but i suppose in terms of crasher via hacked clients it better
Well, I cannot say I'm pleased about having to rewrite all my JSON but thank you for bringing this to our attention, this would have taken me hours of frustration to figure out on my own. (I might have ended up just giving up and waited for skylinerw to update his post)
For a source concerning this being intentional, I asked Searge directly and have the following response:
yes, tellraw and title (anything using text components) needs to be strict JSON now
So it's definitely a requirement now.
Note that books currently (15w32b) use lenient JSON while the rest use strict. But since it is going to be changed, it no longer points to controversy.
Well, I cannot say I'm pleased about having to rewrite all my JSON but thank you for bringing this to our attention, this would have taken me hours of frustration to figure out on my own. (I might have ended up just giving up and waited for skylinerw to update his post)
Unfortunately I cannot update my thread due to formatting issues with the post parser on the forums. Thus far there have been no tag additions to the JSON text component. For converting between lenient and strict, I'll have to see if there's a converter somewhere or I could create one myself for it.
I guess they could add all this in but they should add it into the game for only new command blocks or something. or maybe add them along side the previous stuff. or have a new kind of system with command blocks where you can choose to have the old stuff or the 1.9 stuff so nothing breaks
It seems like there aren't any clear posts as to the pros and/or cons of this change from the game's standpoint, yet there is a vote for it's value.
This is the only post that seems to touch on a pro to this change.
Easier maintainability and debugging as a result of standardization. For example, instead of all of the following being a possibility that has to be parsed by the game or for us to sift through when checking for errors in other people's commands:
Which is a lot less to deal with when determining an issue or parsing input. Everybody will now have the same format to use instead of mixed/assorted preference.
I'm the 3rd generation. The first time you see this, copy as your signature and add 1 to the counter
"I must not fear. Fear is the mind-killer. Fear is the little-death that bring total obliteration. I will face my fear. I will permit it to pass over me and through me. And when it has gone past I will turn the inner eye to see its path. Where the fear has gone there will be nothing. Only I will remain."
In the new 1.9 snapshots, the JSON format has been changed to strict. Not a lot of people know this, because it was not clearly stated in the changelog for 15w31a and 15w31b. I put together a quick guide about the change and how to fix your current commands that use JSON.
HOW WAS IT CHANGED?
All values and tags in JSON needs to be closed in with double-quotes. Additionally, comments are not allowed in JSON anymore.
CAN YOU SHOW ME THIS?
This is an example of how /tellraw would be used to say "Hi World" before the 1.9 snapshots.
/tellraw @a {text:"Hi World",color:green,bold:true}
This is an example of how /tellraw is to be used to say "Hi World" in the 1.9 snapshots.
/tellraw @a {"text":"Hi World","color":"green","bold":true}
Notice that ALL parts of the JSON(except for the raw message) needs to be enclose with quotations. If you do not close in every part of the JSON with quotations, you will get an error and the command won't work.
HOW DOES THIS AFFECTS CUSTOM MAPS AND SERVERS?
All map makers that use /tellraw or other command that use JSON to show the messages(signs, books, etc) will need to re-write their JSON data so that it works with 1.9. Additionally, server owners that have servers which use commands that require JSON to complete the command will also have to rewrite the commands to make them work with the 1.9.
HOW LONG WILL IT TAKE TO REWRITE MY JSON STUFF?
It depends. If you have a custom map or server that has commands which use JSON, you will have to re-write all of it, which could take hours to do depending on the amount of these commands you used.
ARE THERE THINGS THAT DON'T NEED TO BE ENCASED WITH QUOTES?
Yes, there is still some stuff that don't need to be encased with quotes. I will put them into the list bellow when I find them or another community member finds them. If a community member finds them, they will recieve the proper credit in the list.
true/false - Found by: kwerti
null - Found by: 1No_Name1
numbers - Found by: penne12
Check out my PvP map Here!
Check out my website Here!Website is down until further notice.Man this sucks i run the server ProShot a vanilla snapshots server and wow this is gonna require ALOT of rewriting, but i suppose in terms of crasher via hacked clients it better
Be involved in the Survival of Modding in the Post-Notch Era. Enigma + M3L + LiteLoader/API + BlazeLoader {ALL Open-Source!}
Darn.
Well, I cannot say I'm pleased about having to rewrite all my JSON but thank you for bringing this to our attention, this would have taken me hours of frustration to figure out on my own. (I might have ended up just giving up and waited for skylinerw to update his post)
For a source concerning this being intentional, I asked Searge directly and have the following response:
So it's definitely a requirement now.
Note that books currently (15w32b) use lenient JSON while the rest use strict. But since it is going to be changed, it no longer points to controversy.
Unfortunately I cannot update my thread due to formatting issues with the post parser on the forums. Thus far there have been no tag additions to the JSON text component. For converting between lenient and strict, I'll have to see if there's a converter somewhere or I could create one myself for it.
EDIT: Found this converter: http://yamltojson.com/
Example input:
Output:
Minecraft-things: http://skylinerw.com
More Minecraft-things: https://sourceblock.net
Guides for command-related features (eventually moving to Source Block): https://github.com/skylinerw/guides
I primarily hang out in the /r/MinecraftCommands discord, where there's a lot of people that help with commands: https://discord.gg/QAFXFtZ
Their corresponding subreddit: https://www.reddit.com/r/MinecraftCommands/
Why can't everything just stay the same so we don't have to fix things?
I know right? It would be fine if they just kept it lenient so that backwards compatability wouldn't have been broken.
Check out my PvP map Here!
Check out my website Here!Website is down until further notice.Note that "true" and "false" are boolean literals and should not be enclosed in quotes.
Putting the CENDENT back in transcendent!
Oh, OK. I will add that to the main post.
Check out my PvP map Here!
Check out my website Here!Website is down until further notice.I guess they could add all this in but they should add it into the game for only new command blocks or something. or maybe add them along side the previous stuff. or have a new kind of system with command blocks where you can choose to have the old stuff or the 1.9 stuff so nothing breaks
i will notify mojang of this problem if i can, but i dont think they are gonna change it
Contact me for all your redstone and command needs!
It seems like there aren't any clear posts as to the pros and/or cons of this change from the game's standpoint, yet there is a vote for it's value.
This is the only post that seems to touch on a pro to this change.
Easier maintainability and debugging as a result of standardization. For example, instead of all of the following being a possibility that has to be parsed by the game or for us to sift through when checking for errors in other people's commands:
Only the following would be possible:
Which is a lot less to deal with when determining an issue or parsing input. Everybody will now have the same format to use instead of mixed/assorted preference.
Minecraft-things: http://skylinerw.com
More Minecraft-things: https://sourceblock.net
Guides for command-related features (eventually moving to Source Block): https://github.com/skylinerw/guides
I primarily hang out in the /r/MinecraftCommands discord, where there's a lot of people that help with commands: https://discord.gg/QAFXFtZ
Their corresponding subreddit: https://www.reddit.com/r/MinecraftCommands/
I thought the exact same thing and made one!
It should have everything you need.
http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-tools/2567931-1-9-autumns-sign-generator#c8
Maybe, this changes. Its only a snapshot :c
I'm the 3rd generation. The first time you see this, copy as your signature and add 1 to the counter
"I must not fear. Fear is the mind-killer. Fear is the little-death that bring total obliteration. I will face my fear. I will permit it to pass over me and through me. And when it has gone past I will turn the inner eye to see its path. Where the fear has gone there will be nothing. Only I will remain."
JSON things that don't need to be in quotes:
Try Diamond-Lang, it's Ruby (the programming language) for One Command Creations.
Also, programs can create JSON for Minecraft Easier.
Try Diamond-Lang, it's Ruby (the programming language) for One Command Creations.
Here you go: [MCEdit filter] 1.8 JSON to 1.9 "Strict" JSON
This appears to be a more refined way of doing things and a positive change. less to process, less memory usage.
I don't have any tellraw whatsoever.
still a good read.
"null" dosen't need quotes.
.