ArchiveXL: Tags

Summary

Published: ??? by manavortex Last documented update: April 21 2025 by LadyLea

This page will tell you about tags and how they can be used to influence item behaviour. It also teaches you how Adding Custom tags can help you conditionally un-hide items or add new features.

Wait, this is not what I want!

• Tags are used for calculating Garment Support score, see Garment Support: How does it work?

• There is an own page for Influencing other items

What do tags do?

Tags are a way to tell Cyberpunk that an item has certain properties and should behave in a certain way. This makes the game apply properties to your items, which can then be utilized by the game and ArchiveXL.

Base game tags

ArchiveXL tags

Base Game Tags and ArchiveXL Tags - Visual Guides

Root entity tags

There are a few tags that can be added to the root entity or in the .app file. Here's a list:

EmptyAppearance

This will hide an item under certain conditions. Add the following tag to the root entity:

EmptyAppearance:FPP

You have the following other options to achieve the same end:

force_Hair

A tag that forces hair to show up while wearing a head item. By default, head items turn hair invisible. By adding this tag to the root entity, you can override this process.

force_FlatFeet

A tag that forces female V's feet to be flat. Only works with a foot item as $base in the .yaml: use this if you're making flat shoes and don't want female V's feet to look as if she was wearing heels.

Footsteps: Setting footwear sounds

If you don't want your new boots to sound as if V was barefoot, add one of the following tags to the Root entity:

Boots
Heels
Sneakers
Stilettos
Metal_feet

Adding Custom tags

Custom tags let you set component chunk masks from the .xl file without the need of touching either .app or .ent file.

Why would I need this? partsOverrides exists!

1. PartsOverrides can't un-hide components for you. It can only hide them. If you want to load a different mesh (for example, a de-formed hakama when wearing a kimono or haori), then you're flat out of luck.

2. By being clever about your submeshes, you can offer different versions of your mesh (cropped! No arms! No legs), and users only need to install an .xl file! No need to have different meshes or even different .archive files.

Not convinced? Pity, but if you find a new use case for those things, do edit it in!

Example

Registering the tag

Add custom tags in your .xl file (not in your .yaml!)

overrides:
  tags:
    my_custom_unhiding_tag:
      my_hidden_component_name: {show: [0, 1, 2, 3]}
    my_HideSeamfix:
      t0_000_pma_base__full_seamfix: {hide: [0, 1, 2, 3]}

Connecting the tag with the item

Simply add the tag to your appearance's tags array near the bottom of the individual entries.

Making use of Custom Tags in your projects

This section will show an example how Custom Tags are utilized with Body Mods and AXL Clothes. This reference can also be applied for other projects.

Thanks to the development of Custom Tags; Hyst's Body Mods [EVB], [EBB-EBBRB], [EBBP-EBBPRB] [ANGEL], are now updated with a new feature Shapes Add-ons - which allows creators to make use of different chest states other than the default chest - either: Squish or Natural [EBBN]. These add-ons will replace the default chest look of the modded bodies, by adding a Visual Tag.

To make use of custom tags, one of the Visual Tags below must be included within your .app file information list:

• hyst_boobs_natural - To be used for [EBB-EBBRB], [EBBP-EBBPRB], [ANGEL]

• hyst_evb_boobs_natural - To be used for [EVB]

[this tag will load the existing natural chest shape that is available when FemV doesn't wear clothes]

OR

• hyst_boobs_squish- To be used for [EBB-EBBRB], [EBBP-EBBPRB], [ANGEL]

[this tag will load a squished chest shape that is ideal for tight garments such as bras or corsets]

The below example shows how the tag hyst_boobs_squish + other AXL Tags are being utilized together for an AXL garment + Body Mods that are making use of Custom Tags.