Press Random Key?

[Zzyzxx71]

My rough input is, I'd just do something like this, from the bottom (lowest level) up:
(key 1 = Khat's priority key 1, etc.)

Priority Key 
 |---> Step 1 (reset to step 1 after X seconds; adjust to your taste)
            |---> key 1
 |---> Step 2
            |---> key 2
 |---> Step 3
            |---> key 3
 |---> Step 4
            |---> key 4

Strike key (reset to step 1 after 5 seconds)
 |---> Step 1 (do not progress to step 2 for at least 2 seconds)
            |---> strike 1
 |---> Step 2 (do not progress to step 3 for at least 1 seconds)
            |---> strike 2
 |---> Step 3 (do not progress to step 1 for at least 1 seconds)
            |---> strike 3

DPS key (pressed OR released) 
 |---> Step 1 ("reset to step 1 after 2 seconds" just so your normal first "hit" on any new encounter will be the priority ability(ies).)
            |---> Priority key
 |---> Step 2
            |---> Strike key

Considering the vagaries of ability timings, that will give you a close approximation of "random" without getting all insane with complexity, meaning it's manageable. And it "weights" the strikes toward Festering Strike. You can adjust the progress delays to tune it so it works better with your spam rate and results.

My 2 copper after a quick think, anyway.

OK just to make sure I'm understanding this correctly - make a keymap for Priority (1/2/3/4), make a keymap for Strikes, and then make a 3rd keymap that kicks off Priority+Strikes?

I've never done nesting like that, but if my understanding is correct - I'll give it a shot.

[Ughmahedhurtz]

OK just to make sure I'm understanding this correctly - make a keymap for Priority (1/2/3/4), make a keymap for Strikes, and then make a 3rd keymap that kicks off Priority+Strikes?

I've never done nesting like that, but if my understanding is correct - I'll give it a shot.

Yep. Nested step-based mapped keys. The delays can be a nightmare if you get the tuning on things wrong but if the progress delays are at the bottom levels, it won't be nearly as much trouble to tweak and won't have abstract follow-on effects outside of itself.

[Khatovar]

I would say the best option for ISBoxer is to use the strikes as steps because ISBoxer users have the option of "Do not advance for," which HotKeyNet does not. It will not choose a random strike, but it will allow you to hold on a step longer, which should accomplish about the same thing in this instance - giving you more chances for X to go off over Y or Z.

The part you quoted above for my reasoning has more to do with things like my HoTs or things like Sacred Shield, which would constantly overwrite itself and prevent me from ever getting anything else to cast. That's where this is most useful {and what is was born of}, precisely because there is no way to hold on a step in HKN. In ISBoxer, you could set up a mindless HoT key that looks like this -

Macro 1

/castsequence [@party2] reset=combat/alt Riptide, fred

In ISBoxer - Do not advance for 2 sec

Macro 2

/castsequence [@party3] reset=combat/alt Riptide, phred

In ISBoxer - Do not advance for 2 sec

/castsequence [@party4] reset=combat/alt Riptide, gertrude

In ISBoxer - Do not advance for 2 sec

/castsequence [@player] reset=combat/alt Riptide, bertha

In ISBoxer - Do not advance for 2 sec

In ISBoxer - Alt+Key to reset / Do not advance for whatever

This would let you {moreorless} throw Riptides on the whole party without repeatedly casting the same macro on the same person until you run out of mana. There's no way for me to duplicate that in HotKeyNet, thus my use of blank toggles and random.

[Zzyzxx71]

Khotavar's initial reply outlines the history of this request.

The genesis of this can be found here.

[Zzyzxx71]

I finally set it up last night - finally got to an instance where I needed to use the DK's instead of just boosting with a 90.

After tweaking, it's working like a charm. The unholy DK's are out DPSing the Blood by about 20%, the blood consistently has aggro (almost never needs heals as well), and DPS across the board is very consistent.