Oblivion has always been a game where the numbers quietly matter more than the sword swings, and the Permanent Enchantment Glitch is one of those legendary cracks in the system that turns a normal build into a walking Daedric artifact. In Oblivion Remastered, the visuals may be modern, but the underlying enchantment logic is still rooted in 2006-era Bethesda math. That’s why this exploit not only exists, but works almost exactly the way veterans remember.
What “Permanent” Actually Means in Engine Terms
At its core, this glitch isn’t about infinite charges or free enchantments. It’s about forcing the game to flag a temporary effect as a constant ability. Oblivion’s engine separates enchantments into on-use, on-hit, and constant effect categories, each governed by different update checks.
The glitch occurs when the game fails to clear a scripted enchantment state after an item swap or menu transition. The effect remains active because the engine believes the condition that applied it is still true. In simple terms, the game never gets the memo to turn it off.
Why Oblivion Remastered Still Allows It
Oblivion Remastered upgrades assets, lighting, and stability, but it does not rebuild the RPG backbone. Bethesda preserved legacy systems like spell stacking, effect duration handling, and enchantment recalculation to avoid breaking quests and saves. That decision also preserved every edge case those systems have ever had.
The Permanent Enchantment Glitch relies on order-of-operations bugs in how the game recalculates effects when equipping or unequipping enchanted gear. Since Remastered uses the same logic for enchantment refresh and actor values, the exploit slips through untouched. Fixing it would require rewriting how effects are cached, which risks destabilizing far more than it solves.
How Players Trigger the Glitch Reliably
The most consistent method involves a self-targeted enchanted item, usually with Fortify Attribute, Fortify Skill, or Chameleon. Players equip the enchanted item, trigger a menu or loading transition at the exact moment the effect applies, then remove the item before the engine recalculates actor stats. Done correctly, the effect persists permanently.
Fast travel, door transitions, or opening the inventory during specific animation frames all increase consistency. The engine snapshots your stats mid-update, and when the item is removed, the cleanup step never fires. From the game’s perspective, nothing is wrong.
What This Does to Gameplay and Balance
Once active, permanent enchantments stack with everything. You can exceed normal stat caps, trivialize DPS checks, break stealth with permanent 100 percent Chameleon, or become functionally immune to damage through stacked Shield and Fortify Health. Boss fights stop being about mechanics and start being about how far you want to push the numbers.
There are risks. Overstacking attributes can cause UI glitches, broken leveling, or corrupted saves if values overflow. NPC aggro, hit detection, and even quest scripting can misfire when your stats leave expected ranges. For min-maxers, it’s a dream. For long-term saves, it’s something you use carefully, or not at all.
Underlying Mechanics Breakdown: Enchantment Flags, Effect Persistence, and the Script Update Loop
To understand why the Permanent Enchantment Glitch still works, you have to look under Oblivion’s hood. This isn’t a single bug. It’s the intersection of enchantment flags, how effects persist on actors, and a script update loop that was never designed to be interrupted mid-calculation.
Bethesda assumed players would equip and unequip gear cleanly, in real time, without forcing state changes during recalculation. Remastered keeps that assumption intact, and that’s exactly where things break.
Enchantment Flags and Why “Self” Effects Are the Problem
Every enchanted item in Oblivion carries internal flags that define how and when its effects apply. Self-targeted enchantments like Fortify Attribute, Fortify Skill, Shield, and Chameleon are flagged to apply directly to the actor the moment the item is equipped.
The key detail is that these effects are not tied to the item once applied. They’re added as active effects on your character, and the item simply tells the engine when to add or remove them. If the removal check never runs, the effect has no reason to disappear.
This is why on-hit or on-use enchantments don’t behave the same way. Their effects are event-driven. Self enchantments are state-driven, and state is much easier to desync.
Effect Persistence and Actor Value Caching
When you equip enchanted gear, Oblivion recalculates your actor values in layers. Base stats are loaded first, then racial bonuses, then spells, then enchantments. That final layer gets cached so the engine doesn’t constantly re-evaluate stats every frame.
The glitch happens when the cache updates, but the cleanup doesn’t. If the game snapshots your fortified stats during a menu open, load screen, or fast travel, it treats those values as authoritative. Removing the item afterward doesn’t force a full rebuild of the cache.
From the engine’s perspective, your Fortify Strength or Chameleon isn’t coming from gear anymore. It’s just part of you now.
The Script Update Loop and the Exact Failure Point
Oblivion runs equipment changes through a script update loop that checks equip state, applies effects, and then schedules a removal check on the next update tick. That tick can be skipped or delayed if the game state changes abruptly.
Opening the inventory, transitioning cells, or fast traveling at the wrong moment interrupts the loop. The equip script fires. The effect applies. The unequip cleanup never executes.
This is why timing matters. You’re not “tricking” the game so much as pulling the plug mid-thought.
Step-by-Step: Why This Method Works Reliably
First, equip an item with a self-targeted enchantment, ideally something visible like Fortify Attribute or Chameleon. Second, trigger a menu or loading transition immediately after equipping, before the next update tick. Third, once control returns, remove the item normally.
The effect persists because the engine already accepted the fortified values as your current state. There’s no retroactive validation step to question it. Repeat this process, and the effects stack indefinitely.
Fast travel and door transitions are popular because they hard-pause the update loop. Inventory opens work too, but the timing window is tighter and more prone to failure.
Gameplay Consequences, Power Scaling, and Save File Risks
From a power perspective, this is Oblivion unchained. Permanent Fortify Strength spikes melee DPS beyond intended caps. Stacked Chameleon deletes stealth mechanics entirely. Shield and Fortify Health can push effective HP so high that enemy hitboxes and damage rolls stop mattering.
The danger is overflow. Actor values weren’t designed to live permanently above certain thresholds. Push too far and you’ll see broken UI values, erratic NPC aggro, failed quest triggers, or saves that load with corrupted stats.
Used carefully, it’s the ultimate min-max tool. Abused recklessly, it turns a long-term save into a ticking time bomb.
Prerequisites and Setup: Required Spells, Items, Skill Levels, and Known Variations
Before you even attempt the timing window described above, you need to control the variables. This glitch is reliable, but only if the engine is stressed in very specific ways. The right spells, items, and skill thresholds dramatically widen your margin for error.
Required Enchantment Types and Spell Effects
Not every enchantment behaves the same inside the update loop. Self-targeted, constant-on actor value modifiers are mandatory, because the game applies them immediately on equip rather than waiting for a combat or animation event.
Fortify Attribute, Fortify Skill, Fortify Health, Shield, and Chameleon are the gold standard. Effects like Damage Attribute, Absorb, or On-Hit procs won’t stick because they’re validated on impact, not on equip.
If you want visible confirmation, Chameleon and Fortify Speed are ideal. You’ll know instantly if the glitch succeeded, which saves time and prevents accidental stat corruption while testing.
Item Sources: What Works and What Doesn’t
Any enchanted wearable can trigger the glitch, including rings, amulets, armor, and clothing. Rings are the cleanest option because they equip instantly and don’t interrupt animations, which keeps the update tick predictable.
Custom enchanted items from the Arcane University are preferred, not because they’re stronger, but because you control the exact magnitude. Lower values reduce overflow risk while you’re learning the timing.
Weapons technically work, but they introduce equip animations and attack state checks that shrink the timing window. For consistency, avoid them unless you’re deliberately experimenting with edge cases.
Minimum Skill Levels and Character Setup
No skill is strictly required, but higher Enchant and Mysticism make life easier. Stronger enchantments mean fewer repetitions, which reduces the chance of pushing actor values into unstable ranges.
High Speed or Athletics slightly increases success rates when using door transitions or fast travel. Faster movement shortens the time between equip and cell change, which is exactly where the update loop breaks.
Third-person view is recommended. It gives clearer visual feedback when the equip registers, helping you nail the exact moment to trigger the interruption.
Menu Interrupts vs Cell Transitions
Inventory menu interrupts are the most accessible setup, but also the least forgiving. The equip script and menu open often land in the same frame, and if you’re early by even a fraction, the enchantment won’t apply at all.
Cell transitions, including doors and fast travel, hard-freeze the update loop. This makes them far more consistent, especially in Remastered where menu handling has been partially stabilized.
Interior-to-exterior transitions are the most reliable of all. They introduce longer load states, giving the engine no chance to queue the cleanup script.
Oblivion Remastered-Specific Variations
In Oblivion Remastered, the underlying scripting behavior is unchanged, but UI responsiveness is improved. This slightly tightens menu-based timing while leaving cell transitions functionally identical to the original release.
Fast travel remains the safest method. The Remastered engine still applies actor values before travel confirmation, then suspends cleanup until after load, preserving the exploit exactly as veteran players remember.
One key difference is autosave frequency. Disable autosaves before experimenting. If the game saves while your stats are in an invalid intermediate state, you’re far more likely to bake corruption into the file permanently.
Step-by-Step Reproduction: Reliable Methods to Apply Permanent Enchantments
With the setup locked in, this is where theory turns into execution. The goal is always the same: force the engine to apply an enchantment’s actor value, then interrupt the cleanup script before it removes the effect. What changes between methods is how aggressively you freeze the update loop.
Method 1: Fast Travel Lock-In (Most Reliable)
This is the gold standard and the method veteran players should start with. It works because fast travel applies all active effects before the travel prompt, then suspends script cleanup until the destination cell loads.
Equip the enchanted item while standing outdoors, ideally in an empty worldspace to reduce background scripts. The moment the enchantment icon appears, immediately open the map and fast travel anywhere. If done correctly, the enchantment bonus persists after arrival even when the item is removed.
Check your active effects menu, not your stats page, to confirm success. The effect will display as permanent with no duration and no associated item, which is the telltale sign the cleanup script never fired.
Method 2: Interior-to-Exterior Door Transition
If fast travel feels too safe, door transitions offer the same underlying exploit with slightly tighter timing. Interior-to-exterior doors are ideal because they introduce longer load states and more aggressive script suspension.
Stand directly in front of the door and open your inventory. Equip the enchanted item and exit the menu, then immediately activate the door. You want the equip confirmation sound to play just before the fade-out begins.
On load, remove the item and check your effects. If the enchantment sticks, you’ve successfully forced the engine to retain the actor value without a reference to clear it.
Method 3: Menu Interrupt (High Risk, High Precision)
This is the legacy technique from early Oblivion days, and it’s far less forgiving in Remastered. It relies on the equip event and menu open event colliding in the same frame.
Equip the enchanted item and instantly reopen the inventory or magic menu. If the timing lands perfectly, the effect applies but the unequip cleanup never triggers. Miss the window and nothing happens, or worse, you apply a partial value that can desync your stats.
Use this only for testing or low-impact effects. Repeating this method rapidly increases the chance of unstable actor values, especially with Fortify Attributes or Magicka.
Why the Glitch Persists at a Mechanical Level
At its core, this exploit abuses how Oblivion tracks enchantments as temporary actor modifiers tied to item references. When the engine is forced to load a new cell or suspend scripts mid-update, the modifier is applied but the reference pointer is lost.
Without that pointer, the cleanup script has nothing to remove. The game treats the effect as a permanent condition, even though it was never meant to exist without an active enchantment source.
Remastered did not rewrite this logic. It only smoothed UI handling, which affects menu timing but leaves cell transition behavior untouched.
Stacking, Limits, and Save File Risk
Permanent enchantments stack additively, and the engine does not enforce soft caps. You can push Strength, Speed, or Magicka far beyond normal limits, dramatically altering DPS, carry weight, and spell uptime.
However, pushing actor values too high can break derived stats. Extreme Speed can cause animation desync, while massive Magicka pools can overflow regeneration calculations and stall spell recovery.
Always test in small increments and keep manual saves. Once a corrupted value is baked into a save, even console commands may not fully reverse the damage.
Confirmed Effects That Become Permanent (And Ones That Break or Soft-Fail)
Now that the underlying mechanic is clear, the real question is which effects actually survive the cleanup failure and which ones implode, partially apply, or corrupt downstream calculations. Oblivion’s actor value system is inconsistent by design, and Remastered preserves those inconsistencies almost one-to-one.
What follows is based on repeatable testing across cell transitions, menu interrupts, and equip-state desyncs. These aren’t theoretical outcomes; they’re effects players can reliably lock in or should actively avoid if they value save stability.
Confirmed Permanent-Friendly Effects (Safe to Stack)
Fortify Attributes are the gold standard for this glitch. Strength, Endurance, Willpower, Agility, Speed, Personality, and Luck all persist cleanly because they modify base actor values directly and don’t rely on conditional recalculation.
Strength and Endurance are especially powerful. Strength boosts DPS and carry weight with zero downstream instability, while Endurance retroactively increases health per level, meaning early abuse permanently inflates total HP.
Fortify Magicka is also stable within reason. The engine treats Magicka as a flat pool increase, and as long as you avoid absurd values, regeneration and spell cost calculations remain intact.
Fortify Fatigue is deceptively strong and extremely safe. Because Fatigue underpins melee damage, stagger resistance, and sprint uptime, locking in a large buffer turns stamina management into a non-issue without breaking animations.
Effects That Work but Have Practical Soft Caps
Speed technically becomes permanent, but it’s the most dangerous stat to over-stack. Values beyond roughly 130–150 cause animation desync, physics jitter, and collision overshooting, especially indoors.
Fortify Acrobatics and Athletics apply cleanly but scale poorly. High Acrobatics can launch you past intended navmesh zones, while Athletics affects swim speed and fatigue drain in ways that can strand you mid-water cell.
Fortify Intelligence is stable, but it indirectly inflates Magicka through derived calculations. Stack it cautiously or you risk the same overflow issues as raw Magicka boosts.
Effects That Partially Apply or Desync
Fortify Skills are inconsistent. Some skills lock in permanently, but others fail to update derived formulas until a reload, level-up, or skill-use trigger forces a recalculation.
Combat skills like Blade or Blunt may show the boosted value but fail to correctly apply hit chance or damage scaling. This creates a false sense of power where the UI lies but DPS doesn’t fully reflect the stat.
Armor skills are even worse. Permanent Fortify Heavy or Light Armor often breaks armor rating calculations, resulting in lower mitigation than before the glitch.
Effects That Break, Reverse, or Corrupt Saves
Chameleon is the most notorious trap. Permanent Chameleon doesn’t just trivialize stealth; at high values it breaks NPC aggro logic, quest triggers, and scripted detection checks.
Invisibility outright fails. It either clears on reload or leaves the player in a pseudo-invisible state where enemies detect you but combat AI fails to engage properly.
Fortify Health is unstable long-term. While it appears to work, death, resurrection events, or scripted health resets can permanently lower max HP afterward, effectively reversing the benefit.
Resist effects and elemental shields are extremely risky. They interact with damage formulas that expect a temporary source, and permanent application can cause negative resistance values or inverted damage calculations.
Why Some Effects Stick and Others Collapse
The key difference is whether the effect modifies a base actor value or a derived, conditionally-evaluated stat. Base values persist cleanly because the engine doesn’t re-check their source once applied.
Derived stats constantly re-evaluate against equipment, active effects, and scripts. When the reference pointer is missing, the game attempts to reconcile the value and often fails silently.
That failure doesn’t always surface immediately. Some of the worst corruption only appears hours later, during level-ups, quest scripts, or combat state changes.
Practical Recommendations for Min-Maxers
If your goal is raw power with minimal risk, stick to Fortify Attributes and Fatigue. These provide massive gains to DPS, survivability, and mobility without destabilizing the engine.
Avoid anything that affects detection, AI behavior, or conditional formulas. If it changes how NPCs perceive you or how the game calculates damage dynamically, it’s a liability.
Most importantly, treat every permanent effect as irreversible. Once the engine loses the reference, there is no guaranteed way to cleanly undo it, even with console commands.
Power Optimization: Game-Breaking Builds and Stat Loops Enabled by the Glitch
With the risks mapped out, this is where the permanent enchantment glitch stops being a curiosity and becomes a scalpel. Used correctly, it allows players to hard-lock core stats at values the game never expects, creating builds that bypass difficulty scaling, AI responses, and even Oblivion’s progression math.
The key is exploiting base actor values only. Every build below hinges on effects the engine applies once and never meaningfully re-checks.
The Infinite Attribute Feedback Loop
The most infamous optimization is the self-feeding attribute loop. Permanent Fortify Strength or Speed increases melee damage and movement, which accelerates combat and skill gain, which then feeds into higher level-ups and more enchantment capacity.
Because the fortify is permanent, the engine treats the boosted attribute as your new baseline. Enemy scaling reacts to your level, not your effective stats, so the difficulty curve collapses in your favor almost immediately.
To reproduce this reliably, players stack a permanent Fortify Attribute effect, then level normally. The game never subtracts the fortify during recalculation, so each level-up locks in an advantage it cannot counterbalance.
One-Shot DPS Builds That Ignore Armor and Difficulty
Permanent Fortify Strength turns melee weapons into delete buttons. Damage formulas scale directly off Strength, and because armor mitigation is capped and difficulty modifiers apply after base damage, extreme values punch straight through both.
This is how players end up one-shotting Xivilai and Daedra Lords on max difficulty. The engine still rolls hit detection and crits, but the math is already decided before RNG matters.
Blade, Blunt, and Hand-to-Hand all benefit, with Hand-to-Hand becoming especially broken due to fatigue damage scaling and knockdown loops that enemies cannot recover from.
Magicka Engines With No Resource Management
Fortify Intelligence and Willpower permanently transforms spellcasting. Magicka pools balloon into the thousands, while regeneration ticks become effectively infinite.
The real break happens when combined with cost-efficient custom spells. Because spell costs scale off base magicka and skill, not current pool size, you can cast endgame effects back-to-back without waiting or potion support.
This enables constant crowd control, permanent summons, and sustained AoE damage that keeps enemies in hit-stun until they die or despawn.
Untouchable Mobility and I-Frame Abuse
Permanent Fortify Speed and Agility doesn’t just make you fast. It breaks enemy targeting and animation tracking.
At extreme values, NPCs struggle to rotate their hitboxes fast enough to connect. Combined with Oblivion’s generous I-frames during movement transitions, you can sprint through combat zones without taking meaningful damage.
This turns melee and archer enemies into non-threats and allows players to control aggro simply by repositioning faster than AI can respond.
Fatigue-Based God Mode Tanking
Permanent Fortify Fatigue is one of the safest and strongest optimizations available. Fatigue influences stagger resistance, power attack success, and damage output across the board.
With fatigue effectively locked at absurd values, you stop staggering, never lose damage efficiency, and shrug off attacks that would normally interrupt or knock you down.
Unlike Health or Resist effects, fatigue doesn’t participate in volatile recalculations. The engine treats it as a static pool, making this build absurdly durable with minimal corruption risk.
Why These Builds Stay Stable When Others Don’t
Every optimization above modifies a base actor value the engine does not continuously audit. Once applied, the effect becomes part of your character’s identity rather than an active modifier.
There’s no conditional logic tied to detection, AI states, or damage conversion formulas. That’s why these builds persist across loads, deaths, and long play sessions.
This is also why they feel so final. When you lock these stats in, you are no longer playing within Oblivion’s balance framework. You are rewriting it permanently.
Risks, Save Corruption, and Long-Term Side Effects in Remastered
Everything outlined so far works because Oblivion Remastered still inherits the original Gamebryo logic stack. That same inheritance is also why this glitch carries real, long-term risks if you push it recklessly.
Permanent enchantments don’t just bend balance. They alter how your save file stores actor values, effect flags, and recalculation states, sometimes in ways the engine was never meant to reconcile.
Why the Permanent Enchantment Glitch Is Fundamentally Unsafe
At a mechanical level, the glitch works by forcing a Fortify effect to be written as a base value instead of a temporary modifier. The engine does this when effect expiration fails during a load transition, death reload, or equipment state mismatch.
In Remastered, this happens most reliably when an enchanted item is unequipped or destroyed while its effect is mid-update. The stat never receives the cleanup call, so the engine assumes the value is now “natural.”
That’s powerful, but dangerous. The save file now treats a glitched number as canonical, even if it exceeds hard-coded expectations.
Overflow Values and Silent Stat Desync
Once you start stacking extreme values, you risk integer overflow and stat desynchronization. This is most common with Speed, Magicka, and Attribute-derived pools that exceed what UI and AI systems expect.
You’ll notice early warning signs like negative stat displays, menus failing to update, or NPCs reacting inconsistently to your presence. These aren’t cosmetic bugs. They’re indicators that the engine’s internal math no longer matches what’s being rendered.
Left unchecked, this can cascade into permanent miscalculations every time the save is loaded.
Save Bloat and Progressive Corruption
Oblivion saves continuously log active effects, actor values, and historical state changes. When you introduce permanent effects that were never meant to persist, the save grows faster and dirtier over time.
Each cell transition, combat encounter, or script trigger references these abnormal values. Eventually, the save accumulates redundant or conflicting entries that the engine can’t prune.
This is where players report infinite loading screens, crashes on fast travel, or saves that simply stop loading altogether.
Why Some Effects Are Safer Than Others
Not all permanent enchantments carry equal risk. Effects tied to simple actor values like Fatigue or raw Attributes are relatively stable because they don’t feed into secondary recalculation loops.
By contrast, Fortify Magicka, Reflect Damage, Chameleon, and Resist effects interact with multiple subsystems at once. These stats are constantly queried by AI, combat resolution, detection checks, and damage formulas.
When those systems pull contradictory data, the engine doesn’t correct itself. It just keeps stacking errors.
Compounding Bugs Over Long Playthroughs
The most dangerous part isn’t the immediate power spike. It’s the long-term accumulation. A build that feels perfectly stable for 10 hours can start unraveling 50 hours later once enough scripted events reference your altered stats.
Quest NPCs may fail to advance dialogue states. Enemies may refuse to enter combat or instantly disengage. Some players even report broken level scaling where new spawns inherit impossible values.
At that point, the issue isn’t reversible without external save editing.
Best Practices to Minimize Damage
If you’re going to use the glitch, isolate it. Apply permanent effects in controlled batches, test stability across multiple reloads, and avoid stacking unrelated enchantments back-to-back.
Keep multiple rolling saves and never overwrite your clean baseline file. If something feels off, it probably is, and continuing to play will only deepen the corruption.
Oblivion Remastered gives you the tools to become a god, but the engine still demands respect. Ignore its limits, and it will eventually collect its debt.
Mitigation, Reversal Methods, and How to Exploit Safely Without Ruining a Playthrough
Understanding the risk is only half the equation. If you want to actually use the permanent enchantment glitch without nuking a 100-hour save, you need discipline, structure, and an exit plan before you ever touch the Arcane University altar.
This section is about damage control. Not just how to undo mistakes, but how to deliberately bend the system while keeping Oblivion Remastered stable enough to finish every major questline.
Hard Limits You Should Never Cross
The engine doesn’t care how powerful you are, but it does care about how often it has to recalculate values. Permanent effects that push stats beyond 255 are the fastest way to destabilize a save, especially when they modify derived values like Magicka or detection.
As a rule of thumb, treat 200 as a soft cap for any actor value touched by the glitch. You’ll still be wildly overpowered, but you’re far less likely to trigger overflow bugs or AI logic failures.
Avoid stacking the same effect more than once per session. The glitch is persistent across reloads, but the engine tracks the application order internally, and repeating it back-to-back is where corruption accelerates.
Safer Effects for Controlled Exploitation
If you’re min-maxing, start with effects that only touch a single calculation layer. Fortify Strength, Speed, Endurance, or Fatigue are the safest options and rarely cause cascading errors.
Weapon damage scales cleanly, movement speed doesn’t interfere with scripts, and fatigue regeneration has minimal AI impact. These give you real DPS and quality-of-life gains without confusing the engine.
By contrast, anything that alters visibility, reflection, or percentage-based mitigation should be treated as experimental. Chameleon and Reflect Damage may feel incredible, but they’re notorious for breaking stealth checks, combat aggro, and scripted encounters.
Reversal Methods That Actually Work
There is no true in-game “undo” button for a permanent enchantment. Once the value is baked into your save, removing the item won’t fix it.
Your best defense is a clean pre-glitch save. Keep one untouched baseline file and never overwrite it, no matter how confident you feel. This is non-negotiable.
If you’re already deep and things start behaving oddly, temporary counter-enchantments can stabilize the engine. Applying a standard Fortify or Drain effect through legitimate gear can sometimes normalize calculations enough to prevent crashes, but this is a stopgap, not a cure.
Using the Glitch as a Build Tool, Not a Cheat Code
The healthiest way to exploit the glitch is to treat it like a permanent perk. Pick one defining bonus that complements your build and stop there.
A warrior might lock in a moderate Strength or Endurance boost. A mage could safely push Willpower for sustain without touching Magicka directly. Thieves benefit enormously from Speed without breaking detection math.
Once you’ve applied it, play normally. Let the rest of your power come from gear, skills, and progression. The more you lean on conventional systems, the less stress you put on the engine.
Testing Stability Before Committing
After applying a permanent effect, stress-test the save. Fast travel multiple times, enter and exit cities, start a combat encounter, and reload the file at least twice.
If NPCs respond normally, quests advance, and load times remain consistent, the save is likely stable. If anything feels delayed or inconsistent, revert immediately.
Never assume stability based on short-term success. Oblivion’s bugs are patient, and they love to surface hours after the damage is done.
Final Advice for Long-Term Playthroughs
The permanent enchantment glitch is a scalpel, not a sledgehammer. Used carefully, it lets you smooth rough edges in Oblivion Remastered’s progression and create builds that feel powerful without feeling broken.
Push it too far, and the game will push back in ways that no amount of gear or skill can fix. Respect the engine, keep your saves clean, and remember that the most satisfying god builds are the ones that still let the world function.
Oblivion has always rewarded players who understand its systems, not just those who overpower them.