command results (including /say) are not relayed from command blocks.
DimitriBarronmore opened this issue ยท 1 comments
Base informations
Minecraft version: 1.12.2
DiscordIntegration version: DiscordIntegration-mc1.12.2-3.0.5.jar
Server type and version: *Forge 1.12.2-14.23.5.2838
Link to pastebin with (censored) config: https://pastebin.com/RdKdX7jK
Issue
I'm using a command computer from CC:Tweaked to set up a script on a server I'm helping to run. We need to be able to send scheduled messages, which is why we installed DiscordIntegration in the first place, and have previously been using the /say
command through armor stands.
On starting the script, DiscordIntegrations proceeded to hang. Further testing shows that this is because when a command returns a result to chat, it fails to be sent to Discord if the executor is a command block. This includes commands such as /say
. The following error message appears in the console:
[JDA-Thread JDA/INFO] [STDERR]: [chikachi.discord.repack.net.dv8tion.jda.core.utils.SimpleLogger:write:277]: [JDA-Thread JDA] ERROR RestAction - RestAction queue returned failure: [ErrorResponseException] 400: null
This behavior appears to occur regardless of whether or not the gamerules commandBlockOutput
or logAdminCommands
are set to true or false.
Steps to reproduce
- Start a server with the mod installed and configured
- Place a command block, set it to execute
/say hello
- Activate the command block
I've got a gravestone system installed by way of command blocks that does a lot of constant monitoring, so roughly every couple of seconds, I see this error message in my logs. There appears to be a slight memory leak associated with it, as eventually, the server will OOM and crash.