Methods and systems for cross-platform multiplayer session share
Methods and systems are provided for processing gameplay invitations are provided. The method includes receiving a request from a first player to share gameplay of a game during a session of gameplay with a recipient. The method includes generating, responsive to the request, a share link for sending to the recipient. The share link includes embedded metadata that identifies an application identifier for the game and a session identifier for the session of gameplay by the first player. The share link forwards the recipient to a web user interface (UI) that enables input of a selection of a platform system from which the recipient is to join the session. The input at the web UI redirects to a trigger link that starts a launch invocation of the platform system and passes the game identifier and the session identifier to the platform system to initiate gameplay of the recipient in the session of gameplay of the first player.
1 . A method for processing gameplay invitations, comprising:
receiving an indication of a request for a first player device to share gameplay of a game during a session of gameplay with a recipient device; and
generating, responsive to the request, a share link for sending to the recipient device, the share link including embedded metadata that identifies an application identifier for the game and a session identifier for the session of gameplay by the first player device;
wherein the share link comprises a system type-agnostic universal resource link that is invariant with respect to different system types and different recipients and the recipient device causes presentation of a network-served web user interface that enables input of a selection of a system type from a plurality of heterogeneous system types from which the recipient device is to join the session; and
responsive to the input, redirecting to a system type-specific trigger link that starts a launch invocation of the selected system type and passes the application identifier and the session identifier to initiate gameplay for the recipient device in the session of gameplay.
2 . The method of claim 1 , wherein the session of gameplay by the first player device uses a first system type and the system type of the recipient device is a second system type that is different from the first system type.
3 . The method of claim 2 , wherein the share link is sharable with third parties without restriction to being designated as friends on the first system type or the second system type.
4 . The method of claim 1 , wherein the share link is re-sharable by the recipient device or another device that receives the share link to join the session of gameplay of the game, wherein the share link maintains the metadata regarding the application identifier for the game and the session identifier for the session of gameplay by the first player device.
5 . The method of claim 1 , wherein the session is a multiplayer session.
6 . The method of claim 1 , wherein the indication of the request is received via a user interface of a first system type used by the first player device, the request is configured to generate a code that can be visually detected by a mobile device for sending to the recipient device via a message transmitted using the mobile device.
7 . The method of claim 1 , wherein the system type is automatically selected for the recipient device based on a user profile associated with the recipient device.
8 . The method of claim 1 , wherein a message is used to send the share link, the share link identifies telemetry insight data regarding players active in the session, the session being a multiplayer session.
9 . The method of claim 1 , wherein the application identifier is associated with coded system type options that identify a set of system types the game enables using the share link, wherein a backend system of a first system type used by a first player has the game registered with the application identifier.
10 . The method of claim 1 , wherein the launch invocation is a URL-based game launch.
11 . The method of claim 1 , wherein a game server executing the game is configured to receive the request from the first player device to share the gameplay of the game during the session, the game server is configured to get a credentials token responsive to an indication received by the recipient device that the share link was selected and a session manager is configured to associate the recipient device with the session using the credentials token.
12 . The method of claim 1 , wherein the web user interface displays, prior to the selection, real time session metadata identifying current participants and available capacity for the session.
13 . The method of claim 1 , wherein the system type-specific trigger link is a signed, single use link that expires after a predefined time interval.
14 . A system for processing gameplay invitations, the system including one or more servers for executing online multi-player gaming, comprising:
a server receiving an indication of a request for a first player device to share gameplay of a game during a session of gameplay with a recipient device; and
the server generating a share link for sending to the recipient device, the share link including embedded metadata that identifies an application identifier for the game and a session identifier for the session of gameplay by the first player device;
wherein the share link comprises a system type-agnostic universal resource link that is invariant with respect to different system types and different recipients and, when selected on the recipient device, causes presentation of a network-served web user interface that enables input of a selection of a system type from a plurality of heterogeneous system types from which the recipient device is to join the session; and
wherein the server, responsive to the input at the web user interface, redirects to a system type-specific trigger link that that starts a launch invocation of the selected system type and passes the application identifier and the session identifier to initiate gameplay for the recipient device in the session of gameplay.
15 . The system of claim 14 , wherein the session of gameplay by the first player device uses a first system type and the system type of the recipient device is a second system type that is different from the first system type.
16 . The system of claim 14 , wherein the indication of the request is received via a user interface of a first system type used by the first player device, the request is configured to generate a code that can be visually detected by a mobile device for sending to the recipient device via a message transmitted using the mobile device.
17 . The system of claim 14 , wherein the system type is automatically selected for the recipient device based on a user profile associated with the recipient device.
18 . The system of claim 14 , wherein a message is used to send the share link, the share link identifies telemetry insight data regarding players active in the session, the session being a multiplayer session.
19 . The system of claim 14 , wherein the server is associated with a game server executing the game for the first player device and is configured to receive the request from the first player device to share the gameplay of the game during the session, the game server is configured to get a credentials token responsive to an indication received by the recipient device that the share link was selected and a session manager is configured to associate the recipient device with the session using the credentials token.
20 . The system of claim 14 , wherein the server hosts a landing page reachable via the universal resource link, the landing page listing at least three heterogeneous system types and, responsive to recipient selection, constructing the system type-specific trigger link that passes the application identifier and the session identifier.