RPGModder 2.0: Safer deployments and a complete workspace overhaul

Sorry for the delay. This update was actually planned a long time ago. But it wasn't until a few weeks ago that I started working on it.

RPGModder 2.0 rebuilds the manager around one promise: changing your mod setup should not leave the game in a half-deployed state.

This release introduces transactional deployment, automatic rollback, a redesigned desktop workspace, deeper conflict analysis, and automatic recovery of data created by previous RPGModder versions.

Highlights

Transactional deployment

Every deployment now creates a recovery snapshot and transaction journal before the live game is modified. If a manifest is invalid, a file is missing, or the operation is interrupted, RPGModder restores the previous live state and records the rollback in Activity.

Previous installations are preserved

When a game is loaded for the first time in RPGModder 2.0, the compatibility layer searches for the previous layout and imports:

• Installed mods
• Default and named profiles
• The active profile marker
• Vanilla backups
• Save backups
• Profile-specific saves

Migration is resumable and non-destructive. Existing legacy files remain in place, and files already created by RPGModder 2.0 are not overwritten.

A new desktop workspace

The interface is now organized around the work users actually perform:

• Mods: Search, enable, reorder, install, inspect, and deploy mods.
• Conflicts: See every active overlap, its participants, and its resolution.
• Activity: Review successful deployments and automatic rollbacks.
• Creator Tools: Analyze game differences and generate compatible packages.
• Nexus Mods: Browse, link, download, and update mods.
• Settings: Configure deployment, integration, and recovery behavior.

Better conflict information

Conflicts are no longer treated as one generic warning. RPGModder distinguishes:

• File overwrites, where the last enabled mod wins
• Structured JSON merges
• Semantic JSON patches

The Mods inspector and Conflicts workspace expose the affected paths and load-order outcome.

Hardened mod and update handling

RPGModder now rejects unsafe manifest paths and invalid mod IDs before installation. Downloads require HTTPS, use isolated destination names, and enforce size limits. Application updates validate the release package and restore the previous application files if replacement fails.

Linux and Steam Deck-style handheld support

RPGModder now ships as a self-contained Linux x64 application alongside the Windows build. It detects standard and Flatpak Steam libraries, recognizes native Linux RPG Maker launchers and Windows releases managed by Proton, and launches Steam games through their AppID.

Linux desktop integration includes a per-user installer, application menu entry, icon, and nxm:// protocol registration through XDG. Nexus API keys use the desktop Secret Service through secret-tool; they are never intentionally persisted as plaintext when secure storage is unavailable.

Upgrading from an earlier version

1. Close the game and any running RPGModder instance.
2. Keep the existing Mods, ModManager_Backups, and profile files in place.
3. Replace the previous RPGModder application files with the 2.0 release.
4. Launch RPGModder and load each previously managed game once.
5. Wait for migration to finish. Large vanilla backups can take additional time to copy.
6. Confirm the recovery summary and review the Mods and Profiles lists before deploying.

Do not manually move or delete the legacy folders before the first successful 2.0 launch. RPGModder copies legacy data into the new .rpgmodder workspace and leaves the original files untouched.

Important behavior change

RPGModder uses transactional deployment, not runtime filesystem virtualization. It resolves the enabled mod state into the game content directory while protecting the operation with snapshots, journals, validation, and rollback.

Validation

• 42 automated tests passing
• Release build with 0 warnings and 0 errors
• Self-contained Windows x64 and Linux x64 publishes verified
• Isolated startup smoke test verified
• CachyOS/KDE Wayland testing verified the Linux ELF, native game detection and launch, settings permissions, Secret Service access, XDG nxm:// registration, package install/uninstall, Steam discovery, and a sustained XWayland GUI launch

Known limitations

• Linux desktop execution currently uses Avalonia's X11 backend and therefore requires XWayland in a Wayland-only session.
• Direct launch of a Windows .exe on Linux requires a detectable Steam AppID; RPGModder does not invoke Wine with guessed prefixes.
• Secure Nexus credential persistence on Linux requires Secret Service and the secret-tool command.
• A first launch of the self-contained build can take longer while the executable is extracted.
• Runtime loaders and unusually structured RPG Maker games may still require game-specific compatibility rules.