(Quote)
This may be better for a separate thread, but whatever. To the first part - kainet was hilariously broken. In group fights, it was common for me to enfeeble someone (which costs 61 kai), and get that kai back before I got balance back from…
What you describe is a (potential) problem with blackout in general, not anything specific to the clarity artifact, and that's how it needs to be addressed.
(Quote)
Not a change I would recommend/endorse, as it'd effectively make the lyre useless outside of some very niche scenarios, but we can discuss that when/if someone makes a lyre-related report.
(Quote)
I haven't played there in years, but I do look through their announces and such every now and then, and their defensive effects seem much stronger than ours, so I rather doubt that any population disparities are a result of the ability to …
Shamans indeed have their own problems, but that's for a different discussion. Passive/active affliction curing is definitely going to be a big topic during the next liaison round, that much is certain. I'm sure the specifics will be discussed to de…
A channel similar to LT would be interesting to see, as long as it's kept in check to ensure that it stays productive. Even LT can sometimes (very rarely, but still) devolve into arguments, and that's only 6 people - 20 people would be much worse.
(Quote)
Yup, that's exactly why I'm in the "in favour of giving every class their own viable method of shieldbreaking" group - it's the least intrusive solution.
You don't want to use Sunder, regardless on whether it's on a 33% or 50% chance. Get a hammer tattoo instead. Having to rely on that one sucks, yes, but it's the best option at present, and it's not as bad as it used to be, now that it's on a 2s equ…
Yup, looks like shield stops it properly on the liaison testing server, but not in-game. Reported - but you really should bug these things instead of hoping someone else will do so in Ankyrean Anguish - Aetolia-based RAGEComment by IlyonMay 2014
Vinelash does not bypass shield, as far as I can tell. Not sure why it did in that log.