Good evening honnor buddy community
I am having a problem with honor buddy i am using a varied mixture of bots with the same results.
Basically i start wow log into my character wait till everything loads up then open honnor buddy from its own folder on a separate drive designated D on my system.
It starts loads fine the first time and will run most bots for a period of between 4 minutes - 30 minutes after which time the bot window will close itself off the wow account
will still be logged in however if i attempt to reopen honnor buddy after it has crashed it ask's for my key accepts freezes and then throw's up a windows error and then will not reopen
until i have completely logged out of wow , bnet closed through task manager etc.
During these weeks of random issues i have removed honnor buddy and re-installed 3 time's from various admin links in posts to fix problems including the latest download links
i have re installed microsoft c++
deleted the settings folders contents
used all new bots nothing from previous versions complete re install of the client
i have checked that wow is running correctly and is 32bit mode and windowed mode etc
i have tried launching through the Honnor buddy Launcher in the folder itself manually launching wow in its folder
also re installing wow to a fresh drive
deleted the bossland file
and app data files as per advice on similar post to no affect
Affected Bot base's that i have seen do this....
Questing bot
Lazyraider
Enyo
Garrisonbuttler ice
Farm bot
and the profesions one
it also doesnt seem to matter if i stop the bot and switch it over eg questing to lazy raider if it appears to be stuck in any way " i do this regularly"....
please note i also used both custom routines buddy store one's thanks thuna
and the standard ones prior to posting this issue and have seen it across the hunter as per log a warrior in a different zone a druid and a death knight
also if i try to open multiple instances of the bot at the same time it will not open the second one it will through up a windows error that the application has encountered a critical error just after entering the key
I am having a problem with honor buddy i am using a varied mixture of bots with the same results.
Basically i start wow log into my character wait till everything loads up then open honnor buddy from its own folder on a separate drive designated D on my system.
It starts loads fine the first time and will run most bots for a period of between 4 minutes - 30 minutes after which time the bot window will close itself off the wow account
will still be logged in however if i attempt to reopen honnor buddy after it has crashed it ask's for my key accepts freezes and then throw's up a windows error and then will not reopen
until i have completely logged out of wow , bnet closed through task manager etc.
During these weeks of random issues i have removed honnor buddy and re-installed 3 time's from various admin links in posts to fix problems including the latest download links
i have re installed microsoft c++
deleted the settings folders contents
used all new bots nothing from previous versions complete re install of the client
i have checked that wow is running correctly and is 32bit mode and windowed mode etc
i have tried launching through the Honnor buddy Launcher in the folder itself manually launching wow in its folder
also re installing wow to a fresh drive
deleted the bossland file
and app data files as per advice on similar post to no affect
Affected Bot base's that i have seen do this....
Questing bot
Lazyraider
Enyo
Garrisonbuttler ice
Farm bot
and the profesions one
it also doesnt seem to matter if i stop the bot and switch it over eg questing to lazy raider if it appears to be stuck in any way " i do this regularly"....
please note i also used both custom routines buddy store one's thanks thuna
and the standard ones prior to posting this issue and have seen it across the hunter as per log a warrior in a different zone a druid and a death knightalso if i try to open multiple instances of the bot at the same time it will not open the second one it will through up a windows error that the application has encountered a critical error just after entering the key
