Modding guide

How to make a buff or status effect

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

Your own buff changes stats for a while, shows an icon and a timer on the HUD, and comes from an item, a weapon hit, a structure or a creature. It can also run its own logic. A simple buff takes me about an hour the first time. One that runs logic on every creature takes an afternoon, mostly testing on a server.

  • You'll make: a buff that changes stats, shows on the HUD, and is applied and removed where you want
  • Time: about an hour for a simple one; an afternoon for one with logic
  • Level: beginner for stat buffs; intermediate once it runs logic or goes on every creature
  • You'll need: a mod set up and registered, and the vanilla buff closest to yours

Before you start:

  • Have your mod open on its test map, with your PrimalGameData and Mod Data Asset linked. Your first mod covers that.
  • Look up a vanilla buff that does something like yours. The database lists every one with its duration, stat changes and stacking: /ark/browse/buffs.

If you only want the steps, read the numbered list and skip the rest.

What a buff is

A buff is an actor attached to a character: a player or a creature. While it's attached, it can change the character's stats, show on the HUD and run logic. When it ends, it's destroyed.

It's a replicated actor. So the server has one copy, and every nearby client has its own. That matters as soon as your buff runs logic (step 8).

Almost everything in ARK that isn't permanent is a buff: food effects, diseases, bola holds, a creature's special moves. Vanilla has well over a thousand of them, and they make good examples.

