While writing a script in studio, I typed local function round() -- lets do this, and pressed enter, expecting a single end to show up, how it’s supposed to. In contrast, this happened:
From there, I distilled the issue to the fact that I used the keyword ‘do’ in the comment. I moved to a new script and tried all the keywords I could think of. Surely enough, this happens:
Studio autocomplete is completely ignoring that these keywords are being commented out, and still inserting ends regardless. You can type any number of ‘trigger words’ in any order in a comment after a real trigger word (you will have to start with an uncommented do, if, function, etc for this to occur.
More screenshots:
-
This bug happens every time
-
This is happening in production
-
I only comment very rarely, so I can’t tie this to a release.