Meiker Wiki - User contributions [en]

Layers/Dynamic

2026-04-21T18:42:59Z

Jm:

{{TagInfobox
|syntax=[dynamic]
|alias=[d]
|used_on=Category/Group children
}}

[[File:Dynamic Item.png|thumb]]

Dynamic is a tag you can use on an item, to create multi-layered items. Each direct child layer can be plain image layers or colorable layers (using [[Palette|[palette]]]), and each can carry its own additional tags to control color behavior, visibility syncing, [[Blend Modes|blend mode]], and more.

A [dynamic] group is not a category by itself — it lives ''inside'' a category folder tagged with [[Fixed|[fixed]]], [[Optional|[optional]]], or [[Mixed|[mixed]]].

==Usage==
The tag in a PSD file is written as '''[dynamic]''' or its short alias '''[d]'''. It does '''not''' take a value — writing `[dynamic:anything]` is an error.

Place the tag on a '''group folder''' that is a direct child of a category folder. The folder must have at least one child layer, and no more than '''64 children'''. Each child must be a flat image layer (no nested groups are allowed). Children can use any PSD blend mode and can also carry '''[[Palette|[palette]]]''' tags to make them colorable.

'''For example:'''

A category folder named `Hair [fixed]` contains a group named `Wavy Hair [dynamic]`. Inside that group are three image layers:

* '''Outlines''' — no tags. This layer holds the hair line art and is always drawn as-is.
* '''Highlights [palette]''' — tagged with `[palette]`, and given a blend mode (such as Screen or Overlay) in PSD. The player can independently pick a color for the highlights, letting them mix a base shade with a contrasting highlight.
* '''Hair Color [palette]''' — tagged with `[palette]`. The player can use the paintbrush to pick any color from the palette and the hair fills with that color.

Because all three layers sit inside the same `[dynamic]` group, they are treated as one combined item. The player sees a single entry in the Hair category and gets two paintbrush color pickers — one for the hair base and one for the highlights.

==Compatible tags==

Child layers of a [dynamic] group can carry the following tags:
* '''[[Palette|[palette]]]''' — makes the child colorable using the paintbrush.
* '''[[Color Link|[color-link:channel]]]''' — links the child's color to a global scope so colors sync across items.
* '''[[Removable|[removable]]]''' — adds a show/hide toggle button in the player UI for that child.
* '''[[Visibility Link|[visibility-link:scope]]]''' — syncs this child's visibility with others sharing the same scope.
* '''[[Visibility Group|[visibility-group:group]]]''' — within a [visibility-link] scope, makes groups mutually exclusive.
* '''[[Visible When Color In|[visible-when-color-in:palette]]]''' — shows this child only when the active color belongs to the named palette.
* '''[[Ui Hidden|[ui-hidden]]]''' — hides the paintbrush button for this child so it is selectable but not colorable directly.

==Additional Tags to Use with Dynamic==

The [dynamic] tag itself can be combined with '''[[Random|[random]]]''', '''[[Move|[move]]]''', '''[[Reference|[ref]]]''', '''[[Reference#Mirror|[mirror]]]''', '''[[Ui Hidden|[ui-hidden]]]''' and '''[[VFX|[vfx]]]''' on the same group folder. Most other category-level tags are blocked.

A [dynamic] item can be a child of a category that has the '''[[Enable Color Global|[enable-color-global:scope]]]''' tag. When it does, any color the player picks on one item automatically updates every other [dynamic], [[Color Picker|[color-picker]]], and [[Color|[color]]] item in that same scope.

<noinclude>
{{Tags}}
</noinclude>

Ui Hidden

2026-04-21T17:35:19Z

Jm:

{{TagInfobox
|syntax=[ui-hidden]
|alias=[ui-h]
|used_on=[[Dynamic|[dynamic]]] children • [[Layers/Items|items]]
|requires=[[Palette|[palette]]] • [[Color Picker|[color-picker]]]
}}

The '''ui-hidden''' tag hides the color picker (paintbrush) button for an item in the player UI without hiding the item itself. When applied to a child layer inside a [[dynamic|[dynamic]]] folder, the player can still browse and select that item, but the color-editing controls will not be shown for it. This is useful when a piece of artwork should be selectable but not colorable — for example, a non-recolorable accessory that lives alongside recolorable items in the same category.

{| style="width:100%"
|-
| style="width:33%;" | [[File:Without ui-hidden tag.png|thumb|none|Example of PSD (right) and Game (left) without the [ui-hidden] tag. When selecting the item in the game, a paintbrush appears to change the color of each palette layer.]]
| style="width:33%;" | [[File:With ui-hidden tag.png|thumb|none|If the [dynamic] layer has the [ui-hidden] tag, when selecting an item in the game, the paintbrush does not appear to select any color from any [palette] children.]]
| style="width:33%;" | [[File:With ui-hidden in palette.png|thumb|none|If the [ui-hidden] tag is used together with the [palette] tag, then only these will not appear in the paintbrush.]]
|}

==Usage==

The tag is written as '''[ui-hidden]''' or its short alias '''[ui-h]'''. It must be placed on a layer that is a '''direct child of a [dynamic] folder''' or on a layer inside a [[palette|[palette]]] group.

