In my previous setup (PoracleJS), I was able to separate the bot that handles user commands from the bots that send DM alert notifications. This was useful because:
- The command bot stays responsive to user interactions without being bottlenecked by outgoing DM traffic
- Alert delivery bots can focus purely on sending notifications without competing with command processing
- If a sending bot gets rate-limited by Discord, it doesn't affect the user's ability to interact with commands
I'd like to propose a dedicated configuration option for the command bot token, separate from the DM delivery token array. For example:
"commandToken": "BOT_TOKEN_FOR_COMMANDS",
"token": [
"BOT_TOKEN_FOR_DM_1",
"BOT_TOKEN_FOR_DM_2"
]
This way the command bot is entirely independent — it never participates in the DM sending rotation, and the delivery bots never need to handle command interactions. It also makes the intent clear in the config rather than relying on array position conventions.
Alternatively, a boolean flag like "firstTokenCommandOnly": true could achieve a similar result using the existing token array, though a separate setting feels cleaner.
In my previous setup (PoracleJS), I was able to separate the bot that handles user commands from the bots that send DM alert notifications. This was useful because:
I'd like to propose a dedicated configuration option for the command bot token, separate from the DM delivery token array. For example:
This way the command bot is entirely independent — it never participates in the DM sending rotation, and the delivery bots never need to handle command interactions. It also makes the intent clear in the config rather than relying on array position conventions.
Alternatively, a boolean flag like
"firstTokenCommandOnly": truecould achieve a similar result using the existing token array, though a separate setting feels cleaner.