Modding guide

Inheritance and default objects: what a child really gets from its parent

12 min readASA DevKit as of November 2026 (UE 5.8.1)

Every how-to page on this site says the same thing: make a child of a vanilla asset, not a copy. This page explains why that works. It covers what a child stores, what it can and can't change, and how ARK's long class families fit together.

It also covers the class default object, the hidden copy every instance starts from. Most "it works for new things but not old ones" problems come from there.

  • You'll learn: what a child inherits, how parent changes reach it, how casts and class checks see families, what the class default object is and when it matters, and what a cast costs in memory
  • Time: 20 minutes to read
  • Level: intermediate; you've made a child of a vanilla item or structure before
  • You'll need: nothing but the DevKit; the examples use classes you can open yourself

What a child stores

A child class starts as an exact match of its parent. It has the same variables, components, functions and defaults. What the child saves in its own file is only what you changed.

That's why a child is small. A data-only child of a vanilla pick is a few kilobytes. The DevKit says so too: hover over the asset and the tooltip reads Is Data Only: True when you changed defaults and wrote no graph.

It's also why a child keeps up with Wildcard. Every value you didn't touch is read from the parent. When an update changes the parent, your child changes with it.

How a parent change reaches the child

Say the parent's weight is 5 and your child never touched it. Wildcard changes it to 4. Your child now weighs 4.

Now say you set your child's weight to 3. Wildcard's change doesn't reach you. Your 3 stays, because you changed it.

The Details panel shows which is which. A small curved reset arrow sits beside every value that differs from the parent. Click it and the value follows the parent again. Turn on Show Only Modified Properties to see just your changes.

What a child can't change

A child mostly adds things. It can't delete what the parent has, but it can stop the parent's logic from running: override the event or function that uses the thing, and don't call the parent. That works, with a risk: anything else in the parent that expected that logic to run can break, so test the whole class afterwards.

You want to In a child
Change a default value Yes, in Class Defaults
Change an inherited component's settings Yes, select it and edit the Details panel
Remove or rename an inherited component No
Change an inherited variable's type No
Add your own variables, components and functions Yes
Replace a parent's event or function Yes, by overriding it
Switch off a parent's behavior Yes, by overriding what runs it and not calling the parent
Keep the parent's logic and add to it Yes, by overriding and calling the parent

When you hit a "No" in that table, look one step up the family. The parent's parent may not have the thing you want gone. When a copy is unavoidable covers the cases where nothing in the family fits.

Inherited variables are hidden at first

Open a child's My Blueprint panel and the variables list looks empty. The inherited ones are there, just hidden. Click the gear icon on the panel and turn on Show Inherited Variables. ARK's base classes have hundreds, so turn it off again when you've found yours.

Overriding events and functions

When a parent has an event or function, a child can replace it. Events appear when you right-click the graph and search. Functions are under Functions > Override in My Blueprint.

An override starts empty. The parent's logic no longer runs unless you call it. Right-click the event or function entry and pick Add Call to Parent Function. You get a node named after the parent's version.

Where you put that node matters:

  • Call the parent first to let vanilla do its work, then add yours. This is the usual choice.
  • Call it last when you want to change something before vanilla reads it.
  • Leave it out only when you mean to replace vanilla's logic completely.

Many ARK events only run when their gate is on. A gate is a class default named like bUseBP…. The child inherits the parent's gate, so check it in Class Defaults. Override and gate flags explains them.

ARK's class families

Vanilla classes come in long families. Nearly every vanilla creature in the DevKit descends from one Blueprint, Dino_Character_BP: 1,522 of 1,618 creature classes. Most items descend from PrimalItem_Base, and most buffs from Buff_Base.

Between the base and the creature you see, there are often helper classes. Each one adds one behavior:

Family Chain, from the class you see down to the base
Aberrant Raptor Raptor_Character_BP_Aberrant → Raptor_Character_BP → Dino_Character_BP_Pack → Dino_Character_BP
A Rock Drake variant RockDrake_Character_BP_Lightning → RockDrake_Character_BP_Corrupt → RockDrake_Character_BP → Dino_Character_BP_Climber_ForceAllowBoss → Dino_Character_BP_Climber → Dino_Character_BP_NoBossArena → Dino_Character_BP
Rock Drake kibble PrimalItemConsumable_Kibble_RockDrakeEgg → six kibble size classes → PrimalItemConsumableEatable → PrimalItemConsumableGeneric → PrimalItem_Base

