Today, when developing an add-on, your options for auto-updating usually consist of having none, building your own, or using RTB.
With all three options you usually end up having to repackage your add-on every time you release it. In addition to this, each approach has it's own disadvantages. Having no auto-updating at all quickly gets tedious for your users if you need to update something, and people aren't very likely to actually update. Building your own takes a non-trivial amount of work, and delivers an inconsistent user-experience to your users. RTB has a
lot of latency, and it's not unusual to have to wait for days, if not weeks, before your add-on or update is actually released to your users, making it inconvenient for regular releases and almost impossible to use for beta releases and similar. What if releasing an update was as simple as pushing the update to your Bitbucket or GitHub repository, and it'd then be released to users within 5 minutes?
So is this a replacement for RTB, then?No. RTB provides a lot of features that Brickbucket does not even plan to offer, including stuff not related to add-on management (RTB Connect), as well as a useful service for
discovering add-ons. Brickbucket is supposed to come into the picture
after you've "sold" the add-on to the user.
Features- No extra effort for you as the developer, just push it to Bitbucket or GitHub as usual (make sure to structure your repository layout like this)
- Updates released to users within 5 minutes
- In-game auto-updater
- Web-based endpoint that automatically repackages your add-on for Blockland, and includes the metadata required for Brickbucket to function
- Open source
StatusServer - Working
Client - Not yet started
LinksServer Bitbucket repositoryIssue tracker