The process

  1. Pick the right base buff. Make a child of a vanilla base, never a copy of a finished buff.

    Show me how
    You want Start from What it gives you
    Most buffs Buff_Base the plain buff; parent of over 500 vanilla buffs
    A buff only its owner needs: UI, input, private effects Buff_Base_OnlyRelevantToOwner bOnlyRelevantToOwner on, bDestroyOnTargetStasis on
    An area effect around something Buff_Base_AoE no instigator; children set a range and a buff to apply
    A disease Buff_Base_Disease the disease setup
    A food effect Buff_Base_Stew the parent of Focal Chili and the other soups

    All of these sit on the native class PrimalBuff. Right-click the base → Create Child Blueprint Class, and save it in your mod folder with your prefix.

    Don't copy a vanilla buff that belongs to an item. Modders found a copied Tek binoculars buff killed itself when anything but its own item applied it.

  2. Set how long it lasts. Buff_Base ends after 1 second unless you change it. This catches almost everyone.

    Show me how
    • Deactivate After Time (DeactivateAfterTime) is the duration in seconds. Buff_Base sets it to 1.
    • Set it to 0 for a buff that lasts until something removes it. Default buffs and equipment buffs do this.
    • Battle Tartare lasts 180 s (database); Focal Chili lasts 900 s (database).
    • After it ends, the actor lingers for DeactivationLifespan (0.6 s by default) so effects can fade out.

    SlayerXtreme hits this exact problem in the tranq video, at 28:17.

  3. Decide what happens when it's added again. By default, adding the buff again resets its timer. You can extend the time or count stacks instead.

    Show me how

    There are two systems. The first is about adding the buff again:

    Field Default What it does
    bAddResetsBuffTime on adding it again restarts the timer
    bAddExtendBuffTime off adding it again adds time instead
    bAddReactivates off adding it again runs its activation again
    AddBuffMaxNumStacks how many times it can be added

    Radiation Sickness turns reset off and extend on, with AddBuffMaxNumStacks 20.

    The second is a stack counter, for effects that grow:

    Field Default What it does
    bEnableBuffStacking off turns the counter on
    MaxNumStacks 1 the most stacks it can hold
    MinTimeBetweenStacks 0 seconds before another stack counts
    StackDuration −1 how long each stack lasts; −1 means no separate timer

    Cold Snap stacks to 15. The Xiphactinus bleed stacks to 5, at most one stack every 0.25 s. The database's buff pages show each buff's stacking settings.

  4. Change stats with fields, not graphs. Most stat effects are class defaults on the buff. They undo themselves when the buff ends.

    Show me how

    Multipliers apply while the buff is active. All default to 1.0:

    Field Battle Tartare
    MeleeDamageMultiplier 1.6
    ReceiveDamageMultiplier (damage taken) 0.85
    CharacterMultiplier_ExtraFoodConsumptionMultiplier, …ExtraWaterConsumptionMultiplier 1.5, 1.5
    XPEarningMultiplier, HarvestQuantityMultiplier, StaminaDrainMultiplier, WeaponRecoilMultiplier

    Status value changes go in CharacterStatusValueModifiers, one entry per stat:

    Entry field What it does Battle Tartare, health entry
    ValueType which stat Health
    DamageMultiplierAmountToAdd how much to add (negative to take) −90
    SpeedToAdd + bSpeedToAddInSeconds spread it over this many seconds 180, on
    bSetValue, bSetAdditionalValue both on: set the stat's bonus to the amount, for multiplier stats such as movement speed off

    Battle Tartare's second entry sets the SpeedMultiplier bonus to 0.5 with both set flags on. Focal Chili does the same for movement speed (0.25) and crafting speed (1).

    Per-second changes: turn on bAddCharacterValues and fill ValuesToAddPerSecond. Radiation Sickness drains health this way.

    Max stats: MaxStatScalers multiplies a stat's maximum. Radiation Sickness scales max stamina to 0.75.

  5. Give it a HUD name, icon and text. These all live in one struct, Buff Description. Leave the icon empty and the buff runs invisibly.

    Show me how
    Field in BuffDescription Battle Tartare
    ModifierName Battle Tartare
    ModifierDescription the tooltip text
    ModifierIcon BattleTartare_Icon, a texture
    HUDMessage + bDisplayHUDMessage "Battle Tartare Enabled", shown when it starts
    • To hide it, use bHideBuffFromHUD or bHideTimerFromHUD. bDisplayHUDProgressBar shows a bar.
    • To change the icon at runtime, change it on the client as well as the server. Set Members in Struct is the tidy way.
    • To draw your own markers on screen, override the buff's HUD draw functions, such as BPDrawBuffStatusHUD. A ticking or timed draw flickers.
    • A screen effect goes in BuffPostProcessEffect. Modders report it only shows once the material is registered in the game data; the Mod Data Asset has a field for buff post-process effects.
  6. Apply it from where it belongs. Every route ends in the same place: the server adds the buff to a character.

    Show me how
    From How
    An item, the simple way set the item's BuffToGiveOwnerCharacter. Battle Tartare's item (database) and the Tek Sword do.
    An item, with a graph in the item's Event Blueprint Used: Get Owner Inventory → Get Owner → Static Add Buff with your buff class
    A weapon hit set BuffToGiveVictimCharacter on its damage type. DmgType_Bola gives Buff_Bola (database). See How to make a weapon.
    A structure on a server timer, find characters in range, check Has Buff, then Static Add Buff
    An area a Buff_Base_AoE child with AOEBuffRange (cm) and AOEOtherBuffToApply. The Concavenator's dust cloud uses 1,500.
    A creature's attack the attack's damage type, as for weapons
    Every creature or player of a class a default buff in the Mod Data Asset: step 9

    Static Add Buff only works on the server. On a client it returns nothing. Its inputs are the character, the damage causer, the buff class, an associated item and a force-on-client switch.

    BuffToGiveOwnerCharacter is in the item's sparse class data, so find it in Class Defaults.

  7. Remove it cleanly. Ending a buff early means calling Deactivate on it, on the server. Clean up anything your buff changed in both of its end events.

    Show me how
    • Find it with Get Buff or Has Buff on the character, then call Deactivate on the server.
    • A buff can end others when it starts: BuffClassesToCancelOnActivation. Battle Tartare ends the other damage soups this way.
    • To block a buff instead, override BPPreventAddingOtherBuff (gate: bUseBPPreventAddingOtherBuff) on a buff that's already there.
    • Clean up in both BPDeactivated and ReceiveEndPlay. A buff can end without deactivating, for example when the character is destroyed.
    • Stat changes from CharacterStatusValueModifiers undo themselves. But modders found vanilla bleeding applies its damage in C++ in a way you can't undo at runtime. Prevent the bleed buff from being added instead.
  8. If it runs logic, turn on the hooks and keep ticks rare. Most buff events only fire when a matching bUseBP… switch is on. Use timers and events before you reach for tick.

    Show me how
    Event Its switch Use it for
    BPSetupForInstigator bUseBPSetupForInstigator setup, once the buff knows its character
    BPActivated bUseBPActivated the moment it starts
    BPDeactivated bUseBPDeactivated cleanup
    BuffTickServer, BuffTickClient bUseBuffTickServer, bUseBuffTickClient repeated work; slow it with BuffTickServerMinTime / MaxTime
    BPCustomAllowAddBuff bUseBPCustomAllowAddBuff refusing to be added
    • An override with its switch off never runs, and the compile is still clean. Even vanilla has dead ones: 24 of 366 BPDeactivated overrides and 31 of 315 BuffTickServer overrides (lessons §2).
    • Set up in BPSetupForInstigator, not Begin Play. Begin Play can run before the buff knows its character. Quellcrest compares the two at 9:30.
    • Prefer events, then timers, then tick. If you must poll, use a repeating timer, check validity first and bail out early. Server tick is the one to avoid.
    • A buff on a creature stops ticking when the creature goes into stasis, the sleep state for far-away actors.
    • Don't bind the Use key in a buff. Blueprint input nodes consume the key by default, which can kill E for the player (lessons §8).
  9. Decide who sees it: replication and "only relevant to owner". By default every nearby client gets a copy of the buff, and its Begin Play runs on each. Filter your logic, or keep the buff to its owner.

    Show me how
    • Watch the copies. Run PIE with two clients and open your buff's debug object list. One player with the buff shows a server copy plus a copy on every client.
    • Server-only logic: check Is Running On Server first. Cosmetic logic: check Can Run Cosmetic Events.
    • UI for the owner only: Get Owner Controller → Is Valid. Other clients fail the check.
    • bOnlyRelevantToOwner spawns the buff only on its owner's client. It's right for UI and input. It's wrong for anything other players should see: they never get a copy.
    • Talking to the server: the player owns a buff on themselves. So its Run on Server and Run on Owning Client events work, which a structure's don't (tutorials §6).
    • Values other players need belong in replicated variables, with RepNotify for anything visual.
    • Modders report that a multicast in a repeating timer that adds buffs made creatures coming out of stasis invisible to every client. A run-on-server event avoided it.
  10. To put it on every player or creature of a class, register a default buff. That's the Mod Data Asset's Additional Default Buffs. It's how a mod attaches behavior to vanilla creatures without replacing them.

    Show me how
    • In the Mod Data Asset, add an entry to Additional Default Buffs: For Class is the character class, Buff Additions lists your buffs. The Default Buff template uses the player pawn class. How ARK finds your content has the details and the cache trap.
    • Set the buff's duration to 0.
    • Default buffs stack across mods. Older threads saying only one mod's buff works predate the fix.
    • Default buffs are only added when the character spawns or leaves a cryopod. Creatures already in the world when your mod is installed don't get it. Sweep them from a singleton at server start: Get All Actors of Class → Has Buff → Static Add Buff if missing. Changing vanilla content without replacing it covers the singleton.
    • A buff on every wild creature is one more replicated actor per creature. An empty buff costs little, but keep it light: no tick, few replicated variables.
  11. Make it survive a restart, if it should. Buffs aren't saved by default. Turn saving on, and keep any data in a persistent data object.

    Show me how
    Field Default What it does
    bPreventSaving on the buff isn't saved with the character; turn it off to keep it
    bIsBuffPersistent off keeps it through death and server transfer, like diseases
    BuffPersistentDataClass none an object that holds your buff's data across saves
    bAllowBuffStasis lets it stay through stasis

    The Cryo Cooldown buff (database) has saving on, persistence on, stasis allowed, and PrimalBuffPersistentData_GenericTimeRemaining as its data class.

    bIsBuffPersistent on its own doesn't save your Blueprint variables. Put them in a child of a PrimalBuffPersistentData class and point BuffPersistentDataClass at it.

  12. Test it. Give it to yourself with a command first, then test the real route on a dedicated server.

    Show me how
    • ForceGiveBuff takes the buff's Blueprint path and an on/off switch. It works in the DevKit too.
    • ListMyBuffs lists what you have.
    • If it won't apply, print the character and the buff reference where you add it. Then look for a timer of 1 s or a Deactivate call that ends it straight away.

    The full list is in Check it worked.

