WHAT WAS RESEARCHED:
- Blueprint framework documentation and resources
- CurseForge API endpoints and testing method
- Modrinth API documentation
- BuiltByBit marketplace analysis
- Pterodactyl Modpack Installer egg environment variables
- Laravel Task Scheduler integration
KEY FINDINGS:
Blueprint Framework:
- Industry-leading extension framework (well-established)
- Extensions install in seconds via CLI
- Active BuiltByBit marketplace already exists
- Development workflow: init → build → package → distribute
- Templates repo available for scaffolding
CurseForge API:
- Michael already has API key (needs testing)
- Test command provided in docs
- Key endpoints identified for modpack version checking
- BYOK model confirmed as correct approach
Modrinth API:
- Public API, no key required
- User-Agent header mandatory
- Endpoints documented
Database Schema:
- VARCHAR(50) for platform (future-proof vs ENUM)
- is_supported boolean (dynamic based on platform + API)
- Graceful degradation for unsupported platforms
Laravel Integration:
- Pterodactyl already runs schedule:run every minute
- We inject into existing Task Scheduler (no new cron)
- Plug-and-play for buyers
NEXT ACTIONS:
1. Michael tests CurseForge API key with curl command
2. Read Blueprint quick start guide
3. Clone Blueprint templates repo
4. Study CurseForge + Modrinth API docs in detail
5. Test API calls manually
TIMELINE: 1-2 days research → 1-2 weeks development → Launch
This research phase ensures we build on solid technical foundation
before writing any code. Quality over speed.
Signed-off-by: Claude (Chronicler #52) <claude@firefrostgaming.com>
