Reply to thread

Message: <blockquote data-quote="DrSpunj" data-source="post: 1513522" data-attributes="member: 994">Oo, brutal. Good luck with the new job! <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile    :)"  data-smilie="1"data-shortname=":)" />When you get a chance, can you provide links to the new/updated files I sent you so others can download them? Right. I totally agree! It's been quite awhile since I started this thread, and I haven't read back through it recently, so I'm not sure if my past posts gave that impression (or said that exact thing!) or not. I can only say that, after working on this for quite some time my goal is to allow someone to build whatever type of balanced character they want to. If they want Barbarian DR without Rage or Uncanny Dodge, and want to put that with Heavy Armor proficiency and an increased Defense & d12 HD, more power to them!If my CB system works the way I hope it does, as long as they have the points to get those abilities things should work out fine.The devil's in the details though. I agree that Sneak Attack is too powerful to be taken every level, but I think it's okay to take every other level (like the Rogue). So how to keep someone from taking it every level?My current approach was to directly tie it to character level. I could also see a requirement like "your BAB has to increase by at least +1.5 before you can take this feat again". You could limit it to only be taken at odd levels if you wanted to.All of those keep you from taking it every level, but the first one (my way) bugs ouini, I think, because someone could it take it for the first time at 3rd level and get it twice. If they had saved some points they could take it for the first time at 5th level and get it three times! That really doesn't bother me. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f609.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=";)" title="Wink    ;)"  data-smilie="2"data-shortname=";)" /> That PC paid a pretty big opportunity cost in saving those points to splurge all at once rather than buying abilities he could use right away (assuming he lived long enough to spend them!).In the 3.0 DMG I remember reading a section about when to ask for a Save vs when to ask for an Ability check. I'm not sure if that section is in the 3.5 DMG or not, but I really liked what that section had to say. At the core it came down to, "If you're trying to avoid something, it's a Save. If you're trying to accomplish something, it's an Ability check."I tried applying that concept where I could in the Prereqs I came up with for the class ability feats. Evasion only kicks in when you're making a Reflex save, so I gave it a Reflex save prereq. DR is about avoiding damage, so I gave a Fort save prereq.Rage I struggled with a bit. It allows you to do something, so I thought about linking it to Constitution, but with the fatigue/exhaustion and Tireless Rage abilities I came to see Rage as something that pretty much anyone can do, most people just don't have the stamina/fortitude to resist tearing themselves up (and perhaps even killing themselves) doing it. Here I could probably be swayed to add or change it to a Constitution requirement, but I really liked how the Fort save POV allowed me to scale the prereq for the higher level abilities.Thanks.DrSpunj</blockquote>

Verification