(events): it got handled by an automated task.

src/events/guild/guildDelete.ts

@@ -1,20 +0,0 @@
-import { CommandClient, Event, Guild } from "athena-prime";
-import { database } from "../../utils";
-
-// ----------
-
-class GuildDeleteEvent extends Event<CommandClient> {
-  event: string = 'guildDelete' as const;
-
-  async handle(context: CommandClient<any, any>, guild: Guild | { id: string }) {
-    // TODO: Instead, it might be safer to have the configuration be marked for deletion instead.
-    // This would prevent the config from being removed if the server owner decides re-adding
-    // the bot is a smart move.
-    //
-    // For simplicity, I'm keeping it like this. In the future this will be handled by
-    // a scheduled task.
-    await database.deleteConfiguration(guild.id);
-  }
-}
-
-export default new GuildDeleteEvent('guildDelete');

src/events/index.ts

@@ -1,12 +1,10 @@
 import guildCreate from './guild/guildCreate';
-import guildDelete from './guild/guildDelete';
 import messageCreate from './message/messageCreate';
 import messageUpdate from './message/messageUpdate';
 import ready from './client/ready';
 
 export default [
   guildCreate,
-  guildDelete,
   messageCreate,
   messageUpdate,
   ready

src/tasks/deleteExpiredConfigs.ts

@@ -3,7 +3,7 @@ import { Task } from "../types/tasks";
 import { database } from '../utils';
 
 class DeleteExpiredConfigsTask implements Task {
-  interval: number = 360;
+  interval: number = 3_600_000;
   init: boolean = true;
 
   async handler(context: CommandClient): Promise<void> {