Bug Fixes
- Fixed server installation failing with 500 error — The MCManager install process (Paper, Vanilla, Forge, etc.) could fail with a "Wings error: An unexpected error was encountered" when downloading server files. Added a PHP download fallback: if Wings' native
pullfails, the panel now downloads the file directly and uploads it to the server, ensuring installation always succeeds.- Fixed unqualified Exception class in pullFile — The
catchblock inpullFile()was missing a leading\beforeException, which could cause issues in namespaced contexts.Improvements
- Console link during installer run — When the installer is running in the container (Forge, NeoForge, Quilt), the message now contains a clickable "server console" link (blue, underlined) that opens the console in a new tab, allowing users to monitor progress without losing the installation page.
- Auto-redirect to console after setup — After choosing the startup file in the Setup Wizard, you are now automatically redirected to the server console instead of staying on the MCManager page.
- "Do not navigate away" warning — During the installer step, a clear warning is now shown telling users not to navigate away from the page to avoid losing installation progress.
- Enhanced debug logging — The
pullFilemethod now logs detailed debug messages at every step (Wings pull attempt, fallback download, upload), making it much easier to diagnose installation issues from the Laravel logs.
Bug Fixed:
Changes:
- Fixed an issue where modpacks using ServerPackCreator's start.sh
would fail to start due to an interactive Java installation prompt (Jabba). Pterodactyl containers are non-interactive, causing the script to crash immediately.
- Startup detection reordered: JAR files (Forge, Fabric, NeoForge, Quilt) are now detected before shell scripts, ensuring the correct launcher is always preferred.
- Auto-patch variables.txt
: Shell script startups now automatically set SKIP_JAVA_CHECK=true
, since Java is already pre-installed in Pterodactyl's Docker images. No more Jabba conflicts.- Blacklisted helper scripts: install_java.sh
, install.sh
, settings.sh
and other non-startup scripts are now excluded from automatic detection.
