Error: Cannot find module '/root/packbot'
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:941:15)
at Function.Module._load (node:internal/modules/cjs/loader:774:27)
at Object. (/usr/local/lib/node_modules/pm2/lib/ProcessContainerFork.js:33:23)
at Module._compile (node:internal/modules/cjs/loader:1109:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)
at Module.load (node:internal/modules/cjs/loader:989:32)
at Function.Module._load (node:internal/modules/cjs/loader:829:14)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:76:12)
at node:internal/main/run_main_module:17:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}

When using the !beer command, if no args are provided, command returns undefined.

user input should by most triggers be only the username.

Per kaffie, !joint should take a single argument after passing proper sanitazion.

You can !pack more than once withing the pre-set time of the trigger.

This is a much needed feature for me to properly enjoy this discord bot.

A user would trigger !edibles and then the bot would respond similar to the way that !beer does

As a footnote: the commands from discord should be accessible on irc as well.

https://github.com/s4turns/PackBot/blob/f2761a7b2d176ce51f7216fa8500b7c536c9a5c8/commands/bong.js#L4

23:25:20 <@interdom3> let roleMembers = message.guild.roles.get(role).members.map(m=>m.user.tag);
23:25:21 <@interdom3> TypeError: Cannot read property 'members' of undefined
23:25:22 <@interdom3> pls

added !joint following is the code

if (command === "joint") {
 if (args.lenght > 0) {
  return message.reply(`you can only light YOUR OWN joint, sorry!`);
  }
  else {
   message.channel.send(`lights ${message.author.username} joint! smoke up broheim!`);
   }
  }

As the code base keeps on growing at an even speed, we should plan to migrate to a better directory hierarchy migrating event triggers and commands to their own scripts and folders.

• Add PackBot quotes system.

fml

const client = require('./config.json');
^

SyntaxError: Identifier 'client' has already been declared
at createScript (vm.js:56:10)
at Object.runInThisContext (vm.js:97:10)
at Module._compile (module.js:549:28)
at Object.Module._extensions..js (module.js:586:10)
at Module.load (module.js:494:32)
at tryModuleLoad (module.js:453:12)
at Function.Module._load (module.js:445:3)
at Module.runMain (module.js:611:10)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:160:9)

Add the weather trigger handle for packbot.

some of the admin commands as !prune need extra boundary check to avoid abuse. some of the considerations to have are

1. User should only be able to delete his/her own messages.
2. Prune should only go up to 50 instead of 99.
3. User should only be able to use prune once a day? (request for input on this)

Farther boundaries checks should be apply in general.

Without !bøtte one user is unable to partake in their preferred way of using the wonderful plant we all love.

By adding the !bøtte feature this user will not feel left out when everyone else is smoking.

##TODO: !beer should only take either 0 or 1 argument. if 0 arguments are provided it should trigger the response (here ${user2}! take this an ice cold beer! Its a Warsteiner!);
If 1 argument is provided, it should sanitize the input by checking that the argument is a legal username. If the input is not a legal username or more then 2 arguments the trigger reponse should address those particularly and exit cleanly.

(node:32719) UnhandledPromiseRejectionWarning: Error: 404 Not Found
at _response.transport.finalizeRequest.call.then (/root/PackBot/node_modules/snekfetch/src/index.js:195:23)
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:32719) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:32719) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

using msg.reply() for triggers such as !beer renders the USERNAME at the begging of the bot's reply.

/possible fixes/
/exchange msg.reply() for msg.channel.send()/