All Activity

I’m running into a specific issue with WRobot on Turtle WoW. The bot runs perfectly on other Vanilla private servers, but on Turtle WoW, the game instantly crashes the moment the bot attempts to interact with or accept a quest. What I’ve tested: Everything works fine on other 1.12 servers. The crash only happens on Turtle WoW. I’ve tried clearing the WDB folder and disabling all addons, but the result is the same. Is there a specific setting or a custom "Turtle-friendly" questing profile I should be using to avoid these crashes?

Le bot fonctionne t-il avec Burning Crusade sortit le mois dernier je pense que s'est la version 2.5.5

I can confirm it is working now!

Fixed. You need to manually run the Updater to update all content once.

Hello, the problem should be resolved.

got the same issue, it runs fine the first time, then when i lauch WoW, everything crash and cann't run Wrobot anymore until the next reboot

22 2月 2026 12H41.log.htmlThere is no useful information in the log. I open the bot, it shows "Connecting to server..." and then crashes immediately. Everything worked fine before the update.

Diagnostic_20260222_123656.txt

There was an update prompt today. After updating, the software crashes when it shows "Connecting to the server". It worked fine before the update. edit： After testing, switching to another version via the Updater and updating over it works fine. However, when switching back to the WOLK version and updating again, it crashes. Please investigate the cause.

Hello, Yes, it's a typo that made it into production a long time ago. Unfortunately, fixing it now would break all existing FightClass profiles (XML serialization relies on the exact property name), so it has to stay as is. Sorry for the lost time debugging, I understand the frustration. I'll add a note about it in the documentation.

Hello, This problem should be resolved.

no apologies, the matter has been solved I now see it's an 1.12 instead of a 1.12.1, so unsupported by wrobot. thx for the help

Hello, try downloading the game client from another website. Wrobot only works with unmodified game clients.

thats not really work dude

假死等待几秒后再站起来

进不去群

8 years later...no more buying this program

Hey devs, I've been working on some custom FightClass profiles and ran into something that's been driving me crazy for the past few hours. Not sure if this is intentional or an actual bug. The problem: The API uses "ContionType" instead of "ConditionType" - notice the missing 'i'. Same thing with the enum "FightClassContionsType". I was writing XML files and naturally typed this (DOESN'T WORK): <FightClassCondition> <ConditionType>HealthPercent</ConditionType> <Param xsi:type="FightClassConditionNumber"> <Type>Smaller</Type> <Value>50</Value> </Param> </FightClassCondition> Spent forever debugging why my conditions weren't working. Finally checked the actual API docs and saw it's spelled ContionType. Changed to this and it works: <FightClassCondition> <ContionType>HealthPercent</ContionType> <Param xsi:type="FightClassConditionNumber"> <Type>Smaller</Type> <Value>50</Value> </Param> </FightClassCondition> My question is: Is this a typo that made it into production, or was there a reason for spelling it this way? It's in both the CHM file and the HTML docs, so it's definitely in the compiled DLL. Here's what the API shows: public class FightClassCondition { public FightClassContionsType ContionType { get; set; } public FightClassConditionBase Param { get; set; } } If it's a bug: Any chance of fixing this in a future version? I know it would break existing profiles, but maybe you could support both spellings during a transition period? If it's intentional: Could you add a note somewhere in the docs? Would've saved me a lot of time. Just want to make sure I'm not missing something obvious here. Thanks!

Was looking forward to utilize the remote function, but despite running WoW in windows (not maximized, not fullscreen, not minimized), and the Remote setting is on, I have nothing on this page https://wrobot.eu/remote/. What is truly odd is that I have actually seen output for the remote page and got quite a chock that it was working all the sudden. It turns out that the remote is actually working, when the bot is in flight (taxi)! As soon as the bot gets to the ground and continues the profile I get no output on the page! https://snipboard.io/mDuV1I.jpg I have analysed my network traffic and can see traffic for these addresses and ports Image PID Local Address Local Port Remote Address Remote Port Packet Loss (%) Latency (ms) WRobot.exe 13824 192.168.2.3 59973 137.74.42.160 80 0 25 WRobot.exe 13824 192.168.2.3 58115 172.67.154.210 443 0 11 WRobot.exe 13824 192.168.2.3 59929 104.21.6.87 443 - - 11 Feb 2026 19H54.log.html

Hello, you can find the list of supported versions here: https://wrobot.eu/supported-wow-versions/ . The version you just mentioned appears to be a Classic version that is not supported by Wrobot.

CTM is CLICK TO MOVE push Interface Mouse Disable CLICK TO MOVE for all in the FUTURE

Hi, Wrobot dont work on version 2.5.5 for TBCC version. There is a solution or a work in progress to solve this issue ? Have a nice day !