What a buff can't change: class-wide values

Since the 2025 sparse-data change in the DevKit, many class settings live in sparse class data: one copy per class, not per actor. Setting one from a buff changes it for every actor of that class, wherever they are.

Creatures carry a lot of these. In the kit, the Rex's chain keeps FemaleMatingTime, BaseEggClass, bIsBigDino, FallingDamageHealthScaleBase and MeleeSwingSockets there. Many breeding values moved too: mutation chances, mate boost range, gestation. Modders found that many breeding mods broke when this changed.

The compiler warns when you set one of these variables. If you need a per-creature value, make a child of SparseDataOverrideManager and register it. It lets you return a different value for the creatures that have your buff. Register it on your PrimalGameData; Sparse class data has the setup and why.

How the pieces connect

This asset Field Points at
Mod Data Asset Additional Default Buffs your buff, per character class
Item BuffToGiveOwnerCharacter your buff
Damage type BuffToGiveVictimCharacter your buff
AoE buff AOEOtherBuffToApply the buff it puts on things in range
Your buff BuffClassesToCancelOnActivation buffs it ends when it starts
Your buff BuffPersistentDataClass its saved-data object
Your buff BuffDescription.ModifierIcon the HUD icon texture
Your buff BuffPostProcessEffect a screen-effect material

