Hey, for some reason the gb 1759 thread is closed and I have an issue that I need to post in it =P My druid was in Uldum (using 1759) and when bags were full, it hearthed (mailing was set)... which happened to be SW at the time. It only happens on the computer that required the gb.exe workaround (i literally copy and pasted the folder from original computer to this computer and hit start) log attached (debug.html) But the weird thing is... Another druid on the same computer running 1759 just went to silithus to mail =P (debug2.html attached)
Well I was using 1753? or 1751? when that was the case, then Hawker was dead-set on using Silithus mailbox on the new versions It's just kind of weird that 1 will fly over to silithus and one will hearth and think it's in booty bay Code: [11:12:35 AM:219]:Last error message seen: Inventory is full. [11:12:35 AM:242]:Last Red Error Message: Inventory is full. [11:12:35 AM:266]:Inventory is full. [11:12:35 AM:287]:Harvest attempt complete. [11:12:35 AM:345]:Bags full. [11:12:35 AM:363]: Harvest Report: [11:12:35 AM:418]: Whiptail: 23 [11:12:35 AM:438]: Elementium Vein: 34 [11:12:35 AM:457]: Cinderbloom: 32 [11:12:35 AM:476]: 89 nodes gathered in 2 hours 11 minutes 59 seconds. [11:12:35 AM:510]:Do mailbox run. [11:12:35 AM:545]:Starting mail and repair run. Hearthstone first. [11:12:35 AM:565]:MAKE SURE YOUR HEARTHSTONE IS SET TO EVERLOOK, GADGETZAN OR BOOTY BAY[COLOR="red"]. (<-- ignore that)[/COLOR] [11:12:35 AM:882]:Dismount to hearthstone. [11:12:36 AM:826]:Use Hearthstone. [11:12:47 AM:468]:Hearthstone is used. [11:13:00 AM:565]:Can't see player health - is there a valid wow connection. [11:13:02 AM:739]:Pause 10 seconds and then start Booty Bay repair run[COLOR="red"] <-------- ??[/COLOR] but i've gone ahead and posted in the official gb thread. You can close those
the first druid needs repair and the other not! so the objective for the first one is the repair and for the second one to use mail it seems that there is a trick there
