Marshalek

Is Wrobot Vanilla abandoned by devs?

Same here, pathing is totally broken in vanilla AV. Any suggestions @Droidz?

@Droidz

Having same issue, very frustrating to say the least.

Thanks, that plugin is exactly what I was looking for and more. I wasn't aware this existed, probably because there are different plugin repos for each expansion... Droidz should just combine all plugins into a single repository for ease of finding.

Having this issue, it's quite obvious it's a bot when running party mode.
Obviously the bot checks party leader position every X seconds and moves there. The problem is, if the party leader isn't moving, bot invariably stops right on top of the party leader - it's such a perfect stack it's difficult to emulate manually, hence the obvious, instant BOT RED FLAG when anyone sees it.

@Matenia @Droidz can you write a plugin to prevent bot from landing right on top of party leader?

This is awesome. Thanks @Matenia

To me it was an addon that hid the blizzard cast bar. Once I re-enabled blizz cast bar, bot started working.

My concern is automated, software-based detection - can this be in place? Using WRobot 2.0.1 (34770) for wow 2.4.3 (~8606)

Having this exact same issue... any known workarounds?

Thanks all, it was probably the script I was using then, I noticed it got stuck on "go to town" unable to send mail due to no money.

1 minute ago, Mike-Mail said:

i wish to do some testing on this problem, can you give me the realmlist ip?

 

GAME.FELMYST.COM

Tried to bot on Felmyst and got banned rather quickly.
Could they be running some form of client-side detection via Warden?

So my bot dies, then walks back to the corpse. Two different problems:

1. The bot will resurrect on top of the corpse, regardless of whether there is an enemy nearby.
Please research/review Honorbuddy and copy their behavior - the bot TRIANGULATES between corpse and closest enemies, to find THE BEST LOCATION TO RESS AT. I mean this is so basic I can't even believe I'm here writing this.

2. The bot will re-engage in griding/fightting BEFORE IT RESTS. PLEASE ENSURE BOT HAS FULL LIFE AND MANA BEFORE RE-ENGAGING, another "DUH" bug.
 

With the two bugs above, bot will engage into chain-deaths until I stop the bot and move it somewhere safe. These bugs prevent AFK botting, especially for weaker characters at lower levels.

16 hours ago, welpenhund said:

Nope, I've tried that already. In fact I reinstalled wrobot cleanly and still see the issue.

Hi,

My bot is getting stuck for hours on what appears to be path finding issues (using gatherer).
This happens randomly and I cannot resolve it by adding blackspots.
This appears to have started 2 updates ago when there was a change in path-finding and encryption/compression for meshes i think? Not sure.

If I stop/start the bot, the issue goes away and the bot starts moving again.

Excerpt from the attached logs that show what the bot is doing when it gets stuck for hours:

[N] 01:29:38 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor)
[N] 01:29:38 - [Path-Finding] Path Count: 2 (1.916143y)
[N] 01:29:38 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor)
[N] 01:29:38 - [Path-Finding] Path Count: 2 (1.916143y)
[N] 01:29:38 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor)
[N] 01:29:38 - [Path-Finding] Path Count: 2 (1.916143y)
[N] 01:29:39 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor)
[N] 01:29:39 - [Path-Finding] Path Count: 2 (1.916143y)
[N] 01:29:39 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor)
[N] 01:29:39 - [Path-Finding] Path Count: 2 (1.916143y)
[N] 01:29:39 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor)
[N] 01:29:39 - [Path-Finding] Path Count: 2 (1.916143y)
[N] 01:29:39 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor)
[N] 01:29:39 - [Path-Finding] Path Count: 2 (1.916143y)
[N] 01:29:39 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor)
[N] 01:29:39 - [Path-Finding] Path Count: 2 (1.916143y)
[N] 01:29:39 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor)
[N] 01:29:39 - [Path-Finding] Path Count: 2 (1.916143y)
[N] 01:29:40 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor)
[N] 01:29:40 - [Path-Finding] Path Count: 2 (1.916143y)
[N] 01:29:40 - [Path-Finding] FindPath from -8692.03 ; -4497.512 ; 15.96123 ; "None" to -8691.563 ; -4497.671 ; 14.10993 ; "None" (Kalimdor)
[N] 01:29:40 - [Path-Finding] Path Count: 2 (1.916143y)

15_Jul_2017_20H54.log.html