Question - Help with Horn of Unity in INI

[bmars06]

Hey Guys,

Sorry for the noobie question, still figuring this stuff out.

I'm getting the horn of unity for the anni quest and I want to add it to my chars' ini so that they use it when they get bellow a certain amount of endurance or mana (depending on class). This is what I have right now but it does not seem to work reliably.

Any suggestions?

DPS21=Miniature Horn of Unity|98|Cond23

Cond23=(!${Me.Song[Blessing of Unity].ID} && ${Me.PctEndurance} < 80)

 

[ctaylor22]

I just use this in my buffs section:

Buffs15=Miniature Horn of Unity|ManaGroup|60

 

[Marnan]

I take it you wish to use the horn as a combat buff for an endurance using class. The condition looks correct and /echo's back correctly. I'd argue you don't need !${Me.Song[Blessing of Unity].ID} as a condition (though correct), because it's impossible to have the thirty-second song buff up when the Miniature Horn of Unity is ready to cast (10 minute recast) unless you're porting in from POK or GL. But you've got it laid out right. And the endurance condition looks right.

I think though in the course of how KA prioritizes DPS entries, it's just not getting to DPS21 every time you'd like it to go off. My suggestion would be to try this,

DPS21=Miniature Horn of Unity|100|Cond23

Unless I'm mistaken, this should put the Horn of Unity entry higher up on the priority list.

On a different note, from a 110 level perspective, the 1000 points of endurance, mana, and health regen isn't worth much. It's the 600 point damage shield for 30 seconds that's a little sweet. So you might instead set the mob hit points lower (knowing you'd have used at least 1,000 points of endurance by the time the mob is at 90 percent health, and go with a condition such as this,

DPS21=Miniature Horn of Unity|90|Cond23

Cond23=${Target.Level}>=114 && || ${Me.XTarget}>=3

Where you trigger not based on endurance, but just any tougher mob or multi-target pull (knowing you'll have already used at least 1000 points of endurance anyway). But you'll still have the problem with this being way down on the list of DPS priorities.

Good luck.

 

[Rooster]

I take it you wish to use the horn as a combat buff for an endurance using class. The condition looks correct and /echo's back correctly. I'd argue you don't need !${Me.Song[Blessing of Unity].ID} as a condition (though correct), because it's impossible to have the thirty-second song buff up when the Miniature Horn of Unity is ready to cast (10 minute recast) unless you're porting in from POK or GL. But you've got it laid out right. And the endurance condition looks right.

It is probably more to do with the fact that more then one person in group will be casting the buff, so not to waste the 10 min click which will further reduce any usefulness it has as you have also pointed out it is not particularly powerful in today games. But every bit counts and 6 people using a horn effectively and using the !${Me.Song} check is needed to facilitate that. Also song buffs disappear when zoning so it will never be there apart from someone else recently casting it.

To the original topic, it is a small bump to mana/endurance so i would use a particularly high % for the checks, sooner you use it the sooner it is ready to go again. I have always used a ${Math.Calc[${Me.MaxMana}-${Me.CurrentMana}]} lessthen mana giving buff spell im checking to use. So mod rod is what, 12.5k? i use it as soon as ready, if im in combat i'll be using the mana right away anyhow. No point waiting until 80% when 20% of your mana these days is easily 20-30k. Same goes for endurance stuff etc

 

[bmars06]

Correct, I have 4 chars right now with the horn, so I'd like to make sure they are not overriding each other.

Perhaps I should just move it up the DPS# ladder? Maybe just put it to the beginning with a higher endurance %?

 

[Rooster]

I haven't really looked at kissassist dps code stuff, but i assume it will generally be either a order of readiness or order of HP depending on a setting. Most of the time all you normal actualy dps stuff will be ready to fire and just go before horn gets seen. So higher should be better, and it won't really effect the speed of things not being ready to cast and being skipped in the dps routine

You could put it in a mq2melee holyshit , so it should fire outside of any of kissassists stuff. But you will want to add in a !${Me.Invis} && ${Cast.Ready[Miniature Horn of Unity]} && !${Me.Casting} , but that's a whole other thing to deal with

 

[Hylander]

Mine fires on my 6 chars on the following (Mob % health varying across characters to stagger)

DPS15=Miniature Horn of Unity|98|cond7
Cond7=!${Me.Song[Blessing of Unity].ID}

Troubleshoot by removing your condition entirely and see if it fires, if yes, then introduce 1 element of the condition then the other.

What I have found for example are -
1) an MA Buff !${Target.Buff[Ancient Alliance].ID} or my hit points ${Me.PctHPs} etc, even though they /echo correctly don't fire during a fight (when they should). I am not sure if its a speed of response thing or something else .. even adding checks ${Target.Beneficial.ID} haven't assisted.
2) some clickies don't fire in certain sections eg I can't get my Necromantic Dragon Bone or my cleric BP to fire in the [Heals] section or Rage of Rolfron in the [AE] or [Burn] Sections, so I've written them into the DPS section.

Try and configure around it. Personally, (as others above have suggested) I would drop the END check

Hylander

 

[ctaylor22]

There are a few things that can keep a spell/AA/Ability from firing when you think they should. A trick to use to see if your Condition is NOT at fault is to use the Command: tag with the /beep command, and test it. Example:

DPS15=command:/beep|100|cond7

If it beeps consistently then most likely it is not the condition, but a cooldown issue.

 

[LorDeth]

There are a few things that can keep a spell/AA/Ability from firing when you think they should. A trick to use to see if your Condition is NOT at fault is to use the Command: tag with the /beep command, and test it. Example:

DPS15=command:/beep|100|cond7

If it beeps consistently then most likely it is not the condition, but a cooldown issue.

But in saying that, kiss itself checks if an item is not in cooldown before attempting to do that dps line? or do we need to add the item ready check to the condition line?

 

[ctaylor22]

You don't need to check for cooldown in your conditions, because yes kiss checks for that. Spells not firing, because of cooldowns, will give the user a false sense of condition not working or entry being skipped for no reason. The command: tag, however, does not get checked for cooldown and will fire every time.