
Truncation notice is given in `Channels` option channels when in-game channel doesn't exist
J-295 opened this issue ยท 2 comments
Expected behavior
The bot doesn't do the truncation notice (reacting ๐ฌโ) if the channel name configured doesn't exist in-game.
Actual behavior
The bot does the truncation notice even if the in-game channel name configured doesn't exist.
Steps to reproduce
- Configure a channel in the
Channels
option with an in-game channel name that doesn't exist. - Run
/discordsrv reload
- Send a message in the newly configured channel containing more characters than
DiscordChatChannelTruncateLength
.
Server software and version
No response
Checks
- I am not using an outdated version of DiscordSRV.
- I asked in DiscordSRV's Discord server to see whether this issue is in fact a bug that needs to be fixed.
- I didn't actually check any of these things
Anything else
An example of where the current behaviour is an issue is when the configured channel is only for using in alerts.yml
Sometimes a channel will be used just for in-game command to Discord messages (using the broadcast command). The bot will still react to messages sent that are over the character limit. It would be nice if there was a way to disable this reaction entirely, or if it could be recognized the channel in Minecraft doesn't exist.
Sometimes a channel will be used just for in-game command to Discord messages (using the broadcast command). The bot will still react to messages sent that are over the character limit. It would be nice if there was a way to disable this reaction entirely, or if it could be recognized the channel in Minecraft doesn't exist.
@ChiboYen You can set the DiscordChatChannelTruncateLength
to a higher value so that it won't trigger on those messages