Releases: josephistired/SpeedtestTrackerBot
v2.0.4
🚀 SpeedtestTrackerBot v2.0.4 — Stability & Compatibility Fixes
Huge thanks to @59n for this contribution! This release fixes several critical issues that caused the bot to break in Discord servers and improves compatibility with upcoming discord.js v15.
🔧 What’s Fixed in 2.0.4
Core Functionality
- Added
GuildMembersintent
Required for accessing member permission data from interaction payloads. - Wrapped permission checks with
PermissionsBitField
Fixes thepermissions.has is not a functioncrash on every command. - Migrated
ready→clientReadyevent
Removes deprecation warnings to get ready for discord.js v15.
Command & UI Fixes
- Fixed
/serverscommand output
Server data now displays properly instead of showing[object Object]. - Extracted and formatted:
- Server name
- Location
- Host metadata
📝 Why These Changes Matter
These issues previously caused:
- Bot crashes on every interaction
- Permission checks failing for admin/developer commands
- Unusable
/serversoutput - Deprecation warnings during startup
All of these are now resolved in v2.0.4.
❗Reminder
If your API token does not include the required abilities, commands will fail.
Make sure your API token has all these abilities checked in /admin/api-tokens
| Ability | Description |
|---|---|
| Read Results | Allows token to read results. |
| Run Speedtest | Allows token to run speedtests. |
| List Servers | Allows token to list servers. |
📚 Documentation
Full usage instructions, command references, and deployment options are available at:
👉 Docs
v2.0.3
🚀 SpeedtestTrackerBot v2.0.3
Added support for the new servers endpoint, and added new error handling.
✨ What’s New
-
/server— Lists all available Ookla speed test servers with IDs and display names. -
Error Handlers — Centralized handlers for common HTTP errors:
- handleUnauthenticatedResponse (401)
- handleForbiddenResponse (403)
- handleNotFoundResponse (404)
- handleValidationResponse (422)
-
/run [server_id]— Now allows you to specify the Ookla server you want the speed test run on.
❗Reminder
If your API token does not include the required abilities, commands will fail.
Make sure your API token has all these abilities checked in /admin/api-tokens
| Ability | Description |
|---|---|
| Read Results | Allows token to read results. |
| Run Speedtest | Allows token to run speedtests. |
| List Servers | Allows token to list servers. |
📚 Documentation
Full usage instructions, command references, and deployment options are available at:
👉 Docs
v2.0.2
🚀 SpeedtestTrackerBot v2.0.2
🐛 Bug Fix
- interactionCreate.js: corrected the developer‐only permission check by renaming the ENV variable from
DEVELOPERIDtoDISCORD_IDwhich matches the ENV names. Now developer commands will run as expected.
- if (command.developer && interaction.user.id !== process.env.DEVELOPERID)
+ if (command.developer && interaction.user.id !== process.env.DISCORD_ID)v2.0.1
🚀 SpeedtestTrackerBot v2.0.1
Added support for the new run endpoint.
✨ What’s New
/run— Initiates a new speed test, waits for completion, and returns the result.
⚠️ API Token Abilities Now Required
Important: The API now uses Token Abilities for all endpoints.
If your API token does not include the required abilities, all commands will fail.
You must generate a new API token from /admin/api-tokens with the following abilities:
| Ability | Description |
|---|---|
| Read Results | Allows token to read results. |
| Run Speedtest | Allows token to run speedtests. |
| List Servers | Allows token to list servers. |
These abilities are required for the bot to function.
Please update your token before using this version.
Note: The List Servers ability is currently not used, but will be required for the upcoming /servers command in a future release.
📚 Documentation
Full usage instructions, command references, and deployment options are available at:
👉 Docs
v2.0.0
🚀 SpeedtestTrackerBot v2.0.0
SpeedtestTrackerBot now uses the latest Speedtest Tracker API, enabling more comprehensive slash command support and endpoint flexibility. This is a major refresh of the bot’s capabilities.
I've also launched a new documentation site to make setup and usage easier than ever.
✨ What’s New
Supports the Latest Speedtest Tracker API
Full compatibility with current endpoints. (Besides filtering.. too much work to do that right now)
Better error handling and future-proof structure
📚 New Docs Site
All usage instructions, command references, and deployment options are now hosted at
👉 Docs
v1.0.0
Release Notes for SpeedtestTrackerBot v1.0.0
Description:
I am excited to announce the release of SpeedtestTrackerBot v1.0.0! This initial release provides a robust foundation for interacting with the Speedtest Tracker API directly from Discord.
Key Features:
- Health Check Command: Check if Speedtest Tracker is running.
- Latest Speedtest Results Command: Retrieve the latest network speed test results.
- Docker Support: Deploy and manage the bot easily using Docker or Docker Compose.
- Multi-Architecture Support: The Docker image supports multiple architectures including linux/amd64 and linux/arm64.
How to Get Started:
Please refer to the README for detailed setup instructions and usage guidelines.
Contributing:
I welcome contributions! If you would like to contribute, please fork the repository and use a feature branch. Pull requests are welcome.
License:
This project is licensed under the MIT License.
Download the release: SpeedtestTrackerBot v1.0.0