I'm happy to report that this has now been fixed!
Firstly, the "clumped JS" happened as a result of CloudFlare integration. Apparently, the "last modified" detection for files edited via FTP in CloudFlare is a bit dodgy, so any changes made for debugging purposes I would not see reflected in the files.
Disabling CloudFlare integration from the host's customer control panel fixed this issue and the JS files now behave as expected
Secondly, and this was actually completely unrelated to the above issue and really something I should have noticed right off the bat - my apologies for that - the issue of custom avatar styles not saving.
The "Avatar Base" layer that comes with the mod is a "magic layer" in the sense that any new body images MUST belong to that layer. In other words,
/dbtech/avatars/images/parts/character/Male Body.png needed to be
/dbtech/avatars/images/parts/Male Body.png and the part itself had to be deleted and re-added to the system.
For the future, you should upload "Female Body" and "Orc Male Body" etc. to the /parts/ folder, next to Male Body and avatar_base_female.png, etc. Then when you go to add new parts, it will auto-detect that those images should be "Avatar Base" images.
Any other parts like gloves, boots etc for the armour will work fine with the folders you have already created
Also, you should ensure that the "Avatar Base" layer is always the first layer in the display order - I've corrected this on your site as well. As it was, most armour pieces were actually appearing
behind your character
The only exception to this is if you decide to create and sell a background - let's say you are creating a "Guild Crest" to be displayed behind your character. The new layers for that image should be placed before the "Avatar Base" layer in the display order.
When saving an avatar, at least one "Avatar Base" must be present, otherwise it will silently fail as you noticed before.
I will make a note to display an error message in a future version
