Script editor autocomplete doesn't work and syntax errors aren't highlighted.

Bug Reports Studio Bugs
,
1

NOTICE!
** Turning off the “New LuaU Type Solver” fixes this issue. **

Hey there, Roblox.

Recently while trying to program my game, I ran into a frustrating issue where the script editor no longer autocompletes my code.

For example >> I type “lo” and it should give me a recommendation to complete it with “local”

However, this doesn’t work in my main game. It seems that it works inside of local games, but not team create games.

Furthermore, I’ve tested this issue on other devices and with other friends, and they have this same issue.

Image 1: Should have a recommendation to complete to “local”
image
Image 2: No red underline to indicate that there is a syntax error
image

Expected behavior

I expect that these issues are resolved and that hopefully I’ll be able to use autocomplete and syntax error catching again.

Device Specs:

Windows 11 Pro, RX 7900 XTX, Ryzen 9 9950X, 96GB DDR5

4 Likes
2

yea i’m having this issue too :sob:

2 Likes
3

Hi @elunarir and @eljefeistheboss, could you open the Script Analysis widget to check for any error messages there?

Also, could you check which beta features you have enabled in Studio?

4

Hey there @yohooyohoo
Can do!

It seems like there are no errors relating to this issue. Unfortunately, I don’t think this is an in-game glitch, I think this may be a engine bug. Extra info: It seems to work in a private place, but not in my main game under my group and under Team Create.

As for the beta features, I have every single one enabled but the “Next Gen Studio Preview”. I hope this helps!

5

@eljefeistheboss Thanks for the info! One more thing—could you try disabling the “New Luau Type Solver” in the Beta Features panel to the issue is still persist? We may also need to DM you to request the place file to help our team investigate the issue.

6

Got it.

Turning off the New Luau Type Solver actually fixes this issue. The problems I had previously were fixed by turning this beta feature off. Hope this helps, and thank you for the temporary solution!

1 Like
7

Hello! Thank you for beta testing the new Luau type solver, though I’m sorry to hear that you’re running into issues. I get pretty annoyed when autocomplete isn’t working the way I expect!

Would you be willing to share your place file in a private message so that we can debug this issue? We’re tracking a class of issues here, where the new solver is unable to handle exceptionally large types.

8

Sure thing! Just message me, and I’d be happy to send you the place file. (I don’t want to send it in a public forum because of leaking issues, etc)

2 Likes
9

Just checking in: we’ve rolled back the change that caused issues for you when the New Luau Type Solver beta is enabled, so you should be able to re-enable it and still have autocomplete and error reporting.

I’ll be keeping this issue open to fix the root cause.

10

Awesome. Good luck to you guys!

11

Hello! We released an update that should fix this. Please let us know if you encounter any further issues, and thank you again for beta testing the new Luau solver!

1 Like
12

Hi, apologies for pinging an old thread and I don’t know if this is the right place but I thought I’d just let you know that the issue still persists, I had to disable it to get back autocomplete and syntax errors.

13

Sorry to hear! Opening up a new ticket would be the best way to move forward, and if you could send a reproduction (for example, sending a place file in a private message) that would help us narrow down the specific issue.