When testing in Debug mode (Windows), the Game Controller doesn't always call the stack for runtime errors it catches.
For example, in the following error types it only gives a generic message:
- com.stencyl.behavior.BehaviorManager getAttribute (127): Warning: Behavior does not exist.
- com.stencyl.Data loadResourceFromMbsByName (201): Resource with name Null doesn't exist
I learned to add 'import haxe.CallStack;' at the start of the relevant class in the Stencyl install directory, and add '+ CallStack.toString(CallStack.callStack())' inside the trace function, but I suggest this should be enabled for all error messages by default.
For example, in the following error types it only gives a generic message:
- com.stencyl.behavior.BehaviorManager getAttribute (127): Warning: Behavior does not exist.
- com.stencyl.Data loadResourceFromMbsByName (201): Resource with name Null doesn't exist
I learned to add 'import haxe.CallStack;' at the start of the relevant class in the Stencyl install directory, and add '+ CallStack.toString(CallStack.callStack())' inside the trace function, but I suggest this should be enabled for all error messages by default.