How ff11222/atomicarchitect works
Project type and purpose
• From the file tree and README (“這是一個可以自由地組裝和分解各種原子的minecraft模組”), we see this is a Minecraft mod (Atomic Architect) built with Gradle, targeting Forge or Fabric. Its purpose is to let players assemble and decompose atoms in-game.
File structure
• Top-level build files: build.gradle, gradle wrapper, settings.gradle → standard Gradle mod project.
• src/main/java/org/tingyu/atomicarchitect:
• AtomicArchitect.java – mod entry point
• client/… – client-only code (GUI screens registration)
• common/… – shared logic (handlers, utilities, world, inventory, items, blocks, recipes)
• src/main/resources:
• META-INF/mods.toml – mod metadata
• assets/atomic_architect – blockstates, models, textures, lang files
• pack.mcmeta – resource pack descriptor
README for insights
• While minimal, it confirms the functionality (atomic assembly/decomposition) which maps to recipes, containers, blocks, and UI screens.
Elements
• Mod Loader/Minecraft Engine
• AtomicArchitect (entry point)
• RegistryHandler
• Package modules (client GUI, common logic, utilities)
• Resource assets folder
• Startup flow: Entry Point → RegistryHandler → Minecraft engine registers items/blocks/recipes.
• Runtime flow: Player Input → GUI Screen → Container/Menu → World/Inventory update → Client render.
• Data dependencies: Recipes ↔ Serialization ↔ Registry.
• Blue for client-only components
• Green for server/common logic
• Orange for external systems (Minecraft engine, mod loader)
• Grey for resources/assets