Rudimentary instructions on how to integrate (merge) custom skins:
Step 1) Create NEW addon folder:
• Create a NEW folder within the folder structure (location) where your custom skins are installed.
- (ie, for WindowsXP users something like under My Documents then "\The Lord of the Rings Online\ui\skins\")
- (ie, for Windows Vista and 7 users - I do not know for sure - something like under the user's profile directory then "\The Lord of the Rings Online\ui\skins\").
• Also (and very important) give the folder a unique name that will make sense to you.
- (ie, "MyAddon", "MyAuctionCraftMail", etc.)
• The NEW folder structure should look like My Documents or user's profile folder then "\The Lord of the Rings Online\ui\skins\MyAddon\".
• This name will appear in the "Options" panel, found under "UI Settings" button, "Misc" section, "Current User Skin" dropdown menu, which is where you will select the custom skin to be displayed.
Step 2) Copy or move all art assets (note that some addons do not modify art assets):
• Open the folders containing the two (or more) custom skins you want to integrate (or merge).
• Make sure any modified art assets (ie, custom background images, button icons, etc.) have unique names so they do not conflict and overwrite each other when you combine the resources of both addons (custom skins) into one folder.
• If you find identical names for resources (ie, "background.tga") then append the filenames with a prefix identifying the addon the resource is related to (ie, "LAP_background.tga" for LargerAuctionPanel) before copying or moving them.
• Move or copy all art assets from the SOURCE addons folders to the NEW addon folder created above.
Step 3) Create a single "SkinDefinition.xml" file:
• Open your text editor.
- (ie, EditPlus, EditPad Lite, UltraEdit, your favorite text editor, etc.)
• Create a NEW xml file.
• Save and name the NEW xml file as "SkinDefinition.xml" (making sure to include the xml extension) in the NEW addon folder location created above.
• Make sure the NEW "SkinDefinition.xml" is named EXACTLY "SkinDefinition.xml" and NOT "SkinDefinition.xml.txt" by your text editor (update file name if necessary).
• Add Line 1:
Code:
<?xml version="1.0" encoding="UTF-8"?>
• Add Line 2:
• Add Line 3 (using your own addon name from Step 1, of course):
Code:
<SkinName Name="MyAddon"></SkinName>
• Add Line 4:
• Save the NEW "SkinDefinition.xml" file.
Step 4) Integrate code from SOURCE "SkinDefinition.xml" files:
Step 4.1) Copy/Paste "<Mapping>" code:
• Open the "SkinDefinition.xml" file from the SOURCE addon using your text editor.
• Search for lines containing any "<Mapping>" tags (similar to the following):
Code:
<Mapping ArtAssetID="Auction_Base_BG" FileName="larger_auction_background.tga"></Mapping>
• If found, copy/move all of the <Mapping> tag lines from the SOURCE file, and paste them ABOVE the last line in the NEW "SkinDefinition.xml" file.
• Note that the last line in the NEW "SkinDefinition.xml" file should be:
• Note that there should be one <Mapping> line for each custom art asset found in Step 2 above.
• If any art assets were renamed in Step 2 above, then carefully rename any "FileName"(s) in the NEW "SkinDefinition.xml" file to be consistent with the exact filenames used in Step 2 above.
• SAVE the NEW "SkinDefinition.xml" file. (NOT THE SOURCE FILE!)
• Repeat Step 4.1 for all addons (custom skins) being integrated (merged), then continue to Step 4.2 below.
Step 4.2) Review "<Mapping>" code:
• Review all of the "<Mapping>" lines in the NEW "SkinDefinition.xml" file for duplicate "ArtAssetID" names.
• If any "<Mapping>" lines refer to the same "ArtAssetID" name then you will encounter conflicts between the custom skins you are trying to integrate (ie, attempting to modify the same image), and your merged custom skin will likely not display and/or even load correctly.
Step 4.3) Copy/Paste "<PanelFile>" code:
• Search for lines containing any "<PanelFile>" tags (similar to the following):
Code:
<PanelFile ID="ID_UISkin_Auction_MainField">
• Copy/move the code chunk (all of the code lines) including the tag lines from the "<PanelFile ID="...">" to the "</PanelFile>" tag lines from the SOURCE file, and paste them ABOVE the last line in the NEW "SkinDefinition.xml" file.
• Note that there may be more than one <PanelFile ID="..."> to </PanelFile> code chunk for each custom skin being integrated.
- (ie, LargerAuctionPanel modifies the main panel and two templates.)
• Note that the last line in the NEW "SkinDefinition.xml" file should be:
• Note that there should be only ONE "</opt>" line at the bottom of the "SkinDefinition.xml" file.
• SAVE the NEW "SkinDefinition.xml" file. (NOT THE SOURCE FILE!)
• Repeat Step 4.3 for all addons (custom skins) being integrated (merged), then continue to Step 4.4 below.
Step 4.4) Review "<PanelFile>" code:
• Review all of the "<PanelFile>" lines in the NEW "SkinDefinition.xml" file for duplicate "PanelFile ID" names.
• If any "<PanelFile ID="...">" lines refer to the same "PanelFile ID" name then you will encounter conflicts between the custom skins you are trying to integrate (ie, attempting to modify the same panel), and your merged custom skin will likely not display and/or even load correctly.
Step 5) SAVE and close the NEW "SkinDefinition.xml" file.
• Make sure the NEW "SkinDefinition.xml" is named EXACTLY "SkinDefinition.xml" and NOT "SkinDefinition.xml.txt" by your text editor (update file name if necessary).
Step 6) Close and DO NOT SAVE the SOURCE "SkinDefinition.xml" files.
Step 7) Run the game.
* Your mileage may vary, but probably won't.