Three Months, 24 Releases: What AlphaCloud Became

On 1 June 2026 we started counting versions. On 6 September we were at v1.8.0. Between them sit 24 releases, and this is an attempt to turn that into a line rather than a list.

The four phases

June: modules. Honeypot, Sticky Roles, Temp Voice, account age, role names, support call. Plus AI chat with a long-term memory per user. The phase where the basic kit came together.

July: tools instead of features. The Advanced Builder for custom commands, a visual flow editor with real branching. Then Automations, a trigger and an action you assemble yourself. The difference from June is fundamental: before, we built features; from July we built blocks that servers use to build their own.

August: money and protection. Anti Nuke, AutoMod and the level system on one side. On the other, the complete payment pipeline, including withdrawal, cancellation and a billing portal. Less visible and considerably more work than anything before it.

September: the Message Builder. Almost every message the bot sends became designable. In hindsight the logical continuation of the July idea, applied to the text rather than to the flow.

What the version numbers tell us about ourselves

Of 24 releases, 7 were marked major and 17 hotfix. That sounds like a stable product with occasional corrections.

It just is not true. A look at the supposed hotfixes:

• v1.5.1 brought two new modules, Support Hours and Team Feedback, plus the logo collection
• v1.6.1 brought AutoMod and the level system, two of the larger modules overall
• v1.6.2 brought Anti Nuke, the Auto Responder and the self-hosted AI option

Three releases marked as bug fixes that in truth shipped six modules. Our own versioning scheme says vX.Y.Z with Z above zero is a correction. We repeatedly just did not honour that.

Why it matters: the version number is the only information a server owner gets about an update before reading the changelog. If "hotfix" actually means "three new modules", at some point they stop reading it at all.

What changed three times over

One pattern we noticed while reviewing: we patched the same places repeatedly, always in the same direction.

Slash commands. v1.5.0 records that commands could disappear on servers running several command-based modules at once. Fixed. v1.5.1 records that registration stopped getting through on large servers because it asked per module and per server separately. Also fixed. Two different causes, the same symptom, and neither would have happened with one shared place from the start.

Nickname prefixes. v1.6.0 lists five corrections to a single module. Five. A sign the original design was wrong and that we repaired it for too long instead of replacing it.

The AI. That gets its own article, because the story is too good to handle in two sentences here.

What we take from it

The most honest sentence about these three months: the visible part was rarely the expensive part. The Message Builder is the headline of v1.8.0, but the payment pipeline from v1.7.0 cost more time, produced more bugs and dragged more legal text behind it than any module before it.

For the coming months we have two intentions that have nothing to do with features: make the version numbers honest again, and when a module has been patched three times, touch its design on the fourth rather than the bug.