Modules

Events

Events are team competitions run through Sparrow. Teams complete tasks for points and send a screenshot as proof, and staff review every submission. You build the event on the dashboard, and players take part with /event in Discord or on the event's web page.

How an event works

1. Staff build the event on the dashboard: its tasks, its teams, and who can review.
2. Sparrow creates the event's channels and roles, and each team gets its own private channel and board.
3. Players run /event submit with a screenshot as proof.
4. Staff approve, modify, reject or undo each submission. Approved points show on the team's board right away.
5. When the event ends, results are posted to every team. A week later, Sparrow removes the event's channels and roles.

Creating an event

Open Events Panel → Create Event on the dashboard. The event is a draft until you start it, so you can save and come back any time. Players can't see it yet. You can also start from a template.

Before you can start, an event needs its channels set up in General and at least one team. A person can only be on one team per event. If you add someone who's already on another team, Sparrow says which team they're on and doesn't add them.

Tasks, tiers and hidden tasks

Each task has a name, a description, points, and how many times it has to be completed. A task that needs a team to do something five times is one task with a required count of 5, and a player can submit progress toward it a piece at a time.

Group tasks into tiers. Sparrow suggests Easy, Medium, Hard and Elite, or you can make your own. Teams see their tasks by tier on their board.

A task can also be hidden: invisible until it's revealed to a team. You choose what reveals it:

• a team reaching a number of points,
• the first team to reach a number of points,
• a team completing every task in one or more tiers, or
• the first team to complete those tiers.

"First team" reveals are exclusive: only the winning team ever sees the task, and it appears in that team's channel. Staff can also reveal a hidden task to one team, or all of them, at any time with /event task reveal.

Submitting and reviewing

Players run /event submit, pick the task, and attach a screenshot. Sparrow works out their team from their roles. If someone is on two active events, the task list shows which event each task belongs to. They can add a note for staff, and say how many they completed.

Each submission reaches staff with Approve, Modify and Reject buttons. Staff can also review from the Event Portal, and Discord updates too. Made a mistake? /event undo sets a reviewed submission back to pending and takes back its points. The player is told why. Every decision is recorded in the event's audit thread.

Team boards and channels

Each team gets a private channel and a board that shows their tasks, progress and points. Boards update when a submission is approved. Staff can move a team's board to a different channel with /event teamboard post, refresh them all with /event teamboard refresh-all, and post a leaderboard that updates every hour with /event dashboard refresh.

Sparrow only deletes channels it created. A channel you picked yourself is never removed when the event is archived.

Who can run an event

Staff access to an event comes from any one of these:

• Event Staff roles: set for each event in its General tab. They can review and use the staff commands for that event only.
• Event Manager Role: set in Events Settings → Roles (or with /roles). Manages and creates every event.
• Sparrow Master Roles and server admins (Administrator or Manage Server): full access to everything.

Everyone with one of these is added to the event's private channels automatically, and removed if they lose the role. None of these roles need any Discord permission. See Access & Permissions.

The Event Portal

Every event has its own web page. Members sign in with Discord and Sparrow shows them the right view. Team members see their team's tasks, members and charts, staff see the review queue, and everyone else sees the standings and tasks. Share the link from the Start tab.

In the Advance tab you can also:

• allow public access with a password, with an optional expiry. Anyone with the password can see the standings without signing in, but not a team's or staff view.
• give each team its own team password, instead of checking their roles.
• add people to a manual allowlist for team or staff access, for role mix-ups or one-off helpers.

After a few wrong passwords, sign-in is paused and the visitor is told to contact event staff. It doesn't say whether they belong to a team. You can clear a pause early on the Event Portal page.

Changing or removing a password signs out everyone who used the old one. A password works for 12 hours before it has to be entered again.

Ratings

Events have their own category in Reviews. Turn it on under Reviews → Event → Review Settings, where you also choose the log channel, and members are asked to rate the event after results go out. Ratings show up in Reviews (where you can search by reviewer) and as a Ratings card on the event's page in Events History. Each event can also use its own rating message instead of the server-wide one.

Templates

To run the same kind of event again, save any event as a template, then start a new event from Events Templates. A template keeps the tiers, tasks and hidden task reveals. It doesn't keep dates, teams, channels or submissions, so you add those each time. Sparrow also has starter templates.

Ending and archiving

An event ends when its end date arrives, or when staff run /event end. Results are posted to each team's channel. Seven days later, Sparrow removes the event's channels and roles (or staff can do it right away with /event archive, which asks you to confirm and lists exactly what will be deleted).

If submissions are still waiting for review when the end date arrives, new submissions are locked and the event ends once staff finish reviewing. /event end asks first when some are still waiting: if you end anyway, they stay unreviewed and earn no points. After an event has ended, a review can't be undone, but Modify still works.

Nothing about the results is lost: standings and every submission stay in Events History on the dashboard, and the event's audit thread stays in your audit forum. Pick the forum, and a category for archived channels, in Events Settings.

Free servers & Premium

Events are free. Every server can run as many events as it likes at once, with up to 300 tasks each, 10 saved templates, reveals on a date or by points or tiers, a portal password for visitors, a custom review message for one event, a custom footer and the Event Manager Role. The one difference is teams: an event can have up to 10 teams for free, or 25 with Premium. Teams you already have keep working if Premium ends.

Commands

Players use the first five. The rest are for staff, and only staff see them suggested in Discord. See Access & Permissions for what each staff tier means.

Have a question that isn't here? Check Common Questions or open a ticket in our support server.