You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unity's model highly encourages not using any static instances of classes, but instead, to attach a MonoBehaviour to a GameObject, Component, ScriptableObject, etc. Unfortunately, this makes asl-help-unity completely unable to function for classes and games like that.
Luckily, there are ways to find these attached classes within the scene. Each Unity Scene (the C++ versions) contains a linked list of loaded GameObjects. These objects are often loaded in the same order every time. Each of these GameObjects contains an array of attached Components. These components contain the scripts, which finally get linked to the actual MonoClass.
Unity's model highly encourages not using any static instances of classes, but instead, to attach a
MonoBehaviour
to aGameObject
,Component
,ScriptableObject
, etc. Unfortunately, this makesasl-help-unity
completely unable to function for classes and games like that.Luckily, there are ways to find these attached classes within the scene. Each Unity
Scene
(the C++ versions) contains a linked list of loadedGameObject
s. These objects are often loaded in the same order every time. Each of theseGameObject
s contains an array of attachedComponent
s. These components contain the scripts, which finally get linked to the actualMonoClass
.Some helpful code can be found at Micrologist/UnityInstanceDumper.
The text was updated successfully, but these errors were encountered: