#plumbobforge

I’ve had something with programming since I was a kid, but it didn't get serious until my high school web development classes. Webdev has always been my main domain, so this is actually my first time making a standalone app instead of a website! Sadly it shows with how many breaking bugs are now showing up, kind of makes me wish I waited with the release instead of pushing it out so early! But I have to endure it for now

If you do keep both installed, just make sure you don't run them both at the same time or try rebuilding with one when the files are in the other one’s folder!

This one is really difficult to find the cause of without knowing what those two files are and with no look into your database for what might be wrong. Hopefully with the new error logs there will be more context given on why those two files don't appear in your game.

For the technical side of why this was happening: PlumbobForge sorts files based on internal resource tags. Main categories (CAS, Build-Buy, and Other) are simple, but sub-sorting becomes way more tricky because different items often share those. You could say it becomes a game of tag... In this case, Build-Buy objects and CAS presets happen to share a tag that was being used for detection. Because the app was checking for CAS items before checking for Build-Buy, it misidentified them as presets. Swapping the order fixed the issue! While testing that fix, I also caught a bug where some sliders were getting mistagged as skins and cleaned that up too.