How devotedmc/factorymod works
Main Components
a. Core System Components:
• FactoryMod (Main Plugin Class)
• FactoryModManager (Central Management)
• ConfigParser (Configuration Handler)
b. Factory Types Layer:
• Factory Interface/Abstract Classes
• Concrete Factory Implementations (FurnCraftChest, Pipe, Sorter)
c. Supporting Systems:
• Interaction Management
• Power Management
• Repair Management
• Recipe System
• Structure Management
┌─ Plugin Interface Layer ─────────────────────┐
• Commands │
• Listeners │
• Events │
• Core Management Layer ────────────────────┐ │
• FactoryModManager │ │
• Configuration │ │
• Permission Management │ │
• Factory Implementation Layer ────────────┐│ │
• Factory Types ││ │
• Structures ││ │
• Interaction Handlers ││ │
• Supporting Systems Layer ──────────────┐││ │
• Power Management │││ │
• Repair Management │││ │
• Recipe System │││ │
• ┘
Key Relationships to Highlight
a. Factory Creation Flow:
• How Factory Eggs create Factory instances
• Structure definitions to Factory types
• Interaction between Factories and Recipes
b. Operational Flow:
• Power Management → Factory Operation
• Recipe Execution → Events
• User Interaction → Factory State Changes
Specific Implementation Details
Specialized components unique to this plugin:
• Factory Types (FurnCraftChest, Pipe, Sorter)
• Recipe Types (Production, Repair, Upgrade, etc.)
• Event System (FactoryActivateEvent, ItemTransferEvent, etc.)
External Integration Points
Connections to:
• Minecraft Server API
• Citadel Plugin (via CitadelListener)
• Configuration Files
• Storage System
Important Notes
a. Use clear symbols:
• Diamonds for interfaces
• Rectangles for concrete classes
b. Related components:
• Recipe system components together
• Factory types together
• Management systems together