HB is broken.

Hello lads!
THIS ISSUE WAS PRIOR TO THE PATCH
So, I was given an infraction in my previous thread, due to my "crude language". Which, I definitely did not have, but I guess that differs from person to person.

We could talk about a crude attitude, but how would you react, when your support question doesn't get looked at, instead there's a copy pasted reply that has nothing to do with your issue and a thread lock TIMES 3.

I get that you wanted this post moved into the correct category, for that, I have nothing against.

But to throw out an infraction, then there after still not adress my issue, instead say "repost a proper thread" thats... not how to treat a paying customer.

I hope that this time, it will be adressed:

So all of a sudden my HB is stuck at the login sequence.

I have tried this:

Fresh reinstall
Reboot
Disable AntiVirus
Delete Mesh, Caches and Appdata

Here's a log

[12:35:27.223 N] Honorbuddy v2.5.14460.802 started.
[12:35:30.047 N] Logging in...
[12:35:30.261 N] T: 5247485063727952407 H: 3656177943
[12:35:31.290 D] System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.Collections.ArrayList.get_Item(Int32 index)
at System.Diagnostics.ProcessThreadCollection.get_Ite m(Int32 index)
at GreyMagic.ExternalProcessMemory.**​‬‏***‫**** ‎**‫**‬*‪‏‎​‎*‫‏**(ExternalProcessMemory InitP arams )
at GreyMagic.ExternalProcessMemory.**​‬‏***‫**** ‎**‫**‬*‪‏‎​‎*‫‏**(Process , Boolean , Boolean , Boolean , IntPtr , Boolean , Int32 , Boolean , Boolean )
at GreyMagic.ExternalProcessMemory..ctor(Process p, Boolean startupExecutor, Boolean dx9, Boolean startupRasm)
at Honorbuddy.MainWindow.;uk$LN`}myVD\\vx^J$GRx(QT'.M oveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowF orNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.Handle NonSuccessAndDebuggerNotification(Task task)
at Honorbuddy.MainWindow._?N0U\*VTfhG\[;6\*d#;0gApBT\&.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowF orNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.Handle NonSuccessAndDebuggerNotification(Task task)
at Honorbuddy.MainWindow.>\,C|yNwrE-u)tqQ<3MO=y5?n'.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowF orNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.Handle NonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.Valida teEnd(Task task)
at Honorbuddy.MainWindow.|7dMA7=}$r`lCzGeShH@Y!2@#.Mo veNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowF orNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.Handle NonSuccessAndDebuggerNotification(Task task)
at Honorbuddy.MainWindow.{W EZxF}:VB;wb%Dk1)|?-M"!.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilder Core.<>c__DisplayClass2.<ThrowAsync>b__3(Object state)
at System.Windows.Threading.ExceptionWrapper.Internal RealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatch When(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

 

OMG HB is down ATM wait n see

 

omg get over it.

 

My issue was BEFORE the patching and when HB was down.

 

When you do a fresh install, uninstall HB from program files then delete the HB folder from your PC. Also, with the new server system, did you make sure to chose the region you're in ? because i tried "Best latency" and it didn't work. I used north america and everything is fine!

 

Yes, I have done everything in that regard, thanks for the reply though.

 

you need to wait for the new version of honorbuddy to be released BEFORE we can continue working on resolving you issue.
once the new version is released if the issue still persists then please make a NEW support thread with a detailed description of the issue and full log as an attachment and we will be more then glad to help you with this issue.