Poly Mod Loader — Project Overview & Roadmap
Poly Mod Loader is an advanced, in-engine modding platform and bytecode virtualization layer for Minecraft: Java Edition (supporting versions 26.1, 26.1.1, 26.1.2, 26.2, and 26.3 under Java 25).
1. What is Poly Mod Loader?
Unlike external launcher wrappers (such as Prism, CurseForge App, or Modrinth App) that merely manage profile directories and launch separate games, Poly is an in-game bytecode loader:
- It replaces vanilla Minecraft's startup sequence and hosts a unified classloader.
- It dynamically adapts foreign mod bytecode (Fabric, Forge, NeoForge, Quilt) on the fly, allowing mods from different loaders to run together in the same world, server, or client session.
- It provides its own clean Native API with declarative bytecode transforms, headless gametesting, and version-agnostic abstractions.
2. Core Pillars & Technical Differentiators
+-----------------------------------------------------------------------------------+
| Poly Mod Loader |
+-----------------------------------------------------------------------------------+
| [ Native API ] [ Fabric Bridge ] [ Forge Bridge ] [ NeoForge Bridge ] |
| - System API - FabricLoader API - FML Virtualizer - FML 11 Layer Bridge |
| - Lifecycle API - QuiltLoader API - ModLauncher Shim - Shared Mixin Engine |
+-----------------------------------------------------------------------------------+
| Poly Transform Engine (ASM 9.11) |
| - Declarative Bytecode Transforms - Dynamic Host Patch Adjustments (ADR-0030) |
| - Unified Mixin 0.8.7 Service - Granular Conflict Pre-flight Assessment |
+-----------------------------------------------------------------------------------+
| Poly Transforming ClassLoader & JRE 25 |
+-----------------------------------------------------------------------------------+
| Minecraft: Java Edition (26.x) |
+-----------------------------------------------------------------------------------+
1) True In-JVM Multi-Loader Concurrency
Poly does not run separate games or heavy emulation layers. A single game classloader hosts Poly, Fabric, Forge, and NeoForge mod code simultaneously. Forge and NeoForge's FML services run inside Poly's managed layers, while Fabric and Quilt mods are driven through unified Mixin and ClassTweaker pipelines.
2) Pre-flight Conflict & Patch Assessment (POLY-COMPAT-224)
When Forge or NeoForge patches a vanilla Minecraft class, traditional Fabric Mixins fail because injection targets or local variable tables differ. Poly incorporates an automated Host Patch Check (HostPatchCheck):
- It inspects all mod mixins against the host's actual bytecode before launch.
- If a mixin can be safely adapted (via parameter shifting, expression wrapping, or method retargeting), Poly rewrites the injection point on the fly (
HostPatchAdjustments). - If an incompatible mixin is found, Poly isolates the conflicting mod before the JVM starts, outputting clear diagnostic codes (
POLY-COMPAT-224) instead of crashing the game mid-launch.
3) Near-Zero Performance Overhead
- Startup Time & Memory: Memory footprint and startup duration are within measurement noise compared to vanilla and host loaders.
- Shader & GPU Optimization: Full support for major graphics mods (Sodium, Iris, Lithium) with unified render pipelines.
- Custom Loading Screen: Fast, modern
#0E131Fdark overlay (PolyLoadingOverlay) with real-time mod count overlays per loader.
3. Current Project Status (Release 1.2.3)
| Component | Target / Scope | Status | Notes |
|---|---|---|---|
| Supported Minecraft | 26.1, 26.1.1, 26.1.2, 26.2, 26.3 | Stable | Java 25 required across all platforms. |
| Fabric Mod Support | Fabric Loader 0.19.5 API / Mixin 0.8.7 | Full | 138+ popular Fabric mods verified concurrently on 26.2. |
| Quilt Mod Support | Quilt Loader 0.31.x / quilt.mod.json | Full | 114+ Quilt-only Modrinth mods verified. |
| Forge Mod Support | MinecraftForge 62.0.9 ~ 66.1.0 | Full | Verified on client, dedicated server, and GameTest servers. |
| NeoForge Mod Support | NeoForge 26.1.0 ~ 26.3.0 | Full | Runs via unified FML layer; runs alongside Fabric/Quilt. |
| Fabric API on Forge | 6 Core Modules (fabric-item-api-v1, fabric-registry-sync-v0, fabric-content-registries-v0, etc.) | Adapted | Forge host patches automatically retargeted without crash. |
| NeoForge Injection Points | Screen, Container Menu, Data Attachment | Active (1.2.3) | Initial injection point replacements merged in NeoForgeInjectionPoints. |
| Custom Loading UI | PolyLoadingOverlay | Done | Font corruption fix merged in 1.2.3; loader mod count overlay. |
| Bug Reporting Flow | GitHub Issues Direct Route | Done | Exceptions & crash UI direct users to official issue tracker. |
4. Immediate Roadmap & Future Milestones
Milestone A: Client-Side & NeoForge Fabric API Adaptation (In Progress)
fabric-screen-api-v1: RetargetGuiMixin:onExtractGuifor NeoForge client UI mods (ModMenu, etc.).fabric-menu-api-v1&fabric-data-attachment-api-v1: Integrate NeoForgeopenMenuandAttachmentTypeextensions.- Rendering & Model Modules: Adapt
fabric-renderer-api-v1,fabric-rendering-v1, andfabric-model-loading-api-v1for client-side shaders and resource packs.
Milestone B: Minecraft 26.3 Real-World Corpus Verification
- Headless execution and world save/load verification on 26.3 across large corpus modpacks (
corpusFabric26_3,corpusForge26_3,corpusNeoForge26_3). - Hardening against 26.3-specific game changes (SDL keyboard handling, shader
#include, data pack overlay formats).
Milestone C: Technical Benchmarking
- Publish detailed memory, tick-rate, and startup benchmarks comparing Poly against standalone loaders.
Forward Plan: Forge on NeoForge
- Running MinecraftForge mods on top of a NeoForge host environment (
F-N0~F-N8pipeline).