Changing vanilla content without replacing it
12 min readASA DevKit as of November 2026 (UE 5.8.1); ASE where noted
Sooner or later you want to change something Wildcard made: a stack size, a creature's damage, a recipe, a
structure's health. You can't edit the vanilla asset; a mod never ships changes to /Game. You have three tools
instead, and each one changes something different and costs something different.
This page explains the three, gives my default order, and walks through four real examples. It takes about 20 minutes to read. Each change then takes from ten minutes to an hour.
- You'll learn: which of the three tools to use for a change, how to apply it, and what it costs
- Time: about 20 minutes to read; ten minutes to an hour per change
- Level: intermediate (you've registered content and made a buff or a singleton)
- You'll need: a registered mod, and the vanilla class you want to change
The three tools
- A default buff: A buff the game adds to every character of a class as it spawns. It changes each creature or player, one at a time, while the buff is on them.
- A CDO edit: The class default object (CDO) is the copy of a class that every new instance is built from. Your singleton changes a value on it when the server starts. It changes the whole class, for everything made afterwards.
- A remap: You make a child of the vanilla class and tell the game to use yours wherever it would have used the vanilla one. It replaces the class everywhere.
My default order
Use the first one that can do the job:
- An "Additional…" array or a server setting. If the Mod Data Asset or the server's ini already has a field for it, use that. Additions stack with other mods. How ARK finds your content lists them.
- A default buff, for anything on a creature or a player. It never touches the class, so nothing lingers.
- A CDO edit from a singleton, for class data no buff can reach: loot sets, recipes, item and structure values. Run it on the server, add rather than replace, and accept the costs below.
- A remap, only when the class itself has to be different: a new mesh, new graph logic, new components.
Which one to use
| You want to change | Use | Why |
|---|---|---|
| A creature's or player's damage, speed, resistances, behavior | default buff | Per character, stacks with other mods, nothing to undo. |
| What a vanilla crate or loot set can roll | CDO edit (add an entry) | Crates read the loot set's CDO; see loot. |
| A vanilla item's recipe, weight or stack size | CDO edit, or point server owners to the ini | No buff reaches an item's class data. |
| A vanilla structure's health | CDO edit | Default buffs only reach characters. |
| A creature's base stats, mesh or graph | remap a child | Base stats live on its status component, which Blueprint can't write on the CDO. |
| Where a creature spawns | spawn additions | See spawns; a remap breaks other mods. |
| A component's defaults, like a vanilla box's slots | remap, or leave it | Modders report Blueprint-added components can't be edited on the CDO. |
What each one costs
Here are the trade-offs side by side. The sections after the table explain them.
| Default buff | CDO edit | Remap | |
|---|---|---|---|
| Scope | each character, while it has the buff | the whole class | the whole class, everywhere |
| Stacks with other mods | yes | yes, if everyone adds instead of replacing | no: one mod wins |
| Load order | doesn't matter | the last edit wins on the same value | some remaps only work from the first mod |
| Survives a restart | re-added at spawn | no: re-apply on every server start | yes |
| Client side | replicates like any buff | the client needs the edit too, for anything it shows | none |
| Leaves traces | none | vanilla edits linger on the client until the game restarts | your class sits in saves |
| Runtime cost | one buff actor per creature | one pass at start | none |
The costs of a CDO edit, in plain words
It resets on every restart. The CDO is built fresh when the game starts, so your singleton has to apply the edit every time the server comes up.
Clients need it too. The server's edit doesn't reach a client. If players see the value, like a stack size or a recipe, the client must run the same edit. Modders do that by making the singleton replicate.
It lingers on the client. A client keeps your vanilla edit until the game closes. If the player leaves your server and opens single player, your change is still there. ZenRowe's rule is stricter than this page: only read a vanilla class's CDO, never change it, and change your own classes' CDOs on the server only. Experienced modders disagree on how much the lingering matters in practice.
Existing things keep the old value. Only new instances copy the CDO. Items already in inventories need a re-initialize, and placed structures keep what they saved.
Setting a whole array overwrites it, while adding to it stacks. Replacing an array wipes other mods' additions and server owners' ini overrides, so add to arrays, and change single values only when you must.
Sparse data is class-wide anyway. Many ASA fields live in sparse class data, a class-wide block kept beside the CDO. Setting one at runtime changes every instance of the class, from anywhere. So treat any sparse field as a CDO edit, with the same costs. Per-instance values need a sparse data override manager (Sparse class data).
The costs of a remap
A remap replaces the class for everyone. Another mod that remaps the same class conflicts with yours. Modders also report some remaps only take effect from the first mod in load order. Other mods' CDO edits and server owners' ini overrides name the vanilla class, so they miss yours. On creatures, a remap also breaks mods that piggyback on the vanilla species.
The costs of a default buff
A buff on every wild creature is one replicated actor per creature. Keep its graph light and tick only when you need to (lessons §8). It can't change anything class-wide, such as loot or recipes.
The process
Default buff: make the buff, then register it for the class. The buff changes the character it sits on. The Mod Data Asset adds it to every character of that class as it spawns.
Show me how
- Make a child of
Buff_Baseand set Deactivate After Time to 0, or it ends after a second (lessons §8). How to make a buff covers the rest. - In the Mod Data Asset, add an element to Additional Default Buffs (
AdditionalDefaultBuffs, structBuffAddition). For Class is the character class; Buff Additions is your buff. - For Class reaches child classes too. Modders set it to the base creature class to reach every creature. So a buff for the Rex also lands on other mods' Rex variants; check the class in the buff if that matters.
- Several mods' default buffs on one class stack. That was fixed in v36.
- Make a child of
CDO edit: a singleton that edits on every server start. It runs on the server, and on clients when they show the value. Get the CDO, change the value, then refresh what already exists.
Show me how
- Make a
SaveGameActorchild and register it in Server Extra World Singleton Actor Classes. My singleton video shows it at 1:46. - If players see the value, tick Replicates and Always Relevant. Its Begin Play then runs on every client too. Modders traced "the client only sees it after joining single player" to a singleton missing these.
- On Begin Play, call Get Class Default Object (
UVictoryCore) with the vanilla class, and cast the result to its type. - Change the value. For arrays, add or remove your own elements. For structs, use Set Members in …; a Break node gives you a copy.
- Refresh what already exists. Loop over inventories once and re-initialize the items, or drop and pick up an item when you test. Items re-initialize often on their own, but not reliably for this.
- Check before adding, so a second run doesn't double your entries.
Only Blueprint-visible fields can be written this way. Some aren't: a creature's
MaxStatusValuesis editable in the Details panel but not from a graph.- Make a
Remap: make a child, change it, and map the vanilla class to yours. Use the Mod Data Asset's remap fields.
Show me how
- Make a child of the vanilla class and change what you need in it, including its components and sparse data.
- Add a From Class → To Class pair (struct
ClassRemapping) to the field for that kind of content: Remap NPC, Remap Items, Remap Engrams, Remap Supply Crates, Remap NPC Spawn Entries or Remap Resource Components. - Test with your mod alone and with any mod that touches the same class, in both orders.
Four examples
A stack size: stone from 100 to 200
Stone's item class, PrimalItemResource_Stone, stacks to 100 (MaxItemQuantity, a Blueprint-visible field).
- Point server owners to the ini first.
ConfigOverrideItemMaxQuantityin Game.ini does this per item, built in. - If your mod must do it, use a CDO edit on server and clients. Set
MaxItemQuantityto 200 and re-initialize existing stone.
Warning
Stack size edits are the riskiest CDO edit. Modders report players losing items when a server restarted before the edit applied, and stacks above the vanilla size were cut. Some items, Raw Prime Meat among them, behaved badly with an edited stack size. Test a restart with full stacks before you publish.
A creature stat: more Rex melee damage
Use a default buff. A buff carries its own Melee Damage Multiplier and Receive Damage Multiplier fields, so a damage change needs no graph.
- Make a buff with Melee Damage Multiplier at 1.2 and Deactivate After Time at 0.
- Register it in Additional Default Buffs with For Class =
Rex_Character_BP. - Test a wild Rex and a tamed one against a dummy, then the same on a server.
I haven't measured how that field combines with the Rex's other damage multipliers. Check the numbers in game.
Base health is different. The Rex's 1,100 health is on its status component class, DinoCharacterStatusComponent_BP_Rex,
and that array can't be written from a graph. A remapped child can set its own value. A buff can call the status
component's Set Max Status Value at runtime. I haven't tested how that survives leveling or a restart.
A recipe: a cheaper storage box
The small storage box's item, PrimalItemStructure_StorageBox_Small, costs 25 wood, 20 thatch and 10 fiber. That's
its BaseCraftingResourceRequirements array, which Blueprint can write.
- CDO edit on server and clients. Change the amounts in the array. The crafting screen shows the client's copy, so the client needs the edit too.
- Re-initialize items in inventories, or players see the old cost on items they already hold.
- Tell server owners that
ConfigOverrideItemCraftingCostsin Game.ini does the same per item.
A structure's health: a tougher storage box
The small storage box has 500 health. The field is Health, on the native targetable actor class, and Blueprint can
write it.
- CDO edit on the server of
StorageBox_Small, settingHealth. Default buffs can't reach structures. - Place a new box to test. New placements get the new health. Placed boxes saved their own health; I haven't tested how their maximum behaves after the edit.
- Remap a child instead if you also need a new mesh, snap points or inventory.
Common mistakes
My CDO edit works on the server but clients don't see it
The client never ran the edit. Make the singleton replicate (process step 2) so its Begin Play runs on clients too.
Players see my changes in single player after leaving my server
That's a vanilla CDO edit lingering on the client until the game restarts. Move the change to a default buff if you can. Otherwise keep the edit server-side, or accept it and say so on your mod page.
Old items still show the old value
Only new instances copy the CDO. Re-initialize existing items once at start (process step 2).
Server owners' ini settings stopped working
Your mod replaces an array they also override, or remaps the class they name. Add to arrays instead, and avoid remaps.
My remap only works when my mod is first
Some remaps only take effect from the first mod in load order. Move to a CDO edit or a buff if you can. If not, tell server owners where to put your mod.
I can't change a vanilla component's defaults
Modders report Blueprint-added components don't exist in an editable form on the CDO. UVictoryCore has a Get
Blueprint Components From CDO node, but I haven't tested it for this. A remapped child is the route that works.
Check it worked
- On a local dedicated server, the change shows on new creatures, items or structures.
- A separate client sees the same value in every screen that shows it.
- After a server restart, the change is still there and nothing was lost: full stacks, placed structures, tames.
- With another mod that touches the same class, both mods' changes still apply.
- After leaving the server, single player behaves as vanilla. If it doesn't, you've edited a vanilla CDO on the client; decide whether that's acceptable.
Watch
- Wildcard Workshop #12: Class Default Objects (ZenRowe, ASE). 1:45 what a CDO is. 2:36 the client-side risk with vanilla classes. 4:43 his rule: read vanilla CDOs but never change them, and change your own classes' CDOs on the server only.
- Ark Survival Ascended - Dev Kit - Replication (Quellcrest). 26:37 reading an item's CDO.
- Ark Ascended Devkit: The Ultimate CCA (Singleton) Tutorial (my video). 1:46 making and registering the singleton.
- SETTING UP DINO SPAWNS FOR ALL THE MAPS | Episode 15 (SlayerXtreme). 1:22 remaps, and why they replace the creature everywhere.
- UPDATE: How to make your own custom DINO | Episode 13 (SlayerXtreme). 43:57 a remap against the routes that piggyback.
Go deeper
- How ARK finds your content: every Mod Data Asset field, and how mods merge.
- How to make loot crates and change supply drops: a full CDO edit on loot sets.
- How to add creatures to spawns: additions instead of remaps.
- How to make a buff and How to make a custom creature.
- Sparse class data: the settings outside the CDO, and the override manager.
- Inheritance and default objects: the CDO in depth, and why existing things keep old values.
- Load order and name collisions: remaps, first-mod wins and names that clash.
- lessons §1: build on vanilla, never overwrite it.
- The wiki's server configuration for the ini keys server owners already have.
Sources
- DevKit files, read offline on 2026-11-05: From the game module's reflection data:
UModDataAsset's remap and default-buff fields, the structsClassRemappingandBuffAddition,UVictoryCore::GetClassDefaultObjectandGetBlueprintComponentsFromCDO, the Blueprint visibility ofUPrimalItem.MaxItemQuantityandBaseCraftingResourceRequirements,APrimalTargetableActor.Health,APrimalBuff.MeleeDamageMultiplierandReceiveDamageMultiplier, andUPrimalCharacterStatusComponent.MaxStatusValues(editable, not Blueprint-visible) withSetMaxStatusValue. Values from/Game/PrimalEarth/CoreBlueprints/Resources/PrimalItemResource_Stone(stack 100),PrimalItemStructure_StorageBox_Small(25 wood, 20 thatch, 10 fiber),StorageBox_Small(500 health) andDinoCharacterStatusComponent_BP_Rex(1,100 health). - My own notes: lessons §1 and §8 (build on vanilla;
Buff_Baselifetime; one actor per buffed creature), tutorials §5 (sparse data at runtime), and the merge rules on How ARK finds your content. - The ARK Wiki: Server configuration
(
ConfigOverrideItemMaxQuantity,ConfigOverrideItemCraftingCosts). - What modders report, from the ARK Modding Community Discord:
- the three routes, and the split over how risky vanilla CDO edits are (2024 to 2025);
- CDO edits resetting on restart, the client needing the edit, and the replicating singleton (March 2024, March 2025, December 2023 for the singleton settings);
- existing items needing a re-initialize (March and April 2025);
- vanilla CDO edits lingering into single player (November 2024);
- stack size edits losing items on restart and misbehaving on Raw Prime Meat (April 2024);
- Blueprint-added components not editable on the CDO (October 2026);
- default buffs reaching child classes, and their cost (January 2024, April 2026);
- remaps breaking other mods' CDO edits and server ini (January and May 2026); some remaps only working from the first mod (2024).
- Videos listed under Watch: creators' tutorials, not checked against the kit. ZenRowe's is ASE-era.
- Community knowledge from the ARK Modding Community Discord (discussions from December 2023 to October 2026, mainly #asa-general, #asa-graphs and #asa-blueprints), found with Overseer. Threads that helped (they open for server members): why CDO edits are called dangerous (June 2025), CDO edits on items, client side and re-init (March 2025), stack size edits and lost items (April 2024), singleton replication settings (December 2023), remaps and other mods (January 2026).
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 classes and game data, the community Discord and creators' videos (see Sources)