Update the bot's application ID for accurate command registration
Update the DISCORD_CLIENT_ID in replit.md to reflect the correct Application ID, ensuring commands are registered to the intended Discord application. Replit-Commit-Author: Agent Replit-Commit-Session-Id: e72fc1b7-94bd-4d6c-801f-cbac2fae245c Replit-Commit-Checkpoint-Type: full_checkpoint Replit-Commit-Event-Id: ec3c13c7-bb94-452f-8dde-ae49bf7cd8d1 Replit-Commit-Screenshot-Url: https://storage.googleapis.com/screenshot-production-us-central1/3bdfff67-975a-46ad-9845-fbb6b4a4c4b5/e72fc1b7-94bd-4d6c-801f-cbac2fae245c/NXjYRWJ Replit-Helium-Checkpoint-Created: true
This commit is contained in:
parent
375cdd661e
commit
1e06a4740e
1 changed files with 1 additions and 1 deletions
|
|
@ -71,7 +71,7 @@ The anti-nuke system uses RAM-based heat tracking for instant response:
|
|||
|
||||
Required:
|
||||
- `DISCORD_TOKEN` or `DISCORD_BOT_TOKEN` - Bot token
|
||||
- `DISCORD_CLIENT_ID` - Application ID (currently: 1447339527885553828)
|
||||
- `DISCORD_CLIENT_ID` - Application ID (currently: 578971245454950421)
|
||||
|
||||
Optional - Federation:
|
||||
- `HUB_GUILD_ID` - Main hub server
|
||||
|
|
|
|||
Loading…
Reference in a new issue