🌌
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. 01) Setting up a game server
  3. 01a) Creating a server

01ad) Resource Management

Previous01ac) Application Feature LimitsNext01b) Game server configuration

Last updated 1 year ago

Resource Management

You can set CPU, Memory, and Disk Space limits here. I usually leave mine at 0 because I don't care. However, if you have a large number of servers, or if memory and disk space are limited, you may want to change these values.

Memory and disk space will not exceed the total limit that you set when you .

Memory and Disk Space are the only required fields for you to fill out. The CPU Limit, Swap, and Block IO Weight can all be left at their default values.

On to the next step.

configured the node