Get your server into the V3 beta
The beta is rolling and reviewed by hand. Tell us about your server and what you want to build. We read every application and reply personally.
What you get
Access to the system, and a room where the people building with it talk to each other and to us.
Early access on your server
V3 is unlocked for the server you applied with. Your bot restarts once and the new system sits next to your V2 commands.
A private beta category
In the ScootKit Discord: announcements when something ships, a channel to talk with the other testers, and a forum for feedback.
A direct line to the team
The people building V3 read the beta channels. Bug reports and rough edges go straight to them.
A say in what ships next
Feedback from the beta is where we take the next batch of work from. Say what is missing and make the case for it.
Publish modules during the beta
Bundle your flows into a module and put it on the SCNX marketplace. Keep it private and share it by link, or apply for a public listing.
What we ask of you
The beta works because the servers in it tell us things. Three of them matter most.
Feedback we can act on
When something breaks, tell us with steps we can reproduce. When something confuses you, tell us that too. Confusing counts as a bug.
Some of your time
Mostly over the first weeks. Build a couple of flows, then say how it went. That is the whole ask.
Honesty in the application
Tell us what you want to build and how much time you have. A small honest plan reads better than a big invented one.
There is no support for building flows yet. That covers setup, building flows and debugging, whether the flow came from an app you installed or you built it yourself. If it came from an app, ask its developer. Reproducible bugs are a different matter, send those our way. For everything else, the beta community and the docs are where you get help.
How it works
A rolling program. No waves, no deadlines, no counters.
Apply from your server
The apply button opens the SCNX dashboard and asks you to pick the server. Then you answer a few questions about it and about what you want to build.
We read every application
Your application becomes a support ticket that a person reads. We reply personally, and we ask a follow-up when something is unclear.
You hear back
Usually within a few days. If we say yes, that reply carries the Discord invite and where to go from there.
Turn V3 on
From the dashboard, by the server owner or a co-owner. You confirm two things about how flows behave, the bot restarts once, and V3 is live next to your V2 commands.
Who should apply
V3 pays off for people who want to build something specific. If you are not there yet, V2 is not going anywhere.
You build things for your server
And you have a list of ideas V2 could not carry.
You want other servers to install what you made
Modules can go on the marketplace during the beta.
You already stretch V2 to its limits
And you keep running into the same wall.
Wait if
You need three simple commands that answer with a fixed message. V2 does that today, it keeps working, and it is the better tool for the job.
Tips for a strong application
We read every one. These are the parts we look at.
Thin applications get declined. One line about a server and no idea of what you would build gives us nothing to go on. A decline is not permanent, so take another run at it and send it again.
Be specific about what you want to build
"An economy with a daily reward, a shop and a leaderboard" tells us far more than "lots of cool stuff".
Tell us what you tried
Which V2 commands or which other bots you used, and exactly where they fell short. That part shows us where V3 still has to get better.
Say how much time you have
An honest "two evenings a month" is fine, we plan around it. An invented "every day" helps nobody.
Questions about the beta
Yes, but send one application per server. Each application belongs to the server it was started from, and access is granted per server.
More of Custom Commands V3
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.