Pudge
WRobot user
-
Joined
-
Last visited
Everything posted by Pudge
-
Hi, for the first time in a year of botting, I am faced with such a problem. "If complite condition" is triggered, but the quest "follow path" does not end. The task of the quest is to fly along the path of the airship, the quest must be completed when the bot is above the ship, but as you see something happens, the bot starts the next steps, but the bot continues to do the quest "follow path" that just completed... Argent Stand Quests.xml
-
Interact.ClearTarget(); Works fine in latest version, thanks ❤️
-
-
@Droidz There is a faction field in the xml file, but it's missing in the editor, fix please. I dont know its bug or suggestion but if it’s not difficult for you, please add. ps: many many thanks for so quick adding the kill and loot path type :)
-
Hey. To quickly find errors in the profiles I use this code in the plugin to display the current profile name in the logs: wManager.Wow.Helpers.Quest.QuesterCurrentContext.ProfileName == "test.xml" I searched hard, but didn't find a similar code for the grinder..... something like Grinder.GrinderCurrentContext.ProfileName == "test.xml".... Does anyone know a similar method? The next code gives an error if product is not quester: Quester.Bot.QuesterSetting.CurrentSetting.ProfileName == "test.xml" Same code gives an error if product != grinder: Grinder.Bot.GrinderSetting.CurrentSetting.ProfileName == "test.xml"
-
@Droidz We need it, update pls
-
Thank you in advance! I look forward to it.
-
-
Seems it works! Many thanks ❤️
-
Okay, will try it reight now
-
And I will correct, this is not relogger bug, this is wrobot bug. And judging by the comments (more precisely by their absence), I only have this bug/error. PLEASE! Help me to understand why i get this error.... When i launch wrobot.exe by default way ( wrobot.exe shortcut ( with dx ) or from relogger ) - i have 100% wow crash when killing wrobot process. This is wow crash each time when wrobot process is forcedly terminated by relogger or task manager or this code System.Diagnostics.Process.GetCurrentProcess().Kill(); When i launch wrobot.exe no dx hook ( and from relogger with -nodx arg ) - i have no crashes.... what this mean?... That might be the solution.... But when the bot starts with -nodx arg from the relogger, the graphics in WoW doesn't work and the bot doesn't work.... I also tried to delete d3dx libraries and installed SlimDX.... no effect, same error. Windows 7, windows 10 with all updates..... same error.
-
@Droidz Not planning to implement this? What do you think?
-
-
-
-
-
Logs are empty.... because this is not wrobot crash, this is wow crash each time when wrobot process is forcedly terminated by relogger or task manager or this code System.Diagnostics.Process.GetCurrentProcess().Kill(); Here is what I noticed now: whan i launch wrobot.exe by default way (with dx) - i have 100% wow crash when killing wrobot process, when i launch wrobot.exe no dx hook - i have no crashes.... what this mean?...?
-
-
-
-
-
I was wrong, the error is not in the relogger.... wow crashes when wrobot.exe detaches from wow.exe, i think the bug in attaching-detaching...
-
-
-
I tried from many servers..... latest client i used was from https://www.warmane.com/download
