Program, information processing device, and information processing device control method

Abstract

A program, an information processing device, and a method for controlling an information processing device are provided that improve the interface environment used in a game in which players engage in battles with each other. A viewing function is provided that allows viewing permissions related to battles between players belonging to a battle group to be set in response to a request from a terminal of a player acting as an organizer, and allows viewing of the battles between players according to the settings related to the viewing permissions. A viewing permission setting unit can set viewing permissions that prevent viewing of the battles between players belonging to the battle group from being performed by terminals of players who are neither the organizer nor the player engaging in the battle, but allows viewing via the terminal of the player registered as the organizer.

Description

Technical Field

[0001] The present invention relates to a program for players to battle each other, an information processing device, and a method for controlling the information processing device. Background Art

[0002] Conventionally, there are well-known programs for executing games that implement a tournament function, which allows players to battle each other using terminals connected to each other via a communication line with a player acting as an organizer. Some of these existing tournament functions also implement a viewing function that allows the progress of the battle between players to be viewed on the terminal screen. However, this viewing function for player-organized tournaments only allows the user to set whether to enable or disable battle viewing (see Patent Document 1).

[0003] Prior art literature

[0004] Patent Literature

[0005] Patent Document 1: Japanese Patent Application Laid-Open No. 2019-72245 Summary of the Invention

[0006] Inventing the Problem to End

[0007] However, when a spectator function is implemented in a game (so-called TCG) in which players battle each other using a game medium decorated with a trading card theme, participants who are also able to spectate the battle may make it difficult to ensure fairness in the battle because there is a risk that participants who are people other than the players will master the deck construction and the players' unique tactics. For this reason, an interface environment that can provide an appropriate spectator function is needed.

[0008] The present invention has been conceived in view of the above-described circumstances, and an object thereof is to provide a program, an information processing device, and a method for controlling an information processing device that can improve an interface environment for a game in which players battle each other.

[0009] Solutions for ending the problem

[0010] (1) The present invention relates to a program for a game in which players fight each other, the program causing a computer to function as: a group generating unit for generating a battle group in which the player is registered as the organizer in response to a request from a terminal of a player serving as an organizer; a player registering unit for registering a plurality of players in the battle group in response to requests from terminals of a plurality of players different from the organizer; a viewing authority setting unit for setting viewing authority related to a battle between players belonging to the battle group in response to a request from a terminal of the player serving as the organizer; and a viewing function providing unit for providing a viewing function that allows viewing of the battle between players according to the setting content related to the viewing authority, wherein the viewing authority setting unit is capable of setting the following viewing authority, with which the battle between players belonging to the battle group cannot be viewed at a terminal of a player who is neither the organizer nor the player who conducts the battle, but can be viewed via a terminal of the player registered as the organizer.

[0011] (2) In the program according to the present invention, at the terminals of the respective players engaging in battle, it is necessary not to disclose information related to a part of the game media used by the player serving as the opponent, and the viewing function providing unit can provide the viewing function so that the battle between the players can be viewed at the terminal of the player having the viewing authority, which terminal discloses information related to the game media that is not disclosed to the players engaging in battle with each other.

[0012] (3) In the program according to the present invention, the viewing authority setting unit may be capable of setting the following viewing authority, with which the battle between the players belonging to the battle group can be viewed not only via the terminal of the player registered as the organizer, but also via the terminal of the player who is neither the organizer nor the player conducting the battle.

[0013] (4) The present invention relates to an information processing device for a game in which players fight each other, the information processing device comprising: a group generating unit for generating a battle group in which the player is registered as the organizer in response to a request from a terminal of a player serving as an organizer; a player registering unit for registering the multiple players in the battle group in response to requests from terminals of multiple players different from the organizer; a viewing authority setting unit for setting viewing authority related to battles between players belonging to the battle group in response to a request from a terminal of the player serving as the organizer; and a viewing function providing unit for providing a viewing function that allows viewing of battles between players according to setting content related to the viewing authority, wherein the viewing authority setting unit is capable of setting the following viewing authority, with which the battles between players belonging to the battle group cannot be viewed at the terminal of a player who is neither the organizer nor the player conducting the battle, but can be viewed via the terminal of the player registered as the organizer.

[0014] (5) The present invention relates to a control method for an information processing device used for a game in which players fight each other, the control method comprising: a group generating step for generating a battle group in which the player is registered as the organizer in response to a request from a terminal of a player serving as an organizer; a player registering step for registering the multiple players in the battle group in response to requests from terminals of multiple players different from the organizer; a viewing authority setting step for setting viewing authority related to battles between players belonging to the battle group in response to a request from a terminal of the player serving as the organizer; and a viewing function providing step for providing a viewing function that allows viewing of battles between players according to setting contents related to the viewing authority, wherein, in the viewing authority setting step, it is possible to set a viewing authority with which the battles between players belonging to the battle group cannot be viewed at a terminal of a player who is neither the organizer nor the player conducting the battle, but can be viewed via a terminal of the player registered as the organizer.

[0015] Effects of the Invention

[0016] In the above-described program, information processing device, and method for controlling an information processing device, viewing permissions can be set so that battles between players in a battle group can be viewed via the terminal of a player registered as the organizer, but cannot be viewed from the terminal of a player who is neither the registered organizer nor the player conducting the battle. This enables appropriate management of battle groups while still maintaining fairness between players, thereby enhancing the interface environment used for games in which players battle each other. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 It is a diagram showing the overall structure of the information processing system.

[0018] Figure 2 This is a functional block diagram related to a function for allowing viewing of a battle between players, among functions implemented by the information processing system.

[0019] Figure 3 is a flowchart illustrating an example of processing performed in the information processing system.

[0020] Figure 4 2 is a diagram showing an example of a battle mode selection screen displayed on a player terminal.

[0021] Figure 5 1 is a diagram showing an example of a hosting / participation selection screen displayed on a player terminal.

[0022] Figure 6 is a diagram showing an example of a competition information setting screen displayed on a player terminal.

[0023] Figure 7 is a diagram showing an example of items that can be set for competition information.

[0024] Figure 8 2 is a diagram showing an example of a competition registration completion screen displayed on a player terminal.

[0025] Figure 9 is a diagram showing an example of a competition top screen displayed on a player terminal.

[0026] Figure 10 2 is a diagram showing an example of a battle mode selection screen displayed on a player terminal.

[0027] Figure 11 2 is a diagram showing an example of a battle mode selection screen displayed on a player terminal.

[0028] Figure 12 is a flowchart illustrating an example of processing performed in the information processing system.

[0029] Figure 13 is a diagram showing an example of a competition search screen displayed on a player terminal.

[0030] Figure 14 is a diagram showing an example of a competition search screen displayed on a player terminal.

[0031] Figure 15 2 is a diagram showing an example of a competition participation confirmation screen displayed on a player terminal.

[0032] Figure 16: is a diagram showing an example of a search error screen displayed on a player terminal.

[0033] Figure 17 2 is a diagram showing an example of a card pile registration screen displayed on a player terminal.

[0034] Figure 18 2 is a diagram showing an example of a registration confirmation screen displayed on a player terminal.

[0035] Figure 19 is a flowchart illustrating an example of processing performed in the information processing system.

[0036] Figure 20 is a diagram showing an example of a competition top screen displayed on a player terminal.

[0037] Figure 21 is a diagram showing an example of a competition top screen displayed on a player terminal.

[0038] Figure 22 1 is a diagram showing an example of a game screen during battle displayed on a player terminal.

[0039] Figure 23 is a flowchart illustrating an example of processing performed in the information processing system.

[0040] Figure 24 is a diagram showing an example of a competition top screen displayed on a player terminal.

[0041] Figure 25 is a diagram showing an example of a viewing screen displayed on a player terminal. DETAILED DESCRIPTION

[0042] The following will describe embodiments of the present invention. Note that the embodiments described below are not intended to unreasonably limit the content of the present invention as specified in the claims. In addition, not all components described in the context of the present embodiment are necessarily essential elements constituting the present invention.

[0043] 1. Structure of information processing system