For a `[[Dynamic|[dynamic]]]` child, adding `[ui-hidden]` means the item still appears in the selection carousel, but no color selector is displayed when it is active.

For a `[[Palette|[palette]]]` child, `[ui-hidden]` removes the item from the color picker list. The exception is when `[removable]` is also present — in that case the item stays in the list with its visibility toggle intact, but still without the paintbrush button.

==Additional Tags to Use with Ui-Hidden==
'''[[Removable|[removable]]]''' — Combine with [ui-hidden] on a [palette] child to keep the visibility toggle available while still hiding the color picker. Without [removable], [ui-hidden] removes the item from the color picker (paintbrush) completely.

'''[[Dynamic|[dynamic]]]''' — The parent tag for the category folder that [ui-hidden] children belong to. Items inside [dynamic] that should not be colorable at paintbrush are the primary use case for [ui-hidden].

'''[[Color Picker|[color-picker]]]''' — If your uses the [color-picker] tag alongside [ui-hidden], is the equivalent of use [color-picker:hidden] to hide its paintbrush button.

<noinclude>
{{Tags}}
</noinclude>

Ui Hidden

2026-04-21T17:26:59Z

Jm:

{{TagInfobox
|syntax=[ui-hidden]
|alias=[ui-h]
|used_on=[[Dynamic|[dynamic]]] children • [[Layers/Items|items]]
|requires=[[Palette|[palette]]] • [[Color Picker|[color-picker]]]
}}

The '''ui-hidden''' tag hides the color picker (paintbrush) button for an item in the player UI without hiding the item itself. When applied to a child layer inside a [[dynamic|[dynamic]]] folder, the player can still browse and select that item, but the color-editing controls will not be shown for it. This is useful when a piece of artwork should be selectable but not colorable — for example, a non-recolorable accessory that lives alongside recolorable items in the same category.

==Usage==

[[File:Without ui-hidden tag.png|thumb|right|Example of PSD (right) and Game (left) without the [ui-hidden] tag. When selecting the item in the game, a paintbrush appears to change the color of each palette layer.]]

[[File:With ui-hidden tag.png|thumb|right|If the [dynamic] layer has the [ui-hidden] tag, when selecting an item in the game, the paintbrush does not appear to select any color from any [palette] children.]]

[[File:With ui-hidden in palette.png|thumb|right|If the [ui-hidden] tag is used together with the [palette] tag, then only these will not appear in the paintbrush.]]

The tag is written as '''[ui-hidden]''' or its short alias '''[ui-h]'''. It must be placed on a layer that is a '''direct child of a [dynamic] folder''' or on a layer inside a [[palette|[palette]]] group.

For a `[[Dynamic|[dynamic]]]` child, adding `[ui-hidden]` means the item still appears in the selection carousel, but no color selector is displayed when it is active.

For a `[[Palette|[palette]]]` child, `[ui-hidden]` removes the item from the color picker list. The exception is when `[removable]` is also present — in that case the item stays in the list with its visibility toggle intact, but still without the paintbrush button.

==Additional Tags to Use with Ui-Hidden==
'''[[Removable|[removable]]]''' — Combine with [ui-hidden] on a [palette] child to keep the visibility toggle available while still hiding the color picker. Without [removable], [ui-hidden] removes the item from the color picker (paintbrush) completely.

'''[[Dynamic|[dynamic]]]''' — The parent tag for the category folder that [ui-hidden] children belong to. Items inside [dynamic] that should not be colorable at paintbrush are the primary use case for [ui-hidden].

'''[[Color Picker|[color-picker]]]''' — If your uses the [color-picker] tag alongside [ui-hidden], is the equivalent of use [color-picker:hidden] to hide its paintbrush button.

<noinclude>
{{Tags}}
</noinclude>

File:With ui-hidden in palette.png

2026-04-21T17:26:27Z

Jm:

If the [ui-hidden] tag is used together with the [palette] tag, then only these will not appear in the paintbrush.

Ui Hidden

2026-04-21T17:23:26Z

Jm:

{{TagInfobox
|syntax=[ui-hidden]
|alias=[ui-h]
|used_on=[[Dynamic|[dynamic]]] children • [[Layers/Items|items]]
|requires=[[Palette|[palette]]] • [[Color Picker|[color-picker]]]
}}

The '''ui-hidden''' tag hides the color picker (paintbrush) button for an item in the player UI without hiding the item itself. When applied to a child layer inside a [[dynamic|[dynamic]]] folder, the player can still browse and select that item, but the color-editing controls will not be shown for it. This is useful when a piece of artwork should be selectable but not colorable — for example, a non-recolorable accessory that lives alongside recolorable items in the same category.

==Usage==

[[File:Without ui-hidden tag.png|thumb|right|Example of PSD (right) and Game (left) without the [ui-hidden] tag. When selecting the item in the game, a paintbrush appears to change the color of each palette layer.]]

[[File:With ui-hidden tag.png|thumb|right|If the [dynamic] layer has the [ui-hidden] tag, when selecting an item in the game, the paintbrush does not appear to select any color from any [palette] children.]]

The tag is written as '''[ui-hidden]''' or its short alias '''[ui-h]'''. It must be placed on a layer that is a '''direct child of a [dynamic] folder''' or on a layer inside a [[palette|[palette]]] group.

