Reply to thread

Message

<blockquote data-quote="GMMichael" data-source="post: 7889721" data-attributes="member: 6685730">Morrus, what you've described sounds very similar to my game.&nbsp; So I can say with confidence: your idea is starting off on solid footing!&nbsp; Some thoughts:Why not just scale by level - a 10th level character can't exceed +10 skill points?If everybody gets &quot;spells,&quot; while the mage gets 1 HP and the warrior gets 4, then the mage won't be a very popular class.The opposed-roll thing works great.Classes-defined-by-skill works great, as long as your skill list makes sense.&nbsp; For example, you don't want a 10th-level rogue who's an ace at Pick Pockets but can't Distract someone to save her life (since they're related skills).&nbsp; Also, a 20th level mage might wonder why his Wealth is still garbage.I hope I'm not preaching to the choir <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f913.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":geek:" title="Geek&nbsp; &nbsp; :geek:"&nbsp; data-smilie="30"data-shortname=":geek:" />I faced that problem, and came up with this: establish a baseline set of skills.&nbsp; Each player-created skill needs to either branch off one of the baseline skills, or be comparable in scope (subject to GM approval).&nbsp; Also, since skills will likely interact with the rest of your rule set, you want to establish which skills do that and how that relationship works.&nbsp; E.g. if you have a hit points system, pay attention to which skills affect hit points.</blockquote>

[QUOTE="GMMichael, post: 7889721, member: 6685730"] Morrus, what you've described sounds very similar to my game. So I can say with confidence: your idea is starting off on solid footing! Some thoughts: Why not just scale by level - a 10th level character can't exceed +10 skill points? If everybody gets "spells," while the mage gets 1 HP and the warrior gets 4, then the mage won't be a very popular class. The opposed-roll thing works great. Classes-defined-by-skill works great, as long as your skill list makes sense. For example, you don't want a 10th-level rogue who's an ace at Pick Pockets but can't Distract someone to save her life (since they're related skills). Also, a 20th level mage might wonder why his Wealth is still garbage. I hope I'm not preaching to the choir :geek: I faced that problem, and came up with this: establish a baseline set of skills. Each player-created skill needs to either branch off one of the baseline skills, or be comparable in scope (subject to GM approval). Also, since skills will likely interact with the rest of your rule set, you want to establish which skills do that and how that relationship works. E.g. if you have a hit points system, pay attention to which skills affect hit points. [/QUOTE]

Verification