This non-provisional application is based on Japanese Patent Application No. 2022-184964 filed on Nov. 18, 2022 with the Japan Patent Office, the entire contents of which are hereby incorporated by reference.
The present disclosure relates to an information processing program, a game system, a game device, and an information processing method.
In implementing multi-person play in a previous portable game console, a method of connecting portable game consoles to each other through a physical communication cable has been adopted in some cases. In such a communication game system, an operation to physically connect game consoles through a communication cable is substantially synonymous to participation of players in a game.
It is assumed that a game program executed in a conventional portable game console as described above is created on the premise that connection through a physical communication cable is established. Therefore, in an attempt to execute the game program with an emulator and to implement multi-person play over a network, an unexpected operation may occur. For example, participation/leave of a player corresponds to insertion and removal of a communication cable from a point of view of the game program, and participation/leave of a player at any timing during a game may cause an unexpected operation such as forced termination depending on specifications of the game program.
The present disclosure provides a scheme to suppress an unexpected operation such as forced termination even on the occurrence of cut-off of communication in implementation of multi-person play of a game program through communication.
According to Configuration 1, in execution with the emulator, of a game program for which data to be transmitted and received in multi-person play is defined, the defined data is transmitted and received not between/among the plurality of information processing apparatuses but between/among emulators generated in a single information processing apparatus. By adoption of such transmission and reception of data between/among the emulators, even on the occurrence of cut-off of communication with another information processing apparatus, processing can continue with operation information or the like being regarded as being absent, and hence execution of the game program is not forcibly terminated. Thus, even on the occurrence of cut-off of communication or the like, an unexpected operation such as forced termination can be suppressed. Since processing as described above is performed with the emulator generated in the information processing apparatus, the game program itself does not have to be modified.
According to Configuration 2, even when a game program (in the past) for which connection to/disconnection from another information processing apparatus during progress of multi-person play has not been assumed is executed with the emulator, multi-person play can normally be started and terminated while the game program itself remains the same without being modified.
According to Configuration 3, since the first emulator can be generated in the scene where the game program for play in multi-person play is selected, processing necessary for multi-person play can be performed in advance.
According to Configuration 4, even after the game program with which multi-person play is made is terminated, when multi-person play by the same players is desired again, the game program with which multi-person play is made can be selected by performing few operations.
According to Configuration 5, even after the game program with which multi-person play is made is terminated, the same players can immediately start multi-person play.
According to Configuration 7, even when a game program (in the past) for which connection to/disconnection from another information processing apparatus during progress of multi-person play has not been assumed is executed with the emulator, multi-person play can normally be started while the game program itself remains the same without being modified.
According to Configuration 8, even when a game program (in the past) for which connection to/disconnection from another information processing apparatus during progress of multi-person play has not been assumed is executed with the emulator, multi-person play can normally be terminated while the game program itself remains the same without being modified.
The foregoing and other objects, features, aspects and advantages of the present disclosure will become more apparent from the following detailed description of the present disclosure when taken in conjunction with the accompanying drawings.
The present embodiment will be described in detail with reference to the drawings. The same or corresponding elements in the drawings have the same reference characters allotted and description thereof will not be repeated.
[A. Exemplary Configuration of Game System]
An exemplary configuration of a game system according to the present embodiment will initially be described.
The game system includes one or more information processing apparatuses. Any hardware configuration of the information processing apparatus may be applicable so long as the information processing apparatus can execute a game program with an emulator. The information processing apparatus may be implemented, for example, by a game device, a smartphone, a tablet, a portable telephone, or a personal computer. An exemplary configuration where a game device 100 representing a computer is adopted will be described below by way of example of the information processing apparatus.
Each of game devices 100 can communicate with one or more other game devices 100. So long as data can mutually be exchanged between/among game devices 100, any communication method (wired and wireless) may be adopted in game system 1 shown in
In game system 1 shown in
In each of
In an example where game program 118 is adapted to multi-person play, each of game devices 100 communicates with another game device 100 and executes game program 118 adapted to multi-person play based on an operation input (provided by a player of each of game devices 100) with an emulator. Each of game devices 100 transmits data on the operation input to another game device 100.
“Multi-person play” herein means simultaneous play of the same game program by a plurality of players (users). Alternatively, “multi-person play” means participation of a plurality of players (users) in the same player group. Further alternatively, “multi-person play” means execution of game program 118 in each of game devices 100 based not only on information on an operation by a player of that game device 100 but also on information from another game device 100.
All game devices 100 may hold in advance game program 118 with any method. When there is game device 100 that does not hold game program 118, that game device 100 may download game program 118 from game device 100 that holds game program 118.
Alternatively, at least one game device 100 or all game devices 100 may download game program 118 as appropriate from a server (not shown) or the like.
[B. Exemplary Hardware Configuration]
An exemplary hardware configuration of game device 100 included in game system 1 according to the present embodiment will now be described.
Processor 102 is a processing entity for performing processing provided by game device 100. Processor 102 executes a program stored in storage 110 by sequentially developing a necessary part thereof on memory 104.
Memory 104 is a volatile storage device (storage medium) that can be accessed by processor 102, and it may be implemented, for example, by a dynamic random access memory (DRAM) or a static random access memory (SRAM).
Storage 110 is a non-volatile storage device (storage medium) that can be accessed by processor 102, and it may be implemented, for example, by a hard disk or a solid state drive (SSD). Storage 110 may be, for example, a storage medium attachable to and removable from game device 100 such as an optical disc or a cartridge.
A system program 112, an execution management program 114, and an emulator program 116 are stored in storage 110.
System program 112 includes a computer-readable instruction for having processor 102 perform basic processing necessary for functioning as game device 100.
Execution management program 114 includes a computer-readable instruction for having processor 102 execute game program 118 with an emulator.
Emulator program 116 includes a computer-readable instruction for having processor 102 virtually set up an environment for execution of game program 118.
An “information processing program” according to the present embodiment includes at least execution management program 114. The “information processing program” may include system program 112 and/or emulator program 116. How a program is implemented is a matter of design and can be determined as appropriate in accordance with required performance and restrictions.
One or more game programs 118 may be stored in storage 110 or downloaded as appropriate from a server or the like in response to a request from a player. In this case, the game program does not have to be stored in storage 110, although it is developed on memory 104 only while it is executed.
By way of example, game program 118 is a program created to be executed in a game device (for example, a game device in the past developed prior to game device 100) different from game device 100. Even in execution of game program 118 by game device 100, it may remain original. In other words, game program 118 does not have to be modified for being executed with the emulator of game device 100.
App data 130 generated as a result of execution of game program 118 may be stored in storage 110.
Display 106 shows a game screen generated as a result of information processing by processor 102. A plurality of displays 106 may be provided. Game device 100 may be configured to use one or more external displays.
Operation portion 108 accepts an operation input from a player of game device 100. Operation portion 108 includes, for example, a push button, a control lever, a touch panel, a mouse, and/or the like. Operation portion 108 may be implemented by a game controller which is separate from game device 100 and connected through a wire or wirelessly.
Communication unit 120 communicates with another game device 100. Communication unit 120 may include hardware necessary for wired communication and/or hardware necessary for wireless communication. The entirety or a part of processing by communication unit 120 may be performed by processor 102.
Though
At least a part of processing performed in game device 100 may be performed discretely by one or more other apparatuses arranged as being distributed over a network.
Processing performed in game device 100 may be implemented by execution of a program by processor 102, and a part or the entirety of the processing may be implemented by hard-wired circuitry such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). Therefore, the term “processor” herein encompasses not only an ordinary meaning of a processing circuit that performs processing in accordance with a computer-readable instruction described in a program, such as a central processing unit (CPU), a micro processing unit (MPU), or a graphics processing unit (GPU), but also hard-wired circuitry such as an ASIC or an FPGA. In the hard-wired circuitry such as an ASIC or an FPGA, circuitry corresponding to processing to be executed is formed in advance. Furthermore, the “processor” herein also encompasses circuitry in which a plurality of functions are integrated, such as a system on chip (SoC).
[C. Exemplary Functional Configuration]
An exemplary functional configuration of game device 100 included in game system 1 according to the present embodiment will now be described.
Execution management module 124 performs such processing as selection of game program 118 to be executed with emulator 126, management of execution of selected game program 118 with emulator 126, exchange of player operation information and shared data, and output of a game screen.
Execution management module 124 obtains data on an operation input provided from a player (player operation information 150) onto operation portion 108 of the player's device and provides the data to emulator 126. Execution management module 124 outputs a game screen obtained as a result of execution of game program 118 with emulator 126 to display 106. In addition, execution management module 124 may output from a speaker (not shown), voice and sound obtained as a result of execution of game program 118 with emulator 126.
Emulator 126 is a virtual environment for execution of game program 118, and it receives player operation information 150 and outputs a game screen and voice and sound as a result of execution. Emulator 126 exchanges shared data 142 with another emulator 126. Shared data 142 corresponds to data exchanged through a physical communication cable by a previous portable game console. Shared data 142 is defined as data transmitted and received in multi-person play of game program 118. Shared data 142 includes information necessary for implementation of multi-person play and includes, for example, a coordinate of a character or an instruction for an action.
Emulator 126 includes a virtual save area 128 for game program 118 to have data saved. Virtual save area 128 behaves like an inherent save area from a point of view of game program 118. Though virtual save area 128 itself may be implemented on memory 104, saved data (app data) may be stored in storage 110 (for example, app data 130 in
In game system 1 according to the present embodiment, emulators 126 can establish connection that simulates a physical communication cable.
Emulator 126 exchanges with another emulator 126 through connection 140, shared data 142 that has been exchanged through a physical communication cable by a previous portable game console. By establishing connection 140, from a point of view of game program 118, an environment similar to that of a plurality of portable game consoles connected through a physical communication cable can be provided.
Instead of the exemplary functional configuration shown in
Referring to
Emulators 126-1 to 126-4 require data (player operation information 150-1 to 150-4) on operation inputs provided by respective players to operation portions 108 of respective game devices 100-1 to 100-4. Therefore, each game device 100 transmits an operation input (player operation information 150) provided by the player to another game device 100 and receives an operation input (player operation information 150) provided by another player onto another game device 100. Player operation information 150-1 to 150-4 shown in
In the example shown in
Player operation information 150-1 to 150-4 is provided to emulators 126-1 to 126-4, respectively. Emulators 126-1 to 126-4 execute game program 118 based on player operation information 150-1 to 150-4, respectively.
Emulators 126-1 to 126-4 are independent of one another. Emulators 126-1 to 126-4 establish connections 144 that simulate a communication cable by means of execution management module 124. Connection 144 refers to a virtual or logical data transmission channel similarly to connection 140 shown in
Execution management module 124 can output to display 106, a game screen resulting from execution of game program 118 with each of emulators 126-1 to 126-4. Normally, a game screen generated by emulator 126 corresponding to a device to which it belongs (for example, emulator 126-1 for game device 100-1) is outputted to display 106.
When an instruction for screen sharing is given in at least one game device 100 as will be described later, however, the game screen generated by game device 100 (emulator 126) where the instruction has been given may be outputted.
Data (player operation information 150-1) on an operation input provided by the player of game device 100-1 onto operation portion 108 of game device 100-1 is inputted to emulator 126-1 of each of game devices 100-1 to 100-4.
Similarly, data (player operation information 150-2) on an operation input provided by the player of game device 100-2 onto operation portion 108 of game device 100-2 is inputted to emulator 126-2 of each of game devices 100-1 to 100-4.
Similarly, data (player operation information 150-3) on an operation input provided by the player of game device 100-3 onto operation portion 108 of game device 100-3 is inputted to emulator 126-3 of each of game devices 100-1 to 100-4.
Similarly, data (player operation information 150-4) on an operation input provided by the player of game device 100-4 onto operation portion 108 of game device 100-4 is inputted to emulator 126-4 of each of game devices 100-1 to 100-4.
In a normal state, each of game devices 100-1 to 100-4 outputs to display 106, a game screen generated by emulator 126 corresponding thereto.
As player operation information 150-1 to 150-4 is inputted to respective emulators 126-1 to 126-4 in each of game devices 100-1 to 100-4, multi-person play is implemented in each of game devices 100-1 to 100-4.
Thus, each of game devices 100-1 to 100-4 executes with the emulator corresponding thereto, game program 118 adapted to multi-person play based on an operation input, and transmits data on the operation input (player operation information 150) to another game device 100. An image of a game (game screen) executed with the emulator corresponding to one game device is outputted to display 106 thereof. Concurrently, each of game devices 100-1 to 104 obtains data on an operation input by another player (player operation information 150) from another game device and executes with the emulator corresponding to another game device, game program 118 based on the obtained operation input by another player. Furthermore, as data (shared data 142) defined as data to be transmitted and received in multi-person play of game program 118 is transmitted and received between the emulator corresponding to one game device and the emulator corresponding to another game device, multi-person play of the game proceeds.
As the configuration as shown in
Though
[D. Player Operation Information]
In the exemplary configuration shown in
For example, in an example where delay in communication of player operation information 150 is unignorable, information that allows identification of operation timing may be added to player operation information 150.
Referring to
Frame number 152 is a number representing a cycle where game program 118 is executed with emulator 126.
Each emulator 126 determines timing to obtain corresponding operation contents 154 during execution of game program 118, based on frame number 152 included in player operation information 150. Execution management module 124 and/or emulator 126 may include a buffer where player operation information 150 is temporarily stored.
As player operation information 150 includes frame number 152, such a situation that contents of multi-person play that proceeds between/among game devices 100 are inconsistent can be avoided even on the occurrence of delay in communication.
Though an exemplary configuration in which frame number 152 is used is described by way of example, any information may be added so long as the information allows identification of timing of operation by a player. For example, information on time or a counter value may be added.
Furthermore, consistency of contents in multi-person play that proceeds between/among game devices 100 may regularly be checked. For example, with game device 100 that operates as a host being defined as the reference, whether or not a current state in multi-person play on game device 100 that operates as a guest are consistent with a current state in multi-person play on the host may regularly be determined. When the contents are inconsistent, a value on the memory or the like may be corrected as appropriate for consistency with game device 100 that operates as the host. The “host” and the “guest” will be described later.
[E. Exemplary Processing Procedure in Execution of Game Program]
An exemplary processing procedure in execution of game program 118 by game device 100 included in game system 1 according to the present embodiment will now be described.
In connection with game program 118 adapted to multi-person play, a plurality of players simultaneously participate. Therefore, for game device 100, by way of example, selection between two modes of a “host” that calls for participation in multi-person play and a “guest” that participates in response to a call from the “host” can be made.
Referring to
Referring again to
Processing in steps S102 to S116 corresponds to a scene in which game program 118 adapted to multi-person play is selected. Only game program 118 adapted to multi-person play may be shown on display 106, or game program 118 not adapted to multi-person play may also be shown. In the latter case, a manner of representation may be different such that a player can distinguish whether or not a game can be played by multiple persons.
Game device 100 generates emulator 126 in the scene where game program 118 adapted to multi-person play is selected (step S104). In other words, the scene where execution of game program 118 with emulator 126 is started may be a scene where selection as to which of a plurality of game programs 118 is to be started is made.
After step S104 is performed, game device 100 operates as the host, and hence it waits for a request for participation from another player. For example, when another game device 100 issues a request for participation of another player (who operates another game device 100) in multi-person play based on communication, game device 100 allows another player to participate in multi-person play so long as timing of request is before start of execution of game program 118, such as timing immediately after step S104.
More specifically, when game device 100 receives the request for participation from another player (YES in step S106), it shares a screen showing a list of executable game programs 118 with another game device 100 that has transmitted the request for participation (step S108). Game device 100 additionally generates emulator 126 corresponding to game device 100 that has transmitted the request for participation and establishes connection 144 that simulates the communication cable between generated emulators 126 (step S110)
Though not clearly shown in
Game device 100 with which the screen showing the list of executable game programs 118 is shared becomes game device 100 that participates in multi-person play. The screen showing the list may be shared by transmission of screen data itself from the host to the guest or generation of the screen showing the list in each of game devices 100 that function as the guests upon reception of information on selection of game program 118 from the host.
The player as the host can select game program 118 to be executed, by performing an operation for selection in user interface screen 210. An object 216 indicating selection is shown as being superimposed on selected game program 118.
Referring again to
Game device 100 is in a state in which it waits for selection of game program 118 by the player who operates game device 100 itself. When the player selects a game program 118 (YES in step S112), game device 100 shows an object for identifying selected game program 118 (step S114). Game device 100 that operates as the host thus selects one of game programs 118 adapted to multi-person play in response to an operation by the player. In other words, game program 118 adapted to multi-person play that is to be executed may be one of a plurality of game programs 118 adapted to multi-person play.
When the player has selected none of game programs 118 (NO in step S112), processing in step S114 is skipped.
In succession, game device 100 determines whether or not it is instructed to start execution of game program 118 (step S116). When the game device is not instructed to start execution of game program 118 (NO in step S116), processing in step S106 and later is repeated.
When game device 100 is instructed to start execution of game program 118 (YES in step S116), processing in step S118 and later is performed. In step S118, game device 100 proceeds with multi-person play of game program 118 with emulator 126 based on communication between/among game devices 100 of players who participate in multi-person play.
On the other hand, when game device 100 is instructed to operate as the guest (“guest” in step S100) by a player, it shows on display 106, a list of another game device 100 that operates as the host and a corresponding player (step S120). Game device 100 then waits for selection of another game device 100 (or a corresponding player) by the player who operates game device 100.
When the player selects another game device 100 (or a corresponding player) (YES in step S122), game device 100 determines whether or not game program 118 is being executed in selected game device 100 (step S124).
When game program 118 is being executed in selected game device 100 (YES in step S124), a message that game program 118 is being executed is shown (step S126). Processing in step S124 and later is then repeated.
Game device 100 that operates as the host thus allows, when another game device 100 (that operates as the guest) issues a request for participation of another player in multi-person play, a state that another player has not participated in multi-person play to continue while game program 118 is being executed. Game device 100 that operates as the guest provides, when it transmits the request for participation in multi-person play to another game device 100 (that operates as the host), representation (user interface screen 220) for having the player wait for play until it is allowed by another game device 100 to participate in multi-person play. With such representation, the player can be prevented from losing a motivation to participate in multi-person play.
Referring again to
Game device 100 that operates as the host thus allows, when another game device 100 (that operates as the guest) issues a request for participation of another player in multi-person play and transition to a scene where execution of game program 118 with emulator 126 is started has been made (NO in step S124), another player to participate in multi-person play. In processing in step S124, communication between game device 100 that operates as the host and game device 100 that operates as the guest is maintained. The number of emulators 126 generated in each of game devices 100 varies with variation in number of players (game devices 100) who participate in multi-person play. Therefore, when another player participates in multi-person play, in each of game devices 100, multi-person play based on the emulator corresponding to that game device 100 and the emulator corresponding to another game device is made.
In succession, game device 100 determines whether or not it is instructed to start execution of game program 118 (step S132). When the game device is not instructed to start execution of game program 118 (NO in step S132), processing in step S132 and later is repeated.
When the game device is instructed to start execution of game program 118 (YES in step S132), processing in step S118 and later is performed.
In step S118, game device 100 starts execution of selected game program 118 with generated emulator 126. In other words, in game device 100, all generated emulators 126 (as many as the players who participate in multi-person play) each start execution of game program 118. Each of game devices 100 that participate in multi-person play starts execution of game program 118.
Referring to
When the player has not operated operation portion 108 (NO in step S140), processing in step S142 is skipped.
Game device 100 then determines whether or not it has received player operation information 150 from another game device 100 (step S144). When game device 100 has received player operation information 150 from another game device 100 (YES in step S144), received player operation information 150 is stored in game device 100 (step S146). Game device 100 thus obtains from another game device 100, player operation information 150 indicating an operation input by another player. The number of other game devices 100 to which player operation information 150 is transmitted and from which player operation information 150 is obtained varies depending on the number of players who participate in multi-person play.
When the game device has not received player operation information 150 from another game device 100 (NO in step S144), processing in step S146 is skipped.
Game device 100 executes game program 118 with each emulator 126 based on the player operation information and shared data 142 (step S148). More specifically, game device 100 executes game program 118 with emulator 126 corresponding to game device 100 itself, based on the operation by the player onto game device 100 itself. Concurrently, game device 100 executes game program 118 with each emulator 126 corresponding to another game device 100, based on player operation information 150 obtained from another game device 100.
Game device 100 transmits and receives shared data 142 between emulators 126 based on a result of execution with each emulator 126 (step S150). Game device 100 thus proceeds with multi-person play by transmitting and receiving (or updating) shared data 142 between emulator 126 corresponding to game device 100 itself and emulator 126 corresponding to another game device 100.
Game device 100 outputs to display 106, a game screen obtained as a result of execution of game program 118 with emulator 126 (step S152). Normally, game device 100 outputs to display 106, an image (game screen) of game program 118 executed with emulator 126 corresponding to game device 100 itself.
Each of game devices 100 thus executes game program 118 adapted to multi-person play with a plurality of emulators 126 while it communicates with another game device 100.
Referring to
When screen sharing is instructed in at least one game device 100 (YES in step S160), game device 100 shows thereon, a game screen shown on game device 100 where the instruction for screen sharing has been given (step S162). Details of processing involved with screen sharing will be described later. When screen sharing is not instructed (NO in step S160), processing in step S162 is skipped.
Game device 100 determines whether or not an instruction to prematurely terminate game program 118 has been given in at least one game device 100 that participates in multi-person play (step S164). More specifically, each of game devices 100 determines whether or not it is instructed to terminate game program 118 and whether or not it has received a request to terminate game program 118 from another player through communication.
When game device 100 has not been instructed to prematurely terminate game program 118 (NO in step S164), it determines whether or not execution of game program 118 has been completed (step S166). When execution of game program 118 has not been completed (NO in step S166), execution of game program 118 continues and processing in step S160 and later is repeated.
When execution of game program 118 has been completed (YES in step S166), the process returns to step S106.
When the instruction to prematurely terminate game program 118 has been given (YES in step S164), processing as in steps S168 and S170 is performed.
More specifically, game device 100 temporarily suspends execution of game program 18 in emulator 126 (step S168) and shows a screen for obtaining agreement to premature termination of game program 118 (step S170). Game device 100 is thus in a state that it waits for an operation input from each player who participates in multi-person play.
In play-by-player representations 233 and 234 of other players CCC (3P) and DDD (4P), state representations 237 and 238 showing what is selected by each player are given.
Referring again to
Thus, during multi-person play, when game device 100 is instructed to quit the game (by the player thereof) or when game device 100 receives a request to quit the game from another player based on communication, game device 100 thus temporarily suspends the game, and when game devices 100 of all players who participate in multi-person play give instructions to quit the game, game device 100 terminates game program 118.
Game device 100 then makes transition to a scene for selection of game program 118 adapted to multi-person play. In other words, when game devices 100 of all players who participate in multi-person play give the instruction to quit the game and game program 118 is terminated, game device makes transition to the scene where selection as to which of the plurality of game programs 118 is to be started is made.
Since emulator 126 and connection 140 are maintained in each of game devices 100, also after transition to the scene for selection of game program 118 adapted to multi-person play, players who have participated in multi-person play of terminated game program 118 are maintained in a state that they are able to participate in multi-person play. In other words, when game devices 100 of all players who participate in multi-person play give the instruction to quit the game and game program 118 is terminated, game device 100 makes transition to the scene for making selection as to which of the plurality of game program 118 is to be started, with the state that players have participated in multi-person play being maintained.
In contrast, unless all players who participate in multi-person play agree to premature termination of execution of game program 118 (NO in step S172), execution of game program 118 is resumed and continues, and processing in step S140 and later is repeated.
[F. Modification of Processing Procedure in Execution of Game Program]
In the processing procedure shown in
When data does not have to be saved, execution of game program 118 may prematurely be terminated without agreement by all players. In this case, processing in step S170 in
[G. Screen Sharing]
Processing involved with screen sharing (step S162 in
Game device 100 may select the screen sharing mode as shown in
Referring to
In the example shown in
In each of game devices 100, game program 118 is executed with emulator 126 corresponding to another game device 100. Therefore, a game screen generated by emulator 126 corresponding to game device 100, screen sharing with which has been instructed, is additionally outputted. Therefore, game devices 100 do not have to transmit and receive the game screen itself therebetween/thereamong.
In game system 1 according to the present embodiment, players can participate in multi-person play even though they are distant from each other unlike the example where the conventional physical communication cable is used. In multi-person play by the players located at remote locations, however, the players are unable to show game screens to each other. In order to address such a problem, by providing the screen sharing mode, even when a plurality of players participate in multi-person play while they are physically distant from each other, they can mutually know statuses of the game.
[H. Advantage]
According to the present embodiment, a scheme to suppress an unexpected operation such as forced termination even on the occurrence of cut-off of communication in implementation through communication, of multi-person play of a game program (in the past) not intended for multi-person play through communication is provided.
While certain example systems, methods, devices and apparatuses have been described herein, it is to be understood that the appended claims are not to be limited to the systems, methods, devices and apparatuses disclosed, but on the contrary, are intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.
Number | Date | Country | Kind |
---|---|---|---|
2022-184964 | Nov 2022 | JP | national |