For a `[[Dynamic|[dynamic]]]` child, adding `[ui-hidden]` means the item still appears in the selection carousel, but no color selector is displayed when it is active.

For a `[[Palette|[palette]]]` child, `[ui-hidden]` removes the item from the color picker list. The exception is when `[removable]` is also present — in that case the item stays in the list with its visibility toggle intact, but still without the paintbrush button.

==Additional Tags to Use with Ui-Hidden==
'''[[Removable|[removable]]]''' — Combine with [ui-hidden] on a [palette] child to keep the visibility toggle available while still hiding the color picker. Without [removable], [ui-hidden] removes the item from the color picker (paintbrush) completely.

'''[[Dynamic|[dynamic]]]''' — The parent tag for the category folder that [ui-hidden] children belong to. Items inside [dynamic] that should not be colorable at paintbrush are the primary use case for [ui-hidden].

'''[[Color Picker|[color-picker]]]''' — If your uses the [color-picker] tag alongside [ui-hidden], is the equivalent of use [color-picker:hidden] to hide its paintbrush button.

<noinclude>
{{Tags}}
</noinclude>

File:With ui-hidden tag.png

2026-04-21T17:20:51Z

Jm:

Example of PSD (right) and Game (left) with the [ui-hidden] tag. When selecting an item in the game, the paintbrush does not appear to select any color from any palette.

Ui Hidden

2026-04-21T17:18:32Z

Jm:

{{TagInfobox
|syntax=[ui-hidden]
|alias=[ui-h]
|used_on=[[Dynamic|[dynamic]]] children • [[Layers/Items|items]]
|requires=[[Palette|[palette]]] • [[Color Picker|[color-picker]]]
}}

The '''ui-hidden''' tag hides the color picker (paintbrush) button for an item in the player UI without hiding the item itself. When applied to a child layer inside a [[dynamic|[dynamic]]] folder, the player can still browse and select that item, but the color-editing controls will not be shown for it. This is useful when a piece of artwork should be selectable but not colorable — for example, a non-recolorable accessory that lives alongside recolorable items in the same category.

==Usage==

[[File:Without ui-hidden tag.png|thumb|right|Example of PSD (right) and Game (left) without the [ui-hidden] tag. When selecting the item in the game, a paintbrush appears to change the color of each palette layer.]]

The tag is written as '''[ui-hidden]''' or its short alias '''[ui-h]'''. It must be placed on a layer that is a '''direct child of a [dynamic] folder''' or on a layer inside a [[palette|[palette]]] group.

For a `[[Dynamic|[dynamic]]]` child, adding `[ui-hidden]` means the item still appears in the selection carousel, but no color selector is displayed when it is active.

For a `[[Palette|[palette]]]` child, `[ui-hidden]` removes the item from the color picker list. The exception is when `[removable]` is also present — in that case the item stays in the list with its visibility toggle intact, but still without the paintbrush button.

==Additional Tags to Use with Ui-Hidden==
'''[[Removable|[removable]]]''' — Combine with [ui-hidden] on a [palette] child to keep the visibility toggle available while still hiding the color picker. Without [removable], [ui-hidden] removes the item from the color picker (paintbrush) completely.

'''[[Dynamic|[dynamic]]]''' — The parent tag for the category folder that [ui-hidden] children belong to. Items inside [dynamic] that should not be colorable at paintbrush are the primary use case for [ui-hidden].

'''[[Color Picker|[color-picker]]]''' — If your uses the [color-picker] tag alongside [ui-hidden], is the equivalent of use [color-picker:hidden] to hide its paintbrush button.

<noinclude>
{{Tags}}
</noinclude>

File:Without ui-hidden tag.png

2026-04-21T17:16:31Z

Jm:

Example of PSD (right) and the Game (left) without the [ui-hidden] tag. When selecting the item in the game, a paintbrush appears to change the color of each palette layer.

Ui Hidden

2026-04-21T15:05:27Z

Jm:

{{TagInfobox
|syntax=[ui-hidden]
|alias=[ui-h]
|used_on=[[Dynamic|[dynamic]]] children • [[Layers/Items|items]]
|requires=[[Palette|[palette]]] • [[Color Picker|[color-picker]]]
}}

The '''ui-hidden''' tag hides the color picker (paintbrush) button for an item in the player UI without hiding the item itself. When applied to a child layer inside a [[dynamic|[dynamic]]] folder, the player can still browse and select that item, but the color-editing controls will not be shown for it. This is useful when a piece of artwork should be selectable but not colorable — for example, a non-recolorable accessory that lives alongside recolorable items in the same category.

==Usage==
The tag is written as '''[ui-hidden]''' or its short alias '''[ui-h]'''. It must be placed on a layer that is a '''direct child of a [dynamic] folder''' or on a layer inside a [[palette|[palette]]] group.

For a `[[Dynamic|[dynamic]]]` child, adding `[ui-hidden]` means the item still appears in the selection carousel, but no color selector is displayed when it is active.

For a `[[Palette|[palette]]]` child, `[ui-hidden]` removes the item from the color picker list. The exception is when `[removable]` is also present — in that case the item stays in the list with its visibility toggle intact, but still without the paintbrush button.

