Ask or search…
Comment on page

Getting your extension ready for installation

Learn how to export your extension with Blueprint.
We are moving Blueprint's documentation to a brand new website within the following weeks. This documentation website will phase out in the future.
All your extension files need to be moved to your .blueprint/dev folder on your Pterodactyl installation. After doing that, run blueprint -export to export your extension for installation.


Manually packaging extensions is not officially supported and you may encouter issues with it in the future.

With your mouse and keyboard

First, put all your extension's files into a folder and give the folder the same name as your extension's identifier.
Right click the folder and select archive (make sure it archives to a .zip). Now replace the .zip part with .blueprint. Windows and MacOS may warn you that the file may become corrupted, but that does not happen in this case.
Now drag and drop your .blueprint file to "/var/www/pterodactyl" on your target server and run blueprint -i example and replace example with your extension's identifier.
Due to the current limitations of Blueprint, you are required to put all your files in the root of your .blueprint file or in a folder with the same name as your extension identifier.

In your Command Line Interface (Linux)

Put all your extension files into a folder and run zip /path/to/folder. This will generate a zip file with your extension files and output the zip file into the directory you are currently in.
Rename your zip file to a Blueprint extension using mv [IDENTIFIER].blueprint where [IDENTIFIER] is your extension's identifier.
Last modified 27d ago