7

Follow

Changing {Inventory} tag structure

My suggestion is very simple, it is to turn
Inventory:[{Slot:1b,id:"minecraft:stone",Count:1b},{Slot:4b,id:"minecraft:dirt",Count:2b}}                     
to
Inventory:[Slot1:{id:"minecraft:stone",Count:1b},Slot4:{id:"minecraft:dirt",Count:2b}}

There are many benefits to having the Slot on the outside of the rest of the data, for example, you can use execute store on items in specific slots like this:

execute as @a store result score @s score1 run data get entity @s Inventory.Slot1.Count

This was possible before, however it took ~40 commands for ONE slot

Registered User shared this idea

• September 09, 2018 06:20
• Report a Concern

3 Comments

• Facebook
• Twitter
• LinkedIn

Post a new comment:

Please sign in to leave a comment.

Sorted by oldest

• 0

  Registered User commented

  Comment actions Permalink

  • September 19, 2018 18:04
  • Edited
  • Report a Concern
  • Comment actions Permalink

  "Inventory:[Slot1:{id:"minecraft:stone",Count:1b},Slot4:{id:"minecraft:dirt",Count:2b}}" this is invalid NBT (lists objects can't have names)
  
  What I'd suggest instead is this:
  
  Inventory:{<slot as used in the replaceitem command>:{<item data without the slot tag>}}
  for example:
  Inventory:{weapon.offhand:{id:"minecraft:stone",Count:1b}}

• 0

  Registered User commented

  Comment actions Permalink

  • October 06, 2018 17:56
  • Report a Concern
  • Comment actions Permalink

  I really looking for this change, Im making a datapack with custom crafting table and it was a PAIN to make it.

• 0

  Registered User commented

  Comment actions Permalink

  • May 01, 2019 21:14
  • Report a Concern
  • Comment actions Permalink

  I wouldn't suggest removing the Slot tag, as currently you can do Inventory[{id:"minecraft:stone"].Slot to figure out the slot number, but I do understand the annoyance of the array index vs the Slot id.