Skip to content

fix: the bot now only registers "new" commands on startup #179

fix: the bot now only registers "new" commands on startup

fix: the bot now only registers "new" commands on startup #179