Quote:
Originally Posted by vicky_molokh
OK, it seems like mixing up optional and mandatory specialisations in this discussion is something that happens but is to be avoided, so . . .
|
FWIW, I've been making a point
not to conflate them. That said, I could see some merit in an Advantage that you can tie to a skill with mandatory specializations that lets you treat them as optional specializations.
Quote:
Originally Posted by vicky_molokh
Well, the idea of the consolidated list is to avoid something as fiddly as dozens of mandatory specialisations.
|
Right; which is why I mentioned (albeit briefly) that mandatory customization ought to be rare.
Quote:
Originally Posted by vicky_molokh
Actually, Techniques look like the way FATE does specialisation bonuses. Pricing is to be estimated at some level, of course.
|
Pricing is my main issue here: 1 point per +1 is too expensive relative to the cost of a skill. My own pricing for Techniques is to replace each Technique with a Perk that maxes out the Technique or adds +3 if the Technique has no maximum.
Quote:
Originally Posted by vicky_molokh
As for widening the scope of a skill - I have marked some skills with a * symbol in the note column (in the linked document, not in the post), which is meant to denote skill functions that only become available after taking some enabler trait, e.g. TbaM for cinematic combat skill functions. But I see that as a necessary evil.
|
“Necessary evil” is a good way to put it, yes.
Quote:
Originally Posted by vicky_molokh
Having e.g. a dozen scope-expander perks for a dozen ElOps specs would defeat the purpose of skill consolidation. The idea of skill consolidation is that you don't need to specify such fiddly details as whether you know sensors and sonar (which is somehow not a sensor), or one or the other of the two.
|
I know that, which is why I think it should be avoided when it’s reasonable to do so.