Amaprotu

In this order:

1) default.ini - an ini file included in the UI that is used as the default UI ini file when the skin is loaded.

2) /save SkinName - saves the current ini settings (what the screen currently shows) as the default.ini file in the specified skin directory

3) /load SkinName IniFile - load specific ini file. A mod could have a lefty.ini and a default.ini so people who wanted to load a lefty version could type /load coolskin_01 lefty to load the coolskin_01 with the lefty.ini which would have to be in the coolskin_01 folder. If it isn't found the default should be loaded.

4) /save SkinName IniFile - save the current ini settings in the specified folder with the specified name.

Reasons: The positioning stuff doesn't work in the XMLs! But it does work in the ini files. The ini files are more powerful in some ways than the xml files - they describe the tint color, fade rate, position (correctly), what chat windows are open, what is filtered where, and more?

I would like to make really 'smooth' skins, and I'm sure I'm not the only one. It kinda ruins it though if they are relient on the end user rearanging the windows just right. This would also allow for different "version" of a skin to be included very easily.

The ability to choose which UI file is used (current or overwite) is already in game. This extension of that would be wonderful.