Game client updated to 13.2.0.37351.
I there guys,
Edit2: Why is the Valla character missing from the list?
The new version, 471.74, getting better TPS, around 9-14, but the heroe (at least Diablo) just plays as dumb as a door nob. He just stands stop a lot, when attacking, has no survival instinct and just rush in, till he dies lol.. but tue performace is a little better on the tps side.
Also getting randomly a read wall of text
He walks-stop(wait about 4-5secs) to walk-stop again, this happens realllly a lot. Other bug is that sometimes he just spins around in the same spot, lookin bootish
The new version, 471.74, getting better TPS, around 9-14, but the heroe (at least Diablo) just plays as dumb as a door nob. He just stands stop a lot, when attacking, has no survival instinct and just rush in, till he dies lol.. but tue performace is a little better on the tps side.
Also getting randomly a read wall of text
He walks-stop(wait about 4-5secs) to walk-stop again, this happens realllly a lot. Other bug is that sometimes he just spins around in the same spot, lookin bootish
We'll look into Diablo. Thanks
Unhandled exception!Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.ArgumentOutOfRangeException: Cannot move mouse outside of the client window bounds!
Parameter name: location
at Stormbuddy.Game.Win32.RemoteInput.MoveMouse(Int32 clientX, Int32 clientY)
at Stormbuddy.Game.UI.UIFrame.MouseOver()
at Stormbuddy.Game.UI.UIFrame.Click()
at Stormbuddy.Bot.Pulsators.OutOfGamePulsator.%0y`m)fzr/\\)N$o>kHa`wNe4".()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Stormbuddy.Bot.Pulsators.OutOfGamePulsator.Lh4mUHE^Yl>k=MQOQ8L^BbsJ".()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Stormbuddy.Bot.Pulsators.OutOfGamePulsator.=Oceh#(fTbD4RGY`#2M-\.\&-u).()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Buddy.Coroutines.Coroutine.boz)>_hGCMJ9FA\.;{AknK(\\1.=Oceh#(fTbD4RGY`#2M-\.\&-u).()
--- End of inner exception stack trace ---
at Buddy.Coroutines.Coroutine.*************(Boolean )
at Buddy.Coroutines.Coroutine.**************(Boolean )
at Buddy.GameEngine.CoroutinePulsable.Pulse()
Map Changed to Garden of Terror (GardenOfTerror)
Exception while pulsing Stormbuddy.DefaultRoutine.DefaultCombatRoutineSystem.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 0, Size: 4
at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
at GreyMagic.MemoryBase.Read[T](IntPtr addr)
at Stormbuddy.Game.Unit.Equals(Unit other)
at System.Collections.Generic.GenericEqualityComparer`1.Equals(T x, T y)
at System.Linq.Set`1.Find(TElement value, Boolean add)
at System.Linq.Enumerable.<UnionIterator>d__1`1.MoveNext()
at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
at Stormbuddy.DefaultRoutine.DamageTracker.***************()
at Stormbuddy.DefaultRoutine.DefaultCombatRoutine.Pulse()
at Buddy.GameEngine.Pulsator.Pulse()
...
Attacking shambler at X:192.4619 Y:146.3125
Attacking shambler at X:192.5757 Y:146.3125
Attacking shambler at X:192.636 Y:146.3125
Attacking shambler at X:192.7087 Y:146.3125
Attacking shambler at X:192.7485 Y:146.3125
Attacking shambler at X:191.7004 Y:146.3125
Attacking shambler at X:191.0496 Y:146.0718
...
@Aprosule:
The Read/WriteProcessMemory exception is due to the bot using an "invalid" unit. We recently changed how units are handled, so they're consistently correct. (This was a bug we had, which is now fixed, but has raised a few other bugs in the process) I'll definitely get that one fixed ASAP. Thanks for the heads up.
As for the game crash, make sure you uncheck "Send to Blizzard" (for obvious reasons), and please PM me the crash dump folder. (User/Documents/Heroes of the Storm/GameLogs folder contains the crash dump info)