Jump to content
This site uses cookies! Learn More

This site uses cookies!

By continuing to use this site, you agree to allow us to store cookies on your computer. :)

kecsketragya

Members
  • Content Count

    7
  • Joined

  • Last visited

About kecsketragya

  • Rank
    Newbie

Recent Profile Visitors

85 profile views
  1. Droidz was right, get a clean copy of 5.4.8.
  2. If you don't rename WoW-64.exe to something else or don't use -noautolaunch64bit option it'll automatically start the x64 version. Start wow using: WoW.exe -noautolaunch64bit
  3. WRobot has no x64 support. use the 32bit wow client.
  4. You could check the target's class and current form.
  5. I don't really know the code, but FightClassWaitForRegen is run by a wow thread, afaik it is actually run by directx by a hardware break and you sleep this thread -> while (Conditions.InGameAndConnectedAndAliveAndProductStarted && !Common.IsAttackedByNpc), so assuming that the first condition is true, it will sleep the thread updating your code until Common.IsAttackedByNpc becomes true, thisway stopping the originally directx thread from doing it's original job. Guessing from the variable's name it isn't constantly true, rather occasionally. I wouldn't sleep the thread based on that. Edit: the single step exception is actually caused by killing wrobot (the handler for the SEH exception from the hardware bp gets lost) Edit2: Even if that code is run outside of the client, the cause of the problem might be similar.
×
×
  • Create New...