Combo Points for Vehicle Dragons
 

I'm running the latest public version of nUI from Curse, and I'm trying to find where the combo points show up when you're on a vehicle that generates them (I'm a priest, so I don't generally rack up combo points). I know where they show up on the Player/Target HUD as a rogue, but they're not there on the vehicle.

Guidance on this would be greatly appreciated - I'm loving the interface so far, and once I can find those tiny little dots I'm taking this into the Eye.

It's possible they're not showing up... in fact, until you mentioned this, I didn't know there was a vehicle that causes combo points.

A question for rogues out there... do any of you know which quest this is and while your vehicle is generating combo points, is it possible for you to generate combo points as well, or is this one of those things where you can't use your own talents because you're in the vehicle?

If that's the case, then I just need to fix the engine to look for combo points for vehicles as well as the player.

The quest I was referring to is Aces High! in Coldarra, though the vehicle there is the same as the vehicle used in phase 3 of Eye of Eternity (Malygos after the platform blows up).

From the priest perspective, being in the vehicle supersedes my abilities for the duration.

I can confirm the combo points don't show up in malygos, 3rd phase, either.

We're supposed to use the vehicle's abilities, not your own. I don't know if the rogue also generates the points, i supose not. But at that point, what counts is the dragon.

don't know if i'm beeing clear, i'm having a hard time with my English beeing too rusty.

Funny thing happened to me last raid to maly. Though we're not supposed to be able to use our abilities, i clicked in the frame where stance buttons were suposed to be, changed stanced and fell from the dragon, dying in the process.

As a Feral Druid I too use combo points and can confirm that they do not show up when I do the Aces High! quest.

Normally when you're on a vehicle, the stance bar is replaced by a two button possession bar. The second button on that bar is the dismount button. I'm going to guess that's what you clicked without realizing it.

Wow, that's one of my fav dailies and I had no idea it had combo points. :eek:

Perhaps I'll try it with the default Bliz UI.

>.>

Cant...

<.<

Disable...

>.>

nUI...

/falls over

Never mind. I can't possibly play without nUI! :D

~roflmao~

:D

Just to clarify this for you Scott in case youve never done it.

There is a daily quest in Colderra that is basicly identical to the 3rd phase event for Malygos in the Eye.
You are mounted on a dragon and have 5 abilities in your 'vehichle' bar which is limited by an energy level.
You have a main attack ability and a main heal ability.
You have a sub attack, sub heal, and shield ability.
The main heal and main attack abilities create a 'combo point' which stacks.
The sub heal and sub attack abilities potency is multiplied by the number of stacks and consumes them on use.
The shield relies solely on having sufficient energy.
It is vital during the encounters to have sufficient stacks so that the sub abilites will produce large amounts of spike damage.
These stacks do not show in nUI.
Ive learned to count to myself hehe.

Most likely. I remembered those buttons as i read your post, and thought i didn't see them at the time, it is most likely that i pressed them. Maybe they weren't showing up due the atempts i made on costumizing your code :D.

No big deal anyway.

Just reminding, about the combo-points issue, that in malygos, in an earlier phase (2nd) melees do use another vehicle, some disks, that allow u to fly, but you still use your own abilities in there. Rogues and feral droods will need to see their own combo points while using those disks, and when they mount the dragon, see the dragon's combos.

I also am missing the combo points in the 3rd phase of that fight. I ended up downloading the Malygos Stacks addon to keep track. It makes an obnoxiously large button with all the info I need on it.
Hope this helps.

This bug *should* be fixed (not 100% sure it is) in the 5.03.05 update tonight