Gameplay Modules
Survival systems, machines, progression gates, hazards, and world events.
Developer Gateway
Build with ECHO
Create modules, systems, interfaces, missions, routes, worlds, and full experiences on top of the ECHO Platform.
Start from shared contracts, reusable services, launcher-aware metadata, module templates, UI integrations, scanner providers, map overlays, mission systems, and PackOS-ready release flow.
What You Can Build
ECHO gives developers reusable surfaces instead of isolated one-off systems.
Gameplay modules, route logic, mission systems, UI tabs, map overlays, scanner providers, world hazards, machines, PackOS manifests, and launcher-compatible experiences can all become part of the same ecosystem.
Interface Providers
Terminal tabs, Index providers, Lens scanners, and HoloMap overlays.
PackOS Metadata
Manifest, channel, release, dependency, and validation metadata.
Launcher Experiences
Package official or future community experiences for launcher-aware delivery.
Build Paths
Pick a surface and start from the right contract.
ECHO development is organized around reusable integration surfaces. Choose the system you are extending, then follow the docs path that keeps your module compatible with the broader platform.
Create a module
Define a reusable ECHO building block with identity, dependencies, docs, and release notes.
Use templateAdd a Terminal tab
Expose missions, intel, route state, rewards, and addon tools inside the player command surface.
Terminal docsAdd an Index provider
Publish recipes, usage records, item archives, and discovery entries without forking UI logic.
Index docsAdd a Lens scanner
Register scan results for blocks, entities, fluids, machines, hazards, and progression clues.
Lens docsAdd a HoloMap overlay
Attach routes, points of interest, crash sites, hazards, relays, bases, and anomalies to world intel.
HoloMap docsPackage with PackOS
Prepare manifest, channel, lockfile, artifact, and release-gate metadata for launcher-aware delivery.
PackOS docsDeveloper Journey
From workspace to launcher package.
The flow is written as a practical operating path: build locally, integrate through platform surfaces, describe package state, then move toward the launcher path players actually use.
Minecraft/NeoForge TodayRuntime-Independent DirectionPackOS-Aware Flow
Clone and install
Prepare the workspace, dependencies, and local development flow.
Build core modules
Confirm ECHO Core, shared contracts, and required module outputs build cleanly.
Create a module
Start from the module template and define identity, category, and dependencies.
Register contracts
Connect services, lifecycle hooks, data ownership, and runtime-facing surfaces.
Integrate UI systems
Add Terminal tabs, Index providers, Lens scanners, or HoloMap overlays.
Add PackOS metadata
Describe package intent, dependencies, release channel, and validation state.
Validate release state
Use SDK validation, release-index metadata, and site audits to catch broken packaging early.
Package for launcher
Prepare the experience for ECHO Launcher delivery and player handoff.
Integration Surface Map
Modules connect through shared systems, not isolated patches.
This map shows the developer mental model: build on core services, publish into player-facing surfaces, and prepare releases for PackOS and launcher delivery.
Module foundation
Active SurfaceECHO Core
NetCore
DataCore
MissionCore
Player surfaces
Active SurfaceTerminal
Index
Lens
HoloMap
Release path
Release FlowPackOS
Launcher
API Areas
Open the exact docs surface you need.
The developer docs are already split by contract area, integration surface, and release workflow so builders do not have to start from a generic docs index.
Core Services
Services, registries, events, lifecycle contracts, and shared module boundaries.
ServicesEventsContracts
Open docsNetworking
Packets, server actions, sync behavior, rate limiting, and debug-friendly message flow.
PacketsSyncActions
Open docsPersistent Data
Player and world data ownership, storage contracts, migration paths, and save-aware design.
PlayerWorldStorage
Open docsUI Integrations
Terminal tabs, Index providers, Lens scanners, and HoloMap overlays as reusable extension surfaces.
TerminalIndexLens
Open docsRelease Gates
Validation expectations, packaging checks, release notes, and launcher-ready package flow.
ValidationReleaseLauncher
Open docsPackOS
Manifests, channels, lockfiles, snapshots, integrity checks, and future package validation.
ManifestChannelsLockfiles
Open docsNext Build Step
Start with the path that matches what you want to ship.
ECHO development should move from docs to modules to package metadata without losing sight of the player delivery path. Use the getting started guide for setup, the module template for structure, GitHub for source, and Discord for community feedback.