friday-posts

name	friday-posts
description	Generate the two Friday-session Slack posts (morning announcement, final call) ready to paste into Slack - checks the live server for the running mod first. Use when asked for Slack posts, the Friday announcement, session messages, or "what do I post".

Friday Slack posts

Generate both session-day Slack posts in one run, ready to copy-paste. The slot moves week to week, so never assume it - read it:

python3 scripts/sessions.py       # -> "2026-09-04 14:30-15:00 Sydney"

That's data/sessions.json, the one place the session time lives (the leaderboards, the recap and the site countdown all read it). If the week you're posting for isn't listed it falls back to the default - add an entry before writing the posts if the slot has moved. An argument still overrides for a one-off, e.g. /friday-posts 1pm.

It's half an hour at the end of the half-day Friday, so it's the wind-down after work wraps, not a lunch-break squeeze. Pitch it that way (finish the week fragging), never as "sneak off and be back at your desk".

Step 1: check what's actually running (no SSH needed)

curl -s https://ff.benrogerson.dev/info.json
curl -s https://ff.benrogerson.dev/status.json

info.json is served by the live container, so its mode IS the running mod (GunGame / Deathmatch / Classic) - use its tagline as raw material, not verbatim. status.json gives current map, humans/bots and proves the server is up.

Fallbacks, in order:

1. curl fails -> pnpm run status (docker ps over SSH; container name <mod>-xash3d-1 on 27016 names the mod).
2. Box unreachable -> still generate the posts from docs/game-guide.md, but open the output with a loud warning that the mode is UNVERIFIED and must be confirmed before posting (the port-theft incident: never announce a mode without verification).

Step 2: write the two posts

Output each post in its own fenced block for easy copy-paste, with a plain line above saying when to post it, and a --------------- line separating the posts. Slack markdown inside: *bold* (single asterisks), plain dashes for bullets, no headers, no tables. Link as a bare URL so Slack unfurls/links it.

Post 1 - morning announcement (~9am). Sets turnout. Mode name + a one-line pitch rewritten with banter (not the info.json tagline verbatim), day + time ("today 2.30pm" - whatever the schedule says), the URL, and Chrome on desktop for best performance. Short.

No preload post - loading is fast now, don't ask people to prep.

Post 2 - final call (~15 min before). Full join steps so nobody scrolls back. Must include, in join order:

1. Open https://ff.benrogerson.dev and hit PLAY
2. Stuck at the splash screen? Just refresh - fixes every known stall
3. First time on this URL: enter your name again (fresh settings per domain)
4. F1 = Terrorists, F2 = Counter-Terrorists (the numbered team menu also works)
5. Mode-specific line - dm: say /guns in chat for the gun list, then e.g. /awp (applies next spawn); gg: every kill levels your weapon, knife kills steal a level, first to gold knife wins; classic: press B to buy at round start, no respawns - dead means spectating until next round, so don't rush the AWP alone
6. Bot line is mode-dependent - gg/dm: bots fill the server and leave as humans join, early birds aren't alone. classic/vanilla: NO bots (yb_quota 0, manual adds only) - don't claim bots will fill in; pitch showing up on time instead, since early birds wait for humans

Do NOT include the mic-prompt instruction in posts (Ben's call - keep the posts fun, and the refresh step covers stalls anyway).

Fact guardrails (repo data that is wrong or stale - do not propagate)

• URL is https://ff.benrogerson.dev. Player-facing docs still say the old IP URL - never put the IP URL in a post.
• Gun chat commands are /guns, /ak, /awp etc - dm's info.json says !guns, which is wrong.
• Bot count: trust the live status.json / yb_quota (7 as of 2026-08-03 on gg/dm; 0 on classic/vanilla - no bots there unless added by hand); game-guide.md's "quota 9" is stale. Or just say "bots fill the server" (gg/dm only).
• The team menu DOES render in-browser (runbook says otherwise - stale); F1/F2 are the easy path, not the only path.
• Never name the current map in posts - maps rotate and there's voting, so whatever status.json shows now won't be what's on at session time.
• The bots aren't pushovers - never pitch them as free frags or easy kills.

Tone

Hype with banter and CS 1.6 nostalgia; tasteful emoji (it's Slack, not the repo docs). Vary the jokes and angle every run so posts never read templated - riff on last week's session or the mode's flavour (not the current map - see guardrails). The instructions themselves stay unmissable and exact: never sacrifice a fact or a step for a joke.