Ring of cold

[Magu]

any one noticing it breaking with 10 secs left? infact any one noticing all of out roots breaking with time left on them ?(7 secs for truss) <div></div>

[TooFarGo]

I've been watching mine closely over the past few days, as another poster had the same question.  So far, so good.  I could have sworn most of my roots were doing exactly what you say about 2 weeks ago.... Seems OK now. Will continue noticing when it breaks. <div></div>

[Talrinys]

Works perfectly fine for me, what monsters did you test it on? If anything mine has been working even better than before recently. <div></div>

[Mastire]

<DIV>The higher level you are teh longer the spell lasts.<BR><BR></DIV>

[Magu]

yeah I just was messing with it earler today with my guild in perma. RoC always broke with 10 secs left on the timer and truss was always breaking with 7 secs left im lvl 49 BTW <div></div>

[Ishma]

What level are your spells?

[Magu]

adept 1 and my subj is caped BTW Im baseing by times off of the icons I woulnt have a problem if it wasnt breaking 100% of the time, at the same time. <div></div>

[roarfrost]

<P>Its 9 seconds for me, and its not just RoC.</P> <P>I use the training upgrade to Tether, and it does the same thing. 9 seconds. Even the secondary root from it breaks at 9 seconds. Frozen manacles Adept 3? Same thing. 9 seconds.</P> <P>Last night on every encounter, ALL my roots broke with 9 seconds left on them. (Yes, I paid attention to every single one)</P> <DIV> </DIV> <DIV>EDIT:   BTW, to the people saying theirs works correctly, are you hovering your cursor over the icon in the maintained spells window and watching the timer? I did this every time last night, and as soon as it hit 9 secs, root broke.</DIV> <DIV> </DIV><p>Message Edited by roarfrost on <span class=date_text>05-16-2005</span> <span class=time_text>10:04 AM</span>

[TooFarGo]

Ok, I was watching this weekend, and for the most part, it held the full timer. However, it *did* break with 9 (or so) seconds left on the timer several times when I was solo'ing ^^ heroic mobs! My RoC is currently at app4. <div></div>

[SalBlu]

<DIV>Well... when I solo, lets say a lvl 49-50^^, I cast my RoC, then do my regular spell rotation of HO Starter, Piercing Icycles, Immolation, Ball of Flames, Ice Comet, Westfend's Ice Spear.  The next thing I always do is cast my root, ie Truss or Frozen Manacles, then cancel RoC.  At the point of my cancellation, I have about 8 seconds on the timer.</DIV> <DIV> </DIV> <DIV>In groups though, when I am unable to use my secondary roots, my RoC always holds for the full ammount, and is at Adept 1 lvl.</DIV>

[roarfrost]

<DIV>I will do more tests tonight.</DIV> <DIV>I was only testing this on heroic^^ mobs in Obelisk, and like I say, on every one root broke at 9 secs.</DIV> <DIV>I will test on solo mobs and other mob types in different zones tonight.</DIV> <DIV> </DIV> <DIV> </DIV> <DIV>There is obviously a bug here.</DIV> <DIV> </DIV>

[Supa Mint Flava]

<P>I was duoing 49 heroic mobs in Everfrost with another 49 wizzy, and RoC held fine.  Naturally we watch the timer carefully as we have to trade off rooting.  We both have it at Adept I.</P> <P>Typically I will root with RoC and then nuke like crazy, and then cast the root, and then the other wizzy would cast RoC, nuke, rinse repeat.</P> <P>Great xp for going from 49 to 50.</P>

[TooFarGo]

breaking again and again while duo'ing masses and spiders in CT.  breaking right at 9 seconds. AppIV RoC. <div></div>

[SalBlu]

<DIV>There is a very easy solution to this.  COMPENSATE for the lack of holding power if the root is breaking early.  Cast your Truss/Tether/Frozen Manacles early, then cancel the icon for RoC before the dot breaks your slow root. </DIV> <DIV> </DIV> <DIV>Come on people... you have to think outside of the box a bit and learn to cope with the way your spells perform.</DIV>

[TooFarGo]

This is not a question of working around it.  Yes, we can all work around it. It is a question of "is the spell working as it is supposed to?". If it is, fine. Expect it to break. If not, there is a problem that needs to be addressed. <div></div>