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
Fixed, thanks!
0
The commands are too long for the chat (the character limit for chat input is 100 characters in 1.10, and the commands that are failing are longer than that). You must use a command block instead.
0
Only change for 16w43a concerns evocation fangs:
"OwnerUUIDLeast/OwnerUUIDMost" (long)
Stores the UUID of the entity that "owns" these fangs. Introduced as a fix for MC-107846.
/summon minecraft:evocation_fangs ~ ~1 ~ {OwnerUUIDLeast:1l,OwnerUUIDMost:1l}3
Your return to the tracker to vandalize it contradicts these statements.
The bug tracker is not for you to create a report and treat it as though it's your own to mess with as you see fit. You are supposed to report bugs for the sake of the game's benefit, not your own. Any report you give to the tracker belongs to the tracker. Anything that happens to it is ultimately not up to you. The point of the tracker is to track bugs, and moderators must do what they can to keep that intact.
Bug reports are not deleted because they can help link to a main report, or are used as a reference for future conduct (such as a developer stating a certain thing is always "Working as Intended" (which is the case for your report), or as the primary report that duplicates are linked to). By vandalizing your own reported tickets, you are destroying that link and reference. You did this multiple times to your report, until finally (not "suddenly") the reporter was changed to a "holding" account to prevent you from continuing.
Your response to that, such as spamming, racist and sexist remarks, profanity, ban evasion, death threats, and vandalism (all of which occurred both before and after your statements I quoted), is what gets you banned.
0
Changes from 16w42a:
Entity: Arrows
"crit" (byte)
States whether or not the arrow is going to deal critical damage (and produce particles). Intended as a fix for MC-107138.
/summon minecraft:arrow ~ ~10 ~ {crit:1b}0
Scoreboards are a separate system from command blocks. Breaking a block containing a command isn't going to delete unrelated scoreboard entries.
You need to use the /scoreboard command to wipe out scoreboard data, or could otherwise delete the "scoreboard.dat" file:
0
Woops, I had meant to set the duration to INT_MAX (roughly 3 years):
/summon Chicken 39 86 257 {NoAI:1b,Silent:1,PersistenceRequired:0b,ActiveEffects:[{Id:14b,Duration:2147483647,ShowParticles:0b}]}It will still expire in 3 years. The only way around that is to re-apply it using the /effect command:
2
"Passengers" is a list tag, where each compound in the list are entities at the same riding depth:
/summon minecraft:boat ~ ~1 ~ {Passengers:[{id:"minecraft:armor_stand"},{id:"minecraft:armor_stand"}]}1
This is a bug fixed in 1.11: https://bugs.mojang.com/browse/MC-101120
Your Text1 tag is invalid because you do not have a "text" string specified, only the click event. The same goes for all of the other lines on the sign. Fixed:
/give @p sign 1 0 {BlockEntityTag:{Text1:"{\"text\":\"\",\"clickEvent\":{\"action\":\"run_command\",\"value\":\"kill\"}}",Text2:"{\"text\":\"\",\"clickEvent\":{\"action\":\"run_command\",\"value\":\"kill\"}}",Text3:"{\"text\":\"\",\"clickEvent\":{\"action\":\"run_command\",\"value\":\"kill\"}}",Text4:"{\"text\":\"\",\"clickEvent\":{\"action\":\"run_command\",\"value\":\"kill\"}}"},display:{Name:"Custom Sign"}}0
Spigot does not mix well with vanilla command mechanics. At this point you would be better off using/making a plugin, which has much more control and support with Spigot than commands do. That error, while present in vanilla source, is actually not possible to obtain in vanilla. You should probably seek help on Spigot forums instead, since this section primarily focuses on vanilla, while your issue is Spigot.
0
What version are you using and are you using vanilla? If you're not in vanilla, then that would be why.
0
If you want players to modify their own score based on their own score, you'd need to use /execute such that each player is running an operation, and can target themselves (fulfilling the single-target requirement):
0
The presented command works fine with multiple targets. Keep in mind that one of the targets in the command must resolve to a single target in order for the command to succeed. Since you're using a fake player for the second target, that requirement is fulfilled, but if you're swapping it out for a selector that targets multiple entities, then it'll fail if the first one selects multiple players.
0
Have you tried it in the latest snapshot? Errors returned for selectors have been modified to be more clear, so should help in solving the issue.
0
The change was that shorthand parameters are no longer possible (i.e. @e[10,64,10,5] to specify origin and radius without keys). The keys are now required (i.e. @e[x=10,y=64,z=10,r=5]).
Just using the "y" parameter will not work, because "x" and "z" will be filled in automatically with the exeuctor's coordinates (in this case, the coordinates of the command block). That means the player must be at the same X and Z as the command block for it to find them.
The solution is to use /execute to change the origin to that of the player, so that the X and Z will be their own. This also allows you to skip using /testfor, which is not multi-player friendly. For example, the following teleports players that come within 4 blocks of Y100, regardless of their X and Z values: