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

mount macro button moved by itself?

socket

New Member
Joined
Jun 2, 2010
Messages
96
Reaction score
0
Left GB running came back two hours later to it and WoW nowhere to be found. Weird I thought.. not something I'm used to. Logged back into WoW.. bot sitting out on my farming path. Fired up the bot again... wouldn't mount. So look at my bars to find my mount macro moved down a spot. I didn't move that damn macro button. Nor did anyone else. Has anyone else had this happen or have a reasonable explanation? Could the bot have done this some how?
 
ya know.. odds are you accidently moved it with mouse clicks and didnt' realize it. It happens... i'd suggest enabling the locks for the action bars.
 
I considered this... but, I vnc into my GB box. So I watched it cycle through at least 3 nodes before I closed out my VNC session. I've been doing this for about 4 years now can't say I've ever accidently moved a button. I guess it's possible but very unlikely.
 
its highly likely specially with a remote desktop app... phantom signals can cause your mouse/keyboard to do things on the remote box as you log out all though it would be a short thing (like clicking and draggin) :) specially if your the only one with access to the machine. now if you say others have acces to it.. well there's a possibility.. but HB/GB doesn't mess with the button bars..... so just write it off as a fluke.. and move on :)
 
its highly likely specially with a remote desktop app... phantom signals can cause your mouse/keyboard to do things on the remote box as you log out all though it would be a short thing (like clicking and draggin) :) specially if your the only one with access to the machine. now if you say others have acces to it.. well there's a possibility.. but HB/GB doesn't mess with the button bars..... so just write it off as a fluke.. and move on :)

Since no one is lining up with similar experiences... I guess it must be a fluke or some kind of VNC fail.
 
Back
Top