How pnk2u/more-stick-variants works
Project Type and Purpose
• This is a Fabric-based Minecraft mod (“More Stick Variants”) written in Java/Gradle.
• Purpose: augment Minecraft by adding wood-type variants for the Stick item, inject compatibility recipes, loot rules, villager-trade behavior, and ship built-in datapacks & resourcepacks.
Key Architectural Components
a. Minecraft Game Engine
b. Fabric Loader & Fabric API
c. Mixin Framework
d. Mod JAR ("More Stick Variants")
• Java code under src/main/java
• Mixin definitions (mixins.json, access widener)
• Entry point: MoreStickVariants.java
• Trade customizer: MstvVillagerTrades + AbstractVillagerMixin
e. Resources packaged in the JAR
• assets/mstv-base: item models, textures, language files
• data/mstv-base, data/lolmgv, etc.: datapacks (recipes, advancements, loot tables, tags)
• resourcepacks/mstv-leaves-loot-fix: optional resourcepack
f. Gradle Build & Loom
• build.gradle, latest-loom.gradle handle compilation, remapping, publishing
g. CI/CD Workflow
• .github/workflows/publish.yml for automated publishing to CurseForge/Modrinth
Runtime Interaction Flow
1. User launches Minecraft → Fabric Loader initializes
2. Fabric API loads mod JARs and registers entry points
3. Mixin Framework reads mixin JSON → applies bytecode injections on Minecraft classes (e.g., AbstractVillager)
4. Mod entry initializes: registers custom item definitions & data pack provider
5. Data Pack Manager loads built-in datapacks from data/… in the JAR
6. Resource Manager loads assets (item models, textures, languages)
7. During game events:
• Loot table resolution uses mod-supplied loot JSON
• Recipe book reads mod’s recipes
• Villager trade logic calls into injected code in MstvVillagerTrades
8. Optional resourcepack (“leaves-loot-fix”) can override block loot tables at runtime
Architectural Patterns & Principles
• Inversion of Control via Fabric’s entrypoint annotations
• Mixin-based Aspect Injection for extending vanilla behavior without forks
• Data-Driven Design: almost all new items, recipes, loot tables, advancements are JSON-driven datapacks
• Separation of Concerns: Java code focuses on runtime hooks/trade logic; JSON in /data and /assets for content
• Build Automation: Gradle + Fabric Loom for remapping and packaging
A. Initialization Phase
• Minecraft Engine loads Fabric Loader → loads Fabric API & Mod JAR
• Mixin subsystem applies patches to vanilla classes
B. Registration Phase
• Mod registers built-in datapacks & resources
• Data Pack Manager ingests JSON definitions
C. Runtime Hooks
• Loot Table & Recipe resolution (data-driven)
• Villager trade customization via mixin hook
D. Build & CI Pipeline (for context)
• Gradle build → Loom remap → JAR creation → GitHub Actions → Publishing
— End of Explanation —