Difference between revisions of "Documentation/Tools/SCS Workshop Uploader/Workshop mod structure"

From SCS Modding Wiki
Jump to navigation Jump to search
Line 1: Line 1:
The standard mod is a single '''package''' with manifest.sii file inside, description and icon files and the mod data files. The Workshop mod can and should consist of many '''packages''' - this change gives you possibility to create mods that are supporting few game patches without need to activate different mod by your mod users. In the '''versions.sii''' file you specify which '''package''' game should use when using the specified game patch. But remember - this layout is only correct for Workshop mods. Standard mods are still using the one package approach.
+
The standard mod is a single '''package''' with manifest.sii file inside, description and icon files and the mod data files. The Workshop mod can and should consist of many '''packages''' - this change gives you possibility to create mods that are supporting few game updates without need to activate different mod by your mod users. In the '''versions.sii''' file you specify which '''package''' game should use when using the specified game update. But remember - this layout is only correct for Workshop mods. Standard mods are still using the one package approach.
  
 
[[File:Mod_layout_explanation.jpg]]
 
[[File:Mod_layout_explanation.jpg]]

Revision as of 14:57, 11 February 2016

The standard mod is a single package with manifest.sii file inside, description and icon files and the mod data files. The Workshop mod can and should consist of many packages - this change gives you possibility to create mods that are supporting few game updates without need to activate different mod by your mod users. In the versions.sii file you specify which package game should use when using the specified game update. But remember - this layout is only correct for Workshop mods. Standard mods are still using the one package approach.

Mod layout explanation.jpg