Tilemap issue and bot just stops randomly

ive started mining 1-525 but im using all the separate profiles because 1-525 dont work
so atm im in uldum at 497 and doing the uldum 475-500 profile, it keep stopping, flying around for 1 min then stops, ive reinstalled honorbuddy like 9203842397times, deledes cache folders, flushed dns, restored to previous versions of honorbuddy, but the bot still stops, what is the problem?!
i dont know how to get a log file from it so thats why i havent uploaded that one..

and for the honorbuddy admins, in case you havent noticed, i pay for this shit.. i expect it to work..
also ALOT of auth login fails every day..
YOu mind fixing the bot or at least tell me what i should do, i mean if the bot has no tilemap for uldum i should be able to download it..? whats the problem..

 

Yeah same for me....a lot of problems lately

I cant run the bot for more than 20-25 min without a problem

 

lucky you, i can run it for almost 1 min at a time, and thats IF it starts..

 

same problem Tilemap issue hanging on downloading mesh..

 

I made a post about this a while ago but still haven't gotten an answer either =/ Seems to be a lot of problems atm with the nav. system or something.

 

http://www.thebuddyforum.com/buddy-...141-official-server-issues-oct-18-2012-a.html

will be fixed monday hopefully.

Alternative try the following; Open WoW and the Bot , Open a Browser (Firefox or whatever) and surf, hit the start button of Honorbuddy and for some people this fixes the problem , youre not allowed to see the wow window, overlay it with the media player, your browser or whatever.. Im farming now for 2 hours without a problem

 

Tried it but, same thing, stucks on moving to next hotspot and just stands still after a few minutes =/

 

omg the browser thing worked..... as soon as I covered the entire wow windows with browser it worked lol. thats some messed up stuff right there.

 

As I said (or in a other thread) this is not working for everyone but for a couple of people , like me and the guy above.

 

I have the same problem, at first i though it was my setup or such that where failing!

It worked fine for a week or soo, then recently a day or two back, everything starts to fail.
I did e clean installation several times, same stuff over and over again!

No data for Azeroth_32_48.etm
No data for Azeroth_32_48.etm
No data for Azeroth_32_48.etm
No data for Azeroth_32_48.etm
No data for Azeroth_32_48.etm
No data for Azeroth_32_48.etm
No data for Azeroth_32_48.etm
No data for Azeroth_32_48.etm
No data for Azeroth_32_48.etm
No data for Azeroth_31_49.etm
No data for Azeroth_32_48.etm

[Profile Message]: Compiling Northshire Abbey Quests
System.InvalidOperationException: DataReader already active on this command
at System.Data.SQLite.SQLiteCommand.InitializeForReader()
at System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.SQLite.SQLiteCommand.ExecuteReader()
at Styx.CommonBot.Database.Connection.
(SQLiteCommand , Object[] )
at Styx.CommonBot.Database.NpcQueries.GetNearestNpc(WoWFactionTemplate myFaction, UInt32 mapId, WoWPoint searchLocation, UnitNPCFlags npcFlags)
at Styx.CommonBot.Profiles.VendorManager.GetClosestVendor(VendorType type)
Moving to Type: QuestPickUp
System.Threading.ThreadAbortException: Thread was being aborted.
at „..GetTile(TileIdentifier )
at Tripper.Navigation.WowNavigator.LoadTile(TileIdentifier wowTile)
at Tripper.Navigation.WowNavigator.FindPath(Vector3 start, Vector3 end)
at Styx.Pathing.MeshNavigator.CanNavigateFully(WoWPoint from, WoWPoint to, Int32 maxHops)
at Styx.Pathing.Navigator.CanNavigateFully(WoWPoint from, WoWPoint to, Int32 maxHops)
at Styx.Pathing.Navigator.CanNavigateFully(WoWPoint from, WoWPoint to)
at Styx.CommonBot.Database.NpcQueries.GetNearestNpc(WoWFactionTemplate myFaction, UInt32 mapId, WoWPoint searchLocation, UnitNPCFlags npcFlags)

I agree with earlier posts, i payed a year subscription. But i have serious doubts that i did the right thing!

/Zaxxon

 

Yea i am having the same issue....bot continuously crashes. This only started happening after I upgraded to 3 sessions from 1.