CODStatusBot

hey there bro, ive been using the bot for a few weeks now and just recently i started to receive The application did not respond errors on most commands im hitting... i cant even remove my banned accounts since ion get proper responses, is there anything i can do about that?

Quote:

Originally Posted by Txre Hey there, I've been using the bot for a few weeks now, and recently I've started receiving "The application did not respond" errors on most commands. I can't even remove my banned accounts because I’m not getting proper responses. Is there anything I can do about this?

Message me on Discord with more details, and I'll help you resolve the issue. If it turns out to be a problem with the bot, I'll work on a fix.

I recently made some updates to address issues with the CAPTCHA service and to keep it free for everyone as much as possible. However, with the large number of servers it's now part of, managing it is becoming a full-time process.

been user since day one good job with updates.

I'm well aware of the bot having issues after pushing the last update, and after working with some users recently, I have identified the possible causes. I'm currently working on a patch and will update here once it's resolved.

I also want to thank the 15 users who have signed up using the referral link. It helps keep the bot free for others, especially when someone who has signed up with the referral link buys more tokens, as it directly helps keep the bot free for everyone. I keep nothing; whatever percentage is gained, I put back towards the bot for everyone. I have already added some of my personal funds since the bot ran out of tokens a few days ago. So enjoy the bot for free, and thanks to those who contributed.

**CODStatusBot Project Update**

I wanted to give you an update on the status of CODStatusBot and the reason for the delay in addressing the latest bug. Recently, Activision introduced some changes with the release of the Black Ops 6 beta, which has provided more information that the bot can access. While working on the update to fix the bug, I decided to take this opportunity to implement these new data points into the bot.

Additionally, given the bot's growth and the resulting code debt, I've started a major rewrite of the project. I'm replacing the older `discordgo` library with the newer and more maintained `disgoorg` library. This change will make the bot's codebase simpler and more future-proof by simplifying event and interaction handling.

I'm working hard to complete this update and push out the new version as soon as possible. I appreciate your patience, especially since I'm the only person working on this project, and it's something I do in my spare time.

Thank you for your understanding and support!

Hey, may this sound stupid but where do I find the SSO cookie? :4head:

Edit: Already found on the GitHub page nevermind :D

CODStatusBot Project Update - November 2024

I'm back to share that CODStatusBot has evolved significantly and now serves 395+ Discord servers! This growth has pushed me to optimize and enhance every aspect of the bot. While my previous update mentioned potentially switching to disgoorg, I decided to continue with discordgo to focus on core functionality improvements.

Core Improvements:
- Completely rewrote the account checking system with Activision's latest API endpoints
- Implemented efficient error recovery and session management
- Enhanced database performance with optimized queries and connection pooling
- Added robust cookie validation and expiration tracking

Premium Features (Your Own API Key):
- Fully customizable check intervals
- Prioritized error notifications
- Custom notification preferences (channel/DM)
- Adjustable cooldown timers
- VIP status tracking
- Expanded account slots (up to 10 accounts)

Free Tier Features:
- Basic monitoring with standard intervals
- Up to 3 accounts per user
- Essential notifications
- Core status checks

New Commands & Features:
- `/setcheckinterval` - Customize your check frequency
- `/setnotifications` - Toggle between channel or DM notifications
- `/accountage` - Check account creation date and VIP status
- `/accountlogs` - View detailed status history
- `/checkcaptchabalance` - Monitor your token usage
- `/feedback` - Submit anonymous suggestions

EZ-Captcha Integration:
The bot now exclusively uses EZ-Captcha for reliable CAPTCHA solving. Users have two options:
1. Use the bot's default key (with rate limits)
2. Set up your own API key via `/setcaptchaservice` for unlimited usage

For those getting their own key, please use the referral link from `/helpapi`. A portion of all purchases through our referral link goes directly back into maintaining the free tier for everyone.

Need Help?
- Use `/help` for command documentation
- `/helpcookie` for SSO cookie guidance
- `/helpapi` for API key setup instructions
- Direct message me on Discord or EPVP for specific issues

The bot is currently serving over nearly 400 servers, I'm continuously working on improvements and new features. The source remains open on GitHub, and I encourage contributions from the community.

Thanks to everyone using the EZ-Captcha referral link - your support helps keep the basic service free for everyone. If you encounter any issues or have suggestions, feel free to use the `/feedback` command or open an issue on our GitHub repository.

can you make a video of exactly how this works i don't quite understand where to find sso-cookie.
just for the stupid among us

Quote:

Originally Posted by susplayer32 [b]snip

Hey boss, fantastic work on this. I originally coded the my bot in go to keep track of my and my friends accounts once we got SB for the first time, published it without much documentation or anything and just forgot about it. Glad you liked Go, it's an awesome language. Much, much love <3

# CODStatusBot Update - April 2025

I apologize for not keeping this thread updated.

The CODStatusBot has grown tremendously and now serves over 630 Discord server and has been installed as app for nearly 100 users as well.

Supports 2 captchas solvers a 3rd is is partly added for now.

The Command list continues to grow

- `/addaccount` - Add a new account to monitor
- `/removeaccount` - Remove an account from monitoring
- `/updateaccount` - Update an account's SSO cookie
- `/listaccounts` - View all your monitored accounts
- `/accountage` - Check account creation date and VIP status
- `/accountlogs` - View detailed status history
- `/checknow` - Perform an immediate status check
- `/setcheckinterval` - Customize your check frequency
- `/setnotifications` - Toggle between channel or DM notifications
- `/setcaptchaservice` - Configure your own API key
- `/checkcaptchabalance` - Monitor your token usage
- `/feedback` - Submit anonymous suggestions
- `/helpcookie` - Get help obtaining your SSO cookie
- `/helpapi` - Get help setting up your API key
- `/togglecheck` - Enable/disable checks for specific accounts
- `/verdansk` - Get your Verdansk Replay stats

Quote:

Originally Posted by probably a retard Hey boss, fantastic work on this. I originally coded the my bot in go to keep track of my and my friends accounts once we got SB for the first time, published it without much documentation or anything and just forgot about it. Glad you liked Go, it's an awesome language. Much, much love <3

Well it's good to see you return from your hibernation or where ever you went too. You literally dropped some go files off said here it is and disappeared. :awesome:

Important Update Activision SSO Cookie Changes and Bot Future

TL;DR - Bot will likely be archived soon

Due to recent Activision changes, the COD Status Bot will most likely be archived in the near future unless a viable solution is found. Activision has recently implemented significant changes to their SSO (Single Sign-On) cookie system that severely impacts third party applications like this bot.

Previously, the system had the cookies last for 14 days before expiring, meaning the cookie only had to be updated every 2 weeks.
Now the system in place is slightly different and has the cookie expire within the hour, meaning a user would need to re-login every hour to keep the cookie valid, and each login creates a new cookie hash.

The CodStatusbot relied on the SSO cookies to authenticate with Activision's servers and check account statuses.
This is clearly not a sustainable or reasonable expectation for users.
Why I won't implement login credential storage? the obvious technical solution would be to store user login credentials and automatically refresh tokens. However, I have made the deliberate decision NOT to implement this for several reasons.

Trust and privacy are a major one. Users should never have to share their login credentials with third party apps. Even with the best security practices, risks would remain.

Many users would rightfully be uncomfortable sharing such sensitive information, as most were already unsure about sharing the cookie, even though the cookie only allowed read access and no write access.

Given these constraints, the bot will most likely be archived in the near future. The current functionality is no longer viable with hourly cookie refreshes, and implementing credential storage goes against most security principles.