All Activity

Anyone run into issues where the bot cannot figure out water while on a flying mount? Mine will just flying into the water and not dismount to get the node and will eventually fly off, but if I manually dismount while the bot is active and dip under the water, it will figure it out and know that its in water and get itself out. Is there a fix around this that I'm just not noticing? I'm new to botting so this is all out of my realm of expertise lol. I'm using the Sholozar 450 mining file.

yeha me 2

Would it be complicated to adapt the bot to Ebonhold? Because modified clients on the private server side have become a classic.

that was just bad timing on my part then, anyway I can get a refund since this wont be usable for me?

https://wrobot.eu/forums/topic/16294-path-server/#comment-71172

Hello, Could you please share the full log file of the session where you encountered the issue? You can find instructions on how to post your log file here: https://wrobot.eu/forums/topic/1779-how-to-post-your-log-file-with-your-topic/

Hello, Ebonhold doesn't run an original 3.3.5a client. Their Wow.exe is patched to load their own DLL inside the game (they use it for integrity checks and custom Lua functions). WRobot is made for the standard 3.3.5a client. Since everything worked before their server update, they most likely changed something in their client mod that blocks the bot. It has nothing to do with trial vs license, the timing is a coincidence. You can check that WRobot itself is fine by testing on another 3.3.5a server with a clean client. But on Ebonhold I can't do much against a modified client, sorry.

Then, Just waiting, when @Droidz answer here

I just tested the different launchers. Same problem, same error. The game closes when the bot launches.

Hi there - is there any bot that works for WOW ascension Conquest Of Azeroth? Thanks in advance,

Suddenly worked for 3-5minutes, now its back to being retarded again.

Hello, today after firing up the bot its seems he cant find any paths, he just finds the next wall and tried to walk through that. Is there any path server problems or anything i can do? Have tried using VPN and restarting my pc.

I'm not sure, that problem is there... I think, it looks like, Ebonhold's client is in conflict with Wrobot, not detect. Try another version of Wrobot. A

@Droidz What do you think about the issue ?

Tried both of the above, swapping VPN - Start computer. bot stills just runs into the wall and do nothing. Everything worked perfect last night.

Bypassing it is surely going to be complicated, detection is probably done server-side. Aside from modifying the software's hash to make it undetectable, the API that the bot uses to interact with the character must be tracked, and I think it's going to be complicated to get around that. We'd still need to know how they detect the software on the server side.

Is this still an error, last night my 3.3.5 bot was working fine. now it doesnt path at all, have tried different options, Quester / Gatherer but its the same. it just runs straight to a wall and gets stuck. Had some issues last night where it strugguled to find path server.

yeha if somone find a workaround pless share

It looks like a server update that directly targets the bot.

Sadly still the same issue even after that. Also tested it on 2 differant PCs

Hello, I just sent you a message with the card code.

9 Jul 2026 07H33.log.html9 Jul 2026 07H33 - RGncP.log.html 1. I have wow in window mode idk why its not 2. Before the server have a update all work fine any help

Guys, anyway, you can easy to fix this. 1. Launch WoW in Window mode 2. Reset the key binding to default After that, connect your Wrobot

have the same problem