🎯 [EPIC] Phase 1 Vertical Slice - First End-to-End Conversion

[anchapin]

Epic Overview

GOAL: Deliver the first complete end-to-end conversion of a simple Java mod to working Bedrock addon within 2 weeks.

This epic tracks the implementation of critical MVP components identified in the AI Expert Strategic Analysis to achieve a functional vertical slice of the ModPorter AI conversion pipeline.

Success Definition

• Upload simple Java block mod (.jar) → Download working Bedrock addon (.mcaddon)
• Generated addon loads successfully in Minecraft Bedrock
• Block appears with correct texture and properties
• Complete conversion workflow functional end-to-end

Critical Dependencies (MVP Blockers)

🔴 Week 1 Priorities

• Java AST Parsing Pipeline (Issue 🔴 [MVP BLOCKER] Implement Java AST Parsing Pipeline #208)

  • Real .jar file analysis instead of hard-coded templates
  • Block/item/entity detection and property extraction
  • Estimated: 3-4 days

• Bedrock Packager Verification (Issue 🔴 [MVP BLOCKER] Fix Bedrock Packager for .mcaddon Generation #209)

  • Verify and fix .mcaddon structure (currently creates packages but structure may be incorrect)
  • Ensure proper manifest.json generation and UUIDs
  • Estimated: 2-3 days

• Texture Pipeline Integration (Issue 🔴 [MVP BLOCKER] Implement Texture Pipeline Integration #210)

  • Basic PNG copy and asset path mapping
  • Validation and error handling
  • Estimated: 2 days

🟡 Week 2 Priorities

• Frontend Backend Integration (Issue 🟡 [HIGH PRIORITY] Complete Frontend Dashboard Integration #212)

  • Connect existing UI to real conversion APIs
  • Progress tracking and result display
  • Estimated: 2-3 days

• Enhanced Test Sample Repository (Issue 🟡 [HIGH PRIORITY] Create Curated Test Sample Repository #213)

  • Expand beyond existing simple test files
  • Add diverse test cases (entities, GUIs, complex logic)
  • Estimated: 3-4 days

• Template System Expansion (Issue 🟡 [HIGH PRIORITY] Expand Template System Beyond Basic Blocks #211)

  • Multi-type templates beyond basic blocks
  • Smart assumptions engine integration
  • Estimated: 3-4 days

Current Foundation (Already Available)

• ✅ Project Architecture: CrewAI agents, FastAPI backend, React frontend
• ✅ Basic UI Components: Dashboard navigation, upload interface, history
• ✅ Development Environment: Docker, CI/CD, development tooling
• ✅ Initial Test Files: simple_test_mod.jar, simple_copper_block.jar
• ✅ Packaging Infrastructure: .mcaddon creation capability (needs verification)

Phase Implementation Plan

Phase 1: Core Pipeline (Days 1-7)

Focus: Get basic conversion working end-to-end

1. Java Analysis (Days 1-3)

   • Implement real AST parsing in java_analyzer.py
   • Test with existing simple test mods
   • Extract block properties and metadata

2. Package Verification (Days 4-5)

   • Test current .mcaddon output in Minecraft Bedrock
   • Fix any structural issues found
   • Validate manifest.json generation

3. Texture Pipeline (Days 6-7)

   • Basic asset copying and path mapping
   • Integration with packaging system
   • Error handling for missing assets

Phase 2: User Experience (Days 8-14)

Focus: Complete user-facing workflow

1. Backend Integration (Days 8-10)

   • Connect dashboard UI to real APIs
   • Progress tracking and status updates
   • Error handling and user feedback

2. Test Enhancement (Days 11-12)

   • Add complex test cases beyond simple blocks
   • Validation framework for diverse scenarios
   • Performance benchmarking

3. Template Expansion (Days 13-14)

   • Multi-block type support
   • Smart assumptions for incompatible features
   • Enhanced conversion reporting

Success Metrics

• Technical: Simple block mod converts successfully 90%+ of time
• User Experience: Upload to download workflow <2 minutes
• Quality: Generated addons load in Bedrock without errors
• Validation: At least 5 different test mods convert successfully

Risk Mitigation

• Java Parsing Complexity: Start with simple block mods, expand incrementally
• Bedrock Structure Issues: Test early with real Minecraft Bedrock installation
• Integration Challenges: Maintain backward compatibility with existing UI
• Timeline Pressure: Focus on MVP functionality, defer advanced features

Dependencies Map

Java AST (208) ──→ Template System (211)
       │               │
       ▼               ▼
Texture Pipeline (210) ─→ Frontend Integration (212)
       │               │
       ▼               ▼
Package Verification (209) ──→ Enhanced Testing (213)

Completion Criteria

• Real .jar files analyzed programmatically
• Valid .mcaddon packages generated and tested
• Textures correctly copied and mapped
• Full UI workflow functional
• Diverse test cases validate robustness
• Template system handles multiple block types

---

Updated: Based on review comment corrections - packaging agent creates .mcaddon files but needs structure verification, frontend UI partially implemented but needs backend integration, test fixtures have some files but need diversity expansion.

Source: AI Expert Strategic Recommendations (Issue #175)
Next Review: After Week 1 completion