This is amazing! The autocomplete command bar is just too good. However, i noticed that built in methods now don’t have a thicker outline over them like keywords do. Is this change intentional so that we may differentiate between keywords and methods easier?
I’d like to see pre-sets for color blind people, but nice update overall.
If they introduce a new set of Script Editor and Command Bar improvements, does that we can color the error line?
Such a great update! Color Presets is a nice new idea with which the user can choose which one is going to use and it even has the ability to create their own colour scheme. Also, the command bar improvements are great which makes writing the scripts inside of it a lot easier. Thanks
It would be a QoL improvement to add these back for OOP. Please. As well as being able to set font preferences for certain highlights such as the built in ones as they appear bold while I’d want this not to be.
We’ll look into this! Any suggestions?
Is there currently a setting to set the command bar background colour?
Having the colours in the command bar match the script editor is nice, but they don’t match the background colour:
So currently, the command bar is illegible!
I use a dark background with light theme to have contrast between the two.
This is fixed internally. In future versions, the Command line will use the same background color as the script editor for exactly this reason.
Thank you for bringing this up! We’re adding customization options for those keywords as part of Semantic Highlighting in the next release!
Me, who is crazy: Why is there no end at the end of the function?
Ok anyways, two (wait, THREE?) announcements in less than 12 hours? Wow. Keep up the great work on the script editor! This really helps with scripting.
This. Is. Epic. Maybe some quick Vector3 values later?
Btw I gave the hundredth like not to brag, just a fact
I don’t have any vision problems, so I’m hardly an authority, but Microsoft has a high contrast theme built into VSCode that you might be able to borrow colors from. It looks like this:
It highlights
local
differently from the other keywords because of how it’s scoped (it’s a storage modifier according to VSCode) but that’s probably not necessary for Roblox.
There are also high contrast variants of Monokai that you could use.
Wow, in terms of picking a specific colour, this is really ideal! Thank you so much! Now I can select colours without switching tabs between my place and the script I am working on
I love this, but please allow us to define high-lightable words/delimiters and have access to that functionality through plugins
…I might need that at some point soon
It would be lovely to be able to have plugin-access to core script-editor functionalities. I think lots of mainly API-focused developers would consider it a godsend.
Will we ever get a feature to quickly share script color themes, without having to change them all manually? Perhaps copy/paste color sharing?
I noticed the color picker a few weeks back and was in love with it, it made it so nice and easy to pick and visualize colors.
Then on top of that, last night I tried to program something in the command bar and saw the color. The look on my face.
Thank you guys for this amazing update, let’s see where this goes and what other amazing things you add to the script editor!
Will we ever be able to import our own Text fonts? That’d be really cool.
Was there any bug fixes for the script editor? Lots of people have been experiencing extreme lag whenever using the script editor and the only way to stop the lag is to drag the script editor out of the main Roblox window.
Not sure when this started happening, but non-closed functions and “if” statements are no longer being properly linted within the editor unless the last line of code in the script is empty. The Script Analysis window still catches the issue, but the red underscores within the editor are not present. Considering this update focused on the Studio Script Editor, I suspect this issue could be related to the update.
Problem Details:
The PlayerAdded function in the following code is not closed properly. Yet, if there is anything on the last line of the script (there is a tab in this case), Studio does not lint the issue correctly.
If the last line is empty, this issue is linted correctly:
Here is a place file which contains two scripts that show this behavior. The scripts are located in ServerScriptService:
LintingIssue_201009.rbxl (20.7 KB)
I was criticizing the Editor and now I retract myself. THANK YOU! Now looks better, I do noticed some deprecated Globals are getting highlighted and they weren’t before.
I don’t know about anyone else but there was a bug where the little color picker appeared on the lines side of the script editor. Also, for a while, the command bar was syntax highlighting.
Still leaves me to wonder when we get this feature in text boxes.