Most of my coding is filled with these orange underlines!!

Hello!

I encountered this issue early today and decided to wait on it. Nothing has really changed at all!

I keep getting this issue with the orange underline in most of my scripts!

They popped out of nowhere all of a sudden! I restarted the studio/PC, turned off most beta features, and went on a different game. Yet nothing has changed.

People say to turn off the LUA Type thingy..

Nothing has changed at all. I even restarted Roblox Studio and PC!

It’s a very big issue because every time I run the script, the studio crashes, which makes devolpment impossible for me!

  • Beta Features - The only features I have enabled are Dragger Qol, Live Animation Creator, and UI Drag Detectors.

  • I am on Windows 10 PRO

2 Likes

This just randomly popped up for me aswell. I have a whole 5000 line script, and it’s just filled with them, even though the script works completely fine??

This isn’t a bug - it’s a feature. :sweat_smile: It’s from the type checker, hover over them, they detail important info!

The snippet the OP provided is using a method that was deprecated in 2020. While there’s nothing wrong with using your current script, its recommended to create (or find) an Animator under the humanoid and call LoadAnimation on that.

The new luau type solver was rolled out of beta recently, which is more than likely why it only showed up now.

1 Like

So the new feature purposely makes studio crash? Oh I forgot to mention I did that too.

Your studio might be crashing because of high memory usage, which was announced with the new type solver as a known issue.

Hmm.. I will still leave this bug report up since it’s just a baseplate with 1 tiny script and NPC.

1 Like

The orange line itself is not a bug in this case, but the crash definitely is.

The orange lines are there to indicate mistakes in your code, like using “deprecated” APIs (such as Humanoid:LoadAnimation). Hovering your cursor over them should tell you the issue. You can also use the Script Analysis window.

They probably appeared recently because of the following update:

This update enables a set of script warnings by default, called “nonstrict.” Before this update, the Script Editor would use “nocheck” unless you specifically told it not to, which disabled all warnings.

It most certainly should not be crashing. If you’re able to DM us a place file, we’d be happy to check it out.