1. Open new place file
2. Create new LocalScript object under StarterPlayerScripts
3. Launch Play Solo
4. Note that clicking the output (“Hello World!”) opens the LocalScript
5. Stop Play Solo
6. Attempt to open the LocalScript again from the output
Expected Behavior
The LocalScript should open when the output message is clicked
Actual Behavior
The LocalScript does not open, showing a “Source not available” error when hovered:
The script and line of code must be manually found using trace information from the message
Issue Area: Studio Issue Type: Other Impact: Low Frequency: Constantly Date Last Experienced: 2022-12-21 00:12:00 (-07:00) A private message is associated with this bug report
I believe this only happens to LocalScripts that are in Parenting folders (such as StarterPlayer, StarterGui, Starter_). It’s not a bug from my knowledge, the LocalScript doesn’t have the same parent as it did before runtime, thus the Output prevents from pointing to a wrong script (which could happen if 2 different scripts have the same Parent and Name, gladly the fix was implemented.).
You’re describing an edge case that could be easily handled by checking if the script’s source matches.
Anyway, you’re already able to open a LocalScript during runtime, make changes, and have them be applied to the original script when you end the session. It clearly manages to keep the reference somewhere.
I just tested it with multiple scripts of the same name and it works fine:
The cause is that when the second click happens, the Play mode script doesn’t exist any more because it was copied.
Cloned script links will still work as well as ModuleScript links.
A workaround is to click on the link during the Play session to bring the original script up (and then double click on the script if you have Temporary Scripts enabled, to make it a permanent tab).
