Edit history

Earlier versions of Bots receive GUILD_CREATE for every existing guild on connect, newest first.

Current version | Edited by Rex1d ago

Changes

Guild Create Event misleadingBots receive GUILD_CREATE for every existing guild on connect

Show

Bots receive GUILD_CREATE for every existing guild on connect

Observed behaviour

I'm developing my own bot and when I use Events.GuildCreate from @fluxerjs/core, the bot lists all guilds it's in every time I start the bot.

Reproduction steps

import { Events } from "@fluxerjs/core";

const guildCreateEvent = {
    event: Events.GuildCreate,
    execute: async (client: any, guild: any) => {
        console.log(`Joined guild: ${guild.name} (ID: ${guild.id})`);
    },
};

export default guildCreateEvent;

Here is a back-to-back test run

 *  Executing task: npm run start 

npm notice run fluxer-getting-started-bot@1.0.0 start
npm notice run tsx src/index.ts
Getting Started Bot is connected to Fluxer.
Command prefix: !
Joined guild: Getting Started (ID: 1548890981661671424)

 *  The terminal process 'npm run start'" terminated with exit code: 512. 
 *  Terminal will be reused by tasks, press any key to close it. 

 *  Executing task: npm run start 

npm notice run fluxer-getting-started-bot@1.0.0 start
npm notice run tsx src/index.ts
Getting Started Bot is connected to Fluxer.
Command prefix: !
Joined guild: Getting Started (ID: 1548890981661671424)

Build information

"@fluxerjs/core": "^3.0.0"

Platform

API

Original by Rex21d ago