Chore: correct errors in README
CI/CD Pipeline / Unit Tests (Python 3.12) (push) Failing after 7s
CI/CD Pipeline / Unit Tests (Python 3.11) (push) Successful in 32s
CI/CD Pipeline / Security Scanning (push) Successful in 27s
CI/CD Pipeline / Build Docker Image (push) Skipped
CI/CD Pipeline / CI/CD Pipeline Status (push) Successful in 1s
CI/CD Pipeline / Unit Tests (Python 3.13) (push) Successful in 34s
CI/CD Pipeline / Integration Tests (push) Skipped
CI/CD Pipeline / Code Quality & Linting (push) Successful in 28s
CI/CD Pipeline / Generate Test Report (push) Successful in 3s

This commit is contained in:
k.eaven committed 2026-10-30 11:06:14 +00:00
1 parent 9a3122a259
commit 204cc6704c
1 file changed
+2 -2
+2 -2
View File
@@ -716,7 +716,7 @@ tail -n 100 logs/pterodisbot.log
If issues persist after trying these solutions:
1. Enable DEBUG logging by reviewing recent log files
2. Check the [Git Issues](https://git.serendipity.systems/k.eaven/pterodactyl-discord-bot/issues) for similar problems
2. Check the [Git Issues](https://git.serendipity.systems/k.eaven/pterodisbot/issues) for similar problems
3. Verify your setup matches all requirements in [Prerequisites](#prerequisites)
4. Test each component individually (Discord bot, Pterodactyl API, permissions)
@@ -726,4 +726,4 @@ This project is licensed under the GPL-3.0 License - see the [LICENSE](LICENSE)
---
**Note**: This bot supports multiple Pterodactyl domains and multiple Discord guilds simultaneously. Each guild tracks servers independently while sharing the same Pterodactyl infrastructure.
**Note**: This bot supports a singular Pterodactyl or Pelican domain with multiple Discord guilds. Each guild tracks servers independently while sharing the same Pterodactyl/Pelican infrastructure. Users from multiple Discord guilds can view and control the same servers running on a given Pterodaactyl/Pelican domain simultaneously.