Can't get Console++ working

[powershellwhizz]

HI there, I have a feeling I am doing something really dumb here. As a disclaimer, I am hobbyist programmer so I might be missing something obvious in your description of how to set it up.

No matter what I do, I cannot get the console++ to display any kind of debug info I see in your screenshot, and none of the commands worth either. Here is what I did to set it up:

Install your extension Run the command "install console++" - this came back and said it was successful.

All other commands work like importing scripts and saving them. I bring up the console but when I type and press enter, nothing happens.

I then tried to do it all manually via onelivesleft repo. I downloaded the 2 files manually and placed them in in <your user folder>/Documents/Tabletop Simulator/Console suggested on his repo - well, actually I didn't need to, because when I went to do so I noticed they were already there (I guess your "install console++ command works after all!)

For me my documents folder isn't in the usual location, I moved it. But to rule this out I even copied the 2 files to all potential my docs locations (I didn't even move them, I copied them). Still no joy.

Any idea what I am doing wrong here? One bit I am unsure of is where you say to add #include <vscode/console> to your global scope. What is this? I added it to the global.lua file but that didn't fix it, in fact it erroed saying it didn't recognise "include". But I did see on someone elses code I've downloaded they had require("vscode/console") in one the lua files. Can you clear this up for me please if I am doing something wrong?

Thanks.

[TeamDman]

I did get a game saved message, ~~but I can't seem to get anything else to happen~~

commands don't seem to work, but I do see error messages and prints :D

[rddslt]

Same for me. Did anyone work this out?

When I add the require("vscode/console") code to the Global lua script, it puts a load of code into the top of that Global script. Curiously, that code then doesn't show in VSCode, although the communication between VSCode and TTS is otherwise good (i.e. when you change TTS save, it changes VSC, and when you Save and Play from VSC it updates TTS). This might be a separate issue or perhaps it is by design.