Tech Stack

Cons:

• Smaller ecosystem than Unity
• Console export requires third-party (W4 Games)
• 3D capabilities less mature (irrelevant for 2D)

Best For: 2D-focused solo devs, rapid prototyping, those who value ownership

Learning Curve: Low-Medium
2D Quality: ★★★★★

Unity

Pros:

• Massive ecosystem and asset store
• Extensive documentation and tutorials
• Strong console export support
• Industry standard (resume value)
• C# is powerful and widely known

Cons:

• Runtime fee controversy (stabilized but trust damaged)
• 2D is second-class to 3D
• Heavier weight, slower iteration
• Complex for simple 2D games

Best For: Multi-platform release focus, those already knowing C#, projects that might expand to 3D

Learning Curve: Medium-High
2D Quality: ★★★☆☆

GameMaker

Pros:

• Purpose-built for 2D
• Many successful indie games (Undertale, Hyper Light Drifter)
• Fast prototyping
• Good documentation

Cons:

• Subscription model for full features
• GML is unique to GameMaker (not transferable)
• Less flexible for complex systems
• Community smaller than Unity/Godot

Best For: Pure 2D games, those wanting fastest 2D-specific workflow

Learning Curve: Low
2D Quality: ★★★★★

Pygame / Love2D / Custom

Pros:

• Maximum control
• No engine limitations
• Educational value
• Free

Cons:

• Build everything from scratch
• Much longer development time
• Export complexity
• Reinventing solved problems

Best For: Learning, extremely specific technical needs, experienced programmers with time

Learning Curve: High
2D Quality: ★★★★★ (but you build it all)

Recommended: Godot 4.x for This Project

For a solo dev 2D pixel art action-RPG:

• Native 2D is exactly what you need
• GDScript allows rapid iteration
• No licensing concerns
• Built-in tools match your needs
• Active subreddit and Discord for help

Essential Tools Beyond Engine

Version Control

Git + GitHub/GitLab (non-negotiable)

• .gitignore for engine-specific files
• Commit often, branch for experiments
• Consider Git LFS for binary assets

Art Tools

Audio Tools

Project Management

Supporting Tools

• Tiled - External tilemap editor (if engine's is limited)
• TexturePacker - Sprite sheet optimization
• OBS - Recording devlogs, trailers
• Handbrake - Video compression

Development Environment Setup

Recommended Folder Structure

project-root/
├── .git/
├── .gitignore
├── README.md
├── docs/
│   ├── design/
│   │   ├── concept-document.md
│   │   ├── story-bible.md
│   │   ├── game-design-document.md
│   │   └── balance/
│   └── art/
│       ├── style-guide.md
│       └── asset-list.md
├── game/                    # Engine project folder
│   ├── assets/
│   │   ├── sprites/
│   │   ├── tilesets/
│   │   ├── audio/
│   │   └── fonts/
│   ├── scenes/              # or equivalent
│   ├── scripts/
│   └── project.godot        # or equivalent
├── raw-assets/              # Source files (PSD, Aseprite, etc.)
│   ├── art/
│   └── audio/
└── builds/                  # Export outputs
    ├── windows/
    ├── linux/
    └── mac/

.gitignore Essentials

# Godot
.godot/
*.import

# Unity (if using)
Library/
Temp/
Logs/
*.csproj
*.sln

# OS
.DS_Store
Thumbs.db

# Build outputs
builds/

# IDE
.vscode/
.idea/

# Large raw files (use LFS or exclude)
*.psd
*.xcf

Platform Export Strategy

Primary Target: Steam (PC)

• Windows build essential
• Linux build highly recommended
• Mac build if possible

Secondary Target: Itch.io

• Same builds as Steam
• Good for demos, early access

Future/Stretch: Nintendo Switch

• Most accessible console for indies
• Requires approved developer status
• Plan architecture with this in mind (no PC-only dependencies)

Performance Considerations

For Pixel Art 2D Action-RPG

• Target: 60 FPS consistent
• Modern hardware handles this easily
• Focus areas:
  • Efficient collision
  • Object pooling for projectiles/particles
  • Don't premature optimize

What NOT to Worry About (Yet)

• Draw call batching (engines handle it)
• Complex shaders
• Memory limits (pixel art is tiny)

Decision Checklist

Before committing to tech stack:

• Have you completed a tutorial project in this engine?
• Can you create a basic 2D character that moves and attacks?
• Do you know how to export a build?
• Have you found community resources for stuck moments?
• Does it export to your target platforms?
• Does working in it feel sustainable for 1-2 years?

Additional Resources

Reference Files

• references/godot-setup-guide.md - Godot-specific setup instructions
• references/git-workflow.md - Version control best practices

Examples

• examples/project-setup-checklist.md - Step-by-step setup checklist