How gmitch215/mobchip works
Project type and purpose
• This is an open-source, multi-module Java/Kotlin library (“MobChip”) for Minecraft (versions 1.13+).
• Purpose: Provide a unified Entity AI & Bosses API by abstracting Minecraft’s native AI, offering version compatibility via reflection/abstraction layers, and integrating with Bukkit as a plugin module.
File structure
• Top-level modules (Gradle projects):
• abstraction – Defines interfaces, utility classes (ChipUtil, CreatureBehavior, NBTSection, etc.)
• base – Core AI engine: brains, bodies, AIs, behaviors, navigation, memories, schedules; uses abstraction interfaces
• bukkit – Platform integration: BukkitAI, event listeners, plugin entry point, ties core engine to server
• nms – Subfolders for each Minecraft server version (1_13_R1 … 1_20_R4): version-specific implementations of abstraction interfaces
• Build & CI:
• build.gradle.kts in root and each module, settings.gradle.kts, Gradle wrapper, GitHub Actions workflow (build.yml)
• Documentation: JavaDocs under bukkit/src/main/javadoc, README, CONTRIBUTING, LICENSE
README for additional insights
• Emphasizes abstraction for compatibility, ease of use, reflection, version checker, open-source.
• Installation via Maven/Gradle “mobchip-bukkit” artifact, pointing to CodeMC Maven repo.
a. Main components
• Abstraction Layer (interfaces, utilities)
• Core Engine (base module: AI controllers, behaviors, schedules, NBT, combat)
• Version Adapters (nms modules: one submodule per supported server version)
• Platform Adapter (bukkit module: plugin bootstrap, event hooks, API surface for plugin authors)
• Build & CI (Gradle, GitHub Actions)
• External Repositories (CodeMC Maven, GitHub)
b. Relationships and interactions
• base and nms modules implement and consume abstraction interfaces
• At runtime, bukkit module instantiates BaseEngine, invokes VersionChecker to load appropriate nms adapter via reflection
• Plugin code (user) calls Bukkit API facades, which delegate to BaseEngine → abstraction → version adapter
• CI pipeline executes Gradle builds, tests across modules, publishes artifacts to Maven
c. Architectural patterns & principles
• Layered architecture: Abstraction → Core → Adapters → Platform
• Dependency Inversion: core depends on interfaces; adapters provide concrete implementations
• Plugin architecture: bukkit module as plugin entry point
• Reflection-based version loading for backward/forward compatibility
d. Key technologies
• Java & Kotlin (Kotlin DSL in some modules)
• Gradle Kotlin DSL for build scripts
• Bukkit API for server integration
• Reflection and abstraction for version independence
Key details to capture
• Multi-module Gradle structure
• Runtime version resolution mechanism
• Clear separation of concerns: interfaces vs. engine vs. adapters vs. integration
• Build/test/publish workflow