==Additional Tags to Use with Ui-Hidden==
'''[[Removable|[removable]]]''' — Combine with [ui-hidden] on a [palette] child to keep the visibility toggle available while still hiding the color picker. Without [removable], [ui-hidden] removes the item from the color picker (paintbrush) completely.

'''[[Dynamic|[dynamic]]]''' — The parent tag for the category folder that [ui-hidden] children belong to. Items inside [dynamic] that should not be colorable at paintbrush are the primary use case for [ui-hidden].

'''[[Color Picker|[color-picker]]]''' — If your uses the [color-picker] tag alongside [ui-hidden], is the equivalent of use [color-picker:hidden] to hide its paintbrush button.

<noinclude>
{{Tags}}
</noinclude>

Visibility When Color In

2026-04-21T14:42:21Z

Jm:

{{TagInfobox
|syntax=[Visibility When Color In]
|alias=[vwci]
|used_on=[[Dynamic|[dynamic]]] children
|requires=[[Color Link]]
}}

Visibility When Color In is a complex tag, that is used to show a specific layer, only when the linked color, has chosen a color that matches one of the color options of the visibility-when-color-in, palette's colors.

The visible-when-color-in tag makes a layer automatically show or hide based on which color is currently active on itself item. When the active color matches one of the colors in the named palette, the layer becomes visible. When a color outside that palette is selected, the layer hides itself. This lets you create variants — like different scale shapes, pattern overlays, or alternate details — that only appear for specific color choices.

==Usage==
The tag in a PSD file is written as '''[visible-when-color-in:paletteName]''', where '''paletteName''' is the name of a palette defined elsewhere in the PSD. It can also be written as '''[vwci:paletteName]'''. The palette name is required and must match an existing palette's name exactly.

'''[visible-when-color-in] must always be used alongside [[Color Link|[color-link]]] on the same layer.''' The layer also cannot have any children of its own.

'''Example 1:'''

For example, create 2 palettes:
[local-palette:Shirt_Colors] (including the color FF0000 and 0000FF)
[local-palette:Red_or_Blue] (with only the colors FF0000 and 0000FF)

Then in the shirts, have a layer that uses "Shirt Colors", and another layer that has "Red or Blue", these two layers can be linked with the same [[Color Link]], for example:

Left Shirt [palette:Shirt_Colors][color-link:test]
Right Shirt [color-link:test][visibility-when-color-in:Red_or_Blue]

When a user selects the Left Shirt layer, and colors it red or blue, the right shirt layer will become visible

'''Example 2:'''

A mermaid tail has a `[local-palette:colours]` with 9 colors. A "spikey scales" layer uses `[color-link:scales][visible-when-color-in:spike]`, and `[local-palette:spike]` contains colors 1–3 from the main palette. A "round scales" layer uses `[color-link:scales][visible-when-color-in:round]`, and `[local-palette:round]` contains colors 4–6. When the player picks colors 1–3, spikey scales appear. Colors 4–6 show round scales. Colors 7–9 show neither.

==Additional Tags to Use with Visible-When-Color-In==
'''[[Color Link|[color-link]]]''' — Required. [visible-when-color-in] will not work without [color-link] on the same layer.

Cannot be combined with '''[[Visibility Link|[visibility-link]]]'''.

{{Tags}}

Palette

2026-04-20T17:58:41Z

Jm: Created page with "{{TagInfobox |syntax=[palette:{id}] |alias=[pal:{id}] |used_on=[dynamic] children }} [[File:Palette example.jpg|thumb|right|On the right is an example of how the [palette] tag appears in the PSD file; on the left is how it will look in the game.]] The palette tag turns a child layer of a [dynamic] group into a colorable image item. When the player loads, the engine reads the layer's pixels to detect the most prominent color and snaps it to the n..."

{{TagInfobox
|syntax=[palette:{id}]
|alias=[pal:{id}]
|used_on=[[Dynamic|[dynamic]]] children
}}

[[File:Palette example.jpg|thumb|right|On the right is an example of how the [palette] tag appears in the PSD file; on the left is how it will look in the game.]]

The palette tag turns a child layer of a [[dynamic|[dynamic]]] group into a colorable image item. When the player loads, the engine reads the layer's pixels to detect the most prominent color and snaps it to the nearest color in the active palette — that becomes the layer's default active color. In the player, the user can then pick any color from the palette and the layer recolors to match. Without [palette], a child of [dynamic] is a plain image with no color behavior.

==Usage==
The tag is written as '''[palette]''' or '''[palette:paletteName]'''. The alias is '''[pal]''' or '''[pal:paletteName]'''.

When written without a value, the layer uses the '''default''' built-in palette. To assign a specific palette, add the palette name after a colon: '''[palette:cottagecore]''', '''[palette:skintones]''', etc. The name must match either one of the built-in palettes (barbiecore, cottagecore, darkmori, goth, scene, basic, skintones) or a custom palette defined in the PSD via '''[[Local Palette|[local-palette:name]]]'''.

===Built-in Palettes===
{| class="wikitable"
! Name !! Colors
|-
| barbiecore
| [[File:Barbiecore-colors.png|frameless|x20px]]
|-
| cottagecore
| [[File:Cottagecore-colors.png|frameless|x20px]]
|-
| darkmori
| [[File:Darkmori-colors.png|frameless|x20px]]
|-
| goth
| [[File:Goth-colors.png|frameless|x20px]]
|-
| scene
| [[File:Scene-colors.png|frameless|x20px]]
|-
| basic
| [[File:Basic-colors.png|frameless|x20px]]
|-
| skintones
| [[File:Skintones-colors.png|frameless|x20px]]
|}

