Fix: Data Asset Changes Not Saving in Unreal

You modify a UDataAsset at runtime or through an editor utility, everything looks correct in the editor, and then you restart — all your changes are gone. This is one of the most frustrating Unreal Engine issues because there’s no error message. The asset simply reverts to its previous state. Here’s why it happens and how to make your changes stick.

Understanding Unreal’s Dirty Package System

Unreal Engine uses a dirty-flag system for asset persistence. When you modify a property through the editor’s Details panel, the editor automatically marks the containing package as dirty. The asterisk (*) that appears next to the asset name in the tab title is the visual indicator. When you press Ctrl+S, only dirty packages are saved.

When you modify an asset programmatically — through C++ code, a Blueprint utility, or an editor script — you bypass the editor’s property change tracking. The asset is modified in memory, but the package is never flagged as dirty. Ctrl+S skips it entirely because Unreal thinks nothing changed. The fix is to call Modify() before making changes.

// WRONG: modifying without marking dirty
void UMyEditorUtility::UpdateDataAsset(UMyDataAsset* Asset)
{
    Asset->DamageMultiplier = 2.5f;  // Changed in memory only
    // No save — change will be lost on restart
}

// CORRECT: mark dirty, then modify, then save
void UMyEditorUtility::UpdateDataAsset(UMyDataAsset* Asset)
{
    Asset->Modify();  // Marks the outer package dirty
    Asset->DamageMultiplier = 2.5f;

    UPackage* Package = Asset->GetOutermost();
    FString PackageFileName = FPackageName::LongPackageNameToFilename(
        Package->GetName(), FPackageName::GetAssetPackageExtension());
    UPackage::SavePackage(Package, Asset, *PackageFileName,
        FSavePackageArgs());
}

Editor Transactions vs. Saving

A common misconception is that wrapping changes in an FScopedTransaction will cause them to persist. Transactions serve the undo/redo system, not the save system. They record property changes so the user can press Ctrl+Z to revert them, but they do not write anything to disk.

// This enables undo/redo but does NOT save to disk
{
    FScopedTransaction Transaction(LOCTEXT("UpdateAsset", "Update Data Asset"));
    Asset->Modify();  // Required for both undo AND dirty flag
    Asset->Health = 200;
}
// Package is now dirty and undoable, but still needs explicit save

The Modify() call is the critical step shared by both systems. It notifies Unreal that the object is about to change, which both registers the pre-change state for undo and marks the package dirty for saving. If you skip Modify(), you get neither undo support nor dirty-flag marking.

Runtime vs. Editor Modifications

Changes made to data assets during Play-in-Editor (PIE) mode are intentionally discarded when you stop playing. This is by design — Unreal does not want gameplay logic to permanently alter your game data. If you need runtime modifications to persist, you must either save them outside of PIE or use a different storage mechanism like save game files.

For editor utilities that run outside PIE, the standard approach is to call Modify() and then prompt the user to save, or save programmatically. If you’re building a batch processing tool that modifies many assets, collect all dirty packages and save them in one pass at the end.

// Batch-saving multiple modified data assets
TArray<UPackage*> PackagesToSave;

for (UMyDataAsset* Asset : AssetsToModify)
{
    Asset->Modify();
    Asset->RebalancedValue = CalculateNewValue(Asset);
    PackagesToSave.AddUnique(Asset->GetOutermost());
}

// Save all dirty packages at once
FEditorFileUtils::PromptForCheckoutAndSave(PackagesToSave,
    /*bCheckDirty=*/false,
    /*bPromptToSave=*/true);

Source Control Complications

If your project uses Perforce, saving will fail silently if the .uasset file is not checked out. Unreal will mark the package dirty in memory, but SavePackage will return false because the file is read-only on disk. Always check out files before modifying them, or use Unreal’s source control API to handle checkout automatically.

With Git, this is less of an issue because files are not read-only by default. However, if you have Git LFS configured and the file is locked by another team member, you will hit a similar problem when you try to push. The save itself will succeed locally, but collaboration issues can lead to confusing merge conflicts in binary .uasset files.

When in doubt, verify that the file on disk actually changed by checking its modification timestamp or running a diff in your source control tool. This tells you definitively whether SavePackage succeeded or failed silently.

Understanding the issue

Asset pipelines transform source content into runtime data. Each stage can lose information, change behavior, or introduce platform-specific variations. Bugs at this layer are often invisible until the cooked build runs.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in Unreal. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

For Unreal-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

Within Unreal, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

Modify() first, SavePackage second, verify on disk third.