Changelog

What shipped, newest first, and who asked for it.

  • 27 Oct 2026

    Fixes

    The header did not fit at exactly 768 pixels, so every page scrolled sideways on a tablet. Choosing the light theme worked until you changed page, because a hard-coded class was winning against your choice. Dimmed text failed its contrast floor in light mode. The API parameter tables were unreadable on a phone. And the sitemap listed twenty of the thirty-four pages that exist.

  • 27 Oct 2026

    Built with the community

    A board at /community for what you want built, a public roadmap, a changelog, and rewards for ideas that ship. The awkward parts are on the page before you write anything. Most suggestions earn nothing, even good ones. Votes tell us what matters and do not decide the roadmap. A month of Bloom is sometimes given for an idea that ships, capped at twelve months for an account, and it is always a decision a person makes rather than something a vote count triggers.

  • 27 Oct 2026

    My Bloom, for the person who bought your software

    Bloom had two completely different users and one interface, so somebody looking for their download landed in a workspace picker. Buyers now have their own environment: what they own, their licences, their downloads and their orders. The change that matters most to you is that a customer who changed laptop can reset their own machine lock, twice per licence per thirty days, and it is recorded in your log like any other action. That was a support ticket before, and it was the most common one.

  • 27 Oct 2026

    Orders, releases, a first-run checklist, and search

    Four gaps in the creator panel. Orders lists what was sold. Releases shows which versions are still being validated, which needed a change: the validate endpoint always accepted a version and always threw it away, so that page fills as traffic arrives rather than showing history it never had. A new workspace now has a six step checklist, each step read from your real data rather than ticked off by a button, and a demo product you can seed and delete in one click. Ctrl+K searches licences, products, people and orders.

  • 27 Oct 2026

    A homepage that shows the panel instead of describing it

    The old one was twelve thousand pixels of text with almost nothing to look at. It is shorter now and has far more in it: the nine things Bloom does as a diagram you can tab through, the panel's own five screens behind real tabs, and the licence check as an actual request and response rather than a paragraph about one.

  • 27 Oct 2026

    Seven pages for what you build, seven for what Bloom does

    Licensing a Minecraft plugin and licensing a desktop app are the same product and a different conversation. There is a page for each now, under /solutions, for plugins, desktop apps, Discord bots, game tools, games, web apps and developer tools. Each one says what Bloom does not do for that audience as well as what it does. Bloom does not obfuscate your jar. There is no anti-tamper agent to install. Knowing that before you sign up is worth more than finding out after. Alongside them, a page per capability under /features.

  • 27 Oct 2026

    Documentation you can read without an account

    You could not see the API without signing up first, which asks for the commitment before the proof. There are ten public pages at /docs now: a quickstart, authentication, validate, issue and revoke, webhooks, errors, rate limits and Sign in with Bloom, plus an overview at /developers. The examples come from the same source the panel shows you, in six languages, so the two cannot drift apart.

  • 27 Oct 2026

    The people in your Discord server, on your People page

    The People page could only see somebody who had already bought something. The person sitting in your server who has not bought yet is the most interesting name on that page, and Bloom could not see them at all. The bot now keeps that list in step. People are marked by how Bloom knows them: a customer, staff, somebody invited, somebody in your Discord, or a bot. Bots are counted separately, because a server full of bots is not a server full of customers. This needs the Server Members intent switched on for your bot in the Discord developer portal. Until it is, nothing else stops working.

  • 27 Oct 2026

    Invite somebody who does not have an account yet

    Adding a member only worked if they had already signed up, which is the wrong way round: you invite somebody precisely because they are not here yet. Now an address without an account gets an invitation instead of a refusal. They make their own account, with their own password, and accept it themselves. We do not create one on their behalf, and the invitation can only be accepted while signed in as the address it was sent to.

  • 27 Oct 2026

    Somewhere to ask a question

    There was one way to reach us and it was a Discord invite. That is right for most of who buys this and wrong for the rest, and wrong in the case that matters most: deciding whether to put your customers' licences here should not require joining a chat server to ask a question first. There is a form at /support now. It reaches a person either way, it says plainly whether anybody is at a keyboard rather than showing a chat bubble nobody is behind, and if you have an account the whole thread lives there.