[Feature] auto allocation of more than one port for e.g. source games #841
Labels
Feature
Adding a new feature, or substantial improvements on existing functionality
Low Priority
Can wait, not urgent. Handle when possible
Feature Description
Certain pterodactyl eggs needs more than one port to function properly (e.g. ARK needs four: main, main+1, rcon and query port).
While its possible to add more than one port allocation to a product, the user still needs to do several steps by hand, after the server is deployed:
as this breaks the automated deployment of such eggs, it would be nice to have a solution for that.
Solution Idea
it would be great if there would be a way to customize egg parameters at the product setup. There should be a way to auto-allocate additional ports and map it to specified variables of the eggs.
A feasible way could be:
1.) POST to https://{{HOST}}/api/client/servers/{{SERVER_ID}}/network/allocations to assign the allocations to the server.
2.) PATCH to https://{{HOST}}/api/application/servers/{{SERVER_APPID}}/startup to update the servers variables with the learned port numbers.
There are also games which also need Gameport + 1 to function, for example Valheim or ARK. So it would be nice to handle those cases as well. <-- I've learned that those ports are optional and not really required, and there are also limitations on the pterodactyl side, so this part is not that important.
Additional Info
We had a discussion in Discord about this feature: https://discord.com/channels/787829714483019826/1108138041790431435
The text was updated successfully, but these errors were encountered: