Press Random Key?

I've posted this query elsewhere, but wanted to make sure I was thorough.

Khotovar's DK rotation configuration (he uses HotKeyNet) sends 4 keys in a priority (for this example lets say 1,2,3,4) and then one of any of 3 OTHER keys (say 5, 6 or 7). So essentially it's sending 1/2/3/4+5 OR 6 OR 7. Hotkeynet apparently has the ability to send a random key selected from a preconfigured pool of keys (in this example 5,6 or 7).

Anyone have any ideas/recommendations on how to duplicate this configuration in ISBoxer?

Thanks in advance.

Can't find the thread where you refer to Khatovar's setup sending a random key in {5, 6, 7}. Link that and we may be able to provide some insight. Between myself, Mirai and a few others, we're doing some pretty involved stuff with steps/etc.

Quote:

---

Originally Posted by Zzyzxx71

Khotovar's DK rotation configuration (he uses HotKeyNet)

---

I'm a She. ;)

Quote:

---

sends 4 keys in a priority (for this example lets say 1,2,3,4) and then one of any of 3 OTHER keys (say 5, 6 or 7). So essentially it's sending 1/2/3/4+5 OR 6 OR 7.

---

Just want to clarify this for everyone - All the keys are sent at the same time {1-4+5 or 6 or 7}. The "and then" might make some think it's 1-4 and after those are sent, it sends another random key.

Quote:

---

Originally Posted by Ughmahedhurtz

Can't find the thread where you refer to Khatovar's setup sending a random key in {5, 6, 7}. Link that and we may be able to provide some insight. Between myself, Mirai and a few others, we're doing some pretty involved stuff with steps/etc.

---

This is the thread where I was discussing my setup with Zzyzxx71.
http://www.dual-boxing.com/threads/5...iew-Post-6-0-2

This is the original macro thread
http://www.dual-boxing.com/threads/4...ee-Macros-MMMM

This is the configuration for randomized casting in HKN
http://www.dual-boxing.com/threads/4...g-in-HotKeyNet

Edit: Her post outlining his configuration can be found here.

Edit: She utilizes a function within AutoHotKey titled "DoRandomToggle" - In one of her posts she's linked to the following post titled "Priority and Random Casting in HotKeyNet".

Additional edit: By "And Then" my intention was more to communicate "in addition with". Not an extra step, but 1,2,3,4 AND (5 or 6 or 7).

Apologies if I misrepresented the procedure.

If you want to send multiple keys then just add more Keystroke Actions to that particular Step of your Mapped Key.

Quote:

---

Originally Posted by MiRai

If you want to send multiple keys then just add more Keystroke Actions to that particular Step of your Mapped Key.

---

Understood, that's not the problem though. The issue is sending a random key using ISBoxer.

The 1/2/3/4 is figured out - it's the 5 OR 6 OR 7 that has me stumped. :)

I guess I don't understand why it has to be random and what benefit there is to it being random?

She outlined her thought process in a prior post:

"As to why I use DoRandomToggle instead of just DoHotKey or just adding a bunch of toggles into the original hotkey, I wanted it to be a chance for the spells to go off, not something that is always going to go off. This gives me a better chance of things going off only if there's nothing else to do and only on occasion."

I suppose I'm not trying to really understand it, I just want to duplicate it. That, and this appears to be a challenge as far as ISBoxer configuration.

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.)

Code:

---

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.

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

Code:

---

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

---

In ISBoxer - Do not advance for 2 sec

Macro 2

Code:

---

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

---

In ISBoxer - Do not advance for 2 sec

Code:

---

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

---

In ISBoxer - Do not advance for 2 sec

Code:

---

/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.

Quote:

---

Originally Posted by Ughmahedhurtz

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.)

Code:

---

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.

Quote:

---

Originally Posted by Zzyzxx71

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.

What spell is it and why do you only sometimes want it to go off? Perhaps we can address the spirit of the problem if not this specific solution.

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

The genesis of this can be found here.

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.