Why Guildhall Exists

Most game communities do not fail because people are not interested.
They fail because coordination gets messy.

Schedules live in one place, signups in another, reminders in another, and game planning is scattered across chats. Guildhall exists to pull those pieces together so communities can spend less time organizing and more time actually playing.

What Guildhall Helps You Run

• Public or guild-only events
• One-time sessions and recurring series
• Instance-by-instance attendance
• Conversation and photo threads tied to the event itself
• Featured games and ownership visibility
• Store-facing workflows (invites, embeds, APIs, and optional paid RSVP where enabled)

Who Guildhall Is For

Community Organizers

You want reliable turnout, clear RSVPs, and less message chaos before event night.

Guild Leaders

You need structure for private groups, role-based coordination, and recurring events members can trust.

Game Stores

You want to grow repeat attendance, showcase events publicly, and connect event activity to your storefront and operations.

Product Principles

1. Event-first design

Events are the center of the product, not an afterthought. Attendance, updates, and communication should all map to real sessions.

2. Clear permissions and audience boundaries

Public, guild, organizer, and attendee access should be explicit and predictable.

3. Practical over clever

Guildhall prioritizes dependable workflows over novelty. If a feature does not help people host, join, and run better sessions, it does not belong.

4. Built for local communities

The product is designed around real stores, clubs, and friend groups that meet regularly and need tools that hold up week after week.

Company

Guildhall is a project by Loach Studio LLC.

Questions

Use your normal support/admin channel, or start with the Help section for setup and workflow guides.