How fabricmc/fabric-loom works
Main Components
a) Core Plugin Infrastructure
• LoomGradlePlugin (main entry point)
• LoomGradleExtension (configuration)
• ConfigContext (setup context)
b) Decompiler System
• Common decompiler interface
• Three implementations: CFR, Fernflower, and Vineflower
• To core with "uses" relationship
c) Mapping System
• Layered mapping system
• Multiple providers (Mojang, Yarn, Parchment)
• Intermediary mappings
d) Minecraft Processing
• MinecraftProvider
• Library management
• Jar splitting/merging
• To core with "processes" relationship
e) Development Environment Support
• Run configurations
• Project generation
• To core with "generates" relationship
Important Architectural Patterns to Highlight
a) Service Layer
• Service architecture used for mappings, remapping, and decompilation
• Factory pattern used for service creation
b) Extension System
• Plugin's extension mechanism
• How it integrates with Gradle's lifecycle
c) Processing Pipeline
• Demonstrate the transformation pipeline for Minecraft jars
• Flow from raw to processed artifacts
Additional Elements
a) Configuration
• Configuration files and their relationship to components
• Gradle.properties and settings.gradle integration
b) Cache System
• Caching mechanism for processed artifacts
• How it integrates with Gradle's cache
Notes
Notes for:
• Java version compatibility
• Gradle version requirements
• Key external dependencies
• Clear hierarchical layouts
• Custom styling
• Export to various formats
• Version control friendly formats