Modding guide

Sparse class data: class-wide settings, and how to change them for one creature

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

If you've seen CLASS GLOBAL on a Set node, this page is for you. It explains what sparse class data is, why setting one of these values changes every creature of that kind at once, and what to do when you only want to change one.

Most broken breeding and mutation mods from mid-2025 broke on this. So did a lot of item and structure tricks that used to work per actor.

  • You'll learn: what sparse data is, what a runtime change really does, and how the Sparse Data Override Manager gives you per-creature values
  • Time: 15 minutes to read; an hour to set up your first override manager
  • Level: intermediate; you've made a buff or changed a creature's settings before
  • You'll need: a mod that's registered, and a setting you want to change on some creatures but not all

What sparse data is

Every Blueprint class has a class default object: one hidden copy that holds the defaults. Each actor you spawn starts as a copy of it, and from then on has its own values.

Sparse class data is a second block of settings that is never copied. There's one copy per class, and every actor of that class reads from it. Unreal made it to save memory: settings that never differ between two Rexes don't need to be stored on every Rex.

ARK has a lot of it. Creatures have about 650 sparse settings, structures about 300 and items about 150. Wildcard moved a large batch of them there with the UE 5.5 update in 2025. That's when many mods broke.

You still set them the normal way. Open Class Defaults and they're in the Details panel with everything else, usually under a "Sparse Class Data" heading. A child class inherits them from its parent and can change them, like any other setting.

What changes when you set one at runtime

This catches people: a Set node on a sparse setting doesn't change the creature you plugged in. It changes the class's one shared copy. Every creature of that class changes with it: the ones already in the world and the ones that spawn later.

Unreal designed sparse data to be read-only. Wildcard made most of ARK's sparse settings writable, but they're still shared. To warn you, the DevKit labels those Set nodes CLASS GLOBAL. The label only appears once the node is connected to your graph and you compile. The compiler and the log also print a note.

So a buff that halves "this one Rex's" mating cooldown halves it for every Rex on the server. When the buff ends and sets it back, it sets it back for every Rex too, including any another buff had changed.

Three details that follow from that:

  • It's per class, not per family. Modders report that a change on a parent class doesn't reach a child class that has its own sparse values. If you want every creature, you have to set it on every class.
  • It reaches actors that already exist. That's different from editing the class default object at runtime, which only affects actors spawned afterwards.
  • It isn't saved. The shared copy is rebuilt from the class's defaults every time the game starts. A change made at runtime lasts until the server restarts, and then your mod has to make it again.

On a dedicated server, a change on the server doesn't reach clients by itself. On a listen server or in single player, server and client share the class, so the host's change applies there too. Changing vanilla content without replacing it explains the same problem for class default object edits.

When a class-wide change is fine

Sometimes class-wide is exactly what you want:

  • A server setting: "Rexes mate twice as often on my server" is one value for the whole class. Set it once in a singleton when the server starts, from your ini setting.
  • Your own creature or item: If the class is yours, set it in Class Defaults and you're done. No runtime change needed.

What's not fine is anything about one creature: a consumable, a buff, a tame's level, an owner's choice. For those, you need the override manager.

Per-creature values: the Sparse Data Override Manager

Wildcard added the Sparse Data Override Manager in mid-2025, after modders listed the settings they needed per creature. It lets your mod answer one question: "when the game reads this setting for this actor, what should it get?"

It covers only some settings. The list is short and grows when modders ask. In mid-2025 it had settings like these: whether a creature counts as an alpha, gestation on or off, mating time, the mate boost range and its damage multipliers, the random mutation chance and points, and how many items a craft gives. Check the current list in your DevKit (step 3 below). The mating cooldowns weren't on it in early 2026: modders were still asking for them.

Set one up

  1. Make the manager. Create a Blueprint whose parent is SparseDataOverrideManager.

  2. Give it a Manager ID. It's the only default setting. Pick something nobody else will: your mod's name plus a word. Without it, GetSparseDataOverrideManager can't find your manager at runtime.

  3. See what you can override. Open the manager, go to the Functions panel, and open the Override list. Every supported setting is there by its exact name. Search the list: it grows with DevKit updates.

  4. Register it. Open your mod's PrimalGameData and set Sparse Data Override Manager to your manager. A map mod can set it in the map's World Settings instead.

    The Mod Data Asset has the same field. Don't use it for now. Wildcard's documentation says managers set there fight over which one the game creates. A creator found the same in 2025 and moved theirs to the PrimalGameData.

  5. Write the override. Override the function for your setting. It gets:

    • Base Value: what the class's sparse data says;
    • Current Value: the value after other mods' managers have had their say;
    • For Instance: the actor being asked about. Cast it to the class you need.

    Return the value this actor should get. To leave an actor alone, return Current Value, not Base Value. That way you don't wipe out another mod's change.

You don't have to change any of the game's reads of that setting. Wildcard's documentation says the cook rewires them to ask the managers.

Show me how: a mutation boost for one creature

