Skip to content
View in the app

A better way to browse. Learn more.

WRobot

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Droidz

Administrators
  • Joined

  • Last visited

Everything posted by Droidz

  1. Hi, Actions on path points do work, and your format is right (the c#: prefix). The likely issue is that the bot never really lands on that exact point, so the action doesn't fire. It validates a point from a few yards away and moves to the next one, and your points are very close together, so it passes that one without triggering its action. Try spacing that point out from the others first. If that doesn't fix it, share your profile and a log file so I can check.
  2. Hi, It's not the default behavior, the bot only flies to your corpse when it can't make a ground path to it. You can try this plugin (not tested), put it in your Plugins folder and stay on a flying mount when you die: Fly to corpse when dead.cs using System; using System.ComponentModel; using System.Threading; using robotManager.Helpful; using wManager.Events; using wManager.Wow.Helpers; // Force the bot to fly back to its corpse (corpse run on a flying mount). public class Main : wManager.Plugin.IPlugin { private const float MinDistanceToFly = 30f; private const int AscendRetestMs = 5 * 60 * 1000; private const int MinActionIntervalMs = 500; private static bool _testedThisDeath; private static bool _isFlyingMount; private static int _lastAscendTick; private static int _lastActionTick; [ThreadStatic] private static bool _reentry; public void Initialize() { OthersEvents.OnPathFinderFindPath += OnPathFinderFindPath; Logging.Write("[FlyToCorpse] Loaded."); } public void Dispose() { OthersEvents.OnPathFinderFindPath -= OnPathFinderFindPath; Logging.Write("[FlyToCorpse] Unloaded."); } public void Settings() { } private static void OnPathFinderFindPath(Vector3 from, Vector3 to, string continentNameMpq, CancelEventArgs cancelable) { if (_reentry) return; _reentry = true; try { var me = wManager.Wow.ObjectManager.ObjectManager.Me; if (me == null || !me.IsValid) return; if (!me.IsDeadMe) { _testedThisDeath = false; _isFlyingMount = false; return; } if (!me.IsMounted) return; Vector3 corpse = me.PositionCorpse; if (corpse == null || corpse.DistanceTo(Vector3.Zero) <= 0) return; if (to == null || to.DistanceTo(corpse) > 12) return; if (corpse.DistanceTo(me.Position) < MinDistanceToFly) return; int now = Environment.TickCount; if (_lastActionTick != 0 && (uint)(now - _lastActionTick) < MinActionIntervalMs) return; if (!me.IsFlying) { bool mayTest = !_testedThisDeath || (uint)(now - _lastAscendTick) >= AscendRetestMs; if (!mayTest) return; _testedThisDeath = true; _lastAscendTick = now; Move.JumpOrAscend(Move.MoveAction.DownKey); Thread.Sleep(Others.Random(300, 700)); Move.JumpOrAscend(Move.MoveAction.UpKey); Thread.Sleep(Others.Random(300, 700)); _isFlyingMount = me.IsFlying; } if (!me.IsFlying) return; to.Type = "Flying"; _lastActionTick = now; cancelable.Cancel = true; } catch (Exception e) { Logging.WriteError("[FlyToCorpse] " + e); } finally { _reentry = false; } } }
  3. https://wrobot.eu/bugtracker/wow-lk-gatherer-storm-peaks-r1625/
  4. Droidz commented on Endotox's bug report in Bug Tracker
    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/
  5. Droidz commented on Gile's bug report in Bug Tracker
    Hi, Share the full log file from that druid (the .html in the Logs folder, from a session where it got stuck). Also tell me if it gets stuck at the same spot. You can also turn on Radar3D in the Map tab, it draws the bot's path and what it's targeting directly in-game, so you can see where it's trying to go when it gets stuck.
  6. Hi, That error means the bot can't reach our server. It is almost always a VPN or proxy, your antivirus, or your firewall blocking the connection. Disable your VPN, add WRobot to your antivirus and firewall exceptions, and make sure you are on the latest version, then try again.
  7. 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/
  8. Hi, The crash comes from Epoch's custom client and its anti-cheat conflicting with WRobot's.
  9. Hi, Which quester profile are you using? A special objective like absorbing those elementals usually needs a specific step in the profile, the bot doesn't know that custom interaction on its own, so if the profile just kills or interacts normally the absorb won't count.
  10. Hi, When the bot sits to regen, it restores both health and mana in the same sit, and it keeps drinking until the upper drink value (the second %, 95% by default). Your mana is almost always under 95%, so it drinks nearly every time it heals. Lower that upper drink value, for example set drink to 5% -> 30%. Then when it sits to heal it only drinks if mana is really low, and stops fast. If you don't want it to drink at all, leave the drink field empty (or turn off resting for mana) and keep only your heal spell for health.
  11. Hi, The 4.3.4 client workaround doesn't work anymore because Whitemane switched to the newer 4.4.x Cataclysm Classic client. WRobot for Cataclysm only supports the 4.3.4 client, so there is no version that works on Whitemane now.
  12. Hi, There is no workaround. WRobot for Cataclysm only supports the 4.3.4 client, and Whitemane moved to the newer 4.4.x Cataclysm Classic client which isn't supported. There is no version for it at the moment.
  13. Hi, WRobot for Cataclysm only works with the 4.3.4 client. The newer 4.4.x Cataclysm Classic client (Whitemane and others) isn't supported, and there is no version for it at the moment.
  14. Droidz commented on nax's bug report in Bug Tracker
    Hello, Thanks for the suggestion. There's already a protection in place that handles this case, and so far it's been holding up well against Lua-side detection. If you need this on a specific server, a plugin or a fight class override is the cleaner route.
  15. Hello, I can't read the logs on the video.
  16. The last possibility is that it's caused by a wrobot plugin or the fight class. Otherwise, I'm sorry, I don't know what could cause this type of problem.
  17. Try to use the shortcut "WRobot (DX hook)" to launch the bot.
  18. Hello, Your client path shows "TBC-2.4.3.8606-enGB-Repack" - repacks are often slightly modified clients (even if they look "clean"), and that's very likely what's causing the crash. Try to find an original unmodified 2.4.3 client (not a repack) and test with that. That should fix it. No, Vulkan won't help here, the issue is at the memory/hook level, not graphics related.
  19. 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/
  20. Droidz commented on 4mkjp4uh's bug report in Bug Tracker
    Changed Status to Fixed Changed Version to All
  21. Droidz commented on 4mkjp4uh's bug report in Bug Tracker
    Hello, The hosting provider is experiencing a technical issue with their infrastructure. The service will return as soon as the machine hosting the pathfinder server is back online.
  22. Hello, Could you share the versions/builds (of the game) that your servers are using?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.