Droidz
Administrators
-
Joined
-
Last visited
Everything posted by Droidz
-
Hello, Your test with the plugin helped a lot, I could reproduce the crash here and found the cause. It's fixed in the update I just pushed, for all WRobot versions. Can you remove the plugin (DisableGameInput.cs) and try the new version? Tell me if you still get a crash.
-
-
-
Hello, I pushed an update for WotLK, can you try with this version and tell me if it still crashes? If it still crashes, try with this plugin. It turns off the new way keys are sent to the game. Your fight class (AIO) turns the "Move with game input" option back on when it loads, that's why unchecking it did nothing. Create a file DisableGameInput.cs in the Plugins folder with the code below, then enable it in the Plugins tab. using wManager.Plugin; public class Main : IPlugin { public void Initialize() { wManager.Wow.Helpers.GameInput.UseGameInput = false; } public void Dispose() { } public void Settings() { } }If it's better with the plugin, let me know, it will help me find the exact cause. And if the game crashes again, can you send me its crash report by private message? It's the .txt file with the time of the crash in the Errors folder of WoW (World of Warcraft\Errors).
-
Hello, I think it comes from a change in this update, the way keys are sent to the game on 3.3.5 (movement, and spells cast with the action bar keys). Can you try the latest version again with these two options unchecked in the General Settings, and tell me if it still crashes? - "Move with game input" in the "Class / Fights Class" tab - "Cast spells with the action bar keys" in the "Human-like behavior" tab The GetReactionTowards errors are only a side effect of the client going down, you can ignore them.
-
Hello, Can you uncheck "Flying mount: fly around structures (roofs, bridges)" (tab "General Settings" > "Enter advanced settings..." > tab "Path-finding"), save and try again in Storm Peaks? It will tell us if the issue comes from there. Also, can you send me the full log file of a session where it happens (in the "Logs" folder of WRobot), and if possible a short video of the flight? The log file has more details about the flight than what the bot window shows. The error at the end (Main.Dispose) comes from one of your plugins, it is not related to this issue.
-
Hello, It's a bug in the last update, WRobot doesn't start on a new install. It will be fixed in the next version (today or tomorrow). In the meantime, create a file named WRobot.exe.config in the same folder as WRobot.exe with this content, then run WRobot.exe again: <?xml version="1.0" encoding="utf-8"?> <configuration> <startup> <useLegacyV2RuntimeActivationPolicy>true</useLegacyV2RuntimeActivationPolicy> <supportedRuntime version="v4.0" /> </startup> <runtime> <loadFromRemoteSources enabled="true" /> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <probing privatePath="Bin;Products;FightClass" /> <dependentAssembly> <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="13.0.0.0" /> </dependentAssembly> </assemblyBinding> </runtime> <system.net> <settings> <servicePointManager expect100Continue="false" /> </settings> </system.net> </configuration>Make sure Notepad doesn't save it as WRobot.exe.config.txt. If you use the Relogger, add a copy of this file named Relogger.exe.config next to it.
-
-
The action runs right when the bot starts walking to the next point, so the move cancels the cast. You can make it wait inside the action, replace it with: c#: MovementManager.StopMoveTo(); Thread.Sleep(500); robotManager.Helpful.Keyboard.PressKey(wManager.Wow.Memory.WowMemory.Memory.WindowHandle, "x"); Thread.Sleep(5000);The last value is the wait after the key press, in milliseconds (5000 is 5 seconds), adjust it to your cast time. Don't set it much higher than the cast, the bot stays there until the wait is over.
-
-
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.
