Talk:Abstract Encounters

From Epic Path
Revision as of 19:55, 30 June 2016 by Reese (talk | contribs)
Jump to navigation Jump to search

Using Abstract Encounters:

  • vehicle combat
  • roles: 5 stations
  • things to do with pips: yes
  • antagonist/consequences: enemy ships
  • sieges
  • roles:
  • things to do with pips:
  • antagonist/consequences:
  • magic item creation
  • roles:
  • things to do with pips:
  • antagonist/consequences:
  • research
  • roles:
  • things to do with pips:
  • antagonist/consequences:
  • mazes?
  • roles:
  • things to do with pips:
  • antagonist/consequences:
  • bar fights?
  • roles:
  • things to do with pips:
  • antagonist/consequences:
  • chase scenes?
  • roles:
  • things to do with pips:
  • antagonist/consequences: bad guys catch up or get away (as appropriate), local town watch gets involved, etc.


to create a system, pre-work required:

  • different tasks/stations/assignments
    • things to do with your pips (per task/station/assignment)
  • some form of antagonist or resistance or consequences for failure
    • this should be within the context of the abstract encounter. There can ALSO be real-time consequences, but each abstract encounter also needs some reward/failure defined.
  • its possible that players could define their station/role on the fly during each encounter, and also come up with their own way of spending pips. GMs should allow this flexibility, if it seems reasonable. In some cases, these new uses or roles can be recorded for future use, and in others, they offer specific ways of taking advantage of specific circumstances. In either case, such tricky uses of pips is encouraged.


some general theories:

  • each station should feel different, but should empower progress
  • the need for distinct stations is derived from:
  • not every character is good at the same things, gives the nature guys something to do while the war guys do something else and the spell guys do a third thing
  • gives each player something to do that isn't just "I help the guy who is good at it".
  • pips should be:
    • bankable
    • usable to improve the meta of the station - makes future rolls better, in exchange for not really doing anything now
    • usable for immediate gain
    • usable to aid an ally's station
  • since the action pool mechanic will always eventually succeed, there needs to be some external mechanism which rewards quick results and punishes slow results. The real currency is time. How many intervals can you afford to bank dice before you need to act? What are the consequences for not acting sooner?


Treasure/XP

  • XP: I'm thinking XP should be equal to 1 monster of the same CR as the encounter in question, times the number of stations available (not the number of players). This means that a party of 4 in a vehicle with 5 stations would get more XP (per character) than a party of 5 in the same circumstances. This works, because that party of 4 is going to have a harder time of things, since they're missing a critical member of their crew.
  • Treasure: varies. Could use the XP reference model, deriving treasure from monsters. Alternatively (and this is true of any encounter, including monster fights), no treasure, or 'meta' treasure that is only good for the improvement of the party's vehicle or other meta- campaign-based item. The personal rewards can then be banked for future encounters, finding a lost treasure, etc. (Todd, I know you've used this to good effect in the past, including at the most recent Sunday game.) Depriving players of treasure in the short term to give them a bigger haul in the longer term can feel more rewarding.