Hotspot module crashes on too many hotspots

Would be good to know how many hotspots it takes before the bot becomes unstable. We could then set the cap a couple below.

I will ask Rudy in a (forum) PM.

Rudy replied:

I remember it used to be the case. I say "used to be" because in order to test it, I just loaded 20 different spots across two private arenas to test. On the first attempt, it failed to warp on the fourth hotspot until I used the !watch command (not even sure that does anything). In the second arena, the same set of 20 worked fine. Perhaps the crashing had something to do with arena settings, or perhaps even another module running alongside it.

^{oh that was me}

!watch makes the bot change which hotspot it looks at — otherwise it's sitting at a particular location and may or may not randomly be able to pick up player position data in order to figure out if a player is in a given spot. (The magic of client-side bots!)

Setting this to worksforme since we can't reproduce the problem.