Multiplayer Game Logic Isolation for Host Crash Resilience
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional multiplayer game systems face issues with centralized server capacity, reliability of user-maintained servers, and instability in peer-to-peer models due to game crashes and player disconnection.
Innovation Solution
Implementing a dual-process scheme in multiplayer games, where gameplay logic and output are separated into distinct processes, with the gameplay logic managing game state and inputs/outputs handled separately, enabling robust peer-to-peer gameplay even with host device instability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a centralized server model is used to coordinate multiplayer games, then game state management and coordination are reliable and consistent, but server capacity becomes a bottleneck when the game proves very popular
Solution Approach 1:
The patent segments the centralized server functionality by introducing dedicated server tools that allow individuals to run independent server instances. This divides the monolithic server capacity into multiple distributed segments, each handling a portion of the player base, thereby scaling productivity while maintaining centralized coordination reliability through consistent game logic execution on each segment.
Solution Approach 2:
The patent introduces dedicated server tools as an intermediary layer between players and the game logic. These tools act as mediators that standardize server deployment and management, allowing reliable game state coordination to be distributed across multiple independent server instances rather than requiring a single centralized server, thus resolving the capacity bottleneck.
2Productivity
If user-maintained servers are used to increase server capacity and reduce centralization, then scalability improves, but reliability and security decrease due to lack of professional maintenance and updates
Solution Approach 1:
The patent enables self-service through automated dedicated server tools that allow individuals to easily set up, configure, and maintain server instances without requiring professional game server expertise. The tools provide pre-configured game logic, automated updates, and standardized deployment procedures, enabling users to self-manage servers reliably while maintaining scalability through distributed instances.
Solution Approach 2:
The patent changes the parameter of server maintenance from requiring professional expertise to being accessible to ordinary users through simplified tooling. By transforming the complexity parameter and providing user-friendly interfaces for server management, the system enables reliable maintenance across distributed user-maintained servers while preserving scalability.
3Productivity
If peer-to-peer multiplayer architecture is used to eliminate centralized servers, then server capacity constraints are removed, but stability decreases due to game crashes and player disconnections affecting the host
Solution Approach 1:
The patent extracts the game logic execution from the host player's device by implementing a dedicated server model where an independent server instance runs the authoritative game logic. This separation removes the instability caused by host device crashes and disconnections from the peer-to-peer architecture, allowing the game logic to continue running reliably on the dedicated server while players connect as clients, thus resolving the stability issue while maintaining distributed capacity.
Data Source
AI summary
A method of operating a multiplayer game comprises the steps of, on a host device, running the multiplayer game configured as two separate processes, the first process being a gameplay logic application that manages progress of the game according to the game's rules; and the second process being a gameplay output application that manages the presentation of the game to a user at their device; wherein the gameplay logic application is operable to manage progress of the multiplayer game for a plurality of users, detecting if the gameplay output application stops normal operation whilst the gameplay logic application is managing progress of the multiplayer game for at least a predetermined number of other users of remote devices, and if so, continuing to operate the gameplay logic application despite the stopping of the other part of the same multiplayer game on the host device.