Open ghost opened 5 years ago
What if you make it tag:{true:1b}? This parser is known to be very strict with that stuff
What if you make it tag:{true:1b}? This parser is known to be very strict with that stuff
That's not a part of the problem, as seen by the error caused from execute if data entity @s Inventory[{Slot:0b}]
. I never actually used the function shown there as it was a very poor solution to my problem, it was just there to demonstrate the stage at which Sublime Text 3 began to lag.
So I have been having a similer issue with generating custom items in a battle arena, tried the true:1b flag which didn't work, and I have 280 lines and its real laggy. A fix or suggestion for both would be great!
Currently there isn't really a workaround for this. This bug stems from the fact that the parser for NBT paths like this. I'll see if I can work on this over the next week and put out a fix. As far as the lag goes, this is just a result of the fact that the parsing is really inefficient and needs a rewrite.
When using nbt to search an inventory via Inventory[{}] or adding display nbt to an item, it is highlighted as an error. Additionally, when there are many such errors (150+ lines), there is an extreme decrease in the framerate while viewing the file. This framerate drop is not present if the file is viewed as plain text.
execute if data entity @s Inventory[{Slot:0b}]
give @s stick{display:{Name:'{"text":"Sticky"}'}}