What's new.

The counter field used to take any channel and then quietly do nothing with a text channel. It now says so while you are still on the page, instead of leaving you to wonder why the number never moves.

Pick the stat and the wording, press Create channel, and the voice channel appears with the right name already on it. Members cannot join it — it is a label, not a room — and you no longer have to build it by hand first.

Saving a stats channel now shows the real number straight away instead of on the next ten-minute round. The same applies after a restart: the counters are correct as soon as CloudMod is back.

If the channel was deleted, is the wrong type, or CloudMod is missing a permission, that now shows up in the logs instead of the counter silently standing still.

Closing a ticket archives the transcript first and only deletes the channel once it has arrived. If the upload cannot reach your archive channel, the ticket stays put with a note explaining why — nothing is closed into a void.

Submitted forms, bot replies and forwarded logs are part of the transcript file, alongside the plain messages and attachments.

If a member blocks direct messages from your server, they get a note in the ticket before it closes, telling them to ask your team for a copy.

The /ticket diagnose report covers every permission the transcript upload needs, so a green result means the file will go through. The panel editor also warns you when "Delete immediately" is picked without a transcript destination — that combination discards the history for good.

Role sync, reminders, giveaways, birthdays and go-live alerts resume by themselves the moment CloudMod reconnects to Discord, without waiting for a restart.

Every channel CloudMod writes to is verified to belong to your network: once when you save the setting, and again each time the bot uses it. A channel it cannot confirm is left alone rather than written to.

All 32 plugins have their own documentation page, and the sidebar is grouped into sections — Quickstart, How it works, Moderation, Community, Tools, Integrations, Troubleshooting — instead of one long list.

The plugin market gives community plugins their own category, so they turn up while browsing instead of only through search.

Choose whether members born on February 29 are celebrated on February 28 or March 1 in the years that do not have one.

Put your own name, colour, logo and footer on the embeds CloudMod posts. Set it once for the network and it applies everywhere the bot speaks.

Give CloudMod its own nickname and avatar on each of your servers, so the bot fits every community instead of looking identical everywhere. Premium, currently in alpha.

Avatars, banners and logos up to 8 MB are accepted, and CloudMod resizes them for you.

A hijacked account firing @everyone across your channels is stopped on that behaviour alone. Exempt the roles you trust so your staff are never caught by it.

If you set one earlier and it never appeared, open the Welcome page and save it once more.

Build a rule that grants a role only when your conditions are met — on this server or anywhere in your network. Test it against a real set of roles first and see exactly what would happen; a test writes nothing, not to Discord and not to your logs.

When something needs a Discord permission or a higher role position, CloudMod says which one and where. /checkperms looks at a whole server, /ticket diagnose at a ticket setup.

New accounts could not be created for a period. If you tried and gave up, please try again.

A failed sign-in returns to the login page with a message you can read.

A rename on the main server syncs outward once, without echoing back to where it started.

The home page shows the servers you can manage, and the message CloudMod posts after being invited says where to go next.

Sign-ups for raids, scrims and group nights. Build one with /event setup, members join with a button, pick a role and leave a note. When someone drops out, the next person on the waitlist is pinged. Currently in alpha.

See who actually brings people in: every join is attributed to the invite that was used, with a leaderboard for your most active recruiters. It does not use one of your free plugin slots. Currently in alpha.

Set it once during setup, and everything scheduled — events, birthdays, announcements — means the same 20:00 across every server.

The plugin market marks which plugins cost nothing against your quota, and shows how far along each one is.

A removed message in your log channel shows who deleted it, alongside the content and the channel it came from.

Pick the role that can receive reputation. Anyone can give it; only role holders collect it, so the leaderboard shows who actually helps.

Unlock a role for an event and forget about it: /temprole add gives someone a role for 12h, 7d or 2w, and CloudMod takes it back when the time is up. It survives restarts, catches up on anything that came due while the bot was offline, and refuses roles it could never take back.

