Prerequisites

All of the discussed topics below will require Administrative access to the Admin Panel and to the Node(s) hosting the daemons for applying the changes by executing wisp restart command.

Startup Configuration

Daemon will look for the specific string listed in the startup configuration to detect the server as running. If you’re using a different binary than what the original egg was intended for or generic language eggs (nodejs, python, etc), your server might be stuck in a starting state.

To resolve this, adjust the Startup Configuration of your egg accordingly to match whatever output your game/application would output when it has started.

{
    "done": "Connection to Steam servers successful",
    "userInteraction": []
}

You can also specify multiple done strings by using an array. Example below:

{
  "done": [
        ")! For help, type",
        ")! For help, type"
  ],
    "userInteraction": [
        "Go to eula.txt for more info."
    ]
}

The WISP daemon must be restarted to apply new changes to eggs using wisp restart

Log Configuration

Log path must be configured for WISP to upload logs for the audit logs server crashes and using the upload logs button in the server console. All server output will be output into the specified log file.

1) Navigate to Admin Panel → Service Management —> Nests and choose your Nest and Egg.

2) After opening your selected Egg, you will find Log Configuration section at the bottom.

By default for new or imported Eggs from Pterodactyl, the Log Configuration field will be empty and only contain {}. You are able to specify two keys:

Should your game/application have support for its own log file, you can specify path to it instead and set custom to false. However, majority will require you to create a custom log file.

To create a new log file, add the code below to your egg Log Configuration:

{
    "custom": true,
    "location": "latest.log"
}

After making new changes, you will have to run wisp restart on Node(s) hosting the daemon. The log will be used for the servers under that Egg on their next startup.

<aside> ⚠️ The custom log file is overwritten each time server is started. It is not used for history

</aside>