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
*TTRPGs General
Pang of nostalgia for "light" stat blocks
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="Wil" data-source="post: 2780183" data-attributes="member: 3502"><p>Err..I'm not sure that I agree with how <em>ad-hoc</em> is being bantered about - the general usage that I'm aware of is when you are doing something based on the current situation and the results may not be applicable to any other situation. For example, when I issue an <em>ad-hoc query</em> against a database, that means I am executing a query that I have just written, for a specific purpose, that is not likely to be able to be used <em>without modification</em> for another purpose. So, even though I might be able to use the same query again to get the same kind of information, if I need to change the criteria manually it is ad-hoc. If I turn the same query into a <em>stored procedure</em>, where there are input and/or output parameters, it ceases to be ad-hoc even though the query is identical.</p><p></p><p>So, using this as a guideline, every time you make a ruling that is not covered explicitly by the rules (and I mean, word for word by the rules) it would be ad-hoc. This is not bad in any way, nor does it indicate that a game is "incomplete" (unless the ad-hoc rulings are a direct result of lack of rules or poorly designed rules).</p><p></p><p>To bring this back on topic, the idea of having to adjust NPCs <em>after the fact</em> (or, we could say, ad-hoc) is something that I think every GM needs to embrace at some point. I mean, everyone makes mistakes...what if I have a ranger NPC that needs to have hunting and trapping skills to help the party survive part of the adventure and <em>I forget to give the NPC the necessary skills</em>? Am I just to shrug and say, "Well, it's committed to a stat block now, guess I have to live with it"? Nope...and I don't ever have to let the players know about my mistake either. If I overlook a feat, or a Charm, or a power that an NPC <em>should have had</em> but I forgot and the oversight becomes obvious during play - damn straight I'm going to give it to them.</p><p></p><p>Now, in play groups where there is a adversarial relationship between GM and players this may not work and you might need everything spelled out for NPCs. I'm glad I won't play in groups like that, partly because of that reason.</p></blockquote><p></p>
[QUOTE="Wil, post: 2780183, member: 3502"] Err..I'm not sure that I agree with how [i]ad-hoc[/i] is being bantered about - the general usage that I'm aware of is when you are doing something based on the current situation and the results may not be applicable to any other situation. For example, when I issue an [i]ad-hoc query[/i] against a database, that means I am executing a query that I have just written, for a specific purpose, that is not likely to be able to be used [i]without modification[/i] for another purpose. So, even though I might be able to use the same query again to get the same kind of information, if I need to change the criteria manually it is ad-hoc. If I turn the same query into a [i]stored procedure[/i], where there are input and/or output parameters, it ceases to be ad-hoc even though the query is identical. So, using this as a guideline, every time you make a ruling that is not covered explicitly by the rules (and I mean, word for word by the rules) it would be ad-hoc. This is not bad in any way, nor does it indicate that a game is "incomplete" (unless the ad-hoc rulings are a direct result of lack of rules or poorly designed rules). To bring this back on topic, the idea of having to adjust NPCs [i]after the fact[/i] (or, we could say, ad-hoc) is something that I think every GM needs to embrace at some point. I mean, everyone makes mistakes...what if I have a ranger NPC that needs to have hunting and trapping skills to help the party survive part of the adventure and [i]I forget to give the NPC the necessary skills[/i]? Am I just to shrug and say, "Well, it's committed to a stat block now, guess I have to live with it"? Nope...and I don't ever have to let the players know about my mistake either. If I overlook a feat, or a Charm, or a power that an NPC [i]should have had[/i] but I forgot and the oversight becomes obvious during play - damn straight I'm going to give it to them. Now, in play groups where there is a adversarial relationship between GM and players this may not work and you might need everything spelled out for NPCs. I'm glad I won't play in groups like that, partly because of that reason. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*TTRPGs General
Pang of nostalgia for "light" stat blocks
Top