This is an issue ive had a few times as a POWER USER… This is what happened this time (Today): I opened my Team Create place, clicked on an already opened script, scrolled to the line i was thinking of editing, double clicked the ‘and’ operator into just the letter ‘o’ before i decided against switching to the ‘or’ operator.
.
I typed back in my ‘and’ operator, *hit ⌘ + S which should save my script changes * and published. I go into the game and it gives me this error as if the ‘o’ is still in the script.
I publish 5 more times and keep trying to get the script changes to apply but it doesnt work. The script runs fine in Play Solo in studio.
This bug has actually inconvenienced me greatly in the past, when it published a completely broken version of the core script of my game which had like 15k ccu completely bricking the game for everyone for like an hour. I looked back at the code like how is it throwing these errors ??? The quick solution i came up with then was to copy all the text in the script, delete the text, save it like that, paste the text back in and save that, and hope it didnt try to publish the blank version. This happened probably some time after last spring? Sorry i cant really remember…
I dont know how to reproduce this, it just happens to me sometimes. All i know is it only happens in team creates. Usually im the only person in the team create so i assume its only happened while im alone. I dont script with anyone else so thats not really a factor
Enabling LiveScripting mode for your places may resolve the issue. (Live Scripting is set to become the default mode of TeamCreate in the near future). I assume this bug is with the old scripting behavior since you mentioned it also occuring sometime last year.
I’ve also experienced this bug, and I was using team create. Publishing the game would not actually change scripts (unsure if it was the whole game, or just scripts). The same syntax error would show, even though I’ve fixed it already! This was maybe a month ago.
I’m going to close this issue on our end. For any devs still encountering this, if it still occurs after switching to LiveScripting, please submit a new bug.
Live scripting is still in beta, though? Not only just that, but many development flows can’t use Live Scripting as it conflicts with certain setups (for example, some external code editor tools don’t update scripts in real-time and don’t account for edits made by other users) so locking users out of scripts you are editing / forcing them into drafts which can be dealt with later, is most ideal in some cases.
Hi @Abcreator, the locking mode will be removed soon, and LiveScripting will become the new default mode in TeamCreate places. Therefore, if you don’t want other collaborators to affect the script you are editing, we suggest switching to Draft mode. However, I’m wondering what the problem is when you update script content with an external code editor tool in LiveScripting mode?
