You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey! Been a while since I've updated EasyCommands, and I'm back to working on it!
In this updated I added multiple new features and implemented more JavaDoc to help you all understand the code better.
I've also added more error handlings to easily debug what some problems might be.
The update will be available around 8h30-9h PM tonight. (US/CA Eastern Time). This is to let me time fix the latest issues and cleaning up the code a bit more.
New Features
New config 2.0 -> This config file is now located in your bot root folder. ./Saved/Config/config.properties
This new config gets updated automatically with each update of the bot. From now on, when I'll remove or add a new config option it will get updated to your config automatically to keep you up to date! Be careful, do not write anything else than a valid config setting or else it will get removed.
Guild Properties -> Those files are located inside your root folder. ./Saved
This means that finally, your bot can work on multiple different servers. The auto role system has been remastered. It will now grab the role from the correct guild properties and apply it automatically to new members/bots. To configure these roles you can use the commands: /setmemberrole or /setbotrole .
If you don't set any roles, the event will get ignored.
You can now also setup a specific log channel for each one of your different servers with the command /setlogchannel. This command will set the log channel to the current channel for the current guild.
You can also setup a specific music channel for each different guilds now using the command /setmusicchannel.
Important note: The guild properties system only works on non-mysql bots. When using MySQL, the values for your different auto roles and channels for your guilds will get added to MySQL instead of locally inside the ./Saved folder.
MySQL is still under implementation, it's not entirely working just yet since I'm focusing on making the bot work locally and cleaning it's code base.
From now on, when creating a new executor, if you want to add specific authorized roles or channels, you must use the functions updateAuthorizedRoles(JDA jda) or updateAuthorizedChannels(JDA jda) instead of using the Getters. I found out yesterday that this wasn't efficient since the longer your bot was started, more bytes/garbage these arrays would collect depending on the implementation.
I will post new videos on YouTube explaining in depth the new features and changes. I will also make a video on how to correctly port your bot from version 0.7 to 0.8.
I'll also post a video about creating a Discord bot with the new version.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
EasyCommands v0.8.0
Hey! Been a while since I've updated EasyCommands, and I'm back to working on it!
In this updated I added multiple new features and implemented more JavaDoc to help you all understand the code better.
I've also added more error handlings to easily debug what some problems might be.
The update will be available around 8h30-9h PM tonight. (US/CA Eastern Time). This is to let me time fix the latest issues and cleaning up the code a bit more.
New Features
New config 2.0 -> This config file is now located in your bot root folder. ./Saved/Config/config.properties
This new config gets updated automatically with each update of the bot. From now on, when I'll remove or add a new config option it will get updated to your config automatically to keep you up to date! Be careful, do not write anything else than a valid config setting or else it will get removed.
Guild Properties -> Those files are located inside your root folder. ./Saved
This means that finally, your bot can work on multiple different servers. The auto role system has been remastered. It will now grab the role from the correct guild properties and apply it automatically to new members/bots. To configure these roles you can use the commands: /setmemberrole or /setbotrole .
If you don't set any roles, the event will get ignored.
You can now also setup a specific log channel for each one of your different servers with the command /setlogchannel. This command will set the log channel to the current channel for the current guild.
You can also setup a specific music channel for each different guilds now using the command /setmusicchannel.
Important note: The guild properties system only works on non-mysql bots. When using MySQL, the values for your different auto roles and channels for your guilds will get added to MySQL instead of locally inside the ./Saved folder.
MySQL is still under implementation, it's not entirely working just yet since I'm focusing on making the bot work locally and cleaning it's code base.
From now on, when creating a new executor, if you want to add specific authorized roles or channels, you must use the functions updateAuthorizedRoles(JDA jda) or updateAuthorizedChannels(JDA jda) instead of using the Getters. I found out yesterday that this wasn't efficient since the longer your bot was started, more bytes/garbage these arrays would collect depending on the implementation.
I will post new videos on YouTube explaining in depth the new features and changes. I will also make a video on how to correctly port your bot from version 0.7 to 0.8.
I'll also post a video about creating a Discord bot with the new version.
JDA has been updated to latest version.
This discussion was created from the release EasyCommands v0.8.0.
Beta Was this translation helpful? Give feedback.
All reactions