Stylish

alas, the first (and probably hardest to implement..?) feature is done! it now shows your maximum obtainable royal reputation with your current blueprints, with the material costs and the specific blueprints that you need to craft!

next either i’ll add another feature or make the site not just a huge block of text…idk! im kinda just rawdogging this project :P

this first feature (seeing how much royal reputation you can obtain by crafting your dupes) is taking a lot more steps than i expected. most of the time is spent me fighting typescript. but…

right now, it counts up all the material costs of your blueprints, and tells you how much of each material you need to craft them all!… in the console :P

it goes in order of what gives the most royal reputation per material, which is epics -> legendaries -> rares -> uncommons -> commons

next i’ll

1. clamp it to how many materials you actually have
2. show the specific blueprints that you should craft
3. actually make a ui for it instead of just console.logging ;P

so a lot of this project requires me to type in a bunch of data that isn’t in any api…
theres now like 800 lines in constant.ts with all the data for all the blueprints i bothered to put in so far (elemental collection, which is 104 blueprints… THERES STILL LIKE HUNDREDS MORE BLUEPRINTS ON THE SERVER….)
but now it lists all the blueprints you have (in that collection… ill add the rest later…) alongside its rarity, type (standard, exclusive, or arcane), and all the materials needed to craft it!

next ill be adding a page that automagically tells you the most royal reputation you can get by crafting your blueprints!! (it’s probably important to explain that royal reputation is style trophies you get from crafting duplicate cosmetics..!)

starting on the frontend (which is basically the whole project :P)

so far, it fetches the data from the backend, and gets all materials from the infinibag, which contains info of its rarity, theme/type, and count!

i had to implement the theme/type part of materials manually bc the api doesn’t provide that (only ids, names, and rarities…) so i got a big constant array of materials with their names types and rarities that it pulls from :P

i was a bit lost starting this project because i wasn’t entirely sure how i wanted things to work…
i’m using rust and actixweb for the backend, and i was intending to handle all the data calculation and information and whatnot on the backend. but… rust is REALLY strict with json! trying to extract data from the api would be hell because i’d need a thousand structs for everything! it would suck! so a lot of the work i did was just completely scrapped

instead, i’ve just made one backend endpoint that queries the mcci api to return all necessary info from the username inputted (coins, royal rep, cosmetics, and infinibag/infinivault data). the rest of the stuff will be done on the client because typescript is set up a LOT better to handle json!!

so uh… now i’ll start workin on the frontend / all the data that i wanna calculate with the backend data!!