action bullet
{
  ....
  myFunction(you)
  ....
}

function myFunction(ent)
{
    while(ent) //  <- no problem, works   
    {
       if(ent._fireflag)  // <- here I get error when compiling: unknown _arg1 parameter!
....

action bullet
{
  ....
  myFunction(you)
  ....
}

function myFunction(ent)
{
    ent = my;
    while(my) 
    {
       if(my._fireflag)
....

action aLocalDummy
{
   //you is pointer to mother ent!!
   while(you)
   {
      //read the skills given by player input
      vecMovement.x = you._movement_x; 
      .....
      .....
      //now move me with the vec "given" by you (mother ent)
      c_move(me, vecMovement...
      .....
   }
}

• when the parent creates the child, save directly after ent_create the parent-child association by storing the parent pointer into the child. E.g you = ent_create(...); you.skill10 = my;
• as replacement for your main loop of the child object, just place a while loop with (1) argument (infinite loop)
• in the end of the loop before the wait(1); just proof at first if the parent skill is != 0. If it is ==0, the child is a newborn without the parent association. You can circumvent this by waiting one frame before the main loop of your child starts. If it is != 0, a pointer has been stored in it.
• fill it into an entity pointer: you = my.skill10; Now proof you against NULL to see wether the parent entity is present or not. If it is == NULL, the association exists, but no target in the memory. So, the parent is lost (or removed). If == NULL, you can branch and use break; to leave the loop. If YOU != NULL, the parent entity is available and you can proceed on this.

Quote:

---

storing the parent pointer into the child. E.g you = ent_create(...); you.skill10 = my;

---

This is possible?? I've just read about storing strings in skills but pointers too?

Cool I'll follow your suggestions, so it will be more or less easy. (I hope )


Thx a lot -> *5 stars*


nipx


edit: for speed reasons:
Is it faster to set (when required) you to the motherEnt

or

always use my._motherEnt (global ent stored in this skill) instead of seting you to it

?