why not post the LAS/build to go with the logic that is currently in the combat routine? breashing strikes isnt being cast when its procced
Hmm, yeah it looks like for warrior CR that Savage Strikes is being used correctly, however Breaching Strikes (on-crit ability) is not. Previously, Breaching Strikes was triggering right away. View attachment Wildbuddy 4612 2015-02-23-19.10.26.zip
Slingers still appear to have an issue of trying to spam spell surge regardless of the innate being available - and as it's an innate there's really easy way to avoid it (in the case of warriors spamming abilities without enough energy, I simply removed the offending skills from my action set). Is there an easy way to simply disable class innates for spell slingers until this one is resolved? I'm not sure the innate is even necessary for leveling/grinding in most cases. Thanks!
Puck can you give me a log of the issues you are having. Slinger's have spellsurge management but it may need tweaking I thought it was working fine. Currently the routine will use any abilities you set in your LAS they should work. CURRENTLY warrior is being adjusting for a few things but I know breaching strikes works but I will check it over again. I am going to update warrior with my current build in the next day. My real life job have been preventing me from addressing issues. Im sorry . @romancerbcl you can pick any abilites and it should work. Post me a log and I will fix. If you can tell me the LAS you are using that would be great. Some abilties seem to not work well with others this way I will be able to address/fix in the routine.
I think Breaching Strikes in this update changed the syntax from: if (Me.HasBuff("Breaching Strikes") to if (IsSpellProcReady("Breaching Strikes"). I changed to: if (Me.HasBuff("Breaching Strikes") and it started working again. Hope this helps
That's currently what I have it set to....did I mess up something :S. if (Me.HasBuff("Breaching Strikes") && await Cast("Breaching Strikes")) return true;
Here ya go, sorry, I thought I attached on the original. Spell Surge spam begins around line 400. View attachment Log2.txt
Thank you so much! I think I know whats going on here. Going to test later tonight and will let you know when I push fix. Sorry!
Here is temp SVN. https://www.assembla.com/code/default-routine/subversion/nodes Spellslingers fixed. Few other fixes etc just too lazy to type them. Maybe if I worked for some company that did patch notes but just not my thing. Soon all routine updates will come with regular bot updates. Will update more if needed. Please post feedback and I am going to be pushing another update before end of week. Thanks
I'm not 100% sure why, but savage strikes went from working in version 2 to not working in version 3. View attachment Wildbuddy 6436 2015-02-28-19.52.33.zip edit: hmm I reverted to a previous version and savage strikes wasn't working in my old build of the CR either.
I will push a fix later this evening. I know whats wrong just need to make some adjustments. I have a few other tweaks etc on few other classes. Thanks for being so chill !
Update was pushed with changes all over etc. Too lazy to type stuff out. Next update will have it otherwise SVN should have it also. Walter
new to wildsatr bottign fresh from the abn in wow lol i was wondering what to use to just run the comabt routine wituout a profile like enyo did so i can quest manually but the bot do the rotaion for me
You can load up a blank XML file just like any other bot base here and it will do the rotation as you go into combat. That way it won't be calling nav server for movement etc.
Yes it does work if you are having issues let me know and I will push a newer build I have. Default routine is included with wildbuddy but I will put up another SVN for access for when I update faster than core updates. Most of the time when you get new WB updates Combat Routine has been updated and changed. Its always growing I promise.
Thank you But i have another problem. WB gives errors and crashing after a while. Installed dependencies (x64 and dx11) UNHANDLED DISPATCHER EXCEPTION System.NotImplementedException: Yöntem veya işlem uygulanmadı. konum: CombatBot.CombatBot.Equals(IBot other) e:\WildStar\Wildbuddy\Bots\CombatBot\CombatBot.cs içinde: satır 74 konum: System.Collections.Generic.GenericEqualityComparer `1.Equals(T x, T y) konum: System.Collections.Generic.List`1.Contains(T item) konum: System.Windows.Controls.Primitives.Selector.Coerce SelectedItem(DependencyObject d, Object value) konum: System.Windows.DependencyObject.ProcessCoerceValue (DependencyProperty dp, PropertyMetadata metadata, EntryIndex& entryIndex, Int32& targetIndex, EffectiveValueEntry& newEntry, EffectiveValueEntry& oldEntry, Object& oldValue, Object baseValue, Object controlValue, CoerceValueCallback coerceValueCallback, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, Boolean skipBaseValueChecks) konum: System.Windows.DependencyObject.UpdateEffectiveVal ue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType) konum: System.Windows.DependencyObject.SetValueCommon(Dep endencyProperty dp, Object value, PropertyMetadata metadata, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType, Boolean isInternal) konum: System.Windows.DependencyObject.SetValue(Dependenc yProperty dp, Object value) konum: Buddy.Wildstar.MainWindow.InitializeGlobalSettings () konum: Buddy.Wildstar.MainWindow.<AttachProcess>d__1c.Mov eNext() --- Özel durumun oluşturulduğu önceki konumdan başlayan yığın izlemesinin sonu --- konum: System.Runtime.CompilerServices.TaskAwaiter.ThrowF orNonSuccess(Task task) konum: System.Runtime.CompilerServices.TaskAwaiter.Handle NonSuccessAndDebuggerNotification(Task task) konum: Buddy.Wildstar.MainWindow.<HandleProcessSelectorRe fresh>d__2f.MoveNext() --- Özel durumun oluşturulduğu önceki konumdan başlayan yığın izlemesinin sonu --- konum: System.Runtime.CompilerServices.AsyncMethodBuilder Core.<ThrowAsync>b__4(Object state) konum: System.Windows.Threading.ExceptionWrapper.Internal RealCall(Delegate callback, Object args, Int32 numArgs) konum: MS.Internal.Threading.ExceptionFilterHelper.TryCat chWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
