Innerspace & RDX: Click Healing Demo

[zanthor]

Full video posted over here.... ('http://www.wemultibox.com/blogs/zanthor/innerspace-rdx-or-how-i-click-and-heal')

[PyrostasisTDK]

Whats RDX? Isnt that like a pay mod?

[zanthor]

Used to be... now it's http://www.openrdx.com/.

[SpruceGoose]

"OpenRDX is an open source version of RDX"

Describing a word with itself is nothing short of epic failure. I've poked around the "OpenRDX" forums for a bit not and I can find nothing describing what it is or what it does - other than the original RDX was "pay for" software.

Zanthor, help us out - WTF is it!?!?! :P :P

I used to use RDX5 pre-BC, back then it was one of the best add-ons I'd seen for managing a raid. It had several key features rolled into one slick add-on. It had terrific boss mods. The main bar for RDX with the timer and little icons would display the boss mob's health, and the timer would start when the boss was engaged. It gave great warnings and would broadcast them to the raid; pretty standard fare now, but back then RDX had the best implementation of boss mods imo.

It also allowed you to set up customized groupings of health and/or mana bars for raid members. Your druids might have had a small window showing all healer mana so they could easily see who needed an innervate, or a list of dead players they could reference for combat rez. You could also set up main tank windows, and there was a nice auto assist function that made assigning tank targets very easy. The level of customization in these group windows was great, and you could create different set-ups for different encounters. You could also create windows to watch for the presence or absence of certain buffs/debuffs. In general it made raid leading much smoother and made a lot of information available in a completely customized format.

RDX also had wonderful logs for delving into what happened in a raid and why. You could set it up to watch for certain events, or see what occurred in a period of time before a tank died. Before the advent of wow web stats, RDX was one of the best tools for getting your head around the reason why your raid group got destroyed, and devising new strategies to improve.

I don't know the entire background behind what happened with RDX, but my understanding is that it was never meant to be distributed, and had code obfuscation to prevent this. Some guild drama, or something and the thing got leaked. Once the cat was out of the bag and people began raving about it, the author decided to make the next version a pay add-on, with tons of new features. I never used RDX6, but followed the forums, and there were all kinds of crazy new things, a wipe board where you could place icons and draw diagrams the whole raid could see to map out an encounter, and lots of other stuff I don't remember now. Unfortunately RDX6, in addition to costing money, seemed much more complicated and that it was trying to do everything all in one add-on. The author quit wow and until I saw this post I had believed the add-on had died. It's nice to see a group has kept it alive with an open version, but unless I'm missing something it seems like there are a ton of other add-ons which each do pieces of what RDX does much better with no need to learn the complex configuration of RDX.

[zanthor]

RDX stood for Raid Data Exchange. Originally it was a CTRaid replacement + CTBossmods all rolled into one. It had the ability to modify bossmods on the fly and the ability to send them to other raiders in game without the need to have them go download something new. So you are pushing content, a boss has a ZOMGPOUNDYOURASS skill and the programmer would write it up to warn everyone and push it to the raid.

Why is it not documented well? Because the guy who wrote it was the ONLY guy/guild using it for a LONG time. Eventually this leaked, a few chosen friends got into using it, and of course eventually it bled out to the mass public. RDX5 Conquest was leaked, this wasn't the core version but the version Conquest was using, I picked up that leaked copy and maintained my own guilds version for about a year before RDX6 went into public Beta (payed mod) and I signed up for that almost immediately.

The core RDX is very much like InnerSpace - it is a platform. InnerSpace by it's self doesn't do anything, it just sits there and you look at it, and it looks at you. Once you get to know each other you can do amazing things with it. RDX is just that, it's a platform that allows you to build bossmods, unit frames, raid frames, logistical data, etc. And it allows you to sync all this across the raid quite easily if everyone runs it. I started using it for raiding, I still use it because I can update my unitframes mod and push it out to my other 4 shamans and they ALL have the same setup, guaranteed.

A great place to start for an RDX Noob would be here

http://www.wowinterface.com/portal.php?id=478 - the base page. Good info, links to other pages.
http://www.wowinterface.com/downloads/cat115.html - downloads page - packages listed here.

From the package page you check OOBE packages, this is "out of box experience" which is basically a bunch of work done for you already. I use the OpenRDX: Brethren RaidFrames ('http://www.wowinterface.com/downloads/info11137-OpenRDXBrethrenRaidFrames.html') package because it's solid, well documented, and flexible.

