This page is currently under construction! Expected information may be missing, sections may be empty, prose may cut off abruptly, etc.
Please note:
The spinning up a server requires Fleff's approval as it consumes machine resources.
The spinning up of a server necessitates administrator privileges on the Pterodactyl panel. At present, only @SYS:OP members have this.
This guide will go over how to create servers on Pterodactyl.
Eggs
An egg is a file which tells Pterodactyl how to install, launch, and manage whatever application the egg is advertising to be installable. It gives Pterodactyl the commands necessary to download server files, instructions on how to setup the environment for the software appropriately, and what configuration options should be available to server operators.[1]
As all games are different not all egg installations will be the same. Some degree of basic server and computer literacy will be necessary. This guide will aim to be as helpful as possible in spite of this.
The benefit of an egg is that, so long as it has been added to the list of eggs on the panel, EDC can terminate and boot up the relevant software on demand.
Step 0: Does the panel already have the egg?
The first thing we want to do is see if we already have the egg. If we do, things get much simpler.
Click the cog icon to the left of the colored smiley face to access the administrative section of Pterodactyl.The Pterodactyl panel button to get to the administrative section.
You will be greeted with the following list (or similar looking list).
List of Pterodactyl egg nests.
The term nest means exactly what you think it means. You can click into the lists and find the relevant game software that you'd like to install.
If you see the egg in the list, skip to step X of this page.
If you do NOT see the egg in the list, proceed to step 2.
Step 2: Finding the egg
Footnotes
↑For example, for the Arma server, it's egg tells Pterodactyl's GUI to provide an option to change the server's modlist. It maps the input made on the GUI to the relevant configuration file on the server.