Priority and Random Casting in HotKeyNet

[Khatovar]

Setting up priority casting - aka The Mosq2 Method - in HotKeyNet can't get much easier. Just list the keys you want to send to any window in order under your hotkey definition.

<Hotkey 2>
	<SendLabel w1>
		<Key Shift 1>
		<Key Shift 2>
		<Key Shift 3>
		<Key 2>
		<Key Shift 4>
	<SendLabel w2>
		<Key Shift 6>
		<Key 2>
		<Key Shift 1>
	<SendLabel w3>
		<Key Oem4>
		<Key 2>
		<Key Shift 1>
		<Key Shift 2>
		<Key Shift 3>
		<Key Shift 4>
		<Key Shift 5>
		<Key Shift 6>
...etc...

You can also do it using DoHotKey, which I prefer just to make things a little more organized and easy to edit, since my normal Hotkey 2 definition involves a lot of mouseover regions and stuff that makes for a lot of code to sift through.

<Hotkey 2>
	<DoHotkey Hotkey RAlt F10>
	<DoHotkey Hotkey LAlt F10>
	<DoHotkey Hotkey RCtrl F10>
	<DoHotkey Hotkey LCtrl F10>
	<DoHotkey Hotkey RShift F10>
	
//* TANK SPAM
<Hotkey RAlt F9>
	<SendLabel w1>
		<Key Shift 1>
		<Key Shift 2>
		<Key Shift 3>
		<Key 2>
		<Key Shift 4>
		<DoRandomToggle Hotkey Oemax 2>//+

//* HEALER TOGGLES				
<Hotkey LAlt F9>
	<Toggle>
		<SendLabel w2>
			<Key Shift 6>
			<Key 2>
			<Key Shift 1>
	<Toggle>
		<SendLabel w2>
			<Key Shift 6>
			<Key 2>
			<Key Shift 1>
			<DoRandomToggle Hotkey Oemax 1>

//* ENHANCEMENT SPAM
<Hotkey RCtrl F9>
	<SendLabel w3>
		<Key Oem4>
		<Key 2>
		<Key Shift 1>
		<Key Shift 2>
		<Key Shift 3>
		<Key Shift 4>
		<Key Shift 5>
		<Key Shift 6>
				
//* DK SPAM
<Hotkey LCtrl F9>
	<SendLabel w4>
		<Key Oem4>
		<Key 2>
		<Key Shift 1>
		<Key Shift 2>
		<Key Shift 3>
		<Key Shift 4>			
	

//* RET SPAM				
<Hotkey RShift F9>
	<SendLabel w5>
		<Key Oem4>
		<Key 2>
		<Key Shift 1>
		<Key Shift 2>
		<Key Shift 3>
		<Key Shift 4>
		<Key Shift 5>
		<DoRandomToggle Hotkey Oemax 3>

You'll also notice I have some DoRandomToggle's thrown in there, as well as an additional toggle in the Healer toggles. My healer is a resto shaman who uses the glyph for Riptide, which removes the cooldown so she can easily spread it around the entire party, so it works like a Priest's Renew or a Druid's Rejuv.

In order to take advantage of this, I first needed a way to spread the Riptides. I already have one tied to Unleash Weapon for my tank {Shift 6}, so I needed 4 more. I created 4 macros - 1 for each remaining party member

/castsequence [@party2] reset=3 Riptide, fred

/castsequence [@party3] reset=3 Riptide, phred

/castsequence [@party4] reset=3 Riptide, gertrude

/castsequence [@player] reset=3 Riptide, bertha

Each one has a different name used in place of null. I did this because I needed each sequence to be different. If the invalid "spell" I tried to use started with the same letter {nil, nope, nul, nah} the game still seemed to treat it as the same sequence and advanced all of them to the lockup whenever any of them were triggered, which meant they weren't spreading around and weren't resetting. But using different names makes the game think they are different macros so they only advance when they are actually used.

I then tied them to another toggle key "Oemax 3" and added a toggle to the original key just to make it so it's not always getting called.

Then I define this new modifier and key combination "Oemax 3".

<UseKeyAsModifier OemAX>

<Hotkey Oemax 1>
   <Toggle>
	<SendLabel w2>
		<Key Shift 2>
   <Toggle>
	<SendLabel w2>
		<Key Shift 3>
   <Toggle>
	<SendLabel w2>
		<Key Oem4>
   <Toggle>
	<SendLabel w2>
		<Key Oem4>
   <Toggle>
	<SendLabel w2>
		<Key Oem4>
   <Toggle>
	<SendLabel w2>
		<Key Shift 4>
   <Toggle>
	<SendLabel w2>
		<Key Shift 5>
   <Toggle>
	<SendLabel w2>
		<Key Oem4>

You'll note a lot more than the 4 toggles I'd actually need for the 4 Riptide macros {Shift 2-5}. The Oem4 key is just my assist key. I threw this in to keep her from spamming Riptide constantly. This gives a better chance of her not overwriting the Riptides and draining her mana as well as giving a chance for the reset conditional {3 seconds} in the macros to be met.

I use the same setup for my Paladin Tank with Word of Glory, so she's not constantly wasting all her Holy Power on that when she needs it for Shield of the Righteous.

/castsequence reset=3/target Word of Glory, null

<Hotkey Oemax 2>
   <Toggle>
	<SendLabel w1>
		<Key Shift 5>
   <Toggle>
	<SendLabel w1>
		<Key Oem4>
   <Toggle>
	<SendLabel w1>
		<Key Oem4>
   <Toggle>
	<SendLabel w1>
		<Key Oem4>

And for my Ret Paladin so she isn't constantly overwriting Sacred Shield

/castsequence [@party1] reset=3 Sacred Shield, null

<Hotkey Oemax 3>
   <Toggle>
	<SendLabel w5>
		<Key Shift 5>
   <Toggle>
	<SendLabel w5>
		<Key Oem4>
   <Toggle>
	<SendLabel w5>
		<Key Oem4>
   <Toggle>
	<SendLabel w5>
		<Key Oem4>

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.

[Dusl]

​Hey Khatovar,

very interesting. Definitly checking out DoRandomToggle!

But:

<SendLabel w1>
    <Key Shift 1>
    <Key Shift 2>
    <Key Shift 3>
    <Key 2>
    <Key Shift 4>

means it will send multiple keys if you click once? Aren't you afraid to violate the ToS?

Just asking since I'm very new to multiboxing and very careful at the point "one keypress, one action". For a newbie like me that seems to be very grey, if not black. Am I wrong?

[Khatovar]

There's no automation involved, it's no different than using a penny/keycap/Popsicle stick/eraser/fat fingers across your keys, or using /click multiactionbuttonblahblahblah within a macro in the game itself. The game can't and won't process any more than one action for each press. It simply processes the first thing it can and disregards the rest of the keys.

If there were delays or loops, then it would be automation and violate the rules.

[Dusl]

> fat fingers



Thanks for your reply. I just read that in Priority Casting:

> The game then processes the first thing that it can and ignores everything else. It still falls under the "One keypress, one action"

Sounds convincing!