xtensions Not Detected/Appearing in Admin Extensions Page

[lag225]

Current Behavior

CURRENT BEHAVIOR (Copy this section)

Multiple Blueprint extensions are properly installed in .blueprint/extensions/ with all required files (conf.yml, admin files, client files, assets), but they do not appear in the Extensions page (/admin/extensions) of the Pterodactyl panel.

Only "Blueprint" (the framework itself) appears in the Extensions list. All manually installed extensions do not appear despite being:

• Properly installed with correct file structure
• Having valid conf.yml files
• Having correct permissions (web server user ownership, 775/664)
• Having private/.store/conf.yml structure created
• All caches cleared multiple times

Extensions Tested:

• Darkenate v2.0.2 (target: beta-A428-2)
• Nebula (theme extension)
• Multiple extensions tested with same result - appears to be a general issue, not extension-specific

---

Expected Behavior

---

EXPECTED BEHAVIOR (Copy this section)

Installed extensions should appear in the Extensions list at /admin/extensions and be available for activation/enabling. Extensions placed in .blueprint/extensions/{identifier}/ with valid conf.yml files should be automatically detected and displayed.

---

Steps to Reproduce

STEPS TO REPRODUCE (Copy this section)

1. Download any .blueprint extension file from https://blueprint.zip/browse (e.g., Darkenate)
2. Extract the .blueprint file (it's a ZIP archive)
3. Copy all extracted files to .blueprint/extensions/{extension-identifier}/ directory
4. Set proper permissions:

   chown -R {web-server-user}:{web-server-user} .blueprint/extensions/{extension-identifier}
   chmod -R 775 .blueprint/extensions/{extension-identifier}
   find .blueprint/extensions/{extension-identifier} -type f -exec chmod 664 {} \;

5. Create private/.store/ directory structure:

   mkdir -p .blueprint/extensions/{extension-identifier}/private/.store
   cp .blueprint/extensions/{extension-identifier}/conf.yml .blueprint/extensions/{extension-identifier}/private/.store/conf.yml

6. Clear all caches:

   php artisan bp:cache
   php artisan cache:clear
   php artisan config:clear
   php artisan view:clear
   php artisan route:clear
   php artisan optimize:clear

7. Restart web server and PHP-FPM services
8. Navigate to /admin/extensions in the panel
9. Result: Extension does not appear in the list (only Blueprint framework appears)

Note: This affects multiple extensions, not just one specific extension. All manually installed extensions exhibit the same behavior.

---

Blueprint Version

beta-2025-12

Panel Version

1.11.11

Is there an existing issue for this?

• I have searched the existing issues before opening this issue.
• I have provided all relevant details and tested my reproduction steps.
• I have checked to my best capabilities and believe this is a bug with the software, and not a configuration issue with my specific system.
• I have made sure to check that this bug is the fault of Blueprint and is not caused by stock Pterodactyl.

[lucas11222]

you need to use blueprint -install (name file).blueprint or blueprint -build for building extensions, more info in here

[prplwtf]

two things:

1. you really should not do this
2. if you really want to manually install extensions, there should be a file called installed_extensions somewhere in the .blueprint/extensions/blueprint directory