Build 21 and the current state of the project

[Mukade]

I'll give an example to support your argument;

Outfitter used to be able to swap weapons when you changed stance (for warriors who need to switch between a 2 hander or swrd + shield, or rogues who need a dagger in their main hand to use certain abilities while stealthed). 3.3 changed it so addons can't change weapons.

You can still do it with /equip macros, but it's such a PITA having to update them every time you get a new weapon, compared to just updating outfitter.

I don't know why Blizzard made that change, it just seems petty, and may have something to do with promoting their own equipment manager (which is lacking that feature at present).

Jamba is amazing, but it's an addon and therefore is far too tied into the game. I think as much potential to mess things up as is possible, should be taken out of Blizzards hands, as they don't seem to give a damn about addon makers, or even players, and seem to love making changes for change's sake just to massage their own egos (Yes after 2 years playing I'm really beginning to hate the developers, but I've rarely seen them fix anything without breaking something else that was fine in the process. Meanwhile the game is littered with the kind of bugs that take a matter of seconds to fix, many years old now).

[TheFallenOne]

I'll give an example to support your argument;

Outfitter used to be able to swap weapons when you changed stance (for warriors who need to switch between a 2 hander or swrd + shield, or rogues who need a dagger in their main hand to use certain abilities while stealthed). 3.3 changed it so addons can't change weapons.

You can still do it with /equip macros, but it's such a PITA having to update them every time you get a new weapon, compared to just updating outfitter.

I don't know why Blizzard made that change, it just seems petty, and may have something to do with promoting their own equipment manager (which is lacking that feature at present).

Jamba is amazing, but it's an addon and therefore is far too tied into the game. I think as much potential to mess things up as is possible, should be taken out of Blizzards hands, as they don't seem to give a damn about addon makers, or even players, and seem to love making changes for change's sake just to massage their own egos (Yes after 2 years playing I'm really beginning to hate the developers, but I've rarely seen them fix anything without breaking something else that was fine in the process. Meanwhile the game is littered with the kind of bugs that take a matter of seconds to fix, many years old now).

When Blizzard disables the ability to do something, it's because they don't want you doing it. Finding a way to circumvent that is a perfect way to get banned and get the utility you used to do so in trouble.

[Ughmahedhurtz]

When Blizzard disables the ability to do something, it's because they don't want you doing it. Finding a way to circumvent that is a perfect way to get banned and get the utility you used to do so in trouble.

I think you're missing the point. Which is, we'd rather not have the tool itself hard-coded to use in-game mechanics that may or may not exist in a future version of WoW (or any other game for that matter). Having user-created "helper" scripts that CAN account for useful in-game behavior is a different matter.

And I think we're all well aware of where the line is regarding ToS violations.

[TheFallenOne]

I think you're missing the point. Which is, we'd rather not have the tool itself hard-coded to use in-game mechanics that may or may not exist in a future version of WoW (or any other game for that matter). Having user-created "helper" scripts that CAN account for useful in-game behavior is a different matter.

And I think we're all well aware of where the line is regarding ToS violations.

Yeah, I got that point. I was just trying to say that what he was saying was somewhat implying that we should ensure that the program is removed enough from WoW to be able to use the program to do things that Blizzard has intentionally removed, which I don't like hearing.

I don't think there's any question that the tool shouldn't be hardcoded to use in-game mechanics. I haven't seen anyone say anything to the contrary, and I can see a lot of negative things coming from that. As mentioned several times previously, we have Jamba for managing in-game mechanics (as so far as Blizzard will allow).

[Freddie]

I think you're missing the point. Which is, we'd rather not have the tool itself hard-coded to use in-game mechanics that may or may not exist in a future version of WoW (or any other game for that matter). Having user-created "helper" scripts that CAN account for useful in-game behavior is a different matter.

I've been thinking that Mojo will have different features that do different things. Right now we're talking about one of those features, Broadcast, which only sends key strokes (or maybe key combinations). Correct me if I'm wrong but I think the only way Broadcast can trigger actions in WoW is if the action is bound on the left side of WoW's key bind screen.

No matter what else gets added to Mojo, I imagine Broadcast will always work like that. It will always provide a rock-solid "low level" method of controlling WoW manually, with the user completely in control of what's going on.

How's the next version coming Freddie?

I gotta confess, I got derailed and haven't looked at it in over a week.

What happened is, after reading comments here, I had second thoughts about my idea of including WoWs and Toons in the config screens. It seemed to be more complicated than what some people will want. But I couldn't figure out a simpler way that will work. So I decided to think about it overnight ... then the next night ... then etc.

Meanwhile I wrote a program that changes gamma/brightness/contrast depending on which game is in the foreground, and eventually I'll put that code in Mojo, so the week wasn't a total waste, but that didn't get us closer to the next build.

[Fursphere]

I think sometimes people get so caught with what they WANT and totally forget what they NEED. I know I'm guilty of this myself.

I think they original concept of configuring your MAIN and SLAVES was golden. (left side/right side). I'd just run with that until the need for something better came about.

The gamma brightness contrast thing sounds pretty cool. Since you wrote that already, maybe just incorporate it into mojo for the next version? lol

-Fur

[Aragent]

I Have been away for a couple months, I noticed there dosent seem to have been many Build updats for a while,

and havent noticed much chatter on the forum Any chance we can get an project update.

[Blubber]

I haven't been boxing for a long while (still stuck in BC actually), so when I returned to boxing last week and went to the HKN website to download HKN, I was very pleasantly surprised to see HKN get open-sourced. Really nice work freddy!

Anyway, I just have a question about scripting in Mojo. Why don't you just embed Lua as scripting language? It's easy to embed, easy to learn and a lot of users probably already know it. Also, there are lot's of editors with syntax highlighting for Lua. Just my 2 cents .