Skip to content
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

Bugfix/4.0.1 #62

Merged
merged 11 commits into from
Jan 22, 2022
Merged

Bugfix/4.0.1 #62

merged 11 commits into from
Jan 22, 2022

Conversation

moonstar-x
Copy link
Owner

@moonstar-x moonstar-x commented Jan 22, 2022

📝 Checklist

Make sure that your PR fulfills these requirements:

  • Code has been linted with the proper rules.

📄 Description

This PR corresponds to the version 4.0.1 of this bot, this includes the following changes:

  • Fixed a bug in the command deployment script where it would throw an error related to config types.
  • Fixed a bug where any command would throw in a newly joined server because no localizer was initialized for it.
  • Fixed a bug where the bot would crash if it left a server due to trying to clear data from the redis data provider when no data was saved prior.
  • Fixed wrong prefix in help presence message. Added a current version presence message.
  • Fixed a bug where the bot would crash if it left a server before the data provider was ready.
  • Fixed a bug where the bot would crash if someone tried to send a prefixed command in a channel where the bot has no permissions to reply.
  • Fixed a bug where no TTSPlayer would be instantiated for newly joined servers.
  • Fixed a bug where TTSPlayer instances would not be removed when leaving servers.
  • Fixed a bug where the interaction would show up as failed if any of the TTS providers would take longer than 3 seconds to resolve the TTS resource.
  • Fixed a bug where the set_timeout command would not accept valid timeout values.
  • Added a init-replit.sh script to facilitate the setup of the node environment for Repl.it users. Check the README for more information on how to use it.

📌 Does this PR address any issue?

#61

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant