2026.4.0: Duplicate mscorlib - Bug Fix

Features:

- [Feature-2026-5] Added support for Unity UI Toolkit (UIElements) custom types in the compatibility component. Custom VisualElement/UXML types are now automatically skipped from obfuscation to keep UXML bindings valid.

Improvements:

- [Imprv-2026-7] The Anti-Tampering component only supported files up to 2GB (Int32) in size. This has been increased by using Int64 [thanks Alex].

Bug Fixes:

- [Bug-2026-9] Fixed an issue where obfuscated .NET Standard assemblies could get an additional mscorlib reference, causing UnityLinker/IL2CPP builds to fail on DOTS/Unity.Entities projects [thanks Mikael].

2026.3.0: Addressable Binary - Update

Features:

- [Feature-2026-4] Added support for the Addressable binary catalog, next to json catalog.

Improvements:

- [Imprv-2026-6] Optimized the anti-tampering component to use a more efficient checksum algorithm. Depending on the runtime system, hardware acceleration is not supported, which caused the integrity checks to take a long time on app/game startup.

2026.2.2: Maintenance - Update

Improvements:

- [Imprv-2026-5] Refactored the stack trace deobfuscation window tool. It now autoloads the settings mapping and has been optimized to deobfuscate stack traces more effectively [thanks Daztrax].

Bug Fixes:

- [Bug-2026-8] Fixed an issue where enabling control flow obfuscation caused the obfuscated build to fail. The cause was incorrectly resolved try/catch blocks.

- [Bug-2026-7] Enabling public property and field obfuscation caused issues in some IL2CPP builds due to named parameters that IL2CPP could not resolve [thanks Lemior].

2026.2.1: Addressable Shield - Update

Features:

- [Feature-2026-3] Added support for Addressable Shield (Unity 6+). This allows you to obfuscate addressable bundles that are encrypted using Addressable Shield.

2026.2.0: Security & Performance - Update

Features:

- [Feature-2026-2] Add file-based asset analysis cache using hash validation to skip re-analysis of unchanged assets across builds. The cache is stored in GUPS/Obfuscator/Cache/Assets. This reduces the build time, for a second or third etc. build.

- [Feature-2026-1] Added IL2CPP anti-tampering (code integrity check) support for standalone builds (Windows, Linux, macOS). Mono and IL2CPP are now both supported.

Note: Added a .gitignore under GUPS/Obfuscator. I recommend you to keep it or you have to add the following directories to your global gitignore:

**/GUPS/Obfuscator/Temp/

**/GUPS/Obfuscator/Cache/

2026.1.4: Maintenance - Update

Bug Fixes:

- [Bug-2026-6] In Addressables, AssetBundleRequestOptions do not always have a fixed order in the catalog.json file, causing a crc mismatch. This has been fixed [thanks Masakami].

2026.1.3: Maintenance - Update

Improvements:

- [Imprv-2026-4] Optimization of string obfuscation to reduce build size by reusing obfuscated strings that have the same value [thanks Pierre].

2026.1.2: Maintenance - Update

Improvements:

- [Imprv-2026-3] When adding namespaces that are to be skipped by obfuscation (or vice versa included), empty entries are now filtered out, those are always added by mistake [thanks Gleb].

- [Imprv-2026-2] Refactoring of string obfuscation to split string methods into multiple types, so that the 65k method limit of IL2CPP does not cause problems, also optimized performance when reading the string [thanks Pierre].

Bug Fixes:

- [Bug-2026-5] Fixed a burst compiler error. Burst error BC1347: Invalid first argument (code: Call) of string.Format(format, ...). Expecting a const/literal string. Burst compiled code is not valid with string obfuscation, so the string obfuscation module checks for that [thanks Gleb & Lee].

- [Bug-2026-4] Fixed an issue where post-processing (Unity 6000.2 and above) might trigger an exception: Unsupported asset class type name '...'[thanks Nikita].

2026.1.1: Maintenance - Update

Improvements:

- [Imprv-2026-1] Scenes must be added to the build settings to be included in the obfuscator analysis. Unanalyzed scenes can lead to incorrectly functioning UI events (or similiar). Now, a warning is displayed if a scene is skipped when it is opened in the editor but is not included in the build settings [thanks Jiyong].

Bug Fixes:

- [Bug-2026-3] When a Unity event referenced a Unity script (e.g., MonoBehaviors), the reference was lost [thanks Joe].

- [Bug-2026-2] Another problem with WebGL builds has been fixed, where some MonoBehaviour references were not being obfuscated correctly [thanks Angel].

- [Bug-2026-1] There was a problem when loading assets that had missing references (it looks like *Broken text PPtr in file(Assets/.../Player.controller). Local file identifier (1115794168221349032) doesn't exist!*), which caused the obfuscation process to abort. This was not correct; the error is now displayed as a warning. But you might have to look into that, because the error means that some references no longer exist on your asset [thanks Damian].

2026.1: Web - Update

The obfuscator now requires NetStandard 2.1 as a minimum requirement.

Bug Fixes:

- [Bug-2025-8] There was a major issue where references to assets in web builds were not processed correctly. This resulted in MonoBehaviour failing to load.

2025.4: Attributes - Update

Features:

- [Feature-2025-11] Removes various Unity-specific attributes from assemblies after obfuscation, thereby removing metadata that is only relevant in the Unity Editor and allows conclusions to be drawn about the code.

2025.3: Custom Obfuscation - Update

Features:

- [Feature-2025-10] Assemblies (.dll files) can now be obfuscated outside of a Unity build. To do this, open the `Windows -> GuardingPearSoftware -> Obfuscator -> Obfuscate` window. This allows you to obfuscate assemblies of assets that you want to publish in the Asset Store or elsewhere, for example.

Improvements:

- [Imprv-2025-5] Placed the editor code under `GUPS\Editor\Source` in a custom editor assembly definition, to prevent runtime loading [thanks Champi67].

2025.2: Security - Update

Features:

- [Feature-2025-9] Support for signing assemblies has been added. You can now sign your Mono assemblies with a strong name (RSA private key) to uniquely identify the origin of your code! The added component can be found under the *Security* tab and is called `Sign Assembly`.

- [Feature-2025-8] The `Anti Tampering` component has been completely redesigned to meet modern security challenges and got renamed to `Code Integrity Check`. It is also now out of beta!

2025.1

The Obfuscator now follows a yearly versioning system, just like all the other GuardingPearSoftware assets. Along with that, the directory and base namespace have changed. You can now find the Obfuscator under Assets/GUPS/Obfuscator, and the namespace is now GUPS instead of OPS.

We also moved the Obfuscator settings to the Project Settings, so you can now access them here: Project Settings -> GuardingPearSoftware -> Obfuscator

Similarly, the deobfuscation stack trace has a new location: Windows -> GuardingPearSoftware -> Obfuscator -> Error-Stack-Track

You might be wondering why all these changes happened. That’s a fair question! A few years ago, the company rebranded from OrangePearSoftware (OPS) to GuardingPearSoftware (GUPS). Back then, I focused on bug fixes and adding features to the Obfuscator and didn’t have time to update the naming and structure. But now, we’ve finally made it happen.

Here’s what this means for you:

- Obfuscator Settings: Project Settings -> GuardingPearSoftware -> Obfuscator

- Deobfuscation Window: Windows -> GuardingPearSoftware -> Obfuscator -> Error-Stack-Track

- Obfuscator Attributes: If you’re using them, replace OPS with GUPS. Usually, a simple project-wide replacement from OPS.Obfuscator.Attribute to GUPS.Obfuscator.Attribute will do the trick.

Updating from a previous version:

Before you update, make sure to back up your Obfuscator Settings File. You can find it here:

Assets/OPS/Obfuscator/Settings/Obfuscator_Settings.json

Next, delete the current Assets/OPS directory.

Then, install the new Obfuscator and move your settings file to the new location:

Assets/GUPS/Obfuscator/Settings/Obfuscator_Settings.json

If you have any questions, just ask. I’m always happy to help!

Obfuscator Source | Plug and Play Code Protection | v2026