The tag must be placed on a '''direct child layer of a [dynamic] group'''. The layer must have no children of its own and must be an image layer.

'''Example:''' A hair group has `[dynamic]`. It has child layers: '''Hair Base''' and '''Hair Highlights'''. Tag '''Hair Base''' with `[palette:basic]` so the user can pick a base hair color. Tag '''Hair Highlights''' with `[palette:barbiecore]` as well so its highlight tones are independently colorable. Both layers recolor separately, letting the player mix a base shade with a contrasting highlight.

==Grande Palette==
[[File:Grande Palette.jpg|thumb|right|This is how the Grande Palette modal looks when the user clicks on the color wheel button.]]
The '''Grande Palette''' is a premium color picker feature that gives players access to a full color wheel instead of being limited to the preset palette swatches. When enabled, a color wheel button appears at the top of the color selector in the player UI. Clicking it opens a modal with a hue/saturation wheel and a hex input, letting the player pick any arbitrary color and apply it to the `[palette]` layer.

==Compatible tags==
'''[palette]''' can be combined with the following tags on the same layer:
* '''[[Color Link|[color-link:channel]]]''' — links the layer to a global color scope so color picks sync across items.
* '''[[Removable|[removable]]]''' — adds a visibility toggle button in the player UI.
* '''[[Visibility Link|[visibility-link:scope]]]''' — syncs visibility with other items sharing the same scope.
* '''[[Visibility Group|[visibility-group:group]]]''' — makes items in the same visibility-link scope mutually exclusive.
* '''[[Ui Hidden|[ui-hidden]]]''' — keeps the layer active in color logic without showing it as a selectable entry.

It '''can't''' be combined with tags other than the above.

==Additional Tags to Use with Palette==
'''[[Color Link|[color-link]]]''' — Link the palette layer to a color channel so other layers in the same scope stay in sync when the user picks a color.

'''[[Enable Color Global|[enable-color-global]]]''' — Apply to the parent category to activate cross-item color syncing for all [palette] (and [color-picker]/[color]) layers within it.

'''[[Visible When Color In|[visible-when-color-in]]]''' — Use on layers (alongside [color-link]) to show or hide alternate details based on which palette color is currently active.

'''[[Local Palette|[local-palette:name]]]''' — Define a custom set of colors in the PSD for [palette] to reference by name.

<noinclude>
{{Tags}}
</noinclude>

File:Grande Palette.jpg

2026-04-20T17:53:51Z

Jm:

Grande Palette

Visibility Link

2026-04-20T17:38:26Z

Jm:

{{TagInfobox
|syntax=[visibility-link:{id}]
|alias=[vl:{id}] • [v-link:{id}]
|used_on=[[Dynamic|[dynamic]]] children
}}
[[File:Visibility-link tag.png|thumb|right]]
The visibility-link tag links the visibility of multiple items across different [[dynamic|[dynamic]]] layers so they stay in sync. When the player toggles one linked item's visibility, all other items that share the same scope name will mirror that change. This is useful for keeping visually related pieces — spread across separate category groups — behaving as one unit.

Items tagged with [visibility-link] also benefit from the same behavior as [[removable|[removable]]]: they are not automatically forced visible, so their initial visibility state and player toggles are respected.

==Usage==
The tag in a PSD file is written as '''[visibility-link:scopeName]''', where '''scopeName''' is a name you choose to linked items together. It can also be written as '''[vl:scopeName]''' or '''[v-link:scopeName]'''. The scope name is required — the tag will not work without a value.

It must be placed on layers that are '''direct children of a [dynamic] folder'''. Any items across any categories can share the same scope name, and they will all stay in sync.

For example, if you have a sword handle in one `[dynamic]` category and a sword blade in another, tagging both with `[visibility-link:sword]` means toggling one will automatically toggle the other.

==Additional Tags to Use with Visibility-Link==
'''[[Visibility Group|[visibility-group]]]''' — Extends [visibility-link] with mutually exclusive groups. Items in the same scope but different groups will hide each other when one becomes visible. '''[visibility-group] requires [visibility-link] to be present.'''

Cannot be combined with '''[[Visible When Color In|[visible-when-color-in]]]'''.

<noinclude>
{{Tags}}
</noinclude>

File:Palette example.jpg

2026-04-20T17:28:41Z

Jm:

palette tag example

File:Skintones-colors.png

2026-04-20T16:43:26Z

Jm:

Skintones palette colors

File:Basic-colors.png

2026-04-20T16:42:29Z

Jm:

Basic palette colors

File:Scene-colors.png

2026-04-20T16:41:30Z

Jm:

Scene palette colors

File:Goth-colors.png

2026-04-20T16:38:27Z

Jm:

Goth palette colors

File:Darkmori-colors.png

2026-04-20T16:37:34Z

Jm:

Darkmori palette colors

File:Cottagecore-colors.png

2026-04-20T16:36:35Z

Jm:

Cottagecore palette colors

File:Barbiecore-colors.png

2026-04-20T16:33:58Z

Jm:

