Modding guide

Materials, textures and dye regions

14 min readASA DevKit as of November 2026 (UE 5.8.1); ASE where noted

Your mesh gets a material that looks like ARK and takes dye like ARK. You won't build a material from scratch. You make an instance of a Wildcard master material and plug in your textures. Then you paint a mask so players can dye it. The first one takes an afternoon, mostly on the mask.

  • You'll make: a material instance with your textures, dye regions that work in game, and glow if you want it
  • Time: an afternoon the first time; the mask is most of it
  • Level: intermediate (you've imported a mesh)
  • You'll need: your mesh imported (Bringing in your own meshes), its textures, and a vanilla asset like yours

How ARK materials work

Three words first:

  • A master material holds the shader graph. ARK has a handful per kind of asset: creatures, equipment, structures, clothing.
  • A material instance is a child of a master. It can only change the parameters the master exposes: textures, colors, numbers and on/off switches. That's what you make.
  • A colorization mask is a texture whose colors mark the dye regions. The game reads it and tints each region.

An instance of a vanilla master gets ARK's lighting, damage, dye and highlight features for free. A material of your own loses them. Modders also find it often renders differently in the cooked game.

The process

  1. Find a vanilla asset like yours and look at its material. Open the material and follow Parent up to a master. That chain tells you what to use.

    Show me how

    The parents vanilla content uses most. The ASA ones live in /Game/ASA/CoreMaterials/MasterMaterials/MIC/, the older ones in /Game/PrimalEarth/CoreMaterials/MasterMaterials/MIC/.

    You're making Parent to start from Its master
    Creature skin MI_ASA_Dino (the Rex) MM_ASA_Dino
    Fur or feathers MI_ASA_Dino_Fur, MI_ASA_Dino_Feather MM_ASA_Dino_Fur
    Creature eyes MI_Dino_Eye_Refractive MM_Dino_Eye_Refractive
    Weapon, tool, item MI_ASA_Equipment, or MM_Equipment_Metallic_Colorized_MIC (the older one most weapons use) MM_ASA_Equipment, MM_Equipment
    Saddle MM_Equipment_Metallic_Colorized_MIC MM_Equipment
    Armor and clothing MM_Clothing_NoMetallic_Colorized_MIC, MM_Clothing_Metallic_Colorized_MIC MM_Clothing
    Building pieces the structure kits: MI_StructureKit_A (wood and stone), _Metal, _Thatch, _Tek MM_StructureKit_*
    Other structures MM_Structure_Metallic_Colorized_MIC, MM_Structure_NoMetallic_Colorized_MIC MM_Structure
    Item icon the item's own icon material, such as HUD_SwordForged_Colorize_MIC HUD_Colorized_Paint

    I counted the parents of the vanilla instances. The older masters are still common: MM_Equipment sits under half the weapon instances, MM_Clothing under half the clothing ones, and MM_Structure under a third of the structure ones. Creature skins mostly use the ASA masters.

  2. Make an instance of that parent in your mod folder. Right-click the parent → Create Material Instance. Move it into your mod folder. Never edit the vanilla parent.

    Show me how
    • Name it after your asset: MI_MyChest.
    • If the vanilla asset's own instance is closer to what you want, make a child of that instead. The Rex's skin is an instance of MI_ASA_Dino; a child of the Rex's instance keeps its detail layers.
    • Everything you made must live in your mod folder. Referencing vanilla parents is fine (References outside your mod).
  3. Import your textures with the right settings. Most texture problems come from one setting. A texture that holds data, not color, needs sRGB off and the right compression.

    Show me how

    What vanilla uses, read from the Rex's and the small storage box's textures:

    Texture Compression sRGB Vanilla example
    Base color (albedo) Default on RexHead_colorized_D
    Colorization mask Default on RexHead_colorized_M
    Normal map Normalmap off RexHead_N
    Packed maps (roughness, metal, occlusion in channels) Masks off RexHead_L
    • Normal maps import as normal maps on their own if the name ends in _N. If it's from a DirectX tool, leave Flip Green Channel off; from an OpenGL tool such as Blender, tick it.
    • Size: powers of two, which also give the texture its mip levels; without them it can't stream. 2048 is plenty for most items and structures, and 1024 for icons. Wildcard's guide sets a mask's LOD Bias to 1 so a 4K mask cooks at 2K.
    • Compress Without Alpha: tick it on color textures with no real alpha, so a stray alpha channel doesn't push them to a heavier format.
    • Texture Group: pick one that fits the asset, such as Weapon for a weapon. It sets streaming and size limits.
    • Virtual textures: the Rex's textures are virtual (streamed in tiles). To make one virtual, tick Virtual Texture Streaming in the texture itself. Modders warn the right-click convert option scans the whole kit.
    • A texture parameter set up for a virtual texture needs a virtual texture, and a regular one needs a regular one. Modders found a mix can compile in the kit and fail in the cooked game.
  4. Plug in your textures and set the switches. Open your instance. Tick each parameter you override, then set it. Each different combination of switch values makes its own shader version to compile and cook, so match a vanilla instance's switches where you can.

    Show me how

    The ASA masters use these names. The older masters use similar ones.

    Parameter What goes there
    Albedo Map your base color
    Normal Map your normal map
    Material Map your packed roughness, metal and occlusion map
    ColorizationMask your mask (step 5)
    Color0 to Color5 the color each region shows before anyone dyes it
    the per-region switches turn each dye region on
    UseColorization (creatures), IsColorized (older masters) turns colorization on at all

    The per-region switches go by names such as UsingColorizedColor0 to 5 on the ASA masters and Color0Mask to Color5Mask on the older ones. I read these names from the masters' files, so the editor's grouping may differ. Wildcard's guide says the instance looks oversaturated until you switch on the regions your mask uses.

  5. Paint the colorization mask. Paint each dye region in one pure color. Black means "not dyed". The color decides the region number.

    Show me how
    Mask color Region Color parameter
    Red 0 Color0
    Green 1 Color1
    Blue 2 Color2
    Yellow 3 Color3
    Cyan 4 Color4
    Magenta 5 Color5
    Black none keeps the albedo's color

    Wildcard's guide gives this order, and the older structure master's intensity parameters name the same one (Color3_YellowIntensity, Color4_CyanIntensity). Some masks were made with two of the mixed colors swapped; the ASA masters have an Invert Magenta/Yellow Colorization switch for those.

    • Desaturate the albedo under dyed regions. The dye multiplies with it, so a colored base tints every dye and white dye looks wrong. Keep values above about 0.2; darker areas soak up the dye. Modders find the vanilla masters darken the base color, so lighten the gray before import.
    • Keep black areas in full color. They're the parts dye never touches: eyes, metal trim, leather.
    • Watch where colors meet. Red next to blue blends into magenta along the edge, which shows as a thin line of another region. Wildcard's guide charts which colors may touch on one UV shell.
    • Use at least three regions on anything bigger than a small item.
    • Each mesh needs its own mask, laid out on its own UVs, the same as its albedo.
  6. Turn the regions on in the Blueprint too. The material says where the regions are. The Blueprint says which ones can be dyed.

    Show me how
    Asset Settings Example
    Item, weapon, armor, saddle Use Item Colors, Allow Custom Colors, and Use Item Color per region (six ticks) the metal sword ticks regions 0, 1, 2 and 4
    Structure Allow Structure Colors, and Allow Structure Color Sets per region (all six on by default)
    Creature color set, Prevent Colorization Regions, Use Colorization the Rex uses regions 0, 1, 4 and 5

    Wildcard's guide says an item can't be dyed unless both Use Item Colors and Allow Custom Colors are on. For creatures, step 4 of How to make a custom creature covers color sets. Match the material to the Blueprint: the Rex's skin instance sets Color0, 1, 4 and 5, the same four regions its color set uses.

    Changing colors from a graph:

    • Creatures: call ForceUpdateColorSets on the server, never set material parameters (lessons §8). Parameters are lost on save and for late joiners.
    • Structures: modders make a dynamic material instance in Begin Play and set its color parameters. The structure's activate and deactivate material arrays can swap it back out.
    • There's no built-in switch to stop players painting one component while keeping its mask colors. Modders turn off coloring and set the color parameters themselves.
  7. Add glow if you want it. Glow, called emissive, is a texture or a switch on the master. On the ASA equipment master, glow can take its color from the dye regions.

    Show me how
    • Start from MI_ASA_Equipment_Emissive for items. Its switches include Emissive Color Regions?, EmissiveColorFromColorRegions?, Emissive Intensity and a Tek-style Emissive Tek? with its multiplier.
    • Wildcard's guide: when glow takes its color from a region, leave the emissive texture uncolored. A tinted emissive blends with the dye and gives the wrong color.
    • Tek building pieces get their glow from the Tek structure kit. The vanilla Tek wall's instance sets an EmissiveAmount of 0.4.
    • The older masters have glow versions: MM_Equipment_EmissiveColorize, MM_Structure_EmissiveColorize, MM_Tek_Emissive_Colorized.
    • A light that turns on with power swaps whole materials: Activate Materials and In Activate Materials on the structure (How to make a powered structure).
  8. Set the material on your mesh and test the dye in game. Assign the instance to the mesh's material slot. Dye it in PIE. Wildcard's guide gets its dyes with the GiveColors 20 cheat.

Checking what a material costs

Most ARK materials are instances of a vanilla master. An instance adds no new shaders as long as its switch settings match an existing vanilla instance's; a new combination compiles new ones. If you build your own material or function, check it against the vanilla one it replaces. Epic's Unreal Fest 2026 talks target UE 5.8, the kit's own version; the other tips are general Unreal advice I haven't tested in the kit.

How shaders multiply (5.8): A material compiles shaders for every usage flag it has ticked (Used with Skeletal Meshes, Used with Niagara Sprites and so on), times every different combination of static switch values among its instances. A switch alone costs nothing; each new combination does.

  • Tick only the usage flags you need on your own parent. Each one adds shaders to every instance under it. In 5.8 an instance can override a usage flag, so the parent can stay lean.
  • UI and Niagara materials: untick Used with Static Meshes on them.
  • Untick Automatically Set Usage in Editor on your parent, so dropping it on a new kind of mesh doesn't add flags.
  • The 5.8 material editor shows a live shader count. Watch it as you add switches.
  • Use static switches only where they skip texture samples or heavy maths. For a simple choice, an If node fed by a scalar parameter compiles no extra shaders. A Channel Mask Parameter picks a texture channel the same way.
  • Per-actor values: on Nanite meshes, each different material instance on screen costs a little GPU time. Use Custom Primitive Data (below) or a Material Parameter Collection rather than a dynamic instance per actor. ARK's dyes work their own way; this is for your own materials.

Measuring, and other tricks:

  • Shader Complexity view mode and the instruction count at the bottom of the material editor are rough guides. Some instructions cost many times more than others, and a lower count can even run slower. To compare two versions, put each on a plane that fills the screen in an empty level, and compare GPU time in stat unit.
  • A Quality Switch node gives low material quality a cheaper branch.
  • Set texture samplers to Shared: Wrap (or Clamp) when one material samples many textures. It stops you hitting the sampler limit.
  • Pack the most important mask in alpha. In a compressed packed texture, alpha keeps the most detail. Low-detail masks work at small sizes.
  • World Aligned Texture (triplanar) hides seams on rock and wall kits. Blend two tiling scales with noise to hide repetition.
  • DitherTemporalAA fades a mesh in or out without the cost of translucency. Its shadow flickers with the dither; a Shadow Pass Switch gives the shadow its own solid opacity. For foliage with a cull distance, multiply the opacity mask by Per-Instance Fade Amount through the dither, so plants fade out instead of popping.
  • Move slow-changing maths to the vertices. A Vertex Interpolator runs whatever feeds it once per vertex instead of once per pixel. Panning, rotating or scaling UVs look the same and cost less. Lighting-like maths shows the triangle edges, so keep that per pixel.
  • Custom Primitive Data gives copies of one mesh different colors or values while they share one material. Tick Use Custom Primitive Data on a parameter in your own material, then set the values per mesh component, in Class Defaults or from a Blueprint. The copies can still be drawn together, and no dynamic instance is needed. It needs a parameter set up for it, so it doesn't work on vanilla masters.
  • Keep one parent material per kind of asset (characters, environment, effects), so editing one parent doesn't recompile everything.

How the pieces connect

This asset Field Points at
Material instance Parent a vanilla master
Material instance texture parameters your textures
Mesh material slot your instance
Item Item Icon Material Parent a colorized icon material
Blueprint region switches the regions your mask paints

The settings that matter

Setting Where
sRGB, Compression Settings texture
Maximum Texture Size, LOD Bias texture
Compress Without Alpha texture
ColorizationMask, Color0 to Color5 material instance
Use Item Colors, Allow Custom Colors item
Allow Structure Color Sets structure
Emissive Intensity material instance
Visualize Colorization Map material instance

Common mistakes

It's checkered, gray or pink in game

The game drew its default material. Maybe it wasn't cooked: it or a texture sits outside your mod folder (References outside your mod). Maybe it isn't allowed on that mesh: tick its usage flag, such as Used with Nanite (meshes, step 7). A shader error names the material under LogShaderCompilers in the cook log (When a cook or upload fails).

The colors don't apply

One of three things is off. Check the region switch in the material (step 4). Check the Blueprint's switches (step 6). Check the mask has paint in that color (step 5). Creatures: the creature page.

The dye goes to the wrong region

Two mask colors are swapped against the order in step 5. Flip Invert Magenta/Yellow Colorization, or repaint the mask. Thin lines of another region along an edge come from two colors touching on one UV shell.

My texture has gray or washed-out patches

The material is colorized, but the mask leaves that area out, so it shows the gray albedo. Paint the area black in the mask and keep its color in the albedo. Or use a parent that isn't colorized.

White dye looks tinted, or dark dyes look muddy

The albedo under the region isn't gray. Desaturate it and lift the darkest values above about 0.2 (step 5).

Textures are blurry after the cook

Check the player's own texture quality first. Modders traced blurry structures to the game's setting on medium or low. Then check the texture's LOD Bias and Maximum Texture Size; the kit shows their effect live. One modder saw regular textures cap at about 2048 in the cooked game. Make larger ones virtual.

Dyeing broke on my structure skin

A skin's tileset with wrong Color Regions entries breaks the brush. The cosmetic page has the fix.

Check it worked

  1. In the instance: turn on Visualize Colorization Map (or Check Real Colorization Map). Each region shows one flat color, with no lines along edges.
  2. In PIE: spawn it, dye each region with a different color, and look for regions that don't take it.
  3. The icon shows the dye on an item (Item Icon Material Parent).
  4. In a cooked build: no checkered faces, and textures are sharp up close.

Watch

Go deeper

Sources

Where this page's information comes from

Applies to: ASA DevKit as of November 2026 (UE 5.8.1); ASE where noted

the DevKit's own master materials, instances and textures, Wildcard's colorization guide, the community Discord (see Sources)

Esc

↑ ↓ move↵ openCtrl ↵ new tab