Conjuror Unabate Change - A change for the worse

[Xalmat]

<p style="padding-left: 30px;">ACHIEVEMENTS</p> <p style="padding-left: 30px;">Conjuror</p> <p style="padding-left: 30px;">Unabate will now gray out when properly when used.</p><p>OK, good in theory. But bad in practice. Here's why.</p><p>When you cast Unabate, then summon your pet, your pet does NOT get Unabate applied to it. You have to cast Unabate AFTER the pet is summoned for it to apply to the pet.</p><p>On Live, you can cast Unabate while it's active to "refresh" it, so that it reapplies to the pet.</p><p>On Test, when you click Unabate to refresh it, it triggers the 10 second recast. Only after the 10 seconds have passed can you effectively refresh it.</p><p>In situations where your pet dies, followed by you casting Dimensional Storage, this ends up <em>hurting </em>the Conjuror in the long run.</p><p>Please just change it back to the way it was.</p>

[Cele]

<p>Or, they could fix it so it DOES apply to our pet if we cast pet after casting unabate.</p><p>Either way, the recent change is not good for conjys. </p><p>Edit for poor spelling</p>

[feldon30]

It should not be castable when there is no pet. The target should be 'pet'. And this fix would also make the buff cancel if the pet dies.

[Bratface]

<p><span style="font-family: tahoma, arial, helvetica, sans-serif;"><span style="font-size: medium;">But isn't it a buff on both caster and pet? So it would have to allow casting without a pet.</span></span></p><p><span style="font-family: tahoma, arial, helvetica, sans-serif;"><span style="font-size: medium;">If the spell is broken and not refreshing when a new pet is cast then that needs to be fixed or the recast needs to be instant, or both.</span></span></p>

[thog_zork]

<p>come one everyone knows that the nerf would come conjuror are soooo overpowevered they needed to nerf them ...</p><p>come on it is insanne raids are starting to include 4-5  conjuror (summoners) to accompany the 4-5 chanters and 5 bards ... leaving no room for other classes !</p>

[Ciara52]

<p><cite>thog_zork wrote:</cite></p><blockquote><p>come one everyone knows that the nerf would come conjuror are soooo overpowevered they needed to nerf them ...</p><p>come on it is insanne raids are starting to include 4-5  conjuror (summoners) to accompany the 4-5 chanters and 5 bards ... leaving no room for other classes !</p></blockquote><p>I would guess this is sarcasm?   My class hasn't been overpowered since forever -  All I know is that pretty soon there isn't going to be much use playing the characters I like. </p>

[Xalmat]

<p><cite>Bratface wrote:</cite></p><blockquote><p><span style="font-family: tahoma,arial,helvetica,sans-serif;"><span style="font-size: medium;">But isn't it a buff on both caster and pet? So it would have to allow casting without a pet.</span></span></p><p><span style="font-family: tahoma,arial,helvetica,sans-serif;"><span style="font-size: medium;">If the spell is broken and not refreshing when a new pet is cast then that needs to be fixed or the recast needs to be instant, or both.</span></span></p></blockquote><p>Correct, it affects both the caster and pet.</p><p>Ever since it was implemented in EoF it has never been active on the pet after the pet is recast. It's always had to be refreshed when the pet is summoned.</p>

[Robewarrior]

<p>Another meaningless, unnesscessary, and unrequested change.</p><p>Why not spend the time on shared stats guys?</p>

[acctlc]

Agree completely with Xalmat. Either reverse the change or make it automatically effect the pet after its resummoned.

[Valdaglerion]

<p>Spell should be persistent for either caster or pet and apply to pet automatically if casted prior to the pet existing and immediately if dimensional storage is used.</p>

[Robewarrior]

<p>Can we please get a red-name to verify whether or not this change was intended, or an unintended result from another change?</p>

[Cele]

<p><cite>Robewarrior wrote:</cite></p><blockquote><p>Can we please get a red-name to verify whether or not this change was intended, or an unintended result from another change?</p></blockquote><p>It was in the update notes as as stand-alone item. Appears to be intended, but for the life of me, I cant figure out why.</p><p>Maybe a dev noticed it didnt grey out like other cast buffs do and assumed it was an error and 'fixed' it, not knowing it really should not grey out.  ( Or it should apply to the pet  upon recast automatically like the rest of our buffs do)</p><p><span > ACHIEVEMENTS</span></p><p style="padding-left: 30px;">Conjuror</p><p style="padding-left: 30px;">Unabate will now gray out when properly when used.</p>

[Sedenten]

<p><cite>feldon30 wrote:</cite></p><blockquote>It should not be castable when there is no pet. The target should be 'pet'. And this fix would also make the buff cancel if the pet dies.</blockquote><p>As was already pointed out, Unabate is meant (and reads in the description of the AA itself) to affect both the caster and the pet.  Currently the way it works is when you cast it, the buff applies seperately to caster and pet.  If the pet dies, Unabate will not "refresh" onto a new pet.  In those cases, it always needs to be refreshed (regardless of the fact it is already present on the owner).  Conjurors have gotten into a habit of recasting it when they resummon the pet. </p><p>Honestly, I'm lost as to why the change was even done.  I can't think of any good reasons to have Unabate grey out after being cast, nor can I think of any "exploits" conjurors could be using by being able to cast it over and over.  I can possibly see how conjurors that simply didn't notice this happening could find it annoying to always see Unabate up and end up submitting a /bug report without realizing that it needs to be recast whenever their pet dies. </p><p>There's only three fixes I can see for this:  <strong>a.</strong> revert the change back to the way it was (i.e. it does not grey out when cast) or,<strong> b.</strong> change the mechanics of the spell so that as long as it is active on the caster it always gets shared to the pet or, <strong>c.</strong> change the mechanics of the spell so that the 10 second recast is dropped completely and the spell becomes "active" and recastable immediately whenever it is not present on the owner <em><strong>AND</strong></em> the pet (but do NOT cause it to drop from the owner if it is not present on the pet--that would be pointless).</p>

[Draco the Grey]

<p>d.  Just make it a groupwide buff.  That would solve the problem of it being applied to the pet on recast. <img src="/eq2/images/smilies/69934afc394145350659cd7add244ca9.gif" border="0" /></p>

[SilkenKidden]

<p><cite>Xalmat wrote:</cite></p><blockquote><p style="padding-left: 30px;">ACHIEVEMENTS</p><p style="padding-left: 30px;">Conjuror</p><p style="padding-left: 30px;">Unabate will now gray out when properly when used.</p><p>OK, good in theory. But bad in practice. Here's why.</p><p>When you cast Unabate, then summon your pet, your pet does NOT get Unabate applied to it. You have to cast Unabate AFTER the pet is summoned for it to apply to the pet.</p><p>On Live, you can cast Unabate while it's active to "refresh" it, so that it reapplies to the pet.</p><p>On Test, when you click Unabate to refresh it, it triggers the 10 second recast. Only after the 10 seconds have passed can you effectively refresh it.</p><p>In situations where your pet dies, followed by you casting Dimensional Storage, this ends up <em>hurting </em>the Conjuror in the long run.</p><p>Please just change it back to the way it was.</p></blockquote><p>Thank you.  I didn't know that unabate needed to be recast.  I recast conjuror's pact each time the pet is re-created.  I'll add unabate to the list. </p>