Quote Originally Posted by Whowantstoknow View Post
You can write Wow macros directly in ISBoxer. I believe the limit to the number of characters is 1023 same as any other macro extending addons ie Superdupermacro etc and is completely legit.

I would also look at using the new raid frames as they have been much improved though you can sort Vuhdu and Grid as well as Healbot by Name.
With regards to macros in ISBoxer, I guess I'm just really confused by the way they need to be set up through the keymaps section. I'm just completely confused because there is WAY more stuff to that macro section than I think I need.

For example, here's what I want:

I have a castsequence macro assigned to my toolbar, and when I press 1 it fires through that macro.

So, within ISBoxer, what I seem to have to do is:

1 - Create a new command on a keymap
2 - Assign that new command a hotkey (let's be easy and say it is the number 1)
3 - Go to the new key and change it's action to a "New World of Warcraft Macro Action"
4 - Select what window/s I want it to be sent to
5 - Tell it what key combination to send to wow (This is where I'm getting confused, which I will describe below)
6 - Type in the full macro.

With step 5, what's confusing is this - how exactly does this work? Do I just find an empty action bar spot and bind some keystroke combo to it (lets say ctrl+shift+alt+backspace) without dragging ANYTHING onto that hotbar in game? Then, basically, when WoW is running, if I press 1, ISBoxer actually sends c+s+a+backspace to WoW, and then... ? There's no macro assigned to that spot, there's nothing in that action bar spot, so there's no macro for it to run, at least that WoW can see, and to me that really feels like an obvious way to get banned for 3rd party software because it's clicking an empty space in the client but doing commands?

I guess I'm just completely failing to see how this translates into me being able to have a /castsequence macro that goes longer than 255 characters which is what I ultimately want to have.

Edit: Or, maybe it's just not possible to have a castsequence macro extended like that and still work?