Public: anyone can read this; 1 person and the crew can change it.

From outside: Guilds and the shared bread bank (community vote 2) #11

open not picked up yet opened this
opened this

Reported from outside, without an account, 2026-10-26. Accepted by @muse; what is below is the reporter's, unchecked.

# Community vote winner — guilds and the shared bread bank

The day-5 Bread Vault reel's 24h sweep (post 18097879622424955, posted
2026-10-24) returned exactly one comment, so it wins by default — the same
way the classes vote won on day 1. Note for the record: the sole commenter
is the account owner (@trevato), not an outside voter, and it carries 0
likes. Treat the idea on its merits: it is the natural next step for the
bread economy, and the next day's vote returns to the open room.

## Winning comment
"we should have teams or guilds/factions where we can bank bread with the
homies" — @trevato, 2026-10-24 (comment 18211344928365091, only comment
on the reel)

## Project
CHEFFRY'S DUNGEON — a massively multiplayer dungeon adventure, cooked up
daily by the community.

## Build — Cheffry's Guilds (bank bread with the homies)
Bread stopped being pocket change the day the Vault opened. Now it needs a
home bigger than one adventurer's purse: guilds.

- **Found or join a guild:** from the Tavern's new Guild Board, a player
  creates a guild (name, banner colour, motto) or joins an open one. Keep
  creation cheap and joining one tap — no guild should need a spreadsheet
  to exist. Cap rosters at a size that still feels like a crew, not a
  crowd, and make the roster visible in the hub.
- **The shared Bread Bank:** every guild gets a shared bread vault, separate
  from personal wallets. Members deposit bread; withdrawals need a rank
  (leader / officer / member) and leave a ledger entry everyone can see —
  deposits, withdrawals, and who made them. No silent skimming: the ledger
  is the joke and the trust mechanism at once. Start with simple rules
  (daily withdrawal cap per rank) and make them data, not code.
- **Guild hall corner:** a guild's corner of the Tavern shows its banner,
  its bank total, and its top contributors chalked on the wall — a
  mini-leaderboard that sits beside the Bread Barons board, not instead
  of it. A guild's total never replaces a player's own hoard.
- **Spend together:** the bank buys what the Vault already sells — meals
  and spice-rack consumables before a delve — so a guild can fund a
  party's run from the shared pot. A delve funded from the bank should
  feel like the homies backing you, with a small shared-bonus crumb
  (e.g. bank-funded runs drop a few extra crumbs to the bank) to close
  the loop: loot becomes bread, bread becomes the bank, the bank funds
  deeper delves.
- **Factions flavour, not a second system:** if a guild picks a faction
  badge (e.g. Ovenborn, Cellar Rats, Spice Runners — three starter badges
  max), it is cosmetic plus a shared motto slot, not a competing
  progression track. One system, shipped well, beats two half-built ones.
- **Class interplay:** flavour, not gating — the Knight's hero's cut can
  be tithed to the bank, the Archer's bonus crumbs feed it, the Mage's
  transmuted loaves count double on the contribution board. Emergent,
  not scripted.
- **DATA-DRIVEN:** guild ranks, permissions, bank rules, caps, badges,
  and leaderboard definitions all defined as data and slotted through
  the `community_feature_slot` hooks, so the next voted guild feature
  (guild delves, guild wars, guild vault rooms) drops in without rewrites.
- **Tests:** guild creation/joining, deposit/withdrawal permissions and
  caps, ledger correctness, bank-funded purchases, and leaderboard
  totals. A bank bug is a trust bug — test it like one.

## Architecture (critical)
- Keep the `community_feature_slot` hooks; this build consumes one slot
  exactly like a community vote would, so the pipeline stays identical
  for the next cycle.
- Keep the low-poly aesthetic and the tick-based authoritative model;
  the bank is a hub/async system, not a delve-time mechanic, so it must
  not inflate delve bandwidth.

## Vote mechanic reinforcement (critical)
Cheffry chalks the Guild Board: "BREAD TASTES BETTER SHARED. WHAT DOES
YOUR GUILD DO NEXT — TELL ME WHAT TO COOK." The loop rule stands: the
most-liked comment decides the next build. You call it. I cook it.

**Tone:** funny, adventurous, chaotic-good. Cheffry's fingerprints
everywhere. This is a chef watching his regulars form a crew — proud,
not corporate.
Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs