Lobby System

Revision as of 20:30, 12 November 2012 by HE-Jay (Talk | contribs)
Jump to: navigation, search
Example Lobby Directory View



One of the most difficult balancing acts to carry out in an online game is the management and distribution of players between conceptual instances of game systems like parties, guilds, phases, and chat.  Membership often depends upon several factors: the location of the player, the affiliation of the player with social groups, the player's current progression through game content, or a player's immediate functional needs; and, as a result, the population and state of these instances fluctuate wildly with time.  It's useful, then, to have a system in which players - regardless of where they are in the game world - can subscribe, unsubscribe, and interact as members of a given conceptual group quickly, efficiently and in a load-balanced manner.

We call these conceptual groups Lobbies and - with customization - they can be used to facilitate a variety of game mechanics which require tracking player membership and interaction.  Support is included to allow direct interaction with lobbies (via replication) from any arbitrary area server or player's client; this is useful in cases (like the traditional 'pre-game lobby') in which players are expected to immediately and directly interact with the lobby and each-other.

Behind the scenes, the Lobby System's logic is housed in a System Area.  This area is responsible for storing data on all currently instantiated Lobbies as well as facilitating communication (either directly through remote calls or indirectly through replication) between clients of the Lobby System and the system itself. The system is load-balanced to prevent over-crowding of any one lobby system worker instance and allows many sparsely-populated areas/systems' lobbies to be combined into a single area instance.

Possible use cases include:

What problems does this solve?

What problems does this not solve?


Lobby System Overall diagram

Areas of Responsibility

The Lobby System is comprised of four areas of responsibility, each of which is carries out its own piece of the overall logic:

The Control Instance is responsible for maintaining knowledge of all Worker Instances that exist as well as the contents of each of the worker instances.  This is accomplished by responding to spin-up and spin-down events for the worker instances as well as maintaining a set of lightweight objects containing the identity of its heavyweight object as well as a means of communicating with its heavyweight object (this is accomplished, as will be explained below, via replication of lightweight objects from the worker instance to which it belongs). All requests to discover or forget a lobby system entity are directed to the control instance, which - having knowledge of the identities and locations of entities - forwards the request to the appropriate worker instance.

The Worker Instance is responsible for creating, destroying and maintaining all lobby system entities.  When an entity is requested to be created, the creation is delegated from the control instance to an appropriate worker instance based upon the load balancing rules defined. Discovery requests made to the control instance are routed to the worker instances, which respond to these requests by 'revealing' (i.e. replicating) the entity to the requester. Likewise, requests to forget, delete, subscribe to, unsubscribe from, or modify an entity are routed through the control instance to the appropriate worker instance, which passes the request to the appropriate lobby system entity for processing.

The Game Area is defined as any area server instance that wants to act as a client of the lobby system by making requests of it.  This means the game area might be another system area, a communal hub area, or any other game area.  This area is responsible for making requests of the lobby system to create, destroy, subscribe players to, unsubscribe players from, or modify lobby system entities.  This is usually accomplished by - after creating an entity - discovering it and then responding to the discovery by performing specific actions upon it.  Additionally, the game area may make lobby system entities available to clients who also wish to interact with the entity.

The Player Client is involved only in situations in which the game area offers an interface to the client to interact with a lobby system entity.  Situations in which this would happen might include the joining of a player to a specific pre-game lobby (the appropriate response to which might be the revealing of the lobby to the client and the presentation of a lobby GUI) or the joining of a player to a specific chat channel (the appropriate response to which might be the updating of the player's chat GUI to reflect the new channel membership).


All objects within the Lobby System are assigned a unique identifier at the moment of creation. These IDs are used by external clients of the Lobby System to identify lobbies, directories or logical directories to which commands or requests should be directed. The public interface to the Lobby System uses these IDs exclusively as handles for objects and - as a result - it is the responsibility of clients of the Lobby System to remember the IDs of objects it is interested in.

The Lobby System is comprised of three basic types of objects:

Lobbies are contained within worker instances of the lobby system. They are responsible for tracking player membership as well as the state of the lobby. Additionally, they process all logic associated with interactions between players in the lobby and interactions between players and the lobby itself. Lobbies are spec-derived objects and provide hooks for extending or overriding their default behavior. Their expected usage includes handling external requests to add/remove players, modify the state of the lobby, and get replicated to other area servers or player clients. Finally, it should be noted that lobbies may be members of any number of Lobby Directories (commonly, a lobby will be a member of both a specific lobby directory as well as the master 'All Lobbies' directory).

Lobby Directories are responsible for tracking and maintaining Lobby objects. They offer a means of indexing and looking-up member lobbies during situations in which messages (e.g. requests for subscription or discovery) need to be delivered to a specific lobby. These directories may contain any number of lobbies, and each directory may itself be part of a collection associated with a Logical Lobby Directory.

Logical Lobby Directories are objects which associate themselves with one or more Lobby Directories. Due to the load-balanced nature of the Lobby System, lobby directories representing the same 'logical' directory may be spread across multiple worker instances; as a result, accessing a conceptual directory in its entirety requires bringing these lobby directories 'out' of their worker instances (via replication) and providing an interface to access the lobbies their merged collection contains. The Logical Lobby Directory provides this interface for clients of discovered directories.


Communication System Request

Communications between outside systems and the lobby system take one of two forms: System Requests or Object Requests

System Requests are requests that are made without direct access to any particular lobby system entity. They are always routed through the $_LOBBY system node and are always asynchronous due to the distributed nature of objects within the lobby system. They often involve the discovery or creation of objects in order to make them available locally.

Object Requests, in contrast, are requests that are made of an object once it has been made local(through creation and then discovery). Lobby system entities that have been localized may be communicated with directly and any information queried for will be returned synchronously. Requests to perform actions (such as 'Start the game' or 'Lock the lobby'), however, will still be performed asynchronously due to the fact that the authoritative object resides in the system area.

System Requests

Object Requests



Personal tools