Skip to content

Releases: community-ban-list/discord-cbl

Discord Beta Release

22 Sep 06:49
@sceboucher sceboucher
v0.2
b1456b4
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Discord Beta Release Latest
Latest

The system will now be available to install via Discord, and will be maintained on a server hosted by the Community Ban List team.

Please note that the application is new and is still subject to sudden change or downtime.

Assets 2
Loading

Initial Working Beta Version - 0.1

22 Sep 01:44
@sceboucher sceboucher
v0.1
9e0ac5e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Initial Working Beta Version - 0.1 Pre-release
Pre-release

Full Changelog: https://github.com/sceboucher/discord-cbl/commits/v0.1

This version has not been deployed to Discord's app marketplace yet, and also is not running on permanent infrastructure. This version is a working version of the Discord bot code & API interactions.

Discord CBL Bot v0.1.0-alpha (Pre-release)

Features

  • Implemented /cbl command to fetch and display Community Ban List (CBL) history for a given Steam ID
  • Integrated with CBL GraphQL API for data retrieval
  • Created rich embed messages for displaying user information and active bans
  • Implemented thread creation for displaying expired bans
  • Added Winston logger for comprehensive logging

Technical Details

  • Built with Discord.js v14
  • Uses GraphQL for API requests
  • Implements error handling and logging
  • Utilizes Discord's thread feature for organizing information

Usage

To use the bot, invite it to your server and use the /cbl <steamid> command, where <steamid> is the Steam ID of the player you want to check.

Notes for Developers

  • Ensure DISCORD_TOKEN is set in the .env file
  • The bot requires the GatewayIntentBits.Guilds intent
  • Error handling is in place, but additional edge cases may need to be addressed
  • Logging level is set to 'debug' for development purposes

Known Issues

  • Large numbers of expired bans may hit Discord's character limit in threads

Next steps

  • Deployment to stable service/server to host
  • Addition of user-initiated Steam ID check and storage based on Discord profile
  • Addition of automated role assignment filtering based on CBL points (for controlling entry into core server spaces/airlocking)

Possible future enhancements

  • Implement caching to reduce API calls
  • Add pagination for expired bans in threads
  • Enhance error messages for better user feedback
Assets 2
Loading