docs(tasks): Update Task #11 for commercial development
Market Research Completed (Feb 20, 2026):
- ✅ VERIFIED: No competing products exist
- Modpack INSTALLERS exist (manual update only)
- In-game update checkers exist (client-side, not admin tools)
- NO server-side admin monitoring dashboard exists
- FIRST TO MARKET opportunity confirmed
Commercial Development Plan:
- Phase 1: Core functionality (8-12 hours) - Build for Firefrost
- Phase 2: Commercial polish (2-4 hours) - Marketplace ready
- Phase 3: Launch & sales (1-2 hours) - BuiltByBit listing
- Total: 12-18 hours for commercial-quality product
Revenue Potential:
- Pricing: $9.99-12.99 per license
- Conservative: 50 sales = $500
- Moderate: 100 sales = $1,000
- Optimistic: 200 sales = $2,600+
- Ongoing passive income from continued sales
Strategic Benefits:
- Directly attacks $400/month deficit
- Build anyway (operational need)
- Brand visibility in Blueprint marketplace
- Portfolio piece for technical capability
- Dogfooding = we use it, we maintain it well
Decision: Commercial development approved per Michael's
'do it once and get it done' philosophy + revenue generation need
Updated version to 3.7
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
|
||||
**Last Updated:** February 20, 2026
|
||||
**Updated By:** The Deployer (Chronicler #20)
|
||||
**Version:** 3.6 (Promoted IDEA-006: Modpack Update Monitor to Task #11)
|
||||
**Version:** 3.7 (Updated Task #11 for commercial development - market research verified)
|
||||
|
||||
---
|
||||
|
||||
@@ -321,24 +321,63 @@ Remove MkDocs (replaced by Wiki.js).
|
||||
|
||||
---
|
||||
|
||||
### 11. Modpack Update Monitor — Blueprint Extension
|
||||
**Time:** 8-12 hours (Blueprint extension development)
|
||||
**Status:** PROMOTED FROM IDEAS (IDEA-006)
|
||||
### 11. Modpack Update Monitor — Blueprint Extension (COMMERCIAL PRODUCT)
|
||||
**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:** Automated version checking for all modpack servers - compare installed vs latest available versions
|
||||
**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
|
||||
- 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)
|
||||
- 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 Blueprint extension that:
|
||||
Build first-to-market Blueprint extension that:
|
||||
1. Scans each server to detect installed modpack + current version (read manifest files)
|
||||
2. Queries platform APIs (CurseForge, FTB, Modrinth, Technic) for latest versions
|
||||
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
|
||||
|
||||
@@ -349,15 +388,25 @@ Build Blueprint extension that:
|
||||
- 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)
|
||||
|
||||
**Technical Requirements:**
|
||||
- Read server manifests (CurseForge manifest.json, FTB modlist.html, Modrinth modrinth.index.json, etc.)
|
||||
- API integration: CurseForge API, Modrinth API, FTB API, Technic API
|
||||
- Database table: server_id, modpack_id, current_version, latest_version, last_checked, source_platform
|
||||
- React dashboard component for Pterodactyl admin view
|
||||
- Cron job for daily checks (configurable interval)
|
||||
**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)
|
||||
|
||||
**Affected Servers (9 modpack servers):**
|
||||
**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
|
||||
@@ -374,58 +423,109 @@ Build Blueprint extension that:
|
||||
- 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 (https://builtbybit.com/resources/modpack-installer-for-blueprint.40083/)
|
||||
- ✅ 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
|
||||
- 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 details to see changelog
|
||||
3. Admin uses Modpack Installer to update (or manual)
|
||||
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: Systematic update workflow
|
||||
5. Result: Professional update workflow, zero manual checking
|
||||
|
||||
**API Rate Limits to Consider:**
|
||||
- CurseForge: 1000 requests/hour
|
||||
- Modrinth: 300 requests/minute
|
||||
- FTB: Unknown (need to research)
|
||||
- Technic: Unknown (need to research)
|
||||
- Daily cron job = 9 servers × 4 platforms = 36 API calls max
|
||||
|
||||
**Benefits:**
|
||||
**Benefits to Buyers:**
|
||||
- ✅ Immediate visibility of outdated servers
|
||||
- ✅ Reduced manual checking time (15 min/day → 0)
|
||||
- ✅ Proactive security (catch important updates faster)
|
||||
- ✅ Professional operations
|
||||
- ✅ Fills gap in Blueprint marketplace (publishable as community extension)
|
||||
- ✅ Pairs perfectly with staggered restart system
|
||||
- ✅ Scales to unlimited servers
|
||||
- ✅ Works across all major modpack platforms
|
||||
|
||||
**Success Criteria:**
|
||||
**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 working
|
||||
- ✅ 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
|
||||
- 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. Then build this with full focus (8-12 hour session)
|
||||
3. Then enjoy automated version monitoring forever
|
||||
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)
|
||||
|
||||
---
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user