Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="Essenti" data-source="post: 5870605" data-attributes="member: 100205">MINI-RANTMainly posting this because so many people who post on here seem to have a their own definition of what a modular design actually entails:<a href="http://en.wikipedia.org/wiki/Modular_design" target="_blank">Modular design - Wikipedia, the free encyclopedia</a>Those of us who regularly use modular design patterns understand the importance of a tight and simple CORE. You design the CORE around the most basic components that are required to achieve the job at the most minimal level while paying very close attention to the interfaces that allow extensible modules to be integrated on top of the CORE. The CORE should function the  same regardless of the modules added on, they are the baseline mechanic that all modules will use at some level. Any add on module can be swapped out for a different module as a drop in replacement and meeting, form fit and function requirements, and should not break the CORE. You modify what the CORE can achieve by adding on modules, but the you don't actually change the CORE.This CORE that WoTC is talking about is not the core books --it is the basic framework that the core books will use. So many people seem to be assuming that the features they are saying they will support are all going in the CORE. This is most likely NOT the case, and I can understand your fear if that optional stuff was in the CORE, but it is not a robust modular design if all that junk was stuffed into the CORE. The CORE should be as simple as possible, with an elegant and robust interface for adding modules. That is all.Using the 4/4 in the CORE seems like a solid baseline to me. Saying that 4/4 is all that is going to be in the core books, no, no that is just a plain terrible idea. The CORE will be present in the books, but so will various add on modules to extend the game in a great number of directions to support a particular style of play, including other classes ...oh my!Things like healing surges or whatever non-magical healing they are talking about should not be in the CORE, although I do believe those modules should be in the core rule books. Understand that the CORE and the core rule books are not synonymous. That seems to be the big disconnect here. The CORE will be contained in those books, but those books should contain all the necessary add on modules to extend the type of play to something that feels like  BECMI, 3.5e, 4e, Pathfinder-esque, or some type of hybrid./MINI-RANTOkay... mini-rant complete.  Thank you for your time!<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=":)" /></blockquote>

Verification