Task #26: Modpack Update Monitor — Blueprint Extension (COMMERCIAL PRODUCT) #170

New Issue

mkrause612 · 2026-03-21T02:33:09-05:00

mkrause612 commented

2026-03-21 02:33:09 -05:00

Task #26: Modpack Update Monitor — Blueprint Extension (COMMERCIAL PRODUCT)

Time Estimate: 12-18 hours (commercial-quality development)

Documentation: docs/tasks/ (see operations manual)

Time: 12-18 hours (commercial-quality development)
Status: PROMOTED FROM IDEAS (IDEA-006) - COMMERCIAL DEVELOPMENT
Priority: HIGH - Queued after Codex Phase 2
Market Research: ✅ VERIFIED - No competing products exist (Feb 20, 2026)
Revenue Potential: $500-2,600+ (50-200 sales @ $9.99-12.99)
Documentation: docs/tasks/modpack-update-monitor/ (to be created)

Purpose: First-to-market Pterodactyl extension for automated modpack version monitoring across all platforms

Market Gap Confirmed:

✅ Modpack INSTALLERS exist (can update manually)
✅ In-game update checkers exist (notify players, not admins)
❌ NO server-side admin monitoring dashboard exists
❌ NO automated API checking for updates exists
We would be FIRST TO MARKET with this functionality

Commercial Development Phases:

Phase 1: Core Functionality (8-12 hours) - Build for Firefrost

Scan servers to detect installed modpacks + versions (read manifests)
Query platform APIs (CurseForge, Modrinth, FTB, Technic) for latest versions
Database table: server_id, modpack_id, current_version, latest_version, last_checked, source_platform
Basic dashboard showing update status per server
Cron job for daily checks (configurable interval)
Internal testing on 9 Firefrost servers

Phase 2: Commercial Polish (2-4 hours) - Prepare for marketplace

Professional UI/UX design (match Blueprint standards)
Comprehensive README documentation
Installation guide with screenshots
Troubleshooting guide
Configuration options panel
Error handling and graceful degradation
Performance optimization

Phase 3: Launch & Sales (1-2 hours) - BuiltByBit listing

Professional product description
Feature list with screenshots
Video demonstration (optional but recommended)
Pricing: $9.99-12.99 (competitive with similar extensions)
Support channel setup (Discord/tickets)
Launch announcement

Total Development Time: 12-18 hours for commercial-quality product

The Problem:

12 game servers running modpacks (growing to more)
Manual checking across CurseForge/FTB/Modrinth/Technic is tedious
NO existing Blueprint extension monitors for updates (only installers exist)
Risk of running outdated versions with bugs/exploits
Every multi-server Minecraft host has this same problem

The Solution:
Build first-to-market Blueprint extension that:

Scans each server to detect installed modpack + current version (read manifest files)
Queries platform APIs for latest versions
Dashboard showing update status per server
Optional integration with existing Modpack Installer for one-click updates

Dashboard Display:

Server name
Current modpack + version
Latest available version
Update status (✅ Up to date / ⚠️ Update available / ❌ Check failed)
Last checked timestamp
Source platform (CurseForge/FTB/Modrinth/Technic)
"View Changelog" link
"Update Now" button (if Modpack Installer integration enabled)

Revenue Model:

One-time purchase: $9.99-12.99 per license
Target market: Multi-server Minecraft hosts (thousands globally)
Conservative estimate: 50 sales = $500
Moderate estimate: 100 sales = $1,000
Optimistic estimate: 200 sales = $2,600
Ongoing: Passive income from continued sales
Maintenance: ~1-2 hours/month (bug fixes, API updates)

Competitive Analysis:

Modpack Installer for Blueprint: $5.99 (can update manually, no monitoring)
Modpack & Mods Installer: Price unknown (similar, has mod replacement but no dashboard monitoring)
Our advantage: ONLY solution with automated monitoring dashboard
Pricing rationale: More complex than installer alone, adds significant operational value

Affected Servers (9 modpack servers on Firefrost):

All The Mons (Cobblemon) - NC1
Stoneblock 4 - TX1
Society: Sunlit Valley - TX1
Reclamation - TX1
The Ember Project - NC1
Minecolonies: Create and Conquer - NC1
All The Mods 10 - NC1
EMC Subterra Tech - NC1
Mayview - NC1

Not Applicable:

Vanilla 1.21.11 (no modpack)
Homestead (retiring soon)
Hytale (different game)
FoundryVTT (not Minecraft)

Technical Requirements:

Read server manifests (CurseForge manifest.json, FTB modlist.html, Modrinth modrinth.index.json, Technic modpack.json)
API integration: CurseForge API, Modrinth API, FTB API, Technic API
React dashboard component for Pterodactyl admin view
Blueprint extension framework compliance
Database migrations for version tracking
Cron job system for automated checks

API Rate Limits (daily cron = safe):

CurseForge: 1000 requests/hour (plenty of headroom)
Modrinth: 300 requests/minute (more than sufficient)
FTB: Need to research
Technic: Need to research
Daily cron job = 9 servers × 4 platforms = 36 API calls max

Existing Infrastructure:

✅ Modpack Installer for Blueprint already installed on Firefrost
This extension complements it by adding "check for updates" layer
Could integrate for one-click update workflow (sell as feature)

Workflow Example:

Dashboard shows "ATM10 on NC1 is v1.3, v1.5 available on CurseForge"
Admin clicks "View Changelog" to see what changed
Admin clicks "Update Now" (integrates with Modpack Installer if installed)
Admin uses staggered restart system to schedule restart
Result: Professional update workflow, zero manual checking

Benefits to Buyers:

✅ Immediate visibility of outdated servers
✅ Reduced manual checking time (15 min/day → 0)
✅ Proactive security (catch important updates faster)
✅ Professional operations
✅ Scales to unlimited servers
✅ Works across all major modpack platforms

Benefits to Firefrost:

✅ Solve operational problem (build anyway)
✅ Generate passive income ($500-2,600+)
✅ Attack $400/month deficit
✅ Build brand visibility in Blueprint marketplace
✅ Portfolio piece demonstrating technical capability
✅ "Dogfooding" - we use it daily, so we'll maintain it well

Success Criteria (Internal Use):

✅ Extension installed in Blueprint framework
✅ Dashboard accessible from Pterodactyl admin panel
✅ All 9 modpack servers detected and monitored
✅ API integration working for all 4 platforms
✅ Daily cron job running
✅ Update notifications accurate

Success Criteria (Commercial Launch):

✅ Product listed on BuiltByBit marketplace
✅ Professional documentation complete
✅ First 10 sales within 30 days
✅ 4+ star average rating
✅ Support system functional
✅ Zero critical bugs reported

Licensing:

Proprietary (need the income, can open-source later if desired)
Standard commercial license per server instance
Support included for 6 months post-purchase
Free updates for API changes/bug fixes

Considerations:

Handle custom/manually installed modpacks (no source platform = "Unknown")
Permission levels (who can see updates vs install them)
Notification system (email/Discord when updates available - future enhancement)
Error handling for API failures (graceful degradation)
Multi-language support (English first, expand later)

Why Tier 2 (not Tier 0 quick script):

Michael prefers "do it once and get it done"
Blueprint extension = permanent solution, no revisiting
Commercial quality requires proper development
Integrates with existing Pterodactyl workflow
Professional, scalable, maintainable
Worth the upfront time investment for forever solution + revenue

Why Commercial Development Makes Sense:

Building it anyway (sunk development cost)
Market gap confirmed (first-to-market advantage)
Passive income directly addresses deficit
Aligns with "do it once" - build quality, sell forever
Low ongoing overhead if built well
ROI: ~15 hours work → potentially $500-2,600+ revenue + ongoing sales

Execution Order:

Complete Codex Phase 2 first (finish what we started)
Build Phase 1: Core functionality (8-12 hours, internal testing)
Build Phase 2: Commercial polish (2-4 hours, marketplace ready)
Build Phase 3: Launch on BuiltByBit (1-2 hours)
Enjoy automated version monitoring + passive income

Post-Launch Maintenance:

~1-2 hours/month for bug fixes
API changes (platforms update occasionally)
Blueprint framework updates (rare, usually backward compatible)
Feature requests (prioritize based on demand)
Support tickets (estimate 2-5 hours/month initially)

