userPFP/source
2024-03-05 20:45:54 -09:00
..
data.json Updating avatar for 881936715063902289 2024-03-05 20:45:54 -09:00
readme.md Changed the data stuff from db to source and changed the dist.css name to import.css because more userfriendliness(tm) hopefully not nuking everything, i kept the old dist so i dont also nuke the import link for everyone 2023-10-02 10:49:45 +02:00
template.css nuke badges, lets see everything break :trolley: 2023-12-02 08:05:03 +00:00

If you aren't sure exactly what all this is about, read here first

data.json

This is the file that dist.css is built from. Badges and avatars are based on user ID, more in template.css

The data file is now formatted differently. All files must be uploaded to coolesding's repository correctly. How to do that is shown in the readme there. All user ID's will point towards this repository, unless there is more behind it than just image hosting (For example shiggy.fun, it will display a random image each time the link is requested).

dist.css

This is the CSS code users import, here the data from data.json is used according to template.css.

template.css

This is the file where the instruction on how to use data.json lies. If the (pseudo)CSS in this file says "Take the ID of the user and replace the avatar of them with the URL next to their name" this is how dist.css is built.

Example:

.{ID} {
    display: none;
}

Would then build the dist.css in a way that would display: none, so hide, every avatar from a user that has the import to dist.css

of course this exact line wouldn't work because it would be to easy, thats why the selectors in this file are so long lol.