Spirit Shroud disappointment

[Kven]

<DIV>I got 46.3 this morning before work and I'm somewhat disappointed in Spirit Shroud.  I thought we'd lose that 16% base speed penalty ( which nullifies any speed buffs you have since a speed penalty ( slow ) takes precidence over run speed / horse speed [ we all have multiple speeds - In Combat, Slowed, Run, Horse ].</DIV> <DIV> </DIV> <DIV>At least that's what I've gathered.  So with SoW / Jboots on/off it makes no difference, you run at 84% of base speed.</DIV> <DIV> </DIV> <DIV>I would have thought we lose that penalty being the last invis we get <img src="/smilies/9d71f0541cff0a302a0309c5079e8dee.gif" border="0" alt="SMILEY" /></DIV> <DIV> </DIV> <DIV>Basically I feel like my assassin now... even w/ Disappear (lvl 50 sneak) it's 16% penalty.  Argh.</DIV>

[Tanatus]

Buy T2 horse? btw at Adept 1 its 15% RS decrease so with T2 horse you will run at +17%

[Dae]

I may be mistaken but I was sure that Summon Shadows and Aspect of Vul both had a <b>25%</b> movement penalty (That is except App1 of Aspect of Vul, which aparently has none). Spirit Shroud is a big improvement only having 15%. <div></div>

[Kven]

<DIV>Heh.</DIV> <DIV> </DIV> <DIV>My point is, though, that whenever any type of movement penalty is in place, it negates ALL speed buffs.</DIV> <DIV> </DIV> <DIV>Horse speed is it's own speed.</DIV> <DIV> </DIV> <DIV>Here's how I *THINK* speed checks work:</DIV> <DIV> </DIV> <DIV>If there is a penalty, use <EM>base speed</EM> and subtract the penalty -- Ignore buffs</DIV> <DIV>If you are in combat, use Combat Speed [ base speed - penalties ].</DIV> <DIV>If there is no penalty and not in combat, use fastest speed of:<BR>    Horse Speed</DIV> <DIV>           or<BR>    Run Speed [ All buffs go here ]</DIV> <DIV>           or</DIV> <DIV>    Sprint Speed [40%]</DIV> <P>The above 3 technically don't <STRONG>stack</STRONG> per se, though sometimes it <STRONG>appears</STRONG> that they would.</P> <P> </P> <P>When you're on a 32% speed horse, when you hit your sprint key, the horse speed is ignored because sprint is greater.</P> <P>When you have Spirit Totem of the Wolf + pathfinding + jboots and hit sprint, no change of speed [24% + 16% + 10%] because you're already going faster than sprint.</P> <P> </P> <P>Anyhow, you get the basic idea.  I'm not a developer for SOE so it's all merely theory, but from various tests that's how I see it working.</P> <P> </P> <P>So back on topic, base speed - penalty (15%) = 85% movement max, regardless of horse / sow / stow</P> <P> </P> <P>I'll do more tests later.</P>

[Tanatus]

<DIV>Subjectively I feel that with invis on horse I move faster then w/o horse ...Also I danm sure on 100% if you can SoW then someone use group invis - group definitly moves faster then w/o SoW</DIV> <DIV>Lastly if we assume for second that you theory correct that and last speed buff take control - next trick should work. Unequip Jboots, cast spirit shroud equip Jboots - that should grant you total +10% (since Jboot according to your theory will ignore negative bonus of speed from SS)</DIV> <DIV>P.S.</DIV> <DIV>App 1 of Spirit Shroud indeed have -25% speed run</DIV> <DIV>Adp 1 already only -15%</DIV> <DIV>I presume that Master will be -5%</DIV>

[Dae]

My horse most definitely makes me go faster when I'm invis. Not sure exactly how all the stacking works. <div></div>

[Kven]

<DIV>Anyone have Adept III  and can share the speed decrease?</DIV>

[Andre]

<DIV>I have master I of previous version (xxx of Vul). This had 15% speedpenalthy and i could confirm - with T2 horse things are much better.</DIV> <DIV> </DIV> <DIV> </DIV>

[Fepp]

Personally I carry around wolf totems (and use LJB) for a speed buff when I'm inside indoor zones and using invis.  My warlock duo partner always forgets to buy the totems - and you can see the difference in speed. However, there is something strange going on with speed adjust when invis.  My example of this is when you have a heavy burden - if you invis yourself, you will run a lot faster.  In that case it seems like base speed -15%.  Dont know if this still works, /bugged it months ago... doubt its fixed though <div></div>