SKINS FOLDER, tthen OLD GLORY FOLDER WITH SKINS.json

[madmaxgrey]

the way your applying this shit is stupid to be blatant, it should be a on and off not just take over the entire setup when you have a patcher running you expect to be able to swap skins without conflict,

recreate the installer and turn it into a configuration creator then have it make a old glory folder in the steam-ui/skins folder with a skins.json so you can turn it on and off

[PhantomGamers]

Strange that I don't see a pull request linked to this issue with how rude your message was. If it's so stupid, maybe you should fix it.

[Jonius7]

If 6.0 ever comes out, a rework might be necessary. But SteamUI-OldGlory has been designed to be independent of other patchers (and would run beside SFP)

Additionally, there is nothing stopping you from manually copying the theme files over to skins folder

[Jonius7]

So OldGlory now has unofficial Millennium support - as in, I've made a skin.json and put in a libraryroot.custom.css into the millennium subfolder: https://github.com/Jonius7/SteamUI-OldGlory/tree/master/millennium

Keep in mind that this is just default config OldGlory CSS which you can use directly. If you want different settings however: for now you can create your own version of libraryroot.custom.css with the installer and then hit the Reset button to clear your changes, copy the files over to the steamui\skins\OldGlory folder for Millennium to use.

In the near future, I intend to update the OldGlory Installer with a "local mode" so that it won't write directly to the steamui folder - this will be good for skin developers and the like.

[Jonius7]

I have deleted the millennium subfolder and am releasing 5.14 where you can now select the Install Location for OldGlory CSS files - in Advanced Options select the Millennium option and OldGlory will install to steamui\skins\OldGlory automatically.

[Jonius7]

In 5.15, SteamUI-OldGlory now installs to steamui\skins\OldGlory by default.