Build 21 and the current state of the project

[Fursphere]

Originally Posted by Freddie
I'd like to do DNP next but for technical reasons there are three pre-requisites that have to be done first. Here's the schedule for the next couple of weeks:

1. Rewrite the underlying data structures for config info.

2. Finish "launch WoW" because DNP and choosing particular output key combinations for particular WoWs is the same code, and I can't write it unless the program can identify particular WoWs, and its method for doing that will be launch.

3. Make a spreadsheet kind of control that will be used for the DNP/key-assignment screen.

4. Write the DNP/key-assignment screen.

This is where the project currently stands.

[Freddie]

I wrote that after asking everybody which features I should do first.

It only shows the plan for the next few builds. There's lots of other stuff that's planned, half written under the hood, etc.

[thinus]

My personal requirements for bare bones functionality are:

• Mute key broadcasting
• Full key broadcasting
• Limited key broadcasting (DNP list or something similar)
• Window configuration

My perspective is a single boxer perspective so I could care less about communication across machines and the synchronization issues related to it as I don't really see myself running more than 1 instance of Mojo.

Limited key broadcasting is crucial as well. If I remember correctly WoW now stores keybindings and macros server side so unbinding movement keys on alts is something I prefer not to do as I sometimes run those characters solo or switch to "driving" from another window which leads into the next point.

Window configuration: WoW allows us to set where and how the WoW windows are drawn. Being able to pre-configure a desired layout and setup folders where to launch WoW from is crucial. Swapping your main window with an alternate window via hotkeys is also a highly desirable feature.

[Moorea]

The first 2 already exist, but I agree about the next 2 (which is what you can see there) under DNP and Maximizer names; the only difference is I also put "mouse click broadcasting" in the top 4

My personal requirements for bare bones functionality are:

• Mute key broadcasting
• Full key broadcasting
• Limited key broadcasting (DNP list or something similar)
• Window configuration

My perspective is a single boxer perspective so I could care less about communication across machines and the synchronization issues related to it as I don't really see myself running more than 1 instance of Mojo.

Limited key broadcasting is crucial as well. If I remember correctly WoW now stores keybindings and macros server side so unbinding movement keys on alts is something I prefer not to do as I sometimes run those characters solo or switch to "driving" from another window which leads into the next point.

Window configuration: WoW allows us to set where and how the WoW windows are drawn. Being able to pre-configure a desired layout and setup folders where to launch WoW from is crucial. Swapping your main window with an alternate window via hotkeys is also a highly desirable feature.

[Freddie]

This is the last suggestion for the entry window from the other thread. Any comments?

[Svpernova09]

This is the last suggestion for the entry window from the other thread. Any comments?

Is there any way to specify a character (as opposed to a WoW) It has always been easier for me to think in terms of what keys I'm sending which toon, not always which WoW. Maybe I'm just odd

[Zappy]

One feature I love with Keyclone is the ability to round robin a keystroke, but there are several scenarios on which this could be improved greatly.

I arena with my 5 shammys by swapping them around with a dedicated healer, and keyclone has the option to mute a specific clone. Unfortunately ISBoxer doesn't have this, and I don't like the idea of one of my guys running around the arena master while doing arenas. A funny story along those lines was one of the first times I did arenas before I knew how to mute a specific clone, I was queuing up in thunderbluff. About half way through the match, one of my guys died in the heat of battle, and I couldn't tell if I was lagging or not. It turns out, that my clone sitting in thunderbluff comitted suicide by jumping off the plateau.

Back to topic.. this works well for doing arenas and being able to swap toons in and out. The problem is that keyclone is buggy to where I'm pressing a round robin key when one of the clones is muted, the keystroke gets entirely ignored. The end result is that I'll sometimes spam the key a few times to make sure it goes off (thunderstorm, warstomp, etc) and ending up wasting one of them.

Another scenario would save a macro slot on mixed classes. Say you have the DK/ret makeup, and you want to round robin hammer of justice. Currently, you'd have to use a /castsequence macro to do it, as a round robin keystroke would not fire for the DK.

In short, a cool feature would be to have a round robin keystroke that could be mapped to only fire to specific wow target windows.

[Moorea]

the reverse argument is: use jamba for per character/team differences and setup the boxing simply so you don't have to reset up anything when the character change - for me I just need the current window to get all keys and other windows to get all but some keys (WASD) - but maybe an idea that works for everybody is after you got a setting you like; you can name that setting when you save it - and then you're free to name it by a toon name instead of "wow1" so when you reuse/recall it it means something to you ?

[Fursphere]

I tend to agree with Moorea's line of thinking here - but everyone is different in how they setup / run their teams.

So some level of flexibility would be ideal.

[Fursphere]

To get this topic rolling again...

I think things should be as generic as possible. Jamba is not a good example as 1) Blizzard could actively kill the project if they choose. And if you even try to give me a counter argument to that, i'm going to ask you why they actively break mods every patch for no obvious reason other than keeping mod authors busy. 2) WoW changes. A lot. So whatever tools we use should be so generic that they are easily adapted to whatever is thrown at us next. (IWT comes to mind - this is a great addition to WoW - but if its removed, we need to adapt).

How's the next version coming Freddie?