Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Minecraft Mod Autopilot

    0

    Closed-loop Minecraft mod development automation and API reference for Forge, Fabric, and NeoForge.

    Free

    Security scanned
    Minecraft Mod Autopilot

    Minecraft Mod Autopilot

    Example session with this skill installed

    My Forge 1.20.1 mod is crashing on startup after I added a new entity. Run the diagnostics and help me fix the registration error.

    • Read your context and instructions
    • Compiled the minecraft mod autopilot

    I have initiated the diagnostic collection process. I retrieved the latest.log and identified a LifecycleEventException during the mod setup phase. The logs indicate a registry mismatch for your new entity.

    Diagnostic Summary & Fix

    MetricDetails
    Error TypeRegistry Object Missing Exception
    Faulty Classcom.example.mod.entity.ModEntities
    Detected LoaderForge 1.20.1
    Log Sourcelogs/latest.log

    The crash occurs because the entity type is being referenced in the EntityRenderers.register call before the deferred register has completed its cycle. Below is the corrected registration and client setup code based on references/forge-1.20.1-api.md.

    // Corrected Entity Registration
    public static final DeferredRegister<EntityType<?>> ENTITIES = 
        DeferredRegister.create(ForgeRegistries.ENTITY_TYPES, MODID);
    
    public static final RegistryObject<EntityType<MyEntity>> MY_ENTITY = 
        ENTITIES.register("my_entity", () -> EntityType.Builder.of(MyEntity::new, MobCategory.CREATURE)
            .sized(0.6f, 1.8f)
            .build("my_entity"));
    
    // In your Client Mod Event Bus Subscriber
    @SubscribeEvent
    public static void onClientSetup(EntityRenderersEvent.RegisterRenderers event) {
        // Reference the RegistryObject directly
        event.registerEntityRenderer(ModEntities.MY_ENTITY.get(), MyEntityRenderer::new);
    }
    

    Next steps

    1. Run scripts/build.ps1 to recompile the project with the corrected registration logic.
    2. Execute scripts/run-client.ps1 to verify the fix.
    3. If the client launches, use the WebSocket bridge to spawn the entity and check rendering.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Developing Minecraft mods involves constant context switching between API docs, build tools, and crash logs. This skill automates the entire Forge 1.20.1 development lifecycle, providing a closed-loop system for writing, building, and debugging mods.

    What it does

    • Automates development loops through a write-build-run-debug cycle for Forge 1.20.1 projects.
    • Diagnostics collection gathers latest.log and crash-reports to identify and fix runtime errors.
    • Minecraft control bridge enables game manipulation via WebSocket, supporting input simulation, mining, and state queries.
    • Loader API reference provides deep documentation for Forge, NeoForge, Fabric, and Paper.
    • Advanced modding techniques covers Mixin configuration, ASM bytecode patches, boss AI, and custom rendering.

    How it works

    1. Develop code for entities, blocks, or mechanics using the internal code reference library.
    2. Build the project using PowerShell scripts that pin JDK 17 and Gradle paths.
    3. Launch either the standard runClient or a specific PCL2 game instance.
    4. Debug by analyzing collected diagnostics through the error triage reference and applying fixes.

    Frameworks & tools

    Forge 1.20.1, NeoForge 1.21.1, Fabric 1.21.1, Paper/Spigot, Gradle, JDK 17, PCL2 Launcher, Mixin, and ASM.

    Why this beats prompting it yourself

    Standard LLMs often hallucinate obfuscated MCP or Mojang mappings and mix up loader-specific registration events. This skill uses verified project-tested references and local automation scripts to ensure code actually compiles and runs in the Minecraft environment.

    Use cases

    • Implement complex boss AI and custom entity state machines.
    • Fix startup crashes or Mixin conflicts using automated log analysis.
    • Migrate existing Forge mods to Fabric or NeoForge versions.
    • Automate acceptance testing using the WebSocket bridge for input simulation.

    Known limitations

    Autopilot automation is specifically tuned for Forge 1.20.1 environments. Support for other loaders in the automation loop is limited to the code reference library.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Autopilot automation loop is pinned to Forge 1.20.1 and JDK 17. Multi-loader support (Fabric/NeoForge) is restricted to the reference library and lacks closed-loop automation.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 10 days ago

    • Free with an Agensi account

    Software
    Git

    Permissions

    Read Files
    Write Files
    Listed10 days ago

    What's inside

    Frequently Asked Questions

    The skill automates the repetitive 'write-build-crash-fix' cycle by using local scripts to compile code, launch the game, and automatically ingest logs to debug common mapping and Mixin errors.

    While the skill provides deep API documentation for Fabric, NeoForge, and Paper, the full automated build-and-debug loop is currently optimized specifically for Forge 1.20.1 projects.

    The package includes a comprehensive library of verified Minecraft API references, PowerShell automation scripts for Gradle/JDK management, and a WebSocket bridge for in-game control.

    You will need JDK 17, a Gradle-based modding environment, and the PCL2 Launcher if you wish to utilize the automated game instance launching features.

    It uses a WebSocket bridge that allows the AI to send input commands, query block states, and simulate player actions to verify that your modded features work as intended.

    This skill is designed to work with any AI agent capable of executing local shell commands and accessing file systems, such as Claude Dev, Roo Code, or custom GPT-based IDE extensions.

    New in Agents & Orchestration

    Free