This document outlines proposed and confirmed features and changes to new versions of Pterodactyl. Currently, the future features and changes listed in this document are for Pterodactyl v2 which is in ongoing development.
These are features/changes that have been confirmed to appear in future releases by one or more members of the Pterodactyl core team.
- pterodactyl/panel#279
- pterodactyl/panel#278
- pterodactyl/panel#3435
- pterodactyl/panel#2878
- pterodactyl/panel#4443
- pterodactyl/panel#2518
- pterodactyl/panel#4533
- pterodactyl/panel#4569
- pterodactyl/panel#4655
- pterodactyl/panel#4877
- pterodactyl/panel#4509
- pterodactyl/panel#4872
- pterodactyl/panel#4873
- pterodactyl/panel#4869
- pterodactyl/panel#4866
Application API keys have been deprecated in favour of client API keys which have access to application API endpoints for administrative accounts from version 1.8 or later. Eventually they will be removed entirely and client API keys will be reimplemented as "Access Tokens".
The admin API which is used for the admin controls in the panel (not to be confused with the application API) will be integrated into the application API. This means that resources formerly only accessible via the admin web view will now be accessible externally through the use of an API key (e.g. managing mounts).
These are features/changes that have been proposed on the GitHub repository and have relevant discussions in the issue or from the Discord server.
- pterodactyl/panel#291
- pterodactyl/panel#4446
- pterodactyl/panel#4387
- pterodactyl/panel#4377
- pterodactyl/panel#3588
- pterodactyl/panel#4337
- pterodactyl/panel#3846
- pterodactyl/panel#3828
- pterodactyl/panel#3640
- pterodactyl/panel#2754
- pterodactyl/panel#2702
- pterodactyl/panel#2615
- pterodactyl/panel#2594
- pterodactyl/panel#2584
- pterodactyl/panel#2483
- pterodactyl/panel#2234