Marshalek

@Matenia I've disabled HMP combat loot, and now I see this in the logs after 3 failed loot attempts:

[D] 12:02:32 - [Looting] Cannot loot the target (Mob XYZ), ignore it.

So it appears Wrobot already has logic to prevent this issue, but HMP was breaking it like you said.

It's egregiously dumb that Wrobot tries to loot the same mob 200 times, no matter how you look at it. If you can resolve this with a plugin,  it should be incorporated into the vanilla bot per default... I just can't fathom that I'm the first person ever to bring this issue to light?

Yes I've read your message., but I'm not very handy with coding for Wrobot, nor do I have a dev environment setup atm... is this plugin something you can create for me? You said a few lines of code should suffice...

I mean, isn't it obvious that if I try to loot the same mob 30 times and it doesn't work, it probably won't work the 31st time?

It's not a quest item like the chicken quest egg, these are mobs in a particular zone that does not have a chicken quest.
The server is just buggy, it clearly does not work as it should... but because of something so silly, wrobot breaks.

So I'm using Wrobot on this buggy AF server and some mobs show they have loot, but when the bot clicks to loot, there's nothing in the loot window.
The result is, Wrobot stays there clicking non-stop for 5 minutes on the same corpse, until the corpse finally despawns and Wrobot moves on to the next mob (rinse and repeat).

Obviously I will be banned with this behavior, people can tell I'm a bot from miles away.

Is there a way to prevent Wrobot from trying to loot same corpse more than 2 times?

1. Try to loot: fail
2. Try to loot: fail
3. Blacklist corpse and move on
4. Remove from blacklist after 5 minutes

@Droidz @Matenia @Andoido @Ordush for feedback

Droidz already went as far as rebranding Wrobot with "Bot for private servers" so I don't think he's even planning on trying...

Well, if they forced HB and WR out of business (with regards to retail) I think they have the upper hand on this game...

Private botting community? I thought Blizzard had found a way to catch all bots regardless of user count?

@Bambo more like, the best minds in botting (not me) don't know something, so it can't exist.

@Droidz @Matenia @Andoido @Bambo for insight if wanted...

Is it correct to assume that whatever methods Blizzard currently uses to detect bots in retail (BFA) will also be used for Classic WoW?
Do we have any hopes of a working bot that's undetectable for Classic WoW?

Sometimes the bot butt-pulls unintended mobs while already fighting one... can't the bot be made to back off a little when there is a group of mobs nearby, to avoid such butt pulls?
Kind of like what a human would do..

I'm using 77 search and 1 max units, but was still running into packs of Murlocs. So is this the profile's fault?
 

If they caught HB and WR, how do you geniuses figure they wouldn't get an amateur dev making a "private" bot? Stop dreaming, botting on retail is over.

@Svartben this is just how Wrobot works, there is nothing that can be done to stop the idiotic pulls / chain dying, it's just how this bot works.

This stupidity is still a reality 01/15/2019, chain dying on lvl 22 Murlocs in Wetlands, using TBC Wrobot.
I am not using Bambo's profile nor fight class.

@Droidz do you actually use/test Wrobot or is all your development/bugfixing purely theoretical?
There's NO WAY you wouldn't know how broken Wrobot is if you tried to use it for SIMPLE THINGS such as grinding.

All I can see you telling people is to show logs/reinstall Wrobot - but then they do, you say "wait till next release" and nothing ever gets fixed, bot is always the same broken mess as always... wtf dude can't you fix this stuff?

I spend more time MANAGING THE BOTS CONSTANT SHORTCOMINGS than it would take for me to level manually? WTF?

Quest and Objective IDs are good, let me do some more testing on this and I'll post back. Thanks @Droidz

Greetings fellow wroboters,

I'm trying to include a "RunCode" step in my quest profile, to run some code only IF the objectives on a certain quest haven't been met yet.
This is what I have for the RunCode param so far:

if (!Quest.IsObjectiveComplete(2, 9999))
  {
   wManager.Wow.Bot.Tasks.GoToTask.ToPosition(new Vector3(9999.262f, -9999.587f, 999.8167f));
  }

The above doesn't work - the code is run every time I get on that step, regardless of whether objective is complete or not.
How can I make this work?

This is what it looks like in the profile:

<QuestsSorted Action="RunCode" NameClass="if (!Quest.IsObjectiveComplete(2, 9999));  { wManager.Wow.Bot.Tasks.GoToTask.ToPosition(new Vector3(9999.262f, -9999.587f, 999.8167f)); }" />

Thanks @Droidz

should just report him ingame since you know what his bot will be doing

get those accounts banned

This is so very essentially stupid that I can't believe I'm having to ask.
Is there a way to prevent wrobot from instantly releasing from body when I die? This is one of the most obvious ways to spot a bot...
Just create a random delay between 1-5 seconds for release? It would look so much more human-like.

Is there a super-genius, einstein-level marvel of innovation, visionary developer who could have had a revelation about this very elusive, difficult to even notice, troubling aspect of Wrobot and made a simple plugin to create said delay when releasing from body after death?

LOL good luck with that using Wrobot

SOOOOOOOOOOO fing frustrated with Wrobot

Pathing is completely broken, right from the start the bot goes crazy, drops down a cliff and tries to climb the mountain back up as if it were Spiderman.

This is so amazingly frustrating, i don't know why I keep paying for this every month... running this bot requires almost as much work as playing the game, with 100x the risk of being banned, and nothing, NOTHING I want to use the bot for ever works as intended

Are you guys really from Germany?

Bot is broken (pathing) in vanilla AV and after many reports, there's no sign Droidz will even look at it...

Wrobot is abandoned...