Scheduled Commands

Scheduled commands must be enabled in your server's config before anyone can use them.

Once enabled, all members can create schedules up to their limit. Regular users can create up to 3 schedules, while admins can create up to 15 schedules.

Schedule a command to run once at a future time. The command executes automatically and then the schedule is removed.

The when parameter uses the same time format as giveaways (e.g., 30m, 2h, 1d). The command runs relative to when you create the schedule.

Set a command to run automatically on a repeating interval. This is perfect for automated routines like farming harvests or daily check-ins.

The command will run every interval indefinitely until you cancel the schedule. The first execution happens after the first interval has passed.

Admins can schedule messages to be sent to a specific channel at a future time. This is useful for announcements, reminders, or timed event posts.

Message scheduling is restricted to admins to prevent misuse. The message is sent as Nevi, not as you.

View all of your active schedules.

This shows every active schedule with its ID, type (once or recurring), the command or message, and the next execution time.

Cancel a schedule you no longer need using its ID prefix.

You don't need the full ID. Just enough characters to uniquely identify the schedule. You can find IDs using /schedule list.

By default, scheduled commands output their results in the channel where the schedule was created. You can redirect this output to a different channel.

This is useful for keeping automated output out of main channels. Send it to a #bot-spam channel so it doesn't clutter conversation.

Scheduled commands run as you with your current permissions at the time the command executes, not when you created the schedule.

This permission model ensures that scheduled commands can't be used to escalate privileges. If you can't run a command manually, you can't schedule it either.