Tabletop Night Friends

A small server for a regular tabletop night: what we are playing, who can make it, rules questions and a shelf list.

  • 4 categories
  • 13 channels
  • 6 roles
  • Small
Download Discord JSON

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

SCHEDULING

  • this-weeks-game

    What is on the table, and when. Edited by the Host.

  • can-you-make-it

    Yes or no. React and move on.

  • reschedule

    Because the date always moves once.

THE TABLE

  • rules-questions

    Mid-game. One line and a page number, please.

  • teach-me

    Reading up before the night. Long answers welcome.

  • scores

    For whoever keeps track.

  • Table
  • Hangout

THE SHELF

  • what-we-own

    Who has which game. Check before you buy.

  • wishlist

    What the group wants next.

  • tried-and-rated

    One line per game after it hits the table.

OFF THE TABLE

  • hangout

    Everything else.

  • photos

    Tables mid-game, dice rolls, the lot.

Roles

  • HostAdministrator
  • Regular
  • Occasional
  • Rules Lawyer
  • Muted

Overview

A group that meets to play board games has exactly three recurring problems, and this server is three channels for each of them. Scheduling is the first: #can-you-make-it is where the date is proposed and people say yes or no, #this-weeks-game holds what is actually on the table, and #reschedule exists because the date always moves once. The Table is the second: #rules-questions for the argument that stops play, #teach-me for someone reading the rules before the night so the first hour is not a rules explanation, and #scores for the people who keep track. The Shelf is the third and the most useful: #what-we-own lists who has which game, so nobody buys a second copy of the same box; #wishlist is what the group wants next; and #tried-and-rated is one line per game after it hits the table, which is how a group stops replaying the same three titles. Voice has a Table room for playing online and a Hangout for everything else. There are exactly five roles and no hierarchy beyond a Host who can edit the read-only channels, because a group of eight friends does not need moderators — it needs somebody who updates the date. Nothing here assumes the games are digital: the layout works the same whether the group meets in a living room or on a virtual tabletop.

When to use it

A tabletop group's server usually collapses into one channel where the date, the rules argument and the shopping list all live together, so the date gets lost and the same rules question is asked every month. This layout separates scheduling from play from the shelf, keeps a record of what the group already owns and has already tried, and stays small enough that eight people do not feel like they are rattling around an empty building.

What makes it different

  • Scheduling has its own three channels, so the date is never buried under a rules argument.
  • A shelf list records who owns what, which stops the group buying the same box twice.
  • #tried-and-rated is how a group escapes replaying its same three favourites.
  • One Host role and no moderation ladder, because eight friends do not need one.

Recommended Vetox setup

  • Reminders

    Set a Reminder in #this-weeks-game two days before, which is when people actually decide whether they are coming.

  • Suggestions

    Run Suggestions on #wishlist so the group votes on the next purchase instead of the loudest person choosing.

  • Welcomer

    Welcome a new player straight into #what-we-own so they can see the shelf before their first night.

Questions

Why separate #teach-me from #rules-questions?

They happen at different times and want different answers. #teach-me is somebody reading up before the night, where a long explanation is welcome. #rules-questions is mid-game, where the group wants one line and a page number so play resumes. Sharing a channel means the pre-game reading buries the mid-game answer exactly when it is needed.

Does this work for a tabletop RPG group?

For a group that rotates between systems and one-shots, yes: the shelf becomes systems owned and #this-weeks-game becomes tonight's session. For a single long campaign it is the wrong shape, because a campaign wants character channels, a session log and lore rather than a scheduling loop. Use the play-by-post template for that.

Common mistakes

  • Proposing the date in the same channel as the rules argument, so half the group never sees it.
  • Never recording what the group has played, which is why the same three games keep coming out.
  • Building a moderation hierarchy for eight friends, which is overhead nobody uses.

Consider instead

Do you have any doubts?

Our team is there for you

0.0k

Servers

0+

Commands

0

Users

0

Languages