Matchmaking and Rooms in Unreal Engine uses the Sessions interface. For Unreal Engine, a session is an instance of a game running on the server, which is either public, with a set of properties so players can decide whether they want to join, or private so only invited players can join.
Both the Rooms and Matchmaking integrations using the OSS Sessions interface are limited in scope. For a full-featured Room and Matchmaking integration, use the native C APIs.
Please note that when a session is created, either Room or Matchmaking, a VoIP connection is not created. You’ll have to integrate Voice Chat (VoIP) if you want to enable voice chat in your app.
Note that this feature accesses user data and may require you to complete the Data Use Checkup form prior to submitting your app to the Oculus Store. For more information, see Complete a Data Use Checkup.
Oculus uses Rooms as a place for players to gather, these Rooms map to Sessions in Unreal. Oculus Rooms can be expressed in your app in multiple ways: user rooms, matchmaking rooms, and moderated rooms. We’ll discuss how to add matchmaking rooms in the next section, while moderated rooms are created by the server-to-server API calls defined on the Rooms page.
User rooms are not enqueued in the matchmaking service and can not later be promoted.
The following steps describe a basic Rooms integration.
The process to add matchmaking requires that you first create the matchmaking pools, then add the matchmaking service to your app. This guide will review some of the basics and background required for the Unreal integration, but we recommend that you review the complete native Matchmaking guide for a complete overview of the matchmaking service as well as how to create and manage Moderated Rooms.
There are different kinds of matchmaking that you can set up. Choose the multiplayer experience that you want your players to have.
System matches for 2-4 users that all join at the same time
Choose No for Should Pool Manage Rooms?. This means the system manages a pool of users looking for matches, and rooms are created for players once a match has been made. Simple Matchmaking is designed for 2-4 player games, like chess, checkers or tennis, where users don’t need the ability to join matches in progress. For more information how to set up simple matchmaking , see the Simple Matchmaking section of the Matchmaking How-to.
System matches for user-created rooms, and the ability to join/leave games in progress
Choose Yes for Should Pool Manage Rooms?, and both Users and System for Who can create rooms? This means the system manages a pool of users looking for matches and a list of rooms for that pool, where each room might have different matchmaking settings. You configure whether rooms are created by the user, by the matchmaking service, or both. Advanced matchmaking is designed for more complicated games with multiple match options, and where users may join, or leave, during the course of a match. For more information about how to set up an advanced match, see the Advanced Matchmaking section of the Matchmaking How-to.
System manages a pool of rooms that can be browsed by users.
Choose Yes for Should Pool Manage Rooms?, and Users for Who can create rooms?. This results in a pool of rooms. Users can create and host rooms or choose from a list of rooms to join. Browse also supports more complicated games with multiple match options and users may join and leave a match in progress. For more information about how to set up a browse scenario, see the Browse section of the Matchmaking How-to.
Before integrating Matchmaking, you’ll need to create your pools for users that want a match. Please see the Pools section of the Skill page for information about creating Matchmaking and skill components. Please note that the Data Settings and Matchmaking Queries described on that page are not available through the OSS interface.
The following steps describe a basic matchmaking integration.
StartMatchmaking()to enqueue the user in the Matchmaking service. Pass the key for the matchmaking pool you created to start matchmaking.
NewSessionSettings.Settingsas the key for the matchmaking pool you created and
NewSessionSettings.bShouldAdvertiseas true to enqueue the session in the Matchmaking service. If the user wants to remove the room from the Matchmaking service, call
Integrate Matchmaking - Browse
The following steps describe a basic browse matchmaking integration.
FindSessions()and pass the name of your matchmaking pool to retrieve a list of available sessions. Define
SearchSettingsif finding Matchmaking rooms or define
OCULUSMODERATEDROOMSONLYif using Moderated rooms.
NewSessionSettings.Settingsas the key of your matchmaking pool and
NewSessionSettings.bShouldAdvertiseas true to enqueue the session in the Matchmaking service. If the user wants to remove the room from the matchmaking service, call