Current Priorities

[Enchoseon]

Short Version

Make things more extensible and stable--clean up spaghetti.

Long Version

• 🔴 Make the main branch stable enough for a new release (lots of bugs were introduced by package upgrades)
• 🟢 Add debug-info command to output useful debugging info (streamline debugging issues with a bunch of sanity checks)
• 🟠 Fix weird problems with loopback addresses (stopgap: added config.proxy.loopbackAddress)
• 🟠 Fix registry.isSupported crash (it may have been fixed by package upgrades)
• 🔴 Move thread blocking log and WDL stuff to a separate thread
• 🔴 Add setters and getters to status object instead of arbitrarily writing crap to it and doing wacky type checks.
• 🟠 Improve inline documentation.
• 🔴 Make external Mineflayer dependencies (mineflayer-auto-eat, mineflayer-antiafk) optional. Main point isn't minimalism per-say, but a more modular design with smaller attack surface.
• 🔴 Add a state machine to the Mineflayer bot. At the moment it's more convenient for tinkerers to rip out the boilerplate rather than build off of it.
• 🔴 AUR package
• 🔴 Make error logging actually work.
• 🔴 Add ability to log raw packets to the MCPR (ReplayMod Recording) file format.

[unclamped]

As for the first issue, which bugs are you talking about more specifically? You told me in PMs about some reports that weren't made through GitHub issues, maybe you or the person who reported them could compile them in different issues so it's easier to look into them?

[Enchoseon]

I think most of them were just variations of not knowing which loopback address to use or the registry.supportFeature crash in #1. The only concrete ones I can recall are:

• The crafting crash Crafting #10
• Crafting when reading a book (will have to see if it can be replicated on the main branch before adding an issue)
• Supervisor constantly-restarting a script under very vague and unknown circumstances

I've asked the poor lad who reported the problems to make the issues, will see if they do and update this comment.

Iirc, a lot of bugs were 2b-specific, maybe caused by ViaVersion.

[unclamped]

As for the crafting crash, it looks like it's on v1.0.4? I couldn't reproduce it in the main branch, and I can't test by myself if it does crash on v1.0.4 because the version itself doesn't start at all in my host. Plus, the creator of the issue hasn't interacted with their GitHub account since they created the issue, so, it's probably not that important.
As for the crafting/reading crash, how can you read a book and craft at the same time? 🤔
As for the supervisor crash, I've been using it and haven't gotten any errors yet. However, I'll make sure to report any findings.

Tbh, the main branch seems a lot more stable than the actual latest release lol. Unless something more concrete pops up, then it shouldn't be a top priority