A question for the OSR folks: if you were designing a contest for OSR scenarios, how would you convey the idea that submissions should be compatible with multiple OSR systems? Are there certain systems or resources you would point them to?
Note: we’re not necessarily doing this; I’m just gathering information here.
There is no accepted standard. I would say something like “rules must be compatible with either 0e, B/X, 1e, or any of their various retroclones. Ask yourself, would a person familiar with one of these systems know what to do with my stat blocks? If the answer is a clear yes, you are compatible.”
There is no accepted standard. I would say something like “rules must be compatible with either 0e, B/X, 1e, or any of their various retroclones. Ask yourself, would a person familiar with one of these systems know what to do with my stat blocks? If the answer is a clear yes, you are compatible.”
Oh, and I would ask them to identify which product they targeted for compatibility. E.g. “Compatible with 0e.”
Oh, and I would ask them to identify which product they targeted for compatibility. E.g. “Compatible with 0e.”
If you’re looking for brevity, the phrase “system agnostic” would do the trick. Otherwise, I suppose a short list of popular OSRs would be appropriate (LotFP, Into the Odd, Black Hack…)
If you’re looking for brevity, the phrase “system agnostic” would do the trick. Otherwise, I suppose a short list of popular OSRs would be appropriate (LotFP, Into the Odd, Black Hack…)
.
.
Eddie Hardy I would respectfully disagree. System agnostic means a book is compatible with basically anything – i.e. it’s as compatible with Savage Worlds as it is with PbeM. IOW, just a setting/fiction book. To me OSR compatible means at least some kind of stat block with AC, To-hit, HD/hp, Damage, etc.
Eddie Hardy I would respectfully disagree. System agnostic means a book is compatible with basically anything – i.e. it’s as compatible with Savage Worlds as it is with PbeM. IOW, just a setting/fiction book. To me OSR compatible means at least some kind of stat block with AC, To-hit, HD/hp, Damage, etc.
Maybe saying: “Your game should be compatible with at least one of the following systems:” and then just list a few out? Thoughts?
Maybe saying: “Your game should be compatible with at least one of the following systems:” and then just list a few out? Thoughts?
I think identifying the system (like Ray Otus said) is a good standard. It can also be useful to summarize the basics as the environment of retroclones is growing.
So including a line like “this is compatible with Lamentations of the Flame Princess. In this system, AC is ascending and an unarmored human has AC 12. Hit Dice are assumed to be d6 unless otherwise specified.”
I think identifying the system (like Ray Otus said) is a good standard. It can also be useful to summarize the basics as the environment of retroclones is growing.
So including a line like “this is compatible with Lamentations of the Flame Princess. In this system, AC is ascending and an unarmored human has AC 12. Hit Dice are assumed to be d6 unless otherwise specified.”
Yeah. Basically a version of the first sentence of what I suggested would be fine, I think. It’s about as close as you are going to get to defining “OSR compatible” without touching off some kind of war. LOL
Yeah. Basically a version of the first sentence of what I suggested would be fine, I think. It’s about as close as you are going to get to defining “OSR compatible” without touching off some kind of war. LOL
Max Vanderheyden A bald statement like that at the beginning of every OSR thing would be SO helpful!
Max Vanderheyden A bald statement like that at the beginning of every OSR thing would be SO helpful!
In addition to listing out some systems, I might also include a note that says “If you wish to make a scenario for a system not listed here, just get in touch with us.”
In addition to listing out some systems, I might also include a note that says “If you wish to make a scenario for a system not listed here, just get in touch with us.”
Jason Cordova if it’s your contest, I think you’re doing people a favor by explicitly stating what you want your submissions to be compatible with.
Some workarounds I have seen that I favored personally were things like listing specific mechanics of a stat block in a way that uses words rather than system short hand. Things like “as chainmail” or “saves like a lvl2 fighter” but I don’t think those will accomplish the clarity you seem to be looking for.
So, stating what you want seems brief and most utilitarian.
Jason Cordova if it’s your contest, I think you’re doing people a favor by explicitly stating what you want your submissions to be compatible with.
Some workarounds I have seen that I favored personally were things like listing specific mechanics of a stat block in a way that uses words rather than system short hand. Things like “as chainmail” or “saves like a lvl2 fighter” but I don’t think those will accomplish the clarity you seem to be looking for.
So, stating what you want seems brief and most utilitarian.
Bryan Mullins True. It would probably make it easier to judge, too.
Bryan Mullins True. It would probably make it easier to judge, too.
I would set out a style guide a la LotFP, which does things like “armor as chain”, “attacks as Bear”, that sort of thing. Usually if you give a HD value people can work out saves and attack progression as per their system.
I would set out a style guide a la LotFP, which does things like “armor as chain”, “attacks as Bear”, that sort of thing. Usually if you give a HD value people can work out saves and attack progression as per their system.
If you were going to just list five games, at least one of which your scenario must be compatible with, which would they be? Use whatever criteria you wish for now.
If you were going to just list five games, at least one of which your scenario must be compatible with, which would they be? Use whatever criteria you wish for now.
Is “System Agnostic” not an acceptable term in the OSR community?
Is “System Agnostic” not an acceptable term in the OSR community?
If I were referencing D&D and I would say 0e, B/X, or 1e (AD&D). If I were referencing OSR I guess I would say Swords & Wizardry, LL, Osric, LotfP, DCC. The first three of those OSR entries are essentially the same as 0e, B/X, and 1e. 🙂
If I were referencing D&D and I would say 0e, B/X, or 1e (AD&D). If I were referencing OSR I guess I would say Swords & Wizardry, LL, Osric, LotfP, DCC. The first three of those OSR entries are essentially the same as 0e, B/X, and 1e. 🙂
Greg Gorgonmilk, do you have an opinion that’s more informed than the one I just uttered? I don’t know if I qualify as any kind of expert on OSR stuff.
Greg Gorgonmilk, do you have an opinion that’s more informed than the one I just uttered? I don’t know if I qualify as any kind of expert on OSR stuff.
Ray Otus Your list is pretty close to the one I came up with.
Ray Otus Your list is pretty close to the one I came up with.
Here is some draft text:
Submission Guidelines for OSR Scenarios
Content
If you ask ten people what “OSR scenario” means, you’re likely to get ten different answers. For purposes of this contest, “OSR scenario” means compatible with at least one of the following systems: Swords & Wizardry, Labyrinth Lord, OSRIC, Lamentations of the Flame Princess, or Dungeon Crawl Classics.
Scenarios can be any of a wide range of adventure types: location-based mysteries, dungeon crawls, a small hex crawl, a series of interconnected social encounters, and more. The only items your scenario must include are: a short note about which systems it is compatible with (including any notes that help clarify moving between those systems) and a descriptive opening text that tells the reader what the scenario is about.
Additionally, your scenario must include some sort of reference to one of the Gauntlet Keeper titles. This can be as narrow or broad as you wish. For example, if you choose “Keeper of the Pitch-Black Sails,” your scenario could have a magic item called the Pitch-Black Sails or it could be an entire adventure about evil pirates whose ships have “pitch-black sails.” So long as some sort of reference to a Keeper title can be found within your scenario, you’re good. For a full list of the Keeper titles, go here.
Format
Your scenario should be sent to us in a Google Doc using 11 pt Arial. You may use Bold or Italics for headers, but your scenario should otherwise minimize special formatting. You may include tables, charts, and diagrams if doing so would make your scenario more clear. You may also include a simple map if your scenario is a dungeon crawl or hexcrawl. Your scenario will not be judged on the visual quality of your tables and maps. Do not include any art beyond simple maps.
Word Count
Do not exceed 2000 words. We will not read your entry if you do.
Submitting Your Entry and Deadline
Send a link to your Google Doc to gauntletpodcast@gmail.com. Put “Keepers of the Gauntlet Contest” in your subject line. The deadline for submissions is October 16th at 11:59 PM EDT.
Here is some draft text:
Submission Guidelines for OSR Scenarios
Content
If you ask ten people what “OSR scenario” means, you’re likely to get ten different answers. For purposes of this contest, “OSR scenario” means compatible with at least one of the following systems: Swords & Wizardry, Labyrinth Lord, OSRIC, Lamentations of the Flame Princess, or Dungeon Crawl Classics.
Scenarios can be any of a wide range of adventure types: location-based mysteries, dungeon crawls, a small hex crawl, a series of interconnected social encounters, and more. The only items your scenario must include are: a short note about which systems it is compatible with (including any notes that help clarify moving between those systems) and a descriptive opening text that tells the reader what the scenario is about.
Additionally, your scenario must include some sort of reference to one of the Gauntlet Keeper titles. This can be as narrow or broad as you wish. For example, if you choose “Keeper of the Pitch-Black Sails,” your scenario could have a magic item called the Pitch-Black Sails or it could be an entire adventure about evil pirates whose ships have “pitch-black sails.” So long as some sort of reference to a Keeper title can be found within your scenario, you’re good. For a full list of the Keeper titles, go here.
Format
Your scenario should be sent to us in a Google Doc using 11 pt Arial. You may use Bold or Italics for headers, but your scenario should otherwise minimize special formatting. You may include tables, charts, and diagrams if doing so would make your scenario more clear. You may also include a simple map if your scenario is a dungeon crawl or hexcrawl. Your scenario will not be judged on the visual quality of your tables and maps. Do not include any art beyond simple maps.
Word Count
Do not exceed 2000 words. We will not read your entry if you do.
Submitting Your Entry and Deadline
Send a link to your Google Doc to gauntletpodcast@gmail.com. Put “Keepers of the Gauntlet Contest” in your subject line. The deadline for submissions is October 16th at 11:59 PM EDT.
There is more text related to the contest. The above is just the OSR portion.
There is more text related to the contest. The above is just the OSR portion.
I would like to second that if your system covers OD&D, B/X (which is LL & LotfP) and S&W you’ve got most of everything covered. Combined with notations like “weapon: long sword” and “armor: as chain” you’ve got it covered.
Saves could just be handled as “Save for half damage”. Each OSR DM will know how to handle it and infer from context what to throw dice against.
For monsters I think the most important aspect is setting: (1) an HD (which can be used to determine HP, to-hit bonus, and relative size to a 0-level human); (2) describing interesting special attacks; (3) any stats that ARE need, describe again in terms of human units (2x faster than a man).
I would like to second that if your system covers OD&D, B/X (which is LL & LotfP) and S&W you’ve got most of everything covered. Combined with notations like “weapon: long sword” and “armor: as chain” you’ve got it covered.
Saves could just be handled as “Save for half damage”. Each OSR DM will know how to handle it and infer from context what to throw dice against.
For monsters I think the most important aspect is setting: (1) an HD (which can be used to determine HP, to-hit bonus, and relative size to a 0-level human); (2) describing interesting special attacks; (3) any stats that ARE need, describe again in terms of human units (2x faster than a man).
Kiel Chenier I’m probably going to include a link to your Codex piece (fungus dwarves) as an example.
Kiel Chenier I’m probably going to include a link to your Codex piece (fungus dwarves) as an example.
Kiel Chenier what you’re noting is fair enough, but also means that the individual DM has to do additional work between page and table to get the adventure set up. (Especially if you’re making treasure amounts variable in the module, as opposed to a preset amount.) It also adds volume to the statblock and makes it less immediately usable at the table.
Not saying you’re wrong, mind you – the way you’ve described is a legit one to go! But there are some tradeoffs. Personally, I’d prefer a complete, concise statblock clearly designed for one game over the more generic writeup, but that’s a YMMV thing.
Kiel Chenier what you’re noting is fair enough, but also means that the individual DM has to do additional work between page and table to get the adventure set up. (Especially if you’re making treasure amounts variable in the module, as opposed to a preset amount.) It also adds volume to the statblock and makes it less immediately usable at the table.
Not saying you’re wrong, mind you – the way you’ve described is a legit one to go! But there are some tradeoffs. Personally, I’d prefer a complete, concise statblock clearly designed for one game over the more generic writeup, but that’s a YMMV thing.