pawsplay
Hero
ThirdWizard said:I don't follow that at all.
And, Knowledge checks are generally for things you've never seen before, in game. The first time you come across a destrachan, for instance, to know that it has sonic attacks so you know to cast silence defensivly against it. If no one in the party has ever seen a destrachan, and fails the Knowledge check to know what it is, then one Player tell another Player to have his cleric cast silence, I don't see how that could be anything but a bad thing.
How is this different than having read or played through a module before and planning according to how you, as a player, know it is laid out instead of as your character would know?
But it has not been established you've never seen a destrachan. That is, until you roll the dice, I guess.
This could be a bad thing for reasons I've already covered. For instance, a dragon slayer with no related knowledge skill for dragons.
It's completely different from the module example, because it's perfectly reasonable for your character to have met a certain kind of creature, but not to know the layout of a tomb and have perfect foreknowledge of what it contains. That would essentially be cheating.
Bashing the lich with a magic morningstar is not cheating. All liches everywhere have the same weaknesses, and if your character knows how to fight liches, so be it. Now, if you, the player, aren't familiar with liches or don't remember, a Knowledge check will help. And only a knowledge check would supply specific in-game knowledge, like having heard of a particular lich with different defenses and abilities.
It's a choice whether your character knows what, say, a hydra is. That shouldn't hinge on a die roll. Similarly, the GM is free to inform you what any kind of creature is that he says you should recognize. For instance, the war troll is probably fairly obscure, but if your kingdom is being sacked by them, everyone knows what they look like, what they do, and what will and won't stop them.