Hiya all.

I got a couple of "deep" questions regarding how ent_remove works.
They pertain to how ent_remove works when it is executed, and
how it interacts with the engine task-scheduler.
They're pretty core-level question, so thats why I posted here...


Question#1 ::
When an ent_remove is executed, when does the engine wade through all the
scheduled tasks in order to dump all the ones that have a ME pointer
that matches the entity just removed?
A> Does it IMMEDIATELY process the whole scheduler list?
B> Or does it do the whole list at the next wait/return?
C> Or does it do something different?


Question#2 ::
When ent_remove is checking if a scheduled task needs terminating because
its ME has been removed, is the ME that is being checked in this task..
A> ... the ME that it had when the task was FIRST STARTED?
B> ... or is it checking the value that ME has NOW?


Im asking question#1 just or curiosity. I like to know how things work.
Im asking question#2 because Im having some difficulty with some of my
code involving 'proc_status2' and 'proc_kill'.
But I am doing a bit of 'me'-shuffling, so what Im trying to do is just
not feasable if question#2 is answered by A...


Thanks guys...

The scheduler list is processed immediately. It only checks the current "me" pointer - the engine won't remember which value that pointer had when the task was started.

Do not rely on this crude mechanism to fix pointer errors. The normal and proper method is to have code in your script that terminates all its actions and clears all its references when an entity is removed.

Cool. Thanks dude.

This system is fine for THIS task, as it is only a debugging tool.
This 'action' only has ont reference, and it is an unchanging STATIC one.

The code is actually behaving fine now.
The 'difficuly' I was having was based on my coding elsewhere not behaving
as expected, but now fixed...


Again, thanks for the clarification.