Actions

Archive

Archive:The Gaming Tables

From The Wild Tangents

So full-frontal disclaimer:

This concept and this page will very much evolve as we go.

I am basing it around what I do for work, but my job in emergency response has very deliberate infrastructure in place. I'm not expecting us to be as systematic or rigorous.

The Virtual Tables[edit | edit source]

I have two tables planned, each where a scenario is actively set up. The tables can be paused at any time and left in place in between sessions without having to set everything back up or revert to a prior save point.

Scheduling a Scenario[edit | edit source]

There are going to be maybe a dozen or so people in the Wild Tangents, but each table realistically only has room for 3-5 players at any given time.

  1. I signal that a table is open and put out a call for who might be interested
  2. We'll discuss available scenarios and who is interested to play
  3. Once 3-5 players sign up for a scenario, we'll all discuss available times to meet
    1. Ideally, we should plan to meet for two 3 hour chunks within about a 2 week window, which seems to be a good ballpark. This will obviously depend on overall availability because we are all leading adult lives and stuff.
  4. Once the scenario attendees agree on the play sessions, we all lock them into our calendars and keep each other updated on Discord.
  5. We continue our banter via Discord out-of-session and stuff
  6. On game day we try to log on a few minutes early for sound and/or video checks and some catch-up chatting, but otherwise time is precious so let's get to gaming!
  7. I'll try to gauge our time versus scenario progress and plan to take a water refill/bathroom pit-stop about halfway through.
  8. End of session #1, we confirm session #2 still works and reschedule if needed.
    1. End of Session #2 we determine if session #3 is needed and schedule. I don't imagine it will based on the PFS scenario structure, but you never know.
  9. In between sessions we can handle any minor housekeeping stuff as needed
  10. Once a scenario is closed out, the table is reopened for Step 1 :)

Concurrent Scenarios[edit | edit source]

I anticipate there will be times the Wild Tangents have two scenarios running in tandem.

You'd sign up for each scenario as desired and your calendar availability aligns to the group. I don't want to lock someone out of a scenario on Table Beta just because they previously signed up for one on Table Alpha. Since I can only be at one table at a time, we don't have to worry about two game events happening at the same time.

I don't anticipate more than two concurrent tables because I also have responsibilities outside of this, but as things progress maybe my estimation is inaccurate :)

Example Situation[edit | edit source]

We have the following Players:

  • Mario
  • Peach
  • Link
  • Zelda
  • Kirby
  • Samus

And the following Scenarios:

  • Mushroom Kingdom Mayhem
  • Hyrule Castle in Peril
  • Metroids on the Loose
  1. June 8: Table Alpha opens up
  2. June 9: Mario, Zelda, Samus, and Kirby all sign up for Metroids on the Loose
    • They agree to meet on Saturday June 10 at 10am-1pm and Wednesday June 21 from 6pm-9pm
  3. June 10: Alpha Metroids on the Loose Session 1 is successful!
  4. June 15: Table Beta opens up
  5. June 15: Peach, Link, Kirby, and Samus all sign up for Hyrule Castle in Peril
    1. They agree to meet on Saturday June 17 at 4pm-7pm and Friday June 23 from 7pm-10pm
  6. June 17: Beta Hyrule Castle in Peril Session 1 is successful
  7. June 21: Alpha Metroids on the Loose Session 2 is successful, but the group needs a short session 3 to wrap up
    • They decide to meet on Sunday June 25 from 10a-12p
  8. June 23: Beta Hyrule Castle in Peril Session 2 is successful
    1. No session 3 is needed, so the Table closes for GM prep.
  9. June 24: GM finishes prep clean-up. Table Beta opens up
  10. June 25: Alpha Metroids on the Loose Session 3 is successful. Table Alpha closes for GM prep.
  11. June 26: GM finishes prep clean-up. Table Alpha opens up
  12. June 27: Mario, Peach, Link, Zelda, Kirby, and Samus all want to run Mushroom Kingdom Mayhem - but 6 players in one game is difficult to manage so all agree to split into two tables
    1. Mario, Zelda, and Kirby decide on July X and July Y on Table Alpha
    2. Link, Samus, and Peach decide on July Z on Table Beta, and they all decide to have one single full-day session.

And so the cycle continues with more scenarios and stuff.

  • The tables are just containers, the scenarios and players plug into them as needed. Tables don't have fixed days or time slots.
  • A pattern might start to emerge as we progress, and we could decide to lock things into more structured time slots if we want to go that direction.
  • And in the example above, the GM is a participant in determining availability for play as well. I'm spearheading this whole venture, but I too have outside obligations to schedule around.