Improve error handling for missing DISCORD_TOKEN

[TrivCodez]

Description

Enhance the error handling when the DISCORD_TOKEN environment variable is missing or invalid.

Current Behavior

The bot currently raises a generic RuntimeError with minimal guidance.

Desired Behavior

Provide clear, actionable error messages that guide users to:

1. Check if .env file exists
2. Verify token format
3. Provide setup instructions

Task

• Modify bot.py error handling section
• Add specific error messages for different failure cases
• Include helpful links or instructions

Why this is good for beginners

• Teaches proper error handling patterns
• Improves user experience
• Simple string/validation logic
• No external dependencies

Files to modify

• bot.py (lines 11-13)

Example improved error message

if not TOKEN:
    raise RuntimeError(
        "DISCORD_TOKEN not found!\n"
        "1. Copy .env.example to .env\n"
        "2. Replace YOUR_BOT_TOKEN_HERE with your bot token\n"
        "3. Get a token from https://discord.com/developers/applications"
    )

Acceptance Criteria

• Clear error message for missing token
• Validation for token format (basic check)
• Actionable steps provided
• Error occurs before bot initialization
• Code includes comments explaining the validation

[TrivCodez]

Hello @Ghraven!

I noticed your PR #12 also addresses this issue—thank you for improving the DISCORD_TOKEN error message!

Since you've already completed the work as part of PR #12, I'm assigning this issue to you retroactively. Your enhanced error message with clear, actionable steps is a great improvement.

For future contributions: Please comment "I would like to work on this" on issues before starting work. This helps us:

• Coordinate assignments and avoid duplicate effort
• Ensure the issue is still available
• Provide guidance before you begin
• Track who's working on what

We appreciate your work on this and look forward to more contributions! Please also make sure to ⭐ star the repository (required for PR merge).

Thank you! 🎉

[Ghraven]

Thanks for recognising the work, @TrivCodez, and for linking it to PR #12! Will keep the one-issue-per-PR pattern in mind for future contributions. 🙏