🌌
Cosmos Guides
  • Cosmos Guides
  • Docker & Compose Setup
    • 01) Docker installation
    • 02) Cosmos Server setup
    • 03) QoL Docker Compose setup
  • Cosmos Server setup
    • 01) Initial launch of Cosmos Server
    • 02) Initial setup of Cosmos Server
    • 03) Cosmos hostname setup
    • 04) DNS Challenge setup (CF)
      • 04a) SSL/TLS settings
      • 04b) SSL Wildcard setup
      • 04c) Creating a DNS Zone API Key
    • 05) Finishing hostname setup
    • 06) Admin account setup
    • 07) Final Steps
  • Pterodactyl Setup
    • 00) Information about Pterodactyl
    • 01) Installing Pterodactyl
      • 01a) Creating a network for Pterodactyl
      • 01b) The Docker Compose example
      • 01c) Launching Pterodactyl
    • 02) Creating URLs
      • 02a) Create URL for pt-panel
      • 02b) Create URL for pt-wings
      • 02c) Setting up CORS
        • 02ca) CORS Option 1 (secure)
        • 02cb) CORS Option 2 (failsafe)
    • 03) Setup of the Panel
      • 03a) Creating the first user
      • 03b) Setting up a location
      • 03c) Setting up the node
      • 03d) IP and Port allocation
    • 04) Connecting the Wings
      • 04a) Creating the config.yml
      • 04b) Check if pt-wings work
      • 04c) Final touches
  • Using Pterodactyl
    • 00) Overview
    • 01) Setting up a game server
      • 01a) Creating a server
        • 01aa) Core Details
        • 01ab) Allocation Management
        • 01ac) Application Feature Limits
        • 01ad) Resource Management
      • 01b) Game server configuration
        • 01ba) Startup Configuration
        • 01bb) Service Variables
      • 01c) Final Steps
        • 01ca) The Pterodactyl Terminal
        • 01cb) Accessing the SFTP server
    • 02) Importing new eggs
      • 02a) Locating the egg
      • 02b) Downloading the egg
      • 02c) Creating a Nest
      • 02d) Importing the egg to the nest
    • 03) Setting up a SteamCMD server
      • 03a) Creating a server
      • 03b) Game server configuration
        • 03ba) Allocation Management
        • 03bb) Nest Configuration
      • 03c) Service Variables
      • 03d) Final Steps
  • Troubleshooting
    • 00) Overview
      • 01) The Node shows up as offline
      • 02) My Panel login page is blank
      • 03) "x509: certificate signed by unknown authority" error (RHEL/CentOS/Fedora)
Powered by GitBook
On this page
  1. Using Pterodactyl
  2. 02) Importing new eggs

02a) Locating the egg

Previous02) Importing new eggsNext02b) Downloading the egg

Last updated 1 year ago

Locating the egg

For this tutorial, I'm going to import an egg for Valheim with BepInEx enabled.

  1. Go to the , locate and then select V Rising Vanilla.

  1. Most importantly, what you want to take note of are the Server Ports.

  2. It is typically divided into "Game" and "Query" ports. When you create a new server, you allocate the "Game" port in the "Default Allocation" field. However, when configuring the server, you will usually have to manually change the Query port. If that sounds confusing right now, I'll explain when we're ready to create the server.

  1. The default V Rising ports in this case are 9876 for the Game port and 9877 for the Query port. And then 25575 for the RCON port. But these ports can be changed into whatever you'd like.

  1. The important thing here is to count how many ports the game server requires and remember that number for when we build the server. Because the "V Rising" server requires three ports (game, query, and RCON), we require three ports in total.

  1. This includes the one for Default Allocation. In total, we need the default allocated port, plus two additional allocated ports for the query and RCON ports.

In there, you'll see the entire for that egg

README
Egg repository