Game Design Pattern Guide

Explain how to use a specific pattern for game development.

When the user asks about a pattern:

1. Explain what the pattern is
2. Show when to use it in games
3. Provide engine-agnostic pseudocode
4. Discuss trade-offs
5. Give real game examples

Output Format

# Pattern: [Name]

## What It Is
[2-3 sentences explaining the core concept]

## When to Use in Games
- [Use case 1]
- [Use case 2]
- [Use case 3]

## When NOT to Use
- [Anti-pattern 1]
- [Anti-pattern 2]

## Implementation

### Core Structure
```pseudo
// Engine-agnostic pseudocode
class [PatternName] {
    // Key elements
}

Game Development Example

// Specific game example

Trade-offs

Pros

• [Advantage 1]
• [Advantage 2]

Cons

• [Disadvantage 1]
• [Disadvantage 2]

Real-World Examples

• [Game] uses this for [feature]
• [Game] uses this for [feature]

Common Mistakes

• [Mistake 1]: [Why it's wrong]
• [Mistake 2]: [Why it's wrong]

Related Patterns

• [Pattern A] - [Relationship]
• [Pattern B] - [Relationship]

## Common Patterns to Cover

- State Machine
- Component/Entity-Component-System
- Command Pattern
- Observer/Event System
- Object Pool
- Flyweight
- Service Locator
- Factory
- Strategy
- Singleton (and why to avoid it)
- Double Buffer
- Game Loop
- Update Method
- Dirty Flag
- Spatial Partition

Explain the pattern the user asks about.