Poll: SH healdebuff on level 21 (temp change until T3)

[Luth]

If it the version of pounce, that was active at server shutdown I find it almost impossible to abuse midair. There was a fix of it at some point, and before that it could be abused almost as you wanted to. Avoiding fall dmg of keep walls, avoid being punted of ledges, heck even avoid dieing from the big bridge crossing rvr lake in DW near order WC. After that fix it hardly never worked.

And as I somewhat agree with Zealote, I dont really see the difference from pouncing back to taget straight after landing or doing it midair. We are talking half a second or so here, and wont really change much due to global cooldown anyway. thats my oppinion atleast

That fix (i can't really call it like that) made pounce very unreliable in the common gameplay situations. The slightest difference in the z-axis between you and your target let it fail. So you had to spam it most of the time while walking and after the 3rd-4th time maybe you got a successfull pounce while landing near your target with ~ 50% of you AP left.

I would suggest an AP increase to 40 AP (if possible) like it was some time ago, now that it works reliable. I would also suggest a cooldown, but afaik this is not possible atm. Also maybe there could be a block to pounce if the player is in the air, dunno if possible.

But seriously the 1.4.8 pounce was bad mythic ability design as it's best...

Old pounce (40 AP):
https://web.archive.org/web/20080915041 ... px?id=9186

[Luth]

I wonder why people think you should be able to pounce in mid air. Unless you're packing a jetpack, I don't see how that's physically possible.

c-cause magic
Also elfs are very light and agile, so they can move around mid air like birds.

Srsly, would be nice if mid air pounce could be fixed, without making pounce the almost useless ability again it was in until 1.4.8.

[Azarael]

A cooldown can be added to Pounce, but please bear in mind that changing one ability for balance reasons opens the door for others to be changed as well.

When it comes to modifications, there are tiers of viability:

Perfect - displays correctly on client

- Switching tactics and abilities around, changing level requirements for them, changing mastery organisation

Good - client's info will be partially correct

- Changing cooldown (hotbars will display correct cooldown but tooltip will be wrong)
- Changing effect of buffs (buff icon and stats screen will be correct)
- changing AP (consumption will be correct, tooltip will be wrong)
- changing damage (combat log / wsct / buff icon / etc will be correct, tooltip will be wrong)

Tolerable - client's info will be wrong

- changing stacking group for buffs
- adding functionality to abilities

Bad - client's info will be grossly wrong

- changing ability functionality entirely

Unacceptable - client will actively interfere

- changing ability requirements (mechanic points, requiring block/parry etc)

[Luth]

I remember, that one of the later mythic devs (i think it was keaven freeman) wrote somewhere, that when the 1.4.9 pounce works 100% reliable, the next step would be giving it a slight cooldown.
Maybe with a cooldown, the AP increase would be too much (WL is already AP starving).

I think a short cooldown would be perfect/best solution.

[Zealote]

That's interesting to know Azarael, spose it sort of gives an order to try and follow when changing/balancing stuff. R.E. incorrect tooltips, I dno whether you're already doing it yourself but I wonder whether a public list of deliberate ability changes would be useful (e.g. auras, AM's aoe detaunt, no procs off throw axe etc). Would be gd to have an ongoing record anyway but might also help reduce bug reports on stuff that was intentionally changed.

Yh think that's the best way Luth, get it 100% working correctly (if poss) then see if it needs balancing with +ap cost/cd/whatever. Def better than having broken skills anyway, even if it means a period of possible OPness till it's changed. Same with fetch/TE.

[Azarael]

AM's aoe detaunt

Obliged to point this out, but this was changed to 5s/10s because of a bug report which proved that it was this way on live.

[Zealote]

AM's aoe detaunt

Obliged to point this out, but this was changed to 5s/10s because of a bug report which proved that it was this way on live.

Yh I saw the linked patch notes. It was just an example of an ability whose functionality on RoR differs from its tooltip.

Edit: Nvm I see what you mean now: it wasn't a change to how the ability worked on live like the other two examples, the tooltip was already wrong back then.

[mickeye]

I wonder why people think you should be able to pounce in mid air. Unless you're packing a jetpack, I don't see how that's physically possible.

"Physically" possible in fantasy game? I don't think that's really an issue.

But seriously the 1.4.8 pounce was bad mythic ability design as it's best...

Old pounce (40 AP):
https://web.archive.org/web/20080915041 ... px?id=9186

Well not only old Pounce (before patch 1.1) was AoE but it was GTAoE. But if you want to bring it back, I wouldn't mind.

[Luth]

Na, it was just posted to show the increased AP on the old pounce, but with a cooldown added i don't think the AP increase would be needed.

[mickeye]

Na, it was just posted to show the increased AP on the old pounce, but with a cooldown added i don't think the AP increase would be needed.

The AP cost was because of AoE effect. When was ability changed to single target, AP cost was decreased.