Bug Issue: Game controller doesn't call stack for some runtime errors

Pages: 1


  • Subscriber - Stencyl Indie
  • *
June 02, 2020, 01:38:23 pm
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.

Issue updated by Justin - June 03, 2020, 02:27:47 am
  • Tags added: 4.0.3


  • Master Stencyler
  • *
June 04, 2020, 01:29:19 am
In b10546 I've added callstack printing for attribute get/set operations and resource id/name references that don't work. I've also added a little blurb about turning on debug mode to see the callstack if it's not enabled. These changes will be available in public release 4.0.3.
  • Issue Assigned from (none) to Justin
  • Status changed from New to Resolved

Pages: 1


  • Reported
    June 02, 2020, 01:38:23 pm
  • Updated
    June 04, 2020, 01:29:19 am

  • View Status
  • Type
  • Status
  • Priority
  • Version
  • Fixed in
  • Assigned to
  • Category
    Compiling/Testing Games