|
| 1 | +# CreaNexusCore |
| 2 | +**CreaNexusCore** is an ambitious, open-source server architecture designed to unify modifiable games and custom-server environments under a single, streamlined ecosystem. |
| 3 | + |
| 4 | + |
| 5 | +Our mission is to bridge the gap between diverse sandbox gaming communities, providing a centralized core that facilitates interoperability, cross-platform management, and modular extensibility for titles such as **Minecraft** (Java, Bedrock, NetEase, etc.), **ClassiCube**, **Luanti** (formerly Minetest), **Multicraft**, **Hytale**, **Roblox**, **Polytoria**, and more. |
| 6 | + |
| 7 | +## 🌍 Supported Ecosystems & Status |
| 8 | +We track the progress of each engine and protocol bridge. Contributions, bug reports, and pull requests are highly encouraged for items marked as "Experimental" or "In Development." |
| 9 | + |
| 10 | +### ✅ Stable / Semi-Stable |
| 11 | +These integrations are functional but may still have edge-case bugs. |
| 12 | +- **Minecraft (Java Edition)**: Full support (Release/Beta/April Fools). |
| 13 | +- **Minecraft (Bedrock Edition)**: Full support. (1.2-1.26) |
| 14 | +- **Minecraft (NetEase Edition)**: Functional bridge. |
| 15 | +- **EaglerCraft**: Fully integrated. |
| 16 | +- **Discord Chat**: Stable connectivity. |
| 17 | +- **Minecraft Console Edition (Legacy)**: Semi-stable support for Xbox 360, PS3, Wii U, and early PS4/Xbox One versions via VoxelBridge. |
| 18 | +- **ClassiCube**: Stable connection (currently lacking Inventory, Xbox Auth, and Form support). |
| 19 | +- **Luanti / Minetest**: Functional via [BridgeTest](https://codeberg.org/l-koehler/bridgetest) (Requires a Rust-compatible hosting environment; routes through ViaProxy). |
| 20 | + |
| 21 | +### ⚠️ Experimental / W.I.P. |
| 22 | +These implementations are currently in a testing phase or have limited functionality. |
| 23 | +- **Minecraft PE 0.15.x**: Currently in "Spectator Mode" (Limited rendering; no entity support or terrain generation). |
| 24 | + |
| 25 | +### 🏗️ Planned / In Development |
| 26 | +We are currently architecting the protocol bridges for these titles. |
| 27 | +- **Hytale** |
| 28 | +- **Roblox** |
| 29 | +- **Polytoria** |
| 30 | + |
| 31 | +## ⚙️ The Core Architecture: Nukkit MOT |
| 32 | +The heart of **CreaNexusCore** is powered by Nukkit MOT, a highly specialized fork of the Nukkit server software. This core handles the heavy lifting of multi-protocol communication, allowing us to bridge the vast gap between Bedrock versions. |
| 33 | + |
| 34 | +### Core Capabilities: |
| 35 | +- **Version Support**: Extensive support ranging from v1.2 to v1.26 (Bedrock). |
| 36 | +- **NetEase Integration**: Native support for the NetEase protocol variants. |
| 37 | +- **Experimental Legacy Support**: Preliminary support for v1.1. |
| 38 | + |
| 39 | +## 🔗 Protocol Translation Layer: ViaProxy |
| 40 | +To ensure cross-version compatibility for Java and Bedrock clients, we utilize **ViaProxy**. This module acts as the "universal translator," allowing legacy, modern, and experimental Minecraft clients to communicate with our core. |
| 41 | + |
| 42 | +### Supported Protocol Versions |
| 43 | +- **Java Edition**: Full spectrum support from Alpha (a1.0.15) to modern Releases (1.21.11). |
| 44 | +- **Beta/Alpha**: Extensive legacy support (a1.0.15 – b1.8.1). |
| 45 | +- **April Fools**: Specialized support for 3D Shareware, 20w14infinite, and 25w14craftmine. |
| 46 | +- **Combat Snapshots**: Combat Test 8c. |
| 47 | +- **Bedrock Edition**: Support for v1.26.0+. |
| 48 | + |
| 49 | +### 🛡️ Deployment Flexibility: ViaProxyNoCommandRun |
| 50 | +We understand that not every hosting environment allows you to modify the Java startup arguments. **ViaProxyNoCommandRun** is our solution for deploying **ViaProxy** within restrictive environments (like standard shared Minecraft hostings). |
| 51 | +- **How it works**: This specialized .jar bypasses command-line argument requirements, enabling the proxy to initiate successfully in environments where you only have access to a "Start" button or a standard JAR selector. |
| 52 | +- **Best for**: Shared hostings, pre-configured game panels, and quick deployment scenarios where command-line control is unavailable. |
| 53 | + |
| 54 | +[ViaProxyNoCommandRun](https://github.com/Creadores-Program/ViaProxyNoCommandRun) |
| 55 | + |
| 56 | +### Configuration for CreaNexusCore |
| 57 | +ViaProxy must be linked to your **Nukkit MOT** instance (ip and port, ViaBedrock mode) to successfully bridge these versions. |
| 58 | + |
| 59 | +## 🔗 Protocol Translation Layer: ViaProxy & Beta2Release |
| 60 | +To achieve seamless interoperability across Minecraft's history, **CreaNexusCore** leverages **ViaProxy** as the main traffic mediator, enhanced by the **ViaProxyBeta2Release** plugin. |
| 61 | + |
| 62 | +### The Translation Stack |
| 63 | +This combination enables a unified experience for players across widely disparate versions: |
| 64 | +- **ViaProxy Core**: Handles the heavy lifting of multi-protocol communication (Java Alpha to modern Release, Bedrock 1.26.0, and Combat Snapshots). |
| 65 | +- **ViaProxyBeta2Release Plugin**: Specifically bridges the **Beta (b1.0 - b1.8.1)** protocols into the modern Release environment. |
| 66 | + |
| 67 | +## 🌐 EaglerCraft Integration: ayunViaProxyEagUtils |
| 68 | +We bridge the browser-based world of **EaglerCraft** (v1.5.2 and v1.8.8) directly into our server infrastructure. By utilizing the ayunViaProxyEagUtils plugin within **ViaProxy**, we enable WebSocket-to-TCP communication on the same port as your Java traffic. |
| 69 | + |
| 70 | +### Key Features: |
| 71 | +- **WebSocket Support**: Seamlessly handles ws:// connections. |
| 72 | +- **Dual-Version Support**: Compatible with both 1.5.2 and 1.8.8 EaglerCraft clients. |
| 73 | +- **Smart Passthrough**: Supports legacy passthrough and ProtocolSupport, ensuring compatibility even if the backend server does not natively support older protocols. |
| 74 | +> [!NOTE] |
| 75 | + Please be aware that custom skin files are excluded from this bridge. |
| 76 | + |
| 77 | +## 🎮 Minecraft Console Edition (Legacy) Integration: VoxelBridge |
| 78 | +We provide compatibility for the **Legacy Console Edition** of Minecraft (Xbox 360, PS3, Wii U, etc.) through a specialized bridging layer. This allows controllers and consoles from the previous generation to join the **CreaNexusCore** ecosystem. |
| 79 | + |
| 80 | +### The Connection Pipeline |
| 81 | +To ensure proper protocol translation and prevent stability issues, the connection must follow this specific route: |
| 82 | +1. **Console Client**: The console connects to the **VoxelBridge** proxy. |
| 83 | +2. **VoxelBridge**: Acts as the initial interpreter for the Console Edition protocol. |
| 84 | +3. **ViaProxy**: VoxelBridge **must** be configured to point towards our **ViaProxy** instance. |
| 85 | +4. **Nukkit MOT**: ViaProxy finally delivers the translated packets to the core. |
| 86 | + |
| 87 | +- **Status**: Semi-Stable. |
| 88 | +- **Key Requirement**: It is mandatory to daisy-chain **VoxelBridge -> ViaProxy** to resolve version mismatches and ensure that console players are recognized as valid Java-protocol entities before hitting the Bedrock-based core. |
| 89 | + |
| 90 | +## 💬 Community Bridge: Discord Integration |
| 91 | +To maintain a unified community, **CreaNexusCore** includes a native **DiscordChat**. This plugin synchronizes your in-game chat with your Discord server, ensuring seamless communication between players on the server and players on Discord. |
| 92 | + |
| 93 | +### Core Features |
| 94 | +- **Two-Way Sync**: Messages sent in the game are relayed to a specified Discord channel, and messages from that channel are broadcasted in the game. |
| 95 | +- **Bot-Driven**: Powered by a dedicated Discord bot configured within your Nukkit MOT instance. |
| 96 | +- **Management**: Real-time visibility of server activity, player joins/leaves, and chat logs directly from your server's Discord hub. |
| 97 | + |
| 98 | +## 🔧 ClassiCube Integration: Barrel Crea Classic |
| 99 | +To extend CreaNexusCore into the classic sandbox era, we have integrated Barrel Crea Classic. This is a specialized fork of BarrelMC (the predecessor to ViaProxy), heavily modified to support the unique requirements of the ClassiCube protocol. |
| 100 | + |
| 101 | +- **The Bridge Architecture**: By leveraging the logic of ViaBedrock (Geyser Reverse) and the re-architected Java-to-ClassiCube translation layer, Barrel Crea Classic allows legacy-style sandbox clients to interact with our modern server ecosystem. |
| 102 | +- **Protocol Restructuring**: The core has been modified to restructure standard Java packets into the ClassiCube protocol format, effectively allowing seamless communication between your backend and the ClassiCube client. |
| 103 | +- **Status**: Stable. The connection and packet stream are now highly reliable. We have successfully resolved previous byte-stream errors, establishing a consistent gameplay experience. |
| 104 | +- **Current Development**: We are actively working on implementing the Inventory system, Xbox Authentication bypass, and UI Form support to bring full feature parity to ClassiCube players. |
| 105 | + |
| 106 | +## 🦎 Luanti / Minetest Integration: BridgeTest |
| 107 | +We extend our crossplay architecture to the open-source voxel world of **Luanti** (formerly Minetest) using **[BridgeTest](https://codeberg.org/l-koehler/bridgetest)**. This integration allows Luanti clients to interact with our Bedrock-based core by handling external protocol translation. |
| 108 | + |
| 109 | +### The Connection Pipeline |
| 110 | +To successfully process the movement, chat, and block packets, the traffic must route through the following stack: |
| 111 | +1. **Luanti Client**: Connects directly to the **[BridgeTest](https://codeberg.org/l-koehler/bridgetest)** proxy. |
| 112 | +2. **BridgeTest**: Handles the heavy translation from Luanti's native protocol. |
| 113 | +3. **ViaProxy**: [BridgeTest](https://codeberg.org/l-koehler/bridgetest) **must** be configured to point towards our **ViaProxy** instance. |
| 114 | +4. **Nukkit MOT**: ViaProxy delivers the final, clean Bedrock packets to the server core. |
| 115 | + |
| 116 | +### ⚠️ Special Hosting Requirements |
| 117 | +Unlike Java-based utilities, **[BridgeTest](https://codeberg.org/l-koehler/bridgetest) is compiled in Rust**. Because of this binary architecture: |
| 118 | +- **Environment Constraints**: It will **not** run on standard shared Minecraft hosts that only support `.jar` files. |
| 119 | +- **Requirements**: You will need a host with full terminal access (VPS, Dedicated Server, or a custom Pterodactyl egg/Docker container) capable of executing native Rust binaries. |
| 120 | + |
| 121 | +- **Status**: Experimental / Functional. Core movement and text chat are operative, but specialized node/block translations are still under active development. |
| 122 | + |
| 123 | +## 📱 Minecraft Pocket Edition (PE) 0.15.x Integration |
| 124 | +We provide two distinct pathways to bridge legacy MCPE 0.15.x clients into the **CreaNexusCore** ecosystem, allowing administrators to choose between stability and native translation depth. |
| 125 | + |
| 126 | +1. **The DragonProxyPocket Path (Java Bridge Experimental)** |
| 127 | + - **Method**: Utilizes an older **GeyserMC** implementation via **DragonProxyPocket**. |
| 128 | + - **Workflow**: DragonProxy routes players through a Java 1.8 interface, which is then proxied into the **Nukkit** MOT core. |
| 129 | + - **Pros/Cons**: This is currently our most stable method for production environments. While it offers superior connectivity, please be aware that the translation layer may occasionally encounter edge-case rendering bugs or entity desyncs due to the protocol conversion depth. |
| 130 | +2. **The CraftsMine Path (Native Experimental)** |
| 131 | + - **Method**: Utilizes CraftsMine, a specialized fork of BarrelMC. |
| 132 | + - **Workflow**: This implementation bypasses the Java translation layer, attempting to pipe Pocket 0.15 protocol packets directly into the backend architecture. |
| 133 | + - **Pros/Cons**: Designed as a "closer-to-metal" approach, it offers potentially better performance in specific scenarios. However, it is currently in an early Alpha state. Users should expect frequent console warnings/errors and a significantly higher RAM overhead compared to the DragonProxy method. Recommended for testing and development purposes only. |
| 134 | + |
| 135 | +**💡 Pro-Tip**: If you are hosting a multi-protocol server, avoid using newer, non-standard world formats (such as specific internal Bedrock formats or experimental flat-files) as your primary world directory. This will almost certainly lead to packet translation failures for legacy clients. |
| 136 | + |
| 137 | +.gitmodules de CreaNexusCore: |
| 138 | +[submodule "Core"] |
| 139 | + path = Core |
| 140 | + url = https://github.com/MemoriesOfTime/Nukkit-MOT.git |
| 141 | +[submodule "McJava"] |
| 142 | + path = McJava |
| 143 | + url = https://github.com/ViaVersion/ViaProxy.git |
| 144 | +[submodule "McBeta"] |
| 145 | + path = McBeta |
| 146 | + url = https://github.com/ViaVersionAddons/ViaProxyBeta2Release |
| 147 | +[submodule "EaglerCraft"] |
| 148 | + path = EaglerCraft |
| 149 | + url = https://github.com/ayunami2000/ayunViaProxyEagUtils |
| 150 | +[submodule "ClassiCube"] |
| 151 | + path = ClassiCube |
| 152 | + url = https://github.com/Creadores-Program/Barrel-CREA-Classic |
| 153 | +[submodule "McPocket-0_15_x-java"] |
| 154 | + path = McPocket-0_15_x-java |
| 155 | + url = https://github.com/Creadores-Program/DragonProxyPocket.git |
| 156 | +[submodule "McPocket-0_15_x"] |
| 157 | + path = McPocket-0_15_x |
| 158 | + url = https://github.com/Creadores-Program/Craftsmine.git |
| 159 | +[submodule "Discord"] |
| 160 | + path = Discord |
| 161 | + url = https://github.com/PetteriM1/DiscordChat.git |
| 162 | +[submodule "McLegacy"] |
| 163 | + path = McLegacy |
| 164 | + url = https://github.com/brokiem/voxelbridge.git |
| 165 | +[submodule "bridgetest"] |
| 166 | + path = Luanti-Minetest |
| 167 | + url = https://codeberg.org/l-koehler/bridgetest.git |
0 commit comments