The settings that matter

What you're looking for Field
How long it lasts DeactivateAfterTime (0 = until removed)
What re-adding does bAddResetsBuffTime, bAddExtendBuffTime, bAddReactivates
Stacks bEnableBuffStacking, MaxNumStacks
Damage dealt and taken MeleeDamageMultiplier, ReceiveDamageMultiplier
Health, food and other stats over time CharacterStatusValueModifiers, ValuesToAddPerSecond + bAddCharacterValues
Max stats MaxStatScalers
HUD name, icon, text BuffDescription
Hide from the HUD bHideBuffFromHUD, bHideTimerFromHUD
Owner-only bOnlyRelevantToOwner
Saved and persistent bPreventSaving off, bIsBuffPersistent, BuffPersistentDataClass
Event switches bUseBPSetupForInstigator, bUseBPDeactivated, bUseBuffTickServer, bUseBuffTickClient

Common mistakes

My buff vanishes after a second

Buff_Base sets Deactivate After Time to 1. Set your duration, or 0 for no timer.

Static Add Buff returns nothing

You called it on a client. Add gameplay buffs on the server. A client can hold a buff of its own, but only one set up for it: turn the buff's replication off, and tick Force On Client (bForceOnClient) on Static Add Buff. That buff exists on that one machine and nowhere else. Modders rarely need one, and reports on getting it to work differ, so test it on a dedicated server.

My event never fires

Its bUseBP… switch is off. Find the switch named after the event and turn it on.

My buff is gone after a server restart

bPreventSaving is on by default. Turn it off. If it's a default buff, also sweep existing characters at server start (step 10).

Creatures that were already there don't get my default buff

Default buffs are added on spawn and on leaving a cryopod only. Add it to existing creatures from a singleton at server start.

Every player sees my UI, or it opens several times

Each nearby client has a copy of the buff, and Begin Play runs on all of them. Check Get Owner Controller → Is Valid, or use bOnlyRelevantToOwner.

Other players can't see my buff's effect

The buff is only relevant to its owner, so they never get a copy. Turn that off, or move the visual to something everyone has.

The icon doesn't change when I set a new one

You set it on the server only. Set it on the client too.

My buff changes every creature of that species

You set a sparse-data value. Use a SparseDataOverrideManager instead (see above).

Bleeding keeps going after my cure removes it

Vanilla bleed damage can't be undone at runtime. Block the bleed buff from being added instead (step 7).

The E key stopped working

An input node in your buff consumes the Use key. Don't bind Use in a buff.