Say a consumable should double one creature's chance of a random mutation while its buff lasts. A published mod does much the same.

  1. The consumable adds a buff to the creature. The buff does nothing else. Its existence is the signal.
  2. In your manager, override RandomMutationChance_Override.
  3. In the override: cast For Instance to PrimalDinoCharacter. If the cast fails, return Current Value.
  4. Check whether the creature has your buff. If it doesn't, return Current Value.
  5. If it does, return Current Value × 2.

When the buff ends, the creature goes back to the normal value on its own. You never set anything back. Another mod's manager can still make its own change: you multiply whatever it returned.

Keep overrides cheap

The game calls your override every time anything reads that setting, in Blueprint and in the game's own code. For some settings that's very often, on every creature near a player.

  • Never read the same setting inside its own override. That read calls your override again, forever. Use Base Value or Current Value instead.
  • No searches in an override: No Get All Actors Of Class, no loops over the world. Work things out somewhere else (when the buff is added, say) and keep the answer in a map on the manager, keyed by the actor. The override just looks it up.
  • Return early. Check the cheapest thing first: is this the right class? Then: is it in my map?

A manager that overrides nothing still costs a lookup. Don't register one you don't use.

When the setting isn't supported

If your setting isn't in the Override list, you can't change it for one creature. Your options:

  1. Change something else that has the same effect. A modder pointed out a neat one for mating cooldowns: instead of changing the cooldown length, take time off the creature's next allowed mating time. That's a per-creature value, not a sparse one.
  2. Accept class-wide. If it's a server setting anyway, set it once at server start.
  3. Ask for it. Wildcard added the first settings from a list modders posted, and keeps adding. Post the exact setting names and what you need them for in the community Discord's editor requests channel.

Don't fall back to a buff that sets the class value and sets it back. Two creatures with the buff, or two mods doing the same thing, undo each other, and the change reaches creatures it shouldn't.

Reading sparse values

Reading is safe. A Get node on a sparse setting returns the class value, passed through every registered manager, for the actor you plug in. Two things to know:

  • Tools that read only the class default object miss them. If a tool, a script or a data export says a creature has no gestation settings, or says a hook's gate flag is off, it's probably reading the wrong block. The database on this site reads both.
  • Hooks often need a sparse gate. Many events only fire when a matching bUseBP… flag is on, and many of those flags are sparse. BPDoAttack needs Use BP Do Attack, for example. Set the flag in Class Defaults, or your event never runs.

Old settings with _DEPRECATED in the name

When a setting moved to sparse data, its old copy on the class stayed, renamed with _DEPRECATED. The game doesn't read it. If you find a setting twice in Class Defaults, set the one under the sparse heading.

Common mistakes

My buff changed every creature of that kind

The setting is sparse. Look for CLASS GLOBAL on the Set node after you compile. Move the change into a Sparse Data Override Manager if the setting is supported; otherwise see When the setting isn't supported.

My change worked until the server restarted

Runtime changes to sparse data aren't saved. Make them again when the server starts, from your singleton.

My override manager does nothing

Check, in order: it has a Manager ID; it's set on your PrimalGameData, not only the Mod Data Asset; you did the cache reset after changing the PrimalGameData; your override returns your value for the actor you expect (a Print String on the cast tells you).

Another mod's manager stopped working when mine was added

Your override probably returns Base Value. Return Current Value for every actor you don't change, and build on Current Value for the ones you do.

The server hangs or crawls when creatures are near

An override that reads its own setting loops forever. One that searches the world runs thousands of times a second. See Keep overrides cheap.

My event never fires

Check its bUseBP… gate flag in Class Defaults, under the sparse heading.

Watch

Go deeper

Sources

  • Wildcard's DevKit documentation, "Sparse Data Instance Overrides" (devkit.studiowildcard.com, read 2026-11-06): the UE 5.5 change, the CLASS GLOBAL label, the manager's setup and Manager ID, the override inputs, stacking through Current Value, the PrimalGameData-only advice and its bug, the cost warnings, and the cook rewiring the reads.
  • The DevKit's files, read on 5.8.1: the number of sparse settings per class, the sparse blocks on vanilla creatures and items, the _DEPRECATED copies, which hook gates are sparse, and DoAttack reading its gate from the sparse block.
  • My PIE tests: a Get node reading a sparse value, and per-actor sparse values not being reachable from Blueprint.
  • Published mods' files, read for how they use the manager: one overrides the mutation chance and the alpha flag for creatures that carry its buffs; another registers a manager that overrides nothing. I don't name them.
  • Discord threads (open for server members):
    • the "Sparse Data Problems" thread, where modders listed the settings they needed per creature and Wildcard described the manager (2025-05);
    • class-wide changes reaching existing actors, and not cascading to child classes (2025-07);
    • the short list of supported settings (2026-04);
    • taking time off the next mating time instead of changing the cooldown (2026-03);
    • requests for more supported settings (2025-06, 2026-02).
  • Video: Quellcrest's sparse data video, as in Watch, for registering on the PrimalGameData.

Community knowledge from the ARK Modding Community Discord (discussions from May 2025 to April 2026), found with Overseer.

Where this page's information comes from

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

Wildcard's DevKit documentation, the DevKit's own files, my PIE tests and the community Discord (see Sources)

Esc

↑ ↓ move↵ openCtrl ↵ new tab