New Developer Console in Beta

this will be fixed >:D

6 Likes

Long live OCD related fixes!

On a more serious note, so far the console is a great improvement in terms of usability and utility. It could however benefit from some UI improvements. It’s clearly not as polished as the live version, although it’s a beta and as such I assume this component is still being worked on.

3 Likes

Also if you type /newconsole to bring up the new console, then click the X upper right. Typing /newconsole wont bring it up again until you type it one more time. Looks like clicking the X doesn’t reset the command toggle.

5 Likes

Is there any way to give print messages a separate color?

2 Likes

Though this would be a cool feature, I don’t think this will be added.

Oof.

1 Like

you can make them blue with TestService:Message

4 Likes

We have removed the limits to Client/Server logs in the new Developer Console. I advise avoiding the old console if your game is very print() heavy, but the new one will handle that case just fine. Just keep in mind that the new Developer Console will only keep the last 500 lines printed.

2 Likes

Couple of issues that are bothering me with the new console.

  1. When I open the console for the first time and switch to the server tab, it’s completely empty and only displays the server log after I attempt a console command, or if I wait for something to be printed. However, if I switch between client and server logs, the problem happens again.
  1. There is no padding beneath text. :frowning:

image

  1. Intuitively, I want to click and drag the console window around by the top bar, however there is a transparent border around the whole window that keeps fooling me - I cannot drag the window by clicking on the top of this transparent border. It would be a nice QoL thing if the draggable part of the window was extended upwards to include this border.
20 Likes

Thanks for reporting those 3 things; I noticed them too, today. Great pictures

Hope they get resolved soon

1 Like

Thanks for fixing this :slight_smile:

2 Likes

One thing that’s been really tedious is that the console seems to lose any memory of command history (pressing up arrow to recall a previously run command) after you’ve closed it. When re-opening the console, attemting to recall a command will do nothing. I don’t think this was an issue in the old console.

8 Likes

Maybe if the log was less transparent it would be a lot easier to read data. So much info is lovely but when it’s black on black it’s really confusing an option to tweak the transparency would be nice.

4 Likes

The console needs to be able to anchor itself to the bottom, so that when new messages come in, the canvas position is set at the end. This ensures new messages are always shown.

I am currently debugging an issue with a client freeze and determining exactly where it happens with prints, and this missing feature is making my life impossible right now with the new console, since I can’t scroll as the client freezes. Really needs to have anchoring to the bottom before going out of “beta”!

4 Likes

Isn’t it out of beta yet? I can’t seem to open the old console. Pressing F9 always opens the new one.

If you type /console in chat you still get the old one, luckily.

6 Likes

Thank you!

I must agree, the console is missing some previous thing of the previous console which I find essential for work. A current example of this would be the fact you can no longer press the Up / Down arrows to bring up your last few inputs in the Lua command bar.

4 Likes

The new console doesn’t support gamepad input, and it’s a bit too transparent for me.

I can confirm this command will open the new console now, but /oldconsole still works.

1 Like

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.