Had this worong on a private server (Ebonhold) with a trail. Once I purchased a license it no longer works and gives me this on two differant PCs. They had correct settings before.

All of these keybinds are defualt and the display mode is windowed

Just ignore this...

25 minutes ago, Sakonung said:

Just ignore this...

Ignore my post or the error?

It closes the game after these errors come up.

Error.

It's seems like a bug, Idk. When I got this, I'm just pressing "Ok" and everything is okay

Oh gotcha, I tried to but it closes my game automatically. Ill do some trouble shooting later. Game version still shows the same

have the same problem

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

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

12 hours ago, Sakonung said:

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

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

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

yeha if somone find a workaround pless share

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.

@Droidz What do you think about the issue ?

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

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

Then, Just waiting, when @Droidz answer here

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.

1 hour ago, Droidz said:

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.

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

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

4 hours ago, notoeffect said:

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

yeha me 2