Egg Store
by texusInstall and update about 300 community eggs with one click. Pelican eggs are converted for you.
Multi-step server workflows that wait for the real server state: announce, stop, back up with rotation, start again.
Multi-step server workflows that wait for the real server state: announce, stop, back up with rotation, start again.
Pterodactyl's built-in schedules run their tasks blindly after fixed delays. "Stop, back up, start" backs up while the server is still shutting down. Then it starts the server again while the backup is still running. Schedules Plus waits for what the server is actually doing. say Restart in 5 minutes -> wait 5 min -> save-all -> stop -> wait until offline -> backup (wait until finished, keep newest 7) -> start -> wait until running Steps • Power action: start, stop, restart, kill • Console command • Wait for a number of seconds • Wait for state: until the server is really running or offline, with a timeout • Backup: wait until finished, rotation (keep the newest N), ignored files • Condition: only continue if the server is running or offline, otherwise stop or skip the next step • HTTP request: sends a JSON POST about the run. Admins have to enable it. Features • Cron schedule with presets, or only by hand. A workflow can be limited to run only when the server is online or offline. • "Continue on failure" per step, so the server is started again even if the backup failed • Run now, cancel, live status • Run history with a log line for every step • Five templates: • Announced restart • Nightly backup with rotation • Consistent offline backup • Keep server running • Daily restart • Subuser permissions respected per step: power steps need the power permission, commands need console access, backups need backup permissions • Actions appear in the server's activity log • Admin page with: • Statistics • Upcoming runs • All runs with a status filter • Limits per server • Run history retention • Runs on Pterodactyl's own queue worker. Waiting steps don't block it. • No core files are modified, the built-in schedules keep working Licence One purchase = one licence = one panel. The licence is bound to one panel domain and the server it runs on. Subdomains count as separate panels: test1.example.com and test2.example.com can't share a licence. You can move the licence to another panel at any time on texus-addons.de. After buying, sign in on texus-addons.de with your sourceXchange email address. Your licence key is created automatically; download the extension there with the key built in, or enter the key on the extension's admin page. Requirements • Pterodactyl Panel 1.15.x • Blueprint (beta-2026-08 or newer) • The panel cron job and queue worker (pteroq), as required by Pterodactyl anyway Installation • Upload schedulesplus.blueprint to /var/www/pterodactyl • Run blueprint -install schedulesplus • Every server now has a "Schedules Plus" tab. Settings are under Admin > Extensions > Schedules Plus. Support The README in the download explains every step type, the permissions and how runs are executed. If something doesn't work, send me the run history of the workflow (it shows which step failed and why). Website: texus-addons.de – licence keys, downloads and your account Support: Discord support server or support@texus-addons.de
Install and update about 300 community eggs with one click. Pelican eggs are converted for you.
Folder tree and editor tabs for every server: several files at once, Ctrl+S, drag and drop.
Email users about sign-ins from new IPs, password or email changes, 2FA turned off, new keys.
Design your own Pterodactyl theme on one settings page: layout, colours, fonts, links, banner, footer. With a live preview.
Suspend user accounts, sign in as a user, require a new password and require 2FA with a grace period.
Show customers why their Minecraft server lags: live TPS and MSPT, 24 hour history, lag spikes and spark profiler reports.
Write the panel's emails yourself: subject and text per language, placeholders, live preview, test mail, Reply-To address.
Copy a server with its settings and files into a new server, or create a new server from one of its backups.