Tulip Player developer console trigger debugger no longer working?

It looks like at some point recently the old method to allow debugging of app triggers in tulip player was disabled, in which you could open the chrome developer console during a Tulip Player session and run $t.Debug.debugTriggers = true to get access to a wealth of debugging information for triggers running in an app:

Trying this now results only in a flood of errors:

Did this get moved behind a feature flag or changed to something else? This is a critical part of how our developers debug unexpected app behavior, without it we have no way to debug connector function failures or other errors.

Hi @aaronbroussard,

This functionality did change in r245 - apologies for the miss of not properly announcing this. We’ve updated it to run as a function so you can now enable debugging with the following: