Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Create a const that has the createTicket function in it, and don't call the const at all, It still calls the const and creates a ticket.
Expected behavior
Not calling the const shouldn't call anything in that part of the code.
const { PermissionFlags, EmbedBuilder, resolvePermissionsToBitfield } = require('@fluxerjs/core')
module.exports = {
name: 'ticket',
description: 'Create a ticket for support!',
async execute(client, message, args) {
const guild = client.guilds.get(message.guildId) ?? await client.guilds.resolve(message.guildId)
console.log(message)
const channelCreate = guild.createChannel({
type: 0,
name: message.author.globalName,
parent_id: process.env.TICKET_CATEGORY,
});
const create = new EmbedBuilder()
.setTitle('Ticket has been created.')
.setDescription('Please check the channel that you have been pinged in.')
.setTimestamp()
await message.reply({ embeds: [create] });
}
}
What you expected to happen.
Environment
- @fluxerjs/core version: 1.2.4
- Node.js version: 25.6.1
- OS: Linux(arch)
Additional context
Add any other context about the problem here.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Create a const that has the createTicket function in it, and don't call the const at all, It still calls the const and creates a ticket.
Expected behavior
Not calling the const shouldn't call anything in that part of the code.
What you expected to happen.
Environment
Additional context
Add any other context about the problem here.