-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleanup + improvements #1
base: development
Are you sure you want to change the base?
Cleanup + improvements #1
Conversation
Thanks for this! I'll try and block some time over the weekend to properly review 😀 |
If needed, I can take some of those commits and try them on my own modification of Logger, as it's always online and I have a few people that can try it for me |
Fyi I've made a couple of code changes today (which can be seen here), which includes the I may add more features from this PR at some point, but for now I've run out of time. |
Mind pushing those changes to my fork so I can test and merge them ? I already merged most of those changes on my stable build (just need to work on v2 now) |
@AzhamProdLive You can do this yourself by adding my repo as an extra remote to yours:
|
Make sure to test this fully.
@TizzySaurus enjoy
messages.txt
file will be sent along with the haste link forarchive
and messageBulkDelete event.createHaste
function so it's easier to manage..env.example
file to separate which fields is required/optionalnpm run genDB
) so it's easier.MESSAGE_ARCHIVE_SIZE
.env field to set the amount of messages allowed for archive commands. (by default: 1000)${user.discriminator === "0" ? ...}
todisplayUser
function to make things easier. (and not dupe the code over and over again)rethink.js
file (left over from Logger v2 code ig?)IF NOT EXISTS
to the generateDB script for messages/guilds