AlphaCloud v1.10.1: Utility, Timed Role Links and Private Ticket Threads

v1.10.1 came out one day after v1.10.0 and is officially a hotfix. Still, it brings a whole new module. The next suggestions were already waiting on the ideas board, and we built five of them right away.

Utility: manage roles and channels without being an admin

The suggestion was simply called "Add a utilities module", with one explicit wish: the permissions should be adjustable in detail. The new module gives your team two commands. With /utility role, members create, give, take, edit and delete roles, with /utility channel they create, delete, rename, lock and slow down channels. The bot carries everything out.

That is exactly where the risk lies. The bot usually has more permissions than the people using it, and a module that passes those permissions on is only as safe as its rules. So each of the ten actions starts switched off, and for each one you set in the panel:

• who may use it: through the matching Discord permission, through roles or both, plus roles that never may
• which roles and channels it must never touch
• how often a member may use it per hour

On top of that come rules you cannot switch off. A role is only touched if it sits below the member's highest role. Whoever gives a role must have every permission of that role themselves, because a lower role can still be allowed to ban. New roles only get permissions from a fixed list that never contains Administrator, Manage Server, Manage Roles, Manage Channels, Webhooks, Ban or Kick, and even from that list only the ones the member has. Every check runs on each use against the server as it is right now, and once more on the confirmation click.

Deleting always needs a confirmation. And because Discord's audit log then names the bot as the one who did it, Utility reports every deletion to our Anti Nuke beforehand. The Anti Nuke counts it against the member who used the command. Without that step, someone could clear out a server through the bot, and the Anti Nuke would only see the bot, which it deliberately does not suspect.

Without Premium, a member can use an action up to 10 times per hour. With Premium it is up to 100, you decide which permissions a new or edited role may get, and you can limit role actions to a fixed list and channel actions to certain categories. If Premium runs out, these settings keep applying. They almost always restrict, and an expired plan should never allow more than before. Everything else is in the Utility documentation (in German).

Role Links: for a limited time and with several triggers

Role Links only launched with v1.10.0, and two suggestions for it came in right away.

Roles for a limited time. A rule can now give its roles for a limited time, from one hour to 90 days. When the time is up, the bot takes them away again, even if it restarted in between: the end is stored before the role is given, because a role without a stored end would never go away. Afterwards the bot does not give them again just because the member still has the trigger role, otherwise "for a limited time" would mean nothing. The roles also show up in Temporary Roles (in German), where you can end them early.

Several triggers per rule. Instead of 20 rules for 20 roles, one is now enough: whoever has any of these roles gets role X. Free servers can use 3 trigger roles per rule, Premium 25. With "Remove again" switched on, the bot only takes the roles away once the member has none of the trigger roles left. More in the Role Links documentation (in German).

Tickets as private threads, understood correctly this time

In the v1.10.0 article we admitted that we first got the idea "Ticket thread" wrong and built private threads, before it became clear that a forum was meant. The story went on: afterwards came the clarification that a private thread was the point after all. So now there is both.

Every ticket category can open its tickets as their own channel, as a forum post or as a private thread, either in the channel with the ticket panel or in a channel of your choice. Unlike a forum, a private thread is only visible to the people in it: the creator, the staff and everyone who may manage threads in that channel. That makes threads a good fit for applications or payment questions too, without filling up the channel list.

There is one Discord quirk you should know: a role cannot join a thread, only individual members can. So the bot adds the members of your staff roles one by one. It works most reliably when your staff roles may "Manage Threads" in the ticket channel, then they see every ticket without a detour. See Tickets (in German).

AFK logs right in the voice channel

Until now, AFK Room logs went to a separate log channel. Now they can go straight into the text chat of the AFK voice channel, where the moved members are sitting anyway. The member mention never pings there. Along the way, the logs got the new message design. See AFK Room (in German).

Fixed

• Forum tickets could not be reopened or deleted with the buttons under the close message since v1.10.0, the bot claimed you were not in a ticket channel
• AI Chat with your own endpoint: a base URL that already ends in a version, like https://api.groq.com/openai/v1 or https://openrouter.ai/api/v1, got a second /v1 appended, and every message went nowhere. Of all forms, this is the one most providers document. A wrong URL or model name now shows a short hint in the channel instead of an error report
• Reasoning models like Groq's openai/gpt-oss-20b returned empty answers through your own endpoint. Now they get enough room for the actual answer
• /moderation roleall posted a new progress message every few seconds on large servers after 15 minutes, because Discord only lets a bot edit a command reply for 15 minutes. Now a single message keeps the progress up to date
• Tickets: the log message for an automatically deleted ticket shows the retention set in the panel instead of always saying 7 days
• Temporary Roles: an incomplete expiry date in the panel shows a clear hint instead of breaking the page
• Language picker in the panel, Bugs, Ideas, Appeals and Transcripts: a new language now sticks on the first try instead of sometimes switching back after the reload

Changed and removed

• The Discord login tokens behind your panel account are now stored encrypted in our database. Nothing changes for you, you do not have to sign in again
• /check: Gamma is no longer available as a provider because its service is offline

You find Utility in the panel under Moderation, and the full list of changes in the changelog on our Discord server. All five new features in this update came from the ideas board. If something is missing for you: ideas.alphacloud.bot.