Pterodactyl

Provision game servers on a Pterodactyl panel from WemX. Each order creates a panel user when needed, then a server on a node that has room and a free allocation.

Features

• Application API connection with a panel hostname and API key
• Package location, nest, and egg
• Egg variables become package options after the egg is selected
• CPU, memory, disk, swap, and block IO limits
• Database, allocation, and backup limits
• Docker image and startup command taken from the egg
• Place the server on a node in the chosen location that can fit the limits
• Create a panel user for the customer and email the login
• Suspend, unsuspend, terminate, upgrade, and password changes

Install

Install from the WemX marketplace, or download Pterodactyl.zip from a GitHub release and place the Pterodactyl folder at extensions/Servers/Pterodactyl. Then enable Pterodactyl Server.

Publishing a release builds Pterodactyl.zip. Unzipping it creates a folder named Pterodactyl. GitHub’s own “Source code” archive still unpacks to server-pterodactyl-<tag>. Use Pterodactyl.zip.

Connection

Set the panel URL without a trailing slash, for example https://panel.example.com. The API key must start with ptla_ or ptlc_. An application key is required to create users and servers.

Packages

Set the location, nest, and egg. Save the package once so WemX can load that egg’s variables, Docker image, and startup command. Mark location, CPU, memory, disk, and egg variables as configurable when customers should choose them at checkout.

Memory, disk, and swap are entered in GB and sent to the panel in MB. 0 means unlimited for CPU, memory, and disk.