...That is all I want from Next. Include skills as an option in the core rulebook and support them in future books. Then everyone wins. Those who want skills have them supported, and those who don't can easily ignore them.
Maybe I'm stupid.
I read the first 4+ pages of this thread under the impression that you wanted a skill system thrust upon all players and those who preferred a simpler system like ability checks would just have to deal. I can't help but think I'm not alone in having read it that way.
When these kinds of discussions happen, there's a real nebulous lexicon problem. "Basic," "Standard," Advanced," "core," "optional," "modular," et. al. get used in a sort of venn diagram of denotation, and it makes it really difficult for everyone to be on the same sheet of music. There's plenty of overlap, but none of these terms is strictly synonymous with any other. I'm almost as excited about this game going retail for having official nomenclature as I am to actually get and play with new books/rules.
Now on topic, I don't mind if the
optional skill rules are included in the
basic game, as long as they're optional. Truthfully though, I think that they're probably best suited to the
standard ruleset.
Basic is, in my understanding, supposed to be the version of DDN that you grab and go with, minimizing systemic options without infringing on gameplay ones. As such,
basic should probably exclude systems like skills and feats, as the developers have stated that the game is intended to be playable without them.
However, as has been discussed in previous threads, it will be very important for the
basic game to actually contain the kernels of the rules upon which the more complex versions of the game are built. That is to say, playing
basic and then
standard or
advanced should feel like you're still playing the same game, just with added rules/complexity. Otherwise, you're just going to have a bogus, introductory incarnation of the game, skipped by many and insufficiently preparing those who use it prior to playing the "real" game.
None of this really speaks to the term "core" though. Some use
core to mean
basic because of the aforementioned importance of
basic being the foundation upon which other rulesets are built. Others use
core to mean
standard because they believe that will be the default play style. Still others use
core to mean stuff that's not
optional, while others use it to describe whatever is included in the first book(s) of the edition. Since I don't really know what
core is, I won't even bother speculating what should and shouldn't be included therein.
As for the fear of adventure modules being a) too simple, or b) filled with useless stuff, it strikes me as all hat and no cattle. There's no reason that an adventure module can't just include "Strength DC: X, Climb DC: Y" or some such. We're not talking about half a book full of content here. Sure, interfacing an adventure module with a castle-building module would take up a little more space, but thats unlikely to be as common as with/without skills/feats/etc.