Skip to main content
Tags are the Awoken rework’s category system. Any item or weapon can declare one or more tags, and players use a multi-select filter dropdown to show only items matching the chosen tags. The default config ships 26+ tags out of the box, covering food, drink, medical, clothing, tools, electronics, documents, materials, currency, equipment, storage, and every weapon class (pistol, smg, shotgun, rifle, sniper, heavy, launcher, throwable, melee, attachment, ammo).

How the filter works

The Type button in the toolbar opens a multi-select dropdown. Each tag is a coloured chip - clicking selects it, clicking again deselects. Key behaviours:
  • Dynamic - only tags actually present in the currently open inventory appear. If no item in this inventory has the clothing tag, the clothing chip is hidden.
  • OR logic - items match if they have any of the active tags (not all of them).
  • Combines with rarity - tag filter and rarity filter intersect (AND). Tags within a side are OR; the two filter groups are AND.
  • Combines with search - text search runs on top of the tag-filtered set.
  • Persistent - filter selections survive closing and reopening the inventory within the same session. Left and right grids keep independent state.

Defining tags

Tags live in config.json under itemTags. Each entry needs a label and a colour:
config.json

Applying tags to an item

Add a tags array to any item in data/items.lua. Multiple tags allowed.
data/items.lua

Applying tags to a weapon

Identical pattern in data/weapons.lua. Weapons should always include the weapon tag plus a class tag:
data/weapons.lua
Tagging weapons with both weapon and their class lets players filter “all weapons” or narrow further to “all shotguns” with a single click.

Adding a custom tag

  1. Add the entry to config.jsonitemTags:
    config.json
  2. Tag the relevant items:
    data/items.lua
  3. Restart the resource. The new chip appears in the filter automatically whenever a tagged item is in view.

Removing or renaming a tag

  • Renaming a tag key requires updating every item/weapon that referenced the old key. Items with an orphan tag key simply ignore it.
  • Removing a tag from config.json hides the chip from the filter, but items still carry the orphan key in their tags array harmlessly.
Tags declared on items but not present in config.json are silently ignored by the UI. You can use this to keep “private” categorisation that doesn’t surface as a chip.