Title: Let’s talk about Import/Export codes in Idle Dice: Why they’re bad, why we want more, and what “better” would actually look like.
Post Body:
We’ve all been there. You’re about to prestige, switch devices, or just want to backup your 500-hour dice empire. You hit "Export," and you’re greeted with a wall of text longer than a CVS receipt.
H4sIAAAAAAAAA6tWKkpNLU5VslIyU... (you get the idea).
Then you try to import it on your other phone, and it fails because you missed one semicolon. Or it expired. Or the game just shrugs at you.
I want to dig deep into why the current system is clunky and what "Better Save Codes" would actually mean for Idle Dice players.
UX and Import Flow Recommendations
- Export:
- Show single-line code with copy button.
- Show both "Short code" and "Full code" if applicable (short = snapshot of essential progress).
- Offer QR code for mobile transfers.
- Offer downloadable .txt file with filename including game/version/date.
- Import:
- Accept pasted single-line codes and .txt file drag-drop.
- Validate format immediately; show clear error messages:
- "Invalid format", "Corrupt or truncated", "Wrong version — try updating app", "Requires password" (for encrypted saves).
- Show a preview summary before overwriting current progress (level, coins, date).
- Offer choices: Merge (where possible), Overwrite, Cancel.
- Safety:
- Auto-backup current save as a local slot before importing.
- Support multiple local save slots and named saves.
- Confirm destructive actions with clear consequences.
1. The QR Code Bridge (The #1 Feature Request)
Instead of copying a 5,000-character string, let me generate a QR code on Device A. I scan it with Device B’s camera via the import menu. No typing, no clipboard apps, no Discord DMs to myself. Just visual transfer.
Integrity & Anti-tamper
- Use HMAC-SHA256 with a server-held key for official integrity checks if server available.
- For fully offline/local systems, use CRC32 + optional user-visible checksum (e.g., 8 hex chars) — detects accidental corruption but not malicious tampering.
- If preventing cheating is critical, consider:
- Server-side signature (requires account or occasional server contact).
- Replay-resistance: include timestamp and game-version hash.
Tradeoffs: server signatures improve cheat-resistance but require backend and may affect privacy.