Skip to content

Release v0.0.3

Compare
Choose a tag to compare
@github-actions github-actions released this 19 Jan 04:03
b12828c

Bedrock support's done! πŸš€

At this point, there's a decent amount of initial server types supported to start consolidating, refactoring, documenting, and such. The major want by this point is getting some use of the tool to find any initial flaws in the user design or limitations of the server definition spec!

Some things about the current implementation that aren't great:

  • bedrock version checking is currently implemented as a makeshift webscrapper against Gamepedia's Minecraft Bedrock Edition pages!
    • while mildly fragile, the real issue here is speed -- it's pretty slow
    • the current idea is spinning off some "bedrock server versions" API thingy to act as a cache of sorts
  • code coverage keeps going down as more utility functions dot the packages
    • this may be a necessary evil, but realistically speaking, there's a lot of code living in these cracks that isn't direct calls to the outside world
    • there's enough untouched, bespoke code to justify making the effort to properly test it
  • installing plugins and mods is currently really lame
    • ideally, we could support following URL redirects and compressed archives (.zip and .tar.gz) to improve UX
    • even better would be figuring out some sort of mod page integration so people can specify sources directly like curse-forge or bukkit πŸ‘€
    • there's no way to configure mods that are installed!
  • the config subcommand only shows what's been parsed, not what will be used
    • this shouldn't be too hard to fix, it's really low hanging fruit 🍎 πŸ”«
  • there's no validation of config presets!
    • really need to go back and implement this for currently implemented presets πŸ˜…

The next couple of releases will all center around improving the current implementation and adding user guides for everything we already support!