Eat It or Yeet It internals
Source: cogs/fun_cog.py. The game runs on the main bot only —
if the Helper ran it too, rounds and XP would double.
Round lifecycle
/eatyeet → _make_round() picks food + duration → posts the round
embed with vote buttons → a countdown task ticks the message (progress
bar, 🔨 HAMMER TIME! under 15 seconds) → expiry tallies votes, posts
results, awards game XP, and attaches the 🔁 rematch button.
Gotcha: Discord renders
<t:...>timestamps in embed descriptions and fields — but not in footers. A timestamp in a footer shows up as raw text like<t:1791818966:R>. The round's "Voting ends" line lives in the description for this reason.
Restart safety
- Views use
timeout=Noneand stablecustom_ids, and are re-registered inon_ready(_ensure_view()) — see the boot gotcha. - Active rounds persist in the
eatyeet_activetable (Postgres); an expiry loop tallies anything that ended while the bot was down. - Rematch settings persist per channel in the
eatyeet_rematchtable (Postgres), so 🔁 Run it back replays the same duration + food source even after a restart.
Food sources
- Auto (default): 90% chance of a live meal from TheMealDB (free, no key) with the dish photo and a 🌐 fresh rarity; otherwise the local list. Session-level dedup of meal IDs.
- Local only: hand-written foods + community suggestions. No internet.
- API only: live meals only. If the API is unreachable, no round starts — explicit warning, never a silent fallback.
Scoring
Majority voters earn points by rarity: common 1, weird / fresh / community 2, cursed 3. Win streaks and best streaks are tracked per user, and results name every voter on each side.
Game data tables
eatyeet_stats (points, streaks), eatyeet_suggestions (community
pool), eatyeet_active (live rounds), eatyeet_rematch (per-channel
rematch settings) — all in Postgres since the November 2026 cutover
(they moved from JSON to SQLite in October 2026, then to Postgres on
2026-11-12 with the rest of the data, 0 mismatches). The old
data/eatyeet_*.json files are kept as rollback copies, and the SQLite
bot.db is a frozen legacy copy — neither is live.