Skip to main content

Reference Component: [Component Name or Behavior]

📌 This is a reference entry from another game or product.
We use this library to collect ideas that inspire us, teach us, or help us plan our own components later on.

🎮 Game Reference​

  • Title: [Game Title]
  • Studio: [Developer/Publisher]
  • Platform: [PC / Console / Mobile / Web]
  • Scene or Context: [e.g. "Level 3 – Boss Intro", or "Main Menu Navigation"]

📽️ Visual Example​

or link to external video: Watch on YouTube

🔍 What Stands Out​

  • [What this component does and why it's interesting]
  • [Is it about timing? Flow? Feedback? A visual trick?]
  • [Anything that catches your attention or feels smart]

💡 What We Can Learn from It​

  • [How this idea could apply to something we’re building]
  • [What systems it connects with (UI, narrative, movement, etc.)]
  • [What we’d do differently — or replicate]

🧭 Tags / Category​

Choose one or more of the following, or add new ones:

  • Animation
  • Interaction
  • UI
  • Navigation
  • Combat
  • Feedback
  • Systems
  • Onboarding
  • Puzzle Logic

🎯 Type: External Reference​

This is not a Numen component — it’s something we’re using as a learning tool and source of inspiration.

Use cases:

  • Design workshops and team discussions
  • System planning and breakdown
  • Educational onboarding for new teammates

Recommended format:

  • Video length: 10–60 seconds
  • Clear file naming (e.g. dash-hollowknight.gif)
  • Optional subtitle or label: "REFERENCE: Dash mechanic"

🔄 How This Fits into Our Workflow​

This reference is part of a larger cycle:

  • First, we observe and document external ideas
  • Later, we might prototype something similar internally
  • That can lead to tutorials, reusable logic, or public showcases

Each entry here helps us connect what we like with what we might build.