I highly recommend migrating to the new version, as it’s mucher safer and fixed some commands bug along with permissions.
Moved all important credentials to a .env file. It’s much more secure than using a .json file to store them. Yes, the tutorial has been updated to help you work with the new files.
You can now add your own reason when you are using the ban & kick commands! Don’t want to add a reason? Perfectly fine it will default to the reason that is in your config.json.
Fixed a few errors & handling
What to expect in the future?
Slash command support
New Commands
Global Announcement & Server Specific Announcements
Softshudown
Warn
As always if you have any questions or recommendations, please make sure to comment them or message me directly.
I’ll make sure to create one, in the upcoming update! In the meantime, if you would still like help setting it up make sure to directly message me on here or add me on discord. frames#4888
I have a suggestion for this, a command that lets you execute code to the game, example: :execute <code>
It would be a great addition to trigger some custom stuff inside your game without needing to play.
Here is a quick preview of V2! I’m not really sure when It will be dropping but I am actively working on it when I am able to. If you didn’t notice, it’s coming with multi-universe support & new commands, so stay tuned!
Update
I’ve successfully replaced text-based commands with slash-commands.
First I’d like to apologize for the delay in the update, I’ve been really busy with school. Secondly, I didn’t feel comfortable releasing the update, therefore it’s a beta. I’d like some of you to test it and tell me if there are any bugs before I make the official 2.0.0 release.
IF YOU ARE GOING TO TRY THIS OUT, MAKE SURE TO GRAB THE NEW ROBLOX MODEL
What is new?
Completly got rid of text-based commands and replaced them with slash commands.
{
"CLIENT": {
"APPLICATION_ID": "463264827643272",
"GUILD_ID": "59862386532823756248735"
},
"GAME": {
"DATASTORE_NAME": "RBLXManagerBans",
"UNIVERSE_IDS": {
"4045014903": "RBLX Manager",
"4061541317": "Place 2"
},
"BAN_REASON": "Hello, you have been banned permentaly. If you think this was a mistake please contact a moderator to apeal.",
"UNBAN_REASON": "The user has been unbanned",
"KICK_REASON": "Hello, you have been kicked from the server."
}
}
As always if you have any questions or recommendations, please make sure to comment them or message me directly.
Unfortunately, had to discontinue this project since I thought that dependence on users going through a hefty setup can quickly become problematic.
Maybe this is something that you can expand on? You could even host the general bot to streamline this process? I’ve done a bit of brainstorming and hopefully this will point you in the right direction:
You will likely need to store more than one API keys (e.g datastores API keys - allowing access for separate guild panels; experience API keys)
However, saving security information on your end is likely to discourage users from utilizing your bot. From what I’ve read, there’s nothing you can do about that. But, maybe you could cache these values on your parent server instead? Storing data with Keyv | discord.js Guide
There is no harm in prompting users to reinsert their API keys, in-case the cached values are lost (due to a server outage?): Modals | discord.js Guide
Including a simple setup video would have probably helped them out, I created one last night but I have to upload it properly.
I’ve actually been thinking about this, however, I’m just not sure if users will feel safe enough to provide their Keys because from their POV I’m just another user on the devforum.
This tool had been a joy to use! Handles moderation exceptionally well and is a lightweight tool.
Would love to see role-specific permissions in the next update so different Discord roles have different command permissions (Moderators can only Kick, Ban, Unban, etc. - Administrators can use announcements and lock servers, etc.)
| 10/26/2022