[0044] Figure 1 1 is a diagram showing the overall structure of the information processing system 10 according to this embodiment. Figure 1As shown, in the information processing system 10, a server 20 and a plurality of player terminals 40 are connected via a network 30 such as the Internet, a mobile phone network, a LAN, or a WAN, thereby forming a so-called client-server communication system. Furthermore, each of the plurality of player terminals 40 communicates with the server 20 via the network 30 to transmit and receive various information. Furthermore, each of the plurality of player terminals 40 communicates with other player terminals 40 via the network 30 and the server 20 to transmit and receive various information.

[0045] The server 20 includes a control unit 21 comprising a processor such as a CPU; a storage unit 22 comprising a primary storage device such as a ROM or RAM and a secondary storage device such as an HDD or SSD; and a communication unit 23 comprising a communication module or a communication interface. In the server 20, the control unit 21 executes various processes according to the programs stored in the storage unit 22. Furthermore, the server 20 receives information from the player terminals 40 via the communication unit 23 and transmits information related to the results of the processes executed by the control unit 21 to the player terminals 40.

[0046] Each player terminal 40 is a smartphone, tablet computer, personal computer, portable game console, or a fixed game console installed in a store or home. Each player terminal 40 includes a control unit 41, which is composed of a processor such as a CPU; a storage unit 42, which is composed of a main storage device such as ROM or RAM and an auxiliary storage device such as a flash memory, HDD, or SDD; an operation / input unit 43, which is composed of a touch screen, keyboard, microphone, etc.; a display unit 44, which is composed of a liquid crystal display or organic EL display, etc.; and a communication unit 45, which is composed of a communication module or communication interface. The player terminal 40 also executes various processes according to the programs stored in the storage unit 42. Furthermore, each player terminal 40 receives information from the server 20 and transmits information to the server 20 and other player terminals 40 via the communication unit 45.

[0047] Figure 2is a functional block diagram showing the main functions of the server 20. The information processing system 10 according to the present embodiment has: a function for allowing any player serving as an organizer to hold a "user competition", in which a battle group including a plurality of players registered therein is generated, and the players belonging to the battle group fight with each other by using a card-like game medium, and these players compete for ranking based on the battle results; and a function for enabling players to watch battles between other players belonging to the battle group through the screen of the player terminal 40 that has viewing authority in the "user competition". The present embodiment will be explained by an example in which these functions are mainly implemented by the server 20. However, it should be noted that the above-mentioned functions may be mainly implemented by each player terminal 40, or may be implemented in a manner shared between the server 20 and the player terminal 40. In addition, in the server 20, as Figure 2 As shown, the above functions are realized by the cooperative operation between the data storage unit 50 and the game execution unit 60.

[0048] The data storage unit 50 stores data used by the game execution unit 60 to perform various processes, and is mainly implemented by the storage unit 22 .

[0049] The data storage unit 50 also includes a competition information database 51, which stores data related to battle groups. The competition information database 51 stores, for example, a competition ID for identifying a "user competition"; the organizer's player ID; the participant's player ID; battle rules (competition method and format); the effective time period of the battle group (the start time of the "user competition" and the competition holding period); the upper limit on the number of players that can participate; settings related to viewing permissions; a history of comments made by the organizer and participants; and a history of battles between players.

[0050] The game execution unit 60 performs the following processes: managing players using their player IDs; starting the game when game start conditions are met; executing a game mode selected from a variety of game modes; progressing the game; generating events when event generation conditions are met; calculating the game results; and ending the game when game end conditions are met. These processes are primarily implemented by the control unit 21 and the communication unit 23. The game execution unit 60 also performs the following: creating battle groups; registering players who wish to join a battle group; setting viewing permissions within a battle group; and providing a viewing function for battles between players. The game execution unit 60 includes a group generation unit 61; a player registration unit 62; a competition information setting unit (viewing permission setting unit) 63; and a viewing function provisioning unit 64.

[0051] In response to a request from the player terminal 40 of a player acting as an organizer, the group generation unit 61 generates a battle group in which multiple players can participate. The information processing system 10 according to this embodiment allows the player acting as the organizer to host a "user tournament," in which the player creates a battle group for multiple players to participate in, and the players in each battle group battle against each other. The player acting as the organizer of a "user tournament" can enter settings related to the "user tournament" on their player terminal 40. After the organizer completes the input of settings related to the "user tournament" on their player terminal 40 and confirms the holding of the "user tournament," a tournament registration request including the input settings is transmitted from the player terminal 40 to the server 20. Based on the received tournament registration request, the group generation unit 61 generates a battle group by assigning a tournament ID, which identifies the battle group, creating a new tournament record in the tournament information database 51 by linking it to the tournament ID, and registering the organizer's player ID as the organizer ID in the generated tournament record.

[0052] In this embodiment, a player registered as an organizer of any "user competition" cannot host other "user competitions" or participate in other "user competitions" as a participant until the competition holding period of the "user competition" organized by the player ends. However, it should be noted that a player registered as an organizer of a "user competition" may be able to host other "user competitions." In addition, a player registered as an organizer of a "user competition" may be able to participate in other "user competitions" as a participant.

[0053] In response to a registration request from a player terminal 40 of a player other than the organizer, the player registration unit 62 registers the player in the battle group. In this embodiment, a search for a "user competition" can be performed based on the competition ID. When a player enters the competition ID of a user competition to be searched for on their player terminal 40, the player registration unit 62 performs the following operations in response to the competition ID search request from the player terminal 40: if a "user competition" corresponding to the competition ID included in the competition ID search request exists, the player registration unit 62 transmits competition information related to the "user competition" to the player terminal 40 that requested the competition; and if no such "user competition" exists, the player registration unit 62 transmits information to the player terminal 40 indicating that no "user competition" corresponding to the competition ID included in the competition ID search request exists. Furthermore, if a "user competition" corresponding to the searched competition ID exists, the player wishing to participate can confirm their participation in the "user competition" on their player terminal 40. Furthermore, when confirmation input regarding participation in the “user competition” is performed on the player terminal 40 , a participation registration request including the competition ID and the player's own player ID is transmitted from the player terminal 40 to the server 20 .

[0054] Upon receiving a registration request, the player registration unit 62 stores the player ID included in the registration request in the competition record corresponding to the competition ID and registers the new player in a battle group consisting of participants in the "user competition." Note that in this embodiment, the number of players exceeding the upper limit set by the organizer cannot be accepted. For this reason, if a player wishing to join a battle group searches for a competition ID, and the number of players participating in the battle group for the "user competition" corresponding to the competition ID reaches the upper limit, the player cannot enter a confirmation input related to joining the battle group.

[0055] In this embodiment, a player registered as a participant in any "user competition" cannot host other "user competitions" or participate in other "user competitions" as a participant until the competition hosting period of the "user competition" in which the player himself / herself participates ends. However, it should be noted that a player registered as a participant in a "user competition" may be able to host other "user competitions." In addition, a player registered as a participant in a "user competition" may be able to participate in other "user competitions" as a participant.

[0056] In response to a tournament registration request from the player terminal 40 of a player acting as an organizer, the tournament information setting unit 63 stores settings related to the "user tournament" in the tournament record generated in the tournament information database 51. In this embodiment, a viewing permission setting unit is implemented as one of the functions of the tournament information setting unit 63, and sets viewing permissions related to the "user tournament" in response to a tournament registration request from the player terminal 40 of a player registered as an organizer. In this embodiment, one of "organizer only," "organizer and all participants," and "no viewing" can be selected as the settings related to viewing permissions.

[0057] The setting content "Organizer Only" indicates the following viewing permission, which is used to prevent the battle between players belonging to the battle group from being viewed on the player terminal 40 of a player who is neither the organizer nor the player who conducts the relevant battle, but enables the relevant battle to be viewed via the player terminal 40 of the player registered as the organizer.

[0058] The setting content "Organizer and all participants" indicates the following viewing permission, which is used to enable viewing of the battle between players belonging to the battle group not only on the player terminal 40 of the player registered as the organizer, but also on the player terminal 40 of the player who is neither the organizer nor the player conducting the relevant battle.

[0059] Setting the content to "Do not watch" does not grant any player the right to watch. In other words, no player can watch battles between players in the battle group.