Below the last Blueprint there's always a native class written in C++, like PrimalDinoCharacter or PrimalItem. You can't open those, but their settings show in every child.

This shapes how I pick a parent:

  • Pick the closest relative that already does what you want. A pack hunter starts from a pack creature, not from Dino_Character_BP.
  • Variants are children of the main class. Wildcard makes the Aberrant Raptor a child of the Raptor. Do the same with your own creature: make your variant a child of your creature, and every fix reaches both.
  • Look at the middle of the chain. A helper class like Dino_Character_BP_Climber is often a better parent than the creature that uses it. Class Settings in the Blueprint editor shows any class's parent.

The DevKit database on this site lists every vanilla class with its full chain. Look up a creature, item or structure in the browse pages to see where it sits.

How the game sees a family

A child is a kind of its parent. Most checks in ARK and in other mods are written that way, which is the real reason a child beats a copy.

  • A cast succeeds for the class and every child. "Cast To Raptor_Character_BP" passes for your Raptor child and for the Aberrant Raptor.
  • "Class Is Child Of" works the same way for classes instead of objects.
  • An exact class check doesn't. "Get Class equals Raptor_Character_BP" fails for every child, including Wildcard's own variants. Avoid it in your own code unless you mean only that one class.

A copy fails all three. It's a new class with no tie to the original. Modders report copied items failing vanilla casts, like the ones for element and fiber, and failing other mods' checks for a vanilla family. A remap can't fix that: it swaps which class spawns, but casts still look at the family.

The class default object

Each class has one hidden object that holds its defaults: the class default object, or CDO. When the game spawns an actor or creates an item, it copies the CDO. Class Defaults in the Blueprint editor is the CDO you're editing.

A child's CDO is built from its parent's CDO plus your changes. That's the inheritance from the first section, seen from inside.

When the CDO is built

The game builds a class's CDO when it loads the class, from the values saved in the asset. It builds it fresh on every start. Nothing you change on a CDO at runtime is saved.

That's where three common surprises come from:

  • A runtime CDO edit resets on restart. Your singleton has to apply it every time the game starts.
  • Things that already exist keep their old values. They copied the CDO when they were made. Only new ones see the change.
  • A vanilla CDO edit can linger on a player's game. It stays until they restart, even in single player.

Changing vanilla content covers each one and what to do about it.

Code that runs on the CDO

Some things in ARK run on the CDO itself, not on a spawned copy. Skins do: a structure skin's logic runs on the skin class's CDO, with the structure passed in. So store nothing on the skin, and work on the structure you're given.

The CDO isn't in any world. Anything that needs one, like spawning, tracing or getting the game mode, fails. In the log it looks like this, with the class's CDO named Default__ plus the class name:

Script Msg: A null object was passed as a world context object
No world was found for object (… Default__MySkin_C)

When you see Default__ in a log line, the code ran on a CDO. Reading ARK's logs has more of these lines.

Reading a class's defaults

Two nodes give you a class's defaults without spawning anything:

Node What you get Use it for
Get Class Defaults (Unreal) A copy of the values, one output pin per variable Reading a setting off a class, like an item's weight, in your own code
Get Class Default Object (UVictoryCore) The CDO itself Changing a vanilla class's defaults on purpose (how)

Read with the first. Only use the second when you mean to change every future instance.

Some settings aren't on the CDO at all. Many creature and item numbers live in sparse class data: one shared block per class that's never copied. Setting one changes the whole class at once, including what already exists. Sparse class data explains the difference.

Instances can override their class too

The chain doesn't stop at the class. Two kinds of instance keep their own values on top:

  • An actor placed in a level: Select it in the level and edit the Details panel. That value belongs to the placed actor. Change the class default later, and actors whose value you edited keep theirs. Map makers meet this a lot.
  • Anything restored from a save: Variables marked SaveGame come back from the save file, over the class default. So a default you change in an update doesn't reach a saved structure's saved value. Saving your mod's data covers which values save.

So when a value isn't what Class Defaults says, check in this order: the instance, the save, a runtime change, the class, then each parent.

What a cast costs

A cast node names a class. That name is a hard reference: when your Blueprint loads, that class loads with it, and everything the class refers to loads too.

