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
*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
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
Community
General Tabletop Discussion
*Dungeons & Dragons
ludonarrative dissonance of hitpoints in D&D
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="FrogReaver" data-source="post: 7845213" data-attributes="member: 6795602"><p>Yep that's a recap.</p><p></p><p></p><p></p><p>Yes. The explanation is what I gave you in the post above. To summarize,</p><p><span style="font-size: 15px"><span style="font-family: 'Segoe UI'"><span style="color: rgb(20, 20, 20)"> In the original abstraction the subordinate concepts don't all need to be equal or even present in any instance of losing hp. In yours they do. Essentially, that difference has a direct impact on narratives that can be established with each abstraction. </span></span></span></p><p></p><p></p><p></p><p>Kind of. I shouldn't have to emphasize this fact but I guess I do. Game rules aren't typically written to tell you how things don't work. The most I can provide you are the rules for the abstraction 5e is using - which make no mention that all the subordinate concepts of the systems hp abstraction must be equal in every instance of hp loss. In fact we can find rules that suggest but never explicitly say the exact opposite - such that creatures normally show signs of battle when below half hp.</p><p></p><p></p><p></p><p>Why would I need to explain that? Physical durability is included in the abstraction of hp. Characters most certainly can have their physical durability damaged as part of their hp loss.</p><p></p><p></p><p></p><p>Same explanation as above.</p><p></p><p></p><p></p><p>That doesn't change the abstraction.. A single instance of hp loss can be narrated using any part of 5e's abstraction.</p><p></p><p></p><p></p><p>You are mixing up 2 concepts.</p><p></p><p>1. There is the concept of a specific abstraction, which has a specific structure and specific properties itself and includes specific subordinate concepts.</p><p></p><p>2. Then there is the concept of using one of those subordinate concpets to narratively explain an instance of the abstract hp mechanic.</p><p></p><p>You seem to be conflating these two things quite a bit. For example, the portion of your post I quoted right above this - you are asking why we can't 2 without changing 1. But no one is saying that 2 can't be done without changing 1. In fact, That's what's making this so hard to discuss, you keep bringing up examples of changing 2 as if it has anything to do with 1 at all.</p><p></p><p></p><p></p><p>We can decide that ourselves (in the context of the narrative, not in the context of the abstraction). What we cannot do is eliminate a unique subordinate concept from the abstraction without changing the abstraction. But that doesn't mean that in each narrative instance of hp loss that every subordinate concept must be present, only that they exist as possibilities that can explain any instance of hp loss.</p><p></p><p><strong>In Conclusion,</strong></p><p></p><p>I guess it might be best to explain it this way. The HP Abstraction includes all subordinate concepts and combinations of those concepts. Some subset of those concepts and combinations of them <strong>can</strong> be used in narrative to explain the hp loss.</p><p></p><p>To remove subordinate concepts or combinations of concepts from the abstraction then changes the abstraction - essentially reducing the set of possible explanations that can be used to narrate hp loss. To remove them in a specific narrative explanation has no effect on the abstraction.</p><p></p><p>To add a subordinate concept to an abstraction still allows for the subordinate concepts (and combinations of them) that were available before but also new ones that weren't available before. To add a subordinate concept to a specific narrative explanation has no effect on the abstraction (unless it was a concept not originally included in the abstraction to begin with).</p></blockquote><p></p>
[QUOTE="FrogReaver, post: 7845213, member: 6795602"] Yep that's a recap. Yes. The explanation is what I gave you in the post above. To summarize, [SIZE=4][FONT=Segoe UI][COLOR=rgb(20, 20, 20)] In the original abstraction the subordinate concepts don't all need to be equal or even present in any instance of losing hp. In yours they do. Essentially, that difference has a direct impact on narratives that can be established with each abstraction. [/COLOR][/FONT][/SIZE] Kind of. I shouldn't have to emphasize this fact but I guess I do. Game rules aren't typically written to tell you how things don't work. The most I can provide you are the rules for the abstraction 5e is using - which make no mention that all the subordinate concepts of the systems hp abstraction must be equal in every instance of hp loss. In fact we can find rules that suggest but never explicitly say the exact opposite - such that creatures normally show signs of battle when below half hp. Why would I need to explain that? Physical durability is included in the abstraction of hp. Characters most certainly can have their physical durability damaged as part of their hp loss. Same explanation as above. That doesn't change the abstraction.. A single instance of hp loss can be narrated using any part of 5e's abstraction. You are mixing up 2 concepts. 1. There is the concept of a specific abstraction, which has a specific structure and specific properties itself and includes specific subordinate concepts. 2. Then there is the concept of using one of those subordinate concpets to narratively explain an instance of the abstract hp mechanic. You seem to be conflating these two things quite a bit. For example, the portion of your post I quoted right above this - you are asking why we can't 2 without changing 1. But no one is saying that 2 can't be done without changing 1. In fact, That's what's making this so hard to discuss, you keep bringing up examples of changing 2 as if it has anything to do with 1 at all. We can decide that ourselves (in the context of the narrative, not in the context of the abstraction). What we cannot do is eliminate a unique subordinate concept from the abstraction without changing the abstraction. But that doesn't mean that in each narrative instance of hp loss that every subordinate concept must be present, only that they exist as possibilities that can explain any instance of hp loss. [B]In Conclusion,[/B] I guess it might be best to explain it this way. The HP Abstraction includes all subordinate concepts and combinations of those concepts. Some subset of those concepts and combinations of them [B]can[/B] be used in narrative to explain the hp loss. To remove subordinate concepts or combinations of concepts from the abstraction then changes the abstraction - essentially reducing the set of possible explanations that can be used to narrate hp loss. To remove them in a specific narrative explanation has no effect on the abstraction. To add a subordinate concept to an abstraction still allows for the subordinate concepts (and combinations of them) that were available before but also new ones that weren't available before. To add a subordinate concept to a specific narrative explanation has no effect on the abstraction (unless it was a concept not originally included in the abstraction to begin with). [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Dungeons & Dragons
ludonarrative dissonance of hitpoints in D&D
Top