How the Communication Flow Works
The big picture looks like this:
AI Client → Conductor → MCP Bridge → Discovery Server → Engine Instance → Handler → Engine APIs
That flow matters because it shows how GameCatalyst turns a natural-language request into a governed engine action.
Engine integration (multi-language):
- Unity Adapter (C#) — the current full implementation and primary engine experience
- Unreal Adapter (C++ / Blueprint) — part of the architectural direction and future expansion path
- Godot Adapter (GDScript) — also part of the multi-engine vision and planned structure
Why this matters to you:
- AI requests are routed through structure, not chaos
- Project selection and system discovery stay coordinated
- Handlers determine how work is performed
- Engine APIs are reached through a managed flow
- Future engine support has a clearer architectural path
