Data that stays between runs
A flow forgets everything when it finishes, unless you told it what to keep. The Daily question flow keeps two things: the catalogue it picks from, and how many questions it has asked. Both sit in storage fields you set up, and the dashboard shows what is in them.
Stored data
Daily question
117 more entries
42
Illustration only - actual interface may differ
Three ways to keep a value
Every field you set up has a name, a type and a scope. The scope decides who a value belongs to.
A field can hold what the editor works with anywhere else: text, numbers, yes or no, channels, roles, members and lists.
Per member
One value per member of your server, like a count of how often someone answered the daily question.
Whole server
One value the whole server shares. The question catalogue and the counter of asked questions both sit here.
One record per thing
One record for each thing you choose: one per question, one per channel, one per message. Handy for keeping how each question landed.
A field keeps the name you gave it, and you cannot change its type while it still holds data. Every module owns its own fields, and the flows outside a module share one set for the server.
Daily question
ActiveSaveTrigger
ChangeSchedule, every day at 09:00
Get storage value(get-storage-value)
Read the question catalogue from{questions}
Increase storage value(increment-storage-value)
Count the question as asked in{asked}
Illustration only - actual interface may differ
Built for economies and games
Anything that counts, remembers or ranks needs somewhere to put the number: balances and daily rewards, XP and levels, quests and streaks, or a catalogue like the one behind the daily question.
These three modules on the SCNX marketplace are built on storage. All three are German-language modules from community publishers.
Frage des Tages
By Melissas helfende Apps. Keeps the question catalogue and the questions already asked, so the next one is always ready.
Game: Wortsalat by Markus
By Sukram2.0. A letter-scramble word game. Storage keeps the submitted words and the XP per member.
Game: Hau den Maulwurf by Markus
By Sukram2.0. A whack-a-mole reaction minigame, with the scores kept per member.
Room to grow
How much your server can keep grows with its plan, so a server that starts counting one thing and ends up running an economy does not have to think about it. The usage meter in the stored data view shows what your server has used and which fields it went into.
When a field holds something private
You can mark a single field as encrypted at rest. It is an opt-in decision about that one field, not blanket encryption of everything your flows do.
Use it for the values you would not want to read off a table, and leave the rest as they are.
It applies to the field you mark, not to your other stored data.
It cannot be switched off again.
It can only be switched on while the field is still nearly empty.
Leaderboards, ranks, sums and listing across entries stop working on that field.
A value that cannot be decrypted raises an error your flow can catch. It never turns into a silently empty value.
Field settings
Encrypted at rest
OnCan be switched on while this field is still nearly empty. It cannot be switched off again, and leaderboards, ranks and sums stop working on it.
Illustration only - actual interface may differ
Storage questions
No. Storage belongs to the server it was written on. Inside a server, each module keeps its own fields and the flows outside a module share one set for the server, and those two never mix.
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.