Showing posts with label influences. Show all posts
Showing posts with label influences. Show all posts

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.  


Thursday, April 23, 2020

Influences Part 2 - Scum And Villainy

Continuing on the last post about Games that are influencing Beacon design.

One of the bigger influences I have had these past years is Blades in the Dark and the Forged in the Dark rule set.  The influence of this game is so much so that I almost decided to start on my own Forged in the Dark skin instead of coming back to Beacon.

I started to hear about Blades in the Dark on podcasts and on google+ (haha) quite a few years ago.  I was really into Ashen Stars at that time and was struggling with some of the downtime mechanics and the reputation economy and ship as a character in that game and the ideas I was hearing about from Blades in the Dark* sounded like they would be interesting ways to address some of those issues. I think that the stress economy and downtime mechanics was the initial big draw.  I really liked the idea that PCs would accumulate stress and need to take non-optimal actions to blow off steam in some way to get it back.  Stress and vice is universal story fodder, just like money being a real world game mechanics everyone is familiar with.  I also was taken by the idea of the PC group as a game entity in its own right.  I saw this idea first in a Warhammer RPG game, and in Ashen Stars there is a ship sheet for the crew but Blades takes this a step further.

But as much as I like the rules for Blades in the Dark, I really wasn't into the setting.  I mean I have nothing against the setting, its a fantastic setting and a lot of people love it, I would probably like playing in it, but I don't have any fire to run it unfortunately.  I like sci-fi games and I like games where there is a code of conduct or some other reign on the PC actions so it does not just devolve into murder-hoboism.  I really wanted to somehow merge the stuff I was hearing about Blades in the Dark with Ashen Stars and see if I could have the best of both.  I tried a few times to either re-skin Blades into a sci-fi, game or tack on the mechanics I liked onto Ashen Stars but nothing really stuck.

Enter Scum and Villainy.

I bought the book when it came out and although it wasn't an exact match for what I wanted, it was close and  I did want to try to run it.  Because I had been thinking of the mechanics so much in the context of the Ashen Stars, I decided to run it as a continuation of that campaign.  I originally wanted use the ideas I had for skinning the system to make it fit the space cops concept, maybe even tack on some Ashen Stars rules, but I decided against that since I wanted to understand how it worked first.  I played it pretty much straight, although I did mash in my own "Ashen Stars" setting material from past games.
If Scum and Villainy had come with a really detailed setting and I had to substantially work it over to play, I probably would have started adding in my own rules.  However S&V is pretty loose by design and with the more narrative system I thought I would be able to make it work pretty much as written.  I started the campaign on a 'lets see' basis and found that I didn't really have to change anything mechanical to make it work and I was even able to incorporate a lot of the setting materials that came with the game, they had a similar iconic feel as the Ashen Stars material.  The only substantial difference between the old game and the new game was that the players were no longer space cops, but bounty hunters.  That's a slight difference, but it did have a big impact and I'll get back to that point later.

I got lucky running it with a good group of players who were willing to put in some sweat because the first few sessions were very rough.  First off the players were not inclined to take any actions because the resolution system seemed too punishing.  Their perception was that so many rolls had consequences or bad outcomes that they didn't ever want to roll the dice and when they did they gamed things so much they had no room for roleplay.  Part of this I believe was based on the player facing system changed the dice mechanics so that bad rolls were very bad and even many of their successes seemed like failures.  This was not the case of course, but it felt that way since I wasn't rolling for the bad guys and their rolls now drove the game opposition.  So although from my perspective there was a net neutral outcome in this new system, and the PCs were actually very competent, from the player perception they were not able to do what they wanted and their characters were doing very poorly.
The second issue was that I had a hard time understanding how to scale things in a system without hit-points and levels and so things were either a cakewalk or devastating.  Either I was pulling my punches and they were breezing by challenges or I was giving out consequences and they players were taking on damage and serious conditions before the missions even got started.  Initially this because of the players not remembering to use their resistance, but it also took time for them to get used to spending stress to resist things, since they guarded their point very jealously.  I find that when ever you have points in a system players will hoard them.
Thirdly I really tripped up on the effect and consequences relationship and we didn't understand the concept of trading position for effect and so I was overusing harm as a consequence.  I didn't initially understand this dynamic so I was ticking off clock segments based entirely on the roll results instead of assigning an effect for an action and allowing the players to negotiate a better position or by using lesser effect as a consequence.

What saved this game was some whining good discussions with the players about what they were not liking and then I really had to go do my homework since we were obviously missing something.  It also really helped to find some good reference material.  By luck I found this great YouTube series Let's Learn Blades in the Dark.    This is a really good series stepping through the core mechanics and very useful for anyone thinking about running a Forged in the Dark system.  Between this and boning up on specific mechanics that seemed wrong, it gave me the insight I needed to understand how the various game systems work together.  The most important thing that our table learned coming from a more traditional roll 20 type background was understanding resistance and understanding how to trading position for effect.  Once we sorted that out there was a lot more flex in the system and players would take lesser effect as a consequence and spend their stress to resist harm more often.  Once we got that we started to appreciate how flexible they resolutions were and how they could model all kinds of conflict.

There is a lot of good stuff in the Forged in the Dark system,  Things like stress, conditions and the downtime mechanics are really interesting to play with and there is some similarities in how Beacon uses hit points and fatigue and the Forged stress mechanic.  There is also a lot of similarity in how the Beacon skill system and the FitD skill system work.  Even with keeping the resolution mechanics very d20, you can still take away the idea that resolving challenges can be more of a conversation and a negation in how to apply their stated actions into a roll.  Beacon already has the idea of matching skills to activities but I like moving away even more from all the incremental +1 -2 type modifiers and making things a little more organic based on the narrative and this is one of the reasons I want to bring in the advantage/disadvantage mechanics from 5e.  Advantage/disadvantage works well to model all sorts of situations, is easy to understand and speeds things up.

The idea of downtime is a bit more of a stretch to incorporate into Beacon without loosing the d20 compatibility although there are a lot of precedents in d20 games for something like this.  In the core game Beacon has built in downtime for stat healing, making potions etc and the times it takes for players to level up.  Conditions and stress are an attractive idea but I don;t know if they should be built in systems.  Also since its roll20 bases you can always add in campaign specific rules as well depending if you are playing a story type game or a hex crawl or a west marches style shared world.  I though about adding in more of these but I'm not sure if they should be in the core rules or just floating around out there.  Lots of these, like these nifty resource ideas I would be stealing from other OSR blogs in any case.






*When mentioning stress as a mechanic I also have to mention Torchbearer here and the amazing and related Darkest Dungeons video game which I was also looking at at the same time.  I don't remember all the details but apparently it was a heady time filled with madness, alcohol and self flagellation...

Friday, April 3, 2020

OPD 2020


I want to make sure that I plug the One Page Dungeon contest for 2020.  This contest has been going on for 10 years(!)  and its one of the great game resources to come out of the blogosphere.  

One page dungeons are cool, they are hip, they are super easy to adapt into your games.  I've used so many of these for inspiration, even dropping some whole on top of my players.  There is something about the format and level of detail that makes these so easily digestible and the competition makes the cream rise.  The reviews are a good read as well.



Wednesday, March 25, 2020

Influences Part 1 - Ashen Stars

Most of the writing I have done about other games I moved out to my other blog so that it didn't dilute this site, which is supposed to be about Beacon design commentary.  Now that I'm resolved to try to post something on here once a week, I thought it would be good to write about some of the games I've played in the last few years and what influence they've had.  Naturally there is a lot of overlap between what I'm playing and the game design process so I think since its relevant.  I'll try to bring it all back around to how it impacts that crisp hot Beacon brand in any case.

And I guess I should start with Ashen Stars.

Ashen Stars is a gumshoe based space police investigative game.  Players play Lasers who fly their space ship around the crumbling remains of a vast Federation solving crimes, kicking butts in a mostly non-lethal manner.  The game setting is one of the best I have come across, just the right amount of familiarity and the right amount of ambiguity to make good sci-fi stories happen.

I found space cops to be a really good game premise because the players have to follow procedures and maintain their reputations rather than just kicking in doors and shooting people.   Its great fun being able to parade a bad guy around and have him be untouchable because the players don't have the proof to take them down yet.  Players HATE this but it is really the best because they love hating stuff and it takes some time to nurture those relationships.
Also having mechanics that force players to own up to their actions is useful.  Having a reputation mechanic that offers the option for them to take the short cuts but at the risk of loosing future income is delicious.  There are so many good systems in Ashen Stars, the ship combat is simple but fun, the gumshoe investigation mechanics are good, it has the right level of abstraction for tracking items and money.

But.

I did find that some of the mechanics seemed a bit stodgy when the players were resolving physical challenges.  The d6 mechanic does not leave a lot of room point spend systems are are not my favorite.  I am probably not really running gumshoe on all cylinders so my games tend to be too easy and players seem to always have enough points to buy success.  I have tried ramping up the  challenge but once a few ability pools are used up the players want to rest and recoup, this is the 10 minute adventuring day of gumshoe it would seem
But I get the idea that as you use up your resources the narrative gets more tense but in my experience players will be miserly with points and when they run out, they will start feeling the game is against them more than if they had merely failed a roll normally.

I also felt that the game was missing a level of play at the party level.  Ashen Stars has a ship sheet and there is the idea of the crew as a business entity with reputation and shared resources, but I found it wasn't enough to really draw the players together.  The first time I ran the game the players either didn't care about earning money or they didn't have anything to spend their money on and so there was no real fear of loosing their reputation and not finding good jobs or having longer down times between them.  There were some ship modules to buy but for some reason they didn't glom onto these like I expected, maybe they were not as relevant to their PCs regular actions.  Again this might reflect on my GM chops more than the game system itself. 

When I next ran the game I tried to address some of these perceived issues by establishing a corporation for the party with a bank account and I gave them a large Traveller style mortgage on their ship.  I also added in some living expenses and a the concept of financial random encounters all in the effort to give the players something to hunger for and to make the reputation loss mechanics more meaningful.  If I were to run the game again I would incorporate these ideas into the game and pay way more attention for ways to compromise the crew reputation.

I don't want to give the opinion that Ashen Stars is not a great game as written, because it really is a fantastic and classic game.

Since Beacon is designed to be a Old school d20 system and have a high compatibility with other d20 systems there isn't a ton of mechanics that I would try to directly incorporate from Ashen Stars.  I considered adding in some kind of reputation mechanic and know this is done in other d20 games, but I don't think I would add it to the core rules, especially since Beacon is PC focused and not at all party focused mechanically.  I might someday consider some sort of party mechanics outside the core rules, maybe some kind of play supplement or campaign books.  So not much mechanically, however from a 'GM advice' perspective I would definitely take a lot from Ashen Stars, most importantly the gumshoe core concept of giving clues rather than asking for 'notice rolls' and having players get spotlights on collecting information appropriate to their skills and activities.  The Knowledge and Subterfuge skills stand out here but all the skills are easily applied to information gathering.  A player with a high Physical skill would notice an expert swordsman pretending to be a novice, a player with high Communication would naturally draw NPCs out in a conversation etc.

And this is longer than I thought it would be so I'll leave it there.  Would I play this game again - hell yes.  Here's my original thoughts on Ashen Stars from years ago if you are interested;
Part 1
Part 2
Part 3