Another ninja patch

[HB5802W34]

Another ninja patch/update pushed eu side. Noticed it download and update just now. FYI.

 

[iamburst]

Another ninja patch/update pushed eu side. Noticed it download and update just now. FYI.

yes, quick patch went though for me as well (EU) now HB wont attach.

 

[Caper]

Yea. I see daily up to 0-5 ninja patches.

 

[Frizbick]

Yea. I see daily up to 0-5 ninja patches.

Are you sure that were updates? Sometimes my wow client "update" but it dont change version number.

 

[iamburst]

Are you sure that were updates? Sometimes my wow client "update" but it dont change version number.

version number is the same, but HB wont attached :S

 

[ryftobuddy]

What's most likely happening is that you're seeing patches because you've renamed the wow-64.exe to something else and the b.net app is rebuilding the .exe file. It's probably not working because the b.net app is launching the x64 version of wow.

If you really want help, you're going to need to post a log, but I bet the above scenario is what's happening.

You really shouldn't be using b.net app if you're botting btw. Create a desktop shortcut to wow.exe and only run the b.net app if you know a patch occurred and you want to update to it.

 

[iamburst]

[17:39:39.409 N] Honorbuddy v2.5.15260.829 started.
[17:39:39.748 D] Reloading AssemblyLoader<BotBase> - Initializing bots
[17:39:39.748 D] Reloading AssemblyLoader<HBPlugin> - Initializing plugins
[17:39:39.748 D] Reloading AssemblyLoader<CombatRoutine> - Initializing routines
[17:39:43.137 N] Logging in...
[17:39:43.205 D] Logging in to BestLatency (37.187.151.148)
[17:39:43.295 N] T: 5247715934258819820 H: 170974222
[17:39:44.106 D] System.ComponentModel.Win32Exception (0x80004005): Only part of a ReadProcessMemory or WriteProcessMemory request was completed
at System.Diagnostics.NtProcessManager.GetModuleInfos(Int32 processId, Boolean firstModuleOnly)
at System.Diagnostics.NtProcessManager.GetFirstModuleInfo(Int32 processId)
at System.Diagnostics.Process.get_MainModule()
at GreyMagic.MemoryBase.get_ImageBase()
at GreyMagic.MemoryBase.Read[T](Boolean isRelative, IntPtr[] addrs)
at Honorbuddy.MainWindow.mbhKILd1o6}\,\*OL\.iAia>K\[\]!.MoveNext()
--- 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 Honorbuddy.MainWindow.Z%U\.rN_k6O3@XX\*gr;^duz\]Q#.MoveNext()
--- 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 Honorbuddy.MainWindow.B7'%FSq}CY\.G\.FTqJZtz52\*n'.MoveNext()
--- 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 System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Honorbuddy.MainWindow.\\|j?A/hVsU9I5xmX$ah\]s`?o!.MoveNext()
--- 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 Honorbuddy.MainWindow.5=Xbhq6eWxvv\*Z\*X}\*\._SSp\[.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Not using Bnet app, and yea already use desk top short cut.

 

[Aion]

Are you sure that were updates? Sometimes my wow client "update" but it dont change version number.

It is other files updated, not the Wow executables, aka wow.exe or wow-64.exe, so thats why the WoW build is not changed, and its not qualified as patch/ninja patch, so Honorbuddy client should work as usual.