Add or remove an emoji-to-role mapping without opening the dashboard: /reactionrole add, remove, list and clear. Paste the message link, pick an emoji and a role. CloudMod refuses roles it could never assign — anything above its own role — instead of failing silently later.

Running /setup now connects the server and switches CloudMod on in about a minute — moderation with a case history, bulk purge, auto-responses and welcome messages. The dashboard is still there for everything else, it is just no longer the only way in.

Commands that rename, lock, hide or claim something had to finish the change before Discord heard back, so under rate limits they could fail with “the application did not respond”. They now confirm first and do the work after.

The message CloudMod posts after being invited now leads with what it actually does — cross-server sync, moderation, community tools, go-live alerts — and says plainly that a single server is enough. It also reaches the person who added the bot, not just a channel.

Members can now self-assign roles by reacting with an emoji — no button and no label needed. Build the embed in the dashboard with a live preview, map an emoji to each role, and pick whether members can hold several roles or just one.

A single page showing exactly what CloudMod stores and never stores, which Discord permission each feature needs and what breaks without it, plus what an audit entry looks like.

The leveling rank card now shows your position, a progress bar toward the next level with the XP still needed, and your active XP multiplier. Role rewards got stricter validation so a broken mapping is rejected instead of silently ignored.

Your daily member snapshots are now a chart on the project overview instead of a raw list, so you can see whether the network is actually growing.

Single-server projects can assign a role on join without setting up a whole network first.

The safety pass now skips single-server projects entirely and stops posting empty "nothing to do" summaries.

Running just one server? CloudMod now adapts: it goes live instead of dry-run, hides the network UI, and skips cross-server sync until you connect a second server.

Set an updates channel and your server receives short product-update posts from us. Entirely opt-in — no channel, no messages.

New projects get a setup checklist that walks through inviting the bot, connecting a server and creating a first role rule.

Join-to-create voice channels now come with an owner control panel (rename, limit, lock, hide, kick, permit, claim), several lobby presets, and matching /voice commands. Channels clean themselves up when empty.

ModMail was removed rather than left half-working. Tickets cover the same job properly, with panels, private channels and transcripts.

Public network profiles no longer show broken server icons.

Each plugin now has its own page explaining what it does, who it is for and how to set it up, plus a written guide on the blog. Finding out whether CloudMod covers a need no longer means switching it on to see.

Show live counters — members, online, boosters — in voice channel names, with optional milestone goals so your community can see progress toward the next target.

React to every message in a channel automatically, and optionally open a thread for it. Useful for suggestion, showcase and introduction channels that always need the same treatment.

Members thank each other with +rep or /rep, and the points are visible in Discord and on a public leaderboard page for your network.

Welcome messages gained a counterpart: post a farewell when someone leaves, in the same channel or a different one.

Plugins now carry an Alpha or Beta label in the catalogue, so you can tell what shipped last week from what has been running for months before you rely on it.

Set yourself away with /afk. CloudMod replies for you when someone mentions you and clears the status the moment you post again.

/purge deletes messages in bulk with filters for user, bots or attachments. /reminder sets personal reminders, one-off or repeating, delivered in the channel or by DM.

Pick how steeply XP scales instead of accepting one fixed curve, and run double or triple XP events for a weekend without touching every setting.

The plugin market gained search, status filters and a featured row, and it now shows how many plugins your plan has active — no more counting by hand.

Birthday announcements moved to a proper embed, gained an advance reminder and new commands, and are configurable from the dashboard.

Every slash command CloudMod offers is now listed on a public page with its arguments and the permission it needs — searchable, and linkable when you explain something to your staff.

Flood detection now looks at what was actually posted instead of counting messages alone, and acts with a reversible timeout rather than a ban. Busy channels no longer trigger it.

Rapid role changes are grouped instead of posting a line each, so the log stays readable when a member gets several roles at once.