As demonstrated in the video, when I write obvious code that will be flagged by Roblox debugger (ex: writing a Enum value without assigning a variable or not finishing the Enum directory), the debugger doesn’t warn the user. This can be especially problematic for developers who don’t fully grasp the full detail of how code works, where to find a object through a set directory and also for debugging code through finding a red line in a segmented part of the code indicated by Script Editor. This bug affects both non-beta and beta new Studio UI.
The beta features I have activated are UIDragDetectors and New Studio UI (Gen Preview).
In order to reproduce this bug, you can simply create a script and try to write something simple as getting a workspace object. You will instantly notice Script Editor does not give you a visual directory of objects inside of workspace for you to select and extends to more than just Service objects, also variables.
Expected behavior
Errors are highlighted with a red underline or by the Script Editor’s Right bar. This also extends to Warnings.
There is a visual directory provided by Script Editor (Much like any other Editors like Visual Studio) when trying to access a variable or a object’s children that has already been predefined.
This occurs in every game I have access to. If needed, I can show you another demonstration in another place and see if the same result is occuring. This bug essentially makes Script Editor have no functionality besides allowing the developer to code and Output catching errors.
Does this also happen on new games (i.e. if you just open baseplate and insert a script)?
Could you also check what values Workspace.LuauTypeCheckMode and Workspace.UseNewLuauTypeSolver are set to? If not already configured to Strict/Enabled, could you try those? (you may need to re-open the place after updating them)
These are my game Luau types. This is before Strict is enabled. However, Script Editor still refuses to function properly. Even with Strict active, the same issue persists.
I have multiple plugins installed that do not enhance/downgrade Script Editor. In the New Game demonstration, plugins absolutely didn’t affect my Script Editor.
If more information is needed, I can provide more. It appears games made before a certain time date the bug started persisting are affected.
I can’t provide my upcoming game Voxelflict (the one being shown) or any serious games I’ve made. However, I can find other games I have made that are affected by this issue and send you a .rbxl file from there.
Any rbxl that repros the problem works. Just to cover our bases could you also check if you see the problem with the UseNewLuauTypeSolver set to Disabled in your old games?
Update: After disabling NewLuauTypeSolver , my Script Editor debugger and directory reappeared. It appears that NewLuauTypeSolver is currently bugged for older games published after a certain time date, which causes Script Editor to malfunction when it is enabled. However, this does not mean the issue was already solved, as enabling NewLuauTypeSolver causes the bug to reoccur. For now, disabling it allows Script Editor to function as usual as if its a Visual Studio Code functionality while enabling it makes Script Editor experience the same issue again.
Hello! We’ve just rolled out a fix that should mean the new type solver is able to promptly analyze your place file (or at least the one you provided, thank you for that). I’m going to mark this as fixed for now, but do not hesitate to reach out, especially if you find the issue is not resolved for your place file.
