Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Feature Request [autoPlay, addNext]

See original GitHub issue

Issue Description

It’ll be great if you add this feature

Music Related

Autoplay: when enabled, the bot wil continue playing after there is no more songs in the queue.

playNext / addNext : Add the next song right after the current playing song in the queue, so we can play it next playSkip : combination of playNext and skip, skip the current song and play the requested song instantly without affecting the existing queue.

Comannd Handler

add cooldown, guildOnly, ownerOnly, botPermissions, userPermissions to comamnd handler. I know all functions are available. But we have to write every function and their error message for every commands. Isn’t aoijs to simplify and make easy discord bot developing, so make it easy. Bot owner id can be array , and can be added while making new aoi.Bot

If guildOnlyfunction will added to Comamnd handler, we can decide for every comamnd to be used on dm or not. ownerOnly: A new event should be added which will be emitted when a non owner user try to use the command.

To add cooldown to command handler, a new event should be made, it’ll be emitted when there is still a cooldown

botPermissions: it should be array . And a new event should be added, it’ll emit when the bot don’t have permission for that comand

userPermissions: it should be array . And a new event should be added, it’ll emit when the user don’t have permission to use that comand

Issue Analytics

State:
Created 2 years ago
Comments:12 (8 by maintainers)

Top GitHub Comments

2reactions

USERSATOSHIcommented, Nov 14, 2021

regarding this

i have some news on command handler

rn we have added 2 new features

dmOnly : true/false makes cmd only work in dm tho plans are to change it to sendOnlyAt : 'dm' | 'guild' | 'both' default will be both

tho u still have to add guildOnly : false in bot.onMessage()

furthermore, whitelist: true/false (default = false ) has been added to cmds to support new Blacklist system

cmds with whitelist : true will make these cmds usable for the users who are blacklisted

no idea about ownerOnly and music ones

also a question on cooldown do u want this to be temp cooldown aka it resets on restart ( doesnt use db , good for small cooldowns) or permanent cooldown aka which doesnt restart (uses db, good for long cooldowns, bad for short ones)

2reactions

USERSATOSHIcommented, Jun 22, 2021

I liked the guildOnly stuff in cmd handler for letting the bot to respond to dms for only some cmds. Also the music related cmds should be added. I will like to see this in the next update. Pls leref do it as it’s a cool feature

about that, I working in on it but because AOIJS src code needs a update so it will take quite a time