Information processing program, information processing method, and information processing system
Patent Information
- Application Number
- JP2022199283
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2022-12-14
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2041-08-13
AI Technical Summary
Players with less powerful characters in games often struggle to advance and may lose interest due to the lack of engagement and challenge.
Implementing an information processing system that allows players to compete against opponents with varying conditions, including first and second advantageous conditions, which can be granted in duplicate, and dynamically changing parameters to enhance gameplay experience.
Enhances player engagement by providing varied challenges and opportunities, making the game more interesting and rewarding for players with less powerful characters.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[Technical Field]
[0001] The present invention relates to an information processing program, an information processing method, and an information processing system. [Background technology]
[0002] Patent Document 1 discloses a game in which a player cooperates with other players to battle enemy characters. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Patent Publication No. 2021-90699 Summary of the Invention [Problem to be solved by the invention]
[0004] In the above-mentioned games, a player who does not have a powerful character cannot advance the game to an advantage, which may ruin the enjoyment of the game.
[0005] An object of the present invention is to provide an information processing program, an information processing method, and an information processing system that can enhance the enjoyment of a game. [Means for solving the problem]
[0006] In order to solve the above problem, the information processing program includes a process for selecting one of a plurality of opponents including an opponent having at least one or more first conditions and an opponent having at least one or more second conditions; A process of playing a competitive game against the opponent selected by the player; a process of granting a first advantageous condition that is advantageous to a player in the competitive game against the opponent for whom the first condition is satisfied, when the first condition is satisfied in the competitive game; When the second condition is satisfied in the competitive game, a process of granting a second advantageous condition that is advantageous to the player in the competitive game against an opponent other than the opponent for which the second condition is satisfied; The computer executes the following. The first advantageous condition and the second advantageous condition may be granted in duplicate in the competitive game with one of the opponents.
[0007] Parameters are set for the opponent, In the process of playing the competitive game, the parameters of the opponent are changed; In the process of granting the first advantageous condition, when the parameter of the opponent reaches a predetermined value, the first condition may be deemed to be satisfied, and the first advantageous condition may be granted for a predetermined period of time.
[0008] Parameters are set for the opponent, In the process of playing the competitive game, the parameters of the opponent are changed; In the process of granting the second advantageous condition, when the parameter of the opponent reaches a specific value, the second condition is deemed to be satisfied and the second advantageous condition is granted; In the process of making the opponent selectable, the opponent whose parameter has reached the specific value may be made unselectable.
[0009] a process of displaying a list of the first advantageous condition and the second advantageous condition granted in the competitive game with the opponent in a manner that allows a player to distinguish the first advantageous condition and the second advantageous condition; Furthermore, the process may be performed by a computer.
[0010] In order to solve the above problem, an information processing method is an information processing method executed by one or more computers, A process for allowing a player to select one of a plurality of opponents including an opponent having at least one or more first conditions and an opponent having at least one or more second conditions; A process of playing a competitive game against the opponent selected by the player; a process of granting a first advantageous condition that is advantageous to a player in the competitive game against the opponent for whom the first condition is satisfied, when the first condition is satisfied in the competitive game; When the second condition is satisfied in the competitive game, a process of granting a second advantageous condition that is advantageous to the player in the competitive game against an opponent other than the opponent for which the second condition is satisfied; Including, The first advantageous condition and the second advantageous condition may be given to one opponent in duplicate.
[0011] In order to solve the above problem, an information processing system is an information processing system including one or more computers, The computer A process for allowing a player to select one of a plurality of opponents including an opponent having at least one or more first conditions and an opponent having at least one or more second conditions; A process of playing a competitive game against the opponent selected by the player; a process of granting a first advantageous condition that is advantageous to a player in the competitive game against the opponent for whom the first condition is satisfied, when the first condition is satisfied in the competitive game; When the second condition is satisfied in the competitive game, a process of granting a second advantageous condition that is advantageous to the player in the competitive game against an opponent other than the opponent for which the second condition is satisfied; and The first advantageous condition and the second advantageous condition may be given to one opponent in duplicate. [Effects of the Invention]
[0012] According to the present invention, the interest of the game can be increased. [Brief explanation of the drawings]
[0013] [Figure 1] FIG. 1 is an explanatory diagram showing a schematic configuration of an information processing system. [Figure 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. [Figure 3] Fig. 3A is a diagram showing an example of a home screen, Fig. 3B is a diagram explaining an example of an ally character confirmation screen, and Fig. 3C is a diagram showing an example of a quest screen. [Figure 4] Fig. 4A is a diagram illustrating an example of a main quest screen, Fig. 4B is a diagram illustrating an example of a main quest selection screen, and Fig. 4C is a first diagram illustrating an example of a party selection screen. [Figure 5] Fig. 5A is a diagram illustrating an example of a battle screen, and Fig. 5B is a diagram illustrating an example of a result screen. [Figure 6] Fig. 6A is a diagram illustrating an example of an event battle screen, and Fig. 6B is a diagram illustrating an example of a support setting screen. [Figure 7] Fig. 7A is a diagram illustrating an example of a superiority bonus confirmation screen, and Fig. 7B is a diagram illustrating an example of a defeat bonus confirmation screen. [Figure 8] FIG. 8 is a diagram illustrating an example of a bonus awarding condition setting table. [Figure 9] Fig. 9A is a diagram illustrating an example of an event battle selection screen, Fig. 9B is a diagram illustrating an example of a party selection screen, and Fig. 9C is a diagram illustrating an example of a support character selection screen. [Figure 10] Fig. 10A is a diagram illustrating an example of a battle screen related to a sub-boss battle, Fig. 10B is a diagram illustrating an example of an event battle screen, and Fig. 10C is a diagram illustrating an example of an event battle selection screen. [Figure 11] Fig. 11A is a diagram illustrating an example of a party selection screen, and Fig. 11B is a diagram illustrating an example of a support character selection screen. [Figure 12]FIG. 12 is a diagram illustrating the memory configuration and computer functions of the player terminal. [Figure 13] FIG. 13 is a diagram illustrating the memory configuration and computer functions of the server. [Figure 14] FIG. 14 is a sequence diagram illustrating basic processing of the player terminal and the server. [Figure 15] FIG. 15 is a flowchart illustrating an example of a battle game control process in a player terminal. [Figure 16] FIG. 16 is a flowchart illustrating an example of the superiority bonus awarding process in the server. [Figure 17] FIG. 17 is a flowchart illustrating an example of the defeat bonus awarding process in the server. DETAILED DESCRIPTION OF THE INVENTION
[0014] An embodiment of the present invention will be described in detail below with reference to the accompanying drawings. Dimensions, materials, and other specific values shown in the embodiment are merely examples for ease of 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 designated by the same reference numerals to avoid redundant explanation, and elements not directly related to the present invention are not shown.
[0015] (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 that includes a player terminal 1, a server 100, and a communication network 200 having a communication base station 200a.
[0016] A player terminal (information processing device) 1 can establish communication with the server 100 via a communication network 200. The player terminal 1 broadly includes electronic devices that can establish a wireless or wired communication connection with the server 100. Examples of the player terminal 1 include smartphones, mobile phones, tablet devices, personal computers, game consoles, etc. In this embodiment, a case will be described in which a smartphone is used as the player terminal 1.
[0017] The server 100 is configured to be able to communicate with a plurality of player terminals 1, and is communicatively connected to a plurality of player terminals 1. The server 100 accumulates various types of information (player information) for each player ID for identifying a player playing a game.
[0018] The communication base station 200a is connected to the communication network 200 and wirelessly transmits and receives information to and from the player terminal 1. The communication network 200 is made up of a mobile phone network, the Internet network, a LAN (Local Area Network), a dedicated line, etc., and realizes a wireless or wired communication connection between the player terminal 1 and the server 100.
[0019] 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 each assigned a role in controlling the progress of the game, and the game can progress through cooperation between the player terminal 1 and the server 100.
[0020] (Hardware Configuration of Player Terminal 1 and Server 100) Fig. 2A is a diagram illustrating the hardware configuration of the player terminal 1. Fig. 2B is a diagram illustrating the hardware configuration of the server 100. As shown in Fig. 2A, the player terminal 1 includes a CPU (Central Processing Unit) 10, a memory 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 a CPU 110, a memory 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, memory 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, memory 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, the following will describe the hardware configuration of the player terminal 1, and a description of the server 100 will be omitted.
[0023] The CPU 10 runs programs stored in the memory 12 and controls the progress of the game. The memory 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 memory 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 semiconductor memory such as a DRAM (Dynamic Random Access Memory) and stores various programs and data. In the player terminal 1, the programs and data stored in the storage unit 18 are loaded into the memory 12 (RAM) by the CPU 10.
[0026] The communication unit 20 is wirelessly connected to the communication base station 200a for communication, and transmits and receives information such as various data and programs to and from the server 100 via the communication network 200. In the player terminal 1, the programs and the like received from the server 100 are stored in the memory 12 or the storage unit 18.
[0027] The input unit 22 is composed of, for example, a touch panel, buttons, a keyboard, a mouse, a cross key, an analog controller, or the like, which inputs (accepts) player operations. 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 which detects the tilt or movement of the player terminal 1, or a microphone which detects the voice of the player. In other words, the input unit 22 broadly includes devices which can input the player's intentions in a identifiable manner.
[0028] The output unit 24 includes a display device and a speaker. The output unit 24 may be an external device connected 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 content) Next, the content of a game provided by the information processing system S (game device G) of this embodiment will be described using an example. In this embodiment, a so-called battle game is provided in which ally characters battle against enemy characters. Specifically, in the game of this embodiment, multiple ally characters are provided. A player selects multiple ally characters (here, five) from the provided ally characters to form a party. In addition, a player can play multiple types of battle games with different enemy characters and difficulty levels. In a battle game, the objective is for the ally characters formed into a party to defeat (clear) the enemy characters and earn a reward.
[0030] FIG. 3A is a diagram showing an example of a home screen. FIG. 3B is a diagram explaining an example of an ally character confirmation screen. FIG. 3C is a diagram showing an example of a quest screen. Game screens such as those shown in FIGS. 3A, 3B, and 3C are displayed on the display 26 of the player terminal 1. In this embodiment, the game screens are broadly divided into normal screens and battle screens.
[0031] The normal screen is a screen that is primarily used by the player to confirm various settings and information. On the other hand, the battle screen is a screen that is displayed on the display 26 from the start to the end of the battle game. Here, all screens other than the battle screen are normal screens. The normal screen includes a home screen shown in FIG. 3A, an ally character confirmation screen shown in FIG. 3B, a quest screen shown in FIG. 3C, a main quest screen shown in FIG. 4A (described later), an event battle screen shown in FIG. 6A and FIG. 10B (described later), a support setting screen shown in FIG. 6B (described later), a gacha screen (not shown), a menu screen, and a shop screen.
[0032] On the normal screen, a menu bar 30 is displayed at the bottom of the display 26. The menu bar 30 has a plurality of operation units that can be operated (tapped) by the player. The menu bar 30 has a home screen selection operation unit 30a labeled "HOME," an ally character confirmation screen selection operation unit 30b labeled "CHARACTER," a story screen selection operation unit 30c labeled "STORY," a quest screen selection operation unit 30d labeled "QUEST," a gacha screen selection operation unit 30e labeled "GACHA," and a menu screen selection operation unit 30f labeled "MENU." In the menu bar 30, the operation units corresponding to each screen are highlighted so that the screen currently being displayed on the display 26 can be identified.
[0033] When the home screen selection operation unit 30a is tapped, the home screen shown in FIG. 3A is displayed on the display 26. When the ally character confirmation screen selection operation unit 30b is tapped, the ally character confirmation screen shown in FIG. 3B is displayed on the display 26. When the story screen selection operation unit 30c is tapped, a story screen (not shown) is displayed on the display 26. When the quest screen selection operation unit 30d is tapped, a quest screen (not shown) is displayed on the display 26. When the gacha screen selection operation unit 30e is tapped, a gacha screen (not shown) is displayed on the display 26. When the menu screen selection operation unit 30f is tapped, a menu screen (not shown) is displayed on the display 26. Although a detailed description will be omitted, on the story screen, new stories are unlocked as the player progresses through the main quest (see FIG. 4A) described below on the quest screen, and the player can view the unlocked stories from the story screen. On the gacha screen, a gacha lottery can be held to acquire an ally character. On the menu screen, game settings and various information can be confirmed.
[0034] 3A corresponds to the initial screen, and has a header display area 31 at the top. The header display area 31 displays level information 31a indicating the player level associated with the player ID, and a stamina display bar 31b indicating the stamina of the player associated with the player ID. The level information 31a and information related to stamina are also included in the player information.
[0035] Stamina is a parameter necessary for a player to play a battle game. In this embodiment, multiple types of battle games are provided, and each battle game has a set stamina consumption value required for play, a maximum number of times that the game can be played per day, etc. When playing a battle game for which a stamina consumption value required for play is set, the player consumes stamina to play the battle game, and therefore, if the player does not have enough stamina, the player cannot play the battle game.
[0036] Although a detailed explanation will be omitted, when a player wins a battle game, the player can acquire a predetermined value as player experience points. Then, each time the player experience points reach a certain value, the player level increases. A stamina upper limit is set for the player level, and as the player level increases, the stamina upper limit also increases. Stamina recovers by a predetermined value (e.g., 1 point) every fixed time (e.g., 5 minutes) within the upper limit range. The stamina display bar 31b displays the current remaining stamina in relation to the stamina upper limit so that the player can visually grasp it.
[0037] Additionally, an event battle operation section 32 may be displayed on the right edge of the home screen. When an event battle, which will be described in detail later, is held, the event battle operation section 32 labeled "Event Battle" is displayed during the event battle period.
[0038] When the event battle operation unit 32 labeled "event battle" is tapped, an event battle screen (see FIGS. 6A and 10B) is displayed on the display 26. Note that if no event battle is being held, the event battle operation unit 32 is not displayed.
[0039] When the ally character confirmation screen selection operation unit 30b shown in FIG. 3A is tapped, the ally character confirmation screen shown in FIG. 3B is displayed on the display 26. The ally character confirmation screen displays all images of ally characters corresponding to the ally character IDs associated with the player ID. That is, the ally character confirmation screen displays all ally characters possessed by the player. Note that the ally character ID is used to identify the ally characters, and a different ID is assigned to each ally character. When a player acquires a new ally character, for example, through a gacha lottery, the ally character ID of the acquired ally character is associated with the player ID of the player. The ally character ID is configured as part of the player information.
[0040] The ally character ID is stored in association with information about experience points and information about levels. Experience points increase when a character wins a battle game, which will be described later, or when a predetermined item is used. A level is set corresponding to the experience points, and increases each time the experience points reach a predetermined value. Each ally character has a level upper limit set, and the level can only increase up to the upper limit.
[0041] Furthermore, base values for combat power, such as life points, attack power, and defense power, are set for each ally character based on their level. The higher the combat power of an ally character, the more advantageously the player can progress through the battle game. Furthermore, the base values set for each ally character increase as the level increases.
[0042] Furthermore, allied characters can be equipped (set) with weapons and armor. Each piece of equipment has an additional value set for attack power, defense power, etc. When equipment is equipped, the additional value of each piece of equipment is added to the above base value, thereby increasing the combat power of the allied character. Information about these weapons and armor is also associated with the allied character ID and is configured as part of the player information.
[0043] When the quest screen selection operation section 30d shown in Fig. 3A is tapped, the quest screen shown in Fig. 3C is displayed on the display 26. The quest screen displays a plurality of game type selection operation sections 44, each listing the type of battle game that is available. Here, five types of battle games are available, and five game type selection operation sections 44 are displayed.
[0044] The game type selection operation unit 44 is provided with a main quest selection operation unit 44a marked "Main Quest," a guild battle selection operation unit 44b marked "Guild Battle," a 1V1 battle selection operation unit 44c marked "1V1 Battle," a 3V3 battle selection operation unit 44d marked "3V3 Battle," and an event battle operation unit 44e marked "Event Battle." The event battle operation unit 44e is displayed when an event battle is being held, and is hidden when no event battle is being held.
[0045] When the main quest selection operation unit 44a is tapped, the main quest screen shown in FIG. 4A is displayed on the display 26. When the guild battle selection operation unit 44b is tapped, a guild battle screen (not shown) is displayed on the display 26. Similarly, when the 1V1 battle selection operation unit 44c is tapped, a 1V1 battle screen (not shown) is displayed on the display 26. When the 3V3 battle selection operation unit 44d is tapped, a 3V3 battle screen (not shown) is displayed on the display 26. When the event battle operation unit 44e is tapped, an event battle screen (see FIGS. 6A and 10B) is displayed on the display 26.
[0046] Note that some types of battle games have unlocking conditions. Examples of unlocking conditions include a player level being equal to or higher than a predetermined value, viewing a specific story from a story screen, or clearing another predetermined battle game. Each battle game type includes multiple battle games (hierarchical or loop). Each of these battle games also has an unlocking condition. When an unlocking condition is met, the game unlocking information included in the player information is updated.
[0047] In the player terminal 1, it is determined whether or not a battle game is available based on the game availability information, and only the game type selection operation unit 44 of a battle game that satisfies the availability conditions will accept the player's operation (tap). Therefore, the player can play only the battle game that satisfies the availability conditions.
[0048] Fig. 4A is a diagram illustrating an example of a main quest screen, Fig. 4B is a diagram illustrating an example of a main quest selection screen, and Fig. 4C is a first diagram illustrating an example of a party selection screen.
[0049] As described above, when the main quest selection operation section 44a is tapped in the game type selection operation section 44 shown in FIG. 3C, the main quest screen shown in FIG. 4A is displayed on the display 26.
[0050] The main quest screen displays a quest operation section 45 for selecting a plurality of battle games (levels) belonging to the main quest. The main quest screen also displays a menu bar 30 and a header display area 31.
[0051] The quest operation unit 45 also displays information on whether each battle game has been completed. The information on whether the game has been completed is indicated by, for example, three stars. When a battle game belonging to a main quest is completed, stars are earned according to the number of ally characters whose life points are 0 at the time of completion. For example, if there are no ally characters whose life points are 0, three stars are earned; if there is one ally character whose life points are 0, two stars are earned; and if there are two or more ally characters whose life points are 0, one star is earned.
[0052] In the example of Figure 4A, three stars are earned in the battle game "1-1," two stars are earned in the battle game "1-2," and one star is earned in the battle game "1-3." In addition, no stars are earned in the battle game "1-4," and it is announced that this battle game has not been cleared.
[0053] In the main quest, the unlocking condition is set to be clearing the previous battle game. For example, in the example of Figure 4A, the "1-4" battle game is unlocked because the "1-3" battle game has been cleared, but the battle games after that ("1-5" and after, not shown) are not unlocked.
[0054] For example, when the quest operation unit 45 for a battle game "1-4" is operated (tapped) on the main quest screen, the main quest selection screen shown in FIG. 4B is displayed on the display 26. The main quest selection screen displays enemy characters that appear in that battle game and items (rewards) that can be acquired in that battle game. The main quest selection screen also displays a challenge operation unit 46 marked "Challenge" for challenging that battle game, and a cancel operation unit 40 marked "Cancel" for canceling the processing corresponding to the currently displayed screen.
[0055] When the cancel operation unit 40 is operated (tapped), the main quest screen shown in FIG. 4A is displayed on the display 26, and the challenge to the selected battle game "1-4" is canceled.
[0056] On the other hand, when the challenge operation unit 46 is operated (tapped), the party selection screen shown in Fig. 4C is displayed on the display 26. The party selection screen displays all of the ally characters possessed by the player, and below it, a selected ally character display area 47 that displays the selected ally character.
[0057] Also displayed on the party selection screen are a cancel operation section 40 and a battle start operation section 49 labeled "Start Battle."
[0058] When the player operates (tap) a displayed ally character on the party selection screen, the operated ally character is displayed in the selected ally character display area 47. In other words, here, an ally character ID to be used in the battle game (to determine the party) is selected from among multiple ally character IDs associated with the player ID. A party is formed by the player selecting multiple ally characters. Note that the same ally character cannot be set more than once when forming a party.
[0059] Once the party formation is complete, the battle start operation unit 49 is operated (tapped) to start the battle game.
[0060] Fig. 5A is a diagram illustrating an example of a battle screen. Fig. 5B is a diagram illustrating an example of a result screen. When the battle start operation unit 49 is operated (tapped) on the party selection screen shown in Fig. 4C, the battle game starts.
[0061] During the battle game, a battle screen is displayed as shown in FIG. 5A. On the battle screen, ally characters and enemy characters are displayed on the display 26. The ally characters are controlled by a computer and can inflict damage on enemy characters or receive damage from them. The enemy characters are also controlled by a computer and can inflict damage on ally characters or receive damage from them.
[0062] When damage points are awarded to an enemy character, the damage points are subtracted from the enemy character's life points. Similarly, when damage points are awarded to an ally character, the damage points are subtracted from the ally character's life points. When the life points of all enemy characters reach 0, the player wins (clears), and when the life points of all ally characters reach 0 (defeats), the player loses.
[0063] As shown in FIG. 5A, an ally character display area 50 is provided at the bottom of the battle screen. The ally character display area 50 displays life points 50a and a special move gauge 50b for each ally character. The special move gauge 50b increases when the ally character receives damage from an enemy character or inflicts damage on the enemy character. When the special move gauge 50b reaches a predetermined maximum value, the ally character can use a special move. A special move inflicts more damage points on the enemy character than a normal attack, recovers the ally character's life points, or imparts a special effect to the enemy character.
[0064] Here, two patterns are provided for using a special move. One is a method in which the player operates (tap) an ally character displayed in the ally character display area 50 when the special move gauge 50b has reached its maximum value. The other is a method in which, when the special move gauge 50b reaches its maximum value in the auto mode, the ally character uses a special move under computer control. An auto selection operation unit 51 is displayed on the battle screen, and the player can switch between the auto mode and the manual mode by operating the auto selection operation unit 51. When the auto selection operation unit 51 is operated in the manual mode, the mode switches to the auto mode in which the special move is automatically used. When the auto selection operation unit 51 is operated in the auto mode, the mode switches to the manual mode in which the special move is manually used. Even in the auto mode, when the special move gauge 50b has reached its maximum value and the special move has not been used under computer control, the player can operate (tap) the ally character to use a special move.
[0065] Then, when the battle game ends normally (normal end), a result screen is displayed on the display 26, as shown in Fig. 5B. Fig. 5B shows, as an example, the result screen when an ally character wins.
[0066] The result screen displays at least a portion of the game result information of the battle game, and also displays an end operation section 53 marked "Close."
[0067] The game result information includes the ally character ID (party) of the ally character, the enemy character ID of the enemy character, the remaining status of the ally character and the enemy character at the end of the battle (whether or not their life points are 0 at the end of the battle game), the damage points inflicted (total value), whether the game is in manual or auto mode, the battle log ID, the type of battle game (main quest, guild battle, etc.), information associated with each type of battle game (clear information, battle game level, etc.), and information about the items assigned. Regarding whether the game is in manual or auto mode, if the game is in auto mode from the start to the end of the battle game and no special moves are manually used by the player, the game is in auto mode; otherwise, the game is in manual mode. A unique battle log ID is assigned to each battle game. The information associated with each type of battle game varies depending on the type of battle game.
[0068] When the end operation unit 53 is operated (tapped) on the result screen, the display on the display 26 switches from the battle screen to the normal screen. In other words, the result screen is a part of the battle screen. The normal screen that the result screen switches to may be the screen that was displayed immediately before switching to the battle screen, or may be a predetermined screen such as the home screen. In this way, the battle game ends when the display of the result screen ends.
[0069] Next, the event battle will be described. Fig. 6A is a diagram illustrating an example of an event battle screen. Fig. 6B is a diagram illustrating an example of a support setting screen. Fig. 7A is a diagram illustrating an example of a superiority bonus confirmation screen. Fig. 7B is a diagram illustrating an example of a defeat bonus confirmation screen.
[0070] In an event battle, a battle game is played in which all players stored in the server 100 cooperate to fight against a powerful enemy character (in this embodiment, a sub-boss). The event battle of this embodiment is closely related to the story and is a reproduction of a battle game in which, after a specific story, the protagonist of the story fights against the main boss. Therefore, a participation condition is set for the event battle. In this embodiment, the participation condition is set as operating the story screen selection operation unit 30c shown in FIG. 3A and viewing a specific story from the story screen (the player information must include flag information indicating that the specific story has been viewed), and players who have viewed the specific story can participate in the event battle. Therefore, players who have not viewed the specific story cannot participate in the event battle.
[0071] During an event battle, when the event battle operation unit 32 labeled "Event Battle" shown in FIG. 3A or the event battle operation unit 44e shown in FIG. 3C is operated (tapped), the event battle screen shown in FIG. 6A is displayed on the display 26.
[0072] The event battle screen displays four sub-bosses (sub-boss A, sub-boss B, sub-boss C, sub-boss D) and one main boss, as well as a remaining challenge right display area 60a, a challenge right recovery time display area 60b, a support setting operation section 60c, and a raid HP display area 60d.
[0073] In this embodiment, when an event battle is held, each player is granted a certain number of challenge rights, which allow them to challenge multiple sub-bosses. For example, when each player logs in during the event battle period, each player is granted five challenge rights, which allow them to challenge the sub-bosses, at the time of their first login. Note that there is an upper limit to the challenge rights, and in this embodiment, the upper limit is five.
[0074] The player plays a battle game against each sub-boss (hereinafter referred to as a sub-boss battle), and when the battle game meets the end condition (when the life points of all allied characters or the sub-boss reach 0, or when a certain amount of time has passed), one challenge right is consumed. If the player retires during the battle game, the challenge right is not consumed, and the damage points inflicted on the sub-boss during the battle game are also reset.
[0075] The remaining challenge right display area 60a displays the current remaining challenge right relative to the upper limit of the challenge right. In the example shown in Fig. 6A, the remaining challenge right display area 60a displays 3 (times) as the remaining challenge right.
[0076] The right to challenge is granted a predetermined number of times at predetermined time intervals. For example, the right to challenge is granted three times every six hours. The challenge right recovery time display area 60b displays the time remaining until the next time the right to challenge is granted (recovered). In the example shown in FIG. 6A, the challenge right recovery time display area 60b displays 5 hours and 42 minutes as the time remaining until the right to challenge is granted.
[0077] The support setting operation unit 60c is displayed on the event battle screen, and is only displayed while an event battle is being held. When the player operates (tap) the support setting operation unit 60c, the support setting screen shown in FIG. 6B is displayed. On the support setting screen, a support character setting area 61 labeled "Event Battle" is displayed. The player can set up to two support characters in the support character setting area 61.
[0078] In the support character setting, a player can set a support character that the player owns as a support character that can be lent to another player. Other players can borrow the support character set by the player to fight against enemy characters. Here, a player can earn a reward by setting a support character. For example, a player can earn in-game currency as a reward to train the ally character that the player owns.
[0079] In this embodiment, a player can perform friend settings, follow settings, support settings, and the like on the menu screen. In the friend settings, a player can register another player as a friend. Friend registration is performed when a player sends a friend request to another player and the other player accepts the friend request, or when a player accepts a friend request sent from another player. Once friend registration is complete, the player ID and the other player ID are associated as friends, and the other player ID is stored in the server 100 as the player's friend ID. Note that the player ID is used to identify a player, and a different ID is assigned to each player. In other words, a player ID is assigned an ID different from the IDs of other players. In the follow settings, a player can register another player as a follower. Follow registration is performed when a player sends a follow request to another player, and approval from the other player is not required. Once follow registration is complete, the player ID and the other player ID are associated, and the other player ID is stored in the server 100 as the player's follow ID.
[0080] For example, another player can borrow a support character set in the support character setting area 61 from a player who has completed friend registration. Similarly, a player can borrow a support character set in the support character setting area 61 from another player who has completed friend registration. However, a support character set in the support character setting area 61 may also be lent or borrowed between a player who has not completed friend registration and another player (non-friend). For example, a support character set in the support character setting area 61 may be borrowed from another player (non-friend) who the player has registered as a follower.
[0081] Furthermore, in this embodiment, each player can belong to a guild. A player may be able to borrow a support character set in the support character setting area 61 from another player (guild member) who belongs to the same guild. Similarly, a guild member may be able to borrow a support character set in the support character setting area 61 from a player who belongs to the same guild.
[0082] 6B, the player sets one support character in the support character setting area 61. The support character ID of the support character set in the support character setting area 61 is associated with the player ID and saved as part of the player information. The player information including the support character ID is transmitted from the player terminal 1 to the server 100 and saved in the server 100.
[0083] 6B, an additional setting possible mark 61a that allows additional support characters to be set is displayed in the support character setting area 61. The player can add a new support character other than the support characters already set in the support character setting area 61 by operating (tapping) the additional setting possible mark 61a.
[0084] A support character set in the support character setting area 61 is provided with a setting cancellation unit 61b. The player can cancel the setting of the support character by operating the setting cancellation unit 61b. At this time, the association between the player ID and the support character ID is released, and information related to the support character ID is deleted from the player information. However, the setting of the support character cannot be canceled until a certain amount of time (e.g., 30 minutes) has passed since the support character was set. The setting cancellation unit 61b will not accept any operation from the player until a certain amount of time has passed since the support character was set. Note that when the event battle ends, the support character set in the support character setting area 61 is automatically canceled.
[0085] When playing the "event battle" battle game, other players can borrow the support character that the player has set in the support character setting area 61. For example, other players can borrow the support character that has been set in the player's support character setting area 61. Similarly, a player can borrow the support character that has been set in the support character setting area 61 of another player.
[0086] In this embodiment, when an event battle is held, a plurality of sub-bosses are displayed on the display 26 as shown in FIG. 6A so that the players can select them, and a sub-boss battle begins in which all players fight against each sub-boss.
[0087] Each sub-boss has two types of hit points (hereinafter referred to as HP). Specifically, each sub-boss has a raid HP and a battle HP. In this embodiment, the initial value of the raid HP of each sub-boss is set to 2 trillion, and the initial value of the battle HP of each sub-boss is set to 2 million.
[0088] In each sub-boss battle, the battle HP of the opponent's sub-boss is subtracted based on the damage inflicted on the opponent's sub-boss, and when the battle HP of the opponent's sub-boss reaches 0, the opponent's sub-boss is defeated. Also, in event battles, the raid HP of the opponent's sub-boss is subtracted based on the damage inflicted on the opponent's sub-boss by the player in the sub-boss battle. Note that each sub-boss has a set disappearance condition, and even if defeated by the player, each sub-boss will revive until its raid HP reaches 0. Note that a value calculated by applying a predetermined coefficient to the damage inflicted on the opponent's sub-boss by the player in the sub-boss battle may be subtracted from the raid HP.
[0089] The raid HP is a value common to all players participating in the event battle, and the server 100 manages this value (raid HP) during the event battle. When the raid HP of each sub-boss reaches 0, the sub-boss's elimination condition is met and the sub-boss is eliminated. Specifically, the server 100 subtracts the raid HP based on the damage inflicted on each sub-boss by all players participating in the event battle. The server 100 then determines whether the raid HP of each sub-boss has reached 0 (i.e., whether the elimination condition of each sub-boss has been met), and if it determines that the raid HP has reached 0 (the elimination condition has been met), it executes a performance process to eliminate that sub-boss. In other words, parameters (raid HP and battle HP) are set for each opponent, and the opponent's parameters (raid HP and battle HP) change (decrease) when a sub-boss battle in the event battle is executed. In addition, although this embodiment shows a case where both raid HP and battle HP are provided, this is not limited to this, and it is also possible to provide only raid HP without battle HP. In this case, damage inflicted by the player on the opponent's sub-boss in the sub-boss battle may be subtracted from the raid HP of the opponent's sub-boss.
[0090] 6A, a raid HP display area 60d is displayed below each sub-boss. In the raid HP display area 60d, a raid HP display bar showing the remaining raid HP of each sub-boss is displayed.
[0091] When the raid HP display bar displayed in the raid HP display area 60d reaches 0 (i.e., the conditions for the elimination of each sub-boss are met), that sub-boss is eliminated, and an effect is displayed in which the sub-boss disappears from the event battle screen. Furthermore, a notation indicating that the sub-boss has been eliminated is displayed in the raid HP display area 60d. For example, after the sub-boss has been eliminated, the words "Defense Successful" are displayed in the raid HP display area 60d. The player can freely battle any of the four sub-bosses whose elimination conditions have not been met.
[0092] In addition, in this embodiment, depending on the progress of the sub-boss battle, a superiority bonus (first advantageous condition) and a defeat bonus (second advantageous condition) advantageous to the player may be granted in the sub-boss battle with each sub-boss. Note that the superiority bonus (first advantageous condition) and the defeat bonus (second advantageous condition) granted in the sub-boss battle with each sub-boss are valid for all players. However, it is also possible to provide superiority bonuses (first advantageous condition) and defeat bonuses (second advantageous condition) that are valid for at least some players. In this case, for example, the superiority bonus (first advantageous condition) and the defeat bonus (second advantageous condition) may be valid for so-called beginner players. Alternatively, the superiority bonus (first advantageous condition) and the defeat bonus (second advantageous condition) may be valid only among guild members or players who have completed friend registration.
[0093] The superiority bonus (first advantageous condition) and the defeat bonus (second advantageous condition) are not particularly limited in content as long as they are advantageous to the player. Examples of the superiority bonus (first advantageous condition) and the defeat bonus (second advantageous condition) can be, for example, an effect of strengthening the player's character (ally character or support character) in a sub-boss battle (increasing various stats such as attack power and defense power), or an effect of weakening the opponent's sub-boss (reducing various stats such as attack power and defense power of the sub-boss, inhibiting the actions of the sub-boss, etc.).
[0094] As shown in FIG. 6A, the status of the superiority bonus (first advantageous condition) and defeat bonus (second advantageous condition) awarded to each sub-boss is notified to the player by a superiority bonus icon 60e and a defeat bonus icon 60f. Also, as shown in FIG. 6A, a bonus information display section 60g is displayed at the top of the display 26. The bonus information display section 60g displays, for a predetermined period of time, information related to the superiority bonus (first advantageous condition) and defeat bonus (second advantageous condition) newly awarded in the sub-boss battle with each sub-boss. Specifically, the bonus information display section 60g displays, for a predetermined period of time, information related to the superiority bonus (first advantageous condition) and defeat bonus (second advantageous condition) that were not awarded when the previous event battle screen was transitioned to, but that have newly occurred when the current event battle screen is transitioned to.
[0095] As shown in FIG. 6A, in this embodiment, when both a superiority bonus and a defeat bonus are awarded in a sub-boss battle with one sub-boss, superiority bonus icons 60e are displayed in a row at the bottom of the raid HP display area 60d, and defeat bonus icons 60f are displayed in a row at the bottom of the superiority bonus icons 60e. Also, as shown in FIG. 6A, in this embodiment, when only a defeat bonus is awarded in a sub-boss battle with one sub-boss, defeat bonus icons 60f are displayed in a row at the bottom of the raid HP display area 60d. Also, in this embodiment, when only a superiority bonus is awarded in a sub-boss battle with one sub-boss, superiority bonus icons 60e are displayed in a row at the bottom of the raid HP display area 60d.
[0096] In addition, when the conditions for the disappearance of a sub-boss in a sub-boss battle to which a superiority bonus and a defeat bonus are granted are met (when the raid HP becomes 0), the superiority bonus icon 60e and the defeat bonus icon 60f displayed for that sub-boss will be hidden.
[0097] Furthermore, when a superiority bonus icon 60e displayed corresponding to each sub-boss on the event battle screen is operated (tapped), a superiority bonus confirmation screen shown in FIG. 7A is displayed on the display 26. For example, when a superiority bonus icon 60e displayed below "Sub-boss A" on the event battle screen is operated (tapped), a superiority bonus confirmation screen shown in FIG. 7A is displayed on the display 26. The superiority bonus confirmation screen displays a list of superiority bonuses awarded in the sub-boss battle with the sub-boss corresponding to the superiority bonus icon 60e operated (tapped) by the player, and an OK operation section 62a marked "OK" is displayed. Note that when the OK operation section 62a is operated (tapped) on the superiority bonus confirmation screen, the display of the superiority bonus confirmation screen ends, and the event battle screen is displayed on the display 26.
[0098] As shown in FIG. 7A, each superiority bonus is set with an effect advantageous to the player and a remaining effective time for granting the superiority bonus in a sub-boss battle. Note that the superiority bonus granted in a sub-boss battle will expire when the set remaining effective time has elapsed. Furthermore, a superiority bonus with a remaining effective time set to "permanent" will continue to be granted until the sub-boss's expiration condition for the sub-boss battle to which it was granted is met. As shown in FIG. 6A, the superiority bonus icon 60e corresponding to a superiority bonus with a set remaining effective time displays the remaining effective time so that it can be easily identified. Note that the remaining effective time is subtracted from the time the superiority bonus is granted in a sub-boss battle, regardless of whether a sub-boss battle is being held. Note that if the remaining effective time of the superiority bonus is within the effective time of the sub-boss battle at the start of the sub-boss battle and has expired at the end of the sub-boss battle, the effect of the superiority bonus will be treated as valid in that sub-boss battle. In other words, if the superiority bonus is still within its remaining valid time at the start of the sub-boss battle, the superiority bonus will be treated as valid in that sub-boss battle.
[0099] In addition, in this embodiment, an upper limit (activation upper limit) is set for the number of superiority bonuses that can be activated simultaneously, which makes it possible to prevent situations that are excessively advantageous to the player from unintentionally occurring, making it extremely easy to conquer the sub-boss battle, and increases the enjoyment of the game.
[0100] If the number of superiority bonuses granted in a sub-boss battle with one sub-boss exceeds the upper limit, the superiority bonus associated with the newly established first condition may not be granted in the sub-boss battle with that sub-boss. In this case, any newly generated superiority bonuses that have already reached the upper limit are invalidated and will not be applied again even if the upper limit is subsequently reached. However, this is not limited to this. If the number of superiority bonuses granted in a sub-boss battle with one sub-boss exceeds the upper limit, the superiority bonus granted earlier in the sub-boss battle may be activated first. Furthermore, a priority may be set for each type of superiority bonus, and the superiority bonus with the highest priority may be activated first. Alternatively, there may be no upper limit on the number of superiority bonuses that can be activated simultaneously (maximum activation number).
[0101] Furthermore, when a defeat bonus icon 60f displayed corresponding to each sub-boss on the event battle screen is operated (tapped), the defeat bonus confirmation screen shown in FIG. 7B is displayed on the display 26. For example, when the defeat bonus icon 60f displayed below "Sub-boss A" on the event battle screen is operated (tapped), the defeat bonus confirmation screen shown in FIG. 7B is displayed on the display 26. The defeat bonus confirmation screen displays a list of defeat bonuses awarded in the sub-boss battle with the sub-boss corresponding to the defeat bonus icon 60f operated (tapped) by the player, and an OK operation section 62a marked "OK" is displayed. Note that when the OK operation section 62a is operated (tapped) on the defeat bonus confirmation screen, the display of the defeat bonus confirmation screen is terminated, and the event battle screen is displayed on the display 26.
[0102] As shown in Figure 7B, the defeat bonus is set to have an effect advantageous to the player. In this embodiment, the defeat bonus continues to be awarded until the sub-boss in the sub-boss battle to which the bonus is awarded is eliminated. However, the defeat bonus may have a remaining effective time set in the same way as the superiority bonus.
[0103] 8 is a diagram illustrating an example of a bonus-granting condition setting table. In this embodiment, as shown in FIG. 8, a first condition and a second condition are set for each sub-boss.
[0104] In this embodiment, multiple first conditions are set based on the raid HP value of each sub-boss. Specifically, as shown in Fig. 8, four first conditions are set as the first conditions: when the raid HP is subtracted and reaches (falls below) "1900000000000", when the raid HP is subtracted and reaches (falls below) "100000000000", when the raid HP is subtracted and reaches (falls below) "50000000000", and when the raid HP is subtracted and reaches (falls below) "10000000000".
[0105] As shown in FIG. 8, the type of superiority bonus to be awarded when each first condition is satisfied and the type of sub-boss in the sub-boss battle to which the superiority bonus is to be awarded are set in advance. In this embodiment, as shown in FIG. 8, it is set that a specified type of superiority bonus is awarded in the sub-boss battle with the sub-boss for which each first condition is satisfied. Specifically, for example, it is set that when the raid HP against sub-boss A reaches "1900000000000," a superiority bonus A1 is awarded in the sub-boss battle with sub-boss A. Note that one or more types of superiority bonuses are associated with the superiority bonuses A1 to A4, superiority bonuses B1 to B4, superiority bonuses C1 to C4, and superiority bonuses D1 to D4, respectively.
[0106] In other words, when a first condition is satisfied in a battle game, a first advantageous condition that is advantageous to the player is granted in the battle game against the opponent for whom the first condition is satisfied. Also, in other words, when the opponent's parameter (raid HP) reaches a predetermined value (here, raid HP is "1900000000000," "1000000000000," "500000000000," or "10000000000"), the first condition is deemed to be satisfied, and the first advantageous condition (superiority bonus) is granted for a predetermined period of time. While this embodiment illustrates a case in which a different type of superiority bonus is set for each sub-boss, the same type of superiority bonus may be set for at least some of the sub-bosses. Also, this embodiment illustrates a case in which the predetermined value at which the first condition is satisfied is the same for each sub-boss, at least some or all of the predetermined values at which the first condition is satisfied may be different for each sub-boss. Furthermore, the content of the first advantageous condition (superiority bonus) that is granted when the first condition is satisfied may be determined by lottery.
[0107] In this embodiment, a second condition of 1 is set for each sub-boss. Specifically, as shown in Fig. 8, the second condition is set when the raid HP reaches "0." In other words, when the disappearance condition for each sub-boss is met, the second condition is also met.
[0108] 8, the type of defeat bonus to be awarded when each second condition is satisfied and the type of sub-boss in the sub-boss battle to which the defeat bonus is to be awarded are set in advance. In this embodiment, as shown in FIG. 8, it is set so that a defined type of defeat bonus is awarded in a sub-boss battle with a sub-boss other than the sub-boss for which each second condition is satisfied.
[0109] Specifically, for example, when the raid HP against sub-boss A reaches "0," defeat bonus A is awarded in sub-boss battles with sub-bosses other than sub-boss A. Note that defeat bonus A, defeat bonus B, defeat bonus C, and defeat bonus D are each associated with one or more types of defeat bonuses.
[0110] In other words, when the second condition is satisfied in the battle game, a second advantageous condition that is advantageous to the player is granted in the battle game against opponents other than the opponent for whom the second condition is satisfied. In other words, when the opponent's parameter (raid HP) reaches a specific value (here, raid HP is "0"), the second condition is deemed to be satisfied, and the second advantageous condition (defeat bonus) is granted.
[0111] Furthermore, in this embodiment, a case is shown in which a different type of defeat bonus is set for each sub-boss, but the same type of defeat bonus may be set for at least some of the sub-bosses.
[0112] In addition, in sub-boss battles with other sub-bosses whose disappearance conditions are met before the second condition of sub-boss A is met and which have already disappeared, defeat bonuses will not be awarded.
[0113] In addition, in this embodiment, the superiority bonus and defeat bonus can be awarded in the sub-boss battle with one sub-boss. In other words, as the sub-boss battle progresses, the number of superiority bonuses and defeat bonuses awarded in the sub-boss battle with one sub-boss increases, so the more the sub-boss battle progresses, the more advantageous the player can be in the sub-boss battle. This prevents the sub-boss battle from becoming prolonged and causing the player to feel bored, and makes the game more interesting.
[0114] As described above, this embodiment illustrates a case in which multiple first conditions and one second condition are set, but this is not limiting. In other words, it is sufficient that any one of multiple opponents (sub-bosses) including an opponent (sub-boss) with at least one or more first conditions and an opponent (sub-boss) with at least one or more second conditions can be selected. Furthermore, for example, any one of multiple opponents (sub-bosses) including a sub-boss with only the first condition, a sub-boss with only the second condition, and a sub-boss with both the first and second conditions may be selected. Furthermore, an opponent (sub-boss) with neither the first nor the second condition may be included. Furthermore, the specific value of the parameter (raid HP) of an opponent for which the second condition is met may be the same as any of the predetermined values of the parameter (raid HP) of an opponent for which the first condition is met.
[0115] Furthermore, in this embodiment, the first and second conditions are set based on the value of raid HP, but the first and second conditions may use parameters set for the opponents and are not limited to raid HP. For example, in a sub-boss battle, the first and second conditions may be set based on the cumulative number of times each sub-boss's battle HP reaches "0" (i.e., the number of times each sub-boss is defeated). In addition, in a sub-boss battle, the first and second conditions may be set based on various conditions (parameters), such as the cumulative number of times a special move is used against each sub-boss, or whether or not a specific item possessed by each player has been used. In any case, in a fighting game (sub-boss battle), the parameters of the opponent (sub-boss) are changed, and when the parameters of the opponent (sub-boss) reach a predetermined value, the first condition is deemed to be met and a first advantageous condition (superiority bonus) is granted for a predetermined period of time, and when the parameters of the opponent (sub-boss) reach a specific value, the second condition is deemed to be met and a second advantageous condition (defeat bonus) is granted.
[0116] FIG. 9A is a diagram illustrating an example of an event battle selection screen. FIG. 9B is a diagram illustrating an example of a party selection screen. FIG. 9C is a diagram illustrating an example of a support character selection screen. When, for example, "Sub-boss A" is operated (tapped) on the event battle screen, the event battle selection screen shown in FIG. 9A is displayed on the display 26. The event battle selection screen displays the enemy character (sub-boss A) that appears in the battle game and the items (rewards) that can be acquired in the battle game. The event battle selection screen also displays a special effect character display section 63a, a superiority bonus display section 63b, a defeat bonus display section 63c, a challenge operation section 46, and a cancel operation section 40.
[0117] A total of five ally characters (five types in total) are displayed in the special effect character display section 63a. In this embodiment, multiple special effect characters are set in advance for each sub-boss, and when the sub-boss battle is conducted using the special effect characters set for each sub-boss, the sub-boss battle will proceed in an advantageous manner for the player. In this embodiment, multiple special effect characters linked to the story (scenario) are set for each sub-boss. For example, by using special effect characters in a sub-boss battle, when calculating damage, a damage calculation result advantageous to the player is derived by adding or multiplying various parameters (level, HP, attack power, etc.) by the correction value set for each special effect character. Note that in this embodiment, the correction value set for ally characters is set to be larger than that of support characters. Note that, unlike sub-boss battles, the above-mentioned special effect characters are not set in main boss battles, which will be described later.
[0118] The superiority bonus display section 63b displays a list of types of superiority bonuses (first advantageous conditions) that have been granted in the sub-boss battle with the enemy character (sub-boss A) displayed on the event battle selection screen. When the superiority bonus display section 63b is operated (tapped), the superiority bonus confirmation screen shown in FIG. 7A is displayed on the display 26.
[0119] The defeat bonus display section 63c displays a list of types of defeat bonuses (second advantageous conditions) that are granted in the sub-boss battle with the enemy character (sub-boss A) displayed on the event battle selection screen. When the defeat bonus display section 63c is operated (tapped), the defeat bonus confirmation screen shown in FIG. 7B is displayed on the display 26.
[0120] When the cancel operation unit 40 is operated (tapped), the event battle screen shown in FIG. 6A is displayed on the display 26, and the challenge to the battle game of the selected "Sub-boss A" is canceled.
[0121] On the other hand, when the challenge operation unit 46 is operated (tapped), the party selection screen shown in Fig. 9B is displayed on the display 26. The party selection screen displays all of the ally characters possessed by the player, with a selected ally character display area 47 displayed below and a support character selection operation unit 48 displayed above. The party selection screen also displays a cancel operation unit 40 and a battle start operation unit 49.
[0122] When the player operates (tap) a displayed ally character on the party selection screen, the operated ally character is displayed in the selected ally character display area 47, and a party is organized. Note that when organizing a party for an event battle, the player must organize at least one ally character that he or she owns.
[0123] 9B, the party selection screen displays the special effect characters set for the selected sub-boss in an identifiable manner. Specifically, the ally characters set as special effect characters are labeled with the word "special effect."
[0124] Therefore, the player can easily organize five types of special effect characters into a party that can advance the sub-boss battle advantageously. In this embodiment, a different special effect character is set for each sub-boss. This makes it necessary to organize a party taking into account the special effect characters in the battle game for each sub-boss, which improves the strategic nature of the game and makes it more interesting. It is also possible to set the same special effect characters for all sub-bosses.
[0125] Furthermore, when the support character selection operation unit 48 is operated (tapped) on the party selection screen, the support character selection screen shown in Fig. 9C is displayed. The support characters that other players have set in the support character setting area 61 for the "event battle" are displayed on the support character selection screen.
[0126] Here, as shown in FIG. 9C , the support character selection screen displays the special effect characters set for the selected sub-boss in an identifiable manner. Specifically, the support characters set as special effect characters are labeled with the notation "Special Effect." In this embodiment, a single ally character set as a special effect character will give the player an advantage in the sub-boss battle over a single support character set as a special effect character. In other words, when organizing the same special effect characters into a party, it is more advantageous for the player to own that special effect character than to borrow that special effect character from another player.
[0127] On the support character selection screen, when the player operates (tap) a displayed support character, the operated support character is displayed in the selected ally character display area 47.
[0128] In a battle game that belongs to an event battle, an upper limit (for example, four) may be set on the number of selectable support characters. In other words, in a battle game that belongs to an event battle, a player may be able to borrow, for example, up to four support characters. However, this is not limited to this, and the number of support characters that a player can borrow may differ depending on, for example, the type of sub-boss or the main boss described below.
[0129] Once the party formation is complete and the battle start operation unit 49 is operated (tapped), the battle game begins. The basic parts of the battle game are the same as the main quest, so the differences from the main quest will be explained below. FIG. 10A is a diagram illustrating an example of a battle screen related to a sub-boss battle. As shown in FIG. 10A, a superiority bonus display unit 64a and a defeat bonus display unit 64b are displayed on the left and right sides of the battle screen related to the sub-boss battle.
[0130] The superiority bonus display section 64a displays a list of types of superiority bonuses (first advantageous conditions) that have been granted in the sub-boss battle with the enemy character (sub-boss A) displayed on the event battle selection screen. When the superiority bonus display section 64a is operated (tapped), a superiority bonus confirmation screen shown in FIG. 7A is displayed on the display 26.
[0131] The defeat bonus display section 64b displays a list of types of defeat bonuses (second advantageous conditions) that are granted in the sub-boss battle with the enemy character (sub-boss A) displayed on the event battle selection screen. When the defeat bonus display section 64b is operated (tapped), the defeat bonus confirmation screen shown in FIG. 7B is displayed on the display 26.
[0132] In the main quest battle game, the player consumes his / her stamina to play the battle game, whereas in the sub-boss battle, the player does not consume his / her stamina but consumes the challenge right granted to the player to play the battle game.
[0133] Additionally, there are two types of rewards in the sub-boss battle game: a single-subjugation reward when the sub-boss's battle HP reaches 0 and it is defeated, and a elimination reward when the sub-boss's elimination conditions are met. The single-subjugation reward is a reward that can only be obtained by a player who has defeated one sub-boss. A player can obtain the single-subjugation reward each time they defeat a sub-boss. However, even if another player defeats a sub-boss, the player cannot obtain the single-subjugation reward. The elimination reward is a common reward that can be obtained by all players who access the event battle screen during the event battle after the sub-boss has been eliminated.
[0134] Event battles include battle games in which players face off against a main boss (hereinafter also referred to as a main boss battle) in addition to sub-boss battles in which players face off against a sub-boss. The main boss battle appears on the event battle screen when all sub-bosses have been eliminated in the sub-boss battle or a certain period of time has passed since the start of the event battle. In other words, the player cannot face the main boss until all sub-bosses have been eliminated in the sub-boss battle or a certain period of time has passed since the start of the event. Note that if any sub-bosses remain after a certain period of time has passed since the start of the event, an event occurs in which all remaining sub-bosses are forcibly eliminated, and after all sub-bosses have been eliminated, an event occurs in which the main boss appears.
[0135] Fig. 10B is a diagram illustrating an example of an event battle screen. Fig. 10C is a diagram illustrating an example of an event battle selection screen. Fig. 11A is a diagram illustrating an example of a party selection screen. Fig. 11B is a diagram illustrating an example of a support character selection screen.
[0136] 10B shows the event battle screen after all sub-bosses have been eliminated or a certain period of time has passed since the start of the event. The event battle screen displays one main boss, as well as a remaining challenge right display area 60a, a support setting operation section 60c, and an HP display bar 63d.
[0137] In a main boss battle, unlike a sub-boss battle, each player fights the main boss individually. In other words, in a main boss battle, all players cannot cooperate with each other to fight the main boss. However, in a main boss battle, all players may cooperate with each other to fight the main boss.
[0138] In this embodiment, when the main boss battle begins, each player is granted an unlimited number of chances to challenge the main boss. Therefore, the remaining challenge right display area 60a displays text indicating that the challenge right is unlimited. Also, because the challenge right is unlimited, the challenge right recovery time display area 60b, which was present on the event battle screen for the sub-boss battle shown in FIG. 6A, is not displayed on the event battle screen for the main boss battle shown in FIG. 10B.
[0139] The support setting operation unit 60c is displayed on the event battle screen for the main boss battle shown in Fig. 10B, as well as on the event battle screen for the sub-boss battle shown in Fig. 6A. When the support setting operation unit 60c is operated (tapped), the support setting screen shown in Fig. 6B is displayed.
[0140] Even in the main boss battle, other players can borrow the support characters that the player has set in the support character setting area 61 when playing the battle game of the "event battle." Similarly, a player can borrow the support characters that have been set in the support character setting area 61 of other players.
[0141] As shown in FIG. 10B , an HP display bar 63d is displayed below the main boss. In the main boss battle, each player can defeat the main boss by reducing the main boss's HP to 0. In other words, each player's victory condition is to reduce the main boss's HP (HP display bar 63d) to 0. In this embodiment, one type of HP is set for the main boss, and specifically, the initial value of the main boss's HP is set to 20 million. In other words, in this embodiment, the main boss's HP is set to be lower than the raid HP of the sub-boss and higher than the battle HP of the sub-boss. However, the main boss's HP may also be set to be the same as or lower than the battle HP of the sub-boss. Furthermore, the main boss's HP may be set to be different for each player. For example, the main boss's HP may be set to be higher for an advanced player than for a beginner player.
[0142] When "Main Boss" is operated (tapped) on the event battle screen, the event battle selection screen shown in FIG. 10C is displayed on the display 26. The event battle selection screen displays the enemy character (main boss) that appears in the battle game and the items (rewards) that can be acquired in the battle game. The event battle selection screen also displays a challenge operation unit 46 for challenging the battle game and a cancel operation unit 40.
[0143] When the cancel operation unit 40 is operated (tapped), the event battle screen shown in FIG. 10B is displayed on the display 26, and the challenge to the battle game of the selected "main boss" is canceled.
[0144] In this embodiment, unlike sub-boss battles, the above-mentioned special effect characters are not set in main boss battles. Furthermore, the above-mentioned superiority bonus and defeat bonus are not awarded in main boss battles with the main boss. Therefore, as shown in FIG. 10B, the superiority bonus icon 60e and defeat bonus icon 60f on the event battle screen for the sub-boss battle shown in FIG. 6A are not displayed on the event battle screen for the main boss battle. Furthermore, as shown in FIG. 10C, the special effect character display area 63a, superiority bonus display area 63b, and defeat bonus display area 63c on the event battle selection screen for the sub-boss battle shown in FIG. 9A are not displayed on the event battle selection screen for the main boss battle.
[0145] On the other hand, when the challenge operation unit 46 is operated (tapped), the party selection screen shown in Fig. 11A is displayed on the display 26. The party selection screen displays all of the ally characters possessed by the player, with a selected ally character display area 47 displayed below and a support character selection operation unit 48 displayed above. The party selection screen also displays a cancel operation unit 40 and a battle start operation unit 49.
[0146] When the player operates (tap) a displayed ally character on the party selection screen, the operated ally character is displayed in the selected ally character display area 47, and a party is organized.
[0147] Furthermore, when the support character selection operation unit 48 is operated (tapped) on the party selection screen, the support character selection screen shown in Fig. 11B is displayed. The support characters that other players have set in the support character setting area 61 for the "event battle" are displayed on the support character selection screen.
[0148] As mentioned above, unlike the sub-boss battle, the above-mentioned special effect characters are not set in the main boss battle. Therefore, as shown in FIG. 11A, the party selection screen for the main boss battle does not display the notation "special effect" that is attached to the ally character set as the special effect character in the party selection screen for the sub-boss battle shown in FIG. 9B. Similarly, as shown in FIG. 11B, the support character selection screen for the main boss battle does not display the notation "special effect" that is attached to the ally character set as the special effect character in the support character selection screen for the sub-boss battle shown in FIG. 9C.
[0149] On the support character selection screen, when the player operates (tap) a displayed support character, the operated support character is displayed in the selected ally character display area 47.
[0150] As in the sub-boss battle, an upper limit (for example, four) may be set for the number of selectable support characters in the main boss battle.
[0151] Once the party formation is complete and the battle start operation unit 49 is operated (tapped), the battle game begins. The basic parts of the battle game are the same as those of the sub-boss battle and main quest, so a detailed explanation will be omitted. Unlike the sub-boss battle, the main boss battle has unlimited challenge rights and does not require stamina consumption, so the player can challenge the main boss battle any number of times until the victory conditions are met. As mentioned above, in the main boss battle with the main boss, no superiority bonus or defeat bonus is awarded. Therefore, the superiority bonus display unit 64a and defeat bonus display unit 64b on the battle game screen for the sub-boss battle shown in FIG. 10B are not displayed on the battle game screen for the main boss battle.
[0152] When the event battle period ends, the event battle operation unit 32 shown in FIG. 3A and the event battle operation unit 44e shown in FIG. 3C are hidden, and players are unable to access the event battle screen. Therefore, players who are unable to log in to the game during the event battle period or who are unable to defeat the main boss during the event battle period lose the opportunity to challenge the main boss battle. However, after the event battle period ends, a separate event that can be challenged by a single player may be held separately. In this case, each HP (raid HP, battle HP) can be lowered compared to the value during the event battle period.
[0153] Next, a description will be given of the basic configuration and communication processing of the player terminal 1 and the server 100 for executing the event battle. Note that here, an example of the basic communication processing for progressing the game and the main communication processing related to the event battle will be described, and a description of other processing will be omitted.
[0154] (Functional configuration of player terminal 1) 12 is a diagram illustrating the configuration of the memory 12 in the player terminal 1 and its functions as a computer. The memory 12 is provided with a program storage area 12a and a data storage area 12b. When a game starts, the CPU 10 stores a terminal-side game control program (module) in the program storage area 12a.
[0155] The terminal-side game control program includes a game execution control program 80, a battle game execution program 81, a player information saving program 82, a support character setting program 83, a party organization program 84, and a display control program 85. Note that the programs listed in Figure 12 are just examples, and the terminal-side game control program includes many other programs.
[0156] The data storage area 12b is provided with the following storage units for storing data: a game information storage unit 90, a player information storage unit 91, a support character information storage unit 92, and a party composition information storage unit 93. Note that the above storage units are merely examples, and the data storage area 12b is provided with many other storage units.
[0157] 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 game control unit 1A. The terminal game control unit 1A includes a game execution control unit 80a, a battle game execution unit 81a, a player information storage unit 82a, a support character setting unit 83a, a party organization unit 84a, and a display control unit 85a.
[0158] Specifically, the CPU 10 runs a game execution control program 80, causing the computer to function as a game execution control unit 80a. Similarly, the CPU 10 runs a battle game execution program 81, a player information saving program 82, a support character setting program 83, a party organization program 84, and a display control program 85, causing them to function as a battle game execution unit 81a, a player information saving unit 82a, a support character setting unit 83a, a party organization unit 84a, and a display control unit 85a, respectively.
[0159] The game execution control unit 80a controls the overall progress of the game. For example, when logging in to the game, the game execution control unit 80a transmits login information to the server 100. The game execution control unit 80a also acquires event information from the server 100 and stores it in the game information storage unit 90. The event information includes information such as the raid HP and battle HP of each sub-boss in the event battle, superiority bonus information including whether or not a superiority bonus has been awarded and the type of superiority bonus awarded, defeat bonus information including whether or not a defeat bonus has been awarded and the type of defeat bonus awarded, and the type of special effect character.
[0160] The battle game executing unit 81a is responsible for control for executing the battle game. For example, the battle game executing unit 81a updates the battle screen, controls the actions of ally characters and enemy characters, and derives damage points based on operations input to the player terminal 1.
[0161] Specifically, in the event battle, the battle game executing unit 81a allows the player to select one of a plurality of opponents (sub-bosses) including an opponent (sub-boss) having at least one or more first conditions and an opponent (sub-boss) having at least one or more second conditions. Also, a sub-boss whose raid HP has reached 0 cannot be selected. Then, the battle game executing unit 81a executes a battle game against the opponent (sub-boss or main boss) selected by the player.
[0162] Furthermore, when a superiority bonus or a defeat bonus is awarded in a sub-boss battle with an opponent sub-boss, the battle game executing unit 81a derives damage points based on the awarded superiority bonus or defeat bonus. At this time, when a superiority bonus and a defeat bonus are awarded in a sub-boss battle with one sub-boss, the battle game executing unit 81a derives damage points based on both the superiority bonus and the defeat bonus.
[0163] The player information saving unit 82a saves player information acquired from the server 100 in the player information storage unit 91. Furthermore, when the player information is changed in response to an operation by the player, the player information saving unit 82a saves the changed player information in the player information storage unit 91 and transmits the changed player information to the server 100. Here, the player information includes a player ID, an ally character ID, a support character ID, etc. This allows the server 100 to determine whether or not each player meets the conditions for participating in the event battle (main boss battle) based on the player information of each player.
[0164] The support character setting unit 83a sets the support character of the player based on the input operation by the player to the support character setting area 61. Furthermore, the support character setting unit 83a stores information about the set support character (support character information: support character ID) in the support character information storage unit 92 and transmits it to the server 100.
[0165] The party formation unit 84a forms a party based on an input operation by the player on the party selection screen. The party formation unit 84a also stores information about the formed party (party formation information: ally character IDs and support character IDs) in the party formation information storage unit 93 and transmits it to the server 100.
[0166] The display control unit 85a generates a screen to be displayed on the display 26, and causes the generated screen to be displayed on the display 26. For example, as shown in Figures 6A, 9A, and 10A, the display control unit 85a displays a list of the superiority bonus (first advantageous condition) and defeat bonus (second advantageous condition) granted in the sub-boss battle with the opponent so that the player can distinguish them.
[0167] (Functional configuration of server 100) 13 is a diagram illustrating the configuration of memory 112 in server 100 and its computer functions. Memory 112 is provided with a program storage area 112a and a data storage area 112b. When a game starts, CPU 110 stores a server-side game control program (module) in program storage area 112a.
[0168] The server-side game control program includes a game execution control program 180, a battle game execution program 181, a player information saving program 182, a support character information saving program 183, a party composition information saving program 184, a reward granting program 185, a superiority bonus granting program 186, a defeat bonus granting program 187, and a special effect character setting program 188. Note that the programs listed in Figure 13 are just examples, and the server-side game control program is provided with many other programs.
[0169] The data storage area 112b is provided with the following storage units for storing data: a game information storage unit 190, a player information storage unit 191, a support character information storage unit 192, and a party composition information storage unit 193. Note that the above storage units are merely examples, and the data storage area 112b is provided with many other storage units.
[0170] 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 to function as a server-side game control unit 100A. The server-side game control unit 100A includes a game execution control unit 180a, a battle game execution unit 181a, a player information storage unit 182a, a support character information storage unit 183a, a party composition information storage unit 184a, a reward granting unit 185a, a superiority bonus granting unit 186a, a defeat bonus granting unit 187a, and a special effect character setting unit 188a.
[0171] Specifically, the CPU 110 operates a game execution control program 180, causing the computer to function as a game execution control unit 180a. Similarly, the CPU 110 operates a battle game execution program 181, a player information saving program 182, a support character information saving program 183, a party composition information saving program 184, a reward granting program 185, a superiority bonus granting program 186, a defeat bonus granting program 187, and a special effect character setting program 188, causing them to function as a battle game execution unit 181a, a player information saving unit 182a, a support character information saving unit 183a, a party composition information saving unit 184a, a reward granting unit 185a, a superiority bonus granting unit 186a, a defeat bonus granting unit 187a, and a special effect character setting unit 188a, respectively.
[0172] The game execution control unit 180a controls the overall progress of the game. For example, when the game execution control unit 180a receives login information from the player terminal 1, the game execution control unit 180a sets the event information stored in the game information storage unit 190, the player information stored in the player information storage unit 191, the support character information stored in the support character information storage unit 192, and the party composition information stored in the party composition information storage unit 193 so that the player terminal 1 can acquire them.
[0173] The battle game executing unit 181a manages the battle HP and raid HP of each sub-boss during the event battle period. Specifically, the battle game executing unit 181a subtracts the battle HP and raid HP of each sub-boss based on the results of the sub-boss battles between sub-boss A, sub-boss B, sub-boss C, and sub-boss D, executed by each player participating in the event battle. The battle game executing unit 181a keeps each sub-boss alive if the raid HP of each sub-boss has not reached 0, and eliminates each sub-boss if the raid HP of each sub-boss has reached 0. The battle game executing unit 181a keeps each sub-boss alive if the battle HP of each sub-boss has not reached 0, and defeats each sub-boss individually if the battle HP of each sub-boss has reached 0.
[0174] When the player information saving unit 182a receives player information (for example, game result information) from the player terminal 1, the player information saving unit 182a saves the received player information in the player information storage unit 191.
[0175] When support character information storage unit 183a receives support character information from player terminal 1, it stores the received support character information in support character information storage unit 192. At this time, support character information storage unit 183a stores the player ID and support character ID in association with each other. Note that the support character information includes information on the type of support character (support character ID) and status information on the status of the support character (information on the support character's level, equipment, HP, attack power, defense power, etc.).
[0176] When the party composition information saving unit 184a receives the party composition information from the player terminal 1, it saves the received party composition information in the party composition information storage unit 193.
[0177] The reward granting unit 185a grants rewards to players. The reward granting unit 185a grants an item corresponding to the cleared battle game to a player who has cleared the battle game. More specifically, the reward granting unit 185a adds the item to be granted to player information corresponding to the player ID of the player who has cleared the battle game, and stores the player information storage unit 191.
[0178] The superiority bonus granting unit 186a updates the superiority bonus information related to the sub-boss for which the first condition is satisfied, by referring to the bonus granting condition setting table shown in Fig. 8. That is, when the opponent's parameter (raid HP) reaches a predetermined value, the superiority bonus granting unit 186a determines that the first condition is satisfied and grants the first advantageous condition (superiority bonus) for a predetermined period of time.
[0179] The defeat bonus granting unit 187a refers to the bonus granting condition setting table shown in FIG. 8 and updates the defeat bonus information related to surviving sub-bosses (having raid HP greater than 0) other than the sub-bosses for which the second condition is satisfied. That is, when the second condition is satisfied in a battle game, the defeat bonus granting unit 187a grants a second advantageous condition that is advantageous to the player to opponents other than the opponent for whom the second condition is satisfied. In other words, when the opponent's parameter (raid HP) reaches a specific value, the defeat bonus granting unit 187a grants the second advantageous condition (defeat bonus) as the second condition is satisfied. Furthermore, the defeat bonus granting unit 187a sets the event information stored in the game information storage unit 190 so that it can be acquired by the player terminal 1.
[0180] The special effect character setting unit 188a sets a special effect character for each sub-boss.
[0181] (Communication processing between player terminal 1 and server 100) 14 is a sequence diagram illustrating basic processing of the player terminal 1 and the server 100. In the following description, processing in the player terminal 1 is represented as Pn (n is an arbitrary integer), and processing in the server 100 is represented as Sn (n is an arbitrary integer).
[0182] When a player starts a game application on the player terminal 1 (P1), the game execution control unit 80a transmits login information to the server 100. Upon receiving the login information, the game execution control unit 180a of the server 100 identifies the player ID associated with the login information and performs login processing (S1). Here, the game execution control unit 180a sets the player information corresponding to the identified player ID from the player information storage unit 191 so that it can be downloaded by the player terminal 1.
[0183] Furthermore, when the player operates the event battle operation unit 32 or the event battle operation unit 44e during the event battle period, the game execution control unit 80a of the player terminal 1 transmits operation information to the server 100 (P2).
[0184] Upon receiving the operation information, the game execution control unit 180a of the server 100 sets the event information stored in the game information storage unit 190 so that it can be acquired by the player terminal 1 (S2).
[0185] When the game execution control unit 80a and the display control unit 85a of the player terminal 1 acquire the event information, they execute a process (event battle screen processing) to display an event battle screen (Figure 6A or Figure 10B) on the display 26 based on the acquired event information (P3).
[0186] In addition, when the player operates the support setting operation unit 60c on the event battle screen, the game execution control unit 80a and the display control unit 85a of the player terminal 1 execute a process (support setting screen process) to display the support character setting area 61 on the display 26 (P3).
[0187] When a support character is set in the support character setting area 61 by the player, the support character setting unit 83a of the player terminal 1 stores the set support character information (support character ID) in the support character information storage unit 92 and transmits it to the server 100 (P4). When the support character information storage unit 183a of the server 100 receives the support character information from the player terminal 1, it executes a process (support character information storage process) of storing the received support character information in the support character information storage unit 192 in association with the player ID (S3).
[0188] When the player performs an operation to start the battle game (operation of the challenge operation unit 46), the battle game executing unit 81a and the display control unit 85a of the player terminal 1 transmit start information to the server 100 (P5), and display a party selection screen on the display 26. This start information includes player information, battle information, etc. Here, the battle information includes information about the type of battle game selected by the player, enemy character IDs, etc. When displaying the party selection screen on the display 26, the display control unit 85a of the player terminal 1 displays "special effect" for ally characters that have been set as special effect characters based on the event information.
[0189] When the player operates an ally character displayed on the party selection screen or the support character selection screen, the party organization unit 84a of the player terminal 1 performs processing (party organization screen processing) to organize the operated ally character into a party (P6). Furthermore, in the party organization screen processing (P6), when the player operates the support character selection operation unit 48 on the party selection screen, the display control unit 85a of the player terminal 1 displays the support character selection screen on the display 26, and when the player operates the support character selection operation unit 48 on the support character selection screen, the display control unit 85a of the player terminal 1 displays the party selection screen on the display 26. Furthermore, when displaying the party selection screen on the display 26, the display control unit 85a of the player terminal 1 displays "special effect" for support characters that have been set as special effect characters based on the event information.
[0190] In the party formation screen process (P6), when the party formation is completed and the battle start operation unit 49 is operated, the party formation unit 84a stores the party formation information in the party formation information storage unit 93 and transmits it to the server 100.
[0191] When the server 100 receives the party formation information from the player terminal 1, a battle game start process (S5) is executed. In the battle game start process (S5), the party formation information saving unit 184a of the server 100 saves the party formation information received from the player terminal 1 in the party formation information storage unit 193.
[0192] Furthermore, in the battle game start process (S5), the battle game executing unit 181a of the server 100 sets battle game start information and event information required to start the battle game so that the player terminals 1 can acquire them.
[0193] Then, upon receiving the battle game start information, the battle game executing unit 81a of the player terminal 1 performs a battle game start process to start the battle game (P7). Here, for example, an area in the memory 12 for progressing the battle game is secured, and a predetermined program is read from the storage unit 18 to the memory 12. The game execution control unit 80a also stores the event information received from the server 100 in the game information storage unit 90.
[0194] Thereafter, the battle game executing unit 81a of the player terminal 1 performs a battle game control process for controlling the battle game (P8). FIG. 15 is a flowchart illustrating an example of the battle game control process in the player terminal 1. In this battle game control process, an update process for updating various pieces of information is repeatedly executed on a frame-by-frame basis. The number of frames is not particularly limited, and the number of frames per second is, for example, 30 to 60. Therefore, during the battle game, information is updated in the player terminal 1 approximately every 16 ms to 33 ms.
[0195] The battle game executing unit 81a of the player terminal 1 acquires the event information stored in the game information storage unit 90 (P8-1), and acquires the party composition information stored in the party composition information storage unit 93 (P8-2).
[0196] The battle game executing unit 81a of the player terminal 1 performs a battle game calculation process (P8-3) that causes enemy characters and ally characters to perform movement and attack actions according to a predetermined algorithm based on information such as the type of special effect character, superiority bonus information, and defeat bonus information included in the event information acquired in step P8-1, and the party composition information acquired in step P8-2. The battle game calculation process calculates damage when an ally character attacks an enemy character, and when an enemy character attacks an ally character. In other words, in the battle game calculation process, a first advantageous condition that is advantageous to the player is granted in a battle game against an opponent for whom the first condition is satisfied, and a second advantageous condition that is advantageous to the player is granted in a battle game against an opponent other than the opponent for whom the second condition is satisfied.
[0197] Specifically, for example, when calculating damage, various parameters (fixed values or values corresponding to the character or sub-boss) set for each type of superiority bonus and defeat bonus are added or multiplied to derive a damage calculation result that is advantageous to the player. Also, for example, an enemy character for the superiority bonus (hereinafter referred to as a first stealth character) and an enemy character for the defeat bonus (hereinafter referred to as a second stealth character) may be placed in a state that is indistinguishable to the player and is not a battle opponent, i.e., as an in-game object for setting a bonus. In this case, a skill corresponding to superiority bonus information related to the opponent's sub-boss may be set for the placed first stealth character, and a skill corresponding to defeat bonus information related to the opponent's sub-boss may be set for the placed second stealth character.
[0198] Based on the processing of step P8-3, the display control unit 85a of the player terminal 1 executes a drawing process for drawing the battle screen on the display 26 (P8-4).
[0199] Then, the battle game executing unit 81a of the player terminal 1 determines whether or not the end condition of the battle game has been met (P8-5). As a result, if the end condition of the battle game has been met, the process proceeds to step P8-6, and if the end condition of the battle game has not been met, the battle game control process ends.
[0200] When the end condition of the battle game is met, the battle game executing unit 81a of the player terminal 1 generates game result information and ends the battle game control process (P8-6).
[0201] Returning to FIG. 14, the battle game execution unit 81a of the player terminal 1 transmits the game result information generated in the above step P8-6 to the server 100, and a result screen is displayed on the display 26, thereby executing a battle game ending process (P9).
[0202] When the battle game executing unit 181a of the server 100 receives the game result information, it executes an event information update process to update the event information (S6). Specifically, it updates the raid HP of the opponent's sub-boss based on the received game result information. In addition, the reward granting unit 185a grants items based on the game result information.
[0203] Next, the superiority bonus awarding unit 186a of the server 100 executes superiority bonus awarding processing based on the received game result information. Figure 16 is a flowchart illustrating an example of the superiority bonus awarding processing in the server 100. The superiority bonus awarding unit 186a of the server 100 sets a sub-boss to be processed based on the received game result information (S7-1).
[0204] The superiority bonus granting unit 186a of the server 100 determines whether the first condition has been newly satisfied for the sub-boss set in step S7-1 above, by referring to the bonus granting condition setting table shown in Figure 8 (S7-2). If the first condition has been newly satisfied, the process proceeds to step S7-3, and if the first condition has not been newly satisfied, the superiority bonus granting process ends.
[0205] The superiority bonus granting unit 186a of the server 100 updates the superiority bonus information related to the sub-boss for which the first condition is satisfied based on the bonus granting condition setting table shown in FIG. 8 (S7-3), and ends the superiority bonus granting process.
[0206] Returning to Fig. 14, next, the defeat bonus awarding unit 187a of the server 100 executes a defeat bonus awarding process based on the received game result information. Fig. 17 is a flowchart illustrating an example of the defeat bonus awarding process in the server 100. The defeat bonus awarding unit 187a of the server 100 sets the sub-boss to be processed based on the received game result information (S8-1).
[0207] The defeat bonus granting unit 187a of the server 100 determines whether the second condition has been newly satisfied for the sub-boss set in step S8-1 above, by referring to the bonus granting condition setting table shown in Figure 8 (S8-2). If the second condition has been newly satisfied, the process proceeds to step S8-3, and if the first condition has not been newly satisfied, the process proceeds to step S8-4.
[0208] The defeat bonus granting unit 187a of the server 100 updates the defeat bonus information for surviving sub-bosses (with raid HP greater than 0) other than the sub-bosses for which the second condition is met, based on the bonus granting condition setting table shown in Figure 8 (S8-3).
[0209] The defeat bonus awarding unit 187a of the server 100 sets the event information stored in the game information storage unit 190 so that it can be acquired by the player terminal 1, and then ends the defeat bonus awarding process.
[0210] As described above, the player terminal 1 is provided with a game execution control program 80, a battle game execution program 81, a player information storage program 82, a support character setting program 83, a party organization program 84, and a display control program 85. The player terminal 1 also functions as a game execution control unit 80a, a battle game execution unit 81a, a player information storage unit 82a, a support character setting unit 83a, a party organization unit 84a, and a display control unit 85a. However, some or all of these programs and functional units may be provided in the server 100. In other words, these programs and functional units may be provided in either or both of the player terminal 1 and the server 100.
[0211] The server 100 is also provided with a game execution control program 180, a battle game execution program 181, a player information storage program 182, a support character information storage program 183, a party composition information storage program 184, a reward granting program 185, a superiority bonus granting program 186, a defeat bonus granting program 187, and a special effect character setting program 188. The server 100 also functions as a game execution control unit 180a, a battle game execution unit 181a, a player information storage unit 182a, a support character information storage unit 183a, a party composition information storage unit 184a, a reward granting unit 185a, a superiority bonus granting unit 186a, a defeat bonus granting unit 187a, and a special effect character setting unit 188a. However, some or all of these programs and functional units may be provided in the player terminal 1. In other words, these programs and functional units may be provided in either or both of the player terminal 1 and the server 100.
[0212] Furthermore, in the above embodiment, a battle game is shown in which all players stored in the server 100 cooperate with each other to fight a powerful enemy character (in this embodiment, a sub-boss) in an event battle, but this is not limited to this, and the event battle may be conducted individually for each player.
[0213] In the above embodiment, an example has been described in which the player must include at least one ally character in the party for the event battle. However, the present invention is not limited to this, and the player may include all ally characters in the party for the event battle as support characters.
[0214] While one 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 conceive of various modifications or alterations within the scope of the claims, and it is understood that these modifications also fall within the technical scope of the present invention.
[0215] In the above embodiment, the division of processing between the player terminal 1 and the server 100 is merely an example. For example, each of the above processes may be executed by at least one of the player terminal 1 and the server 100, and the execution timing and the device that executes the processes are not particularly limited.
[0216] Furthermore, the processing of the player terminal 1 and the server 100 in the above embodiment is merely an example. It goes without saying that the processing of the player terminal 1 and the server 100 can be designed as appropriate within the scope of the object of the present invention.
[0217] For example, the server 100 may process a superiority bonus (first advantageous condition) or a defeat bonus (second advantageous condition) as follows: First, a subtraction process (parameter update process) is performed on the raid HP of each sub-boss based on the game result information received from the player terminal 1 of each player. Then, based on the raid HP of each sub-boss after the subtraction process is performed, it is determined whether or not a superiority bonus (first advantageous condition) or a defeat bonus (second advantageous condition) has occurred. Then, if a superiority bonus (first advantageous condition) or a defeat bonus (second advantageous condition) has occurred, the ID of the sub-boss for which the superiority bonus (first advantageous condition) or the defeat bonus (second advantageous condition) has occurred, the ID of the occurring superiority bonus (first advantageous condition) or the defeat bonus (second advantageous condition), and information on the time when the superiority bonus (first advantageous condition) or the defeat bonus (second advantageous condition) occurred are retained as event information. When transitioning to the event battle screen, the player terminal 1 may obtain from the server 100 a list of the times when a superior bonus (first advantageous condition) occurred for each sub-boss, a list of the IDs of the generated superior bonuses, and a list of the IDs of the sub-bosses whose disappearance conditions have been met, and may display the event battle screen based on the obtained information.
[0218] Also, at the start of a sub-boss battle with each sub-boss, just as when transitioning to the event battle screen, the player terminal 1 may obtain from the server 100 a list of the times when a superiority bonus (first advantageous condition) occurred for each sub-boss, a list of the IDs of the generated superiority bonuses, and a list of the IDs of the sub-bosses whose disappearance conditions have been met.
[0219] In addition, the player terminal 1 may be configured to store in advance the type of superiority bonus and the ID of the superiority bonus, and the type of defeat bonus and the ID of the sub-boss in correspondence with each other, so that the type of superiority bonus (first advantageous condition) and the type of defeat bonus (second advantageous condition) that will be generated can be identified by obtaining the ID of the superiority bonus that has been obtained and the ID of the sub-boss whose disappearance condition has been met.
[0220] Also, for example, an update operation section marked "Update" may be provided on the event battle screen. In this case, by operating (tapping) the update operation section, the same process (communication between the player terminal 1 and the server 100) as when transitioning to the event battle screen may be performed, and information related to each bonus and raid HP may be updated.
[0221] In the above embodiment, when the number of superiority bonuses awarded in a sub-boss battle with one sub-boss exceeds the upper limit, the superiority bonus associated with the newly established first condition is not awarded (is invalidated) in the sub-boss battle with that sub-boss. Regarding this process, for example, the player terminal 1 may receive from the server 100 the occurrence times of all superiority bonuses (first advantageous conditions) that have occurred, regardless of whether they are valid or invalid, and determine (judge) whether each superiority bonus (first advantageous condition) is valid or invalid within the player terminal 1. Specifically, the player terminal 1 may first determine whether each superiority bonus (first advantageous condition) was valid at the time of occurrence by reproducing the occurrence state of each superiority bonus (first advantageous condition) at the time of occurrence, and narrow down the superiority bonuses (first advantageous conditions) that were valid at the time of occurrence. After narrowing down the superiority bonuses, the results may be compared with the current time to determine which superiority bonuses (first advantageous conditions) are valid or invalid at the current time. This may be a two-stage calculation. By doing this, it becomes unnecessary for server 100 to determine (judge) whether the advantageous bonus (first advantageous condition) is valid or invalid at the time of occurrence, thereby making it possible to reduce the calculation load and implementation load on server 100.
[0222] It should be noted that instead of the information relating to each time described above, the time that has elapsed since the start of the event battle period, or the time until the end of the event battle period, may be used.
[0223] The information processing program for executing the processes in the above-described embodiments may be stored in a computer-readable non-transitory storage medium and provided as such. Furthermore, the information processing program may be provided as a player terminal or information processing system that includes such a storage medium. Furthermore, the above-described embodiments may also be provided as an information processing method that realizes each function and step shown in the flowchart. [Explanation of symbols]
[0224] 1. Player terminal 100 servers S Information Processing System
Claims
1. A process for allowing a player to select one of a plurality of opponents, including opponents for which predetermined conditions are set; A process of playing a competitive game against the opponent selected by the player; a process of granting advantageous conditions that are advantageous to a player in the competitive game against opponents other than the opponent for which the predetermined condition is satisfied when the predetermined condition is satisfied in the competitive game; a process of displaying, for each of the opponents, a list of the advantageous conditions to be granted in the competitive game with the opponent in a manner that allows a player to distinguish the advantageous conditions from the list before the competitive game is started; An information processing program that causes a computer to carry out the above.
2. The opponent has parameters set, In the process of playing the competitive game, the parameters of the opponent are changed, In the process of granting the advantageous condition, when the parameter of the opponent reaches a specific value, it is determined that the predetermined condition is satisfied and the advantageous condition is granted; In the process of making the opponent selectable, the opponent whose parameter has reached the specific value is made unselectable. The information processing program according to claim 1 .
3. The plurality of opponents includes a plurality of opponents for which the predetermined condition is set, the advantageous condition is associated with a different opponent type for which the predetermined condition is set; In the process of granting the advantageous condition, the advantageous condition associated with the type of the opponent for which the predetermined condition is satisfied is granted.
3. The information processing program according to claim 1 or 2.
4. A plurality of the advantageous conditions may be granted in a overlapping manner in the competitive game against one of the opponents. The information processing program according to claim 3.
5. 1. An information processing method performed by one or more computers, comprising: A process for allowing the player to select one of a plurality of opponents including opponents having a predetermined condition; A process of playing a competitive game against the opponent selected by the player; a process of granting advantageous conditions that are advantageous to a player in the competitive game against opponents other than the opponent for which the predetermined condition is satisfied when the predetermined condition is satisfied in the competitive game; a process of displaying, for each of the opponents, a list of the advantageous conditions to be granted in the competitive game with the opponent in a manner that allows a player to distinguish the advantageous conditions from the list before the competitive game is started; An information processing method comprising:
6. An information processing system including one or more computers, The computer includes: A process for allowing the player to select one of a plurality of opponents including opponents having a predetermined condition; A process of playing a competitive game against the opponent selected by the player; a process of granting advantageous conditions that are advantageous to a player in the competitive game against opponents other than the opponent for which the predetermined condition is satisfied when the predetermined condition is satisfied in the competitive game; a process of displaying, for each of the opponents, a list of the advantageous conditions to be granted in the competitive game with the opponent in a manner that allows a player to distinguish the advantageous conditions from the list before the competitive game is started; An information processing system that carries out the above.
