Koil

Minecraft 版本： 1.20.1

平台： fabric quilt

标签： library technology utility

=============================================================================================
    ██╗  ██╗ ██████╗ ██╗██╗       File: https://modrinth.com/mod/koil/settings/description
    ██║ ██╔╝██╔═══██╗██║██║       ----------------------------------
    █████╔╝ ██║   ██║██║██║       Platform: Modrinth
    ██╔═██╗ ██║   ██║██║██║       Owner: SpiritXIV
    ██║  ██╗╚██████╔╝██║███████╗  Org: Koil
    ╚═╝  ╚═╝ ╚═════╝ ╚═╝╚══════╝  -----------------------------------
=============================================================================================

Pre note: as of 6/7 I accidentally deleted the version 0.70.25 from the modrinth and thats what gave us the over 4k downloads, I won't be uploading it again as it still isn't compatable with the 0.70.26 changes that are happening

You can still download 0.70.25 directly from Koil after installation, and the koil-online-data github, but it still won't work. The new system has changed files that 0.70.25 cant find anymore.

What is Koil?

A research-driven middleware framework and experimental operating layer built inside Minecraft.

Koil is not a conventional optimization mod, mod manager, or collection of unrelated quality-of-life features. It is an attempt to explore how much development, automation, content management, diagnostics, artificial intelligence, and system-level tooling can exist within Minecraft while retaining the game’s familiar visual language.

The project is built primarily for developers and technical content creators, including people who create mods, datapacks, resource packs, shaders, configurations, automation routines, and other Minecraft systems.

Koil is experimental software. Many systems are still evolving, and some features require additional configuration, compatible servers, local files, or optional model downloads.

A Development Environment Inside Minecraft

Koil extends Minecraft into a broader technical workspace with integrated tools for inspecting, creating, editing, installing, and managing content without constantly leaving the game.

Current systems include:

• an in-game file explorer and text editor
• configuration discovery and editing
• mod, datapack, resource-pack, shader-pack, and world-content management
• local file previews and metadata inspection
• package construction and installation
• development utilities and project validation
• a Minecraft-integrated console and log viewer
• reusable public APIs for other mods and Koil systems

Koil works with files throughout the Minecraft instance, including configuration files, installed mods, resource packs, shader packs, world datapacks, logs, Koil runtime data, and detected development workspaces.

KPak Package System

Koil includes KPak, a package format and installation system designed for distributing structured Minecraft content and Koil-compatible projects.

KPak provides infrastructure for:

• building packages from inside Minecraft
• package manifests and operation metadata
• author identities and Ed25519 signatures
• package validation
• checksum verification
• transactional installation
• backups and rollback data
• installed-package tracking
• automatic package detection

KPak is still experimental. Its trust infrastructure, key distribution model, and operation semantics continue to be developed and should not be treated as a universal security boundary.

Dynamic Content and Registry Integration

Koil contains a world-aware content registry intended to let content exist dynamically through datapacks and related resources.

The system can inspect active-world datapacks and integrate registered content with supported interfaces.

The long-term objective is to make Minecraft content more dynamic, editable, and world-scoped, while reducing the need to hardcode every possible item, block, property, or metadata field into Koil itself.

Local AI Models

Koil contains a genuine local language-model system rather than a remote chat wrapper.

Supported model infrastructure includes:

• locally installed GGUF models
• a Koil-managed llama.cpp runtime
• configurable local model providers
• streamed model output
• tool-calling support
• local model catalogs
• model compatibility and hardware guidance
• runtime installation, verification, startup, shutdown, and recovery controls
• optional local voice output

Model files are optional and installed separately by the user. Koil can download supported model artifacts and a pinned native inference runtime when requested.

/ask

The normal /ask mode sends a prompt and bounded conversation context to the selected local model. It does not expose Koil tools and cannot directly modify Minecraft or local files.

Deep Thought

/ask deep runs a phased, resumable investigation process.

Deep Thought can use bounded, read-only tools to inspect Minecraft knowledge and configured workspaces. It records evidence, conclusions, progress, and checkpoint state so larger investigations can be paused and resumed.

Automation Mode

Automation Mode allows compatible tool-calling models to operate through registered Koil capabilities.

Depending on the selected mode and approvals, the model may be able to:

• inspect Minecraft state
• create and execute automation plans
• invoke KTL routines
• inspect development workspaces
• create or modify project files
• validate work
• run approved Gradle tasks
• interact with Koil systems
• perform Minecraft actions for the player

Koil includes planning, validation, objective tracking, execution limits, repeated-call detection, approval prompts, and feedback systems. These controls reduce risk, but they do not guarantee that model output or actions are correct.

KTL and Player Automation

Koil includes KTL, its task and automation language.

KTL is backed by an automation architecture containing interpreters, planners, capability registration, execution state, validation, reporting, approvals, feedback, and reusable primitives.

Automation can coordinate actions such as:

• movement and navigation
• looking and turning
• jumping, crouching, and sprinting
• mining and attacking
• using items
• interacting with blocks, entities, inventories, and containers
• executing commands
• running multi-step routines
• maintaining task state across longer operations

Koil automation is designed to operate through structured plans and registered capabilities rather than treating every prompt as an unrestricted command.

Server permissions and normal Minecraft protocol rules still apply. Koil automation does not imply that a server permits automated behavior.

Redesigned F3 and Diagnostics

Koil includes an expanded F3 and diagnostics framework with reusable API structures for modes, sections, data lines, snapshots, targets, and report paths.

The redesigned diagnostic experience is intended to make technical information easier to navigate than the standard debug overlay.

