02-25-2021, 11:06 PM | #1 |
Join Date: Feb 2021
|
Request for Feedback on Warhammer 40,000 Handbook
Hey, I'm looking for some feedback on a Warhammer 40,000 handbook that I'm writing. If anybody with significant experience with running games in a high power, scifi setting, or with significant experience in Warhammer 40,000 in general, or with a strong technical understanding GURPS mechanics, design choices, and statistics is here, your help would be greatly appreciated. If anybody was looking to run a game in Warhammer 40,000 and is willing to playtest/run with the handbook, that would also be greatly appreciated.
Enclosed below is a public release preview of ~60% of the handbook's current scope in an alpha-beta state. If you are interested/want to help, please either leave a comment in the thread or contact me on Discord (Fennefell#4034). https://drive.google.com/file/d/13nY...ew?usp=sharing PLEASE READ BEFORE PROVIDING FEEDBACK 1. Please ensure that you have read and understood the relevant section. 2. Please take a few moments to think of the relevant design choices made about that section. Internal balance and FEELING like Warhammer 40,000 is the most important design factor; no weapon should dominate, each should fit their roles, and so on. Expanding the GM design space and maximizing fun is the next most important, followed by balance with other GURPS things, followed by adherence to Warhammer 40,000 lore. If you make an argument entirely based off lore, it's likely that it will not be useful feedback. 3. Please understand that I've been working on this PDF for a while and have considered a lot of rules and different ways to design things. If you see something and think "You should do x instead, that's obvious", please take a moment to consider I've likely already thought of that, and try to understand the design choices behind it, as per step 2. 4. When providing feedback, please provide constructive feedback. If you think something needs to be changed, please provide a rationale about why, keeping design choices in mind. If possible, give a proof-of-concept of the replacement, and why this proof-of-concept would be better. I likely will not consider feedback of the form "I don't like x. You should do y instead" with no other backing. Instead, try wording it "I think x has problem A. If you instead used y, you could solve problem A within your design choices. Here is an example of that.". 5. Please do not send me angry messages on Discord if I don't take your feedback. Last edited by Fennefell; 05-14-2023 at 11:22 AM. |
|
|