85e28a14d2
Two use cases: 1. Trust/Verification — Check for hacked clients during whitelist 2. Troubleshooting — Help subscribers diagnose crashes Uses mclo.gs for log hosting, bot analyzes and responds. Modpack-specific allowlists for expected mods. Chronicler #75
2.7 KiB
2.7 KiB
task_number, title, status, priority, is_blocker, owner, tags, estimated_hours
| task_number | title | status | priority | is_blocker | owner | tags | estimated_hours | |||
|---|---|---|---|---|---|---|---|---|---|---|
| 106 | Minecraft Log Analyzer Bot | Planned | P3-Low | false | Michael |
|
6 |
Task #106: Minecraft Log Analyzer Bot
Overview
Discord bot integration that analyzes Minecraft logs uploaded to mclo.gs for two purposes:
- Trust/Verification — Check for hacked clients, banned mods during whitelist application
- Troubleshooting — Help subscribers diagnose crashes, connection issues, mod conflicts
Use Cases
Verification Flow
- Player applies for whitelist
- Bot asks: "Please upload your logs to mclo.gs and paste the link"
- Player provides link
- Bot analyzes for:
- Known cheat client signatures
- Xray texture packs
- Banned mod lists
- Suspicious entries
- Bot returns: ✅ Clean or ⚠️ Flagged (with details for staff review)
Troubleshooting Flow
- Subscriber posts in #support: "Game keeps crashing"
- Staff (or bot) asks for mclo.gs link
- Bot analyzes and responds:
- Identified error type
- Common cause
- Suggested fix
- Link to relevant FAQ/guide
Technical Options
Option A: Existing Bot
- LogBot — Pre-built, may have limitations
- HeroBot — More features, may be overkill
Option B: Custom Integration
- Use mclo.gs API to fetch log content
- Build analysis logic into Arbiter or new bot
- Custom rules for Firefrost-specific modpacks
- Auto-respond with modpack-specific troubleshooting
Option C: Hybrid
- Use mclo.gs for hosting
- Custom Arbiter module for analysis
- Tailored responses per server/modpack
Modpack-Specific Considerations
Each modpack has different expected mods. Bot should know:
- ATM10 expected mod list
- Vault Hunters expected mod list
- etc.
Flag anything NOT on the expected list for that server.
Implementation Phases
Phase 1: Research
- Test mclo.gs API
- Evaluate existing bots (LogBot, HeroBot)
- Document common crash patterns across our modpacks
Phase 2: MVP
- Basic log fetching from mclo.gs links
- Simple pattern matching for obvious cheats
- Manual trigger (!analyze )
Phase 3: Troubleshooting
- Crash pattern database
- Auto-suggest fixes
- Link to FAQ articles
Phase 4: Automation
- Auto-detect mclo.gs links in #support
- Integration with whitelist application flow
- Per-modpack mod allowlists
Success Criteria
- Bot can fetch and parse mclo.gs links
- Detects common cheat clients (Wurst, Impact, etc.)
- Identifies top 10 crash causes with suggested fixes
- Staff can verify applicants without manual log reading
- Subscribers get faster support responses
Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️