I want to make a mod with the new API, and to do so I inevitably need to debug variables ingame through testing. Calling DebugCommands.print(...) with a string input (from DebugCommands on the documentation[vortexbuffer.com]) gives me a failed script load: "Attempt to access non-existent member 'print' of the module 'necro.debug.DebugCommands'. I worked out that with the following escape menu options
1: options -> misc options -> show advanced settings turned on
2: options -> misc options -> enable debug console: set to on or single player
I had expected to see either print() or DebugCommands.print() messages to show up somewhere ingame. The autogenerated code file from creating a new mod (customize -> mods -> new mod) said:

-- Press F1 to display debug output in-game

And F1 has not done that. There is no debug output toggle control in the settings, nor F1 or tilde or any of the function keys seem to turn on such a menu.

I noticed the output from the print() messages in my lua mod file is buffered to
when the game is closed. So I can debug through that, but it's just tedious to close the game to check information there every time. I imagine DebugVisuals[vortexbuffer.com] can be used for this somehow, and maybe that is what the debug console is meant to do, but it's not clear how to do that. If there was better documentation, at least for the debug modules, I think it would be easier to make mods with this API, and the API does seem really comprehensive.

(Running on Windows 10)

Any help would be appreciated. Thanks