Actuator execution order

Do actuators get executed from top to bottom, and guaranteed to execute in that order? Will they finish executing 100% before going onto the next actuator?

Reason being… I have a ball… doing things… after it does things… it will kill itself.
But the things HAVE to be done first, before it kills itself.

You can flag controllers to make them execute first, but other than that the order is, for all intents and purposes, random.
However, it all takes place in one frame, so it shouldn’t matter what order.

this is sound theory, but in fact as the object is ended the next frame, it is still able execute the logic other than end object

in this case is better a rapid death

in python write

obj.endObject()

ZAC , end of problem

not read even the line below[EDIT:] instead read again!!! not want death!!:mad:

can also spawn other object from the other world!!!


import bge

def player(cn):
    ow=cn.owner
    
    
    if not "init" in ow:
        ow["init"]=1
        
    print("SONOVIVO")
    ow.endObject()#<<<<<<<<<<<<<<<<<
    print("SONOMORTO")
    k=bge.logic.getCurrentScene().addObject("vv",ow)
    print(k)

continue to spawn also in this way! o.o


import bge

def player(cn):
    ow=cn.owner
        
    print("SONOVIVO")
    ow.endObject()
    pass

    print("SONOMORTO")
    k=bge.logic.getCurrentScene().addObject("vv",ow)

The EndObject Actuator (and it’s Python equivalent endObject() ) just flag the object to be ended.

As agoose writes the flagged object will be removed after the actuators executed.