I don’t know if you compared Rojo as if it was a code editor, but it isn’t.
This was asked a while ago on #studio-features, and I remember the conclusion being no. I heard Roblox Staff uses Rojo to use VSCode and such to implement new features, so that would be cool to see, but it kind of doesn’t make sense to have that there…
I meant support for Rojo or just support for other code editors using another program like Rojo (built-in).
What I see happening now is the code editor getting upgrades (which is not a bad thing). However, when using other code editors that already have these features, I can’t see why Roblox doesn’t want to natively support them. The only reason I see is to lock us developers to only using Roblox studio.
As you said, it’s probably not going to happen Just like Linux support 
Go To Declaration? YES! I waited for it so long…it will really help us.
I think it means it can’t find a local of it I believe.
But there is, a local in it but somehow it can’t detect it.
Or, maybe Counter_Txt looks like it’s in screenGUI but it isn’t.
The issue they’re displaying is the Type Checker looking inside the ScreenGui class for Counter_Txt rather than looking for it as a child.
Ahh kk, I am bad with scripts xd but I still try anyway to learn.
very evident that this issue is the result of a change of this script editor update.
i’d like to see this addressed, this is (what i’d call) a big issue and is quite problematic for any plugin that wants to edit the source quickly - which of course exists. is this intended functionality? i’d hope not
what’s the meaning of “Scripts Are Non-Strict By Default”?
I’m not good at English so I can’t know the exact meaning well, xd
it means scripts don’t have the strict thing on by default
If “Luau-Powered Go To Declaration” is enabled, CTRL+F12 has no response and will not jump to the function declaration
OS:Windows10
Studio Ver:0.474，0.475
Does the script have --!strict at the top? And do you have Scripts are Non-Strict by default enabled?
I’m not sure if you ever got an answer to this, but the issue is it UI.Counter_Txt isn’t a member (like a property) of the ScreenGui. It is bad practice to index for children like this anyway – use Instance:FindFirstChild instead.
local Counter_Txt = UI:FindFirstChild("Counter_Txt") :: TextLabel
There is no “–!strict” in the script
All of my colleagues also have same problem. We have to disable all “Luau-Powered ***” function in Beta Features
For the duration of the beta(s), you will need to put either --!strict or --!nonstrict at the top of your script, or opt into the Scripts are Non-strict by default beta, in addition to the Luau-Powered _ betas for the contained features to work as expected, with --!strict typically giving the best results.
This step will not be necessary in the full release.
Because these features are powered by the Luau type system, the Luau type system must be enabled for the scripts in question, or the editor will have no data to work with.
Hi ArtBlart,
Thanks for sharing! I wonder have you ever using team create collaborative mode? Because monitoring script source change event and replace source by plugin may not work as you expect with that feature on.
Also by the way, we are removing delay text sync from beta feature😄
Part cannot be recognized
Humanoid cannot be recognized but humanoid work
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.