Modded Retribution Paladin (from test build) View attachment Retribution.cs Moved down Wake of Ashes for single target, was casting too soon hitting only 1 mob when more were around. Moved up Blade of Justice (Divine Hammer) for single target and added to AoE section. It was not casting it for AoE losing Holy Power generation, and was even more wastefull if Divine Hammer was talented. Added Justicar's Vengeance to be used with 5 Holy Power. Was casting only with "Divine Purpose". Hope this helps some
Test versions are only released when there's actually a test release candidate. If you're asking how to download the normal version of Singular.. you don't have to. It's the default combat log that comes with the bot.
Feel free to use any other routine for Rogues. Or. Have patience. I'm a single person maintaining not only this but the entire questing pack - you can't expect me to flaw-proof all 36 class specializations within weeks of the release.
I'll investigate these changes as soon as possible. At the moment I'm queing the community contributions up and will evaluate/implement them once high priority bugs are fixed.
I've reduced the default Effuse health% setting to prevent this. But as Xalcon posted, you can manually change this to prevent it from happening.
It won't be removed from the rotation as it's a major part of the rotation - and most people want it in. However, a setting can be added that lets you determine when the bot casts it. I can look into adding that.
Ideally it's best to follow what sites like Icy-Veins suggests. Singular is meant to utilize every talent, so there's no really a best setup specifically for Singular.
Yea, it would be possible. The Honorbuddy API has a "Math" class dedicated to calculating stuff regarding coordinates.
V2: Moved up Justicar's Vengeance as it was not being casted enough and wasting holy power. View attachment Retribution.cs
I think your log was improperly attached as the link goes to a dead end. So far all my testers have been using it fine. But - I can look into it.
It was a bug in the diagnostic logging causing the routine to lag out. This should be fixed in the latest version. If it's not then I'll need a log.
Thanks for the contributions! I'll look into getting these modifications merged to the Singular trunk soon - and will be sure to credit you in the changelog entry.
Vengeance Demon Hunter (test build). Changes Infernal Strike to jump at same location instead of target's. Change Line 90 to: Spell.HandleOffGCD(Spell.CastOnGround("Infernal Strike", location => (Me.Location), ret => DemonHunterSettings.DPSInfernalStrike && Spell.GetCharges("Infernal Strike") > 1)), Or replace file with: View attachment Vengeance.cs This is just personal preference. I hate how Infernal Strike jumps to the target, moving the entire pack of mobs wich often results in some getting in your back. Could be nice to have settings to switch this kind of spells target location but I have no idea how to do that.
I cant put my Warlock to levl up cos Singular is summoning doomguard in every fight few times as you can see from the log , its casting it like a spell. Even i have placed to summone Infernal it keeps summoning dooguard like a spell Any fix for that?
my vengeance dh interrupt mounting after combat. it looks like it's tying to cast some spell |Singular| enter: Rest |Singular| leave: Rest, status=Success and took 2 ms |Singular| enter: Rest |Singular| leave: Rest, status=Success and took 1 ms |Singular| enter: Rest |Singular| leave: Rest, status=Success and took 2 ms |Singular| enter: Rest |Singular| leave: Rest, status=Success and took 2 ms |Singular| enter: Rest |Singular| leave: Rest, status=Success and took 2 ms |Singular| enter: Rest |Singular| leave: Rest, status=Success and took 2 ms |Singular| enter: Rest |Singular| leave: Rest, status=Success and took 2 ms |Singular| enter: Rest |Singular| leave: Rest, status=Success and took 1 ms (Singular) [WoWRedError] 252 |Singular| enter: Rest |Singular| leave: Rest, status=Success and took 2 ms |Singular| enter: Rest |Singular| leave: Rest, status=Success and took 2 ms |Singular| enter: Rest |Singular| leave: Rest, status=Success and took 1 ms |Singular| enter: Rest |Singular| leave: Rest, status=Success and took 2 ms |Singular| enter: Rest |Singular| leave: Rest, status=Success and took 2 ms (Singular) CastingState: Casting=N CastTimeLeft=51 |Singular| enter: Rest |Singular| leave: Rest, status=Success and took 2 ms |Singular| enter: Rest |Singular| leave: Rest, status=Success and took 1 ms |Singular| enter: Rest |Singular| ... enter: Rest.CreateDemonHunterRest.0 |Singular| ... leave: Rest.CreateDemonHunterRest.0, took 0 ms |Singular| leave: Rest, status=Failure and took 2 ms |Singular| enter: PreCombat |Singular| leave: PreCombat, status=Failure and took 0 ms Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. Starting behavior [ForcedSingleton]. Behavior flags changed! All -> Death, Loot, Vendor, Roam, Pull, Rest, FlightPath Done with forced behavior [ForcedSingleton]. Starting behavior Bots.Quest.QuestOrder.ForcedMoveTo. Goal: Moving to <361.9339, 1539.259, 89.47511> [Ref: "MoveTo" @line 101] [Singular] info: Behavior [Combat] DISABLED by Questing or Plug-in (Singular) [WoWRedError] 50 Done with forced behavior Bots.Quest.QuestOrder.ForcedMoveTo. Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. [DoWhen-DoWhen(debug)] DoWhenActivity 'ActivityName(Silence)' removed. [DoWhen-DoWhen(debug)] DoWhen hook removed--no DoWhenActivities to clean up. Removed hook [Questbot_Main] cbb4ebf7-289e-4410-a7a5-f221502d8292 [DoWhen-DoWhen(debug)] DoWhen behavior complete. Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior. [DoWhen-DoWhen(debug)] Behavior completed in 0s Starting behavior Bots.Quest.QuestOrder.ForcedMoveTo.