ISBoxer Toolkit - Zero to Hero in 30 minutes Setup.

[Chilaxx]

1. You can't bind them where, exactly? You can use them as Hotkeys in ISBoxer, and the "press key combination here" box will auto-detect any key pressed on your keyboard. However, if you make a WoW Macro Action, and set the "Key Combination" as a button that WoW has assigned to your Action Bars, it will NOT be able to make the macro. If you want a WoW Macro on your action bars, you need to make it in WoW

2 and 3: As is explained on the ClickBoxer page, ClickBoxer is just a sample UI made via LavishGUI (the UI system built into IS). The section on that page titled "Learn more about LavishGUI" provides links to all of the information you might need as far as the actual XML. No, there isn't a DTD, sorry. I have 0 experience at making DTDs so if you want to give it a shot...

4. You do not press the actual FTL modifiers. By default, for example, 1 through = (or & through whatever the end of your action bar is) will FTL assist, and press the key. You just press the key as you always would, and your other guys assist. Likewise, if you wanted Shift+& to auto-assist, you would copy the same thing the other "FTL DPS keys" are doing -- a do mapped key action to do the "FTL Assist", and then a keystroke action to press Shift+&. If you do it right (by not enabling Hold or FTL on your new Mapped Key, and doing the same actions as in the example keys), then you can use any Hotkey and any other keys, and never have to worry about the actual FTL. You can just assume that by using a Do Mapped Key Action to do FTL Assist, it is going to assist your character, and so on. That is, unless one or more of the 3 keys that implements the FTL (these are FTL Follow, FTL Target, and FTL Assist) is having a problem.

Thx a lot for the reply m8!

- The thing with my keyboard, i'll try it some more this evening, hope i get it working, if not, i'll make my macro's in WoW for my 1->9 buttons. Thx for the explanation :-)

- Also sry that I missed the "LavishGUI" section at the bottom, kinda missed the obvious there . I might be able to make a DTD when I get the time for it, but if I do, it would be nice to know if this is something that'll be still usable when your next gen app is coming out ;-) if not, don't think i'll bother

- And also thx a lot for the explanation about how FTL exactly works, i think i fully understand now! And i'm gonna try it out for sure!

- Thx for the twitter link, it's nice to watch your progress :-)

- Btw, what are you gonna use as frontend? You said it's gonna be next gen so... WPF?
(if so, if you got any question, i can help , ok sry, i'm just fishing for spoilers now )

Keep up the good work!


Ciao

[moosejaw]

Lax, I found a keymap behavior last night that was unusual and I am not sure if it is intended.

The FTL dps keymaps all use the assist {FTL} keymap reference prior to firing the 1 through = keys. This resolves perfectly and I love it. But when I turned on the global "hold down keys when key is pressed" flag for the general map (for movement key entries I made) the assist stopped functioning for FTL DPS assist.

Unchecking the keypress flag and checking it on each movement key was my fix. Is this intended? It certainly explains why my previous efforts to duplicate this function wouldn't work.

I guess I should segregate the movement keys out to their own keymap anyway to keep things clean.

Thanks for the hard work!!

[Lax]

Unchecking the keypress flag and checking it on each movement key was my fix. Is this intended?

Not "intended" no, but not something easily fixed in the current platform. The next-gen software in development has this issue properly handled

[burningforce]

The next-gen software in development has this issue properly handled

oh do tell

sounds interesting

[Lax]

It's in development, and I'm not announcing the features yet.. There's some exciting new stuff though

I am hoping to have an internal alpha operational soon but it's been pushed back by adding Aion support (which is also coming for ISBoxer). The back end is basically ready to support all of the features anyone has dreamed of, and now we're getting started on the front end. I use Twitter to provide progress updates on the software, so if you want to see how it's been going and what I'm working on you can see https://twitter.com/LaxLacks. My Twitter followers tell me they always hated the idea of Twitter because they don't care about Ashton Kutcher etc, but my feed doesn't involve my personal life, and I post information they actually want to see.

When the new software comes out, current subscribers will not need to make a new purchase to upgrade (so there's no "penalty"), and they can just continue to use what they were already using if they want (ISBoxer will continue to be supported too).

[burningforce]

awesome lax, thanks for the twitter link, looking forward to updates

[Lax]

- Btw, what are you gonna use as frontend? You said it's gonna be next gen so... WPF?
(if so, if you got any question, i can help , ok sry, i'm just fishing for spoilers now )

Yes, it is currently being developed with WPF, and should look and feel absolutely beautiful compared to the ISBoxer interface (which, while functional, is not the prettiest, and not always the easiest to follow )

[Jheusse]

Really looking forward to the new version/interface. The existing interface I'd make an analogy to HP calculators with their RPN style calculation entry compared to traditional. Very powerful, very flexible, and you can make an argument that it's superior in function, but it can be really hard to grasp and can take significant time to train your brain to work that way intuitively.

It's been a very slow slog for me to embrace the existing interface, as much by lack of time as by lack of brains, but I'll be interested to see the new interface. The wizards and quick starts and videos have brought ISBoxer from "oh no way, don't even think about it unless you're a coder yourself" to "It's a little tricky but even a layman can handle the basics". It's only a little further in layout and interface to where the light bulb goes on for halfwits like me.

[Chilaxx]

It took me 3 evenings to finally get something going where I was really proud of.
Some stuff that got me frustrated was that apparently my FTL modifiers weren't recognized.. only 3 of the 6 are usable for me. Tbh, this isn't a real problem for me, but it was hard to find out.. I'm a programmer myself, so it's a bit easier for me to find my own bugs

But tbh, lax has done a fantastic job with isboxer, the only sad thing i can think about is that i didn't use it right away when i started boxing! The program is super, but that's not all imo..
You also get great support: irc / forum / the thing where you can post your config in (don't remember the name)
And also, you know he's a great developer, and that he keeps developing isboxer.

Those were 2 of the things that made the switch to isboxer a no-brainer for me!

Just wanted to post my findings ^^


Ciao!

[Seldum]

Thanks for a great Original Post. It was really helpfull in getting started.

I have previously used keyclone and Jamba but im trying ISboxer and innerspace out.

Im struggeling with understanding the FTL system build in into ISboxer, but ill read a bit more and hopefully figure it out.

My current question is how you guys use the repeater. Im use to keyclone where all my keystroke gets repeted on the slaves. I know I can enable this in Isboxer, but I think I wont because it also has some draw backs.

Atm im configuring the F-keys to be repeated on my slaves... but I would also need to setup fx. Shift+F1 seperately if I need this combination repeated....

My question is, do you guys specify all combination you need in ISboxer under keymaps or do you toggle repeater on and off as needed?

My All druid team is only lvl 54 so I don't have alot of instance experience, yet, and therefore not a very sophisticated setup for now.

*EDIT: Poor language.