Summary
Currently, importing an egg into a nest requires downloading the ExportedNestEgg file first and then uploading it manually through the panel. It would be much more convenient if administrators could provide a direct URL instead, such as a raw GitHub link or an egg file link from resources like https://eggs.pterodactyl.io/, and let the panel fetch and import it automatically.
Motivation
Eggs are often shared through direct links in repositories or public egg libraries. For example, users may find eggs through sites like https://eggs.pterodactyl.io/, but importing them still requires multiple manual steps:
- Open the egg source,
- Download the file,
- Go back to the panel,
- Upload it manually.
Allowing URL-based imports would make this much faster and more convenient, especially when testing or importing multiple eggs.
Proposed Behaviour
Add an "Import from URL" option to the existing egg import flow inside a nest.
When a valid URL is provided, the panel should fetch the egg file server-side and process it through the same import logic that is already used for manually uploaded ExportedNestEgg files.
Scope
This feature would improve the current single-egg import workflow. It would not replace or overlap with the Egg Repository / Git sync system, since that serves a different use case.
Notes
- Server-side validation should be applied before fetching the file.
- The existing file upload import should remain available.
Summary
Currently, importing an egg into a nest requires downloading the
ExportedNestEggfile first and then uploading it manually through the panel. It would be much more convenient if administrators could provide a direct URL instead, such as a raw GitHub link or an egg file link from resources like https://eggs.pterodactyl.io/, and let the panel fetch and import it automatically.Motivation
Eggs are often shared through direct links in repositories or public egg libraries. For example, users may find eggs through sites like https://eggs.pterodactyl.io/, but importing them still requires multiple manual steps:
Allowing URL-based imports would make this much faster and more convenient, especially when testing or importing multiple eggs.
Proposed Behaviour
Add an "Import from URL" option to the existing egg import flow inside a nest.
When a valid URL is provided, the panel should fetch the egg file server-side and process it through the same import logic that is already used for manually uploaded
ExportedNestEggfiles.Scope
This feature would improve the current single-egg import workflow. It would not replace or overlap with the Egg Repository / Git sync system, since that serves a different use case.
Notes