Reply to thread

Message

<blockquote data-quote="overgeeked" data-source="post: 8880962" data-attributes="member: 86653">Just an experiment with all this OGL stuff going on. This isn't an OGL thread, so please let's not make this into one.This is a draft of an OGL 5E product I am/was working on. Not sure about it going forward. But here it is anyway.The explanation is missing as I was still working on that bit when the recent unpleasantness began.The short version is: think 4E monster design brought forward to 5E. You have one &quot;standard monster&quot; per PC in your party. The charts list the numbers for &quot;standard monsters&quot; at the four levels of 5E difficulty: easy, medium, hard, and deadly. You decide on the difficulty and go. Either have as many &quot;standard monsters&quot; as you have PCs or &quot;combine&quot; the monsters into a solo monster the PCs face. Adding together the HP, attacks, clock, and XP. The numbers line up almost exactly with the official stuff.Or replace a &quot;standard monster&quot; with a terrain feature, hazard, or trap using the numbers presented on the chart. Does it deal damage, use the listed damage. Can it be attacked directly, use the listed hit points. Does it force a save, use the listed save DC.How many successful skill checks does it take to overcome the obstacle? That's what &quot;clock&quot; is for. Clock is taken from indie games like PbtA and BitD. It's the number of successes you need to overcome the obstacle.To do area attacks and/or condition-inflicting attacks, divide the damage by 2. This is where solo monsters can shine. Combine all their attacks and make it AOE.The math is largely based on Paul Hughes' excellent analysis over on Blog of Holding, though tweaked quite a bit.Any questions? Feel free to ask.The Product Identity and Open Gaming Content of Monsters &amp; Obstacles is as follows. Product Identity: Nothing. Open Gaming Content: Everything.ETA: Please discard the PDF if it's 22-pages long. That’s an earlier, outdated and badly written draft. It should be 5-pages long, 4 of charts and 1 of the OGL.</blockquote>

[QUOTE="overgeeked, post: 8880962, member: 86653"] Just an experiment with all this OGL stuff going on. This isn't an OGL thread, so please let's not make this into one. This is a draft of an OGL 5E product I am/was working on. Not sure about it going forward. But here it is anyway. The explanation is missing as I was still working on that bit when the recent unpleasantness began. The short version is: think 4E monster design brought forward to 5E. You have one "standard monster" per PC in your party. The charts list the numbers for "standard monsters" at the four levels of 5E difficulty: easy, medium, hard, and deadly. You decide on the difficulty and go. Either have as many "standard monsters" as you have PCs or "combine" the monsters into a solo monster the PCs face. Adding together the HP, attacks, clock, and XP. The numbers line up almost exactly with the official stuff. Or replace a "standard monster" with a terrain feature, hazard, or trap using the numbers presented on the chart. Does it deal damage, use the listed damage. Can it be attacked directly, use the listed hit points. Does it force a save, use the listed save DC. How many successful skill checks does it take to overcome the obstacle? That's what "clock" is for. Clock is taken from indie games like PbtA and BitD. It's the number of successes you need to overcome the obstacle. To do area attacks and/or condition-inflicting attacks, divide the damage by 2. This is where solo monsters can shine. Combine all their attacks and make it AOE. The math is largely based on Paul Hughes' excellent analysis over on Blog of Holding, though tweaked quite a bit. Any questions? Feel free to ask. The Product Identity and Open Gaming Content of [I]Monsters & Obstacles[/I] is as follows. Product Identity: Nothing. Open Gaming Content: Everything. ETA: Please discard the PDF if it's 22-pages long. That’s an earlier, outdated and badly written draft. It should be 5-pages long, 4 of charts and 1 of the OGL. [/QUOTE]

Verification