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
One of the ideas I've been playing around with in my head is how to use all the indexing I'm able to do to collect more information about what's in Core XML. Not really to expose to modders, but just for personal information. I finally ended up needing something like that for the Generate Menu, where I collect information on how much each C# property is used in XML so that I can order the list of properties in the Generate Menu.
The solution I came up with was to just create the class, expose it's information through public static fields and throw a debug breakpoint somewhere to gather it during run and comment out all that code afterwards for release. Instead of doing all of that, I think we should be able to have it run only in Debug mode and expose some debug actions to show that information
The text was updated successfully, but these errors were encountered:
One of the ideas I've been playing around with in my head is how to use all the indexing I'm able to do to collect more information about what's in Core XML. Not really to expose to modders, but just for personal information. I finally ended up needing something like that for the Generate Menu, where I collect information on how much each C# property is used in XML so that I can order the list of properties in the Generate Menu.
The solution I came up with was to just create the class, expose it's information through public static fields and throw a debug breakpoint somewhere to gather it during run and comment out all that code afterwards for release. Instead of doing all of that, I think we should be able to have it run only in Debug mode and expose some debug actions to show that information
The text was updated successfully, but these errors were encountered: