Adventures

Somebody has a free Thursday and a dungeon they want to run. On WestMarches.games that becomes an adventure: one session with a start time, a GM, a level range and a number of seats. The bot posts it in Discord, players sign up with a character, and afterwards it stays in the community's history with its rewards and recaps.

This page is for admins and GMs. Players have Joining as a Player.

Who posts the adventures?

The GMs do, and players sign up for the ones that suit them. That's Default Mode, and every community starts in it. It suits most games, because the GM posting a session already knows what to prep for it.

Classic Mode (Settings → Adventure Settings) also lets players post one, which waits for a GM to claim it (More → Claim Adventure). Many communities that switch it on never get a single adventure posted that way, so only do it if your players already plan their own trips and your GMs are happy to run them with little prep.

Worth switching on

Adventure Settings has a few switches, all off to begin with. These are the useful ones.

• Enable 30-minute adventure remindersThe bot pings the GM and every approved player under the Discord post before the start.
• Let GMs manually add characters to adventuresFor the player who says in Discord they're coming and never signs up.
• Create discord calendar event in addition to the adventure postThe bot needs Discord's Create Events permission for this one.

Adventure attributes

Attributes are your own fields on each adventure, like the kind of session or how dangerous it is, and players can filter by them. They're a Patreon feature, and you don't need them while every upcoming adventure fits on one screen. Deleting one wipes it from every adventure, so rename it if that's all you want to change.

Posting an adventure

A few things on the Schedule new Adventure form catch people out.

• You enter the start time in your timezone, and each player sees it in theirs.
• Discord Roles to Ping only lists roles with "Allow anyone to @mention this role" turned on in Discord, and the ping only goes out with the first post.
• Save as Draft keeps it off Discord until you publish.
• An adventure that's already over gets no Discord post, so you can log a past session for its rewards.

The bot posts each adventure in your Adventures channel (Settings → Discord Channels) and edits the post as the adventure changes. Use a forum channel if you can, so each adventure gets its own post with the reminder and recaps underneath. If a post goes missing, Manage → Discord Posts can make a new one.

Signups

Signups wait as pending until the GM approves them, unless the adventure has Automatically approve signups ticked. By default the bot also DMs the GM about each one, with buttons to approve or reject it right there.

A full adventure still takes signups, and the dialog mentions a waitlist, but there's no queue behind it. When someone withdraws, nobody moves up by themselves. With more signups than seats, look at when each player last played (new players get a New player! badge) and give the spot to someone who hasn't had one in a while.

When plans change

If a session falls through, use Cancel. The signups stay and Uncancel brings it back. Delete is for mistakes, like a test post. It removes the adventure for good but leaves the Discord post behind, marked as deleted.

Story not finished? Clone Adventure under More makes the next session with the same players. The copy starts at this time tomorrow, so fix the date.

After the session

The GM hands out experience and currency with Distribute Rewards, and everyone who played can write Adventure Notes. The bot posts the public ones in Discord as the recap, and with Enable adventure recaps page switched on in Settings → Wiki they also collect into a timeline in the World Wiki.