barbiecore palette colors

Enable Color Global

2026-04-17T21:05:46Z

Jm: Created page with "The enable-color-global tag links the children of a category so they all stay in sync with each other, and with any other categories that share the same scope name. When the player picks a color on any item inside a tagged category, every other item under the same scope automatically updates to match. This is useful when a character has multiple body parts spread across separate category groups that should always share the same color. ==Usage== The tag is written as '''..."

The enable-color-global tag links the children of a category so they all stay in sync with each other, and with any other categories that share the same scope name. When the player picks a color on any item inside a tagged category, every other item under the same scope automatically updates to match. This is useful when a character has multiple body parts spread across separate category groups that should always share the same color.

==Usage==
The tag is written as '''[enable-color-global:scopeName]''', where '''scopeName''' is a name you choose to tie categories together. It can also be written as '''[cg:scopeName]''' or '''[color-global:scopeName]'''. The scope name is optional, but a named scope is required when you want two or more categories to share the same color state.

The tag must be placed on a '''category folder layer''', alongside one of the category type tags: [[fixed|[fixed]]], [[optional|[optional]]], or `[[mixed|[mixed]]]`. It applies to all children of that category that carry a [[Color Picker|[color-picker]]], [[color|[color]]], or [[dynamic|[dynamic]]] tag.

For example, if a "Body" category and an "Arms" category should always display the same active color, tag both category folders with `[enable-color-global:skin]`. Selecting a color swatch in either category will immediately update the other.

==Additional Tags to Use with Enable-Color-Global==
'''[[Color Picker|[color-picker]]]''' — A layer item that lets the player choose one color from a fixed set of swatches. When a `[color-picker]` item sits inside a category tagged with `[enable-color-global:scopeName]`, selecting a swatch also updates every other item registered under the same scope.

'''[[color|[color]]]''' — A layer item that represents a single color swatch, where the layer's name is the color value in RGB hex format (e.g., `#FF00FF`). When a `[color]` item sits inside a category tagged with `[enable-color-global:scopeName]`, selecting it also updates every other item registered under the same scope.

'''[[dynamic|[dynamic]]]''' — A layer item that renders color through [[palette|[palette]]] children. When a `[dynamic]` item sits inside a category tagged with `[enable-color-global:scopeName]`, the engine locates each child tagged with `[palette]` and registers it as a member of the global color scope. Selecting a color on any linked item in the scope will update the matching palette child inside every `[dynamic]` item that shares the same scope name.

<noinclude>
{{Tags}}
</noinclude>

Advanced Properties/Ui Category Display

2026-04-17T19:33:25Z

Jm:

{{TagInfobox
|syntax=[advanced-properties] / [ui.categories.display:none]
|used_on=[advanced-properties] children
}}

[[File:Advanced-property tag.png|thumb|right]]
[[File:Ui.categories.display tag.jpg|thumb|right]]

The advanced-properties tag marks a group layer as a container for invisible configuration layers that control advanced player behavior. It does not appear in the player's customization menu — instead, its child layers each carry a single configuration tag that tells the player how to behave. Currently the only supported child property is [[ui.categories.display|[ui.categories.display]]], which controls whether the category selection menu is shown.

==Usage==
The tag is written as '''[advanced-properties]''' on a PSD group layer. It must be placed at the root level of the PSD, not inside another folder. It cannot be combined with any other tags on the same layer, and the group must contain at least one child.

Each child of the '''[advanced-properties]''' group must be an '''empty layer''' (no pixels, no sub-folders) with exactly one configuration tag. The only currently valid child tag is '''[ui.categories.display:none]'''.

For example: create a group named `my settings [advanced-properties]`. Inside it, place a blank empty layer named `hide menu [ui.categories.display:none]`. This will suppress the category navigation bar in the player.

==Additional Tags to Use with Advanced-Properties==
'''[ui.categories.display]''' — The only tag currently valid as a child of [advanced-properties]. Place it on an empty layer inside the group to configure player UI behavior.

<noinclude>
{{Tags}}
</noinclude>

Advanced Properties/Ui Category Display

2026-04-17T19:33:03Z

Jm:

{{TagInfobox
|syntax=[advanced-properties][ui.categories.display:none]
|used_on=[advanced-properties] children
}}

[[File:Advanced-property tag.png|thumb|right]]
[[File:Ui.categories.display tag.jpg|thumb|right]]

The advanced-properties tag marks a group layer as a container for invisible configuration layers that control advanced player behavior. It does not appear in the player's customization menu — instead, its child layers each carry a single configuration tag that tells the player how to behave. Currently the only supported child property is [[ui.categories.display|[ui.categories.display]]], which controls whether the category selection menu is shown.

==Usage==
The tag is written as '''[advanced-properties]''' on a PSD group layer. It must be placed at the root level of the PSD, not inside another folder. It cannot be combined with any other tags on the same layer, and the group must contain at least one child.

Each child of the '''[advanced-properties]''' group must be an '''empty layer''' (no pixels, no sub-folders) with exactly one configuration tag. The only currently valid child tag is '''[ui.categories.display:none]'''.

For example: create a group named `my settings [advanced-properties]`. Inside it, place a blank empty layer named `hide menu [ui.categories.display:none]`. This will suppress the category navigation bar in the player.