[0060] Note that the viewing authority setting unit may be implemented as a function independent of the competition information setting unit 63. For example, it is also acceptable that the viewing authority is not set when registering a "user competition" and that, after registering the "user competition", the viewing authority is separately set by using the user interface of the player terminal 40 of the player registered as the organizer.

[0061] In addition, it is also acceptable that after the setting contents related to the "user competition" are registered, the setting contents related to the viewing authority can be changed by using the user interface of the player terminal 40 of the player registered as the organizer. In the case where the setting contents related to the viewing authority can be changed, it is acceptable that the setting contents related to the viewing authority can be changed only during the period from the registration of the "user competition" until the start time, and cannot be changed while the "user competition" is being held.

[0062] The viewing function providing unit 64 provides a viewing function for enabling viewing of inter-player battles according to the settings regarding viewing rights of the battle group. In this embodiment, if a player has viewing rights, the player can input a viewing request on his / her player terminal 40. When a player who wishes to view an inter-player battle inputs a viewing request, the viewing request is transmitted from the player terminal 40 to the server 20.

[0063] In response to a viewing application request received from a player terminal 40 of a player with viewing privileges, the viewing function providing unit 64 provides a viewing function by registering the player as a viewer and transmitting information required for game calculations (such as information input by each player playing the battle to be viewed) to the player terminal 40 of the player registered as a viewer. At the player terminal 40, the control unit 41 performs game calculations based on the information input by each player and received from the server 20, generates an image related to a viewing screen based on the calculation results, and displays the viewing screen on the display unit 44 of the player terminal 40, thereby allowing viewing of the progress of the battle between the players.

[0064] In this embodiment, during a battle between players, information related to some of the game media used by the opposing player is not disclosed on the player terminals 40 of the respective players engaging in the battle. The viewing function providing unit 64 provides a viewing function that allows viewing of the battle between players on the player terminals 40 of players with viewing authority, while information related to the game media that is not disclosed to the players engaging in the battle is disclosed on these player terminals 40.

[0065] When providing a battle function in the form of a card game, the game execution unit 60 processes field cards and hand cards as follows. Specifically, of the hand and field cards acquired from one player's player terminal 40, the field cards are processed so that regular card information related to the field cards is transmitted by the game execution unit 60 to the player terminals 40 of other players, and the hand cards are processed so that common virtual card information indicating that the card is a hand card is transmitted by the game execution unit 60 to the player terminals 40 of other players. Consequently, each player terminal 40 receiving the card information performs game calculations by referring to the card information database stored in the storage unit 42, treating the regular card information as the field cards and the virtual card information as the hand cards. Consequently, battling players do not possess card information related to their opponent's hand cards in their respective player terminals 40, and therefore cannot determine the type of hand cards not displayed on the game screen during battle. By doing so, even if a player analyzes his / her player terminal 40 by using an unauthorized method, since card information related to the opponent's hand does not exist in the storage unit 42 of his / her player terminal 40, such fraudulent activities can be prevented.

[0066] On the other hand, when providing the spectator function in a card game, the spectator function providing unit 64 transmits card information related to the hand cards and field cards of the two players engaged in the battle to the spectator's player terminal 40. By doing so, the spectator function is provided in a manner that discloses all the hands that are not disclosed to the players engaged in the battle, thereby enabling the spectator to watch the battle between the players in an environment in which the spectator can accurately grasp the status of each player engaged in the battle.

[0067] Another aspect of providing the viewing function may be as follows: the server 20 is responsible for performing game calculations, sending the calculation results to the viewer's player terminal 40, generating an image related to the viewing screen on each player terminal 40 based on the received calculation results, and displaying the viewing screen on the display unit 44.

[0068] Another aspect of providing the viewing function may be as follows: the server 20 is responsible for performing game calculations and generating images related to the viewing screen, sending data related to the images related to the viewing screen to the player terminals 40 of each viewer, and displaying the viewing screen on the display unit 44 of the player terminal 40 based on the data related to the received image.

[0069] The viewing function is not limited to a function for allowing viewing of a currently progressing battle, and another aspect of providing the viewing function may be such that a battle extracted from the history of past battles is reproduced as a viewing screen and then displayed on the display unit 44 .

[0070] 2. Control method in this embodiment

[0071] The control method of the present embodiment will be described in detail below by taking an example in which the game program according to the present embodiment is applied to a game application in the player terminal 40 provided as a smartphone.

[0072] Figure 3 1 is a flowchart showing an example of processing in the server 20 and the player terminal 40 related to generation of a battle group used by player A serving as an organizer to host a “user competition” in which a plurality of players participate.

[0073] First, in the player terminal 40 of player A, the control unit 41 starts the game program stored in the storage unit 42, and when player A makes a predetermined input, the game program is displayed on the display unit 44. Figure 4 The battle mode selection screen 100 is shown (step S101). On battle mode selection screen 100, a "Free Battle" icon image 101 and a "User Match" icon image 102 are displayed. Player A touches one of these icon images and inputs, and can select "Free Battle" or "User Match" as the battle mode. In the "Free Battle" battle mode, players selected from an unspecified number of players are matched up for battle, while in the "User Match" battle mode, players belonging to a battle group used for the competition battle each other.

[0074] While the battle mode selection screen 100 is being displayed, if player A touches the icon image 102 of "user competition" to input ("Yes" in step S102), Figure 5 As shown, the control unit 41 displays a host / participate selection screen 200 on the display unit 44 for selecting whether to host a user competition or participate in an existing user competition (step S103). On the host / participate selection screen 200, an icon image 201 with the message "Host a User Competition" and an icon image 202 with the message "Participate in a User Competition" are displayed. Player A can select either icon image by touching one of these icon images to make an input. Note that if player A touches the "Free Battle" icon image 101 to make an input while the battle mode selection screen 100 is being displayed ("No" in step S102), the process ends and the process related to "Free Battle" is executed.

[0075] When the player A touches the icon image 201 of "Hold User Contest" while the host / participate selection screen 200 is being displayed ("Yes" in step S104), the control unit 41 displays the "Hold User Contest" on the display unit 44. Figure 6The competition information setting screen 300 shown is displayed (step S105). Note that, when player A touches the icon image 202 of "participate in user competition" during the display of the host / participate selection screen 200 ("No" in step S104), the control unit 41 enters the user competition information setting screen 300 according to the following description. Figure 12 The processing in step S114 and subsequent steps is performed according to the flowchart shown in FIG.

[0076] The competition information settings screen 300 is used to set the information required for hosting a "user competition." In the game application according to this embodiment, two players battle by presenting cards using decks of, for example, 30 cards each. Player A, acting as the organizer, can use this screen to input various settings, including "competition method," "format," "maximum number of players," "start time," "competition time period," "viewing settings," and "organizer participation."

[0077] The item "Competition Method" is used to set the battle termination conditions. In this embodiment, Figure 7 As shown, player A can select one of the following three types of battles: "BO1", in which only one round is played, and the game ends when either side wins once; "BO3", in which a maximum of five rounds are played, and the game ends when either side wins three times; and "BO5", in which a maximum of nine rounds are played, and the game ends when either side wins five times. Figure 6 In the example shown, “BO3” is selected as shown in the display area 301 . Player A can input a change in the “matching method” by touching the change button 311 .

[0078] The item "Format" is used to set restrictions on the types of cards that can be included in the card pile used in battle. In this embodiment, Figure 7 As shown, you can select "rotation" and "unlimited" as "format". The "rotation" format only allows cards of a predetermined type to be included in the card pile, and the "unlimited" format allows all types of cards to be included in the card pile without limiting the card type. Figure 6 In the example shown, the “Alternate” format is selected, as shown in display area 302 , and player A may make an input for changing the “Format” by touching change button 312 .

[0079] The item "upper limit of players" is used to set the number of players who can join the battle group. Figure 7As shown, the "upper limit number of players" can be set between 3 and 64. In the case where the organizer participates in the battle group as a player who performs battles, the number of players includes the organizer. In the case where the organizer does not participate in the battle group as a player who performs battles, the number of players does not include the organizer. Figure 6 In the illustrated example, as shown in the display area 303 , the “upper limit number of players” is set to 16, and the player A can make an input for changing the “upper limit number of players” by touching the change button 313 .

