Pfiffel’s dye tool is hopelessly outdated. so we find ourselves again lost as to how dyes and cloths look on the ever increasing number of available skins. which is then further compounded by the fact that some dye masks aren’t very well done.
well I’ve been working on a dye tool that isn’t hard-coded like pfiffel’s, it can update itself and run just fine with little to no effort on my part to keep it up to date. it comes in the form of a downloadable application, and looks something like this when run:
you can get the whole thing here on Github, there’s instructions on README.txt.
couple things worth pointing out:
- I don’t have 16x16 skins on there, and don’t plan to until later
- chosen cloths will only display as “Large Cloth” or “Small Cloth”, turns out the xml on static.drips.pw doesn’t connect the names of cloths to their patterns (at least as far as I can tell), but since the patterns are easily recognizable hopefully it won’t be a big deal.
- there are a lot of unreleased/unmentioned skins on there, but they do exist and are 100% real.
#BUT XAKLOR HOW DO I KNOW UR NOT SOME HAXOR OUT TO STEAL MY STUFF?
actually I’m really new to this so I’m not 100% sure how I can assure you of this. I tried putting it through VirusTotal (the same site Jakisaurus put his Jakcodex/Muledump through) but 3/61 detectors still think I’m out to hack your computer or something.
(hash for Dye-Tool.zip is eb6157b9fd3d8435cff285f22536fde13e197af7f1dbb1433d261f8c9a14b0ee)
so for good measure I’ve also included the original DyeTool.py script the .exe was built from, so you can read the entirety of what’s going on for yourself. heck, if you have python on your computer you can delete the .exe and just use the script if you want to be safe (ok actually you’ll also need pygame and the pillow PIL fork but the point stands).
if you have any other ideas of how I can prove my trustworthiness let me know, or you can just not get it.
inb4 someone with actual experience comes along and tells me how inefficient and messy my code is