==Additional Tags to Use with Advanced-Properties==
'''[ui.categories.display]''' — The only tag currently valid as a child of [advanced-properties]. Place it on an empty layer inside the group to configure player UI behavior.

<noinclude>
{{Tags}}
</noinclude>

Advanced Properties/Ui Category Display

2026-04-17T19:32:27Z

Jm:

{{TagInfobox
|syntax=[advanced-properties][ui.categories.display]
|used_on=[advanced-properties] children
}}

[[File:Advanced-property tag.png|thumb|right]]
[[File:Ui.categories.display tag.jpg|thumb|right]]

The advanced-properties tag marks a group layer as a container for invisible configuration layers that control advanced player behavior. It does not appear in the player's customization menu — instead, its child layers each carry a single configuration tag that tells the player how to behave. Currently the only supported child property is [[ui.categories.display|[ui.categories.display]]], which controls whether the category selection menu is shown.

==Usage==
The tag is written as '''[advanced-properties]''' on a PSD group layer. It must be placed at the root level of the PSD, not inside another folder. It cannot be combined with any other tags on the same layer, and the group must contain at least one child.

Each child of the '''[advanced-properties]''' group must be an '''empty layer''' (no pixels, no sub-folders) with exactly one configuration tag. The only currently valid child tag is '''[ui.categories.display:none]'''.

For example: create a group named `my settings [advanced-properties]`. Inside it, place a blank empty layer named `hide menu [ui.categories.display:none]`. This will suppress the category navigation bar in the player.

==Additional Tags to Use with Advanced-Properties==
'''[ui.categories.display]''' — The only tag currently valid as a child of [advanced-properties]. Place it on an empty layer inside the group to configure player UI behavior.

<noinclude>
{{Tags}}
</noinclude>

Advanced Properties/Ui Category Display

2026-04-17T19:29:57Z

Jm:

[[File:Advanced-property tag.png|thumb|right]]
[[File:Ui.categories.display tag.jpg|thumb|right]]

The advanced-properties tag marks a group layer as a container for invisible configuration layers that control advanced player behavior. It does not appear in the player's customization menu — instead, its child layers each carry a single configuration tag that tells the player how to behave. Currently the only supported child property is [[ui.categories.display|[ui.categories.display]]], which controls whether the category selection menu is shown.

==Usage==
The tag is written as '''[advanced-properties]''' on a PSD group layer. It must be placed at the root level of the PSD, not inside another folder. It cannot be combined with any other tags on the same layer, and the group must contain at least one child.

Each child of the '''[advanced-properties]''' group must be an '''empty layer''' (no pixels, no sub-folders) with exactly one configuration tag. The only currently valid child tag is '''[ui.categories.display:none]'''.

For example: create a group named `my settings [advanced-properties]`. Inside it, place a blank empty layer named `hide menu [ui.categories.display:none]`. This will suppress the category navigation bar in the player.

==Additional Tags to Use with Advanced-Properties==
'''[ui.categories.display]''' — The only tag currently valid as a child of [advanced-properties]. Place it on an empty layer inside the group to configure player UI behavior.

<noinclude>
{{Tags}}
</noinclude>

Advanced Properties/Ui Category Display

2026-04-17T19:28:06Z

Jm: Created page with " right right The advanced-properties tag marks a group layer as a container for invisible configuration layers that control advanced player behavior. It does not appear in the player's customization menu — instead, its child layers each carry a single configuration tag that tells the player how to behave. Currently the only supported child property is ui.categories.display|[ui.cate..."

[[File:Advanced-property tag.png|thumb|right]]
[[File:Ui.categories.display tag.jpg|thumb|right]]

The advanced-properties tag marks a group layer as a container for invisible configuration layers that control advanced player behavior. It does not appear in the player's customization menu — instead, its child layers each carry a single configuration tag that tells the player how to behave. Currently the only supported child property is [[ui.categories.display|[ui.categories.display]]], which controls whether the category selection menu is shown.

==Usage==
The tag is written as '''[advanced-properties]''' on a PSD group layer. It must be placed at the root level of the PSD, not inside another folder. It cannot be combined with any other tags on the same layer, and the group must contain at least one child.

Each child of the '''[advanced-properties]''' group must be an '''empty layer''' (no pixels, no sub-folders) with exactly one configuration tag. The only currently valid child tag is '''[ui.categories.display:none]'''.

For example: create a group named `my settings [advanced-properties]`. Inside it, place a blank empty layer named `hide menu [ui.categories.display:none]`. This will suppress the category navigation bar in the player.

==Additional Tags to Use with Advanced-Properties==
'''[[ui.categories.display|[ui.categories.display]]]''' — The only tag currently valid as a child of [advanced-properties]. Place it on an empty layer inside the group to configure player UI behavior.

<noinclude>
{{Tags}}
</noinclude>

File:Ui.categories.display tag.jpg

2026-04-17T19:27:07Z

Jm:

ui.categories.display tag example

File:Advanced-property tag.png

2026-04-17T19:25:59Z

Jm:

advanced-property tag example

Visibility Group

2026-04-17T18:34:12Z

Jm: Created page with "thumb The visibility-group tag subdivides a [visibility-link] scope into named groups, making them mutually exclusive. When items share the same [visibility-link] scope but belong to different [visibility-group] names, showing one group will automatically hide all other groups in that scope. Items within the same group remain synchronized and show or hide together. This lets you build "pick one" style setups — for..."

