Heya!

I'm currently facing an issue on windows, which I have already solved on linux.

While writing scripts it's quite handy to be able to see the full debug output (I think the client itself cuts it off at something like 50 lines or so). This is mainly in regards to random crashes, NullPointerExceptions etc..

Previously without the JagexLauncher I was able to just run osbot through the terminal, setting the debug port while also getting the console output that way. 
On linux I found a workaround, that involved reading the environment variables of the (3rd party) jagexlauncher.

Afterwards I could just kill the process and set the two needed ones before starting osbot again. ~ Tada - I got console output and am using a jagexaccount.

When trying to achieve something similar on windows, I'm unable to get this to work. 

 

I was wondering, if maybe there was already an parameter, that one could pass to the osbot.jar when running it, that would, idk, open up a terminal, or maybe allow for the whole debug log to be kept.

I'd appreciate any help, guiding me to a solution!

havent tested but you might be able to pipe to the terminal on windows using the -debug flag when patching like so

 

havent tested it as i dont have a jagex accc.

@Muffins sadly that doesn't open a separate terminal, but the idea is great imo.

 

I think I've found somewhat of a solution, using python, currently still testing though.

34 minutes ago, Fegit said:

@Muffins sadly that doesn't open a separate terminal, but the idea is great imo.

 

I think I've found somewhat of a solution, using python, currently still testing though.

lemme test something out, might be able to do it how i envision it

Oh I misread what you meant, yea if you find something I'd be glad if youd share it.