That adds up fast in ARK. Cast to a creature and you may pull in its meshes, animations, sounds and buffs. One modder found a single buff pulling in 1.8 GB that way. Another found that naming element anywhere loaded the whole Tek armor set.

Three things help:

  • Look at the Size Map. Right-click your asset → Size Map, then switch it to memory. It shows everything your asset pulls in. The editor page shows how to read it.
  • Cast to the base, not the leaf. A cast to PrimalItem_Base loads almost nothing new. A cast to a specific weapon loads that weapon.
  • Use soft references for classes you may never use. A soft reference is only a path, and nothing loads until you resolve it. Call its resolve function (modders use ResolveAsset). The automatic conversion only works when the class is already loaded, so it passes in the editor and fails on a live server. "Class Is Child Of" and other nodes with a class picked in a pin are hard references too.

Blueprint interfaces are the other way out. Two classes can call each other through an interface without either one naming the other.

Common mistakes

My child does something I never set

It inherited it. Turn on Show Only Modified Properties on the parent and each class above it, and read what they set. The behavior is usually one of those.

My override stopped vanilla from working

You overrode an event and didn't call the parent. Add Call to Parent Function, and decide whether it goes first or last.

I changed the parent's default but my child didn't change

Your child had its own value. Look for the reset arrow next to that setting in the child. Click it to follow the parent again.

My change only applies to new things

You changed a default, or a CDO at runtime. Things that already exist copied the old value. Change the existing instances too, or accept that it only applies to new ones. Saved values also come back over your new default.

My child landed in the vanilla folder

Right-click → Create Child Blueprint Class puts the child next to the parent. Move it into your mod folder before you do anything else, or it won't be cooked with your mod. Or start from your own folder: Add > Blueprint Class, then search for the parent under All Classes.

My mod loads far more than it should

A cast or class pin pulls in a big family. Check the Size Map and see What a cast costs.

I reparented my class and saved things changed

Reparenting keeps your class's name and path, so saved things still find it. Saved values for variables the new parent family doesn't have are dropped. Modders disagree on whether placed structures survive a reparent, so test on a copy of a real save first. A safer route is a new class next to the old one, with a remap or a swap on load.

Check it worked

  1. Open your child and turn on Show Only Modified Properties. Every value shown should be one you meant to change.
  2. Hover over the asset. A child where you only changed settings says Is Data Only: True.
  3. For each override, check there's a parent call, or that you meant to leave it out.
  4. Open the Size Map in memory mode and look for anything you didn't expect.
  5. In PIE, cast your child to the vanilla parent and print the result. It should succeed.

Watch

Go deeper

Sources

  • The DevKit's files, read on 5.8.1 with the editor closed: the class chains and counts (1,522 of 1,618 creature classes under Dino_Character_BP, the Rock Drake and kibble chains), the data-only flag, and the CDO naming in log lines.
  • My notes from building and testing mods: skins running on the CDO, Show Only Modified Properties and the reset arrow, Add Call to Parent Function, gates inherited from the parent, and CDO edits resetting on restart.
  • Unreal Engine's behavior, as documented by Epic: delta saving of child defaults, inherited components, Show Inherited Variables, Get Class Defaults, and per-instance overrides on placed actors.
  • Discord threads (open for server members):
    • a child passing casts where a copy doesn't (2024-02);
    • copied items failing element and fiber casts, and remaps not fixing casts (2023-11);
    • Create Child Blueprint Class placing the child next to the parent, and picking the parent from your own folder instead (2024-12, 2025-08);
    • overriding a function and unhooking the parent call to replace its logic (2023-11);
    • whether placed structures survive a reparent, with both answers (2023-12);
    • casts as hard references (2023-12);
    • the Size Map in memory mode, and a buff pulling in 1.8 GB (2026-09);
    • class pins and Is Child Of as hidden hard references (2026-09);
    • the Resolve function versus the automatic conversion on a live server (2026-02).

Community knowledge from the ARK Modding Community Discord (discussions from November 2023 to September 2026), found with Overseer.

Where this page's information comes from

Applies to: ASA DevKit as of November 2026 (UE 5.8.1)

the DevKit's own files, my notes from building and testing mods, and the community Discord (see Sources)

Esc

↑ ↓ move↵ openCtrl ↵ new tab