[[File:Visibility-group tag.png|thumb]]
The visibility-group tag subdivides a [[Visibility_Link|[visibility-link]]] scope into named groups, making them mutually exclusive. When items share the same [visibility-link] scope but belong to different [visibility-group] names, showing one group will automatically hide all other groups in that scope. Items within the same group remain synchronized and show or hide together.

This lets you build "pick one" style setups — for example, different fur patterns or scale types — where selecting one variant automatically deselects the others, all while keeping separate [[dynamic|[dynamic]]] categories in sync via a shared [visibility-link] scope.

==Usage==
The tag in a PSD file is written as '''[visibility-group:groupName]''', where '''groupName''' is the name of the group within the scope. It can also be written as '''[vg:groupName]''' or '''[v-group:groupName]'''. The group name is required.

'''[visibility-group] must always be used alongside [visibility-link:scopeName] on the same layer.''' The group name only matters within the same scope — identical group names in different [visibility-link] scopes are completely independent of each other.

For example: three `[dynamic]` children all have `[visibility-link:FurPattern]`. One has `[visibility-group:stripes]`, one has `[visibility-group:spots]`, and one has `[visibility-group:rosette]`. When the player makes one visible, the other two are automatically hidden.

==Additional Tags to Use with Visibility-Group==
'''[[Visibility Link|[visibility-link]]]''' — Required. [visibility-group] has no effect without [visibility-link] on the same layer.

<noinclude>
{{Tags}}
</noinclude>

File:Visibility-group tag.png

2026-04-17T18:31:11Z

Jm:

visibility-group tag example

Visibility Link

2026-04-17T18:17:19Z

Jm: Created page with "right The visibility-link tag links the visibility of multiple items across different [dynamic] layers so they stay in sync. When the player toggles one linked item's visibility, all other items that share the same scope name will mirror that change. This is useful for keeping visually related pieces — spread across separate category groups — behaving as one unit. Items tagged with [visibility-link] also benefit fro..."

[[File:Visibility-link tag.png|thumb|right]]
The visibility-link tag links the visibility of multiple items across different [[dynamic|[dynamic]]] layers so they stay in sync. When the player toggles one linked item's visibility, all other items that share the same scope name will mirror that change. This is useful for keeping visually related pieces — spread across separate category groups — behaving as one unit.

Items tagged with [visibility-link] also benefit from the same behavior as [[removable|[removable]]]: they are not automatically forced visible, so their initial visibility state and player toggles are respected.

==Usage==
The tag in a PSD file is written as '''[visibility-link:scopeName]''', where '''scopeName''' is a name you choose to linked items together. It can also be written as '''[vl:scopeName]''' or '''[v-link:scopeName]'''. The scope name is required — the tag will not work without a value.

It must be placed on layers that are '''direct children of a [dynamic] folder'''. Any items across any categories can share the same scope name, and they will all stay in sync.

For example, if you have a sword handle in one `[dynamic]` category and a sword blade in another, tagging both with `[visibility-link:sword]` means toggling one will automatically toggle the other.

==Additional Tags to Use with Visibility-Link==
'''[[visibility-group|[visibility-group]]]''' — Extends [visibility-link] with mutually exclusive groups. Items in the same scope but different groups will hide each other when one becomes visible. '''[visibility-group] requires [visibility-link] to be present.'''

Cannot be combined with '''[[visible-when-color-in|[visible-when-color-in]]]'''.

<noinclude>
{{Tags}}
</noinclude>

File:Visibility-link tag.png

2026-04-17T18:11:08Z

Jm:

visibility-link tag example

Removable

2026-04-17T17:40:53Z

Jm:

[[File:Removable tag.png|thumb|right]]
The removable tag allows the end user to control the visibility of an individual layer through a toggle button in the player UI. When applied, the item in the player's selection list will have a visibility button next to paintbrush that the user can click to show or hide that layer at will. Unlike a layer that is simply hidden in the PSD, a removable layer's visibility is player-controlled and persists through interactions during the session.

Without this tag, children of a [[dynamic|[dynamic]]] layer are always forced visible when selected. With [removable], the layer respects its initial visibility state and the player can toggle it freely.

==Usage==
The tag in a PSD file is written as '''[removable]'''. It can also be written as '''[rm]'''. It must be placed on a layer that is a '''direct child of a [dynamic] folder'''. It cannot be placed on a category or on any other layer type.

For example, if you have a character with optional accessories drawn in a `[dynamic]` folder, tagging one of the item layers with `[removable]` will allow the player to turn that accessory on and off without it being forced visible every time.

==Additional Tags to Use with Removable==
'''[[visibility-link|[visibility-link]]]''' — Like [removable], [visibility-link] also prevents the automatic forced-visible override. If you need the item's visibility to be synced with another item across categories, use [visibility-link] instead of or alongside [removable].

'''[[ui-hidden|[ui-hidden]]]''' — Can be combined with [removable] if you want to keep a layer's paintbrush hidden but not its visibility toggle.

<noinclude>
{{Tags}}
</noinclude>

File:Removable tag.png

2026-04-17T17:38:49Z

Jm:

Example of removable tag