Assets that are stored on the server cannot be synchronized with clients. This is particularly commonly requested for content mods and their related assets, like sounds, core ShipTemplates, and models/textures/ModelData.
SP/EE were designed for in-person LAN play, where sharing custom content with clients and configuring before playing is relatively straightforward and collaborative effort. With online play, each player has to have access to the assets and the knowledge of where and how to install them, or the GM has to distribute a pre-modified EE package.
Instead of solely relying on clients having the same content already installed locally, SP should have a method for synchronizing such assets from the server to clients for each scenario.
Assets that are stored on the server cannot be synchronized with clients. This is particularly commonly requested for content mods and their related assets, like sounds, core ShipTemplates, and models/textures/ModelData.
SP/EE were designed for in-person LAN play, where sharing custom content with clients and configuring before playing is relatively straightforward and collaborative effort. With online play, each player has to have access to the assets and the knowledge of where and how to install them, or the GM has to distribute a pre-modified EE package.
Instead of solely relying on clients having the same content already installed locally, SP should have a method for synchronizing such assets from the server to clients for each scenario.