We try to to make it work with the most, but for some games, you just have problems. For example I can't call on UnityEngine.SceneManagement before v5.4 so that is why we has have to have separate releases. To get the FULL benefits of DevTools, the game should be about 2017.1, it will still function below that but features start decreasing. I tried it with the Forest though and never had an issue. Note: The Forest has alot of custom loading, so it's prop also filtering the assemblies it will ref.
I have an update I'm working on to fix some most of it, but for now use the legacy ver. The newer version requires about 5.5 to work fully due to Unity splitting DLL's all the time. It's the game version, try using the Legacy version, it's not as nice but it works for sure. However, everything else works just fine including the fallback console which helps a lot with on the fly testing, thanks again for the release, I definitely appreciate it! =P So I've finally gotten to mess around with this after finishing another project and it works really well! Sadly, Inspector and uREPL Console did not work with the game I was working on (The Forest) NET 4.6.2): Īlternate (Legacy) Version: (For troublesome games and Legacy Unity version game below v5.6.7)ĭescription: Unity Runtime DevTools (Legacy) Update v1.05 (Requires Unity Game Version 2019.3+ /. Update v1.02: See here for datails: Unity Runtime DevTools v1.02 (Update) If using standalone injector use the following settings:Īdvanced Unity Hacking Techniques - Methods of Adding Custom Assets Suggestions are welcome.Įither Doorstop, BepInEx 5+, or a StandAlone Injector.
I used a couple of private tools I made that allowed this to happen.įollow the install instructions in README. You'll have a Dev C# REPL Console and hierarchy/inspector in any Unity game, and many more! It was built with Unity 5.5.5f so it should run on the majority of today's Unity games. I rewrote them to work with this method of loading at run-time. Some are projects on Github that aren't published on the asset store. I went through all the Dev/Debugging assets for Unity and chose the best of each category. Each module is self-contained and destroyed on Load/Unload of module. Think kinda Cheat Engine within the game during run-time. Screen (Note that Becastled is Unity 2020.2.1): NOTE: If your game is not one of these versions, continue to use v1.04. This will get you going again with inspecting newer game versions. This is an interim update until v2 which is a whole new design and logic system.
This update provides support for Unity version's 2019.1.3+ when Unity starting breaking shit again.
DevTools Update v1.05 (Unity 2020+ Support)