Vedude

Looks good. No more problems. That new human behavior looks cool, but I dont see it being applied on my run now, perhaps a work in progress? Also, is there any changelog on these kind of updates? I have to dig through the settings to find out every time otherwise. Thanks for everything!

Hello @Droidz , Thank you very much for the assistance. With the plugin, all crashes are gone and Wrobot works with the client without issues. I hope that helps you further to track down the root of the cause. Do you need anything from me?

23 Oct 2026 07H10 - zCoGmoE.log.html Hi. I turned it off and ran it again. As soon as it walked one or two waypoints it crashed. Checked the logs, same red colored errors appeared before crashing. I saw there was a update this morning, so I applied that also before testing.

Update: I used the downgraded version of Wrobot I had from before, and the crashes are gone. This is a workaround, but is there any chance to see what caused these issues on the newest Wrobot version? Thanks!

Hello, After Wrobot update, the WoW client crashes here and there shortly after starting up Wrobot or during combat. The error: Wow.exe 3.3.5a crashes (memory access violation in unknown module) since WRobot 2.8.2 (27439) Whats used: - WRobot 2.8.2 (27439), compiled 10/20/2026, for 3.3.5a_12340 - Log shows: "[Memory] D3D9 used", "HWBP hook", "[StealthProtection] Active", "[Memory] Hooking success" What happens: - About 3 seconds before the crash the game stops responding: Lua calls. - Then the client dies. WRobot logs a flood of these errors as it goes down (I assume this is a symptom, not the cause): GetReactionTowards(WoWFactionTemplate otherFaction): System.NullReferenceException at wManager.Wow.Helpers.WoWFactionTemplate.GetReactionTowards(WoWFactionTemplate otherFaction) Windows Event Viewer (Application log) Faulting application name: Wow.exe, version: 3.3.5.12340, time stamp: 0x4c2452fe Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x7ff44e73 Problem signature: APPCRASH, P4: StackHash_3850, P7: c0000005, P8: PCH_38_FROM_unknown+0x00000000 I have attached the Wrobot logs for the character this happened to, but its the same type of logs on my other characters as well. I never experienced this issue before, and it only started happening after the recent Wrobot update. 22 Oct 2026 10H35 - crash 2.log.html 22 Oct 2026 10H31 - crash 1.log.html

So that only means Wrobot has to be updated to not crash running on Epoch. I will renew my sub if it gets compatible. I see many people are waiting for this so I hope we get a update on Wrobot.

I am also awaiting a fix for this. We are all paying customers, its only fair we ask for support on the servers to bot on. @Droidz Could you please take a look into this as soon as possible? For me the bot just crashes and cloises immediately as soon as I start it up. Thank you.