1.13.4: control of script state broken

If a script is set to 'not running' either through LSL command or through Tools menu command, once the object with such script is taken to inventory and re-rezzed, it's no longer possible to set this script to running again* The Tools command will either report error "Not able to perform recompilation." or report success _but_ silently fail, the LSL command will report error "Couldn't find script script_name".

This is broken also for creator of the item/script in question.

Steps to reproduce:

#1 rezz a cube. Create default script in the cube.
#2 select Tools -> "Set scripts to not running" while the cube is selected
#3 take the cube to inventory
#4 re-rezz the cube, select it, use Tools -> "Set scripts to running". The command will throw error "Not able to perform recompilation. Select object with scripts that are valid".

in some cases step 4 doesn't throw error, but the script is left in not running state anyway.

This behaviour breaks items which disable most of their scripts when unused, in attempt to conserve sim resources. Please fix it if possible, the alternative is script makers will just leave all the scripts running 24/7 with obvious impact on already stressed sims. --;;

*) there's workaround which involves dragging the scripts out of object into the inventory and then dragging them back into the object again which apparently resets script state to running, but it's only possible for items with mod permissions.

Also modding and saving the scripts works, but I spent an hour trying to figure out what was wrong with my dance floor. After spending too long dealing with broken teleporters.

I've had similar problems with a script that was set not to run in an object sitting in-world. Only way to restart it seemed to be to recompile.

Agreed... I had to go in and recompile several scripts before they would work.

In one particular case for example, I had tried "Tools / Set Scripts To Running..." as well as opening the script and ticking the "Running" checkbox. Even with the "Running" checkbox ticked, the script would not perform. After several unsuccessful tries with various combinations of the standard methods, I just added a space and re-saved the script, which is the only thing that worked.