System composition and topology

two GameApis, two QuestMissions share one gamequest RouteMesh · owner selected per PlayerId

System composition and topology two GameApis, two QuestMissions share one gamequest RouteMesh · owner selected per PlayerId Game Client A · Clients Game Client A Game Client B · Clients Game Client B GameApi 1 · Servers GameApi 1 GameApi 2 · Servers GameApi 2 QuestMission 1 · Servers QuestMission 1 QuestMission 2 · Servers QuestMission 2 STREAM STREAM gamequest RouteMesh Clients Servers

Roles

  • • GameApi owns the session actor and gameplay edge, distributing connections. QuestMission provides the PlayerQuestSpot Instance factory.
  • • The Framework selects the owner per PlayerId using Location Store authority and capacity.
  • • The two roles share one RouteMesh, without creating a per-mission ChannelName.

Message roles

  • • STREAM delivers client requests, responses, and pushes.
  • • RouteMesh delivers Spot direct messages between GameApi and QuestMission nodes.