Blackout being super easy to afflict with by multiple classes but only having a cure that works on a 20 second timer is another retarded mechanic, yes.

Edit:: At least in Achaea you can learn a skill to halve the timer. Here you are stuck with 20 second allheale or bust.

Edit:: fixed to correct times. Point still stands that blackout is given far to freely and easily with a long balance cure.

You assume I went through the whole thread lookin for things, heh.

Cauldrons was part of regen thing, which I guess isnt valid anymore.

Totem power = ascendants = imbalances of their own.

Drink was entirely unrelated to streamlining.

DMP means alot. Didnt we just balance out damage? Isnt doing 100 damage also something to balance? Hard to balance damage if one group takes 1400 and another takes 500 isnt it? (made up numbers).

@gregori: I think blackout is vital to some cases like hexes, angel combos, and dreamweaver masking affs. No blackout should be extremely long though. Allheale balance is 20 seconds not 40 though....

Fixed times, and short blackouts don't make it any better, it just means you sip allheale and have to wait 20 seconds while being blacked out 2 - 3 more times in that period with no cure for it.

People diag on me when they get blacked out and all my work gets wasted

No, I mean the zerg train is way harder to survive when you're being choked. Odds go from exciting and very slim to impossible

Wait, if releasing shadows doesn't do that then what does it do? I've never used Night and I assumed the AB was accurate.

Allows for drink/choke/bonds.

Well yeah, I always assumed it had some passive effect. Guess we can stop keeping em released for the duration of every domoth... or not, as long as it's free. Whateeeev.

... releasing them activates Drink. Which is an important defense.

It's not like they're ever being released to stop regeneration (because they don't)-- it's for the other effects!

Blackout is usually 2s or less, they arent generally bad.

Worst two are dreamweaver (havent seen this one for a bit) and hexes (only causes hexes is on demand and really short eq)

I just learned today (no laughing) that there are 4 (?) possible message for every warrior attack, depending on if they use hack, slash, slice or strike. Not sure if that's something worth considering, but I definitely had to go through my system and change every single warrior trigger to account for that.

What about crush/lunge/sweep?

And normal swings?

Also, there's a lot more than those: Hack, Slice, Swipe, Slash, Smite, Bash, Pound, Strike is the full list of warrior targeted. Plus the messages for untargeted swings / jabs (bashing attacks). Also, some of these are things like "pound left, pound right" and "smite down, smite up" which means 2x messages for the same command.

...cry. You aren't making this any less daunting.

Ok. I'm just gonna put a bloody * in and hope it's only the single word that changes.

It's not.

Hack up has a "drooping weapon before hacking upwards with *weapon name*" or some such like that, for example. The first 3-4 words change, then the rest of it is the same from there.

You do what I've always done: break up the warrior attack into parts and trigger the parts. There's the initial swing of the weapon, followed by the hit/miss, and the next line may be a poison or some other effect.

I don't want to give up my warrior flavor messages for anything in the world, and they're much more straightforward than so many other things.

I'm not saying kill the messages. I'm just griping that it can't say "hits" instead of hack/slash/strike/pwns/whatever. I'll have to have a bunch of warriors hit me with stuff to be sure I'm getting all of the different variations, I guess.

Can someone explain why allowing people with nightsight to use certain commands such as exits or observe or inv in choke is not a good sollution?

Because seeing where to go doesn't do anything to help you. People who have problems getting away from SD's don't have it because they don't know which way to go.

If that's your gripe, then you simply need a single word wildcard to take care of it! Wow, that was easy. No lengthy testing, no additional triggers or code.

That was what I initially said, with the *. But Xenthos said that some of the messages are more than just that single word! That's why I was like *panic!*