Releases: LakeYS/Dishorde
Releases · LakeYS/Dishorde
v2.2.1 - Bot Message Fix
v2.2.0 - Bugfixes and 7d!time update
- Reworked the horde night message for the 7d!time command. Horde night messages now look like: "Day 5, 04:00 | The blood moon horde begins on Day 7 (in 2 days)."
- On the day of the horde, 7d!time now counts down the hours to the horde. For example: "Day 7, 11:00 | The blood moon horde begins in 11 hours."
- Fixed error when a Webhook is sent in the bot's channel.
- The config.json file is now shipped as config.example.json. During installation, you must rename this file to config.json before you can start the bot.
A new Discord server has been created for discussion and support of Dishorde. Join us! https://discord.gg/ZMpSE2a3rs
v2.0.1 - Hotfix
- Fixed the setchannel and exec commands being broken.
- Warning messages for "duplicate line" errors are now only displayed when they correlate to a chat message. This should reduce spam in the bot's console and logs.
- Updated discord.js to 13.6.0.
Note: Make sure to re-run npm install
or install.bat when updating from a previous version.
v2.0.0 - Major Bugfixes
- 7DTD-Discord is now known as Dishorde. The new name is now used in the bot's files.
- Discord pings are now filtered out from messages. This means that in-game users can no-longer ping @ everyone, @ here, or other users (via
<@(userid)>
). Attempts to do so now show up with special formatting. - For safety, links posted in messages from the game are no-longer clickable. Added a new config option, allow-links-from-game, that must be enabled to allow links.
- The console will now detect if a log is being spammed and mark it accordingly.
- Added a new config option,
log-console
. This will log the output of the bot's console to a file, console.log. - Updated the bot to discord.js v13.
- Fixed "Server connection: undefined" when disable-status-updates is set to true.
- Fixed token and login errors not displaying their correct error text.
- Fixed console errors related to the GitHub repository URL.
- Attempted fix for console data spilling through to messages.
- Attempted fix for messages failing to show up in chat for long amounts of time.
- Remedied instances where a single message would be spammed in chat. The console will now throw a warning when this occurs and block the spam. A fix for the root cause of this issue is still pending.
- Added an unwritten config option, debug-mode. This option will enable additional logging for investigating issues with receiving messages from the game.
- Added a workaround for messages from Discord with quotes being cut off. (Quotes are removed from the messages)
v1.7.3 - Hotfix, discord.js Update
- Updated discord.js to 12.5.3.
- The console now displays more specific information about certain errors.
- The bot's status now reads "No channel" (same as if none were initially specified) if an invalid channel is entered in config.
v1.7.2 - Alpha 18 Support and Message Cutoff Fix
NOTE: This update is designed for use with Alpha 18 only. Alpha 17 is mostly compatible, however any earlier versions will likely not work correctly.
- Fixed the notorious message cutoff bug. This should fix both messages being cut off and messages simply not displaying at all.
- Updated discord.js to 11.6.2
- Connection errors now dump JSON data if they do not have a message attached
- Fixed the server "online" status emoji showing up as
:large_blue_circle:
in chat.
v1.7.1 - Party System Fix
- Added the config option "show-private-chat". This option toggles whether or not party/friend chats show up in the Discord channel.
- Fixed party system messages showing up in the chat.
- Fixed run_silent.sh using the name "dicord7dtd" instead of "discord7dtd"
- Fixed the bot occasionally cutting messages that contain parentheses.
v1.7 - Alpha 17 Compatibility
NOTE: This version is designed for use with Alpha 17 servers. You may encounter problems if using it with Alpha 16 or earlier.
- The bot now supports Alpha 17.
- Invalid token errors (4004) are now more user-friendly and display more helpful information.
- The terminal now displays an error if there is more than one instance of the bot running. This is to prevent server administrators from accidentally having the bot open more than once.
- Added
run_silent.sh
for Linux users. This is an easy way to run the bot in the background, similar to therun_silent.vbs
file in Windows releases. - Updated discord.js to 11.4.2
- Connection errors have been shortened so they no-longer flood the console.
- The application now starts when "npm start" is called.
- Fixed prefix still defaulting to "7dtd!" if none is specified in config.
- Fixed run_silent.sh reading "dicord7dtd" instead of "discord7dtd"
v1.6
- Overhauled the 7dtd!info command.
- Added config option:
prefix
. This allows administrators to change the bot's command prefix. - The default prefix has been changed from "7dtd!" to "7d!". This can be reverted in the config.
- Added config option:
disable-status-updates
. Setting this to 'true' disables the bot's status display in Discord. It also prevents the icon from changing to red when the server is down. - Added config option:
disable-join-leave-gmsgs
. This disables player join/leave messages. - Added config option:
disable-misc-gmsgs
. This disables other global messages such as player deaths. - The bot now displays help information when it is @mentioned.
- The bot no-longer @mentions users in response to commands. (In compliance and with the Discord bot best practices; this prevents the bot from cluttering the user's "recent mentions" menu)
- A status message now displays when there is no channel specified.
- [1e89d94] Fixed crash when bot fails to send a message to the game
- [ed0c55b] Fixed 7dtd!time command reading "1 days to next horde."
- [3b75c26] Fixed the bot's status not changing from "Error" to "Online" when the server comes online.
- [02ef35c] Fixed the bot's status reading "No connection" after a Discord client error occurs, even if the game server is online.
- [bbe92a9] Fixed the bot's status changing to blank on rare occasions.
- [75cfa90] Fixed the bot responding to other bots.
v1.5.2 - Hotfix for run.sh
- Typing '7dtd!setchannel' without specifying a channel will now use the channel that the command was typed in.
- Fixed formatting of run.sh.