Breaks in multiplayer

does not work on big maps (like gm_bigcity)

The nextbot seems to ignore "AI Ignoreplayers"

tristenbennett381 님이 먼저 게시:

Breaks in multiplayer

Seems to only chase and target one player in multiplayer as well

it can somehow kill you when you're already dead, it will go over ur corpse and the death message will show up like 20 times

Installer Wizard 님이 먼저 게시:

it can somehow kill you when you're already dead, it will go over ur corpse and the death message will show up like 20 times

Pushed an update that fixes this just now! Let me know if it works on your end if you try it again

I died in an enclosed space and it infinitely killed my corpse somehow even after the update. it spawned more and more ragdolls and gibs in an enclosed area, making it loop until the game crashed

The nextbot doesn't seem to appear at all on any maps, even with no other addons. Am I missing a dependency or something?

it ignores other players and only targets the host

I noticed if you go into an area that the bot can't get to (using noclip to go out of bounds) the games FPS drops to almost zero until I go back into the map or back where the bot can navigate to.

Does not work on flatgrass

Wadaw_ 님이 먼저 게시:

The nextbot doesn't seem to appear at all on any maps, even with no other addons. Am I missing a dependency or something?

it might be that it disappears in a random area and starts stalking you but if you cant delete it or it wont show up anywhere even on a small map it might be a bug.

Kills you when you are god mode

Destructoid 님이 먼저 게시:

Kills you when you are god mode

it just sets your health to 0 is probably it, it isn't doing damage.

Fignewts 님이 먼저 게시:

I noticed if you go into an area that the bot can't get to (using noclip to go out of bounds) the games FPS drops to almost zero until I go back into the map or back where the bot can navigate to.

Gargin, you're gonna want to be careful about where you call PathFollower:Compute. If the goal position is somewhere out of bounds, it'll search the entire navmesh before giving up. My lazy hack in Sanic was to detect when it took too long and stop trying to pathfind for a bit. It's hitch-prone but won't tank framerate. If you were feeling fancy, you could try tweaking the generator function to give up after a while instead. It might even be worth doing a quick nearest-navarea search on the goal position to avoid trying to path to somewhere you can't get to? There are a lot of options here.


Also I'd like to report a bug. If he can't pathfind to you while stalking, he'll stop doing anything and never recover from that. You might want to refactor his AI into a state machine (HIDING, STALKING, CHASING, ...) to make the state transitions a little more obvious.