Right now, mod playsets are occasionally useful, but they could be even better!
Current State:
- If you have a mod which provides a shipset, and your custom empire uses that shipset, then switching to a different playset (which lacks the shipset) will crash your game if you try to edit the custom empire.
- If you have a mod which provides origins, traits, different planet types, and so on, and your custom empire uses those options, then switching to a different playset (which lacks the mods) can permanently damage your custom empires when you switch back. You may need to manually reconfigure each custom empire to restore the previous content.
- If I start a game with no mods (e.g. to test a bug), most of my custom empires get trashed. This means I am reluctant to test bugs, and report fewer bugs than I experience. This is bad for both you as a company and me as a player.
Even Better state:
+ Your custom empires with custom shipsets won't even appear if you start the game with a different modset. You will never crash to desktop by editing an empire which isn't in the empire list.
+ Your custom empires with custom traits / planet types / origins / etc. will not be damaged by being loaded into a different modset which lacks that trait / planet type / origin / etc., and will be whole and undamaged when you switch back to the modset for which they were created.
+ When I make a new empty modset and start a game with no mods installed (e.g. to test a bug), the game does not trash my custom empires.
Implementation thoughts:
• Store custom empires in a namespace unique to each modset.
• Handle modset renaming gracefully.
• Back up modsets and custom empires in the cloud, like save games, to be shared between machines which share an account, just as Steam mod subscriptions and saved games are shared between machines on the same account.
EDIT: There's another benefit, which is that when you make a modset for a specific type of RP -- perhaps a total conversion to a popular franchise, or a different species palette (e.g. "space fantasy") -- the custom empires you create for that RP will not be polluted by your regular custom empires, and will not pollute your games with different RP preferences.
Tight coupling between custom empire set and modset seems like it will open up a lot of convenience, with no particular downside.
Current State:
- If you have a mod which provides a shipset, and your custom empire uses that shipset, then switching to a different playset (which lacks the shipset) will crash your game if you try to edit the custom empire.
- If you have a mod which provides origins, traits, different planet types, and so on, and your custom empire uses those options, then switching to a different playset (which lacks the mods) can permanently damage your custom empires when you switch back. You may need to manually reconfigure each custom empire to restore the previous content.
- If I start a game with no mods (e.g. to test a bug), most of my custom empires get trashed. This means I am reluctant to test bugs, and report fewer bugs than I experience. This is bad for both you as a company and me as a player.
Even Better state:
+ Your custom empires with custom shipsets won't even appear if you start the game with a different modset. You will never crash to desktop by editing an empire which isn't in the empire list.
+ Your custom empires with custom traits / planet types / origins / etc. will not be damaged by being loaded into a different modset which lacks that trait / planet type / origin / etc., and will be whole and undamaged when you switch back to the modset for which they were created.
+ When I make a new empty modset and start a game with no mods installed (e.g. to test a bug), the game does not trash my custom empires.
Implementation thoughts:
• Store custom empires in a namespace unique to each modset.
• Handle modset renaming gracefully.
• Back up modsets and custom empires in the cloud, like save games, to be shared between machines which share an account, just as Steam mod subscriptions and saved games are shared between machines on the same account.
EDIT: There's another benefit, which is that when you make a modset for a specific type of RP -- perhaps a total conversion to a popular franchise, or a different species palette (e.g. "space fantasy") -- the custom empires you create for that RP will not be polluted by your regular custom empires, and will not pollute your games with different RP preferences.
Tight coupling between custom empire set and modset seems like it will open up a lot of convenience, with no particular downside.
Last edited: