View Full Version : Brainshock + Tyrannical Mind bug (confirmed on test & live!)
XFnarX
06-07-2008, 07:39 PM
<p>Heres what I am talking about (which has been posted by several other people);</p><p>"<i>After numerous test, YES this is a bug that ALWAYS happens. The Anguish line of spells (doesn't matter the level) is causing 2 triggers of the "Mind" lines to trigger, but only doing damage for 1 of the 2 triggers. AKA this happens.I cast Tyrannical MindI now have 3 triggersI cast Brain ShockI do damage & 1 shot of TMind triggers for damageI am now down to 1 Trigger on TMindThus 1 trigger is vanishingHere's some direct log file info...(1211847301)[Mon May 26 19:15:01 2008] You hit A stinging spined succulent with a mesmerizing blast of psionic energy!(1211847301)[Mon May 26 19:15:01 2008] A stinging spined succulent is mesmerized!(1211847303)[Mon May 26 19:15:03 2008] YOU try to confound a stinging spined succulent with Obliterated Psyche, but a stinging spined succulent resists.</i><i><b>(1211847309)[Mon May 26 19:15:09 2008] You concentrate on the Despotic Mind.(1211847309)[Mon May 26 19:15:09 2008] You are suddenly unable to think of anything but Fnar!</b>(1211847311)[Mon May 26 19:15:11 2008] You concentrate on the torments of Anguish.<b>(1211847311)[Mon May 26 19:15:11 2008] YOUR Despotic Mind critically hits a stinging spined succulent for 1739 mental damage. (Proc # 1)</b>(1211847311)[Mon May 26 19:15:11 2008] A stinging spined succulent snaps out of it.(1211847311)[Mon May 26 19:15:11 2008] Your action awakens a stinging spined succulent.(1211847311)[Mon May 26 19:15:11 2008] A stinging spined succulent is struck with a holy weapon!<b>(1211847311)[Mon May 26 19:15:11 2008] YOUR Brainshock critically hits a stinging spined succulent for 1326 mental damage. (Spell # 1)</b>(1211847311)[Mon May 26 19:15:11 2008] a stinging spined succulent's Needles hits YOU for 77 piercing damage.(1211847311)[Mon May 26 19:15:11 2008] YOUR Brainshock confounds a stinging spined succulent draining 1 111 mental of power.(1211847311)[Mon May 26 19:15:11 2008] a stinging spined succulent tries to pierce YOU with Needles, but YOU resist.(1211847311)[Mon May 26 19:15:11 2008] A stinging spined succulent is filled with Anguish!(1211847311)[Mon May 26 19:15:11 2008] You concentrate on the torments of Anguish.(1211847311)[Mon May 26 19:15:11 2008] You are filled with Anguish!(1211847312)[Mon May 26 19:15:12 2008] You prepare to muddle some thoughts.<b>(1211847312)[Mon May 26 19:15:12 2008] YOUR Hemorrhage critically hits a stinging spined succulent for 1519 mental damage. (Spell # 2)</b>(1211847312)[Mon May 26 19:15:12 2008] a stinging spined succulent's Needles hits YOU for 77 piercing damage.<b>(1211847312)[Mon May 26 19:15:12 2008] YOUR Despotic Mind critically hits a stinging spined succulent for 1835 mental damage. (Proc # 2)</b>(1211847312)[Mon May 26 19:15:12 2008] A stinging spined succulent is struck with a holy weapon!(1211847312)[Mon May 26 19:15:12 2008] A stinging spined succulent is totally confused!(1211847312)[Mon May 26 19:15:12 2008] You are no longer confused.(1211847313)[Mon May 26 19:15:13 2008] a stinging spined succulent tries to crush YOU, but misses.(1211847313)[Mon May 26 19:15:13 2008] You concentrate on an intense feeling of Melancholy.<b>(1211847313)[Mon May 26 19:15:13 2008] YOUR Asylum hits a stinging spined succulent for 1349 mental damage. (Spell # 3)</b>(1211847313)[Mon May 26 19:15:13 2008] a stinging spined succulent tries to pierce YOU with Needles, but YOU resist.(1211847313)[Mon May 26 19:15:13 2008] A stinging spined succulent is consumed by Melancholy!(1211847315)[Mon May 26 19:15:15 2008] a stinging spined succulent hits YOU for 1224 crushing damage.(1211847315)[Mon May 26 19:15:15 2008] A stinging spined succulent is struck with a holy weapon!(1211847316)[Mon May 26 19:15:16 2008] You concentrate on the power of Forced Hesitation.(1211847316)[Mon May 26 19:15:16 2008] A stinging spined succulent is mesmerized!Where's the 3rd proc? There is none. At this point Tyrannical Mind was no longer up. The 3rd trigger never went off and vanished do to the Brainshock being cast earlier.This is a confirmed bug. I have reported it, I suggest you do the same.</i></p><p>Was originally posted by me in <a rel="nofollow" href="http://forums.station.sony.com/eq2/posts/list.m?topic_id=418447" target="_blank">THIS</a> post.</p><p>K-THX-BIE!!</p>
KamidariTuibumbi
06-13-2008, 05:43 PM
Hopefully this is getting some attention... While you can work around it, it's annoying to have to remember not to click that one spell as one of the first two after "mind". <img src="/smilies/8a80c6485cd926be453217d59a84a888.gif" border="0" alt="SMILEY" />
XFnarX
06-14-2008, 03:10 PM
As of 1:00pm CST today, this is STILL a known bug. So I'm gonna go with no, it's not getting attention and being ignored.Another /bug report was sent.
Jesdyr
06-16-2008, 04:47 PM
Guess I will start bugging it as well <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" />
XFnarX
06-19-2008, 04:10 AM
Still active on test AND on live as of 12pm CST June 19th
Aeralik
06-19-2008, 04:27 AM
I have it fixed internally. Spells like that are really split into two. One is the hostile part which hits the target and the second is the part you get. Since its classified as hostile it then try to proc on you but you can't do that so it eats the trigger. To make a long story short though I did fix it and it should be part of gu47.
Rijacki
06-19-2008, 10:47 AM
One more month of counting my Mind procs before casting Shock. At least you found the problem and created a fix and now we have that to look forward to <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" />
KamidariTuibumbi
06-19-2008, 10:53 AM
Great, thanks! <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" />
Eriol
06-19-2008, 11:58 AM
<cite>Aeralik wrote:</cite><blockquote>To make a long story short though I did fix it and it should be part of gu47.</blockquote>To make a long story short, if this was EXTRA procs so we had more DPS, this would be hotfix priority. But because it hurts players, it's delayed to a Game Update.
Filthysnake
06-19-2008, 12:19 PM
<cite>Eriol wrote:</cite><blockquote><cite>Aeralik wrote:</cite><blockquote>To make a long story short though I did fix it and it should be part of gu47.</blockquote>To make a long story short, if this was EXTRA procs so we had more DPS, this would be hotfix priority. But because it hurts players, it's delayed to a Game Update.</blockquote>holy **** chanters never stop complaining
Mr. Dawki
06-19-2008, 01:42 PM
<cite>Eriol wrote:</cite><blockquote><cite>Aeralik wrote:</cite><blockquote>To make a long story short though I did fix it and it should be part of gu47.</blockquote>To make a long story short, if this was EXTRA procs so we had more DPS, this would be hotfix priority. But because it hurts players, it's delayed to a Game Update.</blockquote>You saw the patern too?
Aeralik
06-19-2008, 02:34 PM
<cite>Eriol wrote:</cite><blockquote><cite>Aeralik wrote:</cite><blockquote>To make a long story short though I did fix it and it should be part of gu47.</blockquote>To make a long story short, if this was EXTRA procs so we had more DPS, this would be hotfix priority. But because it hurts players, it's delayed to a Game Update.</blockquote>It's delayed since it required changes to how procs trigger. I think its safer to have one spell combination bugged but easily worked around instead of adding new ones that are potentially worse. Hotfixes are usually meant for things that are pretty cut and dry. Like quest X is supposed to update when Y is killed but it doesnt thats something easily hotfixed. System changes like this one rarely get hotfixed because its very broad and not something you can test thoroughly in a hotfix timeline which is where the danger and desire to play it safe comes in.
Mr. Dawki
06-19-2008, 03:03 PM
<cite>Aeralik wrote:</cite><blockquote><b></b>It's delayed since it required changes to how procs trigger. </blockquote><p>Now we know. None of us thought it would have been a fix quite that difficult. Thankyou for explaining.</p><p>PS: Go to the SK forums k thnx</p>
XFnarX
06-19-2008, 06:49 PM
<cite>Aeralik wrote:</cite><blockquote>I have it fixed internally. Spells like that are really split into two. One is the hostile part which hits the target and the second is the part you get. Since its classified as hostile it then try to proc on you but you can't do that so it eats the trigger. To make a long story short though I did fix it and it should be part of gu47.</blockquote>Thanks man! It's good to hear that this wasn't going unnoticed. Just being curious, was it the post that prompted the fix or was it all the /bug reports? (^_^)
Endorplasmic
06-25-2008, 12:12 AM
<cite>Aeralik wrote:</cite><blockquote><cite>Eriol wrote:</cite><blockquote><cite>Aeralik wrote:</cite><blockquote>To make a long story short though I did fix it and it should be part of gu47.</blockquote>To make a long story short, if this was EXTRA procs so we had more DPS, this would be hotfix priority. But because it hurts players, it's delayed to a Game Update.</blockquote>It's delayed since it required changes to how procs trigger. I think its safer to have one spell combination bugged but easily worked around instead of adding new ones that are potentially worse. Hotfixes are usually meant for things that are pretty cut and dry. Like quest X is supposed to update when Y is killed but it doesnt thats something easily hotfixed. System changes like this one rarely get hotfixed because its very broad and not something you can test thoroughly in a hotfix timeline which is where the danger and desire to play it safe comes in. </blockquote>Oh I so hope that this doesn't bring back lag... I will /wrists for sure <img src="/smilies/283a16da79f3aa23fe1025c96295f04f.gif" border="0" alt="SMILEY" />
vBulletin® v3.7.5, Copyright ©2000-2025, Jelsoft Enterprises Ltd.