a-team-pjnceadc/mite-recrafted

MITE-Recrafted is a Fabric-based Minecraft mod with a clear split between common game logic and client-only presentation logic. The build is Gradle-driven, with Fabric metadata, mixin configs, and an access widener defining how the mod integrates with the base game.

The entrypoint in src/main/java/com/mite/recraft/MiteRecrafted.java is the root of the common-side bootstrap. From there, the mod’s systems are organized around registry-style subsystems: blocks, items, entities, data components, and creative tabs are each isolated into their own packages and registration helpers.

A major architectural boundary is the block/workbench subsystem. It includes custom block types, specialized bar and door blocks, and a workbench family with its own block, menu, and material model. That workbench appears to be a central gameplay surface, not just a decorative block, because it has server-side menu logic and client-side screen UI.

The item/tool subsystem is the largest part of the mod. ModItems, ModTools, ModMaterials, and ModToolMaterial define the base item/material layer, while the toolItem package splits tools into many concrete categories such as swords, bows, arrows, pickaxes, shovels, hatschets, mattocks, warhammers, daggers, and more. This suggests a design where tool behavior is type-specific rather than driven by one generic item class.

The mod also introduces a custom quality/material progression model. Quality and the material-related packages indicate that item strength and crafting results are likely influenced by quality tiers and bespoke material definitions, rather than vanilla item stats alone.

Entity and combat behavior are extended through a custom arrow entity and a set of mixins. The entity/arrowentity/ArrowEntity class is complemented by mixins targeting arrow recovery, stuck-arrow handling, fishing hook behavior, and living-entity arrow state. That indicates the mod modifies vanilla projectile and stuck-projectile logic rather than replacing it entirely.

Networking is small but important: CraftingProgressSyncPayload shows that crafting state is synchronized from server to client. This ties the workbench/menu system to the client screen, so the UI can reflect server-authoritative crafting progress.

The component package suggests the mod uses data components to attach structured state to items or other game objects. In architecture terms, this is the persistence/state layer that sits between registries and runtime behavior.

Client-only code lives under src/client/java, which cleanly separates rendering and screens from the common gameplay systems. The client package provides a custom workbench screen, an arrow renderer, an item property provider for nocked arrows, and a client data generator/model provider for assets.

Data generation is a first-class part of the repository. Providers for recipes, item/block tags, and both English and Chinese language files indicate that a significant portion of content is generated rather than hand-authored, and localization is explicitly supported for two languages.

The resource tree reinforces the content-heavy nature of the mod: there are extensive textures for blocks, doors, bars, workbenches, arrows, bows, tools, and GUI assets. This means the architecture is not just code-driven; the visual and content definitions are a major part of the mod’s surface area.

In diagram terms, the core flow is: Fabric loads the common mod bootstrap, registries install blocks/items/entities/components, mixins alter vanilla behavior, the workbench/menu/server logic produces crafting state, networking syncs that state to the client, and the client renders custom entities, screens, and item models against the generated resources.