add attack.bt #2962
add attack.bt #2962
Conversation
| // reset the suicide timer | ||
| decorator return( STATUS_FAILURE ) | ||
| { | ||
| action resetMyTimer |
There was a problem hiding this comment.
The suicide timer is stuckTime, not myTimer. "My timer" is not used anywhere in this BT so this seems pointless.
There was a problem hiding this comment.
This is the general purpose timer. It is not set or read in C++. But default.bt uses it to wait for 20 seconds before suiciding to spawn as builder. If you change a bot from attack.bt to default.bt, it might suicide immediately if this timer has not been reset in a while.
We should do this in all behavior intented to be available to regular users.
There was a problem hiding this comment.
Oh so old state is not cleared when switching behaviors? We should fix that.
There was a problem hiding this comment.
I did not think about this problem when I added that timer. All I cared about was a timer independent of the paths taken in the behavior tree (decorator timer is closely tied to these paths and success/fail).
We could reset it on behavior changes. Indeed, we should reset bot targets on behavior change too. But what if someone wants to use that timer in an "inverted" way? Like setting it when some positive condition is met, lets say when alertedToEnemy. And later query that time to find out how long a bot has not sensed an enemy. Automatic reset would break this instead.
There was a problem hiding this comment.
But what if someone wants to use that timer in an "inverted" way? Like setting it when some positive condition is met, lets say when
alertedToEnemy. And later query that time to find out how long a bot has not sensed an enemy. Automatic reset would break this instead.
I guess the appropriate way to reset myTimer is to set it to the time that the behavior tree was set, rather than 0. Then it would behave the most similarly to as if the game had just started.
There was a problem hiding this comment.
I opened #2971 to fix this.
There was a problem hiding this comment.
I guess the appropriate way to reset
myTimeris to set it to the time that the behavior tree was set, rather than 0. Then it would behave the most similarly to as if the game had just started.
That seems to be the most sensible choice.
This is the fifth bot behavior players can use on my server. It makes a bot attack the enemy base.
For reference, I use this on my server:
This is similar to
reckless.bt, but more elaborate. I do not dare to changereckless.bt. It is the simplest interesting example behavior, and was the first behavior I studied while learning the behavior tree language.