Auto db push for guilds

[Natemo2625]

Explain your suggestion
I wish that it would automatically check for guilds the bot is in when started and update the database accordingly so I don't have to kick and re-invite the bot to get slash commands to work for every server it's in

[Natemo2625]

Hello, has anyone seen this? Would really help with slash commands not working after system changed and/or DB loss

[Natemo2625]

Will someone please have a look at this? Would solve all of the problems that I'm facing if it were added.

[Natemo2625]

Could someone at least give me a starting point to fix it myself? It's really annoying

[PhantomNimbi]

That would be done via the bot start event emitter.

/*
* client is your discord.js Client
* commands obj is your command data you want to add to the guild
*/
client.on('ready', async (guild) => {
guild.commands.set(commands).then(() => 
console.log(`Commands deployed in guild ${guild.name}!`));
})

Naturally, it would need to be adjusted for this bot's code. But, that's the general idea of how it would be done the easiest.

Might also be a good idea to have some sort of check in there to prevent from updating anything that hasn't changed.

[Natemo2625]

Ah alright, thanks for the starting point, will comment here again if I've got it working

[PhantomNimbi]

Ah alright, thanks for the starting point, will comment here again if I've got it working

It looks like for this bot you might just need to add this to the client.on("ready", async () => { ... }); event emitter:

ApplicationCommandRegistries.setDefaultBehaviorWhenNotIdentical(
        RegisterBehavior.BulkOverwrite
);

So, basically the ready event in the index.ts file would go from this:

client.on('ready', async () => {
        client.music.connect(client.user!.id);
        client.user?.setActivity('/', {
                type: ActivityType.Watching
        });

        client.user?.setStatus('online');
        const token = client.twitch.auth.access_token;
        if (!token) return;

        // happens to be the first DB call at start up
        try {
                const notifyDB = await trpcNode.twitch.getAll.query();

                const query: string[] = [];
                for (const user of notifyDB.notifications) {
                        query.push(user.twitchId);
                        client.twitch.notifyList[user.twitchId] = {
                                sendTo: user.channelIds,
                                logo: user.logo,
                                live: user.live,
                                messageSent: user.sent,
                                messageHandler: {}
                        };
                }
                await notify(query).then(() =>
                        setInterval(async () => {
                                const newQuery: string[] = [];
                                // pickup newly added entries
                                for (const key in client.twitch.notifyList) {
                                        newQuery.push(key);
                                }
                                await notify(newQuery);
                        }, 60 * 1000)
                );
        } catch (err) {
                Logger.error('Prisma ' + err);
        }
});

to this:

client.on('ready', async () => {
        ApplicationCommandRegistries.setDefaultBehaviorWhenNotIdentical(
                RegisterBehavior.Overwrite
        );

        client.music.connect(client.user!.id);
        client.user?.setActivity('/', {
                type: ActivityType.Watching
        });

        client.user?.setStatus('online');
        const token = client.twitch.auth.access_token;
        if (!token) return;

        // happens to be the first DB call at start up
        try {
                const notifyDB = await trpcNode.twitch.getAll.query();

                const query: string[] = [];
                for (const user of notifyDB.notifications) {
                        query.push(user.twitchId);
                        client.twitch.notifyList[user.twitchId] = {
                                sendTo: user.channelIds,
                                logo: user.logo,
                                live: user.live,
                                messageSent: user.sent,
                                messageHandler: {}
                        };
                }
                await notify(query).then(() =>
                        setInterval(async () => {
                                const newQuery: string[] = [];
                                // pickup newly added entries
                                for (const key in client.twitch.notifyList) {
                                        newQuery.push(key);
                                }
                                await notify(newQuery);
                        }, 60 * 1000)
                );
        } catch (err) {
                Logger.error('Prisma ' + err);
        }
});

That should fix it if I'm not mistaken. There might be some indentation errors, however, since I made that edit entirely from GitHub mobile.

[PhantomNimbi]

Thinking about this a bit more. It might be better to have a command that updates all commands and then restarts the bot to load the changes in every guild.

[Natemo2625]

Hmm alright, I can try to do that

[PhantomNimbi]

✅ Update: Auto Command Registration & Database Management Implemented

The automatic slash-command registration requested in this issue has been implemented. The bot now auto-registers and syncs commands across all guilds it belongs to on startup — no need to kick and re-invite the bot after a system change or database loss.

---

🔄 Auto Command Registration (the core request)

• apps/bot/src/lib/setup.ts now sets Sapphire's registry behavior to bulk-overwrite:

  ApplicationCommandRegistries.setDefaultBehaviorWhenNotIdentical(
      RegisterBehavior.BulkOverwrite
  );

• With this, Sapphire automatically detects new/changed commands and bulk-overwrites the command list in every guild the bot is present in on startup.
• Commands also auto-register via the global command registry, keeping the bot's command surface in sync after any system change.

🗄️ Automatic Database Management (the "DB loss" part)

• scripts/common.mjs adds ensurePostgresService(), which on launch:
  • Auto-detects whether PostgreSQL is already running (port 5432).
  • If not, auto-starts it cross-platform (Windows service, macOS brew, Linux systemctl, with a Docker Compose fallback).
  • Waits for the database to become ready before the bot initializes.
• This ensures the database is available and connected at boot, eliminating slash-command failures caused by a missing/stopped DB.

---

🔗 PR Status

This work is bundled into the open maintenance PR:

PR #829 → #829

• Branch: PhantomNimbi:main
• Status: ✅ Open & Ready for Review
• Summary: feat: modernize monorepo, upgrade Lavalink v4 & cipher, enhance dashboard, and fix auth/tooling

This issue is now resolved pending PR #829's merge.