Hi CCP and fellow capsuleers,
I’m a 17-year-old EVE player and fan of both EVE Online and the upcoming Vanguard. I’ve spent a lot of time thinking about how the two games could work together without risking character data or progress, and I’ve written a full proposal for a cross-game sync system.
It includes ideas like a translator, player-controlled backups, and a dual-layer save system (Plan A and Plan B) to protect original character data. I know it would be a big technical challenge, but I believe it could be worth it in the long run.
I’d love any feedback from the community, and I hope someone from CCP finds this helpful or inspiring.
Proposal: Cross-Game Character Sync System for EVE Online and Vanguard
Overview
This proposal outlines a system to allow player characters to move between the EVE Online main game and the new Vanguard ground combat game, enabling a seamless experience without forcing players to download separate games or lose progress. The system focuses on data translation, safe backups, and player control over syncing to maintain integrity and avoid corruption.
Key Concepts
1. Original Character Data (Plan A)
-
Each game keeps its own original character data stored in its native format (EVE Online format or Vanguard format).
-
This original data acts as the source of truth and is never overwritten by data imported from the other game.
-
All official progress and save points happen on this original data.
2. Playable Character Copy (Plan B)
-
When playing either game, the player’s active character is a copy of their original (Plan A) character.
-
This copy includes:
-
The player’s original game data.
-
Imported data from the other game, translated to be compatible.
-
-
Changes made during gameplay update the Plan B copy.
-
Importantly, imported data from the other game enriches the experience but does NOT overwrite the original Plan A data.
3. Translator Layer
-
A translator program converts character data between the two game formats.
-
The translation happens through an intermediate, easier-to-manage programming language or data format to allow smooth conversions.
-
The translator also includes a second smoothing layer to verify consistency and check for errors in translation on both ends.
-
The translator must be maintained to handle updates from either game.
4. Player-Controlled Syncing and Backups
-
The system always reminds players to back up their original character data before syncing.
-
Original data backups are kept safe and only changed when the player explicitly commits Plan B updates back to Plan A.
-
If errors occur or syncing fails, the original Plan A character is always available as a fallback.
-
Players decide when to sync and commit changes, avoiding automatic overwrites.
5. Error Handling and Updates
-
If a connection or translation error occurs, players can check forums or patch notes to see if either game updated.
-
The translator can be manually updated or designed to “learn” changes to continue functioning smoothly.
-
Multiple fallback strategies can be implemented to bypass issues and keep the sync process smooth.
Data Flow Summary
Step
Description
Player plays EVE Online
Plan B (copy) is updated, original Plan A is updated only with local game changes; Vanguard data enriches Plan B but not Plan A.
Player plays Vanguard
Plan B (copy) updated; original Plan A updated only with Vanguard gameplay; EVE data enriches Plan B but not Plan A.
Sync initiated by player
Translator converts Plan B data to other game format and updates that game’s Plan B copy.
Player commits Plan B back to Plan A
Player explicitly decides to overwrite their original character with Plan B progress.