US 12,303,791 B1
Integration of game features across varied hosting topologies
Christopher Byskal, Redmond, WA (US); Christopher Lee, Bellevue, WA (US); Toufeeq Hussain, San Francisco, CA (US); Raymond H. Kelm, Snohomish, WA (US); Nick Roldan Delos Santos, Cerritos, CA (US); David G. Marsee, Renton, WA (US); Jeffery Blaine Petersen, San Diego, CA (US); and Henry Liang Goffin, Seattle, WA (US)
Assigned to Amazon Technologies, Inc., Seattle, WA (US)
Filed by Amazon Technologies, Inc., Seattle, WA (US)
Filed on Dec. 16, 2022, as Appl. No. 18/067,103.
Int. Cl. A63F 13/79 (2014.01); A63F 13/30 (2014.01); A63F 13/358 (2014.01); A63F 13/50 (2014.01); H04L 67/131 (2022.01)
CPC A63F 13/79 (2014.09) [A63F 13/30 (2014.09); A63F 13/358 (2014.09); A63F 13/50 (2014.09); H04L 67/131 (2022.05)] 20 Claims
OG exemplary drawing
 
1. A computing system comprising:
one or more processors; and
one or more memories having stored therein instructions that, upon execution by the one or more processors, cause the computing system to perform computing operations comprising:
registering, based on a first request of an application programming interface (API) of a game feature integration service, a first video game feature component with an event bus of the game feature integration service;
registering, based on a second request of the API of the game feature integration service, a second video game feature component with the event bus;
receiving, via the API of the game feature integration service, event indications of a plurality of events for which the first video game feature component is designated to send event notifications to the game feature integration service;
receiving, via the API of the game feature integration service, action indications of a plurality of actions that are designated for the game feature integration service to call on the second video game feature component;
receiving a rule flow that triggers the game feature integration service to call a first action of the plurality of actions based on a notification of a first event of the plurality of events;
receiving, by the event bus, from the first video game feature component, via the API of the game feature integration service, the notification of the first event; and
calling, by the game feature integration service, based at least in part on the first and the second requests and the rule flow, the first action on the second video game feature component in response to the notification of the first event.