[BUG] DiscordIntegration-1.2.1 (MC 1.15) Custom commands not showing output in discord.
tobi-polar opened this issue · 5 comments
What happened?
- Ran a custom command in discord (/entitycount runs the "/forge entity list" command in game), command executes successfully the first time after a reboot. All subsequent times after that for this command or any other custom commands run successfully in game but don't show an output in discord.
What should happen?
- Commands should run in game, and display the output in discord.
Steps to reproduce
- Make a custom command, can be anything like "/ping playername". Command will run successfully the first time after a fresh server restart, all subsequent times after that the command wont show in discord.
Version
- 1.15.2
Mod version 1.2.1
Config file
-https://pastebin.com/u1QjKEPF
Additional info
Default commands like /list seem to work but not custom commands. It's also worth noting this issue has been around in the last few versions for 1.15.
Screenshot of problem
I second this not occurring. Weirdly enough, if I do a raw exec command (directly execute into console), when I use the tp command, it'll show the output for that (meaning it picks up on messages sent to the "operator"). However, information from the console is not returned
I believe this to be the relevant error, as a fresh Server will print the console out the first time, however any attempts afterwards results in no response from the mod
Exception in thread "Thread-8" [16:15:15] [Thread-8/INFO] [STDERR]: [java.lang.ThreadGroup:uncaughtException:1052]: java.util.ConcurrentModificationException
[16:15:15] [Thread-8/INFO] [STDERR]: [java.lang.ThreadGroup:uncaughtException:1052]: at java.util.HashMap.forEach(HashMap.java:1292)
[16:15:15] [Thread-8/INFO] [STDERR]: [java.lang.ThreadGroup:uncaughtException:1052]: at de.erdbeerbaerlp.dcintegration.Discord.lambda$new$1(Discord.java:224)
[16:15:15] [Thread-8/INFO] [STDERR]: [java.lang.ThreadGroup:uncaughtException:1052]: at java.lang.Thread.run(Thread.java:748)
Ah I see why
Looks like I accidentally moved an code line. Going to fix that