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
*TTRPGs General
Do you Trust Your Players?
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="Jack7" data-source="post: 4659390" data-attributes="member: 54707"><p>I think in this case Hussar may have been getting at the point of "what responsibilities do you entrust to your players" rather than do you trust them to cheat or not to cheat. He can correct me of course, if I am wrong.</p><p></p><p>My personal theory of leadership and command (and control in a situation like this, as referee) is that implicit in the job of leadership and command is the responsibility to train and to shift obligation from a tightly controlled centralized authority to a more flexible and fluid style of multi-functional tactical capabilities that can operate from any point of command.</p><p></p><p>That means an organization, even a group of gamers, can shift more rapidly to successfully address any necessary pressure or demand presented by any anticipated, or even unforeseen obstacle or problem. (As an example I tell my wife all of the time, "It is not my job as husband and leader of this family to control all affairs of this household, it is my job to train everyone else so that if I'm not around or if I get killed, it will run just like, if not better, than if I was here." A commander doesn't control all things, he trains and then delegates. And the better the commander he is, the less he has to control.)</p><p></p><p>Therefore, if that is the case, and what Hussar was shooting at, I encourage my players to do the following kinds of things:</p><p></p><p>Devise their own orders of battle, march, communications and so forth.</p><p></p><p>Devise their own tactical and combat formations.</p><p></p><p>Keep their own records - they do not ask me "what so and so NPC said that time we met on the road to Gallipolis?" I say, "if you didn't write it down, then use your memory. I'm not your personal Wizard of Oz, and I don't think for you or tell you what you should or shouldn't know." Know it or don't, it's not my job to know it for you.</p><p></p><p>I let them keep up with their own character details like Armor class, ammunition counts, etc. They have to keep record and write it down, and I will occasionally check, but that is their job, not mine. I'm not a character policeman, I just regulate on rare occasion.</p><p></p><p>Mapping is their job. I do not map for them, show them maps, or remind them of how they have moved. If they get mapping guidance during the game then they find a map or draw their own.</p><p></p><p>Leadership - they arrange how the party operates and who is in it and what skills they need as a team and as individuals.</p><p>they handle their own leadership disputes and affairs.</p><p></p><p>We play with very flexible rules, but if there is a rules debate then somebody in the party is appointed "Look up Man." I hate rule-a-ramas, and I hate being the guy carrying around a bunch of textbooks. So I give that steamy pile of crap to them. I regulate violations, and interpret flexibilities, but I'm not a freaking lawyer, I'm a DM (a judge). So somebody in the party gets to be the lawyer, not me. Like it or not. Also I don't look up spells, powers, etc. they do and if necessary read them out loud so we all understand them.</p><p></p><p>Inventions and innovations - They are responsible for this. I will say this will work, or this will not as it is currently designed, or let's test this, but it is their invention and experiment, I just test it. This encourages innovation on their part. They want some advantage, they have to figure out what it is and how to make it work.</p><p></p><p>I encourage them to devise their own spells, capabilities, and skills. I encourage the players to use their own real world skills, such as tracking ability or survival skills or language skills and adopt them to their character in-game. If the player can speak Latin then so can their character. If the player can recognize a bear track then so can the character. If the player knows how to find water, so does the character.</p><p></p><p>Seek out their own experts and create their own networks. If they have an in-game question about who the last King of Syria was and what he did in Antioch then they go to a monk, an historian, a sage, or somebody else who knows. Not to me, I don't tell them. They do their own research, and they have learned over time to seek out more than one source of information just to make sure what they learn is accurate. Same with creating networks. Over time they have learned it is better to have a reliable, consistent network of people they can trust than to just go to a new stranger everytime they need something. But they have to build their own networks, it's not my job to make others interested in working with them. They do their own research, and discover their own answers, in and out of game.</p><p></p><p>Buy their own supplies and run their operation like a business. If they need something that is not available then they have to design it and get someone to build it for them and it may not be done right the first time it is tried. They don't tell me, "I need something that will do this, and who do I go to?" I say, "well then, you design it and build it, or you find someone who can. That's not my job."</p><p></p><p>I've found stuff like that takes a ton of work off me, inspires their creativity and innovation, encourages them to invent and design, and makes for a much more interesting milieu than if I invented everything. Because I simply cannot think of everything.</p><p></p><p>And besides my job as referee or game leader is not to control them but to guide them and then to turn them loose if possible. I give the mission parameters, but they have to make it happen. And they have to figure out how to make it happen.</p></blockquote><p></p>
[QUOTE="Jack7, post: 4659390, member: 54707"] I think in this case Hussar may have been getting at the point of "what responsibilities do you entrust to your players" rather than do you trust them to cheat or not to cheat. He can correct me of course, if I am wrong. My personal theory of leadership and command (and control in a situation like this, as referee) is that implicit in the job of leadership and command is the responsibility to train and to shift obligation from a tightly controlled centralized authority to a more flexible and fluid style of multi-functional tactical capabilities that can operate from any point of command. That means an organization, even a group of gamers, can shift more rapidly to successfully address any necessary pressure or demand presented by any anticipated, or even unforeseen obstacle or problem. (As an example I tell my wife all of the time, "It is not my job as husband and leader of this family to control all affairs of this household, it is my job to train everyone else so that if I'm not around or if I get killed, it will run just like, if not better, than if I was here." A commander doesn't control all things, he trains and then delegates. And the better the commander he is, the less he has to control.) Therefore, if that is the case, and what Hussar was shooting at, I encourage my players to do the following kinds of things: Devise their own orders of battle, march, communications and so forth. Devise their own tactical and combat formations. Keep their own records - they do not ask me "what so and so NPC said that time we met on the road to Gallipolis?" I say, "if you didn't write it down, then use your memory. I'm not your personal Wizard of Oz, and I don't think for you or tell you what you should or shouldn't know." Know it or don't, it's not my job to know it for you. I let them keep up with their own character details like Armor class, ammunition counts, etc. They have to keep record and write it down, and I will occasionally check, but that is their job, not mine. I'm not a character policeman, I just regulate on rare occasion. Mapping is their job. I do not map for them, show them maps, or remind them of how they have moved. If they get mapping guidance during the game then they find a map or draw their own. Leadership - they arrange how the party operates and who is in it and what skills they need as a team and as individuals. they handle their own leadership disputes and affairs. We play with very flexible rules, but if there is a rules debate then somebody in the party is appointed "Look up Man." I hate rule-a-ramas, and I hate being the guy carrying around a bunch of textbooks. So I give that steamy pile of crap to them. I regulate violations, and interpret flexibilities, but I'm not a freaking lawyer, I'm a DM (a judge). So somebody in the party gets to be the lawyer, not me. Like it or not. Also I don't look up spells, powers, etc. they do and if necessary read them out loud so we all understand them. Inventions and innovations - They are responsible for this. I will say this will work, or this will not as it is currently designed, or let's test this, but it is their invention and experiment, I just test it. This encourages innovation on their part. They want some advantage, they have to figure out what it is and how to make it work. I encourage them to devise their own spells, capabilities, and skills. I encourage the players to use their own real world skills, such as tracking ability or survival skills or language skills and adopt them to their character in-game. If the player can speak Latin then so can their character. If the player can recognize a bear track then so can the character. If the player knows how to find water, so does the character. Seek out their own experts and create their own networks. If they have an in-game question about who the last King of Syria was and what he did in Antioch then they go to a monk, an historian, a sage, or somebody else who knows. Not to me, I don't tell them. They do their own research, and they have learned over time to seek out more than one source of information just to make sure what they learn is accurate. Same with creating networks. Over time they have learned it is better to have a reliable, consistent network of people they can trust than to just go to a new stranger everytime they need something. But they have to build their own networks, it's not my job to make others interested in working with them. They do their own research, and discover their own answers, in and out of game. Buy their own supplies and run their operation like a business. If they need something that is not available then they have to design it and get someone to build it for them and it may not be done right the first time it is tried. They don't tell me, "I need something that will do this, and who do I go to?" I say, "well then, you design it and build it, or you find someone who can. That's not my job." I've found stuff like that takes a ton of work off me, inspires their creativity and innovation, encourages them to invent and design, and makes for a much more interesting milieu than if I invented everything. Because I simply cannot think of everything. And besides my job as referee or game leader is not to control them but to guide them and then to turn them loose if possible. I give the mission parameters, but they have to make it happen. And they have to figure out how to make it happen. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*TTRPGs General
Do you Trust Your Players?
Top