Platform Overview

ECHO Platform

The foundation behind ECHO experiences.

A modular architecture for launcher-managed worlds, first-party systems, PackOS validation, runtime contracts, and future native ECHO games.

Explore ModulesDeveloper Docs

Architecture

Native Loader first, with explicit compatibility and parity lanes.

Native Loader is the primary future platform lane. NeoForge remains the compatibility backend for Minecraft play, Standalone Runtime is the parity harness, and AdapterCore keeps gameplay contracts shared across them.

Layer 01

Official Experiences

AshfallECHO PrimeFuture ECHO Worlds

Layer 02

Player Layer

ECHO LauncherDownload ChannelsRepair ToolsUpdate Flow

Layer 03

Pack Layer

PackOSManifestsLockfilesChannelsSnapshotsRelease Gates

Layer 04

Module Layer

Core ModulesUI ModulesGameplay ModulesWorld ModulesProgression Modules

Layer 05

Runtime Contract Layer

RegistriesServicesEventsData OwnershipNetworkingSave Compatibility

Layer 06

Runtime Lane Layer

Native LoaderNeoForge Compatibility BackendStandalone Parity HarnessResource BridgeRegistry BridgeContent Bridge

Layer 07

Native Loader Runtime

World RuntimeEntity RuntimeItem RuntimeUI RuntimeRenderer RuntimeSave RuntimeNetworking Runtime

Key Message

ECHO is currently Minecraft-compatible, but it is not architecturally limited to being only a modpack.

The platform is being built around contracts, adapters, validation, tooling, and reusable systems so official ECHO experiences can evolve through Native Loader first while keeping NeoForge fallback and Standalone parity honest.

Platform Systems

The operational pieces that make ECHO feel official.

The site separates the platform into clear responsibilities so players, developers, and contributors can understand where each system fits.

PackOS

Manifest, lockfile, channel, snapshot, release gate, and future integrity layer for official experiences.

AdapterCore

Shared gameplay contract that keeps runtime-specific concerns behind Native Loader, NeoForge, and Standalone hosts.

Runtime Contracts

Services, registries, events, data ownership, and networking surfaces that can outlive a single runtime.

Command Center

Developer-side scanning, validation, promotion, and pack rebuild workflows for ECHO releases.