Question - Keeping clicky item buffs up

[nebulous]

I have a couple clicky haste items in my crew that I'd like for them to click when the buff drops. I'm not sure how to adjust the buff entry to do this. I have tried the name of the spell and the item names with no lucky. I'm not seeing a specific explanation for this in the guide. Can anyone advise me on how to adjust my settings for this?

The item in question is the Lizardscale Plated Girdle: http://everquest.allakhazam.com/db/item.html?item=28461

 

[Meistro]

As I see it, it SHOULD just be in KA

Buffs1=Lizardscale Plated Girdle

but you could try

Buffs1=Lizardscale Plated Girdle|ME
or
Buffs1=Lizardscale Plated Girdle|Dual|Twitching Speed

BUT if that doesn't work you could try it in a down in your MQ2Melee ini (servername_toonname.ini):

downflag1=1
downshit1=/if (!${Me.CombatState.Equal[COMBAT]} && !${Me.Buff[Twitching Speed].ID} && ${Cast.Ready[Lizardscale Plated Girdle]} && !${Me.Moving} && !${Me.Invis} && !${Me.Sitting}) /casting "Lizardscale Plated Girdle"|Item

 

[nebulous]

Excellent. I'll try that when I get home.

 

[Rustycat]

What Meistro said!

 

[Incognito]

Using the Dual switch in KA is bloody brilliant, it has solved me some problems. Kudos for adding that Maskoi!

 

[Wink-]

As I see it, it SHOULD just be in KA

Buffs1=Lizardscale Plated Girdle

but you could try

Buffs1=Lizardscale Plated Girdle|ME
or
Buffs1=Lizardscale Plated Girdle|Dual|Twitching Speed

BUT if that doesn't work you could try it in a down in your MQ2Melee ini (servername_toonname.ini):

downflag1=1
downshit1=/if (!${Me.CombatState.Equal[COMBAT]} && !${Me.Buff[Twitching Speed].ID} && ${Cast.Ready[Lizardscale Plated Girdle]} && !${Me.Moving} && !${Me.Invis} && !${Me.Sitting}) /casting "Lizardscale Plated Girdle"|Item

I don't mean to sidetrack this thread, but do you really need the !${Me.CombatState.Equal[COMBAT]} in a downshit? Will downs fire at all if you are in combat?

 

[Inkie]

I don't mean to sidetrack this thread, but do you really need the !${Me.CombatState.Equal[COMBAT]} in a downshit? Will downs fire at all if you are in combat?

Holyshit will only fire in melee combat,
Downshit can be configured to fire anytime and I'm 99% sure that includes melee combat but haven't tested that specific piece.
Downshit will fire if not in melee combat.

typically:
holyshit for melee toons for things to do in a figh
downshit with ${Me.CombatState.Equal[COMBAT]} for casters to do things during a fight
downshit with !${Me.CombatState... etc.} to do while not in a fight.

 

[Meistro]

I don't mean to sidetrack this thread, but do you really need the !${Me.CombatState.Equal[COMBAT]} in a downshit? Will downs fire at all if you are in combat?

yes downs will fire as long as you are not in melee combat, so they can be set to fire in both combat and non combat situations. So say most casters would put their combat shits and non-combat shits both as downs so that denotation can be critical to make sure they fire at the correct times.

 

[nebulous]

As I see it, it SHOULD just be in KA

Buffs1=Lizardscale Plated Girdle

Don't know why, but now this works. Didn't require anything special. Thanks for the help!

 

[spudz90]

I'm trying to do this with my zerker epic, how can it be done? I would like to click it during a fight. I have no clue how to do anything in holy/down shit.

 

[Incognito]

If you want to do it manually, just set a hotkey with: /useitem NameOfZerkerEpicClickyEffect

You can use /casting as well but in another thread EQMule reminded us of the /useitem cmd and it takes partial names. In the case of /useitem you can just use the (partial) name of the item without having to know the name of the clicky effect itself. Some experimenting may be required...

- - - Updated - - -

I don't mean to sidetrack this thread, but do you really need the !${Me.CombatState.Equal[COMBAT]} in a downshit? Will downs fire at all if you are in combat?

There is overlap on timing. I am just getting around to learning/experimenting with downs and holys, but the first thing I noticed is that the checks fire often, like every second, perhaps not quite as fast as HUD code (which might be 6 times a second), so there are 10's of fires/checks between mode switching (combat VS noncombat). Not to mention any additional delays caused by macro lag (i.e. Kissassist). As such, I will always put my own checks in there.

To prove my point, simply make an error in the code and see how fast the scroll buffer fills up even AFTER your mode has changed.