-
Jelte Jansen authored
While creating messages and extended descriptions, I noticed a few potential problems, which I also fixed; - If the config manager does not accept the modules specification, or if the 'get current config' command returns with an error, the system used to ignore that fact apart from printing an error, and continue running. It seems much better to explicitely fail, since the module would be running independent of what its config is supposed to be, which would be really unstable - If the module cannot parse a command it gets over the command channel, it used to send back an error. If we have multiple modules listening on the same channel, this would result in multiple errors being returned It will now log an error, but it will not send back an answer
c47f23e5