Source: docs/core/tasks.md (Task #26)

### Task #26: Modpack Update Monitor — Blueprint Extension (COMMERCIAL PRODUCT) **Time Estimate:** 12-18 hours (commercial-quality development) **Documentation:** `docs/tasks/` (see operations manual) --- **Time:** 12-18 hours (commercial-quality development) **Status:** PROMOTED FROM IDEAS (IDEA-006) - **COMMERCIAL DEVELOPMENT** **Priority:** HIGH - Queued after Codex Phase 2 **Market Research:** ✅ VERIFIED - No competing products exist (Feb 20, 2026) **Revenue Potential:** $500-2,600+ (50-200 sales @ $9.99-12.99) **Documentation:** `docs/tasks/modpack-update-monitor/` (to be created) **Purpose:** First-to-market Pterodactyl extension for automated modpack version monitoring across all platforms **Market Gap Confirmed:** - ✅ Modpack INSTALLERS exist (can update manually) - ✅ In-game update checkers exist (notify players, not admins) - ❌ NO server-side admin monitoring dashboard exists - ❌ NO automated API checking for updates exists - **We would be FIRST TO MARKET** with this functionality **Commercial Development Phases:** **Phase 1: Core Functionality (8-12 hours) - Build for Firefrost** 1. Scan servers to detect installed modpacks + versions (read manifests) 2. Query platform APIs (CurseForge, Modrinth, FTB, Technic) for latest versions 3. Database table: server_id, modpack_id, current_version, latest_version, last_checked, source_platform 4. Basic dashboard showing update status per server 5. Cron job for daily checks (configurable interval) 6. Internal testing on 9 Firefrost servers **Phase 2: Commercial Polish (2-4 hours) - Prepare for marketplace** 1. Professional UI/UX design (match Blueprint standards) 2. Comprehensive README documentation 3. Installation guide with screenshots 4. Troubleshooting guide 5. Configuration options panel 6. Error handling and graceful degradation 7. Performance optimization **Phase 3: Launch & Sales (1-2 hours) - BuiltByBit listing** 1. Professional product description 2. Feature list with screenshots 3. Video demonstration (optional but recommended) 4. Pricing: **$9.99-12.99** (competitive with similar extensions) 5. Support channel setup (Discord/tickets) 6. Launch announcement **Total Development Time:** 12-18 hours for commercial-quality product **The Problem:** - 12 game servers running modpacks (growing to more) - Manual checking across CurseForge/FTB/Modrinth/Technic is tedious - NO existing Blueprint extension monitors for updates (only installers exist) - Risk of running outdated versions with bugs/exploits - Every multi-server Minecraft host has this same problem **The Solution:** Build first-to-market Blueprint extension that: 1. Scans each server to detect installed modpack + current version (read manifest files) 2. Queries platform APIs for latest versions 3. Dashboard showing update status per server 4. Optional integration with existing Modpack Installer for one-click updates **Dashboard Display:** - Server name - Current modpack + version - Latest available version - Update status (✅ Up to date / ⚠️ Update available / ❌ Check failed) - Last checked timestamp - Source platform (CurseForge/FTB/Modrinth/Technic) - "View Changelog" link - "Update Now" button (if Modpack Installer integration enabled) **Revenue Model:** - **One-time purchase:** $9.99-12.99 per license - **Target market:** Multi-server Minecraft hosts (thousands globally) - **Conservative estimate:** 50 sales = $500 - **Moderate estimate:** 100 sales = $1,000 - **Optimistic estimate:** 200 sales = $2,600 - **Ongoing:** Passive income from continued sales - **Maintenance:** ~1-2 hours/month (bug fixes, API updates) **Competitive Analysis:** - **Modpack Installer for Blueprint:** $5.99 (can update manually, no monitoring) - **Modpack & Mods Installer:** Price unknown (similar, has mod replacement but no dashboard monitoring) - **Our advantage:** ONLY solution with automated monitoring dashboard - **Pricing rationale:** More complex than installer alone, adds significant operational value **Affected Servers (9 modpack servers on Firefrost):** - All The Mons (Cobblemon) - NC1 - Stoneblock 4 - TX1 - Society: Sunlit Valley - TX1 - Reclamation - TX1 - The Ember Project - NC1 - Minecolonies: Create and Conquer - NC1 - All The Mods 10 - NC1 - EMC Subterra Tech - NC1 - Mayview - NC1 **Not Applicable:** - Vanilla 1.21.11 (no modpack) - Homestead (retiring soon) - Hytale (different game) - FoundryVTT (not Minecraft) **Technical Requirements:** - Read server manifests (CurseForge manifest.json, FTB modlist.html, Modrinth modrinth.index.json, Technic modpack.json) - API integration: CurseForge API, Modrinth API, FTB API, Technic API - React dashboard component for Pterodactyl admin view - Blueprint extension framework compliance - Database migrations for version tracking - Cron job system for automated checks **API Rate Limits (daily cron = safe):** - CurseForge: 1000 requests/hour (plenty of headroom) - Modrinth: 300 requests/minute (more than sufficient) - FTB: Need to research - Technic: Need to research - Daily cron job = 9 servers × 4 platforms = 36 API calls max **Existing Infrastructure:** - ✅ Modpack Installer for Blueprint already installed on Firefrost - This extension complements it by adding "check for updates" layer - Could integrate for one-click update workflow (sell as feature) **Workflow Example:** 1. Dashboard shows "ATM10 on NC1 is v1.3, v1.5 available on CurseForge" 2. Admin clicks "View Changelog" to see what changed 3. Admin clicks "Update Now" (integrates with Modpack Installer if installed) 4. Admin uses staggered restart system to schedule restart 5. Result: Professional update workflow, zero manual checking **Benefits to Buyers:** - ✅ Immediate visibility of outdated servers - ✅ Reduced manual checking time (15 min/day → 0) - ✅ Proactive security (catch important updates faster) - ✅ Professional operations - ✅ Scales to unlimited servers - ✅ Works across all major modpack platforms **Benefits to Firefrost:** - ✅ Solve operational problem (build anyway) - ✅ Generate passive income ($500-2,600+) - ✅ Attack $400/month deficit - ✅ Build brand visibility in Blueprint marketplace - ✅ Portfolio piece demonstrating technical capability - ✅ "Dogfooding" - we use it daily, so we'll maintain it well **Success Criteria (Internal Use):** - ✅ Extension installed in Blueprint framework - ✅ Dashboard accessible from Pterodactyl admin panel - ✅ All 9 modpack servers detected and monitored - ✅ API integration working for all 4 platforms - ✅ Daily cron job running - ✅ Update notifications accurate **Success Criteria (Commercial Launch):** - ✅ Product listed on BuiltByBit marketplace - ✅ Professional documentation complete - ✅ First 10 sales within 30 days - ✅ 4+ star average rating - ✅ Support system functional - ✅ Zero critical bugs reported **Licensing:** - **Proprietary** (need the income, can open-source later if desired) - Standard commercial license per server instance - Support included for 6 months post-purchase - Free updates for API changes/bug fixes **Considerations:** - Handle custom/manually installed modpacks (no source platform = "Unknown") - Permission levels (who can see updates vs install them) - Notification system (email/Discord when updates available - future enhancement) - Error handling for API failures (graceful degradation) - Multi-language support (English first, expand later) **Why Tier 2 (not Tier 0 quick script):** - Michael prefers "do it once and get it done" - Blueprint extension = permanent solution, no revisiting - Commercial quality requires proper development - Integrates with existing Pterodactyl workflow - Professional, scalable, maintainable - Worth the upfront time investment for forever solution + revenue **Why Commercial Development Makes Sense:** - Building it anyway (sunk development cost) - Market gap confirmed (first-to-market advantage) - Passive income directly addresses deficit - Aligns with "do it once" - build quality, sell forever - Low ongoing overhead if built well - ROI: ~15 hours work → potentially $500-2,600+ revenue + ongoing sales **Execution Order:** 1. Complete Codex Phase 2 first (finish what we started) 2. Build Phase 1: Core functionality (8-12 hours, internal testing) 3. Build Phase 2: Commercial polish (2-4 hours, marketplace ready) 4. Build Phase 3: Launch on BuiltByBit (1-2 hours) 5. Enjoy automated version monitoring + passive income **Post-Launch Maintenance:** - ~1-2 hours/month for bug fixes - API changes (platforms update occasionally) - Blueprint framework updates (rare, usually backward compatible) - Feature requests (prioritize based on demand) - Support tickets (estimate 2-5 hours/month initially) --- --- **Source:** `docs/core/tasks.md` (Task #26)

mkrause612 added the

area/panel area/wings area/email area/automation for/michael labels 2026-03-21 02:33:09 -05:00

Sign in to join this conversation.