mojira.dev

If you try adding custom NBT data to an item and have unbalanced curly brackets ({), it'll say you have unbalanced brackets. If you put unbalanced brackets ([), it'll say you have unbalanced curly brackets.

My testing:
Working:

/summon Arrow ~ ~ ~ {Motion:[1.0,0.0,0.0]}

Unbalanced "Curly":

/summon Arrow ~ ~ ~ {Motion:[1.0,0.0,0.0}

Unbalanced "Normal":

/summon Arrow ~ ~ ~ {Motion:[1.0,0.0,0.0]

And

Working:

/give FlyingPies155 1 1 0 {display:{Name:Test}}

Unbalanced "Curly":

/give FlyingPies155 1 1 0 {display:[Test}

Unbalanced "Normal:

/give FlyingPies155 1 1 0 {display:{Name:Test}

I know the /give example for the Unbalanced "Curly" is not how you actually use the metadata thing, but it still works.

Attachments

Comments 13

Please attach the exact command used.

Still an issue in 1.7.4, 1.7.5 and 1.8 snapshots

Still an issue in 14w10a/b

Confirmed for 14w11b

3 more comments

That would explain why it starts after the first space.

Confirmed for 14w17a

Confirmed for 14w25b.

Is this still an issue in the most recent versions (i.e. 1.10.2, or 16w42a) of Minecraft?

17w16a's new NBT parser returns different error messages that work as expected.

Flying Pies

(Unassigned)

Confirmed

brackets

Minecraft 13w36b, Minecraft 13w37a, Minecraft 13w37b, Minecraft 1.7.4, Minecraft 14w08a, ..., Minecraft 1.8, Minecraft 1.8.1-pre3, Minecraft 1.10.2, Minecraft 16w41a, Minecraft 16w42a

Minecraft 1.12

Retrieved