Common Event never stops? (Rpg Maker 2k3 Problem), Title says it all Options

[astigz23]

help me guys. I'm trying to make an item that when used, it will trigger an event. But the problem is, every time I test the common event, it never stops. How can I end this event?

This is the common event:
-Message:\n[1] began carving the stone.
-Wait: 0.5 Sec
-Play Sound: sword1
-Play Sound: sword1
-Play Sound: sword1
-Play Sound: sword1
-Play Sound: jingle2
-Message: You just made a \c[1]Mystery Sword.
-Change Items: Mystery Sword 1 Add
-End Event Processing



Take note: THis is in RM2k3


Please, I'm begging all of you to help me.

Thank you in Avance

[Kazesui]

All Auto-start and parallel process events loop forever. To end them, you will want to turn off the switch which activates the common event instead of using end event process, which only terminates the current loop, and therefore doesn't do anything at all when put at the end of the event script.

Another unrelated thing you might want to consider would be to put waits between your sound effects to make it sound more pleasant.

[Redd]

Yeah, not sure about rm2k3, but in RMXP you have to use the Erase Event command and NOT the End Event Processing, because Erase Event kills it completely. Common events, however, just like Kazesui said, need to have the switch turned off to stop working.

[Kazesui]

Yeah, not sure about rm2k3, but in RMXP you have to use the Erase Event command and NOT the End Event Processing, because Erase Event kills it completely. Common events, however, just like Kazesui said, need to have the switch turned off to stop working.

Erase event kills the event until you reload the map if you use it in a map event, true... but this doesn't apply to common events (seemingly not even in RMXP). In a common event, erase event does... pretty much nothing at all.
Erase event is normally a command you'd only use in map events on maps which you'll never return to, or which should happen once whenever visiting the map.

[Redd]

Yeah I know that, I'm just saying you never really want to use End Event Processing in anything, you usually want to use Erase Event.

Common events, however, just like Kazesui said, need to have the switch turned off to stop working.

[Kazesui]

Ah kay, I interpreted it as you'd be referring to the common event as well up there, my bad. Probably related to different mind sets between rmxp users and rm2k3, since end event processing is a very useful command, especially since erase event doesn't do anything in a common event at all, so I didn't quite get your intention of advising against using it.

While you'd want to use some script in rmxp, you'd ideally make the menu (custom ones) in common events in rm2k3, with a new common event for further sub menus, which loop endlessly for key input, where it'd be more practical to use "end event processing" for whatever cancel the submenu scenario you'd have. This is often the case when your calling an event from another instance and you want the event you called to stop at a certain point. Personally, I use end event processing far more than I use erase event.

So yeah, in rm2k3 it's a question of what you want as erase event and end event does 2 different things, whilst in rmxp I guess you'd normally use a script whenever you're doing stuff where it'd be beneficial to use end event processing I'd guess.

[astigz23]

All Auto-start and parallel process events loop forever. To end them, you will want to turn off the switch which activates the common event instead of using end event process, which only terminates the current loop, and therefore doesn't do anything at all when put at the end of the event script.

Another unrelated thing you might want to consider would be to put waits between your sound effects to make it sound more pleasant.

I tried it, but doesn't work, or I just commit a mistake
BTW< Where will I put the turn switch off command, cause I tried it putting in the end of the common event, and doesn't work.

[Kazesui]

Did you remember to remove "end event processing" first? If not then you need to remove it, because it ends the event before it reaches the command which tells it to turn off the switch then. It's correct that you should turn off the switch at the end of the common event, so just make sure that "end event processing" is removed, and that the switch you're turning off is the same one which is triggering the common event.

[astigz23]

Did you remember to remove "end event processing" first? If not then you need to remove it, because it ends the event before it reaches the command which tells it to turn off the switch then. It's correct that you should turn off the switch at the end of the common event, so just make sure that "end event processing" is removed, and that the switch you're turning off is the same one which is triggering the common event.

Oh, my bad. I'm really sorry, çuz i forgot to edit my last post, because I've just realized that the switch i turned off is gotmysterystone, it should be mysterystone, so im really sorry.

BTW, it worked now.

[Redd]

Locking this topic, as you have found your solution.