![]() |
|
#61
|
|||
|
Or, you could get off your illegitimately high horse and -
1. Learn something new for a change 2. Quit changing your argument from "it's impossible..." to "All I'm saying is...". You have the consistency of pissed-in cake batter. Six years is cute, though =). | ||
|
|
|||
|
#62
|
|||
|
I like the book you wrote earlier Reikerz
| ||
|
|
|||
|
#63
|
|||
|
So basically what everyone is saying is: If you want to play a shaman, roll a Gnome.
__________________
Blue - All the classes!!!!
Red - All the races!!!! | ||
|
|
|||
|
#64
|
||||
|
Quote:
I love your math... You show how over a 30 minute fight, stun immunity will give you the ability to cast 2 extra torpor, to gain 2400 hp. Then you dismiss lame +8 standing regen. Let's see, 8 hp per tick = 80 hp per minute * 30 min = 2400 hp. Let's ignore the fact that if you're timing bash properly, you won't let torpor drop and so you don't really gain those 2 extra torpors. Even if you do get those awesome gains, you end up even with the troll on hp, and having spent an extra 400 mana. Next time you say "math time", don't stop doing math after only analyzing half of the equation. I'll give you some help on your argument, since you seem to be having trouble forming a decent one yourself. When bashed, you get stunned for 1.5 seconds. That is extra downtime. Even if you time your big spells around bash, as every good shaman should, you still lose out about 1/2 cast of canni each time you are bashed. This happens about every minute, so you lose roughly 1 canni cast every 2 minutes. This is what you should be focused on if you want to argue the benefits of stun resist. Of course, against the very hardest hitters where you have to back off canni after unlucky streaks of hits, this effect is negated. If you're never reaching full hp with torpor ticking nonstop, the stun immunity offers no benefit. And these are precisely the fights where extra regen offers the greatest benefit (use your math to understand why).
__________________
Orruar <Trump> - 60 cleric - P2002
| |||
|
Last edited by Orruar; 08-28-2012 at 10:19 AM..
|
|
|||
|
#66
|
||||
|
Quote:
| |||
|
|
||||
|
#67
|
||||
|
So, knowing when a bash is coming up helps you know when to not cast, but what if you need to cast something when that bash timer is about to hit?
Do you A) die B) die C) Change time and space so that you can some how change your spells around in a way that doesn't affect your efficiency and you don't run OOM from overlapping spells too soon. To be bashed or not be bashed, that is the question. When it comes to RNG bash will affect you, regardless of how well you can count to ten on your fingers, unless you're an ogre and you give 0ducks. That said, I'd still rather be a lizard in velious.
__________________
Quote:
| |||
|
|
||||
|
#68
|
||||
|
Quote:
__________________
Orruar <Trump> - 60 cleric - P2002
| |||
|
|
||||
|
#69
|
|||||
|
Quote:
__________________
Quote:
| ||||
|
|
|||||
|
#70
|
||||
|
When you time spells around bash, do you assume every bash is going to hit? Say spell cast recovery time finishes and you want to canni, but your bash metrognome shows there is a bash in 2.273 (repeating) seconds. Do you cast? The Ogre doesn't give a hoot.
I mean, this isn't some age-old question without an answer. There's probably a giant sticky on Samanna that says 'ROLL OGRE.' Quote:
| |||
|
|
||||
![]() |
|
|