Obenseuer/Modding:Game Decompilation
Debugging
Calling UnityEngine.Debug.Log(Object) from a mod will print to the in-game console (F1 to access) as well as your Player.log file in your %Appdata%/../LocalLow/Loiste Interactive/Obenseuer/ directory.
The in-game console will format UnityEngine.Debug.Warn(Object) to be coloured yellow and UnityEngine.Debug.Error(Object) to be coloured red for better readability.
Please never submit bug reports to the official bug reporting GitHub page with a modded game instance. Disable or uninstall your modloader first and revert any manual file modifications (Steam game file verification will do this for you).
Reading Code
Obenseuer is a Unity game for Unity 2019.4.41f2 Mono. This makes it very simple to read source code for scripts as it is all in CIL.
To read code, you can either decompile the compiled assembly in its entirety using a tool such as:
Or you can read the decompiled output from an IDE while writing a mod after referencing the game's assembly, both JetBrains Rider and Microsoft Visual Studio provide this functionality.
Unity compiles 2 main assemblies which we care about (the rest are either third party libraries or default Unity assemblies which come with every game):
Reading Unity Documentation
If you need to reference a default Unity class, it is recommended to read the official Unity documentation at https://docs.unity3d.com/2019.4/Documentation/ScriptReference/index.html.
Browsing Scene Hierarchy In-Game
One of the ways you can browse scene hierarchy in-game is to use a runtime editor. There are two major options: