Friday, September 23, 2022

Beacon is... a rules-lite fantasy game.

I prefer to spell this as "rules-lite" and not "rules-light" since using lite indicates this is a simpler variation of another object - in this case the standard d20 SRD.  Lite indicates something lacking a substance usually present like salt or fat, or in this case rules.  Rules-lite is tougher to define, it could mean that there are few rules, and some RPGs do go in that direction.  It can also mean that there are a few simple rules that can be applied in a common way across game concepts, and this is more the definition I have applied.  I use it also because Beacon is a derivation of Microlite so there is lineage implied in the term.  The Microlite system was an eye opener as it managed to boil down the basic d20 rules and present them in an incredibly compact way.  By adding skills to emulate most class based abilities a huge amount of class and level rules were condensed into a tiny rules space.  Much of the material I've added to Beacon is based on this one concept as I've tried to extrapolate the whole system out from that base.  

There are now currently a whole set of Microlite variations to emulate different styles of game from Microlite74 which emulates the original D&D, Microlite81 which mimics B/X and even M20 Fifth which tries to emulate 5th edition.  My first D&D was AD&D so that level of complexity is the pinned expectation I have for fantasy gaming.   So its not a surprise that the development of Beacon is my personal attempt to redevelop a level of rules similar in scope to first edition AD&D from the core Microlite rules, but not to mimic AD&D.  Like other Microlite variations I've tried to model a style of play by adding features or modifications to the core system while trying to keep that system consistent.  The main areas of customization in Beacon are:

  • Finding formulas for game mechanics like penalties/bonuses, leveling costs and class abilities instead of relying on charts;
  • Defining race and class abilities as Stat and Skill bonuses with fewer special rules;
  • Simplifying base damage and damage bonuses to prevent monster hp inflation and long combats;
  • dealing with spell effects vs spell casting costs in a point based system.
When 5th edition came out the bar moved slightly since it was a very good game and introduced many good ideas to streamline rules such as the Advantage mechanic.  Adopting the Advantage mechanic allowed for a lot of simplification for situational modifiers that were in the earlier rules.  Other popular modern d20 ideas like inspiration, talents and feats I didn't incorporate since in my opinion they didn't streamline the core rules but rather added additional tangential systems.

Not all the design has been towards simplified core mechanics, in some cases I have actually added complexity where I though it added value.  The removal of level based dice bonuses found in Microlite have been slowly phased out in favor of skill choices in order to add weight to the skill system.  You can see this in how physical skill now determines combat bonuses or in how some spells are more powerful if you have the appropriate skills.  Anytime I can add in interesting choices for player builds while keeping a simple rule I tried to do that.  There are also rules that were added that are more complex than their traditional equivalents, the initiative and morale systems are cases in point.  These systems I've made more complex than typical rules lite mechanics because I wanted to bring some additional tactical choices into the game for combat and also include a type of death spiral for NPC relationships.  Initial versions of Beacon opted for a stage or phase based approach to initiative while the current rules incorporate even more complexity by focusing on PC actions.

The other aspect of rules-lite is determining what you need the rules for.  Some RPG have rules for every situation that might come up, and others barely have more than a pass/fail rule.  There are some really great games available that have super streamlined rules that will let you quickly resolve anything that might come up in an RPG.  I really admire a lot of the rules-lite Old School games for their simplified and interesting take on the game but find that most of them leave out a lot of things I like to see in my games, particularly in the areas of level advancement and spells.  I tried to include rules that  codified aspects of the game so that players can make informed decisions or interesting choices.  I like to have players choose which skill to invest in based on how it will impact their melee combat bonus vs. how it will impact particular spells, or how many companions they can manage at one time.  That adds interest and customization without requiring a whole feat system.  Also I wanted to reinforce some types of game activity over others by including rules for those activities, so I added in rules for encumbrance, travel, exploration and learning spells.

But this leads into the next design statement:

Beacon is..  an Old School fantasy game.


But I will leave that for next time.

Monday, September 12, 2022

Beacon is... a d20 fantasy game.

Beacon was designed to be light and simple while still feeling like D&D and to remain essentially compatible with (in 2010) modern d20 materials.  There are lots of interesting fantasy games, that use other systems or even rebuild classic D&D.  Some use dice pools, point economies or player and GM playbooks.  Tempting as it can be to play with these however, the core design of Beacon is the d20 system.  

Using the standard D20 mechanics you resolve most challenges using a DC or difficulty class.  The DC is assigned by the game master is determined by how hard the described action is vs the method used to attempt it.  A DC of 5 is for simple things, 10 for normal risk, 15 for hard stuff and 20 for really challenging things.  You can even go higher; DCs like 25 or 30 should be used for truly heroic tasks. There are additional rules but unlike older versions of D&D, with their many tables and charts, d20 really does try to standardize challenge resolution on this simple mechanic.  Even combat uses armour class (AC) as a special version of DC with its associated combat modifiers.

The best reason to use d20 is the amount of material that is available for it.  With very little effort you can adjust materials on the fly between sources.  I do remember the days when the most interesting modules were written for fantasy systems MERP or Role Master and converting these on the fly to d20 took some effort.  Years later, when the d20 Open Game License, came out it seemed that this was going to become the standard for a vast library of sourcebooks and games.  Now there are always going to be published materials that need tweaking for your campaign, adjustments to monsters, treasure, spells, the desired tone etc., however I wanted people to be able to use as much of the existing d20 material in Beacon with as little work as possible.

After 12 years has this paid off?

Well yes and no.  Using a simple d20 system has been great for running games and for tweaking rules.  Its a great baseline.  As for using other material, its not come up as much as I expected and to be honest most of the material I personally use for games is scaled and compatible with the older pre-d20 rules and so needs a lot of adjustment anyway.  The d20 materials I have read don't fit the tone I like, although the power levels are closer to Beacon (up to the point where they aren't).

I have had a constant tug of war trying to find that balance to maintain compatibility between the low values often seen in old AD&D style games and the higher values seen in modern D&D.  My preference for campaign materials seems to land in the older material - mostly the pre-d20 or more modern OSR stuff, however I am first to admin that Beacon which has d20 in its core tracks much closer to d20 monster manuals than it does to the old school monster stats I enjoy.  I have a simple monster stat system in the rules, but you can still easily pull 5th edition monsters right into your Beacon game for use at their intended threat level, where say Labyrinth Lord monsters would generally be too low powered and take a bit of adjustment.  I have mostly relied on generating simplified Beacon monster stats based on creature HD; type x number, and then adding special abilities from the source material.

I have many times lamented this and thought about making changes to down-shift this towards the old materials, but it would come at the expense of this initial design statement.  Twelve years ago that seemed like crazy talk to throw away d20 sources, but today with so many niche d20 experiences its not as wild a prospect.  The market keeps changing however, especially with digital VTT products coming out.  To be useful Beacon needs to be usable and so maybe its not so bad a novice GM can drop in their favorite 5e dungeons and monsters while still benefiting from the other streamlined features in Beacon.  As for my preferences, I can always adjust my favorite adventures on the fly.

As I was writing this post, The Alexandrian posted a thing about the difference in skill resolution between different editions of D&D which is a pretty good read and very relevant to this topic.  Beacon ties skills to leveling and already bounds 20 and 1 rolls with a critical hits and fumbles but that bounded accuracy does not apply to rolls outside of combat.  Its possible to roll a natural 20 and succeed a non-combat challenge but roll a 19+3 and fail one.  He does have some good discussion in that article why the different versions feel so different power wise.

The next design choice I want to talk about is related to how these d20 core mechanics are leveraged.

Beacon is... a rules-lite fantasy game.


So that's next time.


Tuesday, September 6, 2022

Beacon is... 12 years old

Where does the time go?  It was September 2010 when I started posting about Beacon.  There have been big stops and starts in that time, but I have been pushing my thoughts for my fantasy heartbreaker RPG out onto these pages for quite some time.  

I'll be the first to admin that this blog is not a very good ambassador for fantasy role playing, or OSR games, or even for Beacon.  I post rarely and when I do its usually a rambling kind of post that references rules and obscure details.  The Beacon blog seems to be more of a navel gaze and not a really a repository of comprehensive ideas.  The purpose of this blog is to represent the game and document the design choices I make.  That said, the most useful thing a general audience will find on this site is the page where you can download the rules and maybe a notification of a new or upcoming update.  I did write a 'sticky' page to help players navigate character generation.  I should do more of that kind of thing.  I find that when I have time to work on the game its generally fixing rules that are not working and trying to do layout changes to the PDF or updates to the Roll20 character sheet.  That's important stuff certainly, but I think it may all be for nothing if I don't occasionally communicate what Beacon is about and why you might want to play it.  

So what the hell is Beacon anyway?

Beacon is my take on the Dungeons and Dragons game by way of D20, Microlite and OSR content.  

I realized I haven't come back to the Beacon mission statement in quite a while. Over two years ago I laid out a bunch of changes I wanted to make to the game, and I've made most of those changes.  Then I went on to make many more changes based on running the game over a longer period of time. Once that rabbit hole was opened I've dived right in and I have been updating and playtesting and re-updating the rules.   I've pushed past the fairly minor tweaks and polish and have been really making a lot of additional changes I didn't foresee.  Part of this is just catching up with ideas in gaming over the last 5-6 years, but there have been some bigger changes as well.  Playtesting has been a real boon and I'm lucky I have some players who are pushing the rules and making me think about the how and why of Beacon vs other systems and/or their expectations of how the rules should work, what works online and what suits the kind of games I like to run.  

I think that the game has been improved tremendously over the years, the last 3 years especially.  In my opinion it is just overall cleaner, simpler, and better designed for the kind of play I want to be doing.  But, as I've alluded to already, my thoughts lately are trying to sort out if its all just a stack of home rules or if Beacon is its own game and following an actual design. Certainly I have an internal idea - more of a feeling - of what rules I want in the game.  I've had many discussions with players on why a rule works a particular way in Beacon as opposed to other d20 systems.  I think I have a design, but I'm not sure I've communicated it out.  Also Beacon has some rules or systems that are clunky or that seem inelegant but have been kept for compatibility with other d20 games and I have done a lot of back and forth over if I should 'fix' these or leave them.  I've had some large back and forth swings on how to deal with some aspects of the game over the years.  For these situations sometimes I need to swoop out and look at the bigger picture of what the game is supposed to be doing.

So what is the mission statement - the design?  What separates Beacon from basic D20 (and the hundreds of other fantasy RPGs)?  

Next post I'll start with the first one:

Beacon is... a d20 fantasy game.