Quantcast
Channel: OwnedCore - World of Warcraft Exploits, Hacks, Bots and Guides.
Viewing all articles
Browse latest Browse all 280060

Issues Botting on 3.3.5 Server

$
0
0
I was wondering if anyone else was experiencing the same issue. This is from my experience using LazyBot on the Lordaeron server (not sure if its a good idea to mention the name).

So I'm using lazybot and I got a few characters to level 70, however 60-70 was such a headache. The problem I was having (I want to say this only started happening when I got to the Outlands) was some kind of mob targeting/detecting issue. The bot, for no apparent reason, will just simply skip some mobs that should clearly be targeted (within distance, same faction ID, etc.). After not targeting the mob, it will run by, pull aggro, then keep following the way points until the next detected target (and ignore the skipped mob until it leaches). And it’s odd because sometimes it will be just one mob that it skips, then it will successfully target the ones following; although other times, after it skips one mob, it will repeatedly skip mobs and just follow the waypoints without attacking anything and eventually die. This issue also varies by location and by mobs – some areas it’s fairly seamless and other areas practically make it impossible.

Now, it wouldn't be that much of a problem if it weren't for those mobs being added to the blacklist – if they weren't, the bot would detect the mob from aggro, however since it is blacklisted, it will never target it. And I never see why those mobs are being blacklisted in the first place, I only notice blacklists when I start to see several messages of "Removed GUID from blacklist...." in the log. So disabling the blacklist feature would somewhat remedy this issue, but I don’t think that option is available. I tried the “<BlacklistOn>False</BlacklistOn>” tag, but that didn't do anything.

Viewing all articles
Browse latest Browse all 280060

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>