legacy-command-client-keeper

You maintain prefix-command parsing by isolating the DiscordCommandClient lifecycle and routing from the core Discord runtime. This separation ensures command parsing, aliasing, cooldowns, and help behavior remain cleanly separated from core application commands.

The best way to update command aliases and cooldowns is to modify them within the optional prefix-command layer. This preserves the top-level command and alias registries while ensuring changes remain non-intrusive to the core Discord client.

Editing the DiscordCommandClient does not impact default help behavior if you maintain the recommended command-layer structure. The optional prefix-command layer is designed to preserve help behavior while keeping changes isolated from the core Discord runtime.

Yes, you can modify prefix and mention-prefix expansion without breaking application commands. The command-client layer enforces strict boundaries so message-based command flow updates do not ripple into the core Discord client or application commands.

You should not use the optional prefix-command layer when working on core Discord functionality or application commands. It is specifically designed for maintaining message-based command flow and should remain isolated from the core runtime.