We have alveussanctuary in the default set of channel names, so when the extension is active in this channel it should not be watching the extra channel names including alveusgg. However, as seen in recent collaborations, commands run in alveusgg where controlling the extension in alveussanctuary.
After some investigation, the issue stems from the broadcaster_name for alveussanctuary actually being AlveusSanctuary. I've solved this in a few different places for some redundancy -- switching to broadcaster_login gives us back alveussanctuary instead, and then I've ensured we're normalizing all the values used for these name checks to always be lowercase.
We have
alveussanctuaryin the default set of channel names, so when the extension is active in this channel it should not be watching the extra channel names includingalveusgg. However, as seen in recent collaborations, commands run inalveusggwhere controlling the extension inalveussanctuary.After some investigation, the issue stems from the
broadcaster_nameforalveussanctuaryactually beingAlveusSanctuary. I've solved this in a few different places for some redundancy -- switching tobroadcaster_logingives us backalveussanctuaryinstead, and then I've ensured we're normalizing all the values used for these name checks to always be lowercase.