chevron_leftchevron_leftchevron_left
    of     2   

RobloxNewb01
#64270592Tuesday, March 13, 2012 6:51 PM GMT

[Not copying anyone else] coroutine.yield(ABC) should do the trick. Else, just destroy it.
nate890
#64270809Tuesday, March 13, 2012 6:56 PM GMT

"Else just destroy it" And yet I'll repeat myself again, you cannot stop code from executing by removing a script.
Everesty
#64270902Tuesday, March 13, 2012 6:58 PM GMT

Nate is correct. Destroy and remove set the parent nil. If a script is in nil, it still runs. I suggest Disabling the script with a different script, if that would work. `*\~-{ Are we there yet T.T? }-~/*`
nate890
#64271512Tuesday, March 13, 2012 7:10 PM GMT

Disabling doesn't even work, either.
crazyman32
#64279730Tuesday, March 13, 2012 9:23 PM GMT

Agh, coroutine.yield will NOT work in this case! And I can't remove the script; it's a plugin. It's stealing the Source from scripts and executing it.
FlyScript
#64327909Wednesday, March 14, 2012 8:51 PM GMT

I know it isn't always, but if you did in this case, it would be easy to shut down.
aboy5643
#64328117Wednesday, March 14, 2012 8:54 PM GMT

What if you did ABC = nil?? Would that yield the thread because you removed the function definiton?? Or is it statically run??
FlyScript
#64328585Wednesday, March 14, 2012 9:01 PM GMT

You could always ask the creator of the actual plugin. It's functions might be locked or something, there are orbs and stuff, when you try to delete them in studio mode they keep reappearing, I'd suggest asking the creator, or opening studio with a code-time browser, where you can see all the scripts that are going and edit them. Roblox is against them, because they can be used to hack, but if you just use it to veiw the plugin and maybe edit it slightly to find out another way to halt it, that would not bhe so bad.
Merlin11188
#64329609Wednesday, March 14, 2012 9:18 PM GMT

There is no actual way to stop a coroutine from running externally. It will be run until coroutine.yield is called on it, which will not happen until the coroutine is finished running (because it's outside of the coroutine itself). So, what you can do is either: Impossible Useless I believe. Let me know if I'm wrong :D
Merlin11188
#64329672Wednesday, March 14, 2012 9:18 PM GMT

"It will be run until coroutine.yield is called on it, which will not happen until the coroutine is finished running (because it's outside of the coroutine itself)" Slight clarification: That will not happen *externally* until the coroutine has yielded itself.
smurf279
#64335727Wednesday, March 14, 2012 10:48 PM GMT

This looks like a nice little challenge. Maybe when I finish my project (Almost done :D)
nate890
#64341945Thursday, March 15, 2012 12:20 AM GMT

It's impossible to suspend a coroutine outside of a coroutine. Attempting it would just be a waste of time.
smurf279
#64344590Thursday, March 15, 2012 12:56 AM GMT

"It's impossible to suspend a coroutine outside of a coroutine. Attempting it would just be a waste of time." Who says I'm thinking of doing it from outside?
crazyman32
#64362379Thursday, March 15, 2012 11:07 AM GMT

Well I was the one trying to do it from the outside. If there's no way, then I'll leave it there. Thanks all for helping me work through this :P
Voidacity
#64363073Thursday, March 15, 2012 12:12 PM GMT

[ Content Deleted ]
Voidacity
#64363149Thursday, March 15, 2012 12:18 PM GMT

[ Content Deleted ]

chevron_leftchevron_leftchevron_left
    of     2