What does the beta cost?

Nothing on top of what you already pay. V3 is part of your hosted custom bot on SCNX, so there is no separate price for it. Storage and the activity budget grow with the server and its plan, and the dashboard shows where your server stands.

The server owner or a co-owner. Enabling V3 is a server-wide decision, so it is limited to those two. The bot restarts once when you turn it on, and once more if you ever switch back.

Is it safe to let flows act on my server?

Flows run with your bot's Discord permissions and nothing beyond them. Every server has an activity budget that grows with its size and its plan, and a run that tries something extreme, like messaging or removing large parts of your server at once, is stopped before it happens. One button on the overview stops every flow and restarts the bot without deleting anything. Before the enable button unlocks, you confirm in writing that flows act with the bot's permissions and that V2 keeps running alongside.

What happens to my flows after the beta?

They stay, and so do your modules. The beta is about who gets access and how quickly we can react to feedback, not about throwing work away. We will announce general availability in the SCNX changelog. We are not putting a date on it.

Through the apply button on this page. It takes you to the SCNX dashboard, asks you to pick the server, and opens a support ticket with a few questions about your server and what you want to build. We read every one and reply personally.

Custom Commands V3Beta

Build automations, not just commands

Something happens in your server, a flow runs, your bot does the rest. This flow wakes up at 09:00, takes the next question out of storage, posts it in #general and opens a thread for the answers.

Apply for your server How the beta works

Daily question

ActiveSave

Trigger

Change

Schedule, every day at 09:00

Get storage value(get-storage-value)

Read the question catalogue from{questions}

Pick the next entry(array-at)

The one after yesterday's

Send message(send-message)

Input parameters

Channel:#general

Message:Question of the day

Create thread(start-thread-from-message)

Open a thread on that message

Increase storage value(increment-storage-value)

Count the question as asked in{asked}

Illustration only - actual interface may differ

What changed from V2

A V2 custom command has one trigger and one fixed reply, and for rules, links and canned answers that is still the right tool. The flow above starts the same way and then keeps going: it reads stored data, picks the question, sends the message, opens a thread and writes back what it used.

You build that out of 96 triggers, 691 actions and 181 parameter types, and V2 keeps running next to it. Turning V3 on leaves your existing commands untouched, and there is a way back. One bot restart in each direction.

Custom Commands V2

Rules

ActiveSave

Trigger

Change

/rules

Send message

The same reply every time

Custom Commands V3

Daily question

ActiveSave

Trigger

Change

Schedule, every day at 09:00

Get storage value(get-storage-value)

Read the question catalogue from{questions}

Pick the next entry(array-at)

The one after yesterday's

Send message(send-message)

Post the question as an embed in#general

Create thread(start-thread-from-message)

Open a thread on that message

Increase storage value(increment-storage-value)

Count the question as asked in{asked}

Illustration only - actual interface may differ

What is in V3

Seven parts, one system. Start with a trigger and go as far as you like.

Triggers

Slash commands, buttons, member events, schedules. Anything that happens in your server can start a flow.

How triggers work

Flows and the editor

Build what your bot does step by step. Branch, loop, wire values from one step into the next, test before you activate.

Inside the editor

Storage

Give your flows a memory. Counters, catalogues and profiles that are still there tomorrow, for your server and for each member.

How storage works

Modules and apps

Bundle flows into one installable thing, with its own settings, translations and guides.

How modules work

Marketplace

Share a module by link or publish it for everyone. Updates reach the servers that installed it, reviews tell you how it lands.

Marketplace and publishing

AI authoring

Connect an MCP client and describe what you want. It drafts the flow, you review it and activate it.

AI authoring

The beta program

How to get in, what we ask from testers, and what happens after you are accepted.

The beta program

Built by servers already in the beta

Three modules built with V3 and published on the SCNX marketplace, where any server can install them.

Frage des Tages

by Melissas helfende Apps

Posts a question of the day into a channel with its own thread, and lets members suggest questions that your team reviews.

View on the marketplace

Game: Wortsalat by Markus

by Sukram2.0

A letter scramble word game with submitted answers and XP per player.

View on the marketplace

Game: Hau den Maulwurf by Markus

by Sukram2.0

A whack-a-mole reaction game, scored per member.

View on the marketplace

These are community modules, published by their developers. Their content is in German.

Want your server in the beta?

V3 is a large system and it still moves fast, so servers come in one at a time instead of all at once. Every application is read by a person, and you hear back within a few days.

The servers already in the beta decide a good part of what we build next. What you build is yours: flows and modules stay when the beta ends.

Apply for your server How the beta works

Questions about V3

Yes. Enabling V3 does not touch your existing V2 custom commands. They keep running and stay editable, and V3 is added alongside them. You can also switch back to V2 later. Both directions need one bot restart.