Meiker Wiki - User contributions [en]

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