Anyone remember the last time...

[deusx]

... they left Honorbuddy PvP overnight and woke up to find it still running?

I mean what the hell happened with PvP section of the bot it used to be perfect (remember running it for 20+ hours in cata)? I mean I'd understand it if the PvP bot was under development or something, if new features were being added but the PvP is the same as it was year ago (and i might add regardless of community input on bugs and wanted changes) just now it's not even Language working!

I'm a lifetime user and I use every single aspect of the bot (gathering/pvp/archy/ib/grind/quest) and from my exp with it EVERYTHING except archeologybuddy should be wearing a tag [Beta] or [Work in progress] or [Still Language not working]

Yes you can call this whine or hate thread, but i just wanted to say what's on my heart, while trying to be as objective as possible. This is really how I feel about HB right now

p.s just noticed my "joined date" under my avatar. Today's exactly 1 year since i bought buddy product. So there, you can call this thread "Summary of 1 year of HB usage"

 

[Tweath]

I'm a lifetime user and I use every single aspect of the bot (gathering/pvp/archy/ib/grind/quest) and from my exp with it EVERYTHING except archeologybuddy should be wearing a tag [Beta] or [Work in progress] or [Still Language not working]"

I like that part, so true! :')

 

[npittas]

Well I got a 3hour ban from pvping my warlock but that was a player report and that is even more concerning than a tripwire Language-up. If, in AV someone can distinguish you as a bot, between 150 other people then there's something definitely wrong with either the nav or the logic.

 

[deusx]

Logic can be fixed by using the right CC, but there is no cure when it crashes every 45 minutes

 

[phrozenjib]

Ive got no probs, I usually leave my pvp on for about 8 hours and havent crashed or d/ced. Except once but that was my comps fault coz it memory dumped.. But I used the new BG thing in HB in AB lol so I suppose if blizz checks they will see that I love running AB >.<

 

[AlexZ]

having this problem with about every function of HB or gatherer in that manner,
i turn it on at night, go to sleep, when i wake up, it turns out it only went on for 20 minutes after i left, and been sitting on the anti-afk thing ever since,

while if i run it while im watching it, it runs all day without any problems,
probably just my bad luck though..

 

[Tony]

@deusx

can we have a full log with your crashes?

 

[B3AST]

Use the relogger, works amazingly, i still wake up to my char pvping and with a great amount of honor

 

[npittas]

@deux
The skiWarlock CC is gr8, but it's the PVP logic and the pathing/hotpot logic that makes it look like a bot.
Again, in any BG, you have to be, either, following a pack of players and assist in every way your class can, or play solo by Hide-Kill-Run technics so you won't be defined as a bot (in this case you will be defined as a selfish prick but I can live with it )

So in the first situation the bot could scan the area for pack of players,their vectors, and their class and create a path (that can be change on the fly if neede) to follow them and assist accordingly.
In the second situation you should roam near the main paths the enemy is using (they can be hard or soft coded), find the enemy player attack and get away.
in case of more than X (x>=user defined number of) enemies, you don't dismount and you just keep roam.

And all of this without crashing, and without Nav problems.

If this means heavier but more accurate map tiles of the BGs, and/or more memory and CPU usage, so be it.

 

[greaver77]

Have never had this problem before but now HB crashes all the time just locks up this is on 4g system 1 hour after running hb any ideas ?

[6:54:37 AM:77] System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.IO.MemoryStream.set_Capacity(Int32 value)
at System.IO.MemoryStream.EnsureCapacity(Int32 value)
at System.IO.MemoryStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at System.Windows.Forms.RichTextBox.EditStreamProc(IntPtr dwCookie, IntPtr buf, Int32 cb, Int32& transferred)
at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
at System.Windows.Forms.Control.DefWndProc(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.TextBoxBase.WndProc(Message& m)
at System.Windows.Forms.RichTextBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)