UnityExplorer 4.5.0

General

• Due to limited room on the main navigation bar, the "Mouse Inspector" has moved into the "Inspector" panel

Clipboard

Implemented a Clipboard "copy and paste" system.

• There is a new panel called "Clipboard" to see your current paste value, or clear it (resets it to null)
• Can copy the value from any member in a Reflection Inspector, Enumerable or Dictionary, and from the target of any Inspector tab
• Can paste values onto any member in a Reflection Inspector, Enumerable or Dictionary
• Non-parsable arguments in Method/Property Evaluators now allow pasting values instead of using a dropdown
• The C# Console now has helper methods Copy(obj) and Paste() for accessing the Clipboard

Syntax Highlighting

• Methods in the Inspector now display their arguments in their title, to more easily tell similar methods apart
• Built-in system types now use their shorthand name (eg float instead of System.Single)
• Arrays, including multi-dimensional arrays, are now processed properly
• ref, in and out parameters are now processed properly, although they will all just say ref

Notifications

Implemented a popup notification system.

• Currently only really used by the Clipboard, may expand for other uses in the future

UnityExplorer 4.4.4

This is a minor release. The fixes should not affect any of the games on Thunderstore, so it has not been released there.

• Increased project language version to C# 9.0
• Bumped UniverseLib to 1.0.2
• Fixed a niche bug where the C# Console's TextWriter could be disposed for some reason.
• Fixed a potential NullReferenceException with the "World" Inspect-under-mouse.

UnityExplorer 4.4.3

Method Evaluating

The evaluate widget in the Inspector has been improved.

• It is now possible to evaluate any method.
• For Type arguments, an input field with an autocompleter is provided to select your desired Type.
• For other non-parsable arguments, you can select from any of the active inspector tabs via a dropdown to use for the argument. Only tabs which are inspecting a valid object for the argument will be included in the dropdown. Eg, if the argument was of type GameObject, all GameObjects you are inspecting will be available in the dropdown.

Enum values

Enum values now use an input field with autocomplete instead of a dropdown to set your desired value. This is to help with enums that have lots of values, where using a dropdown was inconvenient. You can press the arrow button on the right side of the input field to see all values and choose them that way, which is basically the same as using the old dropdown method.

UnityExplorer 4.4.2

• Fixed an issue with MelonLoader which resulted in a noticeable FPS drop until the HideAndDontSave "scene" was inspected.

UnityExplorer 4.4.1

• The search filtering on the Scene Explorer now only processes when you end editing (press enter or focus something else) to improve performance
• Fixed an issue with component cells showing a white background on some games
• Updated libs

UnityExplorer 4.4.0

• Implemented UniverseLib to fix conflicts with BepInExConfigManager and MelonPreferencesManager.
• Fixed a null ptr exception which could occur in some games when attempting to load the AssetBundle (now moved to UniverseLib)

UnityExplorer 4.3.5

• Fixed issue with games that have stripped UnloadAllAssetBundles
• Fixed bug causing the Scene Loader to disappear in recent versions
• Added a search filter to the scene loader dropdown for games with many scenes

UnityExplorer 4.3.4

• Fixed in issue with the Logs folder not being created since the previous update

UnityExplorer 4.3.3

• Fix rare issue with input on games which use InputSystem
• Added a Harmony patch on AssetBundle.UnloadAllAssetBundles to prevent UnityExplorer's bundle being unloaded
• Added a try/catch to IsNullOrDestroyed to prevent a rare issue
• Fixed IOUtility.EnsureValidDirectory creating filepaths as folders in some cases

UnityExplorer 4.3.2

Hotfix for an issue with the code in generated hooks.

• Arrays and closed generic types (eg string[] or List<object>) should no longer cause any issues in generated hook code. Was going to write a parser for this but it seems Harmony's FullDescription() extension is enough to solve it.