Menu
News
All News
Dungeons & Dragons
Level Up: Advanced 5th Edition
Pathfinder
Starfinder
Warhammer
2d20 System
Year Zero Engine
Industry News
Reviews
Dragon Reflections
White Dwarf Reflections
Columns
Weekly Digests
Weekly News Digest
Freebies, Sales & Bundles
RPG Print News
RPG Crowdfunding News
Game Content
ENterplanetary DimENsions
Mythological Figures
Opinion
Worlds of Design
Peregrine's Nest
RPG Evolution
Other Columns
From the Freelancing Frontline
Monster ENcyclopedia
WotC/TSR Alumni Look Back
4 Hours w/RSD (Ryan Dancey)
The Road to 3E (Jonathan Tweet)
Greenwood's Realms (Ed Greenwood)
Drawmij's TSR (Jim Ward)
Community
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Resources
Wiki
Pages
Latest activity
Media
New media
New comments
Search media
Downloads
Latest reviews
Search resources
EN Publishing
Store
EN5ider
Adventures in ZEITGEIST
Awfully Cheerful Engine
What's OLD is NEW
Judge Dredd & The Worlds Of 2000AD
War of the Burning Sky
Level Up: Advanced 5E
Events & Releases
Upcoming Events
Private Events
Featured Events
Socials!
EN Publishing
Twitter
BlueSky
Facebook
Instagram
EN World
BlueSky
YouTube
Facebook
Twitter
Twitch
Podcast
Features
Top 5 RPGs Compiled Charts 2004-Present
Adventure Game Industry Market Research Summary (RPGs) V1.0
Ryan Dancey: Acquiring TSR
Q&A With Gary Gygax
D&D Rules FAQs
TSR, WotC, & Paizo: A Comparative History
D&D Pronunciation Guide
Million Dollar TTRPG Kickstarters
Tabletop RPG Podcast Hall of Fame
Eric Noah's Unofficial D&D 3rd Edition News
D&D in the Mainstream
D&D & RPG History
About Morrus
Log in
Register
What's new
Search
Search
Search titles only
By:
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
Upgrade your account to a Community Supporter account and remove most of the site ads.
Community
General Tabletop Discussion
*Dungeons & Dragons
Why Balance is Bad
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Manbearcat" data-source="post: 6240434" data-attributes="member: 6696971"><p>As a GM, this is the aspect of balance that is most important to me. To wit, an analogy that likely won't work for some folks (while I find instructive):</p><p></p><p>A forensic engineer investigates a site to discern the cause and origin of a currently unknown event. Going in, he will (i) have a considerable breadth of knowledge of physical phenomenon (a forensic knowledge base) to call upon, (ii) robust experience and training in the component parts of the applied sciences that are relevant to what he is investigating, and (iii) enough detailed information on the present event to propose a few initial surmises (hypotheses) as to what the cause and origin of the event was. He will then look for (iv) independent lines of evidence to support or render null his various surmises. Finally, through this process and these resources (v) he will reach a conclusion and submit his report/findings for peer review (formal playing of the encounter challenge).</p><p></p><p>A GM has a key role as a forensic engineer at the table. He is deconstructing challenges from a thematic idea into their component mechanical parts. He is then reconstructing those component mechanical parts into a machine (the encounter challenge) such that he should have a robust understanding of precisely what it is that he has created and precisely how it will work. The more functional and transparent the process is, the more precise his understanding will be (much like the forensic engineer investigating for cause and origin). The more precise his understanding will be, the more likely his forensic undertaking will be robust. Obviously the opposite also stands. The more dysfunctional and opaque the process, the less precise his understanding will be, and the more sensitive the final product will be to any unforeseen/un(mis)qualified variable of input...leading to variance/aberration in the final product more often than he would like.</p><p></p><p>Any deep variance (imbalance), especially of the unquantified or inappropriately quantified variety, will lead to "GM as poor forensic engineer" which will lead to a proportionate number of anticlimactic challenges for the PCs. BBEGs may turn into walkovers and sentry ganking may turn deadly. As a 25 + year GM, I've dealt with both of those scenarios and I think I can speak for most GMs in saying we aren't a fan of either of those outcomes.</p><p></p><p>Players won't have a forensic level of understanding of what they are undertaking. It will be well-informed by the fiction and by their own understanding of the mechanical processes at work coupled with their PC resources (and their allies'). However, GMs most certainly should have a forensic-level understanding of their encounters and the encounter building process and component parts (of which accurate PC<img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f61b.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":P" title="Stick out tongue :P" data-smilie="7"data-shortname=":P" />C and Monster<img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f61b.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":P" title="Stick out tongue :P" data-smilie="7"data-shortname=":P" />C quantification is imperative) should support that forensic-level understanding.</p></blockquote><p></p>
[QUOTE="Manbearcat, post: 6240434, member: 6696971"] As a GM, this is the aspect of balance that is most important to me. To wit, an analogy that likely won't work for some folks (while I find instructive): A forensic engineer investigates a site to discern the cause and origin of a currently unknown event. Going in, he will (i) have a considerable breadth of knowledge of physical phenomenon (a forensic knowledge base) to call upon, (ii) robust experience and training in the component parts of the applied sciences that are relevant to what he is investigating, and (iii) enough detailed information on the present event to propose a few initial surmises (hypotheses) as to what the cause and origin of the event was. He will then look for (iv) independent lines of evidence to support or render null his various surmises. Finally, through this process and these resources (v) he will reach a conclusion and submit his report/findings for peer review (formal playing of the encounter challenge). A GM has a key role as a forensic engineer at the table. He is deconstructing challenges from a thematic idea into their component mechanical parts. He is then reconstructing those component mechanical parts into a machine (the encounter challenge) such that he should have a robust understanding of precisely what it is that he has created and precisely how it will work. The more functional and transparent the process is, the more precise his understanding will be (much like the forensic engineer investigating for cause and origin). The more precise his understanding will be, the more likely his forensic undertaking will be robust. Obviously the opposite also stands. The more dysfunctional and opaque the process, the less precise his understanding will be, and the more sensitive the final product will be to any unforeseen/un(mis)qualified variable of input...leading to variance/aberration in the final product more often than he would like. Any deep variance (imbalance), especially of the unquantified or inappropriately quantified variety, will lead to "GM as poor forensic engineer" which will lead to a proportionate number of anticlimactic challenges for the PCs. BBEGs may turn into walkovers and sentry ganking may turn deadly. As a 25 + year GM, I've dealt with both of those scenarios and I think I can speak for most GMs in saying we aren't a fan of either of those outcomes. Players won't have a forensic level of understanding of what they are undertaking. It will be well-informed by the fiction and by their own understanding of the mechanical processes at work coupled with their PC resources (and their allies'). However, GMs most certainly should have a forensic-level understanding of their encounters and the encounter building process and component parts (of which accurate PC:PC and Monster:PC quantification is imperative) should support that forensic-level understanding. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Dungeons & Dragons
Why Balance is Bad
Top