Droidz
Administrators
-
Joined
-
Last visited
-
Hello, this is a fairly common issue among users living in China. Often, using a VPN can resolve this problem.
-
-
I just redeployed an update with signed files, the false positive issue from some antivirus programs should now be fixed.- 120 comments
- 6 reviews
-
Salut, c'est un faux positif. Mon certificat de signature a expiré, donc cette mise à jour n'est pas signée, et certains antivirus signalent les outils non signés qui lisent la mémoire d'un autre programme. Je vais racheter un certificat pour régler ça, mais la validation prend quelques semaines, donc il faudra patienter un peu. En attendant, ajoute le dossier de WRobot aux exclusions de ton antivirus et restaure les fichiers qu'il a mis en quarantaine. ____________________________________________________ Hi, it's a false positive. My code signing certificate expired, so this update isn't signed, and some antivirus software flags unsigned tools that read another program's memory. I'm going to buy a new certificate to fix this, but the validation takes a few weeks, so it'll need a bit of patience. In the meantime, add the WRobot folder to your antivirus exclusions and restore the files it put in quarantine.
- 120 comments
- 6 reviews
-
-
- 1
-
-
-
-
Hello, You can do it with the ACTION column. When you're not recording, double-click the ACTION cell of a point and put: c#: robotManager.Helpful.Keyboard.PressKey(wManager.Wow.Memory.WowMemory.Memory.WindowHandle, "x");Then save the profile. One thing to know, the action of a point runs when the bot reaches the point before it (when it starts walking toward that point). So if you want X pressed when standing at 3496.952, -3864.835, put the action on the line right after this one.
-
-
Hello, WRobot now supports TWW. You need to download the latest Updater: https://wrobot.eu/files/file/2-wrobot-official/
-
Hello, The bot doesn't really crash, it closes itself when it can't reach the WRobot servers during startup. That's why your logs stop right after the version line without any error. Since it happens on several machines, it's probably your antivirus or something on your network blocking the connection from time to time. Can you try: 1. Add the WRobot folder to your antivirus exclusions (Windows Defender and any other antivirus you use), then try again. 2. Check that https://download.wrobot.eu/wrobotwotlk/isOnline.php opens in your browser on the same machine (it should just show "true"). 3. If you use a VPN or proxy, try without it. You can also try changing your DNS to 1.1.1.1 or 8.8.8.8. Do you have the same problem with the other WRobot versions on these machines, or only WotLK?
-
Hello, which server do you play on? Do you have this problem during combat ?
-
-
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, your issue should be resolved.
-
-
-
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.
-
Hello, I just sent you a message with the card code.
