AutoCommands

How to Create AutoCommands in SuccubusBot

AutoCommands let server managers schedule existing SuccubusBot commands so a channel keeps its rhythm without someone manually nudging it every hour.

What AutoCommands actually do

AutoCommands are recurring SuccubusBot command jobs. They are useful for scheduled image posts, saved-post discovery, loyalty reminders, and other bot commands that already work manually in the target channel.

They are not arbitrary scripts, custom slash commands, or a promise that every command is safe to automate. The simplest rule: test the command manually first. If it works in that channel and makes sense on a schedule, it is a candidate.

Exact syntax and timing

Core syntax: /auto add <interval> <command_line>. Examples: /auto add 2h saved random, /auto add 1d loyalty, or /auto add 4h booru hentai in a channel where that command already works.

Intervals use compact duration text like 5m, 2h30m, 90d, or 1y. They must be at least 60 seconds and no more than 365 days. Runs are approximate because Succubus spaces jobs slightly to reduce burst posting.

Use /auto list to inspect jobs. Use /auto del <jobs> with a job ID or command match; Succubus asks for confirmation before deleting.

Create your first AutoCommand

Use the manual command as proof before you turn it into a loop.

1

Test the command manually

Run the command once in the exact channel where it will repeat. This catches NSFW-channel, permission, and source errors early.

2

Add the schedule

Use /auto add with an interval and the command line you want repeated. Example interval shapes include 2h, 1d, and 2h30m.

3

Manage it with /auto list

Open /auto list to inspect jobs, see unlock state, extend with loyalty points when available, or delete stale jobs.

Intervals

Intervals can be short or long, but they are not exact-to-the-second timers. Succubus adds a small amount of spacing/jitter so scheduled jobs do not all fire at once.

  • 2h means every two hours.
  • 1d means every day.
  • 2h30m combines units.

Permissions

The manager creating jobs needs Manage Channels. Succubus also needs the channel permissions required by the command being scheduled: usually Send Messages, Embed Links, Add Reactions, and Read Message History. Manage Webhooks can improve posting, but missing webhook permission is not the only thing to check.

Free, loyalty, and premium

Free servers can try automation, then use loyalty points or premium where applicable to keep jobs flowing. Premium raises AutoCommand capacity and reduces recurring unlock friction.

Reliability

Jobs are stored durably and designed to avoid duplicate runs across bot processes. Still, Discord permissions, removed channels, and third-party media sources can affect individual runs.

Frequently Asked Questions

Can AutoCommands run any command?+
They can schedule existing SuccubusBot commands that pass validation and work in the channel. Some commands are poor automation targets, and /auto cannot automate itself.
Why did an AutoCommand stop?+
Common causes are missing permissions, a deleted target channel, an external source failing, the command no longer working manually, or a free/loyalty unlock expiring.
How do I delete a job?+
Use /auto list to find the job, then delete it from your manager view or run /auto del with the job ID or matching command text. Succubus asks for confirmation before deleting matches.
Should I automate NSFW posts?+
Only in an age-restricted channel that matches Discord rules and your server expectations. Test manually before scheduling.

Give your server a pulse

Start with one useful recurring command, then expand only after the channel proves it wants the rhythm.