What's new
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

TeamViewer causing HB to loop "We are stuck"

Status
Not open for further replies.

avatarscape

New Member
Joined
Aug 17, 2012
Messages
33
Reaction score
0
Hey,
I don't know why this happens, or if it only happens for me, but having TeamViewer running in the background is causing HonorBuddy to constantly loop getting stuck even when it's not. I noticed this when I changed the way I access my botting dedi from RDP to teamviewer, as teamviewer can still handle wow at 160+ FPS, but then HB started malfunctioning with getting stuck. After exiting teamviewer fully and running RDP instead, it started working again without a problem.
I suspect teamviewer either injects a hook into WoW, causing HonorBuddy to be receiving incorrect information, or perhaps related to the display ( I know that teamviewer has its own display device, though I haven't installed it)
 
So what's the problem here? Simply close Teamviewer and keep botting.
 
So, what is a good program to monitor remotely? Because my TV just did the same thing.. I was in Zangermarsh and my druid was flying back and forth in thin air, and HB was spamming "We're Stuck!" every second or so.. Obviously my character was not stuck, though. He was flying, and there weren't any trees in the way or anything...

Had to shut TV down, and now I'm monitorless until I can get home from work and find a replacement program. Which means I don't even know for a fact if shutting down TV actually fixed my problem. But I have an irking suspicion that it did.
 
I'm not sure what is causing the issue, but I have definitely noticed the bot getting many "we are stuck" messages, even while flying.
 
@Botanist, are you using TeamViewer?

If not, then that may mean that TV isn't causing this specific issue.
 
So, what is a good program to monitor remotely? Because my TV just did the same thing.. I was in Zangermarsh and my druid was flying back and forth in thin air, and HB was spamming "We're Stuck!" every second or so.. Obviously my character was not stuck, though. He was flying, and there weren't any trees in the way or anything...

Had to shut TV down, and now I'm monitorless until I can get home from work and find a replacement program. Which means I don't even know for a fact if shutting down TV actually fixed my problem. But I have an irking suspicion that it did.


I use log me in as a way to remotely monitor computers. Quick google search should find it for you.
 
So, what is a good program to monitor remotely? Because my TV just did the same thing.. I was in Zangermarsh and my druid was flying back and forth in thin air, and HB was spamming "We're Stuck!" every second or so.. Obviously my character was not stuck, though. He was flying, and there weren't any trees in the way or anything...

Had to shut TV down, and now I'm monitorless until I can get home from work and find a replacement program. Which means I don't even know for a fact if shutting down TV actually fixed my problem. But I have an irking suspicion that it did.

Find a RDP client. That seems to have no issues with it, but it causes me to drop to like 6fps whilst the window is visible (when it's not visible, ie another window covering, it gets 160+)
It is definitely teamviewer causing the trouble.
 
its not TV causing the "we are stuck "message its a bug with Hb introduced since the last wow update it happens using PB an GB as well an causes the bot to blacklist all nodes an then it just flys routes refusing to gather

happens using questing profiles as well refuses to pickup or hand in quests

i wouldnt run HB till its fixed to risky
 
its not TV causing the "we are stuck "message its a bug with Hb introduced since the last wow update it happens using PB an GB as well an causes the bot to blacklist all nodes an then it just flys routes refusing to gather

happens using questing profiles as well refuses to pickup or hand in quests

i wouldnt run HB till its fixed to risky

I was using the questing bot.
 
Status
Not open for further replies.
Back
Top