Best Practices for Game Save Systems

234 views 1 reply

I'm working on implementing a save system for a roguelike and I'm torn between approaches:

Option A: JSON Serialization

Simple, human-readable, easy to debug. But can be slow for large worlds.

Option B: Binary Serialization

Fast and compact, but painful to version and debug.

What do you all use? Any libraries or patterns you'd recommend?

For roguelikes I'd go with JSON but with delta saving — only serialize what changed from the default state. Keeps files small and readable.

Also, always version your save format from day one. Something like:

{
  "version": 2,
  "player": { ... },
  "world": { ... }
}

Then you can write migration functions between versions. Trust me, future you will thank present you.

Moonjump
Forum Search Shader Sandbox
Sign In Register