You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a bot is being rushed or the closing distance to enemy will place the bots guns out of alignment to the enemy, the bot should favor the target acquisition over the distance to target or any flight path and turn it's heading accordingly. This will prevent any enemy from gaining an advantage by attacking on a blind side. The bot will never sacrifice weapon accuracy to flight paths or behaviors. The bots aim must always be guaranteed and all flight skills must revolve around that ability. I noticed in our early tests that I can select a path that will place me behind the bot where I can do damage before he re-acquires his target.
The text was updated successfully, but these errors were encountered:
[14:29] <+BBT_> if he has a shot and the turn to face is greater than "x", boost away and turn
[14:29] @imago if the target has a shot and i dont, boost away and turn
[14:29] <+BBT_> if enemy has a shot and turn to face is >.4 second, boost away
[14:30] <+BBT_> otherwise, they'll boost off and take damage greater than .4 seconds
[14:30] @imago and these arbitrary numbers can be mucked with skill levels
When a bot is being rushed or the closing distance to enemy will place the bots guns out of alignment to the enemy, the bot should favor the target acquisition over the distance to target or any flight path and turn it's heading accordingly. This will prevent any enemy from gaining an advantage by attacking on a blind side. The bot will never sacrifice weapon accuracy to flight paths or behaviors. The bots aim must always be guaranteed and all flight skills must revolve around that ability. I noticed in our early tests that I can select a path that will place me behind the bot where I can do damage before he re-acquires his target.
The text was updated successfully, but these errors were encountered: