Oryan77 said:
Keeping them from finding out durations & other properties of spells their PC's have never encountered & the player doesn't know by memory is something to be frowned upon?
This is the first time in the thread that you've included "their PCs have never encountered" as a restriction on what rules they're prohibited from looking up.
If I'm playing a fighter, and I (as a player) recognise that the NPC just cast Ray of Enfeeblement, and I know that the first-time-wizard player probably doesn't, I (as a player) would tell the wizard's player "Probably Ray of Enfeeblement", since it's a spell on his character's list. If the wizard tells my fighter about the spell, I'll happily act on it directly next time it happens.
If I'm playing a mid-level wizard, and I (as a player) recognise that the NPC just cast Wall of Fire, I'll assume that my character can act on that knowledge. It's on my list. The Spellcraft check, however, might tell me that the NPC actually cast Major Image, or Mordenkainen's Flaming Barrier of Death. If I don't bother with the Spellcraft check, I'd be startled if I were told that I couldn't look up Wall of Fire, though, since I'm playing a wizard who can cast the spell.
If I'm playing a wizard, and I (as a player) recognise that the NPC just cast Wall of Thorns, I'll ask the DM what my +14 in Spellcraft and +12 in Knowledge (Arcana) tell me about it. Unless my PC's seen my buddy the druid cast the same spell before, and knows how it works already.
I guess the line under Spellcraft in the PHB that gives a 20 + spell level DC check for "Identifying a spell that's already in place and in effect" is a bogus check because a player has a PHB infront of him and should be allowed to use the PHB so his PC can avoid a spellcraft check?
Identifying a spell tells you what the spell is. Flicking through the PHB tells you what it might be... and should be filtered through character knowledge.
If the player's have access to use a spell (it's in their spellbook, their deity grants it to them at their level, or a sorcerer knows it), I don't care if they look in the PHB to review the stats on the spell.
This was the information missing from everything you've said so far.
Man, I'm really not seeing why asking players to not look up spells they don't know during combat is a bad thing. People agree that metagaming is unavoidable, but me trying to keep metagaming down a bit is a bad thing? Player's already know so much out-of-game info, why is it bad form to try & keep the out-of-game info down?
Prior to this post, your policy read to me as throwing the baby out with the bathwater. The PHB contains information the characters don't know, therefore the players can't look
anything up.
You've since clarified that you don't mind them looking up things the PCs do know.
After still being baffled from your response, the only thing I can think of is that we have different interpretations of what "identify a spell already cast" actually means. Perhaps you just think it refers to when a caster buffs himself and PC's can't visually tell what he cast.
If I'm a mid-level wizard, and someone casts a spell that creates a cloud of mist, I don't feel that it's metagaming for me to assume it's Obscuring Mist, Fog Cloud, Stinking Cloud, Cloudkill, Acid Fog, or Solid Fog... or possibly an Image spell. Or to look up the descriptions of those spells.
If I succeed at a spellcraft check, I expect to know that it's Stinking Cloud.
Now, the potential metagaming issue is if I roll a 25 on my "Identify a spell in place" Spellcraft check, and am told "You don't know what it is". I can deduce from that that it's
probably Acid Fog, since a 25 is sufficient to identify the others. But the PC is not privy to the number on the d20.
But is it metagaming if the fighter attacks the BBEG, rolls a 19 (total 31), and misses, for him to say "Uh, gang, we're in trouble"? Does the fighter know the difference between a 31 and a 14?
-Hyp.