Request for Comments (RFCs)

This directory contains all RFCs (design proposals) for the Hollowgate game project.

What is an RFC?

A Request for Comments (RFC) is a design document that proposes a new feature, system, or significant change to the game. Unlike ADRs which document decisions already made, RFCs are used to:

  • Propose and discuss new features before implementation
  • Gather feedback from the team
  • Explore design space and alternatives
  • Create a shared understanding of complex systems
  • Document the reasoning behind game design choices

How to Use

  1. Copy the template from ../Templates/RFC-Template.md
  2. Name your file: RFC-XXX-short-title.md (e.g., RFC-001-combat-system.md)
  3. Fill in all sections thoroughly
  4. Share with the team for review
  5. Iterate based on feedback
  6. Update status as it moves through the process
  7. Create an ADR when the decision is finalized

Index of RFCs

IDTitleStatusDateAuthorTags
001Cell SystemDraft2025-12-02Teamexample

Status Definitions

  • Draft: Initial proposal, work in progress
  • In Review: Ready for team feedback
  • Accepted: Approved for implementation
  • Rejected: Not moving forward (keep for historical record)
  • Implemented: Completed and in the game

RFC Process

  1. Draft: Author creates initial RFC
  2. In Review: Team reviews and provides feedback
  3. Discussion: Author updates based on feedback
  4. Decision: Team decides to accept or reject
  5. Implementation: If accepted, implement the design
  6. ADR: Create an ADR to document the final decision

Categories/Tags

Use these tags to categorize your RFCs:

  • #gameplay - Core gameplay mechanics
  • #combat - Combat and battle systems
  • #progression - Character/player progression
  • #narrative - Story and quest design
  • #world - World building and environment
  • #ui-ux - User interface and experience
  • #multiplayer - Online/co-op features
  • #economy - In-game economy and resources
  • #ai - Enemy and NPC behavior
  • #graphics - Visual features and effects
  • #audio - Sound and music
  • #technical - Technical systems and architecture
  • #tools - Development tools and workflow

Tips for Writing Good RFCs

  • Be specific: Provide enough detail for implementation
  • Consider alternatives: Show you’ve explored the design space
  • Think about consequences: What are the trade-offs?
  • Get feedback early: Share drafts before investing too much time
  • Update as you learn: RFCs are living documents during review
  • Link related docs: Connect to relevant ADRs and other RFCs