5.4.0: Mapping - Update

- Feature: The obfuscation mapping can now be loaded from a web endpoint (Get) and saved at a web endpoint (Post).

- Improvement: If an obfuscation mapping could not be saved in the location specified by the user, it is saved in the obfuscator temp directory 'Assets\OPS\Obfuscator\Temp' [thanks David].

5.3.2: data.unity3d - Hotfix 2

- Fix: Error while obfuscating data.unity3d file '.../data.unity3d': Value cannot be null. Parameter name: _Assembly [thanks David].

- Compatibility: Most compatibility components can now be manually activated or deactivated. Default is activated.

5.3.1: data.unity3d - Hotfix

- Fix: Error while obfuscating data.unity3d file : Unable to read beyond the end of the stream [thanks Josh].

5.3.0: iOS - Update

- Improvement: Unity animation compatibility - You can now customize where animation callbacks should be automatically searched (models, animation clips, animator controllers).

- Improvement: Unity event compatibility - You can now customize where event callbacks should be automatically searched (scenes, prefabs).

- Fix: iOS build - MonoBehaviours were not obfuscated correctly in Unity 2022+ iOS builds. Resulting in MonoBehaviours failed to be resolved while runtime.

5.2.0: Addressable - Update

As this is a major update, it is recommended to remove the current OPS directory, make a backup copy of the Obfuscator settings file and download the new version.

- Feature: Lz4 / Lz4HC - The Obfuscator now supports obfuscation of builds that use compression with Lz4 and Lz4HC. This does not affect your workflow, but only improves the obfuscation of MonoBehaviours, which previously required a workaround.

- Feature: Addressables - A popular Unity asset to address assets from different locations. Obfuscator now supports obfuscation of addressable bundles using the JSON catalog. To activate obfuscation of Addressables activate it under the 'Compatibility' tab [thanks Dmitriy].

- Improvement: Memory usage - Obfuscator estimates the compatibility of assets for obfuscation. This included model or texture files. These were not disposed of correctly after loading, leading to potential memory issues.

- Fix: XCode - Obfuscator failed when creating XCode projects. This has been fixed [thanks Misha].

5.1.7: Burst - Update

- Fix: Obfuscated strings compiled by 'Burst' throw an exception that they cannot call managed code in a native environment. Therefore, strings in 'BurstCompile' jobs are now skipped from obfuscation. They are automatically safe due to their native environment [thanks Curtis].

- Fix: There was a rare case in which a type could not be resolved correctly. This caused an exception when building the Unity project. This is now fixed and even if a type still cannot be resolved, a warning is now displayed and the type is skipped from the obfuscation [thanks Cameron].

5.1.6: MongoDB Realm - Update

- Compatibility: Made the Obfuscator compatible with 'MongoDB Realm' [thanks Hector].

-> Classed that inherite from Realms.IAsymmetricObject, Realms.IEmbeddedObject, Realms.IRealmObject and read/store data in the storage can be skipped from obfuscation to preserve the data integrity.

- Improvement: The random code generation no longer will create random code in classes that are skipped from obfuscation. This often lead to unexpected problems, as these classes were skipped by the user for a specific reason.

5.1.5:

- Fix: When disabling obfuscating for serializeable classes, serializeable fields still got obfuscated [thanks Eric].

- Compatibility: Fixed a compatibility issue with Zenject [thanks Dmitriy].

5.1.4:

- Fix: The obfuscation pipline did not check correctly for a development build. So "NotObfuscatedCauseAttribute" were not added to development builds.

- Fix: When obfuscating "older" .Net-Framework assemblies that had native pdb symbols, those symbols could not be rewritten, causing a failed build. The new default for these are portable pdf symbols (which makes even more sense for unity).

- Compatibility: Fixed a compatibility issue with StateMachineBehaviours when obfuscating ScriptableObjects.

5.1.3:

- Compatibility: .NetStandard - Obfusator 2021 and 2022 now use .NetStandard 2.0 and 2023 and onwards use .NetStandard 2.1.

- QoL: The log writer now checks for invalid file locations.

5.1.2:

- Fix: Bee compiler could not resolve 'OPS.Obfusator.Editor'.

5.1.1:

- Fix: Compatibility with Unity 2023.1 and onwards by switching the obfuscator build to .NetStandard 2.1.

- Add: Support of Meta SDKs - Facebook and Oculus

- Add: Support of Microsoft Playfab.

5.1.0:

- Add: OnRectTransformDimensionsChange will now be skipped from obfuscation for MonoBehaviours.

- Update: The UI / GUI compatibility addon was changed to an Unity-Event addon. Mostly UI / GUI or similiar methods are based on UnityEvent.

When activated (by default it is activated), all methods attached to these events will be skipped.

5.0.5:

- Fix: Compatibility fix for the Universal Render Pipeline (URP).

5.0.4:

- Fix: Json serialization for public fields - Class requires Serializable Attribute.

- Fix: Dependency fix at release build.

5.0.3:

- Fix: OPS.Obfusator.dll assembly was loaded as to obfuscate assembly. Is now a helper assembly.

5.0.2:

- Fix: Reference bug to OPS.Obfusator.dll.

5.0.1:

- Improved Gui/Animation method recognition.

- Obfuscator UI improvement.

- OPS.Obfusator.dll is now an AssemblyDefinitionFile.

- Fix: Removed OPS.Obfusator.dll from release builds.

5.0

== Obfuscator 5.0 Introduction ==

The Obfuscator 5.0 version optimizes the MonoBehaviour protection and brings the obfuscation through

new features on a new level. By introducing ControlFlow Obfuscation, method bodies will be scrambled

and transformed into a nearly human unreadable form. An also new feature is the AntiTampering Obfuscation.

This feature builds a system of micro-checks to prevent modification and keeps hacker away.

4.0.6:

- Fix: While cache generating some NullPointer might happen.

- Fix: Building Addressable Assets will no longer trigger the obfuscator and a so failed build.

- Add: You can now enter a custom log directory, instead of a file path only. In this directory, the log will be seperated by platform.

4.0.5:

- Fix: ArgumentException: ... Type .. has no scope?

4.0.4:

- Fix: On Analyse Scenes / Components - MissingMethodException.

- Fix: Enum wont be obfuscated if 'Obfuscate Serializable Classes' is deactivated.

4.0.3

- Fix: While processing pre build pipeline: System.MissingMethodException

4.0.2

- Fix: InvalidCastException while analysing assemblies.

- Fix: Yaml failed deserialization while analysing assets.

4.0.1

- Add: EventTrigger inspector method will now be recognized too.

4.0

== Obfuscator 4.0 Introduction ==

Version 4.0 of the Obfuscator is a reimplemented Obfuscator from the ground up to increase performance, security and Compatibility with Unity 2018+ versions. For you, the process remains the same. The obfuscator continues to automatically apply the obfuscation at build time. The "Settings" and "Error Stack Track" windows received a facelift to be more intuitive and easier to use. The settings and rename mapping are now stored in a serialized json file. This means for you that you have to readjust the settings in the "Settings" window because of the change and extension of the settings.

It is not necessary to change the rename mapping files. They will still be interpreted normally. But new rename mappings however, will be saved in the new json format.

Most important obfuscation changes:

- You have more options to decide which assemblies you want to obfuscate.

- The string obfuscation is now way more advanced. (Pro only)

- The obfuscation of MonoBehaviour/ScriptableObject/Playable subclasses is way more advanced too. (Pro only)

- Also inspector set values / methods are now even better recognized.

Obfuscator Free