Skip to content

+1 for save state syncing #240

Description

@jtbrough

I understand that save synchronization currently excludes save states, likely because reliable state syncing requires much stricter core and version matching than traditional save files.

That said, I'd like to request that save-state synchronization be considered as an optional feature, even if it needs to be gated behind warnings, advanced settings, or explicit compatibility requirements.

For many titles, traditional save files either don't exist or are significantly less useful than save states. The Super Mario Bros. series is a common example, where save states are the only practical way to continue progress across devices.

I've intentionally standardized my setup around matching cores so I can move seamlessly between devices. At the moment, I have the following working:

  1. Web (RomM) — save files and save states
  2. iOS (RomM app) — save files and save states
  3. Android (Argosy Launcher) — save files and save states
  4. Grout on Miyoo Mini Plus — save files only

Even without save-state synchronization, Grout has been an incredible addition and has made handheld retro gaming far more enjoyable. This request is very much a "nice to have" rather than a complaint.

Still, adding optional save-state sync for users who are willing to manage core compatibility themselves would make cross-device play feel truly seamless. I suspect there are others who would gladly accept the associated limitations in exchange for that capability.

Metadata

Metadata

Assignees

No one assigned

    Fields

    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions