ToME: the Tales of Maj'Eyal

The object activation code doesn't check for confusion.

Assuming this gets fixed could we get a usable_while_confused flag check added into that code so we can bypass that filter for certain artifacts? (Like my suggested wintertide phial change would be a good candidate).

On this same note maybe all staff egos should inherit the use_no_silence = true flag so they can't be used while silenced or maybe arcane items in general should inherit this flag.

I dunno. It might make sense for staves to be usable while silenced (are they verbal? Who knows?)

But from a gameplay perspective, currently I tend to feel that status debuffs (especially ones that prevent you from acting or which severely limit your actions) are a bit overpowered and binary, wrecking you completely if you don't resist them. So I'd lean towards giving players the ability to activate staves while silenced, at least -- it's not like silence doesn't suck enough for a spellcaster already; leaving them with some way to fight back seems all right to me.

Runes can't be used while silenced. To me it makes sense that other arcane powered items would follow suit.

edge2054 wrote:Runes can't be used while silenced. To me it makes sense that other arcane powered items would follow suit.

I haven't reached a point in the game where silence comes up much yet, but it seems that the logical (well, pertinent) change to make in that situation is to not disable rune use when silenced unless it makes sense that one would need a voice to use a rune... The lore says that runes get inscribed onto the skin, so unless that is taken to mean that they're simply accessible like test answers scribbled onto your arm, they shouldn't be silence-able?

They activate with a command word

I bet I can guess the Command word for Rune : Shielding

"OhShi.."