Scenarios

Group the settings that work together, read them as one list, and see what is not grouped yet.

Set it up

1. Open Scenarios in the workspace. Automations on Qreate become Scenarios: when you create rules, reminders, scheduled messages, panels or other self-running resources, they belong to Scenarios.
2. Under Ungrouped you will find everything Qreate is running for you that belongs to no scenario yet. Pick the things that work together, give them a name, and create the scenario.
3. Open a scenario to rename it, add more configuration to it, or take something back out. The page opens with a preview of what the scenario does.
4. You can also ask Q in chat to group configuration into a scenario or create one from what the server already has. Q creates or auto-groups the scenario once you apply its proposal. Q cannot activate, pause, set up or publish scenarios: those stay in your hands on the Scenarios page.

What to know

• The preview is built from your own configuration, so it is labelled a generated preview. It shows what sets the scenario off, every message it sends as Discord will lay them out, and the steps that send nothing written out in words. It is not a screenshot and not proof that anything has run.
• Looking at a preview changes nothing. It posts no message, creates no channel and schedules nothing, and the buttons inside it do nothing at all.
• Where a scenario has nothing to show, a rule whose only action calls a webhook for instance, the preview says so rather than drawing a message that does not exist.
• A repeating scenario's preview tells you how often it runs and never on what date. On a copy the date is something the destination server fills in, so showing the author's own date would be misleading.
• The preview plays once and stops. If your system is set to reduce motion, you get the same steps as a list instead, with nothing moving.
• Grouping changes nothing about what runs. Putting a live welcome message into a scenario does not switch it off, switch it on, or rebuild it: the module still owns the message, and taking it back out leaves it running exactly as it was.
• Ungrouped is worked out each time you open the page, never stored, so a panel you created a minute ago is already in the list.
• Ten kinds of configuration can belong to a scenario: automation rules, the welcome message, roles on arrival, scheduled messages, reminders, ticket panels, reaction-role panels, forms, giveaways and briefings.
• The welcome message and roles on arrival are server-wide settings rather than one row among many, so a scenario marks them as shared.
• Needs review on a scenario means Qreate rebuilt it from an older project and could not account for everything that project named. Nothing is broken; it is asking you to look.
• A scenario switches on only when you approve it. Setup asks for what belongs to your server: which channel, which role, your timezone, a date. Qreate suggests channels and roles with similar names and never picks one for you, because a channel called the same thing here is not the same channel as the one the author used.
• A date always comes from you. A copied schedule carrying somebody else's date would fire at everyone the moment it was switched on, so the author's dates never travel.
• Review before activation lists what will be created, what already exists and will be taken over, what your members will see, and anything that touches roles, permissions or credentials. Approving is bound to exactly that list: if you edit the scenario or change a channel afterwards, the old approval stops counting and you are asked to read the new one.
• If a check cannot be answered, activation waits. That is not a statement about your server, it means Qreate could not look, and switching something on without knowing is not something we will do quietly.
• If part of a scenario could not be applied, you are told which part and the scenario does not become active. A step whose result we cannot confirm says so rather than claiming it failed, and it is not retried on its own, because retrying something that may have posted is how a channel gets the same announcement twice.
• Pause stops what repeats and takes panels down. Messages already sent stay sent, roles already given stay given, and tickets already open stay open. Nobody can take those back, and we do not pretend otherwise. A panel or rule that another running scenario also uses stays on, and the pause tells you which scenario is keeping it.
• Publish to the Workshop, on the scenario's own page, offers it to other servers. Six steps: what you are publishing, how it reads, what the other server has to choose, pictures, what you are confirming, and send for review. Packaging makes a draft, and nothing is public until a Qreate reviewer approves it.
• Setup guidance is required, because it is the part the other server reads before it chooses anything. Say which channel or role they need to pick and what will look wrong if they pick badly.
• You can add up to eight of your own pictures, PNG, JPEG or WebP, 10 MB each and 100 MB in total, and each one needs a short description for anybody using a screen reader. Uploads are re-saved without their camera and location data before they are stored, and anything you paint over is removed from the image itself rather than hidden, so the covered part cannot be recovered afterwards. Changing a redaction means uploading the picture again.
• The pictures Qreate makes for you come from the package itself, so they always match what a copy would actually do. They are labelled as a generated preview, not as a screenshot of your server.
• Once you send a version for review it is frozen. Editing its wording or its pictures brings it back to a draft, and you send it again. Pictures waiting for review have no public address at all.
• A public catalogue to browse other people's scenarios in is built but not open yet. Everything that lives on a listing's page waits with it: recommending a scenario you have been running, reporting one, and keeping one for later all work and none of them can be reached until the catalogue opens.
• When it does open, a recommendation will need you to have run the scenario on your own server for at least a day, one per server, and a listing shows no rating at all until it has a few. Keeping a listing is private to you: it installs nothing and counts towards nothing.
• You can follow a creator to see their new work under Following in your workspace.
• Follows are private, and only a creator can see their own follower count.