4b7eca8a46
All checks were successful
Reindex Knowledge Base / reindex (push) Successful in 3s
Adds title, description, type, domain, and tags frontmatter to every doc for improved KB semantic search. The description field is prepended to every search chunk, and domain/type/tags enable filtered queries. Type values: context, guide, runbook, reference, troubleshooting Domain values match directory structure (networking, docker, etc.) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
36 lines
1.2 KiB
Markdown
36 lines
1.2 KiB
Markdown
---
|
|
title: "Card Evolution Mechanic Notes"
|
|
description: "Design notes for a Pokemon-style evolution mechanic ('Up Your Game') for the baseball TCG, covering named and unnamed player evolution paths."
|
|
type: reference
|
|
domain: tcg
|
|
tags: [baseball-tcg, card-design, evolution, game-mechanics]
|
|
---
|
|
|
|
# Card Design Notes
|
|
|
|
## Evolution Mechanic: "Up Your Game"
|
|
|
|
Concept: Pokemon-esque evolution system for higher-powered player versions.
|
|
|
|
### Initial Design Ideas
|
|
|
|
- **Named Players**: Primary target for evolution mechanic
|
|
- Examples: Elite versions of star players with enhanced stats/abilities
|
|
|
|
- **Unnamed Players**: Also viable for evolution
|
|
- Example: "Backup SS" → "Everyday SS"
|
|
- Represents player development and skill progression
|
|
|
|
### Mechanics to Consider
|
|
|
|
- Evolution requirements (experience, achievements, resources?)
|
|
- Stat boosts and new abilities for evolved forms
|
|
- Visual indicators for evolved players
|
|
- Balance implications for gameplay
|
|
|
|
### Questions for Further Development
|
|
|
|
- Should evolution be permanent or temporary?
|
|
- What triggers evolution eligibility?
|
|
- How many evolution stages should exist?
|
|
- Should evolved forms have different costs/requirements to play? |