mrJones2k Member Joined Mar 14, 2010 Messages 86 Reaction score 0 Mar 25, 2010 #1 Just got that error, while botting my 57 hunter with horde 1-60. Using latest HB 1.31 EDIT: As it seems my realm pool went offline. Maybe i got DC and than it tried to check... Dunno EDIT2 here is a better ss: Attachments 25.03.2010 Log..txt 25.03.2010 Log..txt 206 KB · Views: 49 Unbenannt..webp 35.9 KB · Views: 40 Last edited: Mar 25, 2010
Just got that error, while botting my 57 hunter with horde 1-60. Using latest HB 1.31 EDIT: As it seems my realm pool went offline. Maybe i got DC and than it tried to check... Dunno EDIT2 here is a better ss:
ski Well-Known Member Joined Feb 12, 2010 Messages 3,720 Reaction score 48 Mar 25, 2010 #2 You got DC'd. Is this a unique occurrence or does it happen often?
Dalees New Member Joined Feb 17, 2010 Messages 566 Reaction score 2 Mar 25, 2010 #3 think it's just same like at me http://www.buddyforum.de/showthread...adUInt-at-0x13868100-failed&p=32410#post32410
think it's just same like at me http://www.buddyforum.de/showthread...adUInt-at-0x13868100-failed&p=32410#post32410
mrJones2k Member Joined Mar 14, 2010 Messages 86 Reaction score 0 Mar 25, 2010 #4 no, only when the 24h dc by t-com is pending. otherwise thats unique and like i said: my whole realm pool is down.
no, only when the 24h dc by t-com is pending. otherwise thats unique and like i said: my whole realm pool is down.