A little something

I don't think so unless you have a looping event, then it isn't necessary. For me it never is necessary.

 

I used to have problems with infinite loops and laggy resources when I didn't use stop (when I just started Skripting) but for safety measure, I use stop for everything. I normally use it in unnecessary places, however, it is just a habit.

 

Depending on the case you use.

If you are inside a repetition or the code is repetitive and some trigger events arrive
Stop trigger is required

Now if the code that is is simple. (Boolean), you simply use a stop, to detect that the section is finished, remember to read from the bottom up

 

heres an example:

Code (Text):

command /test:
    trigger:
        send "&9LOL!"
        stop trigger

 

No its wrong
Example

With stop trigger

Code (Text):

on any move:
    if {PlayerMove.%player%} is true:
        stop trigger

With stop

Code (Text):

command /test:
    trigger:
        send "&9LOL!"
        stop