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.

Bot thinks it is stuck after charging

Featured Replies

I tested this with multiple fight classes. After using warrior charge or intercept the bot does an unstuck procedure (strafe and jump) almost every time, which looks extremely bot-like. Is there any way to prevent this? I have tried changin the pathfinder settings around to no avail.

 

08:45:17.993 - [Looting] Loot Thunderhawk Hatchling
08:45:23.671 - [Fight] Player Attack Hecklefang Snarler (lvl 18)
[N] 08:45:23.807 - [Path-Finding] FindPath from -1680.312 ; -2000.552 ; 92.35954 ; "None" to -1657.62 ; -2036.933 ; 93.7635 ; "None" (Kalimdor)
[N] 08:45:24.022 - [Server] [Path-Finding] -1680.312, -2000.552, 92.35954 to -1657.62, -2036.933, 93.7635 (Kalimdor, ResultPartial=False, ResultSuccess=True, Path count=3, SkipIfPartiel=False, IgnoreServerRoadsWater=False, Time=3
[N] 08:45:24.022 - [Path-Finding] Path Count: 3 (43.38184y, 214ms)
[F] 08:45:26.237 - Fightclass successfully casted: Charge()
[F] 08:45:26.237 - Iteration took 199ms
[F] 08:45:26.823 - Iteration took 431ms
[F] 08:45:27.439 - Iteration took 462ms
[N] 08:45:27.762 - [MovementManager] Think we are stuck
[N] 08:45:27.762 - [MovementManager] Trying something funny, hang on
[D] 08:45:27.777 - [MovementManager] Avoid wall: StrafeLeft
[F] 08:45:28.116 - Iteration took 523ms
[F] 08:45:28.871 - Iteration took 601ms
[F] 08:45:29.578 - Iteration took 554ms
[F] 08:45:30.285 - Fightclass successfully casted: Heroic Strike()
[F] 08:45:30.285 - Iteration took 553ms
[F] 08:45:30.714 - Fightclass successfully casted: Rend()
[F] 08:45:30.714 - Iteration took 275ms
[F] 08:45:31.284 - Iteration took 416ms

 

  • 6 months later...
  • 4 months later...

disabling it is not a good idea, therefore the path finding algo is to basic (as well as this stupid unstucker), there should be an option to prevent unstuck from running while battle or going more easy (waiting 1.42 secounds or so when in fight to start unstuck algo)

Create an account or sign in to comment

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.