Modular Addon System for Pterodactyl Panel

[ContatoLucasSonntag]

Describe the feature you would like to see.
I would like to see a modular addon system implemented in the Pterodactyl Panel. The idea is to allow developers to install and manage addons without directly modifying the core files of the panel or Wings.

Each addon would live in its own directory (e.g. /addons/my-addon) and contain its own routes, views, migrations, assets, and config files. A basic JSON descriptor (addon.json) could define metadata like name, version, and compatibility.

This system would solve several issues:

Simplifies upgrades, since custom code is isolated

Encourages safe and scalable panel customization

Enables a community-driven addon ecosystem

Allows clean separation of custom functionality

It could also include:

CLI support like php artisan ptero:addon:install addon-name

Optional admin interface to enable/disable addons

Automatic loading of addon routes, views, and migrations

I’ve already created a working example and would be glad to contribute a prototype if needed.

Describe the solution you'd like.
I would like the panel to support a native addon system that allows developers to create modular features without modifying the core files. Each addon would be placed in a dedicated folder (e.g., /addons/my-addon) and include its own routes, views, migrations, and other resources.

The panel would automatically detect and load these addons during boot, using a structured format defined in an addon.json file. This would enable clean separation of custom features, simplify updates, and support the development of a broader addon ecosystem.

Ideally, this system would also include Artisan commands to install, enable, or disable addons, and potentially a user interface in the admin panel to manage them.

Additional context to this request.
Currently, developers who want to extend the functionality of the Pterodactyl Panel need to modify core files or use workarounds that can break with updates. This creates difficulties in maintaining custom features, especially when upgrading the panel to a new version.

A native addon system would solve this by providing an official, safe, and structured way to extend the panel. It would also encourage community contributions and reusable components, similar to how plugin systems work in platforms like WordPress or Laravel Nova.

I've already created a working example of this concept and would be happy to share it or collaborate on a prototype to help move this idea forward.