Several General questions

Botting a ranged toon: is there a mechanism in this bot to get the bot to kit mobs rather than just face tanking everything?

Q2: having an issue where my ranged toon just stands still for seemingly no reason with the bot dialogue page spamming: [LatencyTracker] LowestLatency: 34
[LatencyTracker] HighestLatency: 34

Is there a reason or setting I need to pay attention too to prevent this? Also, thought it happens in standard grind mode, it's far worse then trying to use the questplugin. If anyone knows what will help get the questplugin functional that would be awesome, I've given up on it @ this point.

Q3: I've looked but not seen ideal builds for classes for botting? Any places to go or recommendations here? I seem to die a lot, which is not going to work out so well once I progress to the point where I lose XP for dying.

Q4: Is there a way to exceed 3 concurrent maps with any plugin or with the built in GrindZonechanger?

Q5: Is there a list of "best botting maps" anywhere?

Q6: What classes/build have you guys had the best botting experience with?

Q7: having an issue where my character is actively shooting at a mob point blank and missing and just keeps missing.
Thanks in advance for any assistance.

 

1) Nope, or atleast, not yet
2) Nothing harmful, it's logging your latency debugging purposes
3) Would say 4k+ life/es / capped resists / 20k dps & som defensive logic ) is optimal
4) Not without coding extra zones
5) Dried Lake has been a very good map, else just default mapping in labo/hideout
6) Tanky Icecrash / Bladefall ES-based build

 

tyvm! I'll get to reading on those builds.

 

To add a few things:

Kiting needs to be implemented in the CR (combat routine) if you want such a feature. All combat related tasks are not in the bot itself, but rather a user customizable routine that is loaded at startup. The default routine provided with the bot, OldRoutine (formerly BasicRoutine) does not implement kiting because there's no generic solution that has worked good enough without causing issues for other people. As a result, it face tanks, and users need to make/use a custom CR that is more tailored to their build.

If your character is just standing still, it typically is one of two things:
1. You're using a ranged skill that is bound to your mouse button, so the cursor overlaps the GUI and events are eaten by the client. To fix this, rebind your MMB and RMB to the keyboard, and don't use LMB as a primary ranged skill slot.
2. One of your plugins is having an issue where logic is pretty much stuck. There's an option you can enable from the Global tab via Options, "Debug Last Task" to output the current task execution list so you can see which tasks are being executed and figure out why it's just stopping. If you want to make a Support thread, you can, but we need a full log to be posted, and not just a snippet of tasks.

Latency tracking was added to help debug random issues where unexplained things were happening in the past, that were most likely caused by latency, but no way to really show it. It's now logged just to help people understand various delays or why things might not be working as expected if there's huge latency spikes.

As for your last issue, that's part of the game. You can physically miss mobs due to attack angles and whatnot, so consider using skills that affect AoE or have melee backup skills if mobs get super close. For example, Death's Harp fires two arrows, but the way the game is coded, you're firing arrows two arrows at once which split apart at the attack position, so basically you need a routine that attacks "far behind" a mob to ensure the projectiles try to hit things close by before the diverge. For an easy test to understand this, use Split arrow really close by your character and look at the spread, then use it far away.

 

One more question, I'd like to run two bots in concert. Is there any group option where they will work together?

 

I don't think there are any public group party plugins to do that. It's certainly possible with the API we provide, but the bot implementation we provide is for solo bots.