Setting the configuration value I:"Minimum Delay (ms) for 'Can't Keep Up!' Log Warning" in DragonAPI above 0 causes all chat logging to the server console (this includes command output) to be blocked. Essentially it seems to be locking down anything that would normally appear in latest.log, but has no effect on the fml-server-latest.log. This is a server-only issue, as clients (in singleplayer) with the feature still receive chat, and still can see command output. Clients connected to a server with this feature enabled also still receive chat and command output. I'll try to send as much info your way as possible, and this reproduces with only DragonAPI in the instance.
These are log files from starting up a server with the config set to respective values, and then executing commands say 3 and say 4
Setting the configuration value I:"Minimum Delay (ms) for 'Can't Keep Up!' Log Warning" in DragonAPI above 0 causes all chat logging to the server console (this includes command output) to be blocked. Essentially it seems to be locking down anything that would normally appear in latest.log, but has no effect on the fml-server-latest.log. This is a server-only issue, as clients (in singleplayer) with the feature still receive chat, and still can see command output. Clients connected to a server with this feature enabled also still receive chat and command output. I'll try to send as much info your way as possible, and this reproduces with only DragonAPI in the instance.
These are log files from starting up a server with the config set to respective values, and then executing commands
say 3
andsay 4
Info for cfg = 1 fml-server-latest.log
latest.log Info for cfg = 0 fml-server-latest.log latest.log