Quote from TheMinecraftNerd1»
So it seems that mojang tweaked the Chain Command Blocks and how NBT parsing works. Will this affect any or break current maps using NBT or Chain Command Blocks when the update is released?
For the command block change, it should ideally not break much. It reorders how command blocks are scheduled, fixing an issue where a chain shut off via a Chain block will still fire the next tick (more details here). What might break are any in-game attempts to circumvent that issue, though that depends on the method being used I suppose.
As for NBT changes, if you used quotes for all your strings and did not use list indices, you're good to go. There are a number of changes that were made to the parser though (as it was essentially completely rewritten), so I've got a more detailed post here.
0
Sorry it took so long; updated the thread to 1.12 to include the "keybind" feature.
2
Sorry for the long delay. I'm now back and have updated the thread with a list of changes between 17w18a and 1.12 release, as well as extra info after studying MCP.
Shared Data
Triggers
The entire list of triggers has been relocated to this post due to exceeding the character limit in combination with the main body.
Requirements
Display
Rewards
Some time in the next week I'll be adding a timeline describing when advancements activate in relation to each other and to entities and tile entities. This will be particularly useful for knowing when functions are going to be running.
If I've missed any other changes, please let me know!
2
The NBT parser has been rewritten and you'll need to use quotes around strings that contain syntax-breaking characters (in your case, the colon in "minecraft:villager" is breaking syntax):
{ "pools": [{ "conditions": [{ "condition": "killed_by_player" }, { "condition": "random_chance_with_looting", "chance": 0.01, "looting_multiplier": 0.03 } ], "rolls": 1, "entries": [{ "type": "item", "name": "minecraft:spawn_egg", "weight": 1, "functions": [{ "function": "set_nbt", "tag": "{EntityTag:{id:\"minecraft:villager\"}}" }] }] }] }More information concerning NBT syntax changes here: https://www.reddit.com/r/MinecraftCommands/comments/66jj03/changes_to_the_stringtonbt_parser_in_112/
1
I was able to wait until today before becoming unavailable. Changes to the thread caused by 17w18b:
Shared data
1. A new "block" shared object was added, holding data used by the "minecraft:placed_block" and "minecraft:enter_block" triggers.
Triggers
1. A new "minecraft:arbitrary_player_tick" trigger has been added.
2. A new "minecraft:consume_item" trigger has been added (item is before consumption).
3. A new "minecraft:placed_block" trigger has been added.
The thread has reached the 120k character limit. Not exactly sure what I'm going to do now, especially if more features are going to keep being added. Will probably have to use my second post in this thread to hold all the triggers, which takes up the bulk of the characters.
0
Mmm, the problem there is:
The ":" character is now a special character that will break syntax if it the string it belongs to is not encased in quotes:
As far as I can tell that's the only issue in that particular command:
setblock ~ ~ ~ minecraft:mob_spawner 0 replace {SpawnData:{id:"minecraft:armor_stand",ArmorItems:[{},{},{},{id:"minecraft:leather_boots",Count:1,Damage:4,tag:{Unbreakable:1,display:{color:16777215}}}],HandItems:[{},{}],Pose:{RightArm:[30f,0f,0f],LeftArm:[30f,0f,0f]}},RequiredPlayerRange:0,MaxNearbyEntities:0}1
Changes to the thread caused by 17w18a:
Shared data
1. A new "distance" shared object has been added, holding various options about distance between an origin.
2. The "entity" shared object now uses the "distance" shared object instead of a "distance" range.
Triggers
1. A new "minecraft:tick" trigger has been added.
2. A new "minecraft:tame_animal" trigger has been added.
3. The "minecraft:levitation" trigger now uses the "distance" shared object instead of a "distance" range.
Display
1. A new option "show_toast" has been added.
2. A new option "announce_to_chat" has been added. There is also a new gamerule "announceAdvancements", which when false, prevents all announcements from being shown in the chat.
Unfortunately I will be gone for a couple weeks and will likely not be able to update the thread for the next couple of snapshots. Sorry!
0
Your link doesn't work. Assuming this is what you're referring to, then see this list of changes to the NBT syntax. In particular, this command in the video's description:
/blockdata ~ ~ ~ {SpawnData:{ArmorItems:[0:{},1:{},2:{},3:{id:"minecraft:diamond_hoe",Count:1b,Damage:1s,tag:{Unbreakable:1}}]}}The list indices must be removed; they never worked and the parser was rewritten to not accept keys for list elements:
/blockdata ~ ~ ~ {SpawnData:{ArmorItems:[{},{},{},{id:"minecraft:diamond_hoe",Count:1b,Damage:1s,tag:{Unbreakable:1}}]}}0
0
Resource packs do not control custom player heads.
A player skull with "SkullOwner" string is translated into a compound containing an encoded URL to the skin file on Mojang's servers. That skull will always keep that same URL. Changing your own skin will create a new URL for your new skin, while the old URL will not change and that old head will retain its skin.
So while being logged out, you can change your skin, login, give yourself the skull with your name, exit the game, change your skin to something else, and that skull will still have the old skin. You can do this as many times as you want in order to get custom player skulls to fit your needs that will never expire.
EDIT: I should mention that there may be an issue where the "SkullOwner" string isn't translated, primarily when first provided via /give. You may have to throw the skull on the ground first and pick it back up before exiting the game, otherwise it'll just have the new skin.
0
The NBT parser was written completely for 1.12. I forgot to link to a list of changes, which has now been added to the main post (link).
0
It is not possible. The arrows in the player are not entities so /kill will not remove them.
1
Functions are only available for individual entries, so you have to repeat it.
0
Since the /scoreboard command has player bias, you need to specifically exclude players (adding "type=!player" to the nested selectors, ensuring you keep "c=1"). In 1.12 you can use the @s selector instead.
0
If you don't have quotes around the string value, you need to add them for special characters (in your case, /):
/summon minecraft:skeleton ~ ~1 ~ {DeathLootTable:"minecraft:entities/skeleton"}0
Sadly I don't. I would also recommend not doing so until 1.12 is released; new default advancements have constantly been added, and others moved around, so that resource would likely become outdated very quickly.