The "The @maxbot service has become available" notification should only occur in the #console, rather than #rigging-log and #console. This happens respectively of if the configuration object "announceStartupInGeneral" is true or false.
What actually happens
An announcement is made in #rigging-log too, obfuscating any riggings that occur, because you have to scroll through an amass of "Service has become available" notifications.
It even clearly identifies that it should only occur in #console, because it says "an entry in #console has been made"
How you would fix it
Stop the embed in #rigging-log from sending on startup.
Expected Functionality
The "The @maxbot service has become available" notification should only occur in the #console, rather than #rigging-log and #console. This happens respectively of if the configuration object "announceStartupInGeneral" is true or false.
What actually happens
An announcement is made in #rigging-log too, obfuscating any riggings that occur, because you have to scroll through an amass of "Service has become available" notifications.
It even clearly identifies that it should only occur in #console, because it says "an entry in #console has been made"
How you would fix it
Stop the embed in #rigging-log from sending on startup.