zytesasdch

An annoyingly average discord.js command handler that is very work in progress.

Not really sure what to put here but GH told me to make one kind of omega sus.

zytesasdch class is where your initial loading will take place.

Require --- Deconstruct

require('dotenv').config();
const { Discord } = require('discord.js');
const { zytesasdch } = require('zytesas.dch');

const client = new Client();

Then new constructor on your client.on('ready') event

client.on('ready', () => {
  //passing in the client parameter, and options object as the...
  new zytesasdch(client, {

    /** both commandsDirectory and eventsDirectory
     *  can have whatever name you want.  If the directory specified 
     *  doesn't exist, it'll create it.
     */  

    commandsDirectory: 'commands',
    eventsDirectory: 'events',
    ownerId: [' '],
    prefix: '%',
    mongoURI: process.env.MONGOURI,
  });
  console.log(`Logged in as ${client.user.username}`);

  // .. rest of logging in here
})

Command and Events Folder

Ideally..

File loader will load any folders/files within the specified commandsDirectory and eventsDirectory.

Then require the CommandConstructor and you have some required and optional properties.

//top of ping.js
const { CommandConstructor } = require('zytesasdch');

module.exports = new CommandConstructor({
  name: 'ping',
  aliases: ['pong'], // optional 
  description: 'Ping the pong.',
  leastArgs: 0,
  mostArgs: Infinity,
  ownerOnly: false, // optional
  category: 'fun',
  init: (client) => {
    client.writeOnInfo = ({ result: `${this.name} was loaded.` });
  },
  run: async (message, args, client) => {
    message.reply('Pong.');
  };
});

The three parameters that each command can take are:

• message: Message
• args: Command arguments after the command name [0]
• client: instance of the zyteClient class

Installation

npm i zytesas.dch

License

ISC