Tell Pelican and Pterodactyl apart

In short. Pterodactyl and Pelican are two panels (websites used to manage game servers) from the same family: they look alike, but their eggs (the files that tell the panel how to install a server) are not interchangeable. Three checks tell you which one you have: the name written at the very bottom of the panel, the Eggs or Nests entry in the admin menu, and the start of your API keys.

Before you start #

• Be signed in to your panel, in your browser. Check no. 2 needs the administrator account; checks no. 1 and no. 3 work with an ordinary account.
• A word stops you (panel, egg, nest, Wings)? It is explained in the glossary.

Steps #

1. Read the name at the bottom of the panel. Scroll to the very bottom of a page: the footer shows Pterodactyl or Pelican. This is the simplest check.

   <!-- CAPTURE C-045 -->

   <!-- CAPTURE C-037 -->

2. Look at the admin menu. If you are a panel administrator, open the administration and look at the list of entries:

   • a Nests entry (a nest is the folder where the panel keeps its eggs): this is Pterodactyl;
   • an Eggs entry: this is Pelican.

   The address of the eggs page confirms it: it ends with /admin/nests on Pterodactyl and with /admin/eggs on Pelican. <!-- À CONFIRMER : adresses /admin/nests et /admin/eggs (RAPPORT PEL-1), à vérifier sur le banc Pelican -->

   <!-- CAPTURE C-046 -->

3. Look at the start of a client API key, if you have already created one (an API key is a token that lets a program drive your panel). A Pterodactyl key starts with ptlc_, a Pelican key with plcn_.

4. Write down the conclusion. At least two checks must agree. The table sums it up:

   	Pterodactyl	Pelican
   Name at the bottom of the panel	Pterodactyl	Pelican
   Admin entry	Nests	Eggs
   Eggs page	/admin/nests	/admin/eggs
   Client API keys	start with ptlc_	start with plcn_
   Agora egg to take	Egg for Pterodactyl (agora-egg.json)	Egg for Pelican (agora-egg-pelican.json)

5. Follow the article for your panel: Install on Pterodactyl or Install on Pelican.

You know it worked when… #

You can say "I have Pterodactyl" or "I have Pelican" with two checks that agree, and you know which of the two buttons to take on the Install on my panel page of your space on agorapanel.com: Egg for Pterodactyl or Egg for Pelican.

If it does not work #

Going further #

• Why two files? Both eggs describe exactly the same installation. They only differ in how the variable validation rules are written (a string on Pterodactyl, a list on Pelican). A Pterodactyl egg imported into Pelican shows no error on import: it is afterwards the panel's API that answers with a 500 error (console, files, deployment of the FiveM resource by Agora). Taking the right file avoids all of that.
• The eggs' public addresses. If you run a panel for several customers, you can import the egg from its address: https://agorapanel.com/agora-egg.json (Pterodactyl) or https://agorapanel.com/agora-egg-pelican.json (Pelican). These public files do not contain your license key: you type it when you create the server. The egg downloaded from your space does contain your key.
• Pterodactyl and Pelican: Pelican was born from Pterodactyl, which is why the two look alike. Menu names are not always the same from one version to the next: when in doubt, the panel name plus the API keys settle it. <!-- À CONFIRMER : libellés exacts des menus Pelican selon la version du panel -->