yes, singular throws lots of errors too, but when the bot stopped, the last action was from KoM as far as I see. I didn't stop it manually!
PHP: [06:02:30.318 D] Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.Exception: Nur ein Teil der ReadProcessMemory- oder WriteProcessMemory-Anforderung wurde abgeschlossen, at addr: EEE00000, Size: 400 at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count) at GreyMagic.MemoryBase.Read[T](IntPtr addr) at ..() at Styx.CommonBot.SpellManager.CastSpellById(Int32 spellID, WoWGuid targetGuid) at Styx.CommonBot.SpellManager.CastSpellById(Int32 spellID) at KeepOnMoving.KOMCore.<DruidForm>d__158.MoveNext() in D:\HB\Release\Plugins\KeepOnMoving\KeepOnMoving.cs:line 1152 Seems like HB stopped working when KoM tried to cast DruidForm. There has been a new dev release having this issue fixed. Just wait for the proper release and those errors should cease to occur.
Seems to be the very same error. I can't do much about it; it's HB related, not the plugin itself causing this issue and should be fixed with next hb release
Why isn't the setting window for KoM opening? I have a fresh install of hb.. I have to go to KoM setting folder and edit each .config file to change settings.
PHP: [19:40:07.366 D] System.IO.DirectoryNotFoundException: Could not find a part of the path 'D:\HB\Release\Cache\Plugins\KeepOnMoving\KOM.ico'. Seems like HB is not able to find icon for settings window. Make sure "KoM.ico" is located in KeepOnMoving folder and check spelling (lower/uppercase)
v3.2.78 ꙰ Bug fixed - Settings window couldn't be opened - Char couldn't reach Npc for Brimstone - Rank 2 - Prequest conditions for Brimstone - Rank 3 fixed - Heirlooms weren't properly created ꙰ Minor change - Removed "Use Artifact Knowledge Items" As I am working on implementing all herbalism and mining specific ranks, I will provide this chart indicating current rank coverage: MINING ꙰ Leystone # 1: ⚫ ⚫ ⚫ # 2: ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ # 3: ⚫ ⚫ ⚫ ꙰ Felslate # 1: ⚫ ⚫ ⚫ # 2: ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ # 3: ⚫ ⚫ ⚫ ꙰ Infernal Brimstone # 1: ⚫ # 2: ⚫ # 3: ⚫ ⚪ ⚫ ⚪ ꙰ Empyrium # 1: ⚪ ⚪ # 2: ⚪ ⚪ # 3: ⚪ ⚪ HERBALISM ꙰ Aethril # 1: ⚫ ⚫ # 2: ⚫ ⚫ # 3: ⚫ ꙰ Dreamleaf # 1: ⚫ ⚫ # 2: ⚫ ⚫ # 3: ⚫ ⚫ ꙰ Foxflower # 1: ⚫ # 2: ⚫ ⚫ # 3: ⚫ ꙰ Fjarnskaggl # 1: ⚫ # 2: ⚫ ⚫ # 3: ⚫ ⚫ ꙰ Starlight Rose # 1: ⚫ ⚫ # 2: ⚫ ⚫ # 3: ⚫ ⚫ ꙰ Felwort # 1: ⚫ # 2: ⚫ # 3: ⚪ ꙰ Astral Glory # 1: ⚪ # 2: ⚪ # 3: ⚪ Not yet implemented ⚪ Implemented ⚫ Successfully tested ⚫
v3.2.79 ꙰ Bug fixed - Fixed some more bugs whenever a file is loaded As I am working on implementing all herbalism and mining specific ranks, I will provide this chart indicating current rank coverage: MINING ꙰ Leystone # 1: ⚫ ⚫ ⚫ # 2: ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ # 3: ⚫ ⚫ ⚫ ꙰ Felslate # 1: ⚫ ⚫ ⚫ # 2: ⚫ ⚫ ⚫ ⚫ ⚫ ⚫ # 3: ⚫ ⚫ ⚫ ꙰ Infernal Brimstone # 1: ⚫ # 2: ⚫ # 3: ⚫ ⚪ ⚫ ⚪ ꙰ Empyrium # 1: ⚪ ⚪ # 2: ⚪ ⚪ # 3: ⚪ ⚪ HERBALISM ꙰ Aethril # 1: ⚫ ⚫ # 2: ⚫ ⚫ # 3: ⚫ ꙰ Dreamleaf # 1: ⚫ ⚫ # 2: ⚫ ⚫ # 3: ⚫ ⚫ ꙰ Foxflower # 1: ⚫ # 2: ⚫ ⚫ # 3: ⚫ ꙰ Fjarnskaggl # 1: ⚫ # 2: ⚫ ⚫ # 3: ⚫ ⚫ ꙰ Starlight Rose # 1: ⚫ ⚫ # 2: ⚫ ⚫ # 3: ⚫ ⚫ ꙰ Felwort # 1: ⚫ # 2: ⚫ # 3: ⚪ ꙰ Astral Glory # 1: ⚪ # 2: ⚪ # 3: ⚪ Not yet implemented ⚪ Implemented ⚫ Successfully tested ⚫
I can open window now and it starts. It went to turn in mining quest and got that error where it broke wow. Any idea? I think the FPS stuff is the culprit? tried it again, it started and used artifact power and got error again
A lot of things have changed with latest HB release and I guess this is rather related to new mechanics introduced avoiding Blizzards detection algorithms. I do get a lot of errors myself and had HB + KoM running for days before 7.3 I need to figure out what is causing this behaviour
Seems like HBRelogHelper causes WoW and HB to crash every 5 minutes. It's now working fine without any crashes; maybe this information could be useful for others.
I may will if there's more interest in in. In order to add skinning trainers all over azeroth and evaluating if a mob needs to be skinned or could be bypassed, I will have to invest some time. Time that will not be spent for developing new features or improving the existing ones.
How tun off hb reloghelper? at the moment had to take out your plugin because it crashed all the time
