Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="ECMO3" data-source="post: 9358040" data-attributes="member: 7030563">Precedent for rulings is typically for things that are not covered or are unclear in the rules.  If you say your game is RAW on spells or multiclassing and change that just to spite something a player put in their PC build because you don't like it, that is not setting a precedent.   Then do the right thing and live with it, and remember it for the next session 0. No it doesn't.  If a player comes up with a combination that automatically one-shots every enemy in the game you play the campaign to the end and implement a rule in the next one.It is just flat wrong to lead players to believe they can do something and then take it away because you did not understand how it works ahead of time.Now this is completely different.  TBH when a player researches a new spell I ask them what they want it to do and level they think it should be and more often than not they make it underpowered for the level. Most cases player created spells are pretty weak and I would not let them be even above average for their spell level. For example I had a PC that wanted to use a lightsaber and she made a spell called Sunbird's Lightsaber.  It was similar to shadowblade but used a spell casting ability, was not finesse, could not be thrown, dealt Radiant damage and did not give advantage in darkness.  So overall weaker than Shadowblade.  She said she thought it should be 3rd level and I thought it was underpowered at that level but I let her go with it.</blockquote>

Verification