launcher
ECHO Launcher
Install, update, repair, and launch ECHO experiences.
3 assetsECHO-Launcher
Runtime control surface133 modules indexed
Official ecosystem home
ECHO
Platform
Build worlds. Launch experiences. Evolve beyond the modpack.
ECHO powers official experiences like Ashfall through modules, launcher-managed installs, PackOS validation, developer tooling, runtime contracts, and future native platform foundations.
Current compatibility
Native Loader is the primary future lane, NeoForge is the compatibility backend for Minecraft play, and Standalone Runtime is the parity harness.
Player gateway
Play Ashfall through the official launcher path.
Start with the download portal, follow current release channels, prepare the launcher handoff, and enter the first official ECHO survival experience.
Developer gateway
Build modules and platform-aware integrations.
Start with the developer portal, then move into module templates, service contracts, UI providers, PackOS metadata, and release gates.
Ecosystem Products
The official surface now maps every repo to a product.
Launcher, modules, Ashfall editions, Release Index, SDK, runtimes, and studios each have an owner, release surface, docs entry, and download role.
Public Releases
modules
ECHO Modules
All shared ECHO module source and per-module release artifacts.
670 assetsECHO-Modules
pack
Ashfall Native Edition
Native runtime Ashfall pack using .echo-addon modules.
5 assetsECHO-Ashfall-Native-Edition
pack
Ashfall NeoForge Edition
Minecraft/NeoForge Ashfall pack using -neoforge.jar modules.
5 assetsECHO-Ashfall-NeoForge-Edition
pack
Ashfall Standalone Edition
Ashfall Standalone Edition using -standalone.jar modules.
5 assetsECHO-Ashfall-Standalone-Edition
pack
Openlands Native Edition
Native runtime Openlands pack using .echo-addon modules.
5 assetsECHO-Openlands-Native-Edition
pack
Openlands NeoForge Edition
NeoForge adapter edition using original Openlands content.
5 assetsECHO-Openlands-NeoForge-Edition
pack
Openlands Standalone Edition
Standalone runtime Openlands pack with no Minecraft dependency.
5 assetsECHO-Openlands-Standalone-Edition
pack
Sky Relay Native Edition
Native runtime Sky Relay pack using .echo-addon modules.
8 assetsECHO-Sky-Relay-Native-Edition
pack
Sky Relay NeoForge Edition
NeoForge Sky Relay pack for Minecraft-compatible validation.
8 assetsECHO-Sky-Relay-NeoForge-Edition
pack
Sky Relay Standalone Edition
Standalone runtime Sky Relay pack with no Minecraft dependency.
8 assetsECHO-Sky-Relay-Standalone-Edition
index
ECHO Release Index
Public catalog and channel metadata for launcher and website downloads.
0 assetsECHO-Release-Index
core
ECHO Native Platform
Native runtime, platform contracts, loader code, and PackOS integration.
7 assetsECHO-Native-Platform
runtime
ECHO Standalone Runtime
Standalone runtime shell and engine for ECHO modules.
4 assetsECHO-Standalone-Runtime
sdk
ECHO SDK
SDK, schemas, contracts, templates, and developer docs.
3 assetsECHO-SDK
studio
ECHO Developer Studio
Developer operations app for release validation and publishing.
8 assetsECHO-Developer-Studio
studio
ECHO Addons Studio
Addon creation app for Native and Standalone modules.
7 assetsECHO-Addons-Studio
Signal route map
ECHO is the operating surface between experience, launcher, package, module, and runtime.
This is the idea the homepage needs to own: ECHO is not a loose modpack description. It is a platform architecture for official experiences like Ashfall, Native Loader-first runtime work, NeoForge compatibility fallback, and Standalone parity.
ECHOPlatform
Ashfall
First official survival experience
Readiness Blocked
Launcher
Player install and repair gateway
Public Releases
PackOS
Package validation and release gates
In Progress
Modules
First-party building blocks
133 tracked
Docs
Player and developer entrypoint
Public guides
AdapterCore
Compatibility boundary
Active
Native Direction
Future runtime-independent work
Foundation Phase
Ashfall transmission
The first official ECHO experience is a survival signal, not a product card.
Ashfall proves the platform in real gameplay: toxic air, radiation, orbital wreckage, faction signals, relays, Lens discovery, HoloMap routes, Terminal missions, Index archives, and Nexus anomalies.
Operations lane
Launcher and PackOS are the install path, release path, and trust path.
Input
01Official release
02Pack metadata
03Module artifacts
Output
01Validated state
02Launcher handoff
03Playable experience
Developer surface
Build against interfaces that know the platform.
ECHO modules can connect to services, data, networking, Terminal tabs, Index providers, Lens scans, HoloMap overlays, PackOS metadata, and launcher-aware release flow.
Runtime stack
A platform stack, not a feature card wall.
The stack stays honest: Minecraft/NeoForge compatibility is the current runtime target. Native runtime work remains future-facing until the shipped platform says otherwise.
Layer 01Official ExperiencesAshfall and future ECHO worldsLayer 02Player GatewayLauncher, download channels, repair flowLayer 03Pack LayerPackOS manifests, lockfiles, release gatesLayer 04Module LayerCore, interface, world, progression systemsLayer 05Runtime ContractsServices, registries, data, networkingLayer 06Runtime LanesNative Loader, NeoForge fallback, Standalone parityLayer 07Native LoaderPrimary future platform lane
Terminal feedECHO public surface
Media
OpenNews
OpenECHO Dev Talk #3 - Turning ECHO Into a Standalone EngineLive on YouTubeECHO AdapterCore Explained - The Bridge Between Minecraft, NeoForge, and ECHO NativeLive on YouTubeECHO: Building PackOS - The Architecture of a Deterministic Modding PlatformLive on YouTubeECHO Release Catalog v0.1.0-native-public-alphaJun 16, 2026