⚠️
SmoothDownDetector
  • 📃Information
  • Documentation
    • 💼Setup
    • 📁YAML files
    • ⌨️Commands & permissions
    • ❓FAQ
  • Links
    • BuiltByBit
    • Discord
Powered by GitBook
On this page
  • Requirements
  • How to install SmoothDownDetector
  • 1. Keepalive module
  • 2. Backend servers
  1. Documentation

Setup

Requirements

  • A Minecraft server (Paper 1.16.5 or higher (or any Paper fork), Velocity or BungeeCord)

  • Pterodactyl panel

  • Java 17 or higher

How to install SmoothDownDetector

If you prefer, I can install the system for you (you need to purchase the add-on through BuiltByBit).

1. Keepalive module

  • Navigate to your Pterodactyl panel.

  • Optionally, create a new nest (Admin Settings > Nests > Create New).

  • Import the egg (egg-java.json) into the created nest (Admin Settings > Nests > Import Egg).

  • Create a new Pterodactyl server using the imported egg and ensure Java version is at least 17.

  • Upload SmoothDownDetector-Keepalive.jar to the newly created server.

  • Start and stop the server.

  • Generate a Pterodactyl Account API key (Account Settings > API Credentials > Create).

  • Paste the generated API key into the config.yml file of the new server.

  • Replace panel.server.com (on power-endpoint-url) with your Pterodactyl panel domain.

  • Set the URL for the keepalive (it can be an IP address). If not using SSL, change the URL to HTTP.

  • Edit the Discord webhook settings.

  • Add as many servers as necessary (you can get the pterodactyl-server-id by accessing the console of each server and looking at the URL).

Remember to expose the keepalive port to the backend servers.

2. Backend servers

  • Upload SmoothDownDetector-[Paper/Velocity/Bungeecord].jar to each backend server.

  • Start and stop each backend server.

  • Replace the keepalive URL with the URL configured before.

  • Set the server-id (it must be the same as the pterodactyl-server-id option on the keepalive).

  • Start each server.

If you wish to use HTTPS/SSL, configure a reverse proxy (e.g., using Nginx).

For smooth operation, it's recommended to allocate 200-250MB of RAM to the Keepalive server.

PreviousInformationNextYAML files

Last updated 10 months ago

💼