Check it worked

  1. ForceGiveBuff adds it in PIE. The icon, name and timer show, and the stats change as expected.
  2. It ends on time, or never if it shouldn't. Stats go back when it ends.
  3. Adding it again resets, extends or stacks as you set.
  4. The real route works: the item, the hit, the structure or the default buff.
  5. On a local dedicated server with two clients, the owner sees what they should, and the other player sees only what they should. PIE hides most of these mistakes. See Works in PIE, not on a server.
  6. Restart the server. A buff that should stay is still there, with its data. A default buff is on creatures that existed before the restart.
  7. If anything fails silently, read the Output Log for your buff's name first. See Reading ARK's logs.

Watch

Go deeper

Sources

  • DevKit files, read offline on 2026-11-05: Classes, fields and values come from these: /Game/PrimalEarth/CoreBlueprints/Buffs/ Buff_Base, Buff_Base_OnlyRelevantToOwner, Buff_Base_AoE, Buff_Base_Stew, Buff_BattleTartare, Buff_FocalChili, Buff_EnduroStew; /Game/Aberration/CoreBlueprints/Buffs/Buff_Radiation_Sickness; Buff_AoE_Concavenator_DustCloud; Buff_CryoCooldown and PrimalBuffPersistentData_GenericTimeRemaining; the stacking settings of Cold Snap and the Xiphactinus bleed; the item PrimalItemConsumable_Soup_BattleTartare and PrimalItem_WeaponTekSword; DmgType_Bola; the sparse class data of Rex_Character_BP and Dino_Character_BP. Native defaults (bPreventSaving on, bAddResetsBuffTime on, MaxNumStacks 1, DeactivationLifespan 0.6, multipliers 1.0, and bReplicates on) are from the APrimalBuff constructor. The counts of vanilla buffs per parent and of bUseBP… switches are from the buff database. ForceGiveBuff and ListMyBuffs are cheat-manager commands in the kit. StaticAddBuff, BPSetupForInstigator, BuffTickServer, HasBuff and GetBuff appear in vanilla buff and consumable Blueprints.
  • Modding lessons and What the video tutorials teach in this section: the 1-second Buff_Base, server-only StaticAddBuff, cleanup in both end events, bIsBuffPersistent not saving variables, one actor per creature, the Use key (lessons §8); dead overrides with the switch off (lessons §2); the buff as an owned route to the server (tutorials §6); SparseDataOverrideManager (tutorials §5, from Quellcrest's sparse-data video, recorded on UE 5.5).
  • What modders report, from the ARK Modding Community Discord:
    • item to buff with Event Blueprint Used and Static Add Buff (June 2024); a healing aura from a structure (October 2023);
    • debugging a buff that won't apply, and ForceGiveBuff in the kit (March 2025);
    • the copied Tek binoculars buff ending itself; bleed that can't be undone; post-process effects needing registration (2023–2025);
    • changing the icon on the client (November 2024); drawing with the buff's HUD functions, not tick (December 2025);
    • tick against timers, and buffs on creatures following stasis (October 2024);
    • one buff copy per client, and the owner-controller check (November 2024); what bOnlyRelevantToOwner costs (July 2024); the multicast-in-a-timer stasis bug (July 2025);
    • bPreventSaving on by default, default buffs only on spawn or uncryo, and sweeping at startup (November 2024, November 2025); persistent data objects (April 2025);
    • breeding values made class-wide by sparse data (2025).
  • Videos listed under Watch: creators' tutorials, not checked against the kit. ZenRowe's is ASE.
  • Community knowledge from the ARK Modding Community Discord (discussions from October 2023 to December 2025, mainly #asa-general, #asa-blueprints and #asa-graphs), found with Overseer. Threads that helped (they open for server members): consumable to buff (June 2024), a healing aura (October 2023), a buff that won't apply (March 2025), one copy per client (November 2024), buffs gone after a restart (November 2024), persistent buff data (April 2025), buffing every creature (November 2025), default buffs stacking, fixed v36 (March 2024), sparse data and breeding (May 2025).
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 Blueprints, the community Discord and creators' videos (see Sources)

Look something up in buffs and status effects

1,606 rows, each with its own page. Search by name or any detail, or start from a category.

Browse all buffs and status effects

Look something up in items

3,192 rows, each with its own page. Search by name or any detail, or start from a category.

Browse all items

Look something up in console commands

691 rows, each with its own page. Search by name or any detail, or start from a category.

Browse all console commands

Esc

↑ ↓ move↵ openCtrl ↵ new tab