Your commissioner handles setup. This is the coach's side — five minutes to read, and a handful of commands you'll actually use.
Your commissioner runs the league. This page is everything you need as a coach — how to run a command, what the bot will send you, and the handful of commands you'll actually use. It takes about five minutes to read.
Nobody sees you fumble. Most DynastyDesk replies are private — only you see them. And if a command isn't yours to run, the bot says so instead of doing something you didn't mean.
Looking for the web dashboard instead — roster, stats, recruiting? That's the web app guide.
Your commissioner runs the setup — you don't have to. This is everything you need as a player, whether or not you've used a Discord bot before. It takes about five minutes to read and you'll only ever use a handful of commands.
Type / in your league's channel and a menu appears above the message box. Keep typing to narrow it — /mydesk, say — then press Tab or Enter to pick it, fill in anything it asks for, and hit Enter again. Most options have a dropdown or autocomplete, so you're picking from a list rather than spelling anything exactly right.
Nobody sees you fumble. Most DynastyDesk replies are private — only you see them. And if a command isn't yours to run, the bot says so instead of doing something you didn't mean.
Run /roster set and pick your school — start typing and it autocompletes all 138 of them. Add your Twitch or YouTube link here too if you stream, and the bot will announce when you go live. (Your commissioner may have already added you with /roster add; /roster set is how you change anything about your own entry afterwards.)
It's the post the bot keeps in your league channel, and it's the one thing to keep an eye on: who's ready, who's away, this week's games, and the advance deadline. It edits itself in place, so it's always current — no scrolling back. Worth pinning it if your commissioner hasn't.
If you're facing another coach, the bot opens a thread for the two of you to sort out a time. Playing the CPU instead? Everyone on CPU that week shares one thread — including if you'd already put that game on your own schedule from the dashboard. You can post your kickoff time with /matchup schedule so it shows for everyone in their own timezone.
Run /result log with the score. Against the CPU it's recorded immediately; against another coach, they get a DM to confirm it. Want your player stats tracked too? /stats submit takes your post-game screenshots and reads them for you.
React ✅ on the status board. That's how the league knows you're done — the week can't advance until everyone has, so this is the one step people actually wait on.
React 🏝️ on the status board, or run /away set with the date you're back. Away doesn't hold the league up — the advance goes ahead without you, and you won't be chased about it. Only a coach who is neither ready nor away blocks the week.
If you'd rather just hand your opponent the win rather than hold up the week, /fw give awards them a forfeit win over you.
Everything else is either optional or your commissioner's job. The Command Reference filters down to just the player commands if you want the full list.
There's a web dashboard too. Sign in at web.dynastydesk.gg with the same Discord account for your roster, stats, records and season history — none of it required, all of it nicer to look at than chat.
DynastyDesk tracks user vs user matchups and creates dedicated Discord threads for each game.
Every game thread opens with three buttons, so the things you do most often need no typing at all:
The buttons and the commands do exactly the same thing, so use whichever you prefer — a score logged either way behaves identically, and your opponent still gets the same confirmation DM. The shared CPU Games thread has the same buttons; there they act on whichever game is yours that week.
Who sees this: the buttons are in a thread your league can read, but the reply you get is shown only to you. What everyone does see is the outcome — the thread gets a "game scheduled" or "result submitted" note, exactly as it does when you use the commands.
You can only act on your own game. Pressing a button in someone else's thread won't do anything.
neutral flag for bowls and kickoff games. Run it again on the same pair to move where the game is played. It takes two different coaches — scheduling someone against themselves is refused here and on the dashboard alike, because the game that produces can never be played or confirmed.Deadline updates from /schedule cadence or /week set push to all open threads in real time. Threads are archived automatically on advance.
The shared CPU Games thread is built from the week's CPU games rather than from the ones the advance happened to create, so building your season on the dashboard ahead of time no longer leaves you out of it. Games you've already played and logged are left out — nobody needs a deadline for a game that's finished.
Records the FW request on the matchup and flags it as "FW Pending" on the status board.
Every commish ID on the league receives a direct message notification immediately, showing display names so the alert is readable on mobile.
No explicit close-out command required. Clears during the advance flow.
Members mark themselves away with /away set. Away users count toward the all-ready threshold — commishes don't have to manually account for them. Use /away clear to remove.
Add a day (and month, if you're going further out) to show the league when you're back — it's optional, and without one you're away until you run /away clear. The return date shows as the same day for everyone, whatever timezone they read it in.
Away + UvU: If an away member has a matchup, the bot automatically flags it FW Pending and DMs all commishes.