Depending on configuration and build state, Koil can expose:

• structured client and world information
• performance telemetry
• system and renderer details
• block and entity targeting information
• graphs and historical measurements
• expandable diagnostic sections
• captured snapshots
• exported reports
• integration points for other systems

The redesigned interface can be enabled separately. Users may retain the vanilla interface while continuing to use other Koil systems.

Performance Tools

Koil contains performance-monitoring and recommendation infrastructure rather than functioning solely as an optimization mod.

Its performance systems can inspect runtime conditions, display telemetry, organize settings, and associate recommendations with relevant options.

Koil also provides its own video-options integration designed to present vanilla, Sodium, and compatible add-on settings through a more consistent interface when those integrations are available.

Performance behavior depends on the installed mods, hardware, game configuration, and exact Koil build.

Rich Minecraft Chat

Koil expands the existing Minecraft chat instead of replacing it with a separate chat application.

The rich-chat architecture supports or is being developed around:

• multiline messages
• inline and block LaTeX rendering
• remote images
• animated GIFs
• audio
• video and generic file metadata
• media previews
• clipboard and URL handling
• rich-chat synchronization on compatible Koil servers
• reusable APIs for other mods

Remote media is downloaded and cached locally. Media handling uses type-specific size limits, but external files and decoders should still be treated cautiously.

Content Discovery and Installation

Koil can communicate with external content services to search for and inspect Minecraft projects.

Current network integrations represented in the code include:

• Modrinth project search and metadata
• version and compatibility lookup
• optional CurseForge-related paths when configured
• Mojang profile and skin services
• NameMC skin lookup
• GitHub-hosted Koil data
• Hugging Face model downloads
• GitHub-hosted llama.cpp runtime downloads

Content tools can work with mods, datapacks, resource packs, shader packs, skins, and other supported package types.

Skin Tools

Koil includes skin discovery and local skin-library tooling.

The system can:

• search public player profiles
• retrieve profile texture information
• download public skin textures
• normalize compatible PNG files
• maintain a local skin library
• preview and apply supported skins

Skin searches may contact Mojang, Minecraft texture services, and NameMC.

Themes and Interface Framework

Koil has a data-driven interface and design system.

Interface configuration can control elements such as:

• colors
• borders
• headers
• text roles
• backgrounds
• layout values
• textures
• music and interface audio
• screen-specific design groups

Koil's redesigned interfaces follow a compact, square, Minecraft-oriented visual style rather than attempting to imitate a generic desktop application.

The first-launch process allows users to choose between retaining the vanilla interface and enabling Koil's redesigned screens.

Client and Server Architecture

Koil can run client-side, server-side, or on both sides, but available behavior depends on where it is installed.

On servers without Koil

Local systems may still function, including:

• client-side interfaces
• file and content tools
• local models
• diagnostics
• ordinary Minecraft actions
• some automation behavior

Koil-specific synchronized channels and server-owned systems remain unavailable.

On servers running Koil

Compatible client and server installations can cooperate through registered channels for systems such as:

• presence
• activity snapshots
• rich-chat synchronization
• market data
• HUD state
• server-provided diagnostics
• registered Koil APIs

Koil does not guarantee identical functionality across every server.

Public APIs

A central objective of Koil is to expose reusable infrastructure instead of keeping every feature isolated inside its own screen.

The codebase contains APIs and integration layers for systems including:

• automation and capabilities
• KTL execution
• F3 diagnostics
• content registration
• package management
• performance monitoring
• design and interface data
• file utilities
• local models
• rich media
• server/client communication
• compatibility integrations

Koil is intended to become a shared middleware layer that other mods and creator tools can build upon.

Privacy and Network Behavior

Koil is not entirely offline.

Local model inference uses a localhost provider by default, but other systems can contact external services when their corresponding features are used.

Potential network activity includes:

• downloading Koil bootstrap and design data
• searching Modrinth or other configured content services
• downloading models and native inference runtimes
• retrieving skins
• loading remote chat media
• verifying package information
• communicating with the current Minecraft server

Koil also stores subsystem-specific state such as logs, model configuration, downloaded models, Deep Thought checkpoints, automation feedback, content caches, package records, backups, and rich-media files.

There is currently no single global retention or privacy-management panel covering every subsystem.

Current Requirements

• Minecraft: 1.20.1
• Mod loader: Fabric
• Java: 17 or newer
• Fabric Loader: 0.14.21 or newer

Required dependencies:

• Fabric API
• Fabric Language Kotlin

Some features have additional optional requirements, such as compatible content mods, a supported local model, sufficient storage and memory, or a server running Koil.

Project Status

Koil is an active research project and remains unfinished.

Systems may be incomplete, experimental, redesigned between releases, or unavailable under certain configurations. Back up important worlds and files before using development builds, package-management features, automation, or model-controlled tools.

Bug reports, technical feedback, API experimentation, and contributions are particularly useful while the architecture is still developing.

Who Is Koil For?

Koil is primarily intended for:

• mod developers
• datapack creators
• resource-pack creators
• shader developers
• technical players
• automation researchers
• local AI experimenters
• developers exploring Minecraft as an interface and execution environment

Can I use Koil in my Modpacks?

While YES! you can use Koil in your modpacks, Koil is built for it. There are some things to know:

• Koil doesnt work with essentals UI, but you can just use e2mc to host your worlds.
• Thats it!

Koil is not designed around one narrow feature. It is a growing technical layer for building, inspecting, automating, and experimenting within Minecraft.

Develop inside the game. Inspect the instance. Build reusable systems. Push Minecraft beyond the boundaries of a conventional mod.