Onchain Game Guild

Server structure

Overview

For a guild playing games whose state lives on-chain, where the coordination problems are unlike an ordinary clan's. Games is one channel per title the guild plays, because these games differ enormously and a strategy conversation does not transfer. #game-mechanics is where the guild works out how a system actually behaves, which in this genre is a genuine research activity rather than reading a wiki. Shared Assets is the category that makes this a guild rather than a group chat: #asset-register is a read-only list of what the guild collectively holds and who is currently using it, #lending-log records every hand-off with the date and the terms, and #stewardship-rules states plainly what happens if an asset is lost, damaged or a member leaves — written before it happens rather than argued afterwards, which is where guilds break. Coordination holds #session-planning, #roles-and-specialisations and #new-member-onboarding. Playtesting is specific to this space: #playtest-feedback, #bug-reports and #dev-relations, since guilds are often the largest organised group a small onchain game has and are treated as such. Safety carries the verified links and the never-list. There is no price channel and no discussion of asset value; #guild-rules says so, because a guild that trades its own holdings stops being able to plan.

When to use it

Guilds in this space break over shared assets rather than over play: nobody wrote down who holds what, a member leaves with something the guild considered collective, and there was never an agreed rule for it. This layout keeps a public asset register and lending log, states the stewardship rules before anything goes wrong, and gives each game its own strategy room since mechanics do not transfer between titles.

What makes it different

• A public register of what the guild holds and who currently has it.
• Every hand-off is logged with a date and terms, before it is ever disputed.
• Stewardship rules are written in advance, which is where guilds usually break.
• One strategy room per game, because mechanics in this genre do not transfer.

Recommended Vetox setup

• Self-Roles

  Post a Self-Roles panel in #which-games so a session ping reaches only the members who play that title.

• Logs

  Enable Logs across the shared-asset channels, so changes to the register are recorded rather than remembered.

• Auto-Mod

  Run Auto-Mod link filtering everywhere, since a guild holding assets is a standing target for drainer links.

• Reminders

  Set Reminders in #session-planning so coordinated sessions have the numbers they were planned for.