sorenelise
Member
- Joined
- Dec 4, 2011
- Messages
- 188
I am getting the attached error, please advise.
View attachment 1528 2014-11-23 10.14.txt
View attachment 1528 2014-11-23 10.14.txt
The in-game face target setting works fine with ninjutsu. Try turning the setting off and back on in the game and trying it again. Magitek messes with that setting, and maybe some other CRs do too. I might make an update to magitek later today that makes it stop doing that.Something about Ninja skills not being affected by the option to "Automatically face targets when using skills" so I often get Target is not in range errors with Kupper, it seems like a game bug but is there way for us to artificially fix it?
The in-game face target setting works fine with ninjutsu. Try turning the setting off and back on in the game and trying it again. Magitek messes with that setting, and maybe some other CRs do too. I might make an update to magitek later today that makes it stop doing that.
I'll look into it. It will be at least a couple days because of the holidays and stuff.
Hawk's Eye
Raging Strikes
-
Bloodletter
Straight Shot
-
Blood for Blood
Internal Release
Windbite
-
X-Potion of Dexterity
Venomous Bite
-
Barrage
-
Blunt Arrow
-
Heavy Shot
Flaming Arrow
-
Bloodletter if not available Repelling Shot
-
Heavy Shot
Potent Poisoning Potion
-
REAPPLY DoTs clipping @ 6 seconds
A full duration BRD DoT ticks 6 times, by clipping it @ 6 seconds on this Opener the last 2 ticks from both dots wont tick, but they will be refreshed full duration with all the buffs still active giving you an uptime of 30 seconds with fully buffed DoTs, instead of 36 seconds where all other openers wont even have Internal Release active on their second set of DoTs
After this point, the routine should just go into your awesomely made normal priority rotation.
This is a great combat routine so far. Great work. I have two suggestions.
1. Would it be possible to change the opening rotation more in reference to this? :
The "Ideal" Opener:
pre-pull huton (pull happens @5~ seconds to ninjutsu off cd) -> spinning edge -> ir -> gust slash -> bfb -> dancing edge -> suiton -> spinning edge -> trick attack -> shadow fang -> kassatsu -> mutilate ->raiton -> spinning edge -> mug -> gust slash -> jugulate
This is mathematically the highest average damage opener because of the 'snapshotting' of your dots outweighing other setups. After this opener, you will either dancing edge or aeolian edge depending on if you have Storm's Eye being applied. In this context, your huton will be reapplied in the second ninjutsu after the opener; ideally you're fast enough such that your will start a non-huton'ed gcd then cast huton, effectively extending the duration of the previous huton since a 3-step mudra invocation invariably will delay your next gcd.
The in-a-rush-tank opener:
huton as tank is going in -> spinning edge -> ir -> gust slash -> bfb -> dancing edge -> mug -> mutilate -> jugulate -> spinning edge -> shadow fang. Some time a little later into the fight (3-4 gcds~) you will weave suiton -> trick -> kassatsu -> raiton.
I pulled this information from here and I've tested the difference personally and it's anywhere between a 20-30 dps increase according to ACT. I would love it if someone else could test this to confirm for me and if all is good we can rework the rotation a bit for higher dps.Also, among my server it's becoming noticeable that opening with mutilate is not ideal and it gets commented on infrequently for me. I can only imagine this is going to get worse as more ppl find optimal rotations.
2. I would like to request a feature that acknowledges another ninja or the trick attack debuff for openers.
I understand if this can't be done or is too complicated to implement but it would be such an awesome feature. Let me first clarify by saying this: on my server it's also becoming a thing to have two Ninjas in the party for 20 seconds of the trick attack debuff. Ideally, having two ninjas in the party allows them to coordinate their attacks so they can have the trick attack debuff up as long as possible. As it stands now I can temporarily bypass this by telling everyone "I'll be the first to apply it" because it falls naturally in Kupper's natural rotation, however, if the routine was optimized to recognize the trick attack debuff and adjust it's rotation accordingly then this wouldn't even be an issue any longer.![]()
new PrioritySelector(
Spell.Cast("Spinning Edge", r => !Core.Me.CurrentTarget.HasAura("Shadow Fang", true, settings.ShadowFangClip) && Core.Me.CurrentTarget.CurrentHealth >= settings.DOTLimit && Actionmanager.LastSpell.Name != "Spinning Edge"),
Spell.Cast("Mutilate", r =>
(!Core.Me.CurrentTarget.HasAura("Mutilation", true, settings.MutilateClip) && Core.Me.CurrentTarget.CurrentHealth >= settings.DOTLimit) &&
(
(Actionmanager.LastSpell.Name == "Spinning Edge" && Core.Me.ClassLevel < 4) ||
(Actionmanager.LastSpell.Name == "Gust Slash" && Core.Me.ClassLevel < 26) ||
(Actionmanager.LastSpell.Name == "Shadow Fang") ||
(Actionmanager.LastSpell.Name == "Aeolian Edge") ||
(Actionmanager.LastSpell.Name == "Dancing Edge") ||
(Actionmanager.LastSpell.Name == "Mutilate") ||
(Actionmanager.LastSpell.Name == "EmptySpell")
)),
Spell.Cast("Dancing Edge", r =>
Actionmanager.LastSpell.Name == "Gust Slash" &&
(!Core.Me.CurrentTarget.HasAura("Dancing Edge", false, settings.DancingEdgeClip) && !Core.Me.CurrentTarget.HasAura("Storm's Eye", false)) &&
settings.UseDancingEdge),
Spell.Cast("Aeolian Edge", r => Actionmanager.LastSpell.Name == "Gust Slash"),
Spell.Cast("Shadow Fang", r => Actionmanager.LastSpell.Name == "Spinning Edge" && !Core.Me.CurrentTarget.HasAura("Shadow Fang", true, settings.ShadowFangClip) && Core.Me.CurrentTarget.CurrentHealth >= settings.DOTLimit),
Spell.Cast("Gust Slash", r => Actionmanager.LastSpell.Name == "Spinning Edge"),
Spell.Cast("Spinning Edge")
)
Hello, your CR is really great![]()
However, sometimes when casting Mudra it would say 'cannot execute action at this time'.
Is there a known cause of it? How should I fix it?
Thank you
Can you post a log of that? It's probably animation lock from either a gcd attack or a buff.