Since I don’t have a G15 keyboard to make use of the lights for repeater on/off state. I decided to tweak Zanthor’s old repeater UI he included in his first IS Scripts compilation, so original credits to him for the UI, I just did a few tweaks to incorporate keymap toggle, and ISBoxer Config reload.

repeater.xml (Right click, save as repeater.xml to InnerSpace\Interface)

What does it do?

• Toggle Repeater on / off
• Toggle Specified Keymap
• Reload ISBoxer Settings

Toggle Repeater

Repeater Disabled, Keymap Active

Repeater Disabled, Keymap Disabled

In your repeater profile, if have the startup defaults “key repeat enabled” checked, you’ll need to click the keys button once, then it will catch up and show the correct state. *Keys* should indicated repeating is enabled, Keys will indicate it is disabled. My repeater profile does not have this checked so the Keys button is already at the correct state.

Keymap Toggle

This is setup to toggle a keymap named Base. You can change the name of the keymap you want to toggle on line 37 of repeater.xml “relay all keymapper -togglemap Base” Just replace Base with whichever keymap you want the button to toggle.

Modifying keymapper.iss To Change the button text.

In order to get the Maps Text to indicate the current state of keymaps, we need to change the text on the button when the keymap is toggled.

Open InnerSpace\Scripts\keymapper.iss

Scroll down to line ~387 (or find “method ToggleKeyMap(string name)”)

This is what you should find:

method ToggleKeyMap(string name)
{
if ${LoadedMaps.Contains["${name.Escape}"]}
This:UnloadKeyMap["${name.Escape}"]
else
This:LoadKeyMap["${name.Escape}"]
}

This is what you want to replace it with:

method ToggleKeyMap(string name)
{
if ${LoadedMaps.Contains["${name.Escape}"]}
{
UIElement[keymaptoggle@main@repeater]:SetText["Maps"]
This:UnloadKeyMap["${name.Escape}"]
}
else
{
This:LoadKeyMap["${name.Escape}"]
UIElement[keymaptoggle@main@repeater]:SetText["*Maps*"]
}
}

Save and reload your ISBoxer config (or launch your character set). Open the IS Console (Default ~ key) and type “ui -reload repeater.xml”. You should see the ISBoxer Controls UI show up as in this image (You may not have the WoWSkin loaded, but it’s not required)

Reload

This simply sends a “relay all run isboxer -reload” to reload your ISBoxer Configuration just like the ISBoxer ingame GUI does. I threw this command so i wouldn’t have to open the ISBoxer gui just to reload.

Thanks to Lax and Red-One for answering all my questions in #isboxer.

I hate this place. The first boss took 3 tries but I got him. I pretty much moved in and out of range to catch heals when I needed them and that seemed to work well. Died a couple times to trash, I had no real recovery method if my tank or healer got possessed. I ended up making a macro on the tank that tried to target one of the possessors so I could find them quickly and shut them down.
First boss

Second Boss

Cleared Mana Tombs! No problems at all. I thought the last boss was going to be tough but turned out to be nothing major.
First boss

Second Boss

Third Boss

Cleared The Underbog! Only had 1 death due to not paying attention. I ended up aggroing The Black Stalker before I was ready so the preist didn’t make it. I’m still swapping around spells. I’m not very good with a Shadow Priest. I also realized when I dinged on the 3 lowbies, and went to train, I hadn’t trained Mind Flay at all. Oh well, should see a nice boost next instance. Planning on doing some questing in Zangarmarsh. The lowbies are just over their current levels so I want to get another level maybe before I head into Mana Tombs.

First boss

Second Boss

Third Boss

Fourth Boss

Cleared The Slave Pens with no deaths! ClickBoxer makes healing a non issue. I’m still not using a secondary targeting mechanism for heals. I’m just using a /tar party1. I need to make a macro so I can single target heal a party member.

First boss

Second Boss

Third Boss

I started out with a horizontal ClickBoxer window and after a couple runs it just seemed too small. My idea was to make a vertical window that replaced (or in place of) the right 2 action bars of the default UI and make the buttons bigger.

Here is what I started with:

Here is the Vertical version using 40×40 for button size:

This is all pretty basic stuff. All of the buttons are the same, some of the text is different. I’m mainly posting this to show what can be (easily) done with ClickBoxer. Once I got the vertical layout, I thought, well maybe I should add the flexibility of using either layout. So set each layout as its own window and with some help from the #isboxer crew, I got it all working. I took it a step further and instead of having to run “ui -reload -skin WoWSkin clickboxer vertical” I put that line it it’s own script so I can just run “run vertical” or “run horizontal” for whichever orientation I want.

Vertical Script (Save as vertical.iss to C:\Program Files\InnerSpace\Scripts)
function main()
{
ui -reload -skin WoWSkin clickboxer vertical
}
Horizontal Script (Save as horizontal.iss to C:\Program Files\InnerSpace\Scripts)
function main()
{
ui -reload -skin WoWSkin clickboxer horizontal
}

Here is the full Clickboxer.xml (Save to C:\Program Files\InnerSpace\Interface)
ClickBoxer.xml (Opens new Window) – Saved here as txt for display purposes.

There is a Misc window there that is the building blocks of another window.

About my Clickboxer.xml:
I run 1 system with 3 clients and 1 system with 2. This is why you see “joeslaptop.is1″; this is relaying commands directly to the RemoteUplink joeslaptop (my 2nd system) is1 session. This is not necessarily something you can drop in and just run. Unless you also run your resto druid on is2, your shaman on is3, and your preist on joeslaptop.is1. The idea here was to document the process for myself and show by example how easy it is to build a custom ClickBoxer UI.