/token - RynZen Token Management

The /token command manages your encrypted RynZen token for advanced features like auto-r4id.

Command Usage

/token show
/token set
/token delete

Subcommands

/token show

View your current saved RynZen token.

Options: None

Response:

# your rynzen token

[Your encrypted token displayed]

/token set

Set or update your RynZen token.

Options: None (uses interactive panel)

Process:

1. Click "set token" button
2. Enter token in modal
3. Token validated
4. Saved if valid

/token delete

Delete your saved RynZen token.

Options: None (uses confirmation panel)

Process:

1. Click confirmation button
2. Token permanently deleted
3. Auto-r4id no longer available

Getting a Token

Chrome Extension

Extension Details:

• Name: RynZen Token Extension
• Status: Pending Chrome Web Store publication

Steps to Get Token

1. Install Extension

   • Wait for Chrome Web Store approval
   • Or load unpacked extension

2. Log into Discord

   • Use the token log feature
   • Extension captures encrypted token

3. Copy Token

   • Click copy button in extension
   • Token is encrypted

4. Save with Bot

   • Use /token set
   • Paste encrypted token
   • Validate and save

Step-by-Step Guide

Setting a Token

1. Start Command

/token set

2. Read Warning

# set rynzen token
## dont leak your rynzen token!!

3. Click Set Token

• Modal appears
• Enter encrypted token

4. Validation

decrypting and checking if your token is valid...

5. Success or Error

✅ token validated and saved successfully
❌ that token is bricked or invalid

Viewing Your Token

/token show
→ Displays saved token

Deleting Your Token

1. Start Command

/token delete

2. Confirm Deletion

→ Click confirmation button
→ Token deleted

Token Uses

Auto-R4id

Primary use case for tokens:

• Automated raiding
• Multi-token support
• Advanced functionality

Security Notes

Best Practices

1. Never Share

   • Don't give token to others
   • Don't post publicly
   • Keep encrypted

2. Secure Storage

   • Bot stores encrypted
   • Only you can access
   • Server-side protection

3. Rotation

   • Change if compromised
   • Delete when not needed

What Happens If Leaked

• Others can use auto-r4id as you
• Your account at risk
• Potential issues

Troubleshooting

"invalid token format"

• Token corrupted
• Incomplete copy
• Re-copy from extension

"decryption failed"

• Token modified
• Get fresh token

"that token is bricked or invalid"

• Token expired/revoked
• Re-authenticate in extension

"you dont have a token set yet gng"

• Never set token
• Token was deleted
• Use /token set first

Limitations

One Token Per User

• Each user has one token slot
• Setting new token overwrites old

Validation Required

• Must be valid
• Checked against API
• Invalid tokens rejected

Related Commands

• /auto-r4id - Automated raiding (requires token)