Any ideas on this? It just keeps popping up a bug window in wow with this. I did check to see if I had dotnet 3.5 installed and it does show up in the installed windows components.
any idea's about what was "fixed" if anything with SOTA? I tried to run it a couple of times last night, but it would never leave the beach area. I never saw it head way north like it used to, but it just patrolled back and forth between the boats. (I was using wootsauce's neutral sota profile btw)...
Getting this error again : Code: Authenticating.. Could not connect to the authentication server. It may be too busy to process your request. Please wait a few minutes and try again! Authentication failed. Happened to me last release, then it was fixed and now it does it again with this release.
Use one version before there it was fix'd, anway I can't understand how this got back in. However, this version is really buggy, sometimes he stuck for no reason at a mailbox and also stuck sometimes on a vendor (he just stay in front and don't do anything) but also a greater problem is my "Applying PreCombatBuffs" which let my toon don't do anything but disconnected. This problem happens after a certain time based on my luck. So afk farming is pretty senseless. This happening with every warlock CC even the standart one (pet recalling on every dismount also no matter what cc or standart) Hoping for a new better working version soon. So far
uh. none of which is related to my post, but hey thanks for quoting me. i always get set next to the crazy people.
' How bout a quote in a quote there is no fix for that??Uh uh uh got it? It's a honorbuddy problem back then fix'd today its back.
Seems to be related to the default pally cc. When I tried another cc it stopped this particular error and ran, however that particular cc also seems to have errors.
it's ok, a lot of people here don't use english as their 1st language. last version, and the one previous to that as well had the same problem. i've not seen one that DIDN'T do it. i'm pretty sure it was this release (or was it the last TEST release) that was supposedly held up a day or two BECAUSE of the SOTA problem.
since 3 hours! this is so ******* making me angry. perhaps you should change it from "a few minutes" to "a few hours" or maybe "a few days"....just a bad joke really..i am not the person that flames arround but at some point it is definitely enough!!!!!!!
Here's a really nasty targetting bug that really needs to be fixed targetting has been an issue for as long as i can remember Code: [3:48:29 PM:646] System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object. at Styx.Logic.Targeting.DefaultTargetWeight(List`1 units) --- End of inner exception stack trace --- at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) at System.Delegate.DynamicInvokeImpl(Object[] args) at Styx.Logic.Targeting.a(Delegate A_0, Object[] A_1)
fix looting please. all else is good otherwise. -Bot stands just out of reach of the mob and HB spams POI error
Umm, error with BGs ending and not leaving BG is back... once the BG ends and timer runs out HB causes critical error in wow and it closes... im sticking with older release
