What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Kupper - Demo/Testing

System.NullReferenceException: Object reference not set to an instance of an object.
at Kupper.Rotations.Ninja.OnPulse() in c:\Users\X\Documents\Bots\RebornBuddy\Routines\Kupper\Rotations\Ninja.cs:line 152
at Kupper.KupperRoutine.Pulse() in c:\Users\X\Documents\Bots\RebornBuddy\Routines\Kupper\KupperRoutine.cs:line 61
at ff14bot.Behavior.Pulsator.Pulse(PulseFlags CurrentPulseFlags)
at ff14bot.TreeRoot.()
 
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?
 
Last edited:
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.
 
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.

You were right, it worked after I toggled it, weird bug! Thanks for the help at least. I only mentioned it since I was using Kupper to get my relic weapon on Ninja and I got called out for not doing any DPS to regular mobs since I was bugged with it. Might be because I got Rogue and Ninja on the same playthrough without once logging off or reopening the client. Still am, actually, lol.
 
Would it be possible to work in a scripted opening rotation into the bard that uses a specific rotation and early clip once just at the beginning of the fight? Only improvement imo that could be made to the bard one, it's really great so thank you for it regardless.
 
I'll look into it. It will be at least a couple days because of the holidays and stuff.
 
I'll look into it. It will be at least a couple days because of the holidays and stuff.

No rush, but if it's possible to add it would be awesome. Also if you could work in potion usage into the rotations that would be a step up as well (X-Potion of Dexterity HQ, Potent Poisoning Potion HQ). As far as the bard opening there is a good guide on it atm which I'll link, as well as just post the opening here in plain text.

Code:
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.
 
Last edited:
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. :)

Ichiban,

Please refrain from trusting advice from random users on Reddit. The Dancing Edge opener is not higher potency even without another player applying the slashing debuff. It also has the benefit of debuffs lining up much better further on in the fight translating into less downtime and less clipped DoTs. Applying Dancing Edge first for a chunk of abilities that aren't affected by slashing debuff in any way (ninjutsus, DoTs) is nothing but wasted DPS and wasted debuff time. The opener you have coded already is close to optimal, minus the DoT order (DoTs should be applied in SF -> Mut order, it's an overall 10 potency increase to apply SF first, plus doing SE first allows you to snapshot both DoTs). I've adjusted my own PrioritySelector to:

Code:
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")
						)

and it works as expected.
 
Last edited:
Hello, your CR is really great :D

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
 
Hello, your CR is really great :D

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.
 
Can you post a log of that? It's probably animation lock from either a gcd attack or a buff.

Hi, thank you for your help. The problem was actually user side, after I bought WTFast the problem went away :)

Now I have a new problem though, i am now level 45, Huton available. The CR however prioritize Raiton over Huton all the time :(

log attached
 

Attachments

Hello, used this on my ninja and it was great! I would like to pugilist/monk added please. Will donate =)
 
im using Kupper in conjunction with Fate Bot and it seems to idle quite often due to Line of Sight issues when playing as brd/arc
 
Updated: Added a list to add enemies you don't want to DOT, correctly made shadowfang come before mutilate since people insist it's better, and added a list for enemies to use fuma shuriken on instead of raiton (like the t11 orb thing that resists magic).
 
Back
Top