Route conversation where it belongs.
Game-to-game, game-to-Discord, Discord-to-game, cross-game routes, labels, moderation, filters, and loop prevention.
EmberForge Product 02
Meet Ember Nexus.
A planned customizable, multi-game integration platform for connecting dedicated game servers, Discord, websites, shops, player identities, events, and automation through one extensible system. Phoenix Clan Rising is intended to be the first proving ground, not a permanent product assumption.
Concept / pre-development planning
ARK
Minecraft
Palworld
Conan
Discord
Website
EmberNexus
Why Nexus exists
One connection point. A lot fewer disconnected pieces.
Ember Nexus started with a crosschat problem and immediately grew teeth. Instead of building another one-off replacement for one game, the idea became a reusable platform where communities can connect the systems they already run, choose which capabilities they need, and decide how those systems should talk to each other.
Connect websites to game shops.
Catalogs, currencies, orders, fulfillment queues, delivery state, and adapter-based in-game fulfillment.
Game-agnostic at the core.
The current direction is for ARK, Minecraft, Palworld, Conan, and future games to connect through adapters instead of being baked into Nexus Core.
Link the person behind the accounts.
A future identity layer can connect Discord and game identities into one community account without pretending every platform works the same way.
When this happens, do that.
A future WHEN → IF → THEN engine is planned for alerts, rewards, shop delivery, events, maintenance workflows, and more.
No-code first. API always.
The planned control model combines dashboard configuration for regular admins, deeper controls for power users, and API access for developers.
Architecture direction
Games plug into Nexus. Nexus does not belong to one game.
The core should understand common concepts such as servers, players, messages, events, orders, deliveries, heartbeats, and organizations. Individual adapters translate each game's behavior into that shared language.
Nexus CoreOrganizations, servers, authentication, auditing, health, API versioning.
Event BusCommon events such as chat.message, player.joined, server.offline, and shop.order.created.
Identity LayerLinks community accounts to Discord and game-specific identities.
Game AdaptersARK, Minecraft, Palworld, Conan, and eventually community-built adapters.
Web + DiscordDashboards, websites, shops, chat routes, alerts, and administration.
Product principles
Capabilities, not somebody else's configuration.
Phoenix Clan Rising is planned as the first real-world proving ground, but PCR-specific assumptions should never become Nexus Core assumptions. Ember Nexus is being designed as a product that can take a different shape for every community that eventually uses it.
Your routes. Your labels. Your currencies.
Communities decide how Nexus behaves without editing source code for routine configuration.
Use only what you need.
A community should be able to run crosschat without commerce, commerce without cross-game chat, or build directly against the API.
Isolation is architecture, not cleanup.
Scoped credentials, authentication, tenant isolation, permissions, and audit trails belong in the foundation.
One broken piece should not eat the whole machine.
Failed deliveries should be recoverable, disconnected servers should be contained, and money-moving workflows should be auditable.
Early roadmap
Design the system before summoning the codebase.
Ember Nexus is intentionally still in planning. The current roadmap starts with product identity, terminology, architecture, repository structure, and security thinking before the game-independent core is built and PCR becomes the first crosschat test environment.
PHASE 0
Product Foundation
Brand, terminology, product principles, repository structure, documentation, and initial security/threat modeling.
PHASE 1
Nexus Core
Organizations, servers, API authentication, event ingestion, heartbeats, status, logging, and versioning.
PHASE 2
ARK Adapter + Crosschat
PCR becomes the first production proving ground for ARK ↔ ARK ↔ Discord routing and connection monitoring.
PHASE 3
Nexus Dashboard
No-code management for servers, adapters, routes, credentials, formatting, permissions, event logs, and health.
PHASE 4–6
Identity, Commerce + Automation
Unified player identities, generic shop/fulfillment infrastructure, and configurable WHEN → IF → THEN workflows.
PHASE 7–8
Multi-Game + Productization
Official adapters, Adapter SDK direction, external beta, deployment strategy, documentation, privacy controls, support, and future funding model.
Still on the workbench: Ember Nexus is not released software. The roadmap, supported games, adapters, deployment model, funding model, and individual planned capabilities can change as the product specification and architecture are finalized.
Still on the workbench
Connect your games. Power your community.
Ember Nexus is being shaped as the connection layer between the systems community owners already have to juggle. It is early, deliberately so. Right now the work is product definition before implementation.