Update README
This commit is contained in:
@@ -25,8 +25,8 @@ A comprehensive Discord bot for managing Pterodactyl game servers through Discor
|
|||||||
- **Multi-channel Support**: Status embeds can be placed in any channel
|
- **Multi-channel Support**: Status embeds can be placed in any channel
|
||||||
- **Smart Updates**: Only updates embeds when significant changes occur
|
- **Smart Updates**: Only updates embeds when significant changes occur
|
||||||
- **Role-based Access Control**: Restrict server controls to users with specific roles
|
- **Role-based Access Control**: Restrict server controls to users with specific roles
|
||||||
- **Single-guild Operation**: Designed for use in one Discord server
|
- **Single-guild Operation**: Designed for use in one Discord server to restrict access
|
||||||
- **Persistent Storage**: Remembers embed locations between bot restarts
|
- **Persistent Storage**: Remembers embeds and recreates them between bot restarts
|
||||||
- **Comprehensive Logging**: Detailed logs for all operations and errors
|
- **Comprehensive Logging**: Detailed logs for all operations and errors
|
||||||
|
|
||||||
## Installation
|
## Installation
|
||||||
@@ -41,7 +41,7 @@ A comprehensive Discord bot for managing Pterodactyl game servers through Discor
|
|||||||
|
|
||||||
1. Clone the repository:
|
1. Clone the repository:
|
||||||
```bash
|
```bash
|
||||||
git clone https://github.com/yourusername/pterodactyl-discord-bot.git
|
git clone https://git.serendipity.systems/yourusername/pterodactyl-discord-bot.git
|
||||||
cd pterodactyl-discord-bot
|
cd pterodactyl-discord-bot
|
||||||
```
|
```
|
||||||
|
|
||||||
@@ -87,7 +87,8 @@ Once configured and running, the bot will:
|
|||||||
1. Connect to your Discord server
|
1. Connect to your Discord server
|
||||||
2. Sync slash commands
|
2. Sync slash commands
|
||||||
3. Begin monitoring your Pterodactyl servers
|
3. Begin monitoring your Pterodactyl servers
|
||||||
4. Update status embeds every 10 seconds (configurable)
|
4. Update status embeds whenever server status changes or CPU usage spikes up/down for more than 10 seconds
|
||||||
|
5. Create power control buttons for each Pterodactyl server monitored
|
||||||
|
|
||||||
### First Run
|
### First Run
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user