printing legion bot
- 6 Devlogs
- 7 Total hours
This bot doesn’t slack off. Your printer shouldn’t either.
This bot doesn’t slack off. Your printer shouldn’t either.
It is now more reliable, though it’ll still go down when hackai goes down and slack just stop responding every once in a while. It is now more clear in the testing guidelines, and I have improved the reliability of the region checking. I have also removed the feature where it checks for duplicates, as spam isn’t much of a problem (for now) and it makes testing hard.
I updated the readme with the required changes, and I also fixed the bug where it would say (undefined) if the printer didn’t specify filament stock.
After some feedback from some beta testers, i found that people want dimension filters, since most post companies only accept mail under a certain set of dimentions, and mail is much cheaper than parcel, especially internationally. I wired everything up to threejs and occt and the github api and got the bounding box. Now, there is also a /add-custom-filter command, allowing you to restrict it to any arbitrary set of filters.
I got it running on the server, but since most of my time was spent over ssh, that wasn’t captured by hackatime, but anyhow, it runs on the server now, and I also got a bunch of willing beta testers who are also printing for printing legion.
I got the database working, and the bot probably almost completely works. There is now a /add-as-printer command where you can specify the region where your receiving prints, and it will only include those. I also got eslint setup and refactored the whole codebase. Next, I need to make and upload all the assets like the icons and stuff and make good documentation. Also, I applied for a best server and I’m waiting for approval.
The bot is now able to parse print requests into a json schema using the hack club ai api. Currently the api is down, but it still kinda works with stealth models since they’re free, so right now, i’m using stealth/ox-alpha. I will switch to gpt oss 120b soon for speeeeeed. next, i’ll setup a json db (ik, eww, but it’s easier and im lazy) to store the requests.