WingOver
First Post
Silveras said:Uhm... No. How many "enforcement" options are there ? 2 ? or 20 ? Which things do *you* want to enforce ? Those kinds of things make the tools incredibly more difficult to write. You *do* want something this decade, right ?
Actually I was addressing the prereq restrictions specifically (for feats and prestige classes). Depending on how the software is designed I suppose prereqs could also apply to weapons/equipment or whatever. The solution perhaps is to allow prereq overrides on the feats/classes, not as a global setting.
Silveras said:Let's say you only have 2 modes. The program has to check its settings to see if it is supposed to enforce requirements. How often do you check ? Can the user change his/her mind after starting a character ? If so, you have to check pretty much every time s/he changes something.
Continuing with feat-level prereq overrides, couldn't you have a flag or something that indicates whether the feat prereq was overridden? This should be visible to the user upon load. And when the character changes, then yes, it would force another check throughout the entire character to see if prereqs are valid.
Silveras said:Let's say you have more than 2 settings.. 3.. maybe Feats get checked but PrCs don't. That pretty much doubles the workload of writing the code, and certainly doubles any testing that gets done. 4 settings ? Double again. 5 ? You get the picture.
As I said at the top of the post, you could have 1 setting as long as it was on the feat/class itself.
I know its easy enough to talk about, and the actual software design and implementation is incredibly difficult. But it can't be insurmountable.