Config Aliases

<container>

• • Internal name of the Container Template you are editing.

<slot>

• • Slot number that you want to edit. Always a positive integer number.

    • Can only bind commands to one slot at a time.

    • You can easily check which slot is which using /goop containers config view

  • Though you normally target containers with the c key...

    • For this command do not use it, just do 0-8,9,17 instead of c0-8,c9,c17

    • You don't actually have the container open now so this c key wouldn't work anyway

[alias]

• • The name that you will use to refer to these slots in the future.

    • For example, instead of c23-25 you will now use c<INGREDIENTS>

  • Leave blanc to instead remove the alias from these slots.

• You may use caps or not, but be mindful because aliases are case sensitive.

• The purpose of this command is to make slot-referencing less tedious; Suppose in your command you are targetting c<FLASH> instead of c0-8,c9,c17,c18,c26,c27-35:

  • Using FLASH is more readable.

  • If you decide to change the slots that will flash, you won't have to edit the command, just the aliasese

• The reason it still requires the c prefix is because you could also use this for Personal Containers, that can be referenced while closed

  • goop testinventory %player% |VOID_BAG|<FLASH> m CONSUMABLE MANGO

  • No longer using the c key because this is targetting the personal container. However most of the time you will be using the c key.

• Aliases do not work for contaners config commands, only from everywhere else.