Jump to content

Pudge

WRobot user
  • Posts

    348
  • Joined

  • Last visited

Everything posted by Pudge

  1. Pudge

    3.3.5 Relogger bug

    Seems it works! Many thanks ❤️
  2. Pudge

    3.3.5 Relogger bug

    Okay, will try it reight now
  3. Pudge

    3.3.5 Relogger bug

    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.
  4. @Droidz Not planning to implement this? What do you think?
  5. 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?...?
  6. I just downloaded latest fresh version from the site
  7. This is exe from 2.3.3 (32199) version, since I have no others
  8. 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...
  9. I tried from many servers..... latest client i used was from https://www.warmane.com/download
  10. I used clients from warmane, wowcircle, dalaran-wow.... and getting errors all the time....
  11. @Smokie This happens on any server. I'm testing on Single Player Project, play on Wowcircle.net.
  12. I use wrobot for Wotlk. Hi help me please, I get an error when the Relogger closes the wrobot window for the latest updates. ERROR #132 (0x85100084) Fatal Exception Program: Q:\wowtest\Wow.exe Exception: 0x80000004 (SINGLE_STEP) at 0023:6B56279F the old version is working fine I didn’t see anyone else write about this problem on the forum, but I tested on different computers, and on all the latest version gives an error
  13. @Droidz please please please, do something like this for wotlk, that would be super wonderful..... Default = true - this is for old profiles.
  14. @Matenia Thanks for reply. I already tried to do that. Here is an example of how it works, the same path in the product grinder and kill and loot in the quester. Kill and Loot just stops at every point at low FPS and thinks he's stuck. Even at high FPS, it does not work as well as a grinder product.
  15. Since the current «Kill and loot» having all its flaws is extremely unsuitable for farming mobs in on a fly mount ... @Droidz It would be great if you add a new quest type working as a Grinder product. This will be a «Follow Path» that will attack the mobs like «Kill And Loot», in which the points will not be the hotspots, but will be a points for move like «Follow Path».
  16. Pudge

    Kill and loot

    This is how pathfinder create path in «Kill and loot» type with flying points. It generates for each point very strange «Air-to-Earth-Air» paths that look wildly suspiciously directly asking for a ban. It doesn't use «Long Move» and pauses between each point if the FPS is below 40, it works like these are ground points with type «None».
  17. Pudge

    3.3.5 Relogger bug

    Does anyone have the same problem? I tried on different pc, and versions of windows, the same problem.... I asked my friends who do not use the robot to install the robot and check, also error
×
×
  • Create New...