Goonhub
10-17-2020, 01:15 PM
One thing to keep in mind that bot code is one of the more janky piles of code, and the thing that checks to see if any specific thing is nearby is fairly expensive to run. For a bot to check if it bumped into another bot, there're a few ways we can go about this:
> Have the bot scan the contents of the tile its on every step and check if any of those things are the same type as the bot.
> Make a global list of all the bots' locations, and have the bots check this list if its location matches any of the other ones, as well as knowing which entry on the list is their own and disregarding that.
Then, run a proc that makes the bot fuck around, set a var that says it bumped into a bot, then unset that var in a few seconds so it doesnt keep bumping into the same bot endlessly.
At any rate, it'd probably be obnoxious to code wouldn't result in anything that'd fix the issues here.
I prefer how they used to work, that they were easy to avoid, group or not, but still needed to be avoided. I could change the way the stunner works to force the bot to stop, then run a fairly short actionbar to stun the person.
> Have the bot scan the contents of the tile its on every step and check if any of those things are the same type as the bot.
> Make a global list of all the bots' locations, and have the bots check this list if its location matches any of the other ones, as well as knowing which entry on the list is their own and disregarding that.
Then, run a proc that makes the bot fuck around, set a var that says it bumped into a bot, then unset that var in a few seconds so it doesnt keep bumping into the same bot endlessly.
At any rate, it'd probably be obnoxious to code wouldn't result in anything that'd fix the issues here.
I prefer how they used to work, that they were easy to avoid, group or not, but still needed to be avoided. I could change the way the stunner works to force the bot to stop, then run a fairly short actionbar to stun the person.