quick help suggestion

#1 the full code just in case.

if(!isObject(bigBlueBehavior))
{
	%template = new behaviorTemplate(bigBlueBehavior);
	
	%template.friendlyName = "bigBlueBehavior";
	%template.description = "bigBlueBehavior";
	%template.behaviorType = "bigBlueBehavior";
	
	%template.addBehaviorField(node1, "", object, "", t2dSceneObject);
	%template.addBehaviorField(node2, "", object, "", t2dSceneObject);
			
	%template.addBehaviorField(velocity, "", float, "10");
	%template.addBehaviorField(pauseTime, "", float, "10");

}

function bigBlueBehavior::onBehaviorAdd(%this)
{		
	%this.node1Pos = %this.node1.getPosition();
	%this.node2Pos = %this.node2.getPosition();
	%this.owner.enableUpdateCallback();	
}

function bigBlueBehavior::onUpdate(%this)
{
	%this.bigBluePos = %this.owner.getPosition();
	echo("bigBlueBehavior::onUpdate");
	echo("  %this.bigBluePos " @ %this.bigBluePos);
	echo("  %this.node1Pos " @ %this.node1Pos);
	echo("  %this.node2Pos " @ %this.node2Pos);

	if(t2dVectorCompare(%this.mouserPos, %this.node1Pos))
	{
		%this.schedule(%this.pauseTime, chooseFromNode1);
	}
		
	if(t2dVectorCompare(%this.mouserPos, %this.node2Pos))
	{
		%this.schedule(%this.pauseTime, chooseFromNode2);
	}
		
}

#2 When you say "no return in the echo" I assume you mean the echo result does not show up in the console...

If your not getting the echo, the logic is not getting there. Your onUpdate callback is not getting fired. I don't know why onUpdate gets fired for some objects but not others or why it works for awhile and then stops. That's a mystery for which I'm looking for the answer as well.

#3 ok, thanks Kevin (side note. James is my middle name). what you say makes sense.


I have bumped into something interesting this morning too. And it may relate to some to other issues I was having. But.... I had a behavior, it would set an object to layer 0, then on schedule to 31, then on schedule back to 0 and so on. I changed the behavior to do this to 3 objects instead of one. After I had completed the adding in of the new behavior I simply moved the original object out of the way and, did not delete it. But it was no longer named as a behavior field. Just an object in space i presumed. Anyhow, my new behavior would not work until i deleted this "old object". Upon deleting it, just before I threw my computer out the window, this triggered the behavior to work.


Why is it that an object, which was formerly tied to a behavior, would it's presence disturb the functionality of the "new behavior" it is no longer a part of? Id this logical? it does not sound like it. But again... ghosts in the machine?

#4 This will happen if your old object has a hard coded name. You copy it into a new object and forget to change the name or delete the name on the old object. In that situation, the system is sending callbacks to the old object while the new one sits there neglected.

#5 so in theory, if that name, of that object is deleted. it is, in my case rendered null and erasing the name is just as good as deleting it. Correct?

#6 Exactly. I've made this mistake many times. I copy an object and then pull my hair out trying to figure out why my game suddenly goes haywire. The solution is to delete the old object or rename it.

#7 yes ok. I thought i was good at that.