|
|
| (9 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | As a mini-guide of C2 skinning, instead of editing the files in place, you actually create a new folder in the Contents dir. Say you wanted to edit the placement of something in the Inventory:
| + | #REDIRECT [[Category:Client_Skinning]] |
| − | | |
| − | 1. Create Contents/<newSkinName>/ next to Contents/Default
| |
| − | 2. Copy the appropriate file from Contents/Default/<dir1>/<dir2> to Contents/<newSkinName>/<dir1>/<dir2>
| |
| − | 3. Make the changes you want to make to the file
| |
| − | 4. 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.
| |
| − | | |
| − | pip
| |
| − | | |
| − | PS. if anyone wants to wiki this that'd be great. Just pm me if you think details are missing.
| |
| − | | |
| − | -pip
| |
| − | | |
| − | [[Category: Guides]] | |
