Fixed an issue that instantly crashed dedicated servers. Fixed an issue that would install the AI backend even if the offloading option was turned on.

NOTE: This project is still being discontinued; the project's state was just too fatal to leave it as is.

Locrow AI 0.4.0 — Major AI Backend Overhaul

Release Date: November 2025
Minecraft Forge Mod: Locrow AI
Previous Version: 0.3.0 → New Version: 0.4.0

Overview

Locrow AI 0.4.0 represents a major architectural update to the AI backend system. This release focuses on security, improving backend reliability, modularity, and verification. It introduces a fully versioned manifest system, better Python environment management, and deeper integration between AI extensions, models, and the Minecraft mod context.

Core System Overhaul

• Rebranded all systems from AI Packages to AI Backend for clarity and structure.
• Moved core code and extensions into mod resources to unify deployment and improve sandboxing.
• Introduced a manifest system for backend versioning and verification, ensuring all backend files are hashed and signed.
• Added backend hash and seal verification for higher security and tamper resistance.
• Added load manager and runtime log system to track backend state and diagnostics.
• Implemented a setup log system for backend installation and initialization transparency.

Installation & Verification Improvements

• Introduced on-demand Python library installation ("install-what-you-need" system).
• Added model download and installation support with extraction and renaming.
• Combined wheel download and install into a single streamlined step.
• Added site-package verification and embedded wheel manifests inside the mod’s JAR resources.
• Added multi-pip installs per import name and automatic GPU version tagging for Python dependencies.
• Split backend verification into multiple progress stages for clearer feedback.
• Added AI backend verification on mod startup, checking whether any install tasks remain incomplete.
• Added install or load logic that intelligently decides when to reinitialize the backend.
• Fixed an issue that crashed the game on startup if your system was incompatible.

Security & Integrity

• Added a seal helper system for signing backend extensions.
• Added security checks to prevent unregistered extension declarations.
• Introduced a dynamic port system for backend communication isolation.
• Implemented manifest verification and backend signature validation to ensure integrity.
• Fixed an issue where Windows would ask for permission to allow the Python backend server to access the network.

Extension & Model Enhancements

• Added AI extension freeze functionality to stabilize runtime models.
• Added model registration and loading APIs.
• Added thread-locking features for model access and integrated them across bundled AI extensions.
• Introduced load model functions for streamlined AI extension workflows.

UI & User Experience

• Added third-party extensions warning and failed verification warning screens.
• Improved progress bar accuracy and multi-stage feedback during verification and installs.
• The AI Backend Manager screen now receives control after failed installs instead of reverting to the previous menu.
• Updated UI labels and buttons to reflect the new AI Backend terminology.
• Temporarily disabled the "Install" button on the AI Backend Manager Screen.

Developer Utilities

• Added registration hooks to tie AI scripts directly to mod contexts.
• Moved system probe functions into a dedicated SystemProbe module.
• Improved exception handling across the entire backend and installation process.
• Added backend warmup and freeze APIs for testing and controlled startup.

Known Issues

• Minecraft may crash if the AI Backend verification process fails too quickly upon startup.
• The AI Backend may fail to close if Minecraft encounters certain types of crashes or if it is forcefully closed.
• Installation testing will fail if the RVC model "villager/model" is not installed (you can get around this issue by restarting Minecraft after it errors on the test stage of the installation process).

Summary

Locrow AI 0.4.0 is a foundational release that transforms the AI backend into a robust, secure, and extensible system. With manifest-based verification, improved model management, dynamic installation, and refined logging, it paves the way for a more modular and verifiable AI ecosystem within Minecraft.

Locrow AI 0.3.0:

• Prevented player kicks when executing large scripts by improving request offloading.
• Added a progress bar for package installations.
• Introduced an in-game setup log viewer.
• Added a config screen with a built-in package manager for installing/deleting packages manually.
• Implemented warnings for playing in a world while packages are installing.
• Added automatic deletion of old packages.
• Enabled automatic updates for live patch fixes.
• Added a toast to tell users the packages are warmed up and the Python server is running.
• Updated the API to use Locrow AI Python 0.3.0 with variables, loops, conditionals, and nesting.
• The Python Server now shuts down on most crashes. Forceful closes still bypass this shutdown.

Fixed an issue where PATH ENVs were not properly passed to the Python backend server, causing the server to throw an error stating that llama.dll was missing a dependency.

Bug fixes

• Fixed an issue where the bundled venv pointed to a Python dist on my computer (oops).
• Fixed an issue where the Python server would not run unless the user had a CUDA toolkit version installed.

Installation Changes

The Python venv is no longer bundled with the build and instead is automatically set up on the end-user side. The change should reduce the number of potential issues with system compatibility. However, this change has the consequence of lengthening the package installation time. In my experience, it is now 10-15 minutes as opposed to the 5 minutes before this change. Additionally, this change seems to introduce a Windows Security pop-up asking to allow the Python exe to access the network. Minimal testing shows that clicking Allow or Cancel has no effect on the server.