Consultation Round 2: added egg variable auto-injection Pro feature idea
Pro admin panel UI to inject MODPACK_CURRENT_VERSION into eggs fleet-wide. Calibration widget writes value back to egg variable after first setup. Asking Gemini: delay Pro launch for this, or ship current and add in v1.2?
This commit is contained in:
@@ -91,3 +91,45 @@ API returns. The gating happens server-side.
|
||||
Thanks Gemini! 🔥❄️
|
||||
|
||||
— Michael + Claude (Chronicler #85)
|
||||
|
||||
---
|
||||
|
||||
## New Pro Feature Idea — Egg Variable Auto-Injection
|
||||
|
||||
Michael just came up with a Pro feature none of us thought of:
|
||||
|
||||
**The concept:** A ModpackChecker admin panel UI that lets Pro users select
|
||||
which Pterodactyl eggs to inject a `MODPACK_CURRENT_VERSION` variable into
|
||||
— via checkboxes, one click, handled automatically via Pterodactyl's egg API.
|
||||
|
||||
**Why it matters:**
|
||||
- Standard users: calibrate each server once manually via the widget
|
||||
- Professional users: inject the variable slot into their eggs fleet-wide,
|
||||
then the widget writes the version value back to the egg variable after
|
||||
calibration — making future updates trackable automatically
|
||||
|
||||
**The version value question:** The admin still needs to set the actual
|
||||
version value per server (e.g. `5.5.5`). BUT — if calibration in the widget
|
||||
writes back to the egg variable automatically, then after the first calibration
|
||||
it becomes self-maintaining. Server update → admin picks new version in widget
|
||||
→ egg variable updated → Truth File written → fully automatic from there.
|
||||
|
||||
**The big question for Gemini:**
|
||||
Should we hold the Pro launch and make this the centerpiece Pro feature,
|
||||
rather than launching with just webhooks + intervals + dashboard badges?
|
||||
|
||||
Pros of waiting:
|
||||
- Much stronger Pro differentiator
|
||||
- Closer to the "zero config" dream
|
||||
- Could justify the $24.99 price more clearly
|
||||
- Egg injection is genuinely unique — no other Blueprint extension does this
|
||||
|
||||
Cons of waiting:
|
||||
- More development time (April 15 is in 2 days)
|
||||
- Pterodactyl egg API complexity unknown
|
||||
- Could ship Standard now, add Pro later
|
||||
|
||||
**Please evaluate:** Is this worth delaying the Pro tier launch for, or ship
|
||||
what we have and add this as a v1.2 Pro feature?
|
||||
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user