[tinit5190]

I would love to do this. However, I have some questions. I am running
all 5 versions of WoW on the same PC, but monitors have different
resolutions. So my questions are kinda bundled up into two parts.

1. Can I do this?

2. Would I have to do one of the two things.

a) Make both monitors same size.

b) Place the healer WoW client behind the main client?

[zanthor]

I would love to do this. However, I have some questions. I am running
all 5 versions of WoW on the same PC, but monitors have different
resolutions. So my questions are kinda bundled up into two parts.

1. Can I do this?

2. Would I have to do one of the two things.

a) Make both monitors same size.

b) Place the healer WoW client behind the main client?I run 5 copies of wow on the same PC as well. Two monitors, you only see one here because that's all FRAPS records.

Using Innerspace I run all 5 copies @ 1680x1050 and it scales the non-active ones down to thumbnail sized bits on the other monitor. I can see them, and PIP is so absurdly fast I don't need to interact with them as thumbnails.

What makes this work for healing is I use the same UI layout including unit sorting on all 5 clients, so by binding keys to send the mouseclicks to the specific window I can heal from my 5th shaman while driving any of the others.

[Zerocool2024]

From what I’m getting. You use RDX (The boxes in the middle of the screen) and have IS tell the 5th shaman to heal when you have (1, 2, 3, 4, or whoever is leading the group at the time) to heal when the said leader “clicks” the RDX Square (the person you are wanting to heal) and it sends that information to the 5th to press (in my case, ctrl+1) to heal player1.

It just seems, that if I were to open up RDX the same way across the board, and not bind any keys to the boxes for healing (but only for the 5th toon) how do I script IS to make the 5th press heal upon my click?

If you don’t mind, could you paste some of the script, or whatever coding you did so I could see it better. I understand what you did, just, it seems like I’m missing something…

[tinit5190]

Thanks for the speedy reply. Now all I have to do is ding 60, so I can begin the long grueling process of setting this up...

Oh, and wow, Blackhand. That was my home-server. I knew I remembered the name Zanthor from somewhere.

[tinit5190]

So I am attempting again to get the click through IS to work. What I have done is I have opened up the zbinds.iss file and pasted:


/* Bind for click healing with is5. */
bind zb_Heals_L G10 relay is5 "mouseto \${Mouse};mouseclick left"
bind zb_Heals_R G11 relay is5 "mouseto \${Mouse};mouseclick right"


Right below



/* Bind for AE - Send click to mousebutton.*/
bind zb_sendLeftToCoords G8 relay all"mouseto \${Mouse};mouseclick left"
bind zb_sendRightToCoords G9 relay all "mouseto \${Mouse};mouseclick right"


Is this in the wrong spot or something? Because when I go onto my main, enable mouse and keys, it doesn't work?
Do I need something in one of the other files?

[Zerocool2024]

So I am attempting again to get the click through IS to work. What I have done is I have opened up the zbinds.iss file and pasted:


/* Bind for click healing with is5. */
bind zb_Heals_L G10 relay is5 "mouseto \${Mouse};mouseclick left"
bind zb_Heals_R G11 relay is5 "mouseto \${Mouse};mouseclick right"


Right below



/* Bind for AE - Send click to mousebutton.*/
bind zb_sendLeftToCoords G8 relay all"mouseto \${Mouse};mouseclick left"
bind zb_sendRightToCoords G9 relay all "mouseto \${Mouse};mouseclick right"


Is this in the wrong spot or something? Because when I go onto my main, enable mouse and keys, it doesn't work?
Do I need something in one of the other files?Alright, so your saying that I tell IS to bind Left and right click (mouse) to a button on the last toon to heal?
Then with RDX I make the same window with left and right clicks on all toons, so that when I am on my main or 2, 3, 4 and I click to heal who ever I click (RDX Frame) it transmit to the last toon to heal?

[tinit5190]

@Zerocool2024

I gave up on that. What I did, was I changed the AoE button to G12. That is:

bind zb_sendLeftToCoords G8 relay all "mouseto \${Mouse};mouseclick left"
is now:

bind zb_sendLeftToCoords G12 relay is5 "mouseto \${Mouse};mouseclick left"

Then I simply hover my mouse over where I want the mouse to be on the hidden screen, and click G12. Works awesome with the way I have RDX set-up.
I made it so there are 4 buttons beside each name, that being the 4 sham healing spells, in which that target is the player to the right of the button. So all I have to do is mouse over and "1-click" heal anyone. Clean, simple, and quick.
It's a modification on Zanthor's method. I also have "Show Heal" enabled in RDX, so I can see who is getting healed with a green bar. This makes it so my heals can be really quick and extremely responsive. No second guessing on whether or not I targeted someone.

[Zerocool2024]

@Zerocool2024

I gave up on that. What I did, was I changed the AoE button to G12. That is:

bind zb_sendLeftToCoords G8 relay all "mouseto \${Mouse};mouseclick left"
is now:

bind zb_sendLeftToCoords G12 relay is5 "mouseto \${Mouse};mouseclick left"

Then I simply hover my mouse over where I want the mouse to be on the hidden screen, and click G12. Works awesome with the way I have RDX set-up.
I made it so there are 4 buttons beside each name, that being the 4 sham healing spells, in which that target is the player to the right of the button. So all I have to do is mouse over and "1-click" heal anyone. Clean, simple, and quick.
It's a modification on Zanthor's method. I also have "Show Heal" enabled in RDX, so I can see who is getting healed with a green bar. This makes it so my heals can be really quick and extremely responsive. No second guessing on whether or not I targeted someone.(Press) = keyboard
(Click) = Mouse
Ok ok, I think I'm getting it. Still learning the Lingo for IS.

I don't use that keyboard, so I have to change the G#'s to something else, lets for my sake, say:
bind zb_sendLeftToCoords ctrl+shift+1 relay is5 "mouseto \${Mouse};mouseclick left"

So now on my 5th Shaman, I set up RDX the same way on all screens and Bind ctrl+shift+1 to one of the RDX boxes labled... party1 or whatever.
Now when I am on any of the 4 other toons (not the healer) I can click that button it will tell the 5 to heal that person?

Sorry, more of a (movie/pics/visual) person... Or at some point I will be doing something that has nothing to do with this and it will just CLICK and I will be like *OHWTF* thats so simple, lol.

[tinit5190]

You are over thinking. IS sends the mouse-click to that session. It "left clicks" the mouse on that screen where you mouse currently is.
There is no binding needed on the healers UI. Everything just has to be set up the same.

[Zerocool2024]

Lol I probably am... I do that from time to time. Alright, when I get back to my Shamans, I will take it for a whirl and see what happens.

Thanks.

[Darm]

All of Zanthor's discussion about RDX drew my interest awhile back when he first wrote about it, and I finally had some free time to try this out.

I think Brethren raid frames manages to make the nearly overwhelming amount of customizing options that come with RDX into a more manageable size. Or at least, it's a litle easier to comprehend for a beginner like myself.

Anyway, after an afternoon of asking incredibly patient Lax all kinds of questions in IRC, I got this click healing business up and running. I run one instance on my main PC, and 4 "slaves" on a second PC. Through the magic of IS, I can click on a raidframe and that healer gets healed. It is very cool, although perhaps not a big change in funcitonality from clickboxer, but it looks pretty awesome.

I do have one question -- for Zanthor or perhaps if someone else out there has some expertise with Brethren raid frames. I am struggling to figure out how to change the font color of the name's in the raid frame. I'm using the GridWide setup, and it is defaulting to use the same color as the health bar, which is colored by class. This can make it a little hard to read (e.g. for a priest their name is white text on a white background). I think there is a "custom text" that is associated with a raidframes: script_gridwidetext, but changing that doesn't seem to make any difference, or perhaps Im barking up the wrong tree. Any help here would be greatly appreciated.

I'll also mention a few things in case anyone else is contemplating trying this and perhaps they can be spared duplicating my errors:

- Make sure you are starting with recent installations of both ISBoxer and IS on both the main PCs and any slave PCs. This might sound obvious, particularly since this software updates itself, but in my case, I had some old repeater files in there from way back in the day on one of my machines, and this really threw a wrench in things.

- Hardware cursor should be checked ON for all machines

- Clicking the option "desired rendering size" in the Windows Layout Option and selecting (or entering) the same size as the window which you are using as the master is probably a good idea, and seems to give the most intuitive mouse replicating behavior, in my opinion. It will still work if this option isn't checked, but depending on how your windows layout is setup, there will be an area that will be very difficulty if not impossible for your duplicated mouse to actually click.