Burning Crusade UI changes. - Page 2

exog · 10/06/06, 4:29 AM

Sounds great to me!
Less mods, more skill!

Pressing one button to decurse the entire raid is just stupid imo.
Ofc you should have to choose who to decurse/heal.

Camaris · 10/06/06, 4:37 AM

Would this also destroy action bar mods? Or things like Sprocket and Necrosis, that provide different buttons? Because that would basically mean we're all going back to the default UI.

zepi · 10/06/06, 4:42 AM

Some bar-mods seem to work on top of default toolbars, while other seem to map their own keys for a complete remap. I'm pretty sure that atleast somekind of bar-mods will be possible.

Maybe they could implement a integrated fastcast that'd make that lag issue little less annoying for ppl who don't live right next to their servers.

Metalmilitia · 10/06/06, 4:55 AM

does anyone knows if some changes have been made to:
Â° guilds UI
Â° tradeskills UI
and maybe if some banking system has been introduced?

Ghiest · 10/06/06, 5:09 AM

What's the point in being able to if they basically disable almost every mod with one single peice of sweeping code change?

I know, lets get everyone used to using their favourite mods and addons, now lets completely wipe them out. That'll teach them

burninator · 10/06/06, 5:17 AM

Originally Posted by Veneficus

It appears that in Burning Crusade, Blizzard will be disabling all "click-to-cast" functionality in UI mods. (UI mods can no longer cast spells of their own accord during combat, even with a mouse click or button press.)

From the LUA changes for WoW 2.0 thread on the Wow UI forums:

You will be able to bind keys directly to spells, using the scripting interface, e.g.
/script SetBindingSpell("[", "Holy Light")

Wouldn't this already be a workaround for something like Decursive? I.e. spamming a button and remapping the button as needed? Assuming that scripts/mods can still target units without user interaction of course, if they disable that it would break the majority of UI mods.

Drauk · 10/06/06, 5:28 AM

According to Veni, you cannot rebind keys in combat either. Also according to Gibybo from CQ all sort of advanced targeting fuctions are also disabled, meaning that any 3rd party frames will be useless.

Lactose · 10/06/06, 5:29 AM

Originally Posted by burninator

From the LUA changes for WoW 2.0 thread on the Wow UI forums:

You will be able to bind keys directly to spells, using the scripting interface, e.g.
/script SetBindingSpell("[", "Holy Light")

Wouldn't this already be a workaround for something like Decursive? I.e. spamming a button and remapping the button as needed? Assuming that scripts/mods can still target units without user interaction of course, if they disable that it would break the majority of UI mods.

Cannot change key or mousebindings while in combat. This is done to prevent work arounds like
-You could just rebind the spell to the mouseclick before cast and rebind it to the window action after. This may require a double click instead of a single, but would probably still allow the casting of spells by clicking.

Edit: Not fast enough =(

Vhex · 10/06/06, 5:37 AM

Originally Posted by exog

Sounds great to me!
Less mods, more skill!

Pressing one button to decurse the entire raid is just stupid imo.
Ofc you should have to choose who to decurse/heal.

Except it was never about skill. It was about getting your UI to the point where you didn't have to stare at status bars all night long. It's been nice not having 40 health bars clutter up 1/5th of my screen.

Varg · 10/06/06, 5:44 AM

Originally Posted by Dakous

It would be nice if it promoted intelligent debuffing ("Hey! I just threw Curse of Splat on the entire raid. But you only have to remove it from the rogue highest on the aggro list! - good raids spend 1 decurse, bad raids 25! of mana"), but instead, it's just "hey, let's assign decursers."

Guess you can say huhuran does this, you have to dispel here, but you can't do it mindlessly with decursive.

Like jinndo and hakkar screwed up any attempts of binding decursive to movement keys.

exog · 10/06/06, 5:56 AM

fuckit, i have absolutely no experience from healing classes so ill drop it...

tho ill make a comparison: as a rogue, my main job is to choose the best target and dps it without dying. this is the MA target or the ffa target.

afaik: the healers job is to heal/decurse/buff/whatever a member of the raid party, either an assigned target(ie mt) or ffa target.

now im not sure exactly how much of the healing job thats automated, but lets say the dps job had a lot of automation: then my mod would: pick the right target, cast the correct attack, count combopoints, feint etc etc, all i would have to do would be to keep in melee range and press this one button, now that would be boring and lame...

so while being in the constructive corner today: what exactly do these mods automate for the casters?
- pick the right target to heal?
- Pick the right kind of heal?
- shield/decurse?
- brush your teeth?

edit:

Originally Posted by Vhex

Originally Posted by exog

Sounds great to me!
Less mods, more skill!

Pressing one button to decurse the entire raid is just stupid imo.
Ofc you should have to choose who to decurse/heal.

Except it was never about skill. It was about getting your UI to the point where you didn't have to stare at status bars all night long. It's been nice not having 40 health bars clutter up 1/5th of my screen.

hmf, it thought that was what healing was about... namely staring at bars and healing the low ones...

sp00n · 10/06/06, 6:04 AM

Just think that you would have to attack 40 different mobs, one by one, in a time span of say 30 seconds.
Then, after 1 minute, repeat.

Now you have your lucifron fight. ;)

Daboran · 10/06/06, 6:10 AM

Exog, I suggest you borrow a Druid/Priest/Shaman healer account sometime and try it - most raid ui mods (obvious exceptions include Decursive) are not doing the job for you - they are filtering the information so that you can do the job more effectively. :)

While I can see some of the reasons for changing this Blizzard seem to be missing the point. Most raid mods are made in reaction to a flawed mechanic or UI functionality in the game, not as a conscious effort to circumvent having to actually play. This change could make healer burnout more prevalent.

Skytor · 10/06/06, 6:12 AM

Originally Posted by exog

so while being in the constructive corner today: what exactly do these mods automate for the casters?
- pick the right target to heal?
- Pick the right kind of heal?
- shield/decurse?
- brush your teeth?

1 - Nope
2 - Nope
3 - No / Yes
4 - Cost option only

Heres how my set up works ... Spells bound to mouse clicks:

Left = Healing touch 4 -- Alt + Left = HT7, CTRL + Left = HT11
Right = Rejuv max rank - Alt+Right = Swiftmend
Middle = Regrowth 7

Scan the assigned targets look at their situtation, make a single click to apply the option of your choice
Repeat for 10-15 minutes

No mods...

Scan the assigned targets
Click to target
Hit a key bound to the correct spell
Repeat for 10-15 minutes

How much of a loss is it ... imagine every spell or SS/BS or shot cleared your current targeting and you had to retarget before the next action - thats about how much more time consuming and annoying it will be (for me its enough to consider a main switch out of healing classes)

Goggles · 10/06/06, 6:41 AM

Originally Posted by Camaris

Would this also destroy action bar mods? Or things like Sprocket and Necrosis, that provide different buttons? Because that would basically mean we're all going back to the default UI.

Bartender2 would work with these changes. It just manipulates the current Blizzard bar frames. That said it isn't quite as customisable as other bar mods (you're stuck with 5 bars of 12 buttons).