[0080] The item "start time" is used to set the time period from when the "user competition" is registered in the server 20 until the battle can be started. Figure 7 As shown in the figure, the "start time" can be set to one of 1 hour later, 2 hours later, 3 hours later, 4 hours later, 8 hours later, 12 hours later and 24 hours later. Figure 6 In the illustrated example, as shown in the display area 304 , 4 hours later is selected, and the player A can make an input for changing the “start time” by touching the change button 314 .

[0081] The item "Contest Holding Time Period" is used to set the effective time period for accepting the start of the battle in the "User Contest" (accepting the battle application in response to the battle invitation). Figure 7 As shown in the figure, the “contest holding time period” can be set to one of 1 hour, 2 hours, 3 hours, 4 hours, 8 hours, 12 hours and 24 hours. Figure 6 In the illustrated example, as shown in the display area 305 , 8 hours is selected, and the player A can make an input for changing the “tournament holding time period” by touching the change button 315 .

[0082] The item "viewing setting" is used to set viewing permissions, which are used to specify which players are allowed to watch the battles between players in the "user competition" through their respective player terminals 40. In this embodiment, Figure 7 As shown in FIG, the item "viewing setting" can be set to one of "organizer only", "organizer and participants" and "do not watch". Figure 6 In the example shown, as shown in the display area 306 , “Organizer Only” is selected, and player A can make an input for changing the “Viewing Settings” by touching the Change button 316 .

[0083] The item "Organizer Participation" is used to set whether the player serving as the organizer (Player A in this embodiment) also participates in the battle group as a participant in the battle. Figure 7As shown, the item "Organizer Participation" can be set to "On" or "Off". When the item "Organizer Participation" is set to "On", the organizer is registered as a participant and can fight as a player in the "User Competition". On the other hand, when the item "Organizer Participation" is set to "Off", the organizer is not registered as a participant and cannot fight as a player in the "User Competition". Figure 6 In the example shown, the checkbox 308 "Off" is checked, indicating that the item "Organizer Participation" is set to "Off." Player A can input and switch the setting of the item "Organizer Participation" by touching the checkbox 307 "On" (this operation unchecks the checkbox 308 "Off" and selects the checkbox 307 "On").

[0084] exist Figure 6 The tournament information setting screen 300 shown includes a cancel button 309 and an enter button 310. When player A touches the enter button 310 to make an entry ("Yes" in step S106), the control unit 41 transmits a tournament registration request including the player ID of player A, who serves as the organizer, and information related to the setting items to the server 20 (step S107). Note that when the player touches the cancel button 309 to make an entry ("No" in step S106), the flow returns to the processing of step S103, and the host / participate selection screen 200 is displayed on the display unit 44.

[0085] At the server 20, upon receiving a tournament registration request from the player terminal 40, the control unit 21 generates a tournament record based on the information included in the received tournament registration request in the storage unit 22 (step S201). When generating the tournament record, the control unit 21 assigns a "tournament ID" and stores, in the tournament record generated in the storage unit 22, the "organizer ID" (the player ID of player A serving as the organizer), "competition method," "format," "upper limit number of players," "start time," "tournament holding time period," "viewing settings," "organizer participation," and the like in association with the "tournament ID."

[0086] When the generation of the competition record is completed, the control unit 21 sends a registration completion response to the player terminal 40 of the player A serving as the organizer (step S202). At the player terminal 40 of the player A, upon receiving the registration completion response from the server 20, the control unit 41 displays the result on the display unit 44. Figure 8 The competition registration completion screen 400 is shown (step S108).

[0087] A message indicating that the tournament registration has been completed is displayed on the tournament registration completion screen 400. Furthermore, the tournament registration completion screen 400 is provided with a screen transition button 401 for transitioning to the basic screen of the "user tournament" registered in the server 20. When player A inputs by touching the screen transition button 401, the basic screen dedicated to the "user tournament" held by player A is displayed on the display unit 44.

[0088] Figure 9 The competition top screen 500 shown in FIGURE 5 is an example of a basic screen. The display modes on the competition top screen 500 include "Chat," "Competition Information," "Competition Battle Results," and "Participant List." In the "Chat" display mode, comments sent by organizers and participants from their respective player terminals 40, notifications from the server 20, and the like are displayed. The "Chat" display mode is used to conduct battle invitations, battle applications, and battle viewing in "User Competitions." In the "Competition Information" display mode, settings stored in the competition record are viewed, such as "Competition ID," "Competition Method," "Format," "Maximum Number of Players," "Start Time," "Competition Time Period," "Viewing Settings," and "Organizer Participation." In the "Competition Battle Results" display mode, rankings based on the battle history of players registered as participants are displayed. In the "Participant List" display mode, a list of registered players is displayed.

[0089] On the competition top screen 500, there are provided a chat button 501 for selecting "chat", a competition information button 502 for selecting "competition information", a competition battle result button 503 for selecting "competition battle result", and a participant list button 504. When player A makes an input by touching each button, the control unit 41 switches the display mode.

[0090] In addition, in Figure 9 As shown, when the display mode on the competition top screen 500 is "Chat," comments 506 sent by the organizer and participants from their respective player terminals 40, notifications 507 sent from the server 20, and the like are displayed in chronological order in the chat display area 550. The comments 506 sent by the organizer and participants from their respective player terminals 40 have icon images 505 linked to the player IDs of the players who made the comments. Furthermore, a history of displayed content, such as comments 506 and notifications 507, is stored in the competition log generated in the storage unit 22 of the server 20, and the player terminals 40 download the history of displayed content from the server 20 and display it in the chat display area 550. Furthermore, a scroll bar 508 is provided in the chat display area 550 of the competition top screen 500, allowing the history of displayed content to be seamlessly viewed through touch input by dragging and sliding the slider.

[0091] In addition, below the chat display area 550 of the competition top screen 500, a deck check button 509, a battle invitation button 510, and a comment button 511 are provided. The deck check button 509 is used to check the contents of the deck to be used in the "User Competition" battle. The battle invitation button 510 is used to invite participants in the "User Competition" to join the battle. The comment button 511 is used to call up a comment input form.

[0092] In addition, after player A registers "user competition" in the server 20, at his / her player terminal 40, the control unit 41 registers the "user competition" in the server 20. Figure 10 As shown, a countdown image 602 (which indicates the remaining time until the start time of the "user competition") is displayed on the battle mode selection screen 600 in a manner superimposed on the icon image 601 of the "user competition", and the time displayed on the countdown image 602 is changed as time passes. Using this user interface, the remaining time until the battle of the "user competition" can be grasped. Note that this user interface is also displayed on the player terminal 40 of the player registered as a participant in the "user competition" organized by player A.

[0093] When the player terminal 40 notifies the server 20 that the player has inputted an input for transitioning to the battle mode selection screen 600, the server 20 responds by acquiring from the server 20 information regarding the remaining time until the start time of the "user competition" when the battle mode selection screen 600 is displayed. After acquiring the information regarding the remaining time until the start time of the "user competition" from the server 20, the control unit 41 of the player terminal 40 measures the time using a timer process and reflects the remaining time on the countdown image 602 on the battle mode selection screen 600.

[0094] In addition, at the player terminal 40 of player A after the start time of the "user competition", as shown in FIG. Figure 11 As shown, the control unit 41 displays a countdown image 702 indicating the remaining time until the end of the "user competition" on the battle mode selection screen 700, superimposed on the "user competition" icon image 701, and causes the time displayed on the countdown image 702 to change as time passes. This user interface allows users to understand the remaining time until the acceptance of the battle in the "user competition" ends. Note that this user interface is also displayed on the player terminal 40 of the player registered as a participant in the "user competition" organized by Player A.

[0095] Figure 121 is a flowchart showing an example of processing in the server 20 and the player terminal 40 (i.e., processing performed until player B who wishes to participate in the "user competition" organized by player A is registered as a participant in the battle group of the "user competition" organized by player A).

