Multipurpose-discord-bot
A multipurpose bot, a clan bot, a all in one bot. The one bot u need for ur server originally made as Milrato discord Bot and by Tomato6966.
Source code + guide will be soon online
Category: JavaScript / Miscellaneous |
Watchers: 3 |
Star: 3 |
Fork: 0 |
Last update: Mar 5, 2022 |
A multipurpose bot, a clan bot, a all in one bot. The one bot u need for ur server originally made as Milrato discord Bot and by Tomato6966.
Source code + guide will be soon online
welcome and leave work only in first server you set doesn't work on multi discord server And (LeaveDm doesn't work)
Cannot read properties of undefined (reading 'get') can anyone help me?
At least give credits to gamecord lmao and dont say you didnt steal it because in the 2048 command there is the api of the gamecord's owner lol
If you would like to use owner commands like detailedeval,eval,deployslash
, instead of going to the commands and changing Tomato's ID, it will use the first owner ID in the array in config.json, to decide whether the user is allowed to run the command or not
it was a simple change but bcoz i saw someone made an issue on it i thought it would have been useful to add this
Also fixed setup-boostlog (hopefully, coz i cant test it)
and i did more stuff but i am not bothered to explain, just read the commit messages lol
stop, and think, why do you put EMOJIS IN YOUR FOLDER NAMES WHAT ARE YOUUUUUUUUUUUUUUUUUUUUUUU
Deployslash command is not working not diploying the slash command to guilds fix it
V16.16.0
11.0.0
- OS: Windows
- 10
There is a bug with the setup-admin command, when I select "Per Command Roles" or others I have an error in my console
Steps to reproduce the behavior e.g:
Be able to select the role with the command he has access to
X
v18.16.0
the latest
- windows
- 10
Loadbackup command doesn't work?
Steps to reproduce the behavior e.g:
A clear and concise description of what you expected to happen.
Add any other context about the problem here.
v18.16.0
10.3.0
=== UNHANDLED REJECTION === Reason: DiscordAPIError: Invalid Form Body components[0].components[0].options[0].emoji.id: Invalid emoji components[0].components[0].options[1].emoji.id: Invalid emoji components[0].components[0].options[2].emoji.id: Invalid emoji components[0].components[0].options[3].emoji.id: Invalid emoji components[0].components[0].options[4].emoji.id: Invalid emoji components[0].components[0].options[5].emoji.id: Invalid emoji components[0].components[0].options[6].emoji.id: Invalid emoji components[0].components[0].options[7].emoji.id: Invalid emoji components[0].components[0].options[8].emoji.id: Invalid emoji components[0].components[0].options[9].emoji.id: Invalid emoji components[0].components[0].options[10].emoji.id: Invalid emoji components[0].components[0].options[11].emoji.id: Invalid emoji components[0].components[0].options[12].emoji.id: Invalid emoji components[0].components[0].options[13].emoji.id: Invalid emoji components[0].components[0].options[14].emoji.id: Invalid emoji components[0].components[0].options[15].emoji.id: Invalid emoji components[0].components[0].options[16].emoji.id: Invalid emoji components[0].components[0].options[17].emoji.id: Invalid emoji components[0].components[0].options[18].emoji.id: Invalid emoji components[0].components[0].options[19].emoji.id: Invalid emoji components[0].components[0].options[20].emoji.id: Invalid emoji components[0].components[0].options[21].emoji.id: Invalid emoji components[0].components[0].options[22].emoji.id: Invalid emoji components[0].components[0].options[23].emoji.id: Invalid emoji components[0].components[0].options[24].emoji.id: Invalid emoji at RequestHandler.execute (C:\Users\Administrator\Desktop\discord_bot\node_modules\discord.js\src\rest\RequestHandler.js:350:13) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async RequestHandler.push (C:\Users\Administrator\Desktop\discord_bot\node_modules\discord.js\src\rest\RequestHandler.js:51:14) at async TextChannel.send (C:\Users\Administrator\Desktop\discord_bot\node_modules\discord.js\src\structures\interfaces\TextBasedChannel.js:158:15) at async first_layer (C:\Users\Administrator\Desktop\discord_bot\commands\💪 Setup\setup-membercount.js:67:23) === UNHANDLED REJECTION ===.
https://cdn.discordapp.com/attachments/1065370654599286916/1108094815310200843/bot.PNG
Show the output of:
node -v
--Node version: v18.12.1
From the releases e.g.: 10.2.0 --Release: Latest
- OS: [e.g. iOS]
- Version [e.g. 22] --OS: Microsoft Windows 10 --Version: Latest
A clear and concise description of what the bug is. --Description: The application system, after reworking the deprecated functions, i noticed it doesnt log the User answares anywhere wich makes the entire system pointless, it also doesnt have any way of setting up a log channel appart of the one that logs the users that finished the applications setted up
Steps to reproduce the behavior e.g:
A clear and concise description of what you expected to happen.
Add any other context about the problem here.
I like it lamamaamama
Some minor changes which may be relevant for u!
Created a new Branch sharded_with_mongo
... there will soon be a shardable version of this bot which uses the MONGODB database instead of ENMAP using quickmongo
for better support and a status dashboard and cluster system etc.
Fixxed a few bugs in mute command, updated serverinfo github translate and developer and changed some functions in /handlers/functions.js
Now changed from 25 Limitations to: 100 Limitations for:
Changed the starting console logs, so that it looks more "fluent"
Changed some sync-blocking tasks to async-nonblocking to improve speed.
Improved speed of almost every system which got listed above^^
A few fixes for the improved version of the apply, menuapply, ticket and menuticket system!
V13 + Many new Features and security stuff!