Where to call script after unpackUpdate ?

#1 Look into Con::executef()

#2 Thanks anthony -

i know how to call script,
i'm just leery of calling possibly lengthy script functions inside of unpackUpdate().

#3 Im doing it now for hitpoint updates. It shouldnt effect anything calling it there. But if your really concerned you could set a bool "onDataChanged" and in the processTick, call your script if that var is set.

#4 processTick!
thanks very much peter.

what about doing something like this:

[b]change this:[/b]
function player::somethingChanged(%this)
{
   doLengthScriptOperation();
}

[b]to this:[/b]
function player::somethingChanged(%this)
{
   %this.schedule(0, "somethingChangedReally");
}

function player::somethingChangedReally(%this)
{
   doLengthScriptOperation();
}

#5 Update:

a major reason to watch out for calling to script directly from unpackUpdate,
and why Peter's processTick suggestion is a better method:

when the client is first ghosted an object,
it seems to me and my colleagues that the object is not assigned a simID until the unpackUpdate is finished.

so,
if you're doing something like this inside unpackUpdate:

Con::executef(this, 1, "somethingChanged");

you may find that on the script side, %this is zero, even tho this in C++ was valid.


So what i'm currently planning to do is a slight generalization of Peter's "onDataChanged" idea:
add a new member to netObject: mDirtyMaskBitsClient,
and set bits in it individually in unpackUpdate(), and then have various clearers in processTick.