PDA

View Full Version : Surviel : Seems bugged


Elv
04-11-2005, 04:22 PM
<DIV>Last night while in Super Nek, I was wacking away on the spiritsucker when surviel decided to stay perma queued. I dont know whether someone else's spell over wrote it or if its still bugged. I know this used to happen to me when grouped with a necro ( who'd put skele form on the group ) but since the last live update, have not had any issues. </DIV> <DIV> </DIV> <DIV> It made that fight rather difficult and my means of reducing agro were gimped. Since evade was all I had ... woo woo ~ Needless to say I was MT for a good portion. We did survive and a camp out was all that was needed to reset the ability, but this shouldnt be a fix. </DIV><p>Message Edited by Elvar on <span class=date_text>04-11-2005</span> <span class=time_text>05:25 AM</span>

Putka
04-11-2005, 04:25 PM
heh this bug has been around for some time now.. supposedly the HO "ardent challenge" breaks it. It's not a bug with Surveil in particular, but all (most?) stealth CAs with the mask symbol. In any case, it seems to be fairly certain it's tied to HOs <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" /> Like you said.. relog, zone or evac will fix it. <DIV> </DIV> <DIV>Oh and, since people discovered what causes it I've been using the Merciless Villainy line exclusively to advance mask steps. This one never gets "stuck".</DIV><p>Message Edited by Putka on <span class=date_text>04-11-2005</span> <span class=time_text>05:41 AM</span>

Elv
04-11-2005, 05:02 PM
<P>Now that you mention that, it makes sense. I completed the ( Tricksters Gap ) HO.. I believe that is the name. Using Surviel as the trigger and thats when It seemed to [Removed for Content] me last night. </P> <P>So it seems multiple HO's using a stealth as the trigger move will *perma queue it. Thanks for the info~ Ill be using MV till they find a fix. </P>

Outerspace
04-12-2005, 05:20 AM
Experienced this and /bug'd it. GM contacted me in game and just advised to relog which fixed it. Thanks for the pointers regarding the cause of it! <div></div>