How dlindustries/system works
Project type and purpose
• This is a Minecraft client‐side mod built with Fabric (a fork of the Argon client) that injects into the Minecraft client to provide optimized PvP features, event hooks, GUI modules, and mixin‐based bytecode patches. Its primary goal is to bypass specific anticheats (Vulcan, Grim) while providing a modular, event‐driven framework for gameplay enhancements.
File structure
• Top‐level build files (build.gradle, settings.gradle, gradlew) indicate a Gradle‐based Java project.
• src/main/java/dlindustries/vigillant/system contains the core:
• Main.java – entry point to initialize the event bus, module manager, and mixins.
• system/event – Event, CancellableEvent, EventManager, Listener interfaces (Observer pattern).
• module – Module, ModuleManager, categories & module implementations (extensibility points).
• mixin & imixin – Fabric Mixin definitions and interfaces for bytecode injection into Minecraft classes.
• gui & font – ClickGui, windowing, font rendering components for the in‐game UI.
• utils – helper classes for game interactions (block, mouse, network simulation).
• src/main/resources/client.mixins.json & fabric.mod.json define Fabric loader metadata and mixin configuration.
• assets/system includes fonts and images for the GUI skin.
README for additional insights
• The README confirms it extends Argon’s core, adds anti‐cheat bypass optimizations (module adjustments, packet ordering fixes).
• Usage instructions show it’s packaged as a Fabric mod JAR, placed in the mods folder.
a. Main components to include
• Minecraft Client (external system)
• Fabric Loader & Fabric API (mod‐loading framework)
• Core Init (Main.java)
• Event System (EventManager + Listener/Event hierarchy)
• Mixin Layer (client.mixins.json → mixin classes → injection points into MinecraftClient, NetworkHandler, Renderer, etc.)
• Module Framework (ModuleManager + individual Module classes grouped by Category)
• GUI Subsystem (ClickGui, Window, Components, FontRenderer)
• Utility Library (Utils, MouseSimulation, BlockUtils, etc.)
• Resources (assets/system/fonts, images)
• Build Pipeline (Gradle wrapper, build scripts)
b. Relationships & interactions
• Fabric Loader initializes the mod via fabric.mod.json, invokes Main.java.
• Main registers mixins (via Fabric API) and initializes the EventManager and ModuleManager.
• Mixin classes inject hooks into Minecraft’s game loop, input handlers, network handlers, and rendering.
• Injected code dispatches events to the EventManager.
• Modules subscribe (Listener) to specific events (e.g., AttackListener, TickListener) to modify behavior or send custom packets.
• Utility classes are invoked by Modules and Listeners to perform computations and simulate user inputs.
• Gradle orchestrates compilation, resource processing, and packaging into a Fabric‐compatible JAR.
c. Architectural patterns & principles
• Observer pattern: EventManager dispatching to Listener implementations.
• Plugin architecture: ModuleManager dynamically loads and manages feature modules.
• Dependency injection & bytecode weaving: Fabric Mixin framework to alter game internals without direct modification.
• Separation of concerns: clear division between core mod init, event dispatch, modules, GUI, and utils.
d. Key technologies & frameworks
• Java 17+
• Gradle build system
• Fabric Loader & Fabric API
• SpongePowered Mixin
• Minecraft client internals (net.minecraft.*)