G Gionis New Member Joined Jun 18, 2010 Messages 4 Reaction score 0 Apr 7, 2011 #1 I got a crushing problem causing my GB to crush overnight Attachments Debug.html Debug.html 172.4 KB · Views: 50
H haxed New Member Joined Jan 15, 2010 Messages 545 Reaction score 1 Apr 7, 2011 #2 Is your mount on bar 3 button 1?
Tony "The Bee" Joined Jan 15, 2010 Messages 128,830 Reaction score 571 Apr 7, 2011 #3 looks like a random wow dc wow is crashed or dced?
G Gionis New Member Joined Jun 18, 2010 Messages 4 Reaction score 0 Apr 7, 2011 #4 Mount is in B3b1 and all macros are fine by textbook. The wow client didnt crash it can't be random every time though...
Mount is in B3b1 and all macros are fine by textbook. The wow client didnt crash it can't be random every time though...
H haxed New Member Joined Jan 15, 2010 Messages 545 Reaction score 1 Apr 7, 2011 #5 What Tony means i think is that at this point [5:37:06 AM:821]:Mount to Patrol Your bot tried to mount and couldn't but if it was a hb issue im sure that you would have an error afterwards but it just keeps trying to mount.
What Tony means i think is that at this point [5:37:06 AM:821]:Mount to Patrol Your bot tried to mount and couldn't but if it was a hb issue im sure that you would have an error afterwards but it just keeps trying to mount.
Tony "The Bee" Joined Jan 15, 2010 Messages 128,830 Reaction score 571 Apr 7, 2011 #6 haxed said: What Tony means i think is that at this point [5:37:06 AM:821]:Mount to Patrol Your bot tried to mount and couldn't but if it was a hb issue im sure that you would have an error afterwards but it just keeps trying to mount. Click to expand... tbh after a second look on the log the problem starts at [6:16:06 AM:80] it looks like the char got stucked Last edited: Apr 7, 2011
haxed said: What Tony means i think is that at this point [5:37:06 AM:821]:Mount to Patrol Your bot tried to mount and couldn't but if it was a hb issue im sure that you would have an error afterwards but it just keeps trying to mount. Click to expand... tbh after a second look on the log the problem starts at [6:16:06 AM:80] it looks like the char got stucked
