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

Reply to thread

Message: <blockquote data-quote="Lanefan" data-source="post: 6045508" data-attributes="member: 29398">I think I already (unintentionally) answered that a few posts up from this one. <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=":)" />I maintain they are the same thing, or at least should be; as the PCs also need to be balanced against the game world.In other words, for any NPC the party interacts with I need to be able to answer "What makes this NPC tick in the event it suddenly either joins the party or attacks it?".  And it's way easier to answer that question quickly if NPCs and PCs are built the same way.Note this does not mean you need to stat everything out ahead of time; 95% of the time you'd be wasting effort.  But you always need to know what it is - peasant, 3rd-level Thief, militia type, whatever - as a starting point.  If need be, stat it up later or on the fly.Where the disconnect seems to be coming is there should and must be NO DIFFERENCE in the above case between a statted-up party member NPC and the same at-the-time-irrelevant NPC you met yesterday when she served your ale in the tavern*.  Just because she joins the party changes absolutely nothing in the game world - she is exactly what she was, and must be; otherwise internal consistency goes out the window.  Ditto for if she never joins the party - she still is what she is.* - e.g. Dragonlance's Tika WaylandLanefan</blockquote>

Verification