Information processing system, information processing method, and information processing program
The information processing system simplifies the selection of multiplayer games by allowing players to set search conditions for rescue requests, enhancing operational efficiency in multiplayer game systems.
Patent Information
- Application Number
- JP2023073571
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-04-27
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2043-04-27
AI Technical Summary
The existing multiplayer game systems face complexity in player operations when handling a large number of rescue requests, making it difficult for players to select suitable multiplayer games efficiently.
An information processing system that includes a search setting function allowing players to preset search conditions for rescue requests, enabling the system to filter and display relevant multiplayer game options based on these conditions, thereby simplifying the selection process.
The system improves operational efficiency by allowing players to easily find and participate in multiplayer games that match their preferences, reducing the complexity of selecting from numerous rescue requests.
Smart Images

Figure 2024158404000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an information processing system, an information processing method, and an information processing program. [Background technology]
[0002] For example, Patent Document 1 discloses a system that realizes a multiplayer game in which multiple players cooperate to play against an enemy character. In this system, a player can request other players to help, i.e., participate in, a multiplayer game that the player has started. Therefore, a request for help is sent to each player for a multiplayer game in which the player can participate. The player can select the multiplayer game in which the player wishes to participate from among the multiplayer games for which the player has received a request for help. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Patent No. 7116233 Summary of the Invention [Problem to be solved by the invention]
[0004] In the above system, multiple types of multiplayer games are provided in which multiple players can participate. Each player can select the multiplayer game in which he or she will participate after checking the type of the multiplayer game for which the rescue request has been received. However, if a large number of rescue requests are received, the operation of the player to select a multiplayer game may become cumbersome.
[0005] An object of the present invention is to provide an information processing system, an information processing method, and an information processing program that can improve operability for a player. [Means for solving the problem]
[0006] In order to solve the above problem, an information processing system includes: One or more computers; The computer, A process of executing a multiplayer game having a content ID selected by a first player; a process of having a second player different from the first player acquire one or more pieces of game information including the content ID selected by the second player; A process of having the second player participate in the multiplayer game corresponding to the game information selected by the second player from among the game information acquired by the second player; Carry out the following.
[0007] The computer, A process of associating the content ID selected by a player with one of a plurality of storage units; A process of receiving an operation by a player to select one of the plurality of storage units; displaying the game information including the content ID associated with the storage unit selected by a player from the acquired game information; may be carried out.
[0008] The process of causing the second player to obtain the game information includes: This may include a process for generating information that can be posted to an SNS.
[0009] In order to solve the above problem, an information processing method includes: One or more computers A process of executing a multiplayer game having a content ID selected by a first player; a process of having a second player different from the first player acquire one or more pieces of game information including the content ID selected by the second player; A process of having the second player participate in the multiplayer game corresponding to the game information selected by the second player from among the game information acquired by the second player; Carry out the following.
[0010] In order to solve the above problem, an information processing program includes: A process of executing a multiplayer game having a content ID selected by a first player; a process of having a second player different from the first player acquire one or more pieces of game information including the content ID selected by the second player; A process of having the second player participate in the multiplayer game corresponding to the game information selected by the second player from among the game information acquired by the second player; The computer is made to carry out the above steps. Effect of the Invention
[0011] According to the present invention, it is possible to improve operability for the player. [Brief description of the drawings]
[0012] [Figure 1] FIG. 1 is an explanatory diagram showing a schematic configuration of an information processing system. [Diagram 2] Fig. 2A is a diagram illustrating the hardware configuration of a player terminal, and Fig. 2B is a diagram illustrating the hardware configuration of a server. [Diagram 3] Fig. 3A is a diagram showing an example of a My Page screen, and Fig. 3B is a diagram showing an example of a quest list screen. [Figure 4] Fig. 4A is a diagram showing an example of a rescue request list screen, Fig. 4B is a diagram showing an example of a multi-battle list screen, and Fig. 4C is a diagram showing an example of a multi-battle selection screen. [Diagram 5] Fig. 5A shows an example of a My Page screen when a rescue request is received from another player. Fig. 5B shows an example of a quest list screen when a rescue request is received from another player. Fig. 5C shows an example of a rescue request list screen when a rescue request is received from another player. [Figure 6]Fig. 6A is a first diagram for explaining an example of a rescue search screen, Fig. 6B is a second diagram for explaining an example of a rescue search screen, and Fig. 6C is a third diagram for explaining an example of a rescue search screen. [Figure 7] Fig. 7A is a diagram for explaining an example of a search setting screen, and Fig. 7B is a diagram for explaining an example of a rescue setting screen. [Figure 8] FIG. 8 is a diagram illustrating the search pattern storage unit. [Figure 9] Fig. 9A is a diagram showing an example of a rescue request screen, Fig. 9B is a diagram showing an example of a rescue request completion screen, and Fig. 9C is a diagram showing an example of a battle screen. [Figure 10] FIG. 10 is a functional block diagram of the player terminal. [Figure 11] FIG. 11 is a functional block diagram of the server. [Figure 12] FIG. 12 is a first sequence diagram illustrating the processing of the player terminal and the server. [Figure 13] FIG. 13 is a second sequence diagram illustrating the processing of the player terminal and the server. [Figure 14] FIG. 14 is a third sequence diagram illustrating the processing of the player terminal and the server. [Figure 15] FIG. 15 is a sequence diagram illustrating the processing of the second player terminal and the server. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] An embodiment of the present invention will be described in detail below with reference to the accompanying drawings. The numerical values and the like shown in the embodiment are merely examples for easy understanding and do not limit the present invention unless otherwise specified. In this specification and drawings, elements having substantially the same functions and configurations are given the same reference numerals to avoid duplicated explanations, and elements not directly related to the present invention are not shown.
[0014] (Overall configuration of information processing system S) 1 is an explanatory diagram showing a schematic configuration of an information processing system S. The information processing system S is a so-called client-server system including a player terminal 1, a server 100, and a communication network N having a communication base station Na. The information processing program is a variety of programs executed in the information processing system S.
[0015] The player terminal 1 can establish communication with the server 100 via the communication network N. The player terminal 1 broadly includes electronic devices capable of wireless or wired communication connection with the server 100. Examples of the player terminal 1 include smartphones, mobile phones, tablet devices, personal computers, game devices, and the like. In this embodiment, a case where a smartphone is used as the player terminal 1 will be described.
[0016] The server 100 is communicatively connected to a plurality of player terminals 1. The server 100 manages the game and accumulates various information (player information) for each player playing the game. The server 100 also updates the accumulated information and controls the progress of the game based on operations input from the player terminals 1.
[0017] The communication base station Na is connected to the communication network N. The communication base station Na wirelessly transmits and receives information to and from the player terminal 1. The server 100 is connected to the communication network N. The communication network N is composed of a mobile phone network, an Internet network, a LAN (Local Area Network), a dedicated line, etc. The communication network N realizes a wireless or wired communication connection between the player terminal 1 and the server 100.
[0018] In the information processing system S of this embodiment, the player terminal 1 and the server 100 function as a game device G. The player terminal 1 and the server 100 are assigned roles for controlling the progress of the game, and the game can progress through cooperation between the player terminal 1 and the server 100.
[0019] A game realized by the information processing system S is, for example, a browser game. In a browser game, the player terminal 1 transmits information based on an input operation of the player to the server 100. The server 100 controls the progress of the game based on the received information, and causes the player terminal 1 to receive screen information according to the progress of the game. The player terminal 1 displays a game screen on a display based on the received screen information. Note that the game realized by the information processing system S is not limited to a browser game, and may be an application game in which at least a part of the progress control of the game is executed by the player terminal 1.
[0020] (Hardware configuration of the player terminal 1 and the server 100) Fig. 2A is a diagram for explaining the hardware configuration of the player terminal 1. Fig. 2B is a diagram for explaining the hardware configuration of the server 100. As shown in Fig. 2A, the player terminal 1 includes one or more CPUs (Central Processing Units) 10, a storage device 12, a bus 14, an input / output interface 16, a storage unit 18, a communication unit 20, an input unit 22, and an output unit 24.
[0021] As shown in FIG. 2B, the server 100 includes one or more CPUs 110, a storage device 112, a bus 114, an input / output interface 116, a storage unit 118, a communication unit 120, an input unit 122, and an output unit 124.
[0022] The configurations and functions of the CPU 110, storage device 112, bus 114, input / output interface 116, storage unit 118, communication unit 120, input unit 122, and output unit 124 of the server 100 are substantially the same as those of the CPU 10, storage device 12, bus 14, input / output interface 16, storage unit 18, communication unit 20, input unit 22, and output unit 24 of the player terminal 1. Therefore, in the following, the hardware configuration of the player terminal 1 will be described, and a description of the server 100 will be omitted.
[0023] The CPU 10 runs a program stored in a storage device 12 to control the progress of the game. The storage device 12 is composed of a ROM (Read Only Memory) or a RAM (Random Access Memory), and stores programs and various data required for controlling the progress of the game. The storage device 12 is connected to the CPU 10 via a bus 14.
[0024] An input / output interface 16 is connected to the bus 14. To the input / output interface 16, a storage unit 18, a communication unit 20, an input unit 22, and an output unit 24 are connected.
[0025] The storage unit 18 is configured with a ROM or RAM, and stores various programs and data. In the player terminal 1, the programs or data stored in the storage unit 18 are loaded by the CPU 10 into the storage device 12 (RAM).
[0026] The communication unit 20 is wirelessly connected to the communication base station Na for communication, and transmits and receives information such as various data and programs to and from the server 100 via the communication network N. In the player terminal 1, the program or data received from the server 100 is stored in the storage device 12 or the storage unit 18.
[0027] The input unit 22 is composed of, for example, a touch panel, a button, a keyboard, a mouse, a cross key, an analog controller, etc., into which the player's operation is input (which accepts the operation). The input unit 22 may also be a dedicated controller provided in the player terminal 1 or connected (externally) to the player terminal 1. Furthermore, the input unit 22 may be composed of an acceleration sensor that detects the inclination or movement of the player terminal 1, or a microphone that detects the voice of the player. In other words, the input unit 22 broadly includes devices that can input the player's intention in an identifiable manner.
[0028] The output unit 24 includes a display device and a speaker. The output unit 24 may be a device connected (externally attached) to the player terminal 1. In this embodiment, the player terminal 1 includes a display 26 as the output unit 24, and a touch panel superimposed on the display 26 as the input unit 22.
[0029] (Game Contents) Next, the content of the game provided by the information processing system S (game device G) of this embodiment will be described using an example. The game of this embodiment is a so-called online RPG (Role-Playing Game), and multiple players can play the game simultaneously in one game world via a communication network N. A main character is given to the player by the operator. In addition to the main character, the player can also acquire multiple sub-characters by lottery or the like and make them his or her allies. Hereinafter, the main character and the sub-characters that have been made his or her allies are called ally characters.
[0030] Various quests are prepared for the game. The game progresses as the player accepts quests. A quest involves a battle between an enemy character according to the content of the quest and the player's ally character. The quest is cleared by winning the battle. Note that the number of enemy characters in one battle is not limited to one, and may be multiple. The game content of this embodiment will be described in detail below.
[0031] FIG. 3A is a diagram showing an example of a My Page screen. FIG. 3B is a diagram showing an example of a quest list screen. When the player terminal 1 accesses the server 100 and enters a logged-in state, the game starts. When the game starts, the My Page screen shown in FIG. 3A is displayed on the display 26 of the player terminal 1. The My Page screen is provided with a plurality of operation units such as tabs that can be operated by the player (here, operation operations). Note that operation units that can be operated by the player are also provided on various screens other than the My Page screen, which will be described later.
[0032] As shown in Fig. 3A, on the My Page screen, a frame bar 30 is displayed at the bottom of the display 26. The frame bar 30 is also displayed when the screen displayed on the display 26 changes to a screen other than the My Page screen. The frame bar 30 is provided with a My Page tab 30a marked "My Page," a reload tab 30b marked "Reload," and a back tab 30c marked "Back."
[0033] When the My Page tab 30a is operated, the My Page screen is displayed, and it is possible to return to the My Page screen from a screen other than the My Page screen. When the Reload tab 30b is operated, the screen being displayed on the display 26 is reloaded, and the displayed screen is updated. When the Back tab 30c is operated, it is possible to return to the screen that was displayed immediately before the screen being displayed on the display 26.
[0034] As shown in Fig. 3A, a menu tab 31a labeled "Menu" is displayed on the upper right of the My Page screen. When the menu tab 31a is operated, a menu screen (not shown) is displayed. The player can configure various settings related to the game on the menu screen.
[0035] As shown in FIG. 3A, the My Page screen displays a formation tab 32a labeled "Formation," a strengthening tab 32b labeled "Strengthening," a gacha tab 32c labeled "Gacha," and a quest tab 32d labeled "Quest."
[0036] When the formation tab 32a is operated, a formation screen (not shown) is displayed. On the formation screen, a party to be used in a quest battle can be formed. A party is formed with main members who are starting members in a battle, and sub-members who are substitutes. The main members are formed with a total of four characters, the main character and three sub-characters. The sub-members are formed with two sub-characters. In a battle, if any of the main member characters becomes unable to fight, a sub-character from the sub-members will be added to the battle. Note that the contents of the party formation are not limited to this example, and any formation may be used. Also, the player can equip the main character with a weapon on the formation screen.
[0037] When the strengthen tab 32b is operated, a strengthening screen (not shown) is displayed. On the strengthening screen, the player can strengthen the weapon he or she possesses according to a predetermined rule.
[0038] When the gacha tab 32c is operated, a gacha screen (not shown) is displayed. On the gacha screen, a weapon can be acquired by lottery by consuming in-game currency. In addition, when a specific type of weapon is acquired for the first time, a sub-character corresponding to the specific type of weapon can be acquired. The acquired sub-character can be organized into a party.
[0039] As will be described later, one type of quest is a multi-battle quest (hereafter referred to as a multi-battle). In a multi-battle, multiple players can cooperate to battle one enemy character. For example, suppose a first player executes a multi-battle and starts (launches) a new multi-battle. The first player can request help from other players.
[0040] The second player can receive a rescue request from the first player and later join the multi-battle started by the first player. The player who starts a new multi-battle is sometimes called the discoverer, and the player who joins later is sometimes called the rescuer. The number of people who can join together in a multi-battle (discoverer + rescuer) is limited to a certain number (for example, 30 people).
[0041] As shown in FIG. 3A, AP (Active Points) and BP (Battle Points) are displayed near the Quest tab 32d. AP is the points required to execute a quest, and a player consumes AP to execute a quest. For example, AP is consumed when executing a multi-battle as a discoverer. BP is the points required to participate in a multi-battle, and a player can consume BP to participate as a rescuer in a multi-battle started by another player. AP and BP are recovered over time or by consuming a specified item.
[0042] When the quest tab 32d is operated, a quest list screen shown in Fig. 3B is displayed. The quest list screen displays a quest selection tab 33. The quest selection tab 33 displays information related to executable quests.
[0043] Quests include main quests related to the progress of the main story, arbitrarily set free quests, the above-mentioned multi-battles, etc. A quest selection tab 33 is displayed for each executable quest. If there are multiple executable quests, they are displayed side by side at the bottom of the quest list screen. If there are many quests, all of the quests can be displayed by scrolling the quest list screen downwards.
[0044] 3B, a quest selection tab 33a corresponding to a multi-battle is displayed with "Multi Battle" written in the banner. When any quest selection tab 33 is operated, the quest corresponding to the operated quest selection tab 33 is executed. For example, when the quest selection tab 33a corresponding to a multi-battle is operated, a multi-battle is executed as the discoverer.
[0045] 3B, a multi-battle tab 34 labeled "multi-battle" is displayed on the quest list screen. The multi-battle tab 34 is located, for example, above the top quest selection tab 33 on the screen.
[0046] Fig. 4A is a diagram showing an example of a rescue request list screen. Fig. 4B is a diagram showing an example of a multi-battle list screen. Fig. 4C is a diagram showing an example of a multi-battle selection screen. When the multi-battle tab 34 in Fig. 3B is operated, the rescue request list screen shown in Fig. 4A is displayed.
[0047] The rescue request list screen is provided with a new arrivals tab 35a and a rescue search tab 35b. The new arrivals tab 35a and the rescue search tab 35b function as operation units that accept operations by the player. When the new arrivals tab 35a is selected, the rescue request list screen shown in FIG. 4A is displayed. When the rescue search tab 35b is operated while the rescue request list screen is displayed, a rescue search screen, which will be described later, is displayed.
[0048] On the rescue request list screen, a game information display area 35c is provided below a new arrival tab 35a and a rescue search tab 35b. A multi-battle tab 35c1 and an event tab 35c2 are provided above the game information display area 35c.
[0049] In the game information display area 35c, game information is displayed that indicates a multi-battle that another player has started and in which the player can participate. The game information includes various information related to the multi-battle. In the example of FIG. 4A, no game information is displayed in the game information display area 35c, indicating that there is no multi-battle in which the player can participate.
[0050] Multi-battles are broadly divided into normal multi-battles that players can play at any time, and event multi-battles that are only provided during an event period. When the multi-battle tab 35c1 is operated, game information corresponding to the normal multi-battle is displayed in the game information display area 35c. When the event tab 35c2 is operated, game information corresponding to the event multi-battle is displayed in the game information display area 35c. In the game information display area 35c, game information corresponding to the latest multi-battle among the multi-battles in which the player can participate as a rescuer is displayed.
[0051] In addition, on the rescue request list screen, the new arrivals tab 35a is highlighted more than the rescue search tab 35b, so that it is possible to identify that the new arrivals tab 35a is selected. In addition, while the rescue request list screen is being displayed, the currently selected tab is highlighted out of the multi-battle tab 35c1 and the event tab 35c2.
[0052] 4A, an ID input button 35d is provided on the rescue request list screen. When the ID input button 35d is operated, an ID input screen (not shown) is displayed. When any player initiates a multi-battle and then issues a rescue request, a multi-battle ID associated with the initiated multi-battle is acquired. Each player can also participate in a multi-battle by directly inputting a multi-battle ID into the ID input screen.
[0053] Also, as shown in Fig. 4A, a multi-battle list button 35e is displayed on the rescue request list screen. When the multi-battle list button 35e is operated, the multi-battle list screen shown in Fig. 4B is displayed. As shown in Fig. 4B, the multi-battle list screen displays a normal selection tab 36b marked "NORMAL" and a high level selection tab 36c marked "HIGH LEVEL."
[0054] When the normal selection tab 36b is operated, a difficulty level selection tab 36d for multi-battles classified as the normal class is displayed. On the other hand, when the high level selection tab 36c is operated, a difficulty level selection tab 36d for multi-battles classified as the high level class is displayed. In the example of FIG. 4B, the difficulty level selection tab 36d for the normal class is displayed. In the high level class, enemy characters are set stronger than in the normal class. The difficulty level of the difficulty selection tabs 36d is indicated by the number of stars, and multiple tabs are displayed according to difficulty level. The higher the difficulty level, the stronger the enemy characters are set.
[0055] When the difficulty level selection tab 36d is operated, a multi-battle selection screen shown in Fig. 4C is displayed. The multi-battle selection screen is displayed with content corresponding to the difficulty level selected in the operated difficulty level selection tab 36d.
[0056] As shown in FIG. 4C, the multi-battle selection screen displays a multi-battle selection tab 37a. The multi-battle selection tab 37a is displayed for each type of multi-battle. In addition, the multi-battle selection screen displays a multi-battle challenge tab 37b marked "Challenge" for each multi-battle selection tab 37a. When the multi-battle challenge tab 37b is operated, the multi-battle corresponding to the multi-battle challenge tab 37b is executed as the discoverer. In addition, the multi-battle selection screen displays a cancel tab 37c marked "Close." When the cancel tab 37c is operated, the user can return to the multi-battle list screen.
[0057] In addition, on the multi-battle selection screen, information in the multi-battle selection tab 37a of a multi-battle that cannot be executed (not yet released) may be made undisclosed. Also, on the multi-battle selection screen, operations on the multi-battle challenge tab 37b of a multi-battle that cannot be executed (not yet released) may be disabled.
[0058] Fig. 5A shows an example of a My Page screen when a rescue request is received from another player. Fig. 5B shows an example of a quest list screen when a rescue request is received from another player. Fig. 5C shows an example of a rescue request list screen when a rescue request is received from another player.
[0059] As shown in FIG. 5A, when a rescue request is received from another player, a multi-battle rescue reception tab 38 labeled "Multi Battle" is additionally displayed on the My Page screen.
[0060] Also, as shown in FIG. 5B, when there is a request for help from another player, the frame of the multi-battle tab 34 marked "multi-battle" is highlighted on the quest list screen so as to be distinguishable from when there is no request for help.
[0061] When the multi-battle rescue reception tab 38 shown in FIG. 5A is operated, or when the highlighted multi-battle tab 34 shown in FIG. 5B is operated, a rescue request list screen is displayed as shown in FIG. 5C. When there is a rescue request from another player, a multi-battle participation tab 39 is displayed in the game information display area 35c. The multi-battle participation tab 39 displays game information related to the multi-battle. In other words, the rescue request includes game information.
[0062] Here, as game information, an image indicating the type of multi-battle, the class, the difficulty level, the name of the multi-battle, i.e., the quest name, the remaining HP of the enemy character at the time of the rescue request, and the BP required for participation are displayed in the multi-battle participation tab 39. Note that the game information displayed in the multi-battle participation tab 39 is not limited to this. For example, the game information may include information about the player participating in the multi-battle, and information about the ally character or enemy character. Also, for example, the remaining HP of the enemy character may be displayed variably in real time in the multi-battle participation tab 39.
[0063] When the multi-battle participation tab 39 is operated, the player can participate as a rescuer in the multi-battle of another player who has issued a rescue request. Although a detailed explanation is omitted, when the multi-battle participation tab 39 is operated, a party formation screen is displayed. After forming a party on the party formation screen, the player can participate in the multi-battle using the formed party.
[0064] Here, in this embodiment, as described above, many types of multi-battles with different difficulty levels, enemy characters, etc. are provided. If many multi-battle participation tabs 39 are displayed in the game information display area 35c, the operation for the player to search for a desired multi-battle becomes complicated. Therefore, in this embodiment, a rescue search setting function is provided that allows each player to set in advance the rescue request that he or she wants to receive. The rescue search setting function will be described in detail below.
[0065] FIG. 6A is a first diagram illustrating an example of a rescue search screen. FIG. 6B is a second diagram illustrating an example of a rescue search screen. FIG. 6C is a third diagram illustrating an example of a rescue search screen. When the rescue search tab 35b is operated on the rescue request list screen, the rescue search screen shown in FIG. 6A is displayed. On the rescue search screen, similar to the rescue request list screen, a new arrival tab 35a, a rescue search tab 35b, a game information display area 35c, an ID input button 35d, and a multi-battle list button 35e are displayed.
[0066] However, on the rescue search screen, instead of the multi-battle tab 35c1 and the event tab 35c2 displayed on the rescue request list screen, a first setting tab 35b1, a second setting tab 35b2, a third setting tab 35b3, and a search setting button 35f are displayed. Each player can set three patterns of search conditions for rescue requests in advance. Hereinafter, the pattern of search conditions will be referred to as a search pattern. When the search conditions are set, rescue requests are searched according to the set search conditions. Then, when rescue requests that match the search conditions are extracted, the extracted rescue requests are displayed on the rescue search screen for each search pattern.
[0067] Fig. 7A is a diagram for explaining an example of a search setting screen. Fig. 7B is a diagram for explaining an example of a rescue setting screen. For example, when the search setting button 35f is operated on the rescue search screen shown in Fig. 6A, the search setting screen shown in Fig. 7A is displayed. The search setting screen displays a setting display area 40. The setting display area 40 is provided with a first setting button 41a, a second setting button 41b, and a third setting button 41c.
[0068] The first setting button 41a corresponds to the first search pattern among three search patterns that the player can set. Similarly, the second setting button 41b corresponds to the second search pattern, and the third setting button 41c corresponds to the third search pattern. Note that the first search pattern, the second search pattern, and the third search pattern can also be referred to as the first search condition, the second search condition, and the third search condition, respectively.
[0069] The player can select a search pattern to be set by operating the first setting button 41a, the second setting button 41b, and the third setting button 41c displayed in the setting display area 40. For example, the player can set a first search pattern by operating the first setting button 41a. In this case, the player can set the first search pattern, i.e., the first search condition.
[0070] In this embodiment, the player can set three types of multi-battles for one search pattern. In other words, three search frames are provided for each of the three search patterns, and the player can set a type of multi-battle for each of the three search frames for each search pattern.
[0071] 8 is a diagram illustrating a search pattern storage unit. The storage device 12 of the player terminal 1 and the storage device 112 of the server 100 are provided with a search pattern storage unit. The search pattern storage unit may be provided in the storage device 18 of the player terminal 1 and the storage device 118 of the server 100. The search pattern storage unit includes a first search pattern storage unit, a second search pattern storage unit, and a third search pattern storage unit. The first search pattern storage unit, the second search pattern storage unit, and the third search pattern storage unit are provided with a first setting frame, a second setting frame, and a third setting frame, respectively.
[0072] That is, as shown in FIG. 8, the search pattern storage unit is provided with nine storage areas. A content ID is stored in each storage area. The content ID is identification information provided for each quest, i.e., for each type of multi-battle. The content ID differs for each quest, and further for each class and difficulty level of each quest. In other words, the content ID is linked to any one of quests with different contents. The player can set up to three content IDs for each search pattern.
[0073] 7A, three battle information display sections 42 are provided in the setting display area 40. The upper, middle, and lower battle information display sections 42 displayed in the setting display area 40 correspond to the first setting frame, the second setting frame, and the third setting frame, respectively. For example, when the first setting button 41a is operated, game information indicating the quests (multi-battles) set in each setting frame of the first search pattern is displayed in the battle information display sections 42.
[0074] The game information displayed in the battle information display section 42 is linked to the content ID set by the player in the setting frame. Here, the game information displayed in the battle information display section 42 includes an icon linked to the quest (multi-battle) and the name of the quest.
[0075] In the example shown in Fig. 7A, "Not Set" is displayed in the middle battle information display section 42. This indicates that no content ID has been set in the second setting frame of the first search pattern storage section.
[0076] Furthermore, for example, when the second setting button 41b or the third setting button 41c is operated, game information corresponding to the content IDs included in the second search pattern or the third search pattern is displayed in the battle information display section 42. At this time, in the setting display area 40, the selected button among the first setting button 41a, the second setting button 41b, and the third setting button 41c is highlighted.
[0077] A delete button 43 is provided to the right of the battle information display section 42 where the game information is displayed. When the delete button 43 is operated, the content ID corresponding to the game information displayed to the left of it is deleted from the search pattern storage section.
[0078] Furthermore, when the battle information display section 42 of the setting display area 40 is operated, a rescue setting screen shown in Fig. 7B is displayed. On the rescue setting screen, like the multi-battle list screen described above, a normal selection tab 36b, a high level selection tab 36c, and a difficulty level selection tab 36d are displayed. On the rescue setting screen, the player can select the type of multi-battle for which he or she wishes to receive a rescue request, i.e., the content ID.
[0079] For example, suppose that the first setting button 41a is operated in the setting display area 40 to select the first search pattern, and then the lower battle information display section 42 is operated. In this case, the content ID selected on the rescue setting screen is stored in the third setting frame of the first search pattern storage section. Also, suppose that the third setting button 41c is operated in the setting display area 40 to select the third search pattern, and then the middle battle information display section 42 is operated. In this case, the content ID selected on the rescue setting screen is stored in the second setting frame of the third search pattern storage section.
[0080] As described above, the player can set the type of multi-battle in which a rescue request is to be received from the search setting screen. Here, the player can set three search patterns, i.e., three search conditions. However, the number of search conditions that the player can set may be one, two, four or more. Here, the player can set up to three content IDs for one search pattern. However, the number of content IDs that can be included in one search pattern may be one, two, four or more.
[0081] Returning to Fig. 6A, when the first setting tab 35b1 is operated on the rescue search screen, a list of multi-battle participation tabs 39 corresponding to multi-battles that match the first search pattern, i.e., the first search conditions, is displayed. Similarly, when the second setting tab 35b2 is operated, a list of multi-battle participation tabs 39 corresponding to multi-battles that match the second search conditions is displayed, as shown in Fig. 6B. Furthermore, when the third setting tab 35b3 is operated, a list of multi-battle participation tabs 39 corresponding to multi-battles that match the third search conditions is displayed, as shown in Fig. 6C.
[0082] The player can participate in a multi-battle as a rescuer in the same manner as described above by operating the multi-battle participation tab 39 displayed on the rescue search screen. Note that if a search pattern for which no content ID is set is selected, the multi-battle participation tab 39 is not displayed, and a message indicating that the search conditions have not been set is displayed, as shown in FIG. 6C.
[0083] Here, when the first setting tab 35b1 is operated on the rescue setting screen, a request to extract a multi-battle that matches the first search condition is sent to the server 100. When the second setting tab 35b2 is operated, a request to extract a multi-battle that matches the second search condition is sent to the server 100, and when the third setting tab 35b3 is operated, a request to extract a multi-battle that matches the third search condition is sent to the server 100. The server 100 searches for and extracts multi-battles in accordance with the received extraction request. The player terminal 1 displays a multi-battle participation tab 39 based on the search results in the server 100.
[0084] That is, here, only the multi-battle rescue request corresponding to the tab operated by the player among the first setting tab 35b1, the second setting tab 35b2, and the third setting tab 35b3 is displayed. In other words, the player can confirm receipt of a multi-battle rescue request that matches any of the three search conditions by operating a tab. However, when the player terminal 1 communicates with the server 100, multi-battle rescue requests that correspond to all three search patterns may be searched for and extracted.
[0085] Furthermore, an individual reload button 35g is provided in the game information display area 35c. When the individual reload button 35g is operated, an extraction request corresponding to the currently selected tab among the first setting tab 35b1, the second setting tab 35b2, and the third setting tab 35b3 is transmitted to the server 100. That is, when the player operates the individual reload button 35g, a multi-battle participation tab 39 corresponding to the latest battle game that matches the currently selected search criteria is displayed.
[0086] Furthermore, the multi-battle participation tab 39 is updated when the reload tab 30b of the frame bar 30 is operated. When the reload tab 30b is operated, a request to extract multi-battles that match the three search conditions may be sent. Alternatively, similar to the individual reload button 35g, only a request to extract multi-battles that match the currently selected search conditions may be sent.
[0087] Here, the player can set the above-mentioned normal multi-battle and event multi-battle as search conditions. However, the multi-battle that can be set as a search condition may be only one of normal multi-battle and event multi-battle. In addition, the rescue list screen displays a multi-battle participation tab 39 corresponding to the latest multi-battle in which a rescue request was sent, regardless of the search pattern set by the player.
[0088] In other words, among the multi-battles in which the player can participate, rescue requests that match the search conditions set by the player will be displayed on the rescue search screen shown in Figure 6A, and the most recent rescue requests that do not match the search conditions set by the player will be displayed on the rescue request list screen shown in Figure 5C.
[0089] In addition to the event period, a campaign period may be set. During the campaign period, the AP or BP required to play the campaign quest may be reduced, or the rewards may be increased. During the campaign period, the campaign icon 35h is displayed on the multi-battle participation tab 39 of the campaign quest, as shown in FIG. 6A.
[0090] As described above, in this embodiment, a player can set the type of multi-battle for which he / she wants to receive a rescue request as a search condition. Then, game information corresponding to the received rescue request is displayed for each set search condition. This allows each player to participate in the multi-battle as a rescuer without the need for complicated operations, improving convenience.
[0091] In this case, different content IDs are associated with the same quests of different difficulty levels (quests with common settings other than difficulty level). However, a common content ID may be associated with the same quests of different difficulty levels. In this case, rescue requests of different difficulty levels corresponding to the content IDs included in the search conditions can be received. Also, for example, the difficulty level may be set as a search condition separately from the content ID. In this case, it is preferable that a rescue request that matches both the set content ID and the set difficulty level is received.
[0092] Next, an example of a case where a multi-battle is conducted as the discoverer will be described.
[0093] FIG. 9A is a diagram showing an example of a rescue request screen. FIG. 9B is a diagram showing an example of a rescue request completion screen. FIG. 9C is a diagram showing an example of a battle screen. When the quest selection tab 33a showing the multi-battle in the quest list screen shown in FIG. 3B is operated, or the multi-battle challenge tab 37b in the multi-battle selection screen shown in FIG. 4C is operated, the battle screen shown in FIG. 9C is displayed. When the battle screen is displayed, it is immediately switched to the rescue request screen shown in FIG. 9A. In the rescue request screen, the player can set the range of players who will issue a rescue request.
[0094] 9A, the rescue request screen displays a general selection checkbox 50a marked "Everyone," a friend selection checkbox 50b marked "Friends," and a guild selection checkbox 50c marked "Guild." The rescue request screen also displays a rescue request sending tab 50d marked "Rescue request" and a cancel tab 50e marked "Cancel."
[0095] A friend is a player who has registered a certain number of friends with the player among other players in the game. A player can register up to a certain number of friends that correspond to his / her rank. A player's rank can be increased by clearing quests. The certain number of people that can be registered as friends increases as the rank increases. A guild is a group made up of multiple players in the game. By joining a guild, a player can cooperate with other players in the guild to challenge quests.
[0096] When the overall selection check box 50a is operated, the overall selection check can be switched between on and off. When the rescue request transmission tab 50d is operated while the overall selection check box 50a is in the on state, a player for whom a search condition including a content ID linked to the started multi-battle is set is randomly selected from all players. Then, a rescue request is sent to the selected player. In this case, the randomly selected player can participate in the started multi-battle.
[0097] As another example, the player to whom the rescue request is to be sent may be extracted regardless of the search conditions set by each player. In this case, when communication is established between the player terminal 1 of the player set as the destination of the rescue request and the server 100, it may be determined whether the rescue request matches the search conditions. Then, the server 100 may allow only players determined to match the search conditions to receive the rescue request.
[0098] When the friend selection check box 50b is operated, the friend selection check can be switched on and off. When the rescue request transmission tab 50d is operated while the friend selection check box 50b is in the on state, a rescue request is transmitted to the player's friends. In this case, the player who transmitted the rescue request and the players who are registered as friends can participate in the started multi-battle.
[0099] In addition, here, when a friend is selected as the destination of the rescue request, the rescue request is sent regardless of the search condition settings of the player who is registered as a friend. In other words, each player may receive a rescue request from a player who is registered as a friend that does not match the search condition that the player has set. If the received rescue request does not match the search condition of the player, the rescue request may be displayed on the rescue list screen shown in FIG. 5C. However, the rescue request may be sent only to players who are registered as friends and who have search conditions set that include the content ID linked to the started multi-battle.
[0100] When the guild selection check box 50c is operated, the guild selection check can be switched on and off. When the rescue request sending tab 50d is operated while the guild selection check box 50c is in the on state, a rescue request is sent to players in the guild to which the player belongs. In this case, players in the guild to which the player who sent the rescue request belongs can participate in the multi-battle of the player who sent the rescue request.
[0101] In addition, here, when a guild is selected as the destination of the rescue request, the rescue request is sent regardless of the search conditions set by the players in the guild. In other words, each player may receive a rescue request from a player in the same guild that does not match the search conditions set by the player. If the received rescue request does not match the search conditions of the player, the rescue request may be displayed on the rescue list screen shown in FIG. 5C as described above. However, the rescue request may be sent only to players in the same guild who have search conditions set that include the content ID linked to the started multi-battle.
[0102] The rescue request tab 50d may be operated with the all selection checkbox 50a, the friend selection checkbox 50b, and the guild selection checkbox 50c all in an on state. In this case, a rescue request is sent to each of a player randomly selected from all players, a player registered as a friend, and a player in the guild to which the player belongs.
[0103] When the rescue request sending tab 50d shown in Fig. 9A is operated to complete the sending of the rescue request, a rescue request completion screen shown in Fig. 9B is displayed. When the OK tab 50f marked "OK" is operated on the rescue request completion screen, the screen is switched to a battle screen shown in Fig. 9C.
[0104] Also, when the cancel tab 50e shown in Fig. 9A is operated, a rescue request is not made, and the screen switches to the battle screen shown in Fig. 9C, allowing the player to fight alone. Note that if a predetermined time has passed since the start of a battle without a rescue request being made, or if a rescue request is made but no rescuer is available even after a predetermined time has passed, the rescue request screen may be displayed again when the predetermined time has passed.
[0105] 9A, an SNS tab 50g is provided on the rescue request screen. When the SNS tab 50g is operated, a posting screen (not shown) is displayed and information that can be posted to a social network service (SNS) is generated. The information generated at this time includes, for example, a multi-battle ID. On the posting screen, the player can transmit the multi-battle ID of the started multi-battle to the outside via the SNS.
[0106] In this case, the SNS tab 50g is provided separately from the rescue request sending tab 50d. That is, the player can select whether to send a rescue request to other players within the game system or to send a rescue request to other players using an SNS outside the game. However, the SNS tab 50g is not essential. For example, when the rescue request sending tab 50d is operated, a rescue request may be sent via an SNS at the same time.
[0107] Furthermore, the method of sending a rescue request to other players using the SNS is not particularly limited, and any known technology can be applied. For example, the posted information may be sent directly to the SNS server by the game application. Also, for example, when a player switches the game application to an application for the SNS on the player terminal 1 and then performs a posting operation on the SNS application, the posted information may be sent to the SNS server.
[0108] As shown in Fig. 9C, in the upper half of the battle screen, ally characters 51a and enemy characters 51b are displayed. At the start of a battle, main members of the party are displayed as ally characters 51a. Fig. 9C also illustrates a case where there is one enemy character 51b.
[0109] Each enemy character 51b and each ally character 51a is set with a parameter value (e.g., HP value) related to life (or physical strength) (specifically, HP (hit points)). When the HP value of the enemy character 51b decreases and reaches a predetermined limit value (e.g., 0), the enemy character 51b disappears (is removed from the screen).
[0110] When all enemy characters 51b on the battle screen are eliminated, the battle is won and the quest is cleared. By clearing the quest, the player is given a reward. Also, when the HP value of any character among the ally characters 51a reaches a predetermined limit value (for example, 0), that character becomes unable to fight. The character that is unable to fight is removed from the battle screen, and if there is a sub-member, the sub-member appears on the battle screen.
[0111] The survival or disappearance of the enemy character 51b may be determined not only based on the HP value but also based on, for example, an HP ratio (parameter ratio) indicating the ratio of the remaining HP value to the maximum HP value. The HP ratio indicates the ratio of the remaining HP and may be expressed as a percentage. For example, when the HP ratio of the enemy character 51b decreases and reaches a ratio corresponding to a limit value (for example, 0%), the enemy character 51b may be disappeared.
[0112] Furthermore, the parameter relating to the life of the enemy character 51b is not limited to HP, and may be, for example, damage received by the enemy character 51b. In this case, the survival or disappearance of the enemy character 51b may be determined based on a total damage value obtained by accumulating the damage received. For example, when the total damage value of the enemy character 51b increases and reaches a predetermined limit value (for example, a value corresponding to the maximum value of HP), the enemy character 51b may be disappeared.
[0113] Furthermore, the survival or disappearance of the enemy character 51b may be determined based on a total damage ratio indicating a ratio of the total damage value to the maximum value of HP. The total damage ratio may be expressed as a percentage. For example, when the total damage ratio of the enemy character 51b increases and reaches a ratio corresponding to a limit value (for example, 100%), the enemy character 51b may disappear.
[0114] 9C, an attack input tab 52 labeled "attack" is displayed on the battle screen. The attack input tab 52 is disposed, for example, below the screen of the ally character 51a. The attack input tab 52 receives an input indicating a player's action (for example, an attack).
[0115] Basically, the multi-battle proceeds in a turn-based manner. When the attack input tab 52 is operated, the ally character 51a attacks the enemy character 51b, and then the enemy character 51b takes action, and one turn passes. When the ally character 51a attacks the enemy character 51b, the HP value of the enemy character 51b changes based on the attack.
[0116] When the enemy character 51b attacks the ally character 51a, the HP value of the ally character 51a changes based on the attack. After that, no turn passes until the attack input tab 52 is next operated, and the enemy character 51b does not perform any action during that time.
[0117] In addition, in the lower half of the battle screen, an ability selection tab 53a, a summoned beast selection tab 53b, and a recovery tab 53c labeled "Recovery" are displayed. The ability selection tab 53a is displayed for each ally character 51a displayed in the upper half of the screen. When the ability selection tab 53a is operated and the type of ability to be activated is determined, the determined ability is activated by the ally character 51a. When an ability is activated, a special effect due to the activated ability is given to the enemy character 51b or the ally character 51a. The number of turns from when the ability is activated once until it can be activated again is set for the ability. Also, unlike input in the attack input tab 52, the enemy character 51b does not take action at the timing of activation of the ability.
[0118] When the summoned beast selection tab 53b is operated to select the summoned beast to be summoned, the selected summoned beast is summoned. When the summoned beast is summoned, an attack by that summoned beast is given to the enemy character 51b. The summoned beast can be summoned when a predetermined condition is met, such as the passage of a predetermined number of turns. Also, unlike inputs made through the attack input tab 52, the enemy character 51b does not take action at the time of summoning the summoned beast.
[0119] When the recovery tab 53c is operated and a recovery item to be used is determined, the determined recovery item recovers the HP value of the ally character 51a. Unlike inputs made through the attack input tab 52, the recovery made through the recovery tab 53c does not cause the enemy character 51b to take action at the time of the operation.
[0120] Below the recovery tab 53c on the screen, a contribution display area 54 is formed. In the contribution display area 54, contribution information such as the contribution or ranking among one or more players in the multi-battle is displayed. When the player in the multi-battle is the only player (e.g., PY1), only the contribution information of the player in the multi-battle is displayed. When there are multiple players in the battle, the contribution information of the player in the multi-battle and the contribution information of the top two players among the other players in the multi-battle are displayed.
[0121] As shown in FIG. 9C, an HP gauge 55 of the enemy character 51b is displayed at the top of the battle screen. The HP gauge 55 is an image showing the HP ratio of the enemy character 51b. The HP gauge 55 is displayed in a bar shape extending in the left-right direction of the screen. The HP gauge 55 is displayed in a predetermined color. The predetermined color is, for example, red, but can be set to any color. The left end of the HP gauge 55 on the screen corresponds to the HP ratio corresponding to the limit value (for example, 0%). In FIG. 9C, the HP gauge 55 is displayed when the HP ratio is 100%. As the HP ratio decreases, the right end of the HP gauge 55 on the screen moves to the left side of the screen, and the length of the HP gauge 55 is shortened. By displaying the HP gauge on the battle screen, the player can easily recognize the state of the HP of the enemy character 51b.
[0122] The actions of the enemy character 51b are broadly divided into normal actions and special actions. Actions other than the special actions are all considered to be normal actions. The special actions have characteristics such as being stronger than the normal actions, having a wider attack range, or having a larger number of attacks.
[0123] The special action is managed in association with the parameter value (e.g., HP value) or parameter ratio (a ratio based on the maximum parameter value, e.g., HP ratio) of the enemy character 51b. The special action is executed based on the satisfaction of a specific condition. The specific condition may be, for example, that the attack input tab 52 is operated and the parameter value or parameter ratio of the enemy character 51b reaches a preset specific value.
[0124] Although not shown in the figures, let us assume that a second player (PY2) joins a multi-battle in response to a rescue request from a first player (PY1). In this case, a pop-up such as "PY2 has joined the battle" is displayed on the battle screen of the player terminal 1 to inform the player that a rescuer has been added.
[0125] Furthermore, when the attack input tab 52 is operated on the player terminal 1 of the second player, the ally character 51a of the second player attacks the enemy character 51b, and the HP value of the enemy character 51b changes. Then, on the player terminal 1 of the first player, even if the first player does not perform an attack input, the HP gauge 55 of the enemy character 51b changes in real time based on the attack input of the second player.
[0126] In a multi-battle, when any player activates an ability, all players may enjoy the effect of the ability. For example, suppose that the second player (PY2) activates an ability that weakens the enemy character 51b. In this case, a pop-up explaining the effect of the activated ability is displayed on the battle screen of the other players (e.g., the first player) in the battle. Then, not only the second player but also the other players (e.g., the first player) in the battle can proceed with the battle with the enemy character 51b in a weakened state.
[0127] Note that the game content of the multi-battle and the method of displaying the game screen are merely examples. In any case, as long as multiple players can participate, the game content is not particularly limited.
[0128] The following describes the processes of the player terminal 1 and the server 100 for implementing the above game, and the functional units that execute these processes. Note that the following describes the processes related to the rescue request in particular, and omits descriptions of other processes.
[0129] (Functional parts of player terminal 1) 10 is a functional block diagram of the player terminal 1. A program storage area 12a and a data storage area 12b are provided in the storage device 12 of the player terminal 1. When the game starts or the browser is launched, the CPU 10 stores a program (module) for controlling the browser in the program storage area 12a.
[0130] The programs that control the browser include a communication control program 70, a multi-battle control program 71, a search setting program 72, a rescue request program 73, and a game information display program 74. Note that the programs listed in Fig. 10 are just examples, and many other programs are provided as programs that control the browser.
[0131] The CPU 10 runs each program stored in the program storage area 12a and updates data in each storage unit in the data storage area 12b. The CPU 10 runs each program stored in the program storage area 12a, causing the player terminal 1 (computer) to function as a terminal control unit 1A. That is, the player terminal 1 is an information processing device equipped with the terminal control unit 1A that executes the processing of various information processing programs. The terminal control unit 1A includes a communication control unit 70a, a multi-battle control unit 71a, a search setting unit 72a, a rescue request unit 73a, and a game information display unit 74a.
[0132] Specifically, the CPU 10 runs a communication control program 70, causing the computer to function as a communication control unit 70a. Similarly, the CPU 10 runs a multi-battle control program 71, a search setting program 72, a help request program 73, and a game information display program 74, causing the computer to function as a multi-battle control unit 71a, a search setting unit 72a, a help request unit 73a, and a game information display unit 74a, respectively.
[0133] The data storage area 12b is provided with a player information storage area 80 and a search pattern storage area 81 as storage areas for storing data. Note that the above-mentioned storage areas are merely examples, and the data storage area 12b is provided with many other storage areas.
[0134] The player information storage unit 80 stores various pieces of information related to the player, such as the player ID.
[0135] 8, the search pattern storage unit 81 includes a first search pattern storage unit, a second search pattern storage unit, and a third search pattern storage unit. As described above, each of these storage units includes a first setting frame, a second setting frame, and a third setting frame. In each setting frame of each storage unit, a content ID selected by a player is stored.
[0136] The communication control unit 70a transmits and receives information to and from the server 100. For example, the communication control unit 70a transmits predetermined request information based on an operation by a player to the server 100, and receives information from the server 100 in response to the transmitted request information.
[0137] The multi-battle control unit 71a cooperates with the server 100 to control the execution of the multi-battle in response to the player's operation or the progress of the game. For example, the multi-battle control unit 71a displays an image based on information received from the server 100 on the display 26. In other words, the multi-battle control unit 71a executes a multi-player game of a content ID selected by a player.
[0138] The search setting unit 72a stores a content ID in the search pattern storage unit 81 based on the operation input of the player. In other words, the search setting unit 72a associates the content ID selected by the player with one of the multiple storage units. In addition, the search setting unit 72a accepts operations on the first setting tab 35b1, the second setting tab 35b2, the third setting tab 35b3, and the search setting button 35f on the rescue search screen. In other words, the search setting unit 72a accepts the player's operation to select one of the multiple storage units.
[0139] The rescue request unit 73a issues a rescue request within the game or via an SNS based on the player's operation input. That is, the rescue request unit 73a requests the server 100 to generate a rescue request including game information and to transmit the rescue request to other players.
[0140] The game information display unit 74a displays various images on the display 26 based on the information received from the server 100. For example, when the game information display unit 74a receives a rescue request, it displays the game information included in the rescue request in the multi-battle participation tab 39. That is, the game information display unit 74a displays, from among the acquired game information, game information including a content ID associated with the storage unit selected by the player.
[0141] (Functional part of server 100) Fig. 11 is a functional block diagram of the server 100. The storage device 112 of the server 100 is provided with a program storage area 112a and a data storage area 112b. The program storage area 112a stores a game execution control program 170, a communication control program 171, a rescue request search program 172, a game information generation program 173, and a post information generation program 174. Note that the programs listed in Fig. 11 are just examples, and many other programs are stored in the program storage area 112a.
[0142] The CPU 110 runs each program stored in the program storage area 112a and updates data in each storage unit in the data storage area 112b. The CPU 110 runs each program stored in the program storage area 112a, causing the server 100 (computer) to function as a server control unit 100A. That is, the server 100 is an information processing device equipped with a server control unit 100A that executes the processing of various information processing programs. The server control unit 100A includes a game execution control unit 170a, a communication control unit 171a, a rescue request search unit 172a, a game information generation unit 173a, and a posting information generation unit 174a.
[0143] Specifically, the CPU 110 runs a game execution control program 170, causing the computer to function as a game execution control unit 170a. Similarly, the CPU 110 runs a communication control program 171, a rescue request search program 172, a game information generation program 173, and a post information generation program 174, causing the computer to function as a communication control unit 171a, a rescue request search unit 172a, a game information generation unit 173a, and a post information generation unit 174a, respectively.
[0144] The data storage area 112b includes, as storage units for storing data, a game information storage unit 180, a player information storage unit 181, and a battle log storage unit 182. Note that the above storage units are merely examples, and the data storage area 112b includes many other storage units.
[0145] The game information storage unit 180 stores various information related to the progress of the game, such as the progress status of the game. The player information storage unit 181 stores various information related to each player. The player information storage unit 181 also includes a search pattern storage unit.
[0146] The battle log storage unit 182 stores battle logs for multi-battles, etc. For example, the battle log storage unit 182 may store rescue request destination information that specifies a player who is the destination of a rescue request in association with the multi-battle from which the rescue request originates, and battle participation information that specifies a player who accepted the rescue request and participated in the multi-battle.
[0147] The game execution control unit 170a controls the progress of the entire game. For example, the game execution control unit 170a updates the game information of the entire game based on reception of various information indicating the input operation of the player to the player terminal 1. Furthermore, when the game information of the entire game is updated, the game execution control unit 170a generates display information based on the updated game information and causes the player terminal 1 to receive the display information via the communication control unit 171a.
[0148] Furthermore, the game execution control unit 170a controls the execution of the multi-battle in cooperation with the multi-battle control unit 71a of the player terminal 1. For example, the game execution control unit 170a allows the player to participate in a multi-player game corresponding to game information selected by the player from among game information acquired by the player.
[0149] The communication control unit 171a transmits and receives information to and from the player terminal 1. For example, the communication control unit 171a receives from the player terminal 1 predetermined request information based on the operation of the player, and causes the player terminal 1 to receive display information generated based on the received information. In addition, the communication control unit 171a causes the player to obtain one or more pieces of game information including a content ID selected by the player, i.e., a rescue request.
[0150] When the reception of a rescue request is confirmed from the player terminal 1, the rescue request search unit 172a searches for a rescue request that matches the search conditions set by the player.
[0151] The game information generating unit 173a generates game information when a rescue request is generated and transmitted. The rescue request generated by the game information generating unit 173a is received by other players by the communication control unit 171a.
[0152] The post information generating unit 174a generates information that can be posted to an SNS based on an operational input by the player.
[0153] (Communication processing between player terminal 1 and server 100) Among the communication processes between the player terminals 1 and the server 100, a part of the processes related to the above-mentioned multi-battle and rescue requests will be described below.
[0154] 12 is a first sequence diagram for explaining the processing of the player terminal 1 and the server 100. In the following explanation, the processing in the player terminal 1 is indicated as Pn (n is any integer). Also, the processing in the server 100 is indicated as Sn (n is any integer). In the following explanation, it is assumed that the player has input an operation to start the game and has completed logging in.
[0155] As shown in FIG. 12, when the Quest tab 32d on the My Page screen shown in FIG. 3A is operated, the communication control unit 70a of the player terminal 1 executes a quest list request process for transmitting quest list request information to the server 100 (P1).
[0156] When the game execution control unit 170a of the server 100 receives the quest request information via the communication control unit 171a, it extracts executable quests based on the player ID and generates quest list screen information that displays the extracted quests (S1). The game execution control unit 170a then causes the player terminal 1 to receive the generated quest list screen information via the communication control unit 171a.
[0157] When the game information display unit 74a of the player terminal 1 receives the quest list screen information via the communication control unit 70a, it executes a quest list screen display process to display a quest list screen on the display 26 based on the received quest list screen information (P2).
[0158] Furthermore, when the multi-battle tab 34 on the quest list screen shown in FIG. 3B is operated, the communication control unit 70a of the player terminal 1 executes a rescue request list request process for transmitting rescue request list request information to the server 100 (P3).
[0159] When the rescue request search unit 172a of the server 100 receives the rescue request list request information via the communication control unit 171a, it generates rescue request list screen information for displaying a rescue request list screen based on the rescue request destination information in the battle log storage unit 182 (S2). Here, if the rescue request destination information includes player information of the sender of the rescue request list request information, the rescue request search unit 172a generates rescue request list screen information for displaying a multi-battle participation tab 39 on the rescue request list screen as shown in FIG. 5C.
[0160] On the other hand, if the rescue request destination information does not include player information of the sender of the rescue request list request information, the rescue request search unit 172a generates rescue request list screen information that does not display the multi-battle participation tab 39 on the rescue request list screen as shown in Fig. 4A. Then, the rescue request search unit 172a causes the player terminal 1 to receive the rescue request list screen information via the communication control unit 171a.
[0161] When the game information display unit 74a of the player terminal 1 receives the rescue request list screen information via the communication control unit 70a, it executes a rescue request list screen display process to display a rescue request list screen on the display 26 based on the received rescue request list screen information (P4).
[0162] Fig. 13 is a second sequence diagram illustrating the processing of the player terminal 1 and the server 100. When the multi-battle list button 35e on the rescue request list screen shown in Fig. 4A is operated, the communication control unit 70a of the player terminal 1 executes a multi-battle list request processing to transmit multi-battle list request information to the server 100 (P5).
[0163] When the game execution control unit 170a of the server 100 receives the multi-battle list request information via the communication control unit 171a, it causes the player terminal 1 to receive multi-battle list screen information, which displays a multi-battle list screen, via the communication control unit 171a (S5).
[0164] When the game information display unit 74a of the player terminal 1 receives the multi-battle list screen information via the communication control unit 70a, it executes a multi-battle list screen display process to display a multi-battle list screen on the display 26 based on the received multi-battle list screen information (P6).
[0165] In addition, when the difficulty level selection tab 36d on the multi-battle list screen shown in Figure 4B is operated, the communication control unit 70a of the player terminal 1 executes a difficulty level selection process to send difficulty level selection information including information on the selected difficulty level to the server 100 (P7).
[0166] When the game execution control unit 170a of the server 100 receives the difficulty level selection information via the communication control unit 171a, it causes the player terminal 1 to receive multi-battle selection screen information via the communication control unit 171a, which displays a multi-battle selection screen corresponding to the selected difficulty level (S6).
[0167] When the game information display unit 74a of the player terminal 1 receives the multi-battle selection screen information via the communication control unit 70a, it executes a multi-battle selection screen display process to display a multi-battle selection screen on the display 26 based on the received multi-battle selection screen information (P8).
[0168] Fig. 14 is a third sequence diagram illustrating the processing of the player terminal 1 and the server 100. When the multi-battle selection tab 37a on the multi-battle selection screen shown in Fig. 4C is operated, the communication control unit 70a of the player terminal 1 executes a multi-battle start request process (P10) for transmitting multi-battle start request information including information specifying the selected multi-battle to the server 100.
[0169] When the game execution control unit 170a of the server 100 receives the multi-battle start request information via the communication control unit 171a, it executes various start settings related to the multi-battle (S10). For example, the game execution control unit 170a performs settings for the enemy character 51b in the multi-battle specified by the multi-battle start request information, initial settings for the HP value of the enemy character 51b, settings for special actions of the enemy character 51b, and the like.
[0170] Next, the game execution control unit 170a executes a battle screen information generation process for generating battle screen information for displaying a battle screen (S11). Here, the game execution control unit 170a causes the player terminal 1 to receive the generated battle screen information via the communication control unit 171a.
[0171] The game information display unit 74a of the player terminal 1 performs a battle screen display process to display a battle screen on the display 26 based on the battle screen information received via the communication control unit 70a (P11).
[0172] Furthermore, the game execution control unit 170a of the server 100 generates rescue request screen information for displaying a rescue request screen after a predetermined time has elapsed since the battle screen information was received by the player terminal 1 in step S12, and causes the player terminal 1 to receive the rescue request screen information (S12). Note that the rescue request screen information may be generated together with the battle screen information in step S12.
[0173] When the game information display unit 74a of the player terminal 1 receives the rescue request screen information via the communication control unit 70a, it executes a rescue request screen display process to display the rescue request screen shown in FIG. 9A on the display 26 based on the received rescue request screen information (P12).
[0174] When the rescue request sending tab 50d on the rescue settings screen is operated, the rescue request unit 73a executes a rescue request information sending process to send rescue request information based on whether the overall selection checkbox 50a is checked, whether the friend selection checkbox 50b is checked, and whether the guild selection checkbox 50c is checked to the server 100 via the communication control unit 70a (P13).
[0175] The rescue request information includes a multi-battle ID that is assigned to the executed multi-battle, a content ID, and a player ID of the player playing the game. The multi-battle ID may be issued at the start of the multi-battle, for example, in S10. Alternatively, the multi-battle ID may be issued at P13 when the rescue request information is sent, or may be issued at S13, which will be described later, when the rescue request information is received.
[0176] When the game execution control unit 170a of the server 100 receives the rescue request information via the communication control unit 171a, it executes a rescue request destination setting process (S13). Here, the game execution control unit 170a identifies a player to whom the rescue request is to be made based on the received rescue request information. Then, the game execution control unit 170a stores rescue request destination information associated with the identified player in the multi-battle from which the rescue request was made in the battle log storage unit 182.
[0177] Here, the game information generating unit 173a generates game information linked to the rescue request destination information. The game information includes a multi-battle ID, a content ID, a player ID of the player who made the rescue request, and a player ID of the player specified as the rescue request destination.
[0178] Here, the player to whom the rescue request is made is specified based on the search conditions set by each player. For example, assume that rescue request information in which the overall selection check box 50a is checked is received. In this case, the player to whom the rescue request is made is randomly selected from among the players whose content IDs included in the rescue request information are stored in the search pattern storage unit.
[0179] However, here, a player to whom a rescue request is to be made may be extracted regardless of the search conditions set by each player, and rescue request destination information may be stored in the battle log storage unit 182.
[0180] Also, here, the game execution control unit 170a causes the player terminal 1 to receive, via the communication control unit 171a, rescue request completion information indicating the completion of the rescue request.
[0181] When the SNS tab 50g on the rescue setting screen is operated, in S13, the post information generating unit 174a generates information that can be posted to the SNS.
[0182] When the game information display unit 74a of the player terminal 1 receives the rescue request completion information via the communication control unit 70a, it executes a rescue request completion screen display process to display the rescue request completion screen shown in FIG. 9B based on the received rescue request completion information (P14).
[0183] Furthermore, when the OK tab 50f on the rescue request completion screen is operated on the player terminal 1, the multi-battle control unit 71a executes a battle screen display process for switching from the rescue request completion screen to a battle screen (P15).
[0184] The player terminal 1 performs a battle execution process for executing a battle by communicating with the server 100 based on an input operation by the player on the battle screen (P16). In addition, the server 100 performs a battle execution process for executing a battle based on information received from the player terminal 1 (S14).
[0185] Fig. 15 is a sequence diagram for explaining the processing of the second player terminal 1 and the server 100. Here, a case will be explained in which the processing shown in Fig. 14 is executed in the first player terminal 1 and the server 100, and the processing shown in Fig. 15 is executed in a second player terminal 1 and the server 100 different from the first player terminal 1. Note that in Fig. 15, the processing executed in the second player terminal 1 is indicated as 2Pn (n is any integer).
[0186] Also, a player who operates the first player terminal 1 is called the first player, and a player who operates the second player terminal 1 is called the second player. The first player differs from the second player in that the first player logs in to the first player terminal 1 and the second player terminal 1 with different player IDs.
[0187] When an operation to select a content ID is input on the search setting screen shown in FIG. 7A or the rescue setting screen shown in FIG. 7B in the second player terminal 1, the search setting unit 72a executes a search setting process (2P20). Here, the search setting unit 72a stores the content ID in the search pattern storage unit 81 based on the operation input by the player. In addition, the search setting unit 72a transmits search setting information to the server 100 based on the stored information in the search pattern storage unit 81. The search setting information includes the content ID stored in the search pattern storage unit 81.
[0188] When the game execution control unit 170a of the server 100 receives the search setting information via the communication control unit 171a, it executes a registration process (S20). Here, the game execution control unit 170a stores a content ID in the search pattern storage unit of the player information storage unit 181 based on the received search setting information.
[0189] Thereafter, it is assumed that the server 100 receives rescue request information from the first player terminal 1 and executes a rescue request destination setting process (S13). Thereafter, it is assumed that the second player terminal 1 executes a predetermined communication process involving communication with the server 100 (2P21). The predetermined communication process is executed, for example, when the reload tab 30b, the first setting tab 35b1, the second setting tab 35b2, or the third setting tab 35b3 is operated. When the predetermined communication process is executed, the communication control unit 70a transmits reception confirmation information to the server 100.
[0190] When the server 100 receives the reception confirmation information, the rescue request search unit 172a executes a rescue request extraction process (S21). Here, the rescue request search unit 172a searches the battle log storage unit 182 and extracts rescue requests in which the second player is specified as the rescue request destination. Then, when a rescue request is extracted, the rescue request search unit 172a causes the second player terminal 1 to receive game information corresponding to the extracted rescue request.
[0191] When multiple rescue requests are extracted, the rescue request search unit 172a causes the second player terminal 1 to receive game information corresponding to the multiple rescue requests. At this time, an upper limit may be set on the number of pieces of game information that the second player terminal 1 can receive.
[0192] Also, as described above, in the rescue request destination setting process (S13), the player to whom the rescue request is to be made may be determined regardless of the search conditions set by each player when rescue request information is received from the first player terminal 1. In this case, in the rescue request extraction process (S21), the second player terminal 1 receives only game information corresponding to rescue requests including the content ID stored in the search pattern storage unit, among the rescue requests for which the second player has been determined as the player to whom the rescue request is to be made.
[0193] When the second player terminal 1 receives the game information, the game information display unit 74a executes a game information display process to display the game information in the multi-battle participation tab 39 (2P22). For example, an upper limit may be set on the number of multi-battle participation tabs 39, i.e., game information to be displayed. In this case, when new game information is received, it is preferable to discard the oldest received information first. Here, the game information display unit 74a displays the game information corresponding to the search pattern storage unit selected by the player, as shown in Figs. 6A, 6B, and 6C.
[0194] In the second player terminal 1, after the multi-battle participation tab 39 is operated, the party organization is completed, and a predetermined participation operation is performed, the communication control unit 70a executes a participation request process (2P23). Here, the communication control unit 70a transmits participation request information to the server 100.
[0195] When the server 100 receives the participation request information, the game execution control unit 170a executes a battle participation process to allow the second player to participate in the multi-battle selected by the second player (S22).
[0196] Next, the game execution control unit 170a executes a battle screen information generation process to generate battle screen information for displaying a battle screen (S23). Here, the game execution control unit 170a causes the second player terminal 1 to receive the generated battle screen information via the communication control unit 171a.
[0197] The game information display unit 74a of the second player terminal 1 performs a battle screen display process to display a battle screen on the display 26 based on the battle screen information received via the communication control unit 70a (2P24).
[0198] The second player terminal 1 performs a battle execution process (2P25) for executing a battle by communicating with the server 100 based on an input operation of the player on the battle screen. The server 100 also performs a battle execution process (S24) for executing a battle based on information received from the second player terminal 1 and other player terminals 1 participating in the multi-battle.
[0199] Through the above processing, a multi-battle is executed in which a plurality of players can participate. Furthermore, through the above processing, the player terminal 1 becomes able to acquire a help request corresponding to the type of multi-battle set by the player.
[0200] Although one aspect of the embodiment has been described above with reference to the accompanying drawings, it goes without saying that the present invention is not limited to the above embodiment. It is clear that a person skilled in the art can come up with various modified or revised examples within the scope of the claims, and it is understood that these also naturally belong to the technical scope.
[0201] In the above embodiment, the case where the player terminal 1 is a smartphone has been described as an example. However, the player terminal 1 is not limited to a smartphone, and may be any computer such as a personal computer.
[0202] Moreover, the game contents in the above embodiment are merely examples. Furthermore, the game genre to which the above technical matters can be applied is not particularly limited. For example, the above technical matters can be applied to all game genres, such as RPG, action games, puzzle games, training games, sports games, etc. In any case, the information processing system S includes one or more computers, and the computers perform the following processes.
[0203] A process of executing a multiplayer game (a multi-battle as an example in the embodiment) of a content ID selected by the first player (P16, S14, S24, and 2P25 as an example in the embodiment). A process (S21 in the embodiment as an example) of allowing a second player different from the first player to obtain one or more pieces of game information including a content ID selected by the second player. A process of allowing the second player to participate in a multiplayer game corresponding to game information selected by the second player from among game information acquired by the second player (S22 in the embodiment as an example).
[0204] The computer may also perform the following processes. A process of associating a content ID selected by a player with one of a plurality of storage units (in the embodiment, 2P20, S20 as an example). A process of accepting a player's operation of selecting one of a plurality of storage units (in the embodiment, 2P20, 2P21 as an example). A process of displaying game information including a content ID associated with a storage unit selected by a player from among the acquired game information (in the embodiment, 2P22 is an example). A process of generating information that can be posted to an SNS (S13 in the embodiment as an example).
[0205] In the above embodiment, the case where the content ID is stored in the search pattern storage unit has been described. However, the search pattern storage unit is not essential. For example, when a player selects a content ID, game information including the selected content ID may be searched for, and the player terminal 1 may receive the extracted game information. In this case, it is sufficient that the player selects a content ID to communicate with the server 100, and there is no need to store the content ID as in the above embodiment.
[0206] Furthermore, for a content ID that is stored in a large number of search pattern storage units, in other words, a content ID that is set as a search target by many players, the players to whom a rescue request is made may be classified into a plurality of groups. When determining the player to whom a rescue request is made, a group may be determined first, and then some or all of the players classified into the determined group may be determined as the players to whom a rescue request is made. In this way, even in a multi-battle with a large number of rescue requests, many players can obtain the rescue request.
[0207] In the above embodiment, the information processing system S, which is a client-server system, performs each of the above information processes. However, the function of the server 100 in the above embodiment may be provided in the player terminal 1. Also, the function of the player terminal 1 in the above embodiment may be provided in the server 100. In other words, each of the above processes may be performed by either the player terminal 1 or the server 100.
[0208] The program in the above embodiment may be stored in a computer-readable storage medium and provided as the storage medium. Furthermore, the program may be provided as a game terminal device or an information processing system including the storage medium. The above embodiment may also be an information processing method for implementing each function and step shown in the flowchart. [Explanation of symbols]
[0209] 1 Player terminal 100 Servers S Information Processing System
Claims
1. One or more computers; The computer, A process of executing a multiplayer game having a content ID selected by a first player; a process of having a second player different from the first player acquire one or more pieces of game information including the content ID selected by the second player; a process of having the second player participate in the multiplayer game corresponding to the game information selected by the second player from among the game information acquired by the second player; To carry out Information processing system.
2. The computer, A process of associating the content ID selected by a player with one of a plurality of storage units; A process of receiving an operation by a player to select one of the plurality of storage units; displaying the game information including the content ID associated with the storage unit selected by a player from the acquired game information; To carry out The information processing system according to claim 1 .
3. The process of causing the second player to acquire the game information includes: A process for generating information that can be posted to a social networking site is included.
3. The information processing system according to claim 1 or 2.
4. One or more computers A process of executing a multiplayer game having a content ID selected by a first player; a process of having a second player different from the first player acquire one or more pieces of game information including the content ID selected by the second player; a process of having the second player participate in the multiplayer game corresponding to the game information selected by the second player from among the game information acquired by the second player; To carry out Information processing methods.
5. A process of executing a multiplayer game having a content ID selected by a first player; a process of having a second player different from the first player acquire one or more pieces of game information including the content ID selected by the second player; a process of having the second player participate in the multiplayer game corresponding to the game information selected by the second player from among the game information acquired by the second player; An information processing program that causes a computer to carry out the above.
Citation Information
Patent Citations
Video game control system, video game control server, and video game control program
JP2013153815A
Information processor and program
JP2020000767A
Information processing program, information processing device, and information processing method
JP7116233B1
