Having another rezz related bug. After death bot will return to path and start farming without waiting for rezz sickness to wear off. Still getting an error stating "http sync is lagging! Error - sync2: WebClient does not support concurrent I/O operations." I did a fresh install of Gatherbuddy. Could this be on my end? Could this be cause by a virus? I just noticed I have a virus that is cloning explorer and running random .exes. Any help is appreciated.
Can I get an official response from someone/ Hawker maybe? I have two lifetime accounts that I bought when the euro was very high and I feel like something resembling tech support is not too much to ask. Thanks.
I have seen this, but it hasn't harmed anything as mine picks back up in a few seconds or less it also looks like the stop button was pressed (it doesn't check for buffs, so if you click start / stop, it's not going to wait for rez sick) Code: [10:13:34 AM:552]:Patrol: Ascent complete.<br> [10:13:35 AM:576]:Gatherbuddy 1.7.5.6 is stopped.<br> [10:13:35 AM:735]: Harvest Report:<br> [10:13:35 AM:741]: Deaths: 4<br> [10:13:35 AM:746]: Cinderbloom: 55<br> [10:13:35 AM:751]: Azshara's Veil: 2<br> [10:13:35 AM:756]: Stormvine: 6<br> [10:13:35 AM:761]: 63 nodes gathered in 1 hours 56 minutes 47 seconds.<br> [10:13:36 AM:630]:Stopping patrol.<br> [10:14:16 AM:539]:Error - sync2: WebClient does not support concurrent I/O operations.<br> [10:16:16 AM:567]:http sync is lagging!<br> [10:26:16 AM:660]:Error - sync2: WebClient does not support concurrent I/O operations.<br> [10:28:16 AM:673]:http sync is lagging!<br> now for your rez sickness problem... Your settings: Code: [8:17:45 AM:96]:Character will harvest herbs.<br> [8:17:45 AM:97]:Combat range is 5 yards.<br> [8:17:45 AM:98]:Character will repair when gear is at 50% durability.<br> [8:17:45 AM:100]:Will exit in 8 hours.<br> and your death looks fine (11mins, 15 secs) Code: [COLOR="red"][SIZE="5"][B][8:37:49 AM:501]:Found a spirithealer!<br>[/B][/SIZE][/COLOR] [8:37:58 AM:856]:Waiting for resurrection sickness to expire.<br> [8:37:59 AM:91]:Get Aura, Aspect, Shadowform or other long buff.<br> [8:37:59 AM:117]:Waiting for resurrection sickness to expire.<br> [8:38:01 AM:107]:Get 5 minute buff.<br> [8:38:01 AM:124]:Waiting for resurrection sickness to expire.<br> [8:38:02 AM:817]:Get 15 minute buff.<br> [8:38:02 AM:901]:Waiting for resurrection sickness to expire.<br> [8:38:04 AM:838]:Mount to avoid combat with Rez Sickness.<br> [8:38:04 AM:873]:Bar 3 button 1 to mount.<br> [8:38:04 AM:909]:Waiting for resurrection sickness to expire.<br> [8:38:08 AM:656]:MountAndTakeOff: Ascent needed.<br> [8:38:18 AM:653]:MountAndTakeOff: Ascent complete.<br> [8:38:18 AM:656]:Mount sequence complete.<br> [8:38:18 AM:750]:Waiting for resurrection sickness to expire.<br> [8:38:34 AM:186]:Resurrection complete.<br> [8:38:34 AM:299]:Waiting for resurrection sickness to expire.<br> [8:42:48 AM:989]:Error - sync2: WebClient does not support concurrent I/O operations.<br> [8:42:49 AM:12]:Waiting for resurrection sickness to expire.<br> [8:44:49 AM:2]:http sync is lagging!<br> [8:44:49 AM:27]:Waiting for resurrection sickness to expire.<br> [8:47:49 AM:39]:Error - sync: Thread is running or terminated; it cannot restart.<br> [8:47:49 AM:46]:Waiting for resurrection sickness to expire.<br> [COLOR="red"][B][SIZE="5"][8:49:04 AM:842]:Ready to patrol<br>[/SIZE][/B][/COLOR] [8:49:04 AM:843]:Cinderbloom<br>
That's the thing, I check wait for rezz sickness and it does not wait....I stopped the bot manually because it went back to harvesting. This is a real problem and I do have quite a lot of experience botting, I just don't post often. I guess all I can do is wait for the next release. Thank you for your advice Kickazz I am beginning to think you are the only one who reads these, I am appreciative.
it will always buff and fly up, did it buff, fly up and start patrolling I don't really watch mine much, but was it going to repair maybe (with rez sick)? But yeah, if it's acting up, delete the settings as Tony suggests.
Hey Tony, Kickazz I tried the solutions you suggested and it is doing the same thing, I moved another bot on a fresh install and it does the same thing, it is only doing it in Hyjal though, I am getting quite a few odd death related bugs. I am probably going to try a fresh install of windows and tough it out until the next update. As always appreciate the advice!
I have to agree there seems to be an issue but since it is with the core HB they probably will not address it here only in a bug report. I was using the grinding bot and at level 39. As you can see from the timestamps it goes to repair and then pulls a mob on the way and has not had time for the rezz sickness to wear off. 2:46:43 PM:185] Activity: Releasing from corpse [2:46:43 PM:277] Activity: Releasing corpse [2:46:43 PM:298] Activity: Releasing from corpse [2:46:45 PM:426] interact: 0x29DF9BFC [2:46:45 PM:429] interact done: 0x29DF9BFC [2:46:48 PM:545] Spell_C::CastSpell(783, 0, 0x0, 0) [2:46:51 PM:935] Spell_C::CastSpell(1126, 0, 0x5000000049FBF88, 0) [2:46:52 PM:696] Changed POI to: Type: Repair, Name: Razbo Rustgear [2:46:55 PM:35] Spell_C::CastSpell(783, 0, 0x0, 0) [2:47:22 PM:809] Changed POI to: Type: Loot, Name: Searing Hatchling [2:47:27 PM:128] Changed POI to: Type: Kill, Name: Firemane Scout [2:47:27 PM:249] Activity: Pulling
This is the GB forum. What you have described is a HB combat class error. Post your full log next time it happens please.
Strange, mine is doing that too! It does everything as though the wait for rez sickness is not ticked.
