|
|
| (8 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | == Client 2 Skinning Guide ==
| + | #REDIRECT [[Category:Client_Skinning]] |
| − | | |
| − | In Client 2, instead of editing the files in place, you actually create a new folder in the Contents dir. This will allow us to patch files without overwriting mods and allow people to share mods more easily.
| |
| − | | |
| − | Here is an example of creating a simple mod for C2:
| |
| − | | |
| − | # Create ''Contents/<newSkinName>/'' next to ''Contents/Default''
| |
| − | # Copy the appropriate file from ''Contents/Default/<dir1>/<dir2>'' to ''Contents/<newSkinName>/<dir1>/<dir2>''
| |
| − | # Make the changes you want to make to the file
| |
| − | # Change the ''UserConfig.xml'' packages attribute to read ''packages="<newSkinName> Default"'' instead of ''packages="Default"''
| |
| − | #* This will tell C2 to first look in <newSkinName> for the files it needs, then revert to Default for anything it doesn't find. You can chain many of these packages to apply multiple mods. (Eventually we'll have a UI mod manager as well). | |
| − | | |
| − | Lastly, the packages attribute can also read in zip files, so you could place a zip file named '''<newSkinName>.zip in Contents/ and add it to the packages in the same way''', and it would read it. (This will make it even easier to share mods with others)
| |
| − | | |
| − | Any questions related to this can be sent to pip on the forums or asked on IRC.
| |
| − | [[Category: Guides]] | |
