Embedded Files
Containers that save items inside Players
Containers that save items inside Players
Like the enderchest, no matter where the player opens them, their items will be there; The player owns its own copy.
Item Storage
Item Storage
Targetting Items (with the <slot> argument of GooP commands)
Targetting Items (with the <slot> argument of GooP commands)
While the player has the container open, the Observed Container key c will work.
Anytime, anywhere, use the internal name of them as the key |INTERNAL_NAME| (case sensitive, must be enclosed in bars).
This can only target the player's owned version of this container.
Special key for ConsumeItem to also sweep through all Personal Containers of a player:
P for normal item slots
L for slots inside shulker slots
Restrictions check the player interacting with the container (even if its not the owner).
Soft checks of restrictions (against the owner) to determine if the slots should de-activate.
To stop counting for MMOItems Equipment (see section below)
Will drop the items only to the owner (if the restriction behaviour is DROP)
Items put in slots of your choosing will add their MMOItem stats to a player's total.
The items will not count if the player does not meet the slot restriction requirements.
Instead of storing items in a player, store items in an item.
Like shulker boxes, but open with right-click, no need to place down.
Instead of storing items in a player, store items in an animal (or any other non-player entity).
Limitations
Limitations
A player cannot own more than one copy of a container.
Usage Examples
Usage Examples
/goop nbt setItem cocopad |NETHERCHEST|9-17 m CONSUMABLE GRAPES 1
Set the contents of the second row of cocopad's Netherchest to MMOItems grapes.
Page updated
Google Sites
Report abuse