[0096] First, at the player terminal 40 of player B, the control unit 41 starts the game program stored in the storage unit 42, and when player B makes a predetermined input, Figure 4 The battle mode selection screen 100 shown is displayed on the display unit 44 (step S111). On the battle mode selection screen 100, an icon image 101 of "free battle" and an icon image 102 of "user competition" are displayed, and player B can select one of "free battle" and "user competition" as the battle mode by touching one of the icon images to make an input.

[0097] While the battle mode selection screen 100 is being displayed, if player B touches the icon image 102 of "user competition" to input ("Yes" in step S112), Figure 5 As shown, the control unit 41 displays the host / participate selection screen 200 for selecting whether to host a user competition or participate in an existing user competition on the display unit 44 (step S113). Note that if player B touches the "free battle" icon image 101 while the battle mode selection screen 100 is being displayed ("No" in step S112), this process ends and the process related to "free battle" is executed.

[0098] When the host / participate selection screen 200 is displayed and the player B touches the icon image 202 of "participate in user competition" to input ("Yes" in step S114), the control unit 41 Figure 13 The competition search screen 800 shown is displayed on the display unit 44 (step S115). When the player B touches the icon image 201 of "Hold User Competition" while the host / participate selection screen 200 is being displayed ("No" in step S114), the control unit 41 enters the user competition according to the above-mentioned Figure 3 The flowchart shown performs the processing in step S105 and subsequent steps.

[0099] A competition ID input area 801 and a search execution button 802 are provided on the competition search screen 800. Player B can grasp the competition ID (e.g., 123456) based on a direct message from player A or by checking player A's notice on a bulletin board or SNS (social network service) on the Internet, and Figure 14 As shown, the competition ID can be entered in the competition ID input area 801.

[0100] When player B makes an input by touching the search execution button 801 while the competition search screen 800 is being displayed (step S116 ), the control unit 41 transmits a competition ID search request including the content input in the competition ID input area 801 to the server 20 (step S117 ).

[0101] At the server 20, upon receiving a competition ID search request from the player terminal 40, the control unit 21 searches to see whether a competition record corresponding to the competition ID included in the received competition ID search request exists in the storage unit 22 (step S211), and sends a search completion response corresponding to the search result to the player terminal 40 of player B (step S212).

[0102] If there is a competition record corresponding to the competition ID included in the competition ID search request, the control unit 21 sends a search completion response including competition information such as the following to the player terminal 40 of player B: "Organizer ID", "Competition format", "Format", "Upper number of players", "Number of participants", "Competition holding time period" and "Viewing settings".

[0103] At the player terminal 40, in the case where the control unit 41 receives a search completion response including competition information ("Yes" in step S117), the control unit 41 Figure 15 The competition participation confirmation screen 900 shown is displayed on the display unit 44 (step S118). On the competition participation confirmation screen 900, content based on the competition information included in the search completion response is displayed in the display area 901. In addition, the competition participation confirmation screen 900 is provided with a cancel button 902 and a participation confirmation button 903. If player B touches the participation confirmation button 903 to make an input while the competition participation confirmation screen 900 is displayed ("Yes" in step S120), the control unit 41 sends a participant registration request including player B's player ID to the server 20 (step S121). Note that if player B touches the cancel button 902 to make an input while the competition participation confirmation screen 900 is displayed ("No" in step S120), the control unit 41 displays the competition search screen 800 on the display unit 44.

[0104] At the server 20, upon receiving a participant registration request from the player terminal 40, the control unit 21 updates the competition record of the "user competition" organized by player A by additionally registering the player corresponding to the player ID included in the participant registration request as a participant (step S213), and reports the completion of registering player B as a participant in the "user competition" organized by player A by sending a registration completion response to the player terminal of player B (step S214). Although not shown in the figure, when receiving the participant registration request, if the control unit 21 cannot register the requested player as a participant due to reasons such as the number of participants reaching the upper limit number or the start time having passed as a result of referring to the competition record of the "user competition", the control unit 21 issues an error response to the player terminal 40 that sent the participant registration request.

[0105] Furthermore, if no tournament record exists for the tournament ID included in the tournament ID search request, the control unit 21 transmits a search completion response to player B's player terminal 40, including search error information indicating that no applicable user tournament exists. For example, if "123457" is mistakenly entered as the tournament ID when "123456" should have been, a search error will result. Note that "user tournaments" containing the same number of participants as the upper limit can be excluded from the user tournaments to be searched. By doing so, when the server 20 receives a tournament ID search request for a real tournament ID, the server 20 can transmit a search completion response including the search error information to the player terminal 40.

[0106] At the player terminal 40, in the case where the control unit 41 receives a search completion response including search error information ("No" in step S117), the control unit 41 Figure 16 The search error screen 810 shown is displayed on the display unit 44 (step S119). A return button 811 is provided on the search error screen 810, and when player B makes an input by touching the return button 811, the control unit 41 displays the competition search screen 800 on the display unit 44.

[0107] In addition, in the present embodiment, a player who participates in the "user competition" needs to register a deck of cards to be used in battle after completing registration of himself / herself as a participant. Figure 17The illustrated deck registration screen 1000 is an example of a user interface for registering a deck of cards to be used in a "user competition." The control unit 41 may display the deck registration screen 1000 on the display unit 44 upon completion of registration as a participant in the "user competition," or may display the deck registration screen 1000 on the display unit 44 when a player registered as a participant makes a predetermined input at any time not later than the start time of the "user competition" for which the player has been registered as a participant.

[0108] exist Figure 17 In the example shown, the player prepares deck A, deck B, deck C, and deck D as card decks corresponding to the "rotation" format, and a deck selection button 1001 for selecting deck A, a deck selection button 1002 for selecting deck B, a deck selection button 1003 for selecting deck C, and a deck selection button 1004 for selecting deck D are provided on the deck registration screen 1000. By touching one of the deck selection buttons to make an input, a player participating in a "user competition" can select a deck to be used in the "user competition."

[0109] When the player inputs by touching one of the card pile selection buttons while the card pile registration screen 1000 is being displayed, the control unit 41 of the player terminal 40 Figure 18 The registration confirmation screen 1010 shown is displayed on the display unit 44. On the registration confirmation screen 1010, a message requesting confirmation of registration is displayed, and a cancel button 1011 and a register button 1012 are provided.

[0110] If a player inputs a change by touching the register button 1012 while the registration confirmation screen 1010 is displayed, the control unit 41 transmits a stack registration request to the server 20. The request includes the tournament ID of the "user tournament" in which the selected deck is to be registered, the player ID of the player registering the deck, and information related to the selected deck. Upon receiving the stack registration request, the control unit 21 updates the tournament record corresponding to the tournament ID included in the stack registration request by registering the information related to the deck in the tournament record, associating it with the player ID. Note that if a player inputs a change by touching the cancel button 1011 while the registration confirmation screen 1010 is displayed, the control unit 41 displays the stack registration screen 1000 on the display unit 44 without transmitting the stack registration request.

[0111] Figure 194 is a flowchart showing an example of processing in the server 20 and the player terminal 40 (i.e., processing performed until players are caused to battle each other while a "user competition" organized by player A is being held). The following description assumes that player B, who is registered as a participant in the "user competition" organized by player A, enters the game by using Figure 9 The user interface of the illustrated tournament top screen 500 gives an invitation to a battle, and Player C, who is also registered as a participant in the "User Tournament" organized by Player A, challenges Player B to a battle.

[0112] First, at the player terminal 40 of player C, the control unit 41 starts the game program stored in the storage unit 42, and when player C makes a predetermined input, Figure 11 The battle mode selection screen 700 shown is displayed on the display unit 44 (step S131). On the battle mode selection screen 700, a countdown image 702 indicating the remaining time until the end time of the "user competition" in which player C is registered as a participant is superimposed on the icon image 701 of the "user competition".

[0113] While the battle mode selection screen 700 is being displayed, if player C touches the icon image 701 of "User Competition" to make an input ("Yes" in step S132), the control unit 41 of the player terminal 40 transmits a competition record access request including the competition ID of "User Competition" and the player ID of player C to the server 20, thereby acquiring information stored in the competition record of "User Competition" in which player C is registered as a participant (step S133). Note that, while the battle mode selection screen 700 is being displayed, if player C touches the icon image of "Free Battle" to make an input ("No" in step S132), this process ends and processing related to "Free Battle" is executed.

[0114] At the server 20, when a competition record access request is received from the player terminal 40, the control unit 21 searches for the competition record based on the competition ID included in the competition record access request (step S231), and sends a competition data sending response including information stored in the competition record of the "user competition" organized by player A to the player terminal of player C corresponding to the player ID included in the competition record access request (step S232).

[0115] At the player terminal 40 that receives the competition data transmission response from the server 20, the control unit 41 Figure 20 The competition top screen 520 shown is displayed on the display unit 44 (step S134).

[0116] exist Figure 20On the competition top screen 520 shown, a comment 521 indicating that player B is accepting a battle is displayed, and a battle application button 522 is provided on the comment 521. In this embodiment, when a battle ID is generated, the comment 521 with the battle application button 522 is posted.

[0117] More specifically, when a player registered as a participant in a "user competition" makes an input by touching a battle invitation button provided below the comment display area, the control unit 41 of the player terminal 40 transmits a battle ID generation request to the server 20. At the server 20 that receives the battle ID generation request, the control unit 21 issues a battle ID in association with the player ID of the player who issued the battle invitation, and stores the battle ID in the competition record.

[0118] In the competition record, battle status information is associated with the battle ID. When the battle ID is generated, the battle status information is set to "Accepting." Then, when a battle between Player B and another player begins, the battle status information associated with the battle ID changes to "Battle in Progress." When the battle ends, the battle status information associated with the battle ID changes to "Battle Ended."

[0119] In other words, on the competition top screen 520, as a result of player B making an input by touching the above-mentioned battle invitation button, a comment 521 having a battle application button 522 linked to the battle ID issued in response to the battle invitation given by player B is displayed on the display unit 44 of the player terminal 40 of player C.

[0120] Since the viewing setting is set to "organizer only" in the "user competition" organized by player A, the comment 521 on the competition top screen 520 on the player terminal 40 of the player registered as a participant is provided with only the battle application button 522. However, if the viewing setting is set to "organizer and participant", Figure 21 As shown, the comments 521 on the competition top-level screen 520 will be provided with not only a battle application button 522, but also a viewing application button 523.

[0121] While the competition top-level screen 520 is being displayed, when player C makes an input by touching the battle application button 522 ("Yes" in step S135), the control unit 41 of the player terminal 40 sends a battle application request to the server 20 (step S136), which includes the competition ID of the "user competition" in which player C is registered as a participant and the battle ID issued in response to the battle invitation given by player B.

[0122] At the server 20, upon receiving a battle application request from the player terminal 40, the control unit 21 refers to the competition record based on the competition ID and battle ID included in the received battle application request, and determines whether the battle status information associated with the battle ID is set to "accepting" (step S233).

[0123] If the battle status information associated with the battle ID included in the battle request is set to "Accepting" ("No" in step S233), the control unit 21 updates the battle record based on the battle ID included in the battle request request by registering player C as a competitor in the battle corresponding to the battle ID (step S234). At this time, the battle status information associated with the battle ID also changes from "Accepting" to "Battle in Progress." In addition, the control unit 21 sends a battle acceptance completion response to player C's player terminal 40 (step S235), which reports that the battle request made by player C based on the battle request request has been accepted. Although not shown in the figure, if the battle status information associated with the battle ID included in the battle request request is not set to "Accepting" ("Yes" in step S233), the control unit 21 sends a battle request error response to the player terminal 40 reporting that the battle request could not be accepted, and ends the process.

[0124] Then, when the battle application made by player C is accepted in response to the battle invitation given by player B, battle processing for conducting a battle in the form of a card game is executed, wherein the control unit 41 of the player terminal 40 of player B and the control unit 41 of the player terminal 40 of player C exchange input information, card information, etc. with each other via the server 20 (terminal side processing: step S137, server side processing: step S236).

[0125] At the player terminal 40 of player B, the control unit 41 performs the following processing as terminal-side processing: processing of sending player B's input information, card information, etc. to the server 20; processing of obtaining player C's input information, card information, etc. from the server 20; processing of performing game calculations based on the input information, card information, etc. of each player, and generating images related to the game screen in battle based on the calculation results; and so on.

[0126] At the player terminal 40 of player C, the control unit 41 performs the following processing as terminal-side processing: processing of sending player C's input information, card information, etc. to the server 20; processing of obtaining player B's input information, card information, etc. from the server 20; processing of performing game calculations based on the input information and card information of each player, and generating images related to the game screen in battle based on the calculation results; and so on.

[0127] At the server 20, the control unit 21 performs the following processing as server-side processing: processing of sending input information, card information, etc. received from the player terminal 40 of player B to the player terminal 40 of player C; processing of sending input information, card information, etc. received from the player terminal 40 of player C to the player terminal 40 of player B; processing of managing the progress of the battle; and so on.

[0128] Figure 22 11 is an example of an in-battle game screen 1100 displayed on the display unit 44 of the player terminal 40 of player B during a battle between player B and player C.

[0129] The in-battle game screen 1100 is provided with a turn end button 1101 for announcing the end of the turn of player B. When player B makes an input by touching the turn end button 1101, player B's turn ends, and the turn of player C serving as the opponent begins.

[0130] During battle, a point indicator 1102 indicating player B's points (PP) and a point indicator 1103 indicating player C's points (PP) are provided on the game screen 1100. These point indicators represent the points at the start of each player's turn and the remaining available points. For example, "3 / 5" on point indicator 1102 means that the player's points (PP) at the start of the turn are 5, and the remaining available points are 3.

[0131] During battle, a character icon 1104 of player B and a character icon 1105 of player C are displayed on the game screen 1100. The numeric characters displayed in the character icon 1104 represent a player life indicator 1106 of player B, and the numeric characters displayed in the character icon 1105 represent a player life indicator 1107 of player C. These player lives are an element for determining winning or losing in the card game, and a player can win the card game by reducing the opponent's player life to 0.

[0132] Player B's hand 1108 is displayed to the right of Player B's character icon 1104, and Player C's hand 1109 is displayed to the left of Player C's character icon 1105. Since the game screen 1100 during battle is displayed on the display unit 44 of Player B's player terminal 40, card information related to Player B's hand 1108 is displayed, but card information related to Player C's hand 1109 is not displayed. Each of Player B's hand cards 1108 displays card information such as the card name (not shown), card image (not shown), cost indicator 1110, attack power indicator 1111, and card life indicator 1112. Player C's hand 1109 is displayed with a card skin that shows the same design as the deck used by Player C. Note that the opponent's hand is identified as follows. The server 20 transmits virtual card information for the cards used as hands, and the player terminal 40 that receives the virtual card information references the card information database in the storage unit 42.

[0133] When player B's turn begins, one card is added to player B's hand 1108 from reserve cards 1115, which includes unused cards in player B's deck. When player C's turn begins, one card is added to player C's hand 1109 from reserve cards 1116, which includes unused cards in player C's deck.

[0134] In addition, during battle, the game screen 1100 displays player B's field card 1113 and player C's field card 1114. Each player can convert hand cards into field cards within the available cost range during their turn. They can also reduce the life of the opponent's field cards or the opponent's player life based on the attack power of the field card. When the life of a field card reaches 0, the field card leaves the field. Furthermore, as described above, when either player's player life reaches 0, the other player wins.

[0135] Therefore, on the game screen 1100 during the battle, player B cannot know the card information related to player C's hand cards 1109, but player B can know the card information related to the field cards 1114 that have changed from the hand cards 1109.

[0136] Figure 23 This is a flowchart illustrating an example of processing in the server 20 and the player terminal 40 (i.e., processing executed until viewing of a battle between players is permitted while a "user tournament" organized by player A is being held). The following description assumes that player A, registered as the organizer of the "user tournament," is viewing a battle between players B and C, who are registered as participants in the "user tournament" organized by player A.

[0137] First, at the player terminal 40 of player A, the control unit 41 starts the game program stored in the storage unit 42, and when player A makes a predetermined input, the game program is displayed on the display unit 44. Figure 11 The battle mode selection screen 700 is shown (step S141). On the battle mode selection screen 700, a countdown image 702 indicating the remaining time until the end time of the "user competition" in which player A is registered as a participant is superimposed on the icon image 701 of the "user competition".

[0138] While the battle mode selection screen 700 is being displayed, if player A touches the icon image 701 for "User Competition" to make an input ("Yes" in step S142), the control unit 41 of the player terminal 40 transmits a competition record access request including the competition ID of "User Competition" and player A's player ID to the server 20, thereby acquiring information stored in the competition record of "User Competition" for which player A is registered as the organizer (step S143). Note that, while the battle mode selection screen 700 is being displayed, if player A touches the icon image for "Free Battle" to make an input ("No" in step S142), this process ends and processing related to "Free Battle" is executed.

[0139] At the server 20, when a competition record access request is received from the player terminal 40, the control unit 21 searches for the competition record based on the competition ID included in the competition record access request (step S241), and sends a competition data sending response to the player terminal of player A corresponding to the player ID included in the competition record access request (step S242), and the competition data sending response includes information stored in the competition record of the "user competition" organized by player A.

[0140] At the player terminal 40 that receives the competition data transmission response from the server 20, the control unit 41 displays the Figure 24 The competition top screen 560 is shown (step S134).

[0141] exist Figure 24On the top-level competition screen 560 shown, a comment 561 indicating that Player B and Player C are currently battling is displayed, and a request-to-watch button 562 is provided above the comment 561. In this embodiment, the request-to-watch button 562 is displayed only on the player terminals 40 of players registered as organizers or participants of the "User Competition" and who have set viewing rights in the "Viewing Settings." In this embodiment, since the "Viewing Settings" is set to "Organizer Only," Player A can request to watch on his / her own player terminal 40. However, the request-to-watch button 562 is not displayed on the player terminal 40 of, for example, Player D (who is registered as a participant but is different from Player B and Player C who are battling), and therefore Player D cannot request to watch.

[0142] While the competition top-level screen 560 is being displayed, when player A inputs by touching the viewing application button 562 ("Yes" in step S145), the control unit 41 of the player terminal 40 sends a viewing application request to the server 20 (step S146), which includes player A's own player ID, the competition ID of the "user competition", and the battle ID related to the battle between player B and player C (the battle ID generated when the battle invitation is given).

[0143] At the server 20, upon receiving a viewing request from the player terminal 40, the control unit 21 refers to the competition record based on the competition ID included in the received viewing request, and determines whether the player ID included in the viewing request belongs to a player with viewing permission (step S243). Since the "viewing setting" of the "user competition" is set to "organizer only" and player A is registered as the "organizer", it is determined that the player ID included in the viewing request sent from player A's player terminal 40 is the player ID of a player with viewing permission.

[0144] In the case where the player ID included in the viewing application request indicates a player with viewing rights ("Yes" in step S243), the control unit 21 updates the competition record by registering the player ID included in the viewing application request as a viewer of the battle corresponding to the battle ID included in the viewing application request in the competition record based on the competition ID included in the viewing application request (step S244). In addition, the control unit 21 sends a viewing acceptance completion response to the player terminal 40 of player A, reporting that the acceptance of the viewing application made by player A based on the viewing application request has been completed (step S245). Although not shown in the figure, if the player corresponding to the player ID included in the viewing application request is not a player with viewing rights ("No" in step S243), the control unit 21 sends a viewing application error response to the player terminal 40, reporting that the viewing application cannot be accepted, and ends the processing.

[0145] Then, when registration as a spectator of the battle between player B and player C is accepted, the control unit 41 of player A's player terminal 40 performs viewing processing for enabling viewing of the battle by obtaining player B's input information and card information and player C's input information and card information via the server 20 (terminal side processing: step S147, server side processing: step S246).

[0146] At the player terminal 40 of player A, the control unit 41 performs the following processing as terminal-side processing: processing of obtaining input information, card information, etc. of player B and player C from the server 20; processing of performing game calculations based on the input information, card information, etc. of each player, and generating an image related to the viewing screen based on the calculation results; and so on.

[0147] At the server 20, the control unit 21 performs the following processing as server-side processing: processing of sending input information and card information received from player B's player terminal 40 to player A's player terminal 40; processing of sending input information and card information received from player C's player terminal 40 to player A's player terminal 40; processing of managing the progress of the battle; and so on.

[0148] Figure 25 12 is a viewing screen 1200 displayed on the display unit 44 of the player terminal 40 of the player A who is viewing the battle between the player B and the player C.

[0149] The viewing screen 1200 is a screen seen by the player who has issued a battle invitation associated with the generation of a battle ID. Similar to the in-battle game screen 1100, the viewing screen 1200 is a screen seen from player B during a battle between player B and player C. However, the viewing screen 1200 differs from the in-battle game screen 1100 in that card information related to player C's hand 1109 is displayed. Specifically, in this embodiment, the viewing function differs from the battle function in that, when providing the viewing function, the server 20 transmits regular card information related to the hand and field cards of the two players engaged in the battle. Thus, the images associated with the viewing screen are generated in such a way that the hand and field cards of each player engaged in the battle are displayed on the spectator's player terminal 40 based on the received regular card information.

[0150] Therefore, on the viewing screen 1200 , player A serving as a viewer can view the battle in a state in which player A can know card information regarding the hand cards and field cards of both player B and player C.

[0151] The information processing system 10 described above enables viewing permissions to be set so that players belonging to a battle group formed for a "user competition" can watch battles via the terminal of a player registered as an organizer, while players who are neither organizers nor players participating in the battles cannot watch the battles on their terminals. This enables organizers to appropriately manage battle groups while still maintaining fairness among players, thereby enhancing the interface environment associated with games in which players compete with each other.

[0152] In particular, if participants are allowed to watch a battle-style game in which information about some cards is not disclosed, as in the card game implemented by information processing system 10, participants can learn the contents of other participants' decks and battle tactics before the battle begins. This can affect fairness among participants. Therefore, the present invention is suitable for enabling viewing rights that only allow organizers to view the game.

[0153] In addition, the information processing system 10 can be used not only for card games, but also for games that allow players to battle each other, allowing organizers to act as supervisors who can detect improper behavior during battles and violations of game etiquette (such as giving up the game during battles).

[0154] In addition, the information processing system 10 can also be used in the following manner: participants in the battle cannot watch the battle to ensure fairness, and only the organizer is granted viewing rights, so that the organizer can distribute the viewing screen of the organizer's own player terminal 40 via the Internet to enable third parties to watch the battle.

[0155] In addition, since the information processing system 10 also allows selection of viewing rights for enabling players registered as participants to view the battle, the organizer can manage the battle group according to the preferences of the "user competition".

[0156] In particular, in a game played in a battle format where information about some cards is not disclosed, such as the card game implemented by the information processing system 10, a player can watch the game by viewing card information that is not disclosed to competitors through his / her viewing screen. Therefore, by allowing the setting of viewing rights for players registered as participants to view the game, the information processing system 10 can also be used to provide participants with an opportunity to study battle tactics.

[0157] 3. Modifications

[0158] Player matching for battles between players can be achieved not only by sending an application in response to a battle invitation, but also by randomly matching players in a battle group.

[0159] In addition, "players" are not limited to real players, but include computer players and non-player characters (NPCs) that act according to a predetermined algorithm. For example, if no battle application is made after a certain period of time from the start of the battle invitation, a battle can be started with a computer player or non-player character (NPC) as the opponent.

[0160] Furthermore, battles between players need not be independent of each other, but can be held in a tournament format. Player matching in a tournament format can be achieved by determining players through a lottery on server 20, or can be achieved, for example, by the organizer manually inputting a pair of players to be matched on player terminal 40 and transmitting the input to server 20 to register the matched players in the tournament record. Furthermore, when a tournament format is employed, the present invention can be configured to enable the selection of seed players. If, without seed players being set, a match cannot be made due to the number of participants in the tournament, a computer player or non-player character (NPC) can be added as an opponent.

[0161] Furthermore, while the present invention is configured so that a view button for requesting to view is not displayed on the player terminal 40 of a player without viewing authority, the view button may be displayed regardless of whether the player has viewing authority. In this case, the present invention may be configured so that when a view request is sent to the server 20 as a result of an input from a player without viewing authority to the view button on his / her player terminal 40, the server 20 receiving the view request may issue an error response due to the player's lack of viewing authority. Furthermore, the present invention may be configured so that the view button is displayed on the player terminal 40 of a player without viewing authority, but processing is performed to not accept input to the view button and graying out the view button, thereby notifying the player that the view button is disabled.

[0162] Alternatively, server 20 can be configured as two separate servers, one for providing the battle function and the other for providing the spectator function. This allows communication traffic to be dispersed even when the number of viewers increases, thereby mitigating the adverse effects on the provision of the battle function. This configuration is particularly effective when providing the spectator function for games where server response delays significantly affect the outcome of the game, such as fighting games and sports games.

[0163] In addition, although the viewing screen is the screen seen by the player who issued the battle invitation, the present invention may be provided with a viewpoint change function for switching to the viewing screen seen from the opponent in response to an input from the viewer's player terminal 40. In the case of providing a viewpoint change function for switching the viewing screen, input for switching the viewpoint may be enabled when a viewing request is made (for example, by providing a view request button for viewing from the viewpoint of player B and a view request button for viewing from the viewpoint of player C), or alternatively, the viewing screen may be provided with a viewpoint change button so that the viewpoint change function is activated in response to input to the viewpoint change button.

[0164] Furthermore, the viewing function may include a user interface for exiting the battle viewing at any convenient time for the viewer. For example, the present invention may be configured to provide a viewing exit button on the viewing screen, so that upon inputting the viewing exit button, a viewing exit request is transmitted from the viewer's player terminal 40 to the server 20. In response to the viewing exit request, the server 20 may terminate the provision of the viewing function by, for example, terminating the transmission of input information from the player participating in the battle to the viewer's player terminal 40.

[0165] Furthermore, if participants are also granted viewing privileges, a fixed number (upper limit) may be set for the number of viewers that can be registered for each battle. If the number of viewers registered in the match record reaches the fixed number, and the server 20 receives a new viewing request from the player terminal 40, the server 20 may issue an error response to the player terminal 40 of the requester. Furthermore, the present invention may be configured to disable input of viewing requests on the player terminal 40 if the number of viewers registered in the match record reaches the fixed number.

[0166] Although the present invention has been described using a card game as an example of a game that allows players to battle each other, the viewing function of the information processing system 10 can be provided for other types of games. The present invention is applicable to any type of game that allows players to battle each other, including fighting games, sports games, action games, battle royale games, role-playing games, etc. In addition, battles between players are not limited to one-on-one battles and can take the form of many-to-many battles or one-to-many battles.

[0167] In addition, the present invention can be configured to allow players who only watch the battle and do not participate in the battle to be registered as non-competitors in the competition record of "User Competition", thereby reducing the burden of non-competitors registering card piles. In addition, the "Viewing Settings" of "User Competition" can be set with the following selectable options: "Organizers and Non-competitors Only", which is a viewing permission for only organizers and non-competitors to view the game; "Non-competitors Only", which is a viewing permission for only non-competitors to view the game; and so on.

[0168] Furthermore, card information that is not displayed on the in-battle game screen but is displayed on the viewing screen can be applied to all reserve cards, hand cards, and field cards, or only to some of these cards. Furthermore, if there are multiple hands, card information related to only some of these hands can be displayed on the viewing screen.

[0169] In addition, even during the "user competition" being held, new players can be registered as participants in the "user competition". In addition, even after the competition record of the "user competition" is generated with the organizer set not to participate in the battle, the server 20 can change the registration content in response to a request from the organizer's player terminal 40 to set the organizer as the organizer and participant.

[0170] Description of Reference Numerals

[0171] 10 Information Processing System

[0172] 20 servers

[0173] 40 Player Terminal

[0174] 21,41 Control Unit

[0175] 22,42 storage units

[0176] 23,45 communication units

[0177] 43 Operation / input unit

[0178] 44 display units

[0179] 50 data storage units

[0180] 51 Competition Information Database

[0181] 60 Game Execution Unit

[0182] 61 groups of generation units

[0183] 62 Player Registration Unit

[0184] 63 Competition Information Setting Unit (Viewing Permission Setting Unit)

[0185] 64 Viewing function providing unit

Claims

1. A computer program product comprising a program for a game in which players battle each other, the program causing a computer to function as: a group generating unit for generating, in response to a request from a terminal of a player serving as an organizer, a battle group in which the player is registered as an organizer; a player registration unit for registering the plurality of players in the battle group in response to requests from terminals of the plurality of players different from the organizer; a viewing authority setting unit for setting viewing authority related to a battle between players belonging to the battle group in response to a request from a terminal of the player serving as the organizer; as well as a viewing function providing unit for providing a viewing function that allows viewing of a battle between players according to setting contents related to the viewing authority, Among them, the viewing permission setting unit is capable of setting the following viewing permission, with which the battle between players belonging to the battle group cannot be viewed at the terminal of a player who is neither the organizer nor the player conducting the battle, but can be viewed via the terminal of the player registered as the organizer.

2. The computer program product according to claim 1, wherein At the terminals of the respective players engaging in battle, information on a portion of the game media used by the opponent player is not disclosed, and The viewing function providing unit provides the viewing function so that a battle between players can be viewed at a terminal of a player having the viewing authority, the terminal disclosing information related to a game medium that is not disclosed to players who are battling each other.

3. The computer program product according to claim 1 or 2, wherein: The viewing permission setting unit is capable of setting the following viewing permission, with which the battle between the players belonging to the battle group can be viewed not only via the terminal of the player registered as the organizer, but also via the terminal of the player who is neither the organizer nor the player conducting the battle.

4. An information processing device for use in a game in which players battle each other, the information processing device comprising: a group generating unit for generating, in response to a request from a terminal of a player serving as an organizer, a battle group in which the player is registered as an organizer; a player registration unit for registering the plurality of players in the battle group in response to requests from terminals of the plurality of players different from the organizer; a viewing authority setting unit for setting viewing authority related to a battle between players belonging to the battle group in response to a request from a terminal of the player serving as the organizer; as well as a viewing function providing unit for providing a viewing function that allows viewing of a battle between players according to setting contents related to the viewing authority, Among them, the viewing permission setting unit is capable of setting the following viewing permission, with which the battle between players belonging to the battle group cannot be viewed at the terminal of a player who is neither the organizer nor the player conducting the battle, but can be viewed via the terminal of the player registered as the organizer.

5. A method for controlling an information processing device used in a game in which players battle each other, the method comprising: a group generating step for generating, in response to a request from a terminal of a player serving as an organizer, a battle group in which the player is registered as an organizer; a player registration step for registering the plurality of players in the battle group in response to requests from terminals of the plurality of players different from the organizer; a viewing authority setting step for setting viewing authority related to a battle between players belonging to the battle group in response to a request from a terminal of the player serving as the organizer; as well as a viewing function providing step for providing a viewing function that allows viewing of a battle between players according to setting contents related to the viewing authority, Among them, in the viewing permission setting step, the following viewing permission can be set, with which the battle between players belonging to the battle group cannot be viewed at the terminal of a player who is neither the organizer nor the player conducting the battle, but can be viewed via the terminal of the player registered as the organizer.

6. A storage medium storing a program for a game in which players battle each other, the program causing a computer to function as: a group generating unit for generating, in response to a request from a terminal of a player serving as an organizer, a battle group in which the player is registered as an organizer; a player registration unit for registering the plurality of players in the battle group in response to requests from terminals of the plurality of players different from the organizer; a viewing authority setting unit for setting viewing authority related to a battle between players belonging to the battle group in response to a request from a terminal of the player serving as the organizer; as well as a viewing function providing unit for providing a viewing function that allows viewing of a battle between players according to setting contents related to the viewing authority, Among them, the viewing permission setting unit is capable of setting the following viewing permission, with which the battle between players belonging to the battle group cannot be viewed at the terminal of a player who is neither the organizer nor the player conducting the battle, but can be viewed via the terminal of the player registered as the organizer.

Images