JP7408756B1 - Information processing program, information processing method, and information processing system - Google Patents

Abstract

[Problem] To reduce the annoyance felt by a player.
[Solution] At least one of a plurality of predetermined games whose order is set in advance can be selected by a predetermined operation by a player, and the selected predetermined game is executed based on at least the input of the predetermined operation, and at a predetermined opportunity. Based on this, an auto mode is executed in which predetermined games are sequentially executed in order without requiring a predetermined operation by the player. In cases where the player can set whether or not to execute a production, and a specific game is executed based on input of a predetermined operation, and when a specific game is executed in auto mode with the predetermined production set to be executed. When a specific game is executed in auto mode in a state where the specified game is set to be executed, the specified effect is executed, and the specified effect is not executed, and the specified end condition is satisfied. to stop auto mode.
[Selection diagram] Figure 14

Description

Article 30, Paragraph 2 of the Patent Act applies on June 27, 2020 at https://priconne-redive. jp/news/update/18366/ https://dmg. priconne-redive. jp/news/detail. php? id=18366 https://dmg. priconne-redive. jp/news/? ym=202206 https://twitter. com/priconne_redive/status/1541255027188469761 https://twitter. Although the internal mechanism is not disclosed at com/priconne_redive, the invention is disclosed as a readable summary of the invention.

Article 30, Paragraph 2 of the Patent Act applies on June 30, 2020 at https://priconne-redive. jp/news/information/18392/ https://dmg. priconne-redive. jp/news/detail. php? id=18392 https://dmg. priconne-redive. jp/news/? ym=202206 https://twitter. com/priconne_redive/status/1542342680025649152 https://twitter. com/priconne_redive https://www. youtube. com/watch? Although the internal mechanism is not disclosed at v=73E1krEumXM, the invention is disclosed as a readable outline of the invention.

Article 30, Paragraph 2 of the Patent Act applies on June 30, 2020 https://itunes. apple. com/jp/app/id1134429300 https://play. google. com/store/apps/details? id=jp. co. cygames. princessconnectredive https://dmg. priconne-redive. A game service implementing the system according to the present invention is released at jp/

The present invention relates to an information processing program, an information processing method, and an information processing system.

Conventionally, as shown in Patent Document 1, for example, an information processing method has been proposed in which a game is automatically executed and the game is treated as if it had been completed.

Patent No. 7029011

However, if a player is forced to repeatedly perform tasks for automatic execution of a game that is a target of automatic execution, there is a risk that the player may feel troublesome.

An object of the present invention is to provide an information processing program, an information processing method, and an information processing system that can reduce the annoyance felt by players.

In order to solve the above problems, the information processing program
A process of enabling a player to select at least one of a plurality of predetermined games whose order is set in advance by a predetermined operation;
a process of executing the selected predetermined game based on at least the input of the predetermined operation;
A process of executing an auto mode in which the predetermined games are sequentially executed in the order without requiring the predetermined operation by the player based on a predetermined opportunity;
Processing that allows a player to set whether or not to execute a predetermined effect when a specific game included in the plurality of predetermined games is executed in the auto mode;
When the specific game is executed based on the input of the predetermined operation, and when the specific game is executed in the auto mode in a state where execution of the predetermined effect is set , the predetermined effect is executed. If the specific game is executed in the auto mode in a state where it is set not to execute the predetermined effect, the specific game is executed with the predetermined effect not executed. processing and
processing for stopping the auto mode when a predetermined termination condition is met;
Let the computer carry out the
By executing the auto mode, the predetermined games that have not yet been cleared can be executed sequentially based on the order ;
The predetermined game progresses as parameters related to the predetermined game change,
The predetermined performance is progressed by the player's operation without any variation in the parameters .

a process of consuming a predetermined consideration in response to execution of the predetermined game;
During execution of the auto mode, when a predetermined operation unit is operated, a process of notifying the player of the total amount of the predetermined consideration consumed up to now;
The computer may further perform the steps .

Processing that allows a player to set stop information for stopping the auto mode when the specific game executed in the auto mode does not satisfy a predetermined clearing condition,
Furthermore, let the computer carry out the
The predetermined end condition may include that the specific game executed in the auto mode does not satisfy the predetermined clear condition while the stop information is set.

In order to solve the above problems, the information processing method is
An information processing method performed by one or more computers, the method comprising:
The computer includes:
A process of enabling a player to select at least one of a plurality of predetermined games whose order is set in advance by a predetermined operation;
a process of executing the selected predetermined game based on at least the input of the predetermined operation;
A process of executing an auto mode in which the predetermined games are sequentially executed in the order without requiring the predetermined operation by the player based on a predetermined opportunity;
Processing that allows a player to set whether or not to execute a predetermined effect when a specific game included in the plurality of predetermined games is executed in the auto mode;
When the specific game is executed based on the input of the predetermined operation, and when the specific game is executed in the auto mode in a state where execution of the predetermined effect is set , the predetermined effect is executed. If the specific game is executed in the auto mode in a state where it is set not to execute the predetermined effect, the specific game is executed with the predetermined effect not executed. processing and
processing for stopping the auto mode when a predetermined termination condition is met;
carry out the
By executing the auto mode, the predetermined games that have not yet been cleared can be executed sequentially based on the order ;
The predetermined game progresses as parameters related to the predetermined game change,
The predetermined performance is progressed by the player's operation without any variation in the parameters .

In order to solve the above problems, the information processing system
An information processing system comprising one or more computers,
The computer includes:
A process of enabling a player to select at least one of a plurality of predetermined games whose order is set in advance by a predetermined operation;
a process of executing the selected predetermined game based on at least the input of the predetermined operation;
A process of executing an auto mode in which the predetermined games are sequentially executed in the order without requiring the predetermined operation by the player based on a predetermined opportunity;
Processing that allows a player to set whether or not to execute a predetermined effect when a specific game included in the plurality of predetermined games is executed in the auto mode;
When the specific game is executed based on the input of the predetermined operation, and when the specific game is executed in the auto mode in a state where execution of the predetermined effect is set , the predetermined effect is executed. If the specific game is executed in the auto mode in a state where it is set not to execute the predetermined effect, the specific game is executed with the predetermined effect not executed. processing and
processing for stopping the auto mode when a predetermined termination condition is met;
carry out the
By executing the auto mode, the predetermined games that have not yet been cleared can be executed sequentially based on the order ;
The predetermined game progresses as parameters related to the predetermined game change,
The predetermined performance is progressed by the player's operation without any variation in the parameters .

According to the present invention, it is possible to reduce the annoyance felt by the player.

FIG. 1 is an explanatory diagram showing a schematic configuration of an information processing system. FIG. 2A is a diagram illustrating the hardware configuration of the player terminal. FIG. 2B is a diagram illustrating the hardware configuration of the server. FIG. 3A is a diagram illustrating an example of a home screen. FIG. 3B is a diagram illustrating an example of an ally character confirmation screen. FIG. 4A is a diagram illustrating an example of a story screen. FIG. 4B is a diagram illustrating an example of the quest screen. FIG. 5A is a diagram illustrating an example of the main quest screen. FIG. 5B is a first diagram illustrating an example of the main quest selection screen. FIG. 5C is a second diagram illustrating an example of the main quest selection screen. FIG. 6A is a diagram illustrating an example of a party selection screen. FIG. 6B is a diagram illustrating an example of a support character confirmation pop-up display. FIG. 7A is a diagram illustrating an example of a battle game screen. FIG. 7B is a diagram illustrating an example of the first result screen. FIG. 7C is a diagram illustrating an example of the second result screen. FIG. 8A is a diagram illustrating an example of a BOSS story screen. FIG. 8B is a diagram illustrating an example of area clear display. FIG. 9A is a diagram illustrating an example of a party selection screen for automatic progression. FIG. 9B is a diagram illustrating an example of an automatic ongoing support confirmation pop-up display. FIG. 2 is a first diagram illustrating an example of an auto progress setting screen in the main quest. FIG. 2 is a second diagram illustrating an example of an auto progress setting screen in the main quest. FIG. 7 is a third diagram illustrating an example of an auto progress setting screen in the main quest. FIG. 13A is a diagram illustrating an example of a stamina recovery screen. FIG. 13B is a diagram illustrating an example of a stamina recovery confirmation screen. FIG. 13C is a diagram illustrating an example of a stamina shortage confirmation screen. FIG. 2 is a first diagram illustrating an example of an automatic progress setting screen when forming support characters in the main quest. FIG. 7 is a second diagram illustrating an example of an automatic progression setting screen when forming support characters in the main quest. FIG. 7 is a third diagram illustrating an example of an auto-progress setting screen when forming support characters in the main quest. FIG. 17A is a first diagram illustrating an example of a battle game screen during automatic progression in the main quest. FIG. 17B is a diagram illustrating an example of the first result screen during automatic progression in the main quest. FIG. 17C is a first diagram illustrating an example of the second result screen during automatic progression in the main quest. FIG. 18A is a second diagram illustrating an example of a battle game screen during automatic progression in the main quest. FIG. 18B is a second diagram illustrating an example of the second result screen during automatic progression in the main quest. FIG. 19A is a first diagram illustrating an example of an automatic progress stop notification screen in the main quest. FIG. 19B is a second diagram illustrating an example of the automatic progress stop notification screen in the main quest. FIG. 19C is a third diagram illustrating an example of an automatic progress stop notification screen in the main quest. FIG. 20A is a diagram illustrating an example of an automatic progression reward list display in the main quest. FIG. 20B is a diagram illustrating an example of a story release display in the main quest. FIG. 20C is a diagram illustrating an example of a friend application confirmation screen in the main quest. FIG. 21A is a first diagram illustrating an example of an automatic progress stop display in the main quest. FIG. 21B is a second diagram illustrating an example of an automatic progress stop display in the main quest. FIG. 22 is a diagram illustrating an example of a setting screen. FIG. 23A is a diagram illustrating an example of an event quest screen. FIG. 23B is a first diagram illustrating an example of the event quest selection screen. FIG. 23C is a second diagram illustrating an example of the event quest selection screen. FIG. 24A is a diagram illustrating an example of a party selection screen for automatic progression. FIG. 24B is a first diagram illustrating an example of an automatic progress setting screen in the event quest. FIG. 24C is a second diagram illustrating an example of an automatic progress setting screen in the event quest. FIG. 25A is a diagram illustrating an example of an automatic progress setting screen when stamina is insufficient. FIG. 25B is a diagram illustrating an example of a stamina recovery dialog. FIG. 25C is a diagram illustrating an example of a stamina recovery result screen. FIG. 26A is a first diagram illustrating an example of a battle game screen during automatic progress in an event quest. FIG. 26B is a diagram illustrating an example of the first result screen during automatic progress in the event quest. FIG. 26C is a first diagram illustrating an example of the second result screen during automatic progress in the event quest. FIG. 27A is a second diagram illustrating an example of a battle game screen during automatic progress in an event quest. FIG. 27B is a second diagram illustrating an example of the second result screen during automatic progress in the event quest. FIG. 28A is a first diagram illustrating an example of an automatic progression reward list display in an event quest. FIG. 28B is a first diagram illustrating an example of a story release display in an event quest. FIG. 29A is a second diagram illustrating an example of an automatic progression reward list display in an event quest. FIG. 29B is a second diagram illustrating an example of a story release display in an event quest. FIG. 30A is a first diagram illustrating an example of an automatic progress stop display in an event quest. FIG. 30B is a second diagram illustrating an example of an automatic progress stop display in an event quest. FIG. 31 is a diagram illustrating the memory configuration and computer functions in the player terminal. FIG. 32 is a flowchart illustrating an example of management processing at the player terminal.

One aspect of the embodiment of the present invention will be described in detail below with reference to the accompanying drawings. The dimensions, materials, and other specific numerical values shown in these embodiments are merely examples for easy understanding, and do not limit the present invention unless otherwise specified. In this specification and the drawings, elements with substantially the same functions and configurations are given the same reference numerals to omit redundant explanation, and elements not directly related to the present invention are omitted from illustration. do.

(Overall configuration of information processing system S)
FIG. 1 is an explanatory diagram showing a schematic configuration of an information processing system S. As shown in FIG. The information processing system S is a so-called client-server system that includes a player terminal 1 functioning as a client, that is, a game terminal, a server 1000, and a communication network N having a communication base station Na.

In the information processing system S of this embodiment, the player terminal 1 and the server 1000 function as a game device G. The player terminal 1 and the server 1000 are each assigned the role of controlling the progress of the game, and the game can progress through cooperation between the player terminal 1 and the server 1000.

Player terminal 1 can establish communication with server 1000 via communication network N. The player terminal 1 includes a wide range of electronic devices that can be connected to the server 1000 for wireless or wired communication. Examples of the player terminal 1 include a smartphone, a mobile phone, a tablet device, a personal computer, and a game device. In this embodiment, a case where a smartphone is used as the player terminal 1 will be described.

The server 1000 is communicatively connected to a plurality of player terminals 1 . The server 1000 accumulates various types of information for each player who plays the game. Furthermore, the server 1000 performs processes such as updating accumulated information and causing the player terminal 1 to download images and various information based on operations input from the player terminal 1.

The communication base station Na is connected to the communication network N and transmits and receives information to and from the player terminal 1 wirelessly. The communication network N is composed of a mobile phone network, an 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 1000.

(Hardware configuration of player terminal 1 and server 1000)
FIG. 2A is a diagram illustrating the hardware configuration of the player terminal 1. Further, FIG. 2B is a diagram illustrating the hardware configuration of the server 1000. 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 section 18, a communication section 20, an input section 22, and an output section 24. be done.

Further, as shown in FIG. 2B, the server 1000 includes a CPU 1010, a memory 1012, a bus 1014, an input/output interface 1016, a storage section 1018, a communication section 1020, an input section 1022, and an output section 1024.

Note that the configurations and functions of the CPU 1010, memory 1012, bus 1014, input/output interface 1016, storage section 1018, communication section 1020, input section 1022, and output section 1024 of the server 1000 are the same as those of the CPU 10, memory 12, and output section 1024 of the player terminal 1, respectively. The bus 14, input/output interface 16, storage section 18, communication section 20, input section 22, and output section 24 are substantially the same. Therefore, below, the hardware configuration of the player terminal 1 will be explained, and the explanation of the server 1000 will be omitted.

The CPU 10 operates programs stored in the memory 12 to control the progress of the game. The memory 12 is configured with a ROM (Read Only Memory) or a RAM (Random Access Memory), and stores programs and various data necessary for controlling the progress of the game. Memory 12 is connected to CPU 10 via bus 14.

An input/output interface 16 is connected to the bus 14 . A storage section 18 , a communication section 20 , an input section 22 , and an output section 24 are connected to the input/output interface 16 .

The storage unit 18 is composed of a semiconductor memory such as a DRAM (Dynamic Random Access Memory), and stores various programs and data. In the player terminal 1, programs and data stored in the storage unit 18 are loaded into the memory 12 (RAM) by the CPU 10.

The communication unit 20 is wirelessly connected to the communication base station Na, and sends and receives information such as various data and programs to and from the server 1000 via the communication network N. In the player terminal 1, programs and the like received from the server 1000 are stored in the memory 12 or the storage unit 18.

The input unit 22 includes, for example, a touch panel for inputting (receiving operations) a player's operations, buttons, a keyboard, a mouse, a cross key, an analog controller, and the like. Further, the input unit 22 may be a dedicated controller provided in the player terminal 1 or connected (externally attached) to the player terminal 1. Furthermore, the input unit 22 may be configured with an acceleration sensor that detects the tilt or movement of the player terminal 1, or a microphone that detects the player's voice. That is, the input unit 22 broadly includes devices that can input the player's intention in a discernible manner.

The output unit 24 includes a display device and a speaker. Note that the output unit 24 may be a device connected (externally attached) to the player terminal 1. In this embodiment, the player terminal 1 includes a display 26 as the output section 24 and a touch panel provided to overlap the display 26 as the input section 22.

(Game content)
Next, the content of the game provided by the information processing system S (game device G) of this embodiment will be explained using an example. In this embodiment, a so-called battle game in which a friendly character competes against an enemy character is provided. In the game of this embodiment, a plurality of ally characters are provided to the player by the game management side. For example, a player can own a plurality of ally characters acquired through a lottery called gacha or ally characters distributed by the management side.

The player can form a party by selecting a plurality of ally characters (five in this case) from among the ally characters that the player owns. The player can play a battle game using the formed party. In a battle game, the objective is for friendly characters formed in a party to defeat (clear) enemy characters and obtain rewards. The player can play multiple types of battle games with different enemy characters and difficulty levels.

FIG. 3A is a diagram showing an example of the home screen 40. FIG. 3B is a diagram showing an example of the ally character confirmation screen 50. FIG. 4A is a diagram showing an example of the story screen 60. FIG. 4B is a diagram showing an example of the quest screen 70. On the display 26 of the player terminal 1, game screens as shown in FIGS. 3A, 3B, 4A, and 4B are displayed. In this embodiment, the game screen is roughly divided into a normal screen and a battle screen.

The normal screen is mainly a screen for waiting for the game to start, and a screen for the player to make various settings and check information. On the other hand, the battle screen is a screen displayed on the display 26 from the start to the end of the battle game. Here, all screens other than the battle screen become normal screens. The normal screen includes a home screen 40 shown in FIG. 3A, an ally character confirmation screen 50 shown in FIG. 3B, a story screen 60 shown in FIG. 4A, a quest screen 70 shown in FIG. 4B, a gacha screen (not shown), and a menu screen (not shown). , a plurality of screens such as a title screen (not shown) are provided.

The home screen 40 shown in FIG. 3A is the first screen displayed after the player taps the display 26 on the title screen (not shown) (that is, after starting the game). As shown in FIG. 3A, on the home screen 40, a menu bar 41 is displayed at the bottom of the display 26. The menu bar 41 is displayed at the bottom of the display 26 on normal screens other than the title screen (not shown).

The menu bar 41 is provided with a plurality of operation units that can be operated (tapped) by the player. The menu bar 41 includes a home screen selection operation section 41a labeled "Home", an ally character confirmation screen selection operation section 41b labeled "Character", a story screen selection operation section 41c labeled "Story", A quest screen selection operation section 41d labeled "Quest", a gacha screen selection operation section 41e labeled "Gacha", and a menu screen selection operation section 41f labeled "Menu" are provided. Note that in the menu bar 41, the operation units corresponding to each screen are highlighted so that the screen currently displayed on the display 26 can be identified.

When the home screen selection operation section 41a is tapped, the home screen 40 shown in FIG. 3A is displayed on the display 26. Further, when the ally character confirmation screen selection operation section 41b is tapped, an ally character confirmation screen 50 shown in FIG. 3B is displayed on the display 26. Further, when the story screen selection operation section 41c is tapped, a story screen 60 shown in FIG. 4A is displayed on the display 26. Further, when the quest screen selection operation section 41d is tapped, a quest screen 70 shown in FIG. 4C is displayed on the display 26.

Further, when the gacha screen selection operation section 41e is tapped, a gacha screen (not shown) is displayed on the display 26. Further, when the menu screen selection operation section 41f is tapped, a menu screen (not shown) is displayed on the display 26. Although a detailed explanation will be omitted, on the gacha screen, you can perform a gacha lottery in which you can win an ally character by lottery. Also, on the menu screen, you can check game settings and various information.

At the top of the home screen 40, a header display area 42 is provided. In the header display area 42, player information associated with the player ID is displayed. For example, in the header display area 42, level information 42a indicating the player level and a stamina display bar 42b indicating the stamina of the player are displayed. Further, as shown in FIG. 3A, the player's stamina is displayed numerically at the bottom of the stamina display bar 42b.

The player information includes a player ID, ally character identification information for identifying ally characters owned by the player (hereinafter referred to as ally character ID), level information 42a, stamina information displayed on the stamina display bar 42b, and a story to be described later. This includes progress information, battle game clear information, and in-game currency information indicating the amount of in-game currency owned by the player.

Note that stamina is a parameter necessary for the player to play the battle game. In this embodiment, a plurality of types of battle games are provided, and each battle game has a stamina consumption value necessary for playing, a maximum number of times the game can be played per day, etc. When playing a battle game in which a consumption value of stamina required for play is set, the player will play the battle game by consuming stamina. Therefore, if the player lacks stamina, the player cannot play the battle game.

Although a detailed explanation will be omitted, when a player wins a battle game, he or she can obtain a predetermined value as a player experience value. Then, each time the player's experience value reaches a certain value, the player level increases. An upper limit value of stamina is set for the player level. As the player level increases, the upper limit of stamina increases. Stamina is recovered by a predetermined value (for example, 1 point) at fixed time intervals (for example, 5 minutes) within the upper limit. The stamina display bar 42b displays the current remaining amount of stamina with respect to the upper limit of stamina so that it can be visually grasped. In addition, the stamina value displayed at the bottom of the stamina display bar 42b, "260/277" in the example of FIG. The stamina "260" is displayed.

Further, when the ally character confirmation screen selection operation section 41b of the menu bar 41 is tapped, the ally character confirmation screen 50 shown in FIG. 3B is displayed on the display 26. On the ally character confirmation screen 50, all images of ally characters corresponding to the ally character ID associated with the player ID are displayed.

That is, on the ally character confirmation screen 50, all ally characters owned by the player are displayed. Note that the ally character ID is assigned a different ID for each ally character. Then, when the player acquires a new ally character through a gacha lottery or the like, the ally character ID of the acquired ally character is associated with the player ID of the player.

Information regarding experience values and information regarding levels are stored in association with the ally character ID. Experience points increase when you win a battle game (described later) or when you use a predetermined item. The level is set corresponding to the experience value, and the level increases each time the experience value reaches a predetermined value. Note that an upper limit value of the level is set for each ally character, and the level increases only within the range up to the upper limit value.

Furthermore, base values of combat power such as life points, attack power, defense power, etc. are set for the ally characters based on their levels. The higher the fighting power of the ally character, the more advantageously the player can proceed with the battle game. Furthermore, each base value set for an ally character increases as the level increases.

Furthermore, it is possible to equip (set) equipment such as weapons and armor to the ally character. For each piece of equipment, an additional value for attack power, defense power, etc. is set. When equipment is equipped, the additional value of each equipment is added to the above base value, and the combat power of the ally character can be increased. Information regarding equipment such as weapons and armor is also associated with the ally character ID and constituted as part of the player information.

When the story screen selection operation section 41c of the menu bar 41 is tapped, a story screen 60 shown in FIG. 4A is displayed on the display 26. As shown in FIG. 4A, the story screen 60 displays a menu bar 41, a header display area 42, a main story selection operation section 61, a character story selection operation section 62, and an extra story selection operation section 63.

When the main story selection operation section 61 on the story screen 60 is tapped, a main story screen (not shown) is displayed on the display 26. The main story screen displays multiple main stories that will be released depending on the progress of the "main quest" described below. When a new main story is released by the player progressing through the main quest described below, the player can view the released main story from a main story screen (not shown).

Further, when the character story selection operation section 62 in the story screen 60 shown in FIG. 4A is operated (tapped), a character story (not shown) that is released depending on the intimacy level of the ally character is displayed on the display 26. Ru.

Note that the intimacy level of an ally character increases when the player wins a battle game, which will be described later, or when a predetermined item is used. Each time the degree of intimacy reaches a predetermined value, the rank of the degree of intimacy increases. Note that an upper limit value of the rank of intimacy is set for the ally character, and the rank increases only within the range up to the upper limit value. When an ally character's intimacy level reaches the upper limit, all character stories for that ally character will be released. Then, when a new character story is released, the player can view the released character story from a character story screen (not shown).

Further, when the extra story selection operation section 63 in the story screen 60 shown in FIG. 4A is operated (tapped), an extra story screen (not shown) is displayed on the display 26. On the extra story screen, for example, a plurality of extra stories that are released depending on the progress of an "event quest" to be described later are displayed. When a new extra story is released by the player progressing through an event quest described below, the player can view the released extra story from an extra story screen (not shown).

Returning to FIG. 3A, when the quest screen selection operation section 41d of the menu bar 41 is tapped, the quest screen 70 shown in FIG. 4B is displayed on the display 26. The quest screen 70 displays a menu bar 41, a header display area 42, and a plurality of game type selection operation sections 71 in which types of battle games being provided are described. Here, five types of battle games are provided, and five game type selection operation sections 71 are displayed.

The game type selection operation section 71 includes a main quest selection operation section 71a marked with "Main Quest", a guild battle selection operation section 71b marked with "Guild Battle", and a 1V1 battle selection section marked with "1V1 Battle". It includes an operation section 71c, a 3V3 battle selection operation section 71d labeled "3V3 Battle", and an event quest selection operation section 71e labeled "Event".

When the main quest selection operation section 71a is tapped, a main quest screen 72 (FIG. 5A), which will be described later, is displayed on the display 26. Further, when the guild battle selection operation section 71b is tapped, a guild battle screen (not shown) is displayed on the display 26. Similarly, when the 1V1 battle selection operation section 71c is tapped, a 1V1 battle screen (not shown) is displayed on the display 26. Further, when the 3V3 battle selection operation section 71d is tapped, a 3V3 battle screen (not shown) is displayed on the display 26. Further, when the event quest selection operation section 71e is tapped, an event quest screen 172 (FIG. 23A), which will be described later, is displayed on the display 26.

Note that the "event quest" can be played by the player over a preset period (for example, 10 days), and the event quest selection operation section 71e is displayed on the display 26 only during this period. That will happen. That is, outside the execution period of the "event quest", the event quest selection operation section 71e is hidden, and the game type selection operation section 71 includes the main quest selection operation section 71a, the guild battle selection operation section 71b, and the 1V1 battle selection operation section. Four game type selection operation sections 71, 71c and 3V3 battle selection operation section 71d, are displayed.

Note that some battle games have release conditions set. Examples of release conditions include that the player level is at least a predetermined value, that another predetermined battle game has been cleared, and so on. Moreover, a plurality of battle games (layers or rounds) belong to each battle game type. Each of these battle games also has release conditions set. Then, when the release condition is satisfied, the game release information included in the player information is updated.

In the player terminal 1, it is determined whether a battle game has been released based on the game release information, and only the game type selection operation section 71 of the battle game that satisfies the release conditions accepts the player's operation (tap). . Therefore, the player can only play battle games that satisfy the release conditions.

When the main quest selection operation section 71a in the quest screen 70 shown in FIG. 4B is tapped, the main quest screen 72 shown in FIG. 5A is displayed on the display 26.

FIG. 5A is a diagram illustrating an example of the main quest screen 72. FIG. 5B is a first diagram illustrating an example of the main quest selection screen 74. FIG. 5C is a second diagram illustrating an example of the main quest selection screen 74.

The main quest screen 72 displays a menu bar 41, a header display area 42, and a main quest operation section 73 for selecting a plurality of battle games (layers) belonging to the main quest.

In the main quest, there are multiple floors for each area. For example, the first area has 15 levels of battle games from "1-1" to "1-15". Furthermore, in the second area, there are 15 levels of battle games from "2-1" to "2-15". For example, there are several dozen areas each having multiple levels.

The main quest operation section 73 also displays clear information for each battle game. Clear information is indicated by three stars, for example. In a battle game that belongs to the main quest, when the battle game is cleared, stars are acquired according to the number of ally characters whose life points are 0 at the time of clearing. For example, if there are no friendly characters with 0 life points, you will get 3 stars, and if there is only 1 friendly character with 0 life points, you will get 2 stars. , if there are two or more ally characters whose life points are 0, one star is obtained.

In the example of FIG. 5A, three stars are obtained in the "1-1" battle game, two stars are obtained in the "1-2" battle game, and one star is obtained in the "1-3" battle game. has been acquired. Furthermore, in the battle game "1-4", it is reported that no stars have been acquired and this battle game has not been cleared.

Furthermore, in the main quest, the release condition is to clear the previous battle game. For example, in the example shown in FIG. 5A, the battle game "1-4" is unlocked by clearing the battle game "1-3", but after that ("1-5" and later, not shown), the battle game "1-4" is unlocked. ) battle game has not yet been released.

Furthermore, when the battle game on the last floor belonging to a predetermined area is cleared, the next area will be released. Specifically, for example, when the battle game "1-15", which is the battle game on the last level belonging to the first area, is cleared, the second area is released. When the second area is released, the player can select "2-1", which is the first battle game belonging to the second area. Similarly, when the battle game "2-15", which is the battle game on the last level belonging to the second area, is cleared, the third area is released. When the third area is released, the player can select "3-1", which is the first battle game belonging to the third area.

In this way, the player can sequentially release areas by successively clearing the selectable battle games. However, if you clear the battle game on the last floor (for example, "60-15") belonging to the last area implemented in the game (for example, the 60th area), the next area (for example, the 61st area) will be cleared. (areas) will not be released immediately. In this case, the next area (for example, the 61st area) will be released at the timing when the next area (for example, the 61st area) is installed. For example, a predetermined number (for example, one or more) of new areas may be implemented (added) every predetermined period (for example, one month).

On the main quest screen 72, for example, when the main quest operation section 73 of a battle game "1-4" is operated (tapped), a main quest selection screen 74 shown in FIG. 5B is displayed on the display 26. The main quest selection screen 74 displays enemy characters appearing in the battle game and items (rewards) that can be obtained in the battle game.

As mentioned above, in the main quest, new areas are added regularly, making it possible to periodically stimulate the desire of advanced players to play. However, if the difficulty level of the battle game is set relatively low, advanced players may feel tired because they have to regularly play many battle games that are low in difficulty and have an extremely low risk of defeat. There is a possibility that the player will memorize the information and lose interest in the game. Furthermore, even if the difficulty level of the battle game is set relatively high, the need to play many battle games on a regular basis may become tedious and reduce the player's desire to play the game. There is.

Also, beginner players need to play many battle games up to the last level battle game (for example, "60-15") that belongs to the last area (for example, the 60th area) implemented in the game. As a result, you may feel tired. Furthermore, as new areas are added on a regular basis, the number of battle games that need to be completed increases further, which may reduce the player's desire to play the game.

Therefore, in the present embodiment, an auto-progress function is provided in the main quest, which makes it possible to automatically execute battle games in sequence to reduce the annoyance of the player. The details will be explained later, but by using the auto progression function, the battle games in the main quests that have not yet been cleared will be automatically executed one after another, without requiring any operation input from the player, until a predetermined ending condition is met. becomes possible.

For example, if the battle game "1-4" is started using the auto progression function, and the battle game "1-4" is cleared, the auto progression will automatically start "1-4". 5" battle game begins. Similarly, when the battle game "1-5" is cleared, the battle game "1-6" is automatically started by automatic progression.

By using the auto-progression function, it is possible to reduce the annoyance for both advanced players and beginner players, thereby suppressing the possibility that the players will lose their desire to play the game. becomes possible.

Although details will be described later, in this embodiment, the battle game screen 80 (FIG. 17A) is displayed on the display 26 even when the automatic progression function is used. This allows the player to view the battle between the ally character and the enemy character on the battle game screen 80 (FIG. 17A) while reducing the player's annoyance. This makes it possible to suppress the possibility that the presentation effect will deteriorate.

As shown in FIG. 5B, the main quest selection screen 74 is provided with a checkbox for enabling the auto-progress function, and by operating (tapping) this check box, the auto-progress function is enabled and It is possible to disable it.

That is, as shown in FIG. 5B, when a check is displayed in the check box, the automatic progress function is enabled, and as shown in FIG. 5C, when the check box is not checked, the automatic progress function is enabled. Progress functionality is disabled.

In this embodiment, a case has been described in which enabling and disabling of the automatic progress function can be switched by a check box, but the present invention is not limited to this. For example, by displaying both an operation section for enabling the auto-progression function and an operation section for disabling the auto-progression function on the display 26, and having the player operate (tap) either of these operation sections. , the automatic progress function may be configured to be switchable between valid and invalid. Furthermore, the checkboxes and operation units that enable and disable the automatic progression function described above may be displayed on a screen other than the main quest selection screen 74. For example, on the main quest screen 72, the auto progression party selection screen 77a (described later), the auto progression setting screen 100 (described later), the auto progression setting screen 100a (described later), etc., there is a check box that enables or disables the auto progression function described above. It is also possible to display an operation section.

Furthermore, in the present embodiment, in the main quest, battle games in which the auto progression function can be used are limited to battle games that the player has not yet cleared. Therefore, on the main quest selection screen 74 for the battle game of the main quest that has already been cleared, the checkbox for enabling the automatic progression function is displayed in a non-selectable state (grayed out). Note that on the main quest selection screen 74 for a battle game of a main quest that has already been cleared, the checkbox itself for enabling the automatic progression function may be hidden. However, the auto progression function may also be available for battle games with cleared main quests.

In addition, the main quest selection screen 74 displays stamina after consuming stamina when challenging a battle game by consuming stamina. Specifically, as shown in FIGS. 5B and 5C, on the event quest selection screen 174, when the battle game "1-4" is executed, stamina is consumed from the current stamina 260 to 252. It will be displayed that it is scheduled to change to.

The main quest selection screen 74 also includes a challenge operation section 75 labeled "Challenge" for challenging the battle game selected by the player, and a challenge operation section 75 for canceling the process corresponding to the currently displayed screen. A cancel operation section 76 labeled "Cancel" is displayed.

When the cancel operation unit 76 is operated (tapped), the main quest screen 72 shown in FIG. 5A is displayed on the display 26, and the challenge to the selected battle game "1-4" is canceled.

Further, when the auto progress function is disabled, that is, when the challenge operation section 75 in FIG. 5C is operated (tapped), a party selection screen 77 shown in FIG. 6A is displayed on the display 26.

FIG. 6A is a diagram illustrating an example of the party selection screen 77. All ally characters owned by the player are displayed on the party selection screen 77. Further, a selected ally character display area 78 is displayed below the party selection screen 77 to display the selected ally characters.

Here, in this embodiment, the player can perform friend settings, follow settings, support settings, etc. on a menu screen (not shown). In the friend setting, the player can register as friends with other players. Friend registration is performed by a player sending a friend request to another player and the other player approving the friend request, or by the player approving a friend request sent from another player.

When the friend registration is completed, the player ID and the other player ID are associated as friends, and the other player ID is stored in the server 1000 as the player's friend ID. Note that the player ID is for identifying the player, and a different ID is assigned to each player. That is, the player ID is assigned an ID different from other player IDs.

In the follow setting, a player can register other players to follow. Follow registration is performed by a player sending a follow request to another player, and approval from the other player is not required. When follow registration is completed, the player ID and other player IDs are associated with each other, and the other player IDs are stored in the server 1000 as the player's follow IDs.

In support settings, a player can set an ally character that the player owns as a support character (hereinafter referred to as a support character) that can be lent to another player. Other players can borrow the support character set by the player and play against enemy characters. Here, the player can earn rewards by setting a support character. For example, the player can receive in-game currency as a reward for developing an ally character that the player owns.

For example, by consuming a predetermined amount of in-game currency (mana), a player can borrow a support character set as a support character from another player who has completed friend registration in a main quest battle game. . Furthermore, by consuming a predetermined number of in-game currencies, the player can also borrow support characters from other players (non-friends) for whom friend registration has not been completed in the main quest battle game.

As shown in FIG. 6A, the party selection screen 77 displays an all operation section 90 labeled "All" and a support operation section 91 labeled "Support." When all the operation units 90 are operated, as shown in FIG. 6A, a list of all ally characters owned by the player is displayed. In addition, when the support operation unit 91 is operated, support characters of other players whose friend registration has been completed and support characters of other players (non-friends) selected at random are displayed in a list.

When the player operates (tap) a displayed ally character on the party selection screen 77, the operated (tapped) ally character is displayed in the selected ally character display area 78. That is, here, the ally character ID for use in the battle game (for determining the party) is selected from among the plurality of ally character IDs associated with the player ID. A party is formed by the player selecting a plurality of ally characters. Note that when forming a party, the same ally character cannot be set twice.

Further, on the party selection screen 77, a cancel operation section 76 and a battle start operation section 79 labeled "Battle Start" are displayed.

When the party formation is completed and the battle start operation section 79 is operated (tapped), if the support character is not included in the party formation, the battle game is started and a battle game screen 80 (FIG. 7A) is displayed on the display 26. Is displayed. On the other hand, if the support character is included in the party composition, the battle game is not started and a support character confirmation pop-up display 92 shown in FIG. 6B is displayed superimposed on the party selection screen 77.

FIG. 6B is a diagram illustrating an example of the support character confirmation pop-up display 92. As shown in FIG. 6B, the support character confirmation pop-up display 92 displays the types of support characters that the player has included in the party composition. Further, in the support character confirmation pop-up display 92, the player names of other players who are owners of the support characters included in the party formation by the player are displayed. Furthermore, the support character confirmation pop-up display 92 displays the amount of in-game currency that will be consumed when a battle game is played using a support character. Further, in the support character confirmation pop-up display 92, the amount of in-game currency held by the player is displayed.

Further, the support character confirmation pop-up display 92 displays a cancel operation section 93 marked with "Cancel" and an OK operation section 94 marked with "OK".

When the cancel operation section 93 is operated, the display of the support character confirmation pop-up display 92 ends, and a party selection screen 77 is displayed on the display 26. When the OK operation unit 94 is operated, a battle game is started, and a battle game screen 80 (FIG. 7A) is displayed on the display 26.

FIG. 7A is a diagram illustrating an example of the battle game screen 80. FIG. 7B is a diagram illustrating an example of the first result screen 83. FIG. 7C is a diagram illustrating an example of the second result screen 85. During the battle game, a battle game screen 80 is displayed as shown in FIG. 7A. On the battle game screen 80, an ally character and an enemy character are displayed on the display 26. The ally character operates under computer control and deals damage to or receives damage from the enemy character. In addition, the enemy character operates under computer control and damages or receives damage from the ally character.

When damage points are given to the enemy character, the damage points are subtracted from the enemy character's life points. Similarly, when damage points are given to an ally character, the damage points are subtracted from the ally character's life points. When the life points of all enemy characters become 0, the player wins (clear), and when all the ally characters' life points become 0 (defeat), the player loses.

Here, at the bottom of the battle game screen 80, as shown in FIG. 7A, an ally character display area 81 is provided. The ally character display area 81 displays a life point 81a and a special move gauge 81b for each ally character. The special move gauge 81b increases when an ally character receives damage from an enemy character or deals damage to an enemy character. When the special move gauge 81b reaches a predetermined maximum value, the ally character becomes able to use the special move. A special move deals more damage points to the enemy character than a normal attack, restores the life points of an ally character, or gives a special effect to the enemy character.

Here, there are two patterns of how to use the special move. One method is for the player to operate (tap) an ally character displayed in the ally character display area 81 whose special move gauge 81b has reached its maximum value. The other method is for an ally character to use a special move under computer control when the special move gauge 81b reaches its maximum value in the automatic activation state. Note that an auto selection operation section 82 is displayed on the battle game screen 80, and by operating the auto selection operation section 82, the player can switch between an automatic activation state and a manual activation state. When the automatic selection operation section 82 is operated (tapped) in the manual activation state, the automatic activation state is entered in which the special move is automatically used. Furthermore, when the auto selection operation section 82 is operated (tapped) in the auto activation state, the player enters a manual activation state in which the special move is manually used. Even in the automatic activation state, if the player operates (tap) an ally character when the special move gauge 81b has reached its maximum value and no special move is being used under computer control, the special move will be activated. It is possible to use.

When the battle game ends normally (normal end), the first result screen 83 is displayed on the display 26, as shown in FIG. 7B. FIG. 7B shows, as an example, the first result screen 83 when the ally character wins.

The first result screen 83 displays at least part of the game result information of the battle game. Further, on the first result screen 83, a next operation section 84 labeled "Next" is displayed.

When the next operation section 84 is operated (tapped), a second result screen 85 shown in FIG. 7C is displayed on the display 26.

The second result screen 85 displays at least part of the game result information of the battle game. Further, on the second result screen 85, a next operation section 86 labeled "Next" is displayed. Furthermore, when the next operation section 86 is operated (tapped), the display on the display 26 is switched from the battle screen to the normal screen. That is, the first result screen 83 and the second result screen 85 are part of the battle screen. In this embodiment, when the next operation unit 86 is operated (tapped), a main quest screen 72 shown in FIG. 5A is displayed on the display 26.

The game result information includes the ally character ID (party) of the ally character, the enemy character ID of the enemy character, and the remaining status information of the ally character and enemy character at the end of the battle (if the life points become 0 at the end of the battle game). ), damage points inflicted (total value), player operation information (manual activation state or auto activation state), battle log ID, battle game type information (main quest, guild battle, etc.), each type of battle game Contains information associated with (clear information, battle game hierarchy, etc.), assigned item information, etc.

In addition, whether it is in a manual activation state or an auto activation state, if it is in an automatic activation state from the start to the end of the battle game and the special move is not used manually by the player, it will be in an automatic activation state, otherwise it will be in a manual activation state. It becomes activated. Moreover, a battle log ID is uniquely assigned to each battle game. Further, the information associated with each type of battle game has different contents depending on the type of battle game.

FIG. 8A is a diagram illustrating an example of the BOSS story screen 95. In a battle game on the last level (for example, a "1-15" battle game) belonging to a predetermined area (for example, the first area), a BOSS character set for each area appears as an enemy character. . Then, after the battle game (for example, "1-15" battle game) of the last level belonging to a predetermined area (for example, the first area) has started, and before the battle with the BOSS character starts. At the front, a BOSS story screen 95 is displayed on the display 26. On the BOSS story screen 95, for example, a conversation between ally characters or performance images explaining the characteristics of the BOSS character are sequentially displayed in response to the player's operations. As a result, it is possible to increase the player's sense of tension and improve the performance effect when competing against the BOSS character.

Then, when the display of the BOSS story screen 95 ends in response to the player's operation, a battle game screen 80 is displayed on the display 26, and a battle with the BOSS character begins.

When the BOSS character is defeated (cleared), the battle game on the last floor belonging to a predetermined area is cleared, and the operation section 86 is operated (tapped) to proceed to the second result screen 85, an area clear display 96 is displayed. is displayed superimposed on the main quest screen 72.

FIG. 8B is a diagram illustrating an example of the area clear display 96. As shown in FIG. 8B, in the area clear display 96, "Area Clear!" is written, making it possible to notify the player that the battle game on the last level belonging to a predetermined area has been cleared. This makes it possible to give the player a sense of accomplishment.

Further, when the automatic progression function is enabled, that is, when the challenge operation section 75 in FIG. 5B is operated (tapped), an automatic progression party selection screen 77a (FIG. 9A) is displayed on the display 26.

FIG. 9A is a diagram illustrating an example of the automatic proceeding party selection screen 77a. As shown in FIG. 9A, the auto-progress party selection screen 77a displays a selected ally character display area 78 and a cancel operation section 76, similar to the party selection screen 77 described above.

Further, a next operation section 79 labeled "Next" is displayed on the automatic party selection screen 77a. Further, a caution display stating "*Auto progress setting in progress" is displayed at the bottom of the next operation section 79a. As a result, the player is informed that the auto progression function is scheduled to be used in the main quest battle game.

Further, as shown in FIG. 9A, the automatic proceeding party selection screen 77a displays all the operation sections 90 and the support operation section 91, similarly to the party selection screen 77 described above. When all the operation units 90 are operated, all ally characters possessed by the player are displayed in a list, as shown in FIG. 9A.

As described above, when a battle game is played using a support character, a predetermined in-game currency is consumed. That is, when a plurality of battle games are sequentially executed using the automatic progression function, a predetermined in-game currency is consumed each time a battle game is executed. Therefore, in this embodiment, when the support operation section 91 is operated on the auto-progress party selection screen 77a, an auto-progress support confirmation pop-up display 97 (FIG. 9B) is superimposed on the auto-progress party selection screen 77a. Ru.

FIG. 9B is a diagram illustrating an example of the auto-in-progress support confirmation pop-up display 97. As shown in FIG. 9B, in the auto progress support confirmation pop-up display 97, a warning is displayed stating, "During auto progress, the selected support character will be formed for the second and subsequent battles." This prevents the situation where a battle game is executed using the auto progression function with support characters organized, and the player's in-game currency is unintentionally depleted. It becomes possible.

Further, as shown in FIG. 9B, an OK operation section 98 marked with "OK" is displayed in the auto-in-progress support confirmation pop-up display 97. When the OK operation unit 98 is operated, the display of the auto progress support confirmation pop-up display 97 ends, and support characters of other players whose friend registration has been completed and a random selection are displayed on the auto progress party selection screen 77a. A list of support characters of other players (non-friends) will be displayed.

When the party formation is completed and the next operation section 79a is operated (tapped), if the support character is not included in the party formation, an auto progress setting screen 100 (FIG. 10) is displayed on the display 26. .

FIG. 10 is a first diagram illustrating an example of an automatic progress setting screen 100 in the main quest. FIG. 11 is a second diagram illustrating an example of the auto progress setting screen 100 in the main quest. FIG. 12 is a third diagram illustrating an example of the automatic progress setting screen 100 in the main quest. As shown in FIG. 10, on the auto-progress setting screen 100, the player can make detailed settings for the auto-progress function when using the auto-progress function in the main quest.

Specifically, as shown in FIG. 10, on the auto progress setting screen 100, the player can set any of three setting items as "auto progress stop condition setting." Specifically, the player can check any of the checkboxes marked "Until stamina runs out", the checkbox marked "Just before the BOSS appearance quest", or the checkbox marked "When the story is released". It is possible to choose one.

When "until stamina runs out" is set as the "auto progression stop condition setting" on the auto progression setting screen 100, the condition for stopping the auto progression function is set when the player runs out of stamina. As a result, it is possible to proceed with the battle game using the auto-progress function until the player's stamina is exhausted, thereby making it possible to eliminate the player's annoyance as much as possible.

However, if you lose the battle game, automatic progression will be forcibly stopped, regardless of whether your stamina is depleted or not. Also, if a support character is included in the party composition, if the in-game currency (mana) the player possesses is less than the in-game currency (mana) required to execute the next battle game, Also, automatic progression will be forcibly stopped regardless of whether stamina is depleted or not.

As described above, in this embodiment, in the battle game (for example, "1-15" battle game) on the last level belonging to a predetermined area (for example, the first area), the BOSS story screen 95 is displayed on the display 26. will be displayed. If a large number of battle games are progressed at once in the "main quest" using the auto progress function, there is a possibility that the display of the BOSS story screen 95 will end without the player noticing. Furthermore, it can be said that the difficulty level of a battle game in which a BOSS character appears is set relatively high compared to a battle game in which a BOSS character does not appear, since a strong enemy called a BOSS character appears. Therefore, in a battle game in which a BOSS character appears, some players want to carefully organize and strengthen the party of ally characters in advance, compared to a battle game in which a BOSS character does not appear.

Therefore, in the present embodiment, when "immediately before the BOSS appearance quest" is set as the "auto progress stop condition setting" on the auto progress setting screen 100, the condition for stopping the auto progress function is set as a battle in which the above-mentioned BOSS character appears. The case is set when the battle game immediately before the game is cleared. This makes it possible to eliminate the player's annoyance and to suppress the possibility that the player, who is looking forward to viewing the BOSS story screen 95, will miss the BOSS story screen 95. Furthermore, it is possible to fulfill the player's wish to carefully organize and strengthen the party of allied characters before executing a battle game in which the BOSS character appears.

Further, as described above, in this embodiment, a story may be released depending on the progress of the "main quest". Specifically, in the "main quest", if the player wins a predetermined battle game, the number of stories that the player can view increases.

Therefore, if a large number of battle games are progressed at once in the "main quest" using the auto progress function, the player will not be able to view the story as soon as the conditions for story release are met. Therefore, players who are looking forward to viewing the story may feel disappointed.

Also, if you use the auto progression function to progress through many battle games at once in the "main quest", many stories may be unlocked at once. In such a case, for example, a story that would normally be released sequentially will be released all at once, so there is a risk that the story's development will be spoiled from the story title.

Therefore, in the present embodiment, even if the auto-progress function is enabled, an auto-progress stop function is provided when a story is released, which stops the auto-progress function when a new story is released. If "when the story is released" is set as the "auto progress stop condition setting" on the auto progress setting screen 100, the auto progress stop function when the story is released is enabled, and the condition for stopping the auto progress function is to clear the battle game. Based on this, a case where the above-mentioned main story is newly released is set. This makes it possible to satisfy the expectations of players who are looking forward to viewing the story while eliminating the player's annoyance.

In addition, as shown in FIG. 10, on the auto progress setting screen 100, the player can select a check box marked "Stop" or a check box marked "Do not stop" as "Stop setting when 3-star clear is not achieved." It is possible to select one of the checkboxes.

If "Stop" is set as "Stop setting when 3-star clear is not achieved" on the auto progression setting screen 100, life points will be awarded when the battle game is cleared using the auto progression function. If there is one or more ally characters with 0, the automatic progression function is set to be stopped.

In addition, if "Do not stop" is set as "Stop setting when 3-star clear is not achieved" on the auto progression setting screen 100, when the battle game is cleared using the auto progression function, when the battle game is cleared, Even if there is one or more ally characters whose life points are 0, it is set that the automatic progression function does not stop.

Further, as shown in FIG. 10, on the auto progression setting screen 100, the player can select a checkbox marked "Skip" or a checkbox marked "Do not skip" as "BOSS story skip setting". It is possible to select one of them.

If "Skip" is set as the "BOSS story skip setting" on the auto progress setting screen 100, when the display timing of the BOSS story screen 95 is reached while using the auto progress function, the display of the BOSS story screen 95 will be stopped. Set to omit. However, if "Skip" is set as "BOSS Story Skip Setting", when the display timing of the BOSS Story screen 95 is reached while using the auto progression function, the BOSS Story screen will be displayed without any player operation. The effect images in 95 may be displayed sequentially.

In addition, if "Do not skip" is set as "BOSS story skip setting" on the auto progress setting screen 100, when the display timing of the BOSS story screen 95 is reached while using the auto progress function, the BOSS story screen 95 will be displayed. The effect images on the BOSS story screen 95 can be sequentially displayed in accordance with the player's operations without omitting the display.

In addition, as shown in FIG. 10, on the auto progression setting screen 100, the player can check the check box labeled "AUTO" indicating that an ally character will use a special move in an auto-activated state, and the battle that is in progress automatically. In the game, it is possible to select one of the check boxes labeled "Do not use" to indicate that the player will not allow his or her ally character to use a special move. By selecting one of these checkboxes, the player can change whether or not to set the auto-activation state of the special move in the battle game that is being automatically progressed.

Note that the above-mentioned check box for changing whether or not to set the auto-activation state of the special move in the battle game that is in progress automatically may be displayed on the main quest selection screen 74 (FIGS. 5B and 5C).

Furthermore, if "until stamina runs out" is selected as the "auto progress stop condition setting" on the auto progress setting screen 100, as shown in FIG. amount (here, 260) is displayed. Further, as the amount of stamina scheduled to be consumed, the same amount of stamina as the current amount of stamina (here, 260) is displayed. Note that if the stamina possessed by the player increases while using the auto-progress function, the amount of stamina actually consumed may be greater than the amount of stamina planned to be consumed. Furthermore, for example, the battle game may be able to be executed without consuming stamina until the player's level reaches a predetermined level. In this case, 0 may be displayed as the amount of stamina scheduled to be consumed.

Here, cases where the stamina possessed by the player increases while using the auto progression function include, for example, when stamina is recovered over time, or when the player level increases and stamina is granted. is applicable. That is, the automatic progression function may not be stopped based on an increase in the player level. However, the automatic progression function may be stopped based on an increase in the player level.

Furthermore, if "immediately before the BOSS appearance quest" is selected as the "auto progress stop condition setting" on the auto progress setting screen 100, as shown in FIG. The amount (here, 260) is displayed. Further, the amount of stamina required to clear the battle game immediately before the battle game in which the BOSS character appears, that is, the amount of stamina scheduled to be consumed (here, 80) is displayed. In other words, since the battle games in which the BOSS character appears are preset, the number of main quests executed from the battle game currently selected by the player to the battle game in which the BOSS character appears, and the number of main quests in one main quest. The amount of stamina to be consumed is derived from the amount of stamina required for execution.

In addition, when "when story is released" is selected as the "auto progression stop condition setting" on the auto progression setting screen 100, as shown in FIG. (here, 260) is displayed. Further, the amount of stamina required to clear the battle game until the story is released, that is, the amount of stamina scheduled to be consumed (here, 32) is displayed. In other words, since the battle game in which the story is released is set in advance, the number of main quests executed from the battle game selected by the player to the battle game in which the story is released, and the number of main quests in one main quest. The amount of stamina to be consumed is derived from the amount of stamina required for execution.

Further, a stamina recovery operation section 101 is displayed on the auto progress setting screen 180. When the stamina recovery operation section 101 is operated, the stamina recovery screen 110 is displayed superimposed on the auto progress setting screen 100 on the display 26.

FIG. 13A is a diagram illustrating an example of the stamina recovery screen 110. On the stamina recovery screen 110, the player can purchase a predetermined number of stamina and recover stamina by consuming in-game currency.

As shown in FIG. 13A, the stamina recovery screen 110 allows the player to arbitrarily set the number of times stamina is purchased. Then, on the stamina recovery screen 110, the number of stamina purchases set by the player is displayed.

Furthermore, the stamina recovery screen 110 displays the amount of stamina recovered based on the number of stamina purchases set by the player.

Furthermore, the stamina recovery screen 110 displays the amount of in-game currency that is scheduled to be consumed and the amount of in-game currency that the player possesses, based on the number of stamina purchases set by the player.

Furthermore, on the stamina recovery screen 110, a cancel operation section 111 marked with "Cancel" and an OK operation section 112 marked with "OK" are displayed.

When the cancel operation section 111 is operated, the purchase of stamina is canceled. Further, the display of the stamina recovery screen 110 ends, and the auto progress setting screen 100 is displayed on the display 26.

Further, when the OK operation unit 112 is operated, stamina is purchased based on the number of times of stamina purchase set by the player. Additionally, a stamina recovery confirmation screen 113 is displayed on the display 26.

FIG. 13B is a diagram illustrating an example of the stamina recovery confirmation screen 113. As shown in FIG. 13B, the stamina recovery confirmation screen 113 displays a message indicating that stamina has been recovered by consuming in-game currency. Furthermore, on the stamina recovery confirmation screen 113, changes in in-game currency held by the player and changes in stamina held by the player are notified.

Further, as shown in FIG. 13B, an OK operation section 114 labeled "OK" is displayed on the stamina recovery confirmation screen 113. When the OK operation unit 114 is operated, the display of the stamina recovery confirmation screen 113 on the display 26 ends, and the auto progress setting screen 100 is displayed on the display 26.

Returning to FIG. 10, the automatic progress setting screen 100 displays a cancel operation section 102 labeled "Cancel" and a battle start operation section 103 labeled "Battle Start".

When the cancel operation unit 102 is operated (tapped), the display of the auto-progress setting screen 100 on the display 26 ends, and the auto-progress party selection screen 77a (FIG. 9A) is displayed.

When the battle start operation section 103 is operated (tapped), if the current stamina is greater than or equal to the stamina scheduled to be consumed, the battle game is started and a battle game screen 80 (FIG. 17A) is displayed on the display 26. Is displayed.

On the other hand, when the current stamina is less than the stamina scheduled to be consumed and the battle start operation section 103 is operated (tapped), a stamina shortage confirmation screen 115 is displayed superimposed on the auto progress setting screen 100.

FIG. 13C is a diagram illustrating an example of the stamina shortage confirmation screen 115. As shown in FIG. 13C, the stamina shortage confirmation screen 115 displays a message stating "Stamina is insufficient. Do you want to recover?" to notify the player of the stamina shortage.

Further, as shown in FIG. 13C, the stamina shortage confirmation screen 115 displays a cancel operation section 116 labeled "Cancel" and an OK operation section 117 labeled "OK."

When the cancel operation unit 116 is operated, the display of the stamina shortage confirmation screen 115 on the display 26 ends, and the auto progress setting screen 100 is displayed on the display 26. That is, if the current stamina is less than the stamina scheduled to be consumed, the battle game cannot be started. However, it may be possible to advance the battle game automatically up to the battle game in the main quest that can be executed within the range of the current stamina possessed by the player.

On the other hand, when the OK operation unit 117 is operated, the stamina recovery screen 110 is displayed on the display 26, and as described above, it becomes possible to recover (purchase) stamina by consuming in-game currency. .

As described above, in this embodiment, support characters can be included in the party composition in the main quest battle game.

In FIG. 9A, when the party formation is completed and the support character is included in the party formation, when the next operation section 79a is operated (tapped), the auto progress setting screen 100a during support character formation (FIG. 14 ) is displayed on the display 26.

FIG. 14 is a first diagram illustrating an example of an automatic progression setting screen 100a when forming support characters in the main quest. FIG. 15 is a second diagram illustrating an example of the automatic progression setting screen 100a when forming support characters in the main quest. FIG. 16 is a third diagram illustrating an example of the auto progress setting screen 100a when forming support characters in the main quest.

On the auto progression setting screen 100a, the player can perform various settings similar to those on the auto progression setting screen 100 described above (FIGS. 10, 11, and 12). Furthermore, when "until stamina runs out" is selected as the "auto progress stop condition setting" on the auto progress setting screen 100a, as shown in FIG. The amount of local currency (mana) (here, 191297471) is displayed. Additionally, the amount of in-game currency (mana) scheduled to be consumed by using the support character (50,000 for each quest cleared) is displayed. Please note that the amount of in-game currency (mana) that is expected to be consumed by using a support character is the maximum amount of in-game currency (mana) that is expected to be consumed by using a support character (for each quest cleared). (up to 50,000) may be displayed.

Furthermore, if "immediately before the BOSS appearance quest" is selected as the "auto progress stop condition setting" on the auto progress setting screen 100a, as shown in FIG. The amount of currency (mana) (here, 191297471) and the amount of in-game currency (mana) to be consumed (here, 500000) are displayed.

Furthermore, if "when story is released" is selected as the "auto progression stop condition setting" on the auto progression setting screen 100a, as shown in FIG. (mana) amount (here, 191297471) and the amount of in-game currency (mana) scheduled to be consumed (here, 200000).

FIG. 17A is a first diagram illustrating an example of a battle game screen 80 during automatic progression in the main quest. FIG. 17B is a diagram illustrating an example of the first result screen 83 during automatic progression in the main quest. FIG. 17C is a first diagram illustrating an example of the second result screen 85 during automatic progression in the main quest.

During auto progress, on the battle game screen 80, first result screen 83, and second result screen 85, "Auto progress" and an auto progress display 118 indicating the hierarchy of the battle game are displayed at the upper right of the screen. be done.

Furthermore, during automatic progression, the player cannot manually activate a special move of an ally character. Furthermore, during automatic progression, even if the player operates (tap) the automatic selection operation section 82, it is not possible to switch between the automatic activation state and the manual activation state.

In addition, during automatic progression, if a predetermined time period (for example, 1 second) has elapsed since the first result screen 83 was displayed, the operation unit 84 is operated to proceed to the next page after the first result screen 83. (tap), and the display on the display 26 automatically transitions to the second result screen 85. At this time, the next operation section 84 marked with "Next" may be displayed in black, indicating that it is not an operation target.

In addition, during automatic progression, when a predetermined time period (for example, 1 second) has elapsed since the second result screen 85 was displayed, the operation unit 86 is operated to proceed from the second result screen 85. (tap), and the display of the second result screen 85 on the display 26 ends. At this time, the next operation section 86 marked with "Next" may be displayed in black, indicating that it is not an operation target.

In this way, during automatic progression, even if the player operates (tap) the next operation section 84 on the first result screen 83 and the next operation section 86 on the second result screen 85, the screen transition It is no longer possible to do so.

FIG. 18A is a second diagram illustrating an example of a battle game screen 80 during automatic progression in the main quest. FIG. 18B is a second diagram illustrating an example of the second result screen 85 during automatic progression in the main quest. During auto progression, if none of the auto progression stop conditions set on the auto progression setting screen 100 or the auto progression setting screen 100a is satisfied, when the display of the second result screen 85 ends, the next event quest will be displayed. A battle game (here, "1-5") is automatically started. Thereafter, the battle game screen 80, first result screen 83, and second result screen 85 are displayed in the same manner until the auto progress stop condition set on the auto progress setting screen 100 or the auto progress setting screen 100a is satisfied. , the main quest battle game is executed.

That is, the next quest is started on the display 26 without displaying the main quest screen 72, main quest selection screen 74, auto progression party selection screen 77a, auto progression setting screen 100, and auto progression setting screen 100a. That will happen.

However, on the display 26, the next quest is displayed via at least one of the main quest screen 72, main quest selection screen 74, auto progression party selection screen 77a, auto progression setting screen 100, and auto progression setting screen 100a. It may also be started. In this case as well, the screens on the display 26 may be changed by assuming that a predetermined operation section on each screen has been operated (tapped).

For example, as shown in FIG. 18B, it is assumed that the second result screen 85 for the battle game "3-15" of the event quest is displayed on the display 26. At this time, if the auto progress stop condition is satisfied based on insufficient stamina and the next quest is not started, an auto progress stop notification screen 120 (FIG. 19A) is displayed on the display 26.

FIG. 19A is a first diagram illustrating an example of the automatic progress stop notification screen 120 in the main quest. FIG. 19B is a second diagram illustrating an example of the automatic progress stop notification screen 120 in the main quest. FIG. 19C is a third diagram illustrating an example of the automatic progress stop notification screen 120 in the main quest. As shown in FIG. 19A, on the automatic progress stop notification screen 120, a message regarding the reason why automatic progress has stopped is displayed. In FIG. 19A, it is displayed that auto progression has stopped due to insufficient stamina.

Also, for example, if "immediately before the BOSS appearance quest" is set as the "auto progress stop condition setting" on the auto progress setting screen 100, and the battle game immediately before the battle game in which the BOSS character appears is cleared. Suppose that In this case, the automatic progress stop condition is satisfied based on the fact that the battle game immediately before the battle game in which the BOSS character appears has been cleared. In this case, a message is displayed to the effect that the automatic progression has stopped because the battle game immediately before the battle game in which the BOSS character appears has been cleared (not shown).

Further, for example, if "when story is released" is set as "auto progress stop condition setting" on the auto progress setting screen 100, and when the battle game is cleared using the auto progress function, the predetermined It is assumed that a predetermined release condition is satisfied. In this case, a message is displayed to the effect that the automatic progression has been stopped because the player has won the predetermined battle game and the number of stories that the player can view has increased (not shown).

For example, if "Stop" is set as "Stop setting when 3-star clear is not achieved" on the auto progression setting screen 100, and the battle game is cleared using the auto progression function, , it is assumed that there is one or more ally characters whose life points are 0 when the game is cleared. At this time, the automatic progress stop condition is satisfied based on the presence of one or more ally characters whose life points are 0 when the game is cleared. In this case, an auto progress stop notification screen 120 (FIG. 19B) is displayed on the display 26. As shown in FIG. 19B, the automatic progress stop notification screen 120 displays a message that the automatic progress has been stopped because a predetermined clear condition has not been met.

Further, if the battle game cannot be cleared using the auto progress function, that is, if the battle game is defeated, an auto progress stop notification screen 120 shown in FIG. 19C is displayed on the display 26. As shown in FIG. 19C, the automatic progress stop notification screen 120 displays that the automatic progress has been stopped due to a defeat in the battle game.

Further, on the automatic progress stop notification screen 120, the total number of stamina consumed by the player is displayed.

Further, an OK operation section 121 labeled "OK" is displayed on the auto progress stop notification screen 120. When the OK operation unit 121 is operated, the display of the auto progress stop notification screen 120 ends, and the main quest screen 72 is displayed on the display 26. Additionally, an auto progress reward list display 122 (FIG. 20A) is displayed superimposed on the main quest screen 72.

In this embodiment, when the auto progression function is used, even if the battle game on the last floor belonging to a predetermined area is cleared before the auto progression function stops, the area clear display 96 will not be displayed. Do not show. This avoids a situation where the area clear display 96 is displayed multiple times in a row when the auto progress function is used across multiple areas until the auto progress function stops. becomes possible.

FIG. 20A is a diagram illustrating an example of the automatic progress reward list display 122 in the main quest. FIG. 20B is a diagram illustrating an example of the story release display 124 in the main quest. FIG. 20C is a diagram illustrating an example of the friend application confirmation screen 127 in the main quest. As shown in FIG. 20A, the automatic progression reward list display 122 displays a list of items (rewards) acquired during automatic progression.

Further, a close operation section 123 labeled "Close" is displayed on the automatic progress reward list display 122. When the close operation unit 123 is operated (tapped), if there is a newly released story during automatic progression, a story release display 124 is displayed on the display 26 as shown in FIG. 20B. In other words, if "when story is released" is set as the "auto progress stop condition setting", the auto progress function is stopped based on the story release, and the newly released story is notified on the story release display 124. It will be done.

As shown in FIG. 20B, the story release display 124 displays a newly released story operation section 125 for viewing newly released stories during automatic progression, and a close operation section 126 labeled "Close". be done. When the newly released story operation section 125 is operated (tapped), the contents of each story can be viewed.

Note that a newly released story during automatic progression can also be viewed from the aforementioned main story screen (not shown) without operating the newly released story operation section 125.

During automatic progression, when a support character owned by a non-friend player is used, when the close operation unit 126 is operated, a friend application confirmation screen 127 is displayed on the display 26, as shown in FIG. 20C. As shown in FIG. 20C, the friend application confirmation screen 127 displays the player name of another player who is the owner of the support character used by the player during automatic progression. Then, on the friend request confirmation screen 127, a message for confirming whether or not to make a friend request to the other player is displayed.

As shown in FIG. 20C, the friend request confirmation screen 127 displays a cancel operation section 128 labeled "Cancel." Further, on the friend request confirmation screen 127, an OK operation section 129 labeled "OK" is displayed. When the cancel operation unit 128 is operated, the display of the friend request confirmation screen 127 ends without making a friend request. When the OK operation unit 129 is operated, a friend request is made, and the display of the friend request confirmation screen 127 ends.

FIG. 21A is a first diagram illustrating an example of the automatic progress stop display 130 in the main quest. FIG. 21B is a second diagram illustrating an example of the automatic progress stop display 130 in the main quest. As described above, during automatic progression, the player manually activates a special move of an ally character on the battle game screen 80, and the automatic activation state based on the player's operation (tap) on the automatic selection operation section 82. It is not possible to switch between the manual activation state and the manual activation state. During automatic progress, when the ally character display area 81 of the battle game screen 80 is operated (tapped) or the automatic selection operation section 82 is operated (tapped), the battle game is temporarily stopped. When the battle game is stopped, an auto progress stop display 130 shown in FIG. 21A is superimposed on the battle game screen 80.

Note that the battle game may be temporarily stopped when a predetermined location on each screen is operated (tapped) while using the auto-progress function. For example, when an unillustrated menu operation unit for displaying an unillustrated menu screen is operated (tapped), the battle game may be temporarily stopped. Furthermore, the battle game may be temporarily stopped when a predetermined peripheral area of each operating section is operated (tapped), rather than each operating section itself.

Similarly, during automatic progression, if an operation (tap) is performed on the next operation section 84 of the first result screen 83 or the next operation section 86 of the second result screen 85, the battle game will temporarily stop. However, the automatic progress stop display 130 shown in FIG. 21B is displayed so as to be superimposed on the first result screen 83 and second result screen 85 that are being displayed.

As shown in FIGS. 21A and 21B, the auto progress stop display 130 displays confirmation of stopping auto progress and the number of stamina that has already been consumed. Further, the auto progress stop display 130 may further display the number and types of battle games that have been cleared so far. Further, in the automatic progress stop display 130, a cancel operation section 131 labeled "Cancel" and an OK operation section 132 labeled "OK" are displayed.

When the cancel operation unit 131 is operated (tapped), the automatic progress stop display 130 is hidden from the display 26. In addition, the battle game that has been temporarily stopped due to the display of the automatic progress stop display 130 will be restarted by automatic progress.

Further, when the OK operation unit 132 is operated (tapped), the automatic progress stop display 130 is hidden from the display 26. Additionally, the battle game will restart with automatic progression stopped. Furthermore, the automatic progress display 118 that was displayed on the battle game screen 80, the first result screen 83, or the second result screen 85 is also hidden.

Furthermore, when the automatic progression is stopped, automatic screen transitions on the first result screen 83 and the second result screen 85 are also not executed. When the automatic progression is stopped, when the player operates (tap) the next operation section 84 of the first result screen 83, a second result screen 85 is displayed on the display 26. Then, when the player operates (tap) the operation section 86 next to the second result screen 85, the display of the second result screen 85 on the display 26 ends.

Since the automatic progression is stopped, the screen transitions to the main quest screen 72 without starting the next battle game in the event quest. At this time, the items (rewards) acquired by the player up to the point in time when the automatic progression was stopped are displayed as a list in the automatic progression reward list display 122 (FIG. 20A). Furthermore, when the close operation section 123 of the auto progression reward list display 122 is operated (tapped), a story release display 124 (FIG. 20B) that allows viewing of the story that was newly released at the time the auto progression was stopped. is displayed on the display 26.

FIG. 22 is a diagram illustrating an example of the setting screen 140. When a predetermined operation unit is operated on a menu screen (not shown), a setting screen 140 is displayed on the display 26. As described above, in this embodiment, in the battle game (for example, "1-15" battle game) of the last level belonging to a predetermined area (for example, the first area) in the main quest, as an enemy character, A BOSS character set for each area will appear.

Then, after the battle game (for example, "1-15" battle game) of the last level belonging to a predetermined area (for example, the first area) has started, and before the battle with the BOSS character starts. At the front, a BOSS story screen 95 is displayed on the display 26. In this embodiment, after once clearing a battle game in which a BOSS character appears, if you challenge a battle game in which the BOSS character appears again, you can set whether or not to display the BOSS story screen 95. . This allows a player who has missed the BOSS story screen 95 to view the BOSS story screen 95 again using the auto-progress function, for example.

Next, event quests will be explained. Since the basic parts of the battle game in the event quest are the same as the main quest, duplicate explanations will be omitted, and only the parts that are different from the main quest will be explained.

FIG. 23A is a diagram illustrating an example of the event quest screen 172. FIG. 23B is a first diagram illustrating an example of the event quest selection screen 174. FIG. 23C is a second diagram illustrating an example of the event quest selection screen 174.

The event quest screen 172 displays a menu bar 41, a header display area 42, and an event quest operation section 173 for selecting a plurality of battle games (layers) belonging to the event quest.

In the event quest operation section 173, clear information for each battle game is also displayed, similar to the above-mentioned main quest.

Furthermore, in the event quest, like the main quest described above, the release condition is set to clear the previous battle game. For example, in the example of FIG. 23A, since the battle game "1-1" has not been cleared, the battle games after "1-2" are unreleased.

On the event quest screen 172, for example, when the event quest operation section 173 of the “1-1” battle game is operated (tapped), an event quest selection screen 174 shown in FIG. 23B is displayed on the display 26. Similar to the main quest selection screen 74 described above, the event quest selection screen 174 displays enemy characters appearing in the battle game and items (rewards) that can be obtained in the battle game.

In this embodiment, the event quest includes 15 battle games from "1-1" to "1-15". As described above, the player can play the event quest only during a preset period (for example, 10 days). Therefore, the difficulty level of the battle game is set to be relatively low so that not only advanced players but also novice players can enjoy it. Beginner players have a lower level of development of their ally characters than advanced players, so they have to experience victory or defeat in each battle game of the event quest, and progress through the event quest through joys and sorrows. I have to go.

On the other hand, advanced players may feel tired because they are required to play many battle games that are low in difficulty and have an extremely low risk of defeat. Therefore, in the present embodiment, an automatic progress function is provided in the event quest as well, which allows battle games to be executed sequentially in an automated manner to reduce the annoyance of the player.

As shown in FIG. 23B, the event quest selection screen 174 is provided with a checkbox for enabling the automatic progression function, and by operating (tapping) this checkbox, the automatic progression function can be enabled and It is possible to disable it.

That is, as shown in FIG. 23B, when the checkbox is checked, the auto progress function is enabled, and as shown in FIG. 23C, when the checkbox is not checked, the auto progress function is enabled. Progress functionality is disabled.

In this embodiment, a case has been described in which enabling and disabling of the automatic progress function can be switched by a check box, but the present invention is not limited to this. For example, by displaying both an operation section for enabling the auto-progression function and an operation section for disabling the auto-progression function on the display 26, and having the player operate (tap) either of these operation sections. , the automatic progress function may be configured to be switchable between valid and invalid. Furthermore, the checkboxes and operation units that enable and disable the automatic progress function described above may be displayed on a screen other than the event quest selection screen 174. For example, on the event quest screen 172, the auto progression party selection screen 177 (described later), the auto progression setting screen 180 (described later), the auto progression setting screen 190 when insufficient stamina (described later), etc., the auto progression function described above can be enabled or disabled. It is also possible to display check boxes and operation sections.

Furthermore, the event quest selection screen 174 displays stamina after consuming stamina when challenging a battle game by consuming stamina. Specifically, as shown in FIGS. 23B and 23C, on the event quest selection screen 174, when the "1-1" battle game is executed, stamina is consumed from the current stamina 260 to 252. It will be displayed that it is scheduled to change to. However, when the auto progression function is enabled, 15 battle games from "1-1" to "1-15" are scheduled to be executed sequentially, so on the event quest selection screen 174 of FIG. 23B, It may be displayed that the current stamina of 260 is scheduled to change to 140 as stamina is consumed. In other words, the total amount of consideration required for a plurality of predetermined games (battle games) that are scheduled to be sequentially executed in auto mode (auto progress function) may be displayed.

The event quest selection screen 174 also includes a challenge operation section 75 marked "Challenge" for challenging the battle game selected by the player, and a challenge operation section 75 for canceling the process corresponding to the currently displayed screen. A cancel operation section 76 labeled "Cancel" is displayed.

When the cancel operation unit 76 is operated (tapped), a main quest screen 72 shown in FIG. 23A is displayed on the display 26, and the challenge to the selected "1-1" battle game is canceled.

Furthermore, when the auto progression function is disabled, that is, when the challenge operation section 75 in FIG. 23C is operated (tapped), a party selection screen 77 (FIG. 5C) similar to the above-mentioned main quest is displayed on the display 26. Ru. On the other hand, when the automatic progression function is enabled, that is, when the challenge operation section 75 in FIG. 23B is operated (tapped), an automatic progression party selection screen 177 (FIG. 24A) is displayed on the display 26.

FIG. 24A is a diagram illustrating an example of the party selection screen 177 for automatic progression. As shown in FIG. 24A, the automatic progression party selection screen 177 displays a selected ally character display area 78 and a cancel operation section 76, similar to the party selection screen 77 described above.

Furthermore, a next operation section 179 labeled "Next" is displayed on the party selection screen 177 for automatic progression. Furthermore, a warning display stating "*Auto progress setting in progress" is displayed at the bottom of the next operation section 179. As a result, the player is informed that the auto progression function is scheduled to be used in the event quest battle game.

When the party formation is completed and the next operation section 179 is operated (tapped), an automatic progress setting screen 180 (FIG. 24B) or an automatic progress setting screen 190 when stamina is insufficient (FIG. 25A) is displayed on the display 26.

FIG. 24B is a first diagram illustrating an example of the automatic progress setting screen 180 in the event quest. FIG. 24C is a second diagram illustrating an example of the automatic progress setting screen 180 in the event quest. As shown in FIG. 24B, the auto progress setting screen 180 shows that the current stamina is 260, and that when the auto progress function is enabled, 15 stamina numbers from "1-1" to "1-15" are displayed. Since the battle games are scheduled to be executed sequentially, it is displayed that a maximum of 120 stamina (total consumed stamina) will be consumed.

Further, as described above, in this embodiment, a story may be released depending on the progress of the "event quest". Specifically, in the "event quest", if the player wins a predetermined battle game, the number of stories that the player can view increases.

Therefore, if you use the auto progression function to progress through all the battle games from "1-1" to "1-15" in "Event Quest" at once, when the conditions for story release are met, Players cannot view the story quickly. Therefore, players who are looking forward to viewing the story may feel disappointed.

Also, if you use the auto progression function to progress through all the battle games from "1-1" to "1-15" at once in "Event Quest", the stage when the battle game "1-15" has finished. Sometimes, a large number of stories are released at once. In such a case, for example, a story that would normally be released sequentially will be released all at once, so there is a risk that the story's development will be spoiled from the story title.

Therefore, in the present embodiment, even if the auto-progress function is enabled, an auto-progress stop function is provided when a story is released, which stops the auto-progress function when a new story is released.

As shown in FIG. 24B, the auto progress setting screen 180 is provided with a check box for enabling the auto progress stop function when the story is released. By operating (tapping) a checkbox, the player can enable or disable the auto-progress-stopping function upon story release.

That is, as shown in FIG. 24B, when a check mark is displayed in the checkbox labeled "Stop", the automatic progress stop function upon story release is enabled. Further, as shown in FIG. 24C, if a check is displayed in the checkbox labeled "Do not stop", the automatic progress stop function upon release of the story is disabled.

In this embodiment, a case has been described in which an auto-progress stop function is provided when a story is released, which stops the auto-progress function when a new story is released; however, the present invention is not limited to this. For example, the automatic progression may be stopped when the player level increases, when predetermined content other than the story is released, or when a predetermined time (for example, 30 minutes) has elapsed. A predetermined check box or a predetermined operation unit may be displayed so that the player can set whether or not to stop when these conditions are met. Note that "when predetermined content other than the story is released" may be, for example, a case where the number of content that can be purchased with in-game currency increases.

Further, as shown in FIG. 24B, the auto progress setting screen 180 includes a check box labeled "AUTO" indicating that an ally character will use a special move in an auto-activated state in a battle game that is progressing automatically. Also, in the battle game that is being automatically progressed, a check box labeled "Do not use" indicating that the ally character will not be allowed to use the special move is displayed. By selecting one of these checkboxes, the player can change whether or not to set the auto-activation state of the special move in the battle game that is being automatically progressed.

Note that the above-mentioned checkbox for changing whether or not to set the auto-activation state of the special move in the battle game that is in progress automatically may be displayed on the event quest selection screen 174 (FIGS. 23B and 23C).

Further, on the auto progress setting screen 180, a cancel operation section 181 labeled "Cancel" and a battle start operation section 182 labeled "Battle start" are displayed.

When the cancel operation unit 181 is operated (tapped), an automatic proceeding party selection screen 177 is displayed on the display 26.

When the battle start operation section 182 is operated (tapped), a battle game is started, and a battle game screen 80 (FIG. 26A) is displayed on the display 26.

FIG. 25A is a diagram illustrating an example of an automatic progression setting screen 190 when stamina is insufficient. FIG. 25B is a diagram illustrating an example of the stamina recovery dialog 200. FIG. 25C is a diagram illustrating an example of the stamina recovery result screen 210. When the party formation is completed and the next operation section 179 is operated (tapped), if the current stamina is less than the total consumed stamina, the automatic progress setting screen 190 when insufficient stamina shown in FIG. 25A is displayed. 26.

As shown in FIG. 25A, on the auto progress setting screen 190 when stamina is insufficient, the current stamina (here, 60) and the total consumed stamina (here, 120) is displayed. Further, on the auto progress setting screen 190 when running out of stamina, it is displayed that the player does not have enough stamina to clear 15 battle games from "1-1" to "1-15".

Further, in the automatic progress setting screen 190 when stamina is insufficient, a check box is provided for enabling the automatic progress stopping function when the story is released, similar to the above-described automatic progress setting screen 180 (FIG. 24B).

In addition, in the automatic progress setting screen 190 when stamina is insufficient, similarly to the above-described automatic progress setting screen 180 (FIG. 24B), in a battle game that is progressing automatically, whether or not an ally character uses a special move in an auto-activated state is displayed. A check box is provided to set the .

In addition, the automatic progress setting screen 190 when running out of stamina includes a cancel operation section 191 marked with "Cancel", a next operation section 192 marked with "Next without recovery", and a next operation section 192 marked with "Recover". A recovery operation section 193 is displayed.

When the cancel operation unit 191 is operated (tapped), an automatic proceeding party selection screen 177 is displayed on the display 26.

Further, when the next operation unit 192 is operated (tapped), a battle game is started, and a battle game screen 80 (FIG. 26A) is displayed on the display 26.

Further, when the recovery operation section 193 is operated (tapped), a stamina recovery dialog 200 shown in FIG. 25B is displayed on the display 26. As shown in FIG. 25B, the stamina recovery dialog 200 includes information such as the number of in-game currencies consumed to recover stamina, the number of in-game currencies the player has, the amount of stamina recovered, and the amount of stamina recovered. You will be asked to confirm that you wish to do so.

Further, in the stamina recovery dialog 200, a cancel operation section 201 marked with "Cancel" and an OK operation section 202 marked with "OK" are displayed.

When the cancel operation unit 201 is operated (tapped), the recovery of stamina is interrupted, and an automatic progress setting screen 190 when stamina is insufficient is displayed on the display 26.

Furthermore, when the OK operation unit 202 is operated (tapped), the in-game currency held by the player is consumed to recover stamina. Further, on the display 26, a stamina recovery result screen 210 shown in FIG. 25C is displayed.

As shown in FIG. 25C, the stamina recovery result screen 210 includes the number of in-game currencies consumed to recover stamina, changes in the number of in-game currencies held by the player, and information about the player before and after recovery. The amount of stamina you have and notifications that you have recovered your stamina will be displayed.

Further, on the stamina recovery result screen 210, an OK operation section 211 labeled "OK" is displayed. When the OK operation unit 211 is operated, an auto progress setting screen 180 is displayed on the display 26.

FIG. 26A is a first diagram illustrating an example of a battle game screen 80 during automatic progress in an event quest. FIG. 26B is a diagram illustrating an example of the first result screen 83 during automatic progress in the event quest. FIG. 26C is a first diagram illustrating an example of the second result screen 85 during automatic progress in the event quest. During the battle game, as shown in FIG. 26A, a battle game screen 80 is displayed as in the main quest described above.

Further, similarly to the main quest described above, when the end conditions of the battle game are met, the first result screen 83 and the second result screen 85 are displayed on the display 26.

However, during auto-progress, on the battle game screen 80, first result screen 83, and second result screen 85, "Auto-progress" is displayed in the upper right corner of the screen, and an auto-progress display 215 indicating the level of the battle game is displayed. is displayed.

Furthermore, during automatic progression, the player cannot manually activate a special move of an ally character. Furthermore, during automatic progression, even if the player operates (tap) the automatic selection operation section 82, it is not possible to switch between the automatic activation state and the manual activation state.

In addition, during automatic progression, if a predetermined time period (for example, 1 second) has elapsed since the first result screen 83 was displayed, the operation unit 84 is operated to proceed to the next page after the first result screen 83. (tap), and the display on the display 26 automatically transitions to the second result screen 85. At this time, the next operation section 84 marked with "Next" may be displayed in black, indicating that it is not an operation target.

In addition, during automatic progression, when a predetermined time period (for example, 1 second) has elapsed since the second result screen 85 was displayed, the operation unit 86 is operated to proceed from the second result screen 85. (tap), and the display of the second result screen 85 on the display 26 ends. At this time, the next operation section 86 marked with "Next" may be displayed in black, indicating that it is not an operation target.

Therefore, during automatic progression, even if the player operates (tap) the next operation section 84 on the first result screen 83 and the next operation section 86 on the second result screen 85, the screen transition is performed. It is now impossible to do so.

FIG. 27A is a second diagram illustrating an example of a battle game screen 80 during automatic progress in an event quest. FIG. 27B is a second diagram illustrating an example of the second result screen 85 during automatic progress in the event quest. FIG. 28A is a first diagram illustrating an example of an automatic progression reward list display 220 in an event quest. FIG. 28B is a first diagram illustrating an example of the story release display 230 in the event quest. When the second result screen 85 finishes displaying during auto-progress and the auto-progress stop function upon story release is set to disabled, the next battle game (here, "1-2") in the event quest is displayed. ) will be started automatically. Thereafter, the battle game screen 80, first result screen 83, and second result screen 85 are displayed in the same manner, and the event quest battle game is executed up to "1-15".

That is, on the display 26, the next quest is displayed without displaying the event quest screen 172, the event quest selection screen 174, the auto progression party selection screen 177, the auto progression setting screen 180, and the auto progression setting screen 190 when insufficient stamina. It will be started.

However, on the display 26, through at least one of the event quest screen 172, event quest selection screen 174, auto progression party selection screen 177, auto progression setting screen 180, and auto progression setting screen 190 when insufficient stamina, the next The quest may be started. In this case as well, the screens on the display 26 may be changed by assuming that a predetermined operation section on each screen has been operated (tapped).

Finally, as shown in FIG. 27B, a second result screen 85 for the battle game "1-15" of the event quest is displayed on the display 26. In addition, on the second result screen 85, a pop-up is displayed to notify that the auto progression has ended, and the number and type of battle games cleared and the total amount of stamina consumed by the player are displayed in the pop-up display. It may also be displayed.

When the display of the second result screen 85 is finished, the event quest screen 172 is displayed on the display 26, as shown in FIG. 28A. Additionally, an auto progression reward list display 220 is displayed superimposed on the event quest screen 172.

As shown in FIG. 28A, the automatic progression reward list display 220 displays a list of items (rewards) acquired during automatic progression.

Further, a close operation section 221 labeled "Close" is displayed on the automatic progress reward list display 220. When the close operation unit 221 is operated (tapped), a story release display 230 is displayed on the display 26, as shown in FIG. 28B.

As shown in FIG. 28B, the story release display 230 displays a newly released story operation section 231 for viewing newly released stories during automatic progression, and a close operation section 232 labeled "Close". be done. When the new release story operation section 231 is operated (tapped), the contents of each story can be viewed.

Note that in order to view a newly released story during auto-progress, it can also be viewed from the above-mentioned extra story screen (not shown) without operating the newly released story operation section 231.

FIG. 29A is a diagram illustrating an example of an automatic progression reward list display 220 in an event quest. FIG. 29B is a diagram illustrating an example of the story release display 230 in the event quest. It is assumed that a predetermined release condition is satisfied during auto-progress and when the auto-progress stop function upon story release is enabled. Here, the release conditions are set such that the player wins a predetermined battle game and the number of stories that the player can view increases. In this case, when the display of the second result screen 85 ends, the next battle game in the event quest is not started and the automatic progression is stopped.

At this time, as shown in FIG. 29A, the items (rewards) that the player has acquired up to the time when the automatic progression is stopped are displayed as a list in the automatic progression reward list display 220. Then, when the close operation unit 221 is operated (tapped), a story release display 230 is displayed on the display 26 that allows viewing of a newly released story at the time when automatic progress is stopped.

FIG. 30A is a first diagram illustrating an example of the automatic progress stop display 240 in the event quest. FIG. 30B is a second diagram illustrating an example of the automatic progress stop display 240 in the event quest. As described above, during automatic progression, the player manually activates a special move of an ally character on the battle game screen 80, and the automatic activation state is activated based on the player's operation (tap) on the automatic selection operation section 82. It is not possible to switch between the manual activation state and the manual activation state. During automatic progress, when the ally character display area 81 of the battle game screen 80 is operated (tapped) or the automatic selection operation section 82 is operated (tapped), the battle game is temporarily stopped. When the battle game is stopped, an auto progress stop display 240 shown in FIG. 30A is superimposed on the battle game screen 80.

Note that the auto progress function may be stopped by operating (tapping) a predetermined location on each screen while using the auto progress function. For example, when an unillustrated menu operation unit for displaying an unillustrated menu screen is operated (tapped), the battle game may be temporarily stopped. Furthermore, the battle game may be temporarily stopped when a predetermined peripheral area of each operating section is operated (tapped), rather than each operating section itself.

Similarly, during automatic progression, if an operation (tap) is performed on the next operation section 84 of the first result screen 83 or the next operation section 86 of the second result screen 85, the battle game will temporarily stop. However, the automatic progress stop display 240 shown in FIG. 30B is displayed so as to be superimposed on the first result screen 83 and second result screen 85 that are currently being displayed.

As shown in FIGS. 30A and 30B, the auto progress stop display 240 displays confirmation of stopping auto progress and the number of stamina that has already been consumed. Further, the auto progress stop display 240 may further display the number and types of battle games that have been cleared so far. Further, in the automatic progress stop display 240, a cancel operation section 241 marked with "Cancel" and an OK operation section 242 marked with "OK" are displayed.

When the cancel operation unit 241 is operated (tapped), the automatic progress stop display 240 is hidden from the display 26. In addition, the battle game that has been temporarily stopped due to the display of the automatic progress stop display 240 will be restarted by automatic progress.

Further, when the OK operation section 242 is operated (tapped), the automatic progress stop display 240 is hidden from the display 26. Additionally, the battle game will restart with automatic progression stopped. Furthermore, the automatic progress display 215 that was displayed on the battle game screen 80, the first result screen 83, or the second result screen 85 is also hidden.

Furthermore, when the automatic progression is stopped, automatic screen transitions on the first result screen 83 and the second result screen 85 are also not executed. When the automatic progression is stopped, when the player operates (tap) the next operation section 84 of the first result screen 83, a second result screen 85 is displayed on the display 26. Then, when the player operates (tap) the operation section 86 next to the second result screen 85, the display of the second result screen 85 on the display 26 ends.

Since the automatic progression is stopped, the screen transitions to the event quest screen 172 without starting the next battle game in the event quest. At this time, the items (rewards) acquired by the player up to the point in time when the automatic progression was stopped are displayed as a list in the automatic progression reward list display 220 (FIG. 29A). Furthermore, when the close operation section 221 of the auto progression reward list display 220 is operated (tapped), a story release display 230 (FIG. 29B) allows viewing of the story that was newly released at the time the auto progression was stopped. is displayed on the display 26.

Next, the functional configuration of the player terminal 1 for executing the main quest battle game described above using the automatic progression function will be described.

(Control processing in player terminal 1)
FIG. 31 is a diagram illustrating the configuration of the memory 12 in the player terminal 1 and its function as a computer. The program storage area 12a stores a main quest selection reception program 500, a party formation reception program 502, a setting management program 504, a battle game start operation reception program 506, and a battle management processing program 508. Note that the above program stored in the program storage area 12a is just an example, and the program storage area 12a is provided with many other programs.

The data storage area 12b is provided with an information storage section 550 that stores various information for battle games. Note that the above-mentioned storage section provided in the data storage area 12b is an example, and the data storage area 12b is provided with many other storage sections.

The CPU 10 operates each program stored in the program storage area 12a and updates data in each storage section of the data storage area 12b. Then, the CPU 10 causes the player terminal 1 (computer) to function as the terminal-side control unit 1A by operating each program stored in the program storage area 12a. The terminal side control section 1A includes a main quest selection reception section 500a, a party formation reception section 502a, a setting management section 504a, a battle game start operation reception section 506a, and a battle management processing section 508a.

Specifically, the CPU 10 operates the main quest selection reception program 500, the party formation reception program 502, the setting management program 504, the battle game start operation reception program 506, and the battle management processing program 508, and causes the computer to operate the main quest selection reception program 502. 500a, a party formation reception section 502a, a setting management section 504a, a battle game start operation reception section 506a, and a battle management processing section 508a.

FIG. 32 is a flowchart illustrating an example of management processing in the player terminal 1. The main quest selection reception unit 500a displays the main quest screen 72 on the display 26, and performs a main quest selection reception process for accepting the operation of the main quest operation unit 73 on the main quest screen 72 (P1-1).

In the main quest selection reception process (P1-1), when the main quest operation unit 73 is operated, the main quest selection reception unit 500a displays the main quest selection screen 74 on the display 26.

In the main quest selection reception process (P1-1), the main quest selection reception unit 500a sets the main quest selection screen 74 to a state where the auto progress function is enabled, that is, the challenge operation unit 75 in FIG. When tapped), an automatic proceeding party selection screen 77a (FIG. 9A) is displayed on the display 26.

Further, in the main quest selection reception process (P1-1), the party formation reception unit 502a accepts the formation of a party based on the player's operation on the automatic progression party selection screen 77a.

In addition, in the main quest selection reception process (P1-1), the party formation reception unit 502a selects the support character to be added to the party formation when the next operation unit 79a is operated (tapped) on the automatic progression party selection screen 77a. If not included, an auto progress setting screen 100 (FIG. 10) is displayed on the display 26.

In addition, in the main quest selection reception process (P1-1), the party formation reception unit 502a selects the support character to be added to the party formation when the next operation unit 79a is operated (tapped) on the automatic progression party selection screen 77a. If it is included, an auto progress setting screen 100a (FIG. 14) is displayed on the display 26.

The settings management unit 504a executes a settings management process that accepts various settings on the auto progress setting screen 100 or the auto progress setting screen 100a (P1-3). In the settings management process (P1-3), specifically, when "until stamina runs out" is set as the "auto progress stop condition setting", the settings management unit 504a sets the condition (until stamina is insufficient) to stop the auto progress function ( The case where the player lacks stamina is set as the stop information).

In the setting management process (P1-3), the setting management unit 504a sets the condition (stop information) for stopping the auto progress function when "when story is released" is set as the "auto progress stop condition setting". Based on the clearing of the battle game, a case is set in which the above-mentioned main story is newly released.

In the setting management process (P1-3), the setting management unit 504a sets the condition (stop information) for stopping the auto progress function when "immediately before the BOSS appearance quest" is set as the "auto progress stop condition setting". , a case is set in which the battle game immediately before the battle game in which the above-mentioned BOSS character appears has been cleared.

In addition, in the setting management process (P1-3), the setting management unit 504a determines the conditions for stopping the auto progress function (stop information ), a case is set in which when the battle game is cleared using the auto-progress function, there is one or more ally characters whose life points are 0 at the time of clearing.

In addition, in the setting management process (P1-3), the setting management unit 504a controls the auto progress function if "do not stop" is set as "stop setting when 3-star clear is not achieved" on the auto progress setting screen 100. When the battle game is cleared using this function, it is set so that the auto progress function does not stop even if there is one or more ally characters whose life points are 0 at the time of clearing.

In addition, in the setting management process (P1-3), the setting management unit 504a displays the BOSS story screen 95 while using the auto progress function if "Skip" is set as the "BOSS story skip setting". When the timing is reached, the display of the BOSS story screen 95 is set to be omitted.

In addition, in the setting management process (P1-3), the setting management unit 504a displays the BOSS story screen 95 while using the auto progress function if "Do not skip" is set as the "BOSS story skip setting". When the timing is reached, the display of the BOSS story screen 95 is not omitted, and the effect images on the BOSS story screen 95 are sequentially displayed in accordance with the player's operation.

Further, in the setting management process (P1-3), the setting management unit 504a allows the player to clear the battle game in which the BOSS character appears again on the setting screen 140, and then restart the battle game in which the BOSS character appears. If a challenge is taken, the setting of whether or not to display the BOSS story screen 95 is accepted.

Specifically, if "ON" is set as the "BOSS story redisplay setting", the setting management unit 504a will restart the battle game in which the BOSS character appears after clearing the battle game in which the BOSS character appears. When the game starts, it is set to display the BOSS story screen 95.

In addition, in the setting management process (P1-3), if "OFF" is set as the "BOSS story redisplay setting", the setting management unit 504a, after once clearing the battle game in which the BOSS character appears, When the battle game in which the BOSS character appears starts, it is set not to display the BOSS story screen 95.

Further, the battle game start operation reception unit 506a executes a process of accepting a player's operation for starting a main quest battle game using the automatic progression function. Specifically, when the battle start operation unit 103 is operated (tapped), the battle game start operation accepting unit 506a determines whether or not the start condition for automatic progression is satisfied (P1-5). Note that the battle game start operation reception unit 506a determines that the start condition is satisfied when the current stamina is greater than or equal to the stamina scheduled to be consumed by automatic progression.

As a result, if it is determined that the start condition is met (YES at P1-5), the battle management processing unit 508a executes battle management processing (P1-7). Specifically, the battle management processing unit 508a performs damage calculation processing when a friendly character attacks an enemy character and when an enemy character attacks a friendly character. The battle management processing unit 508a also executes animation drawing processing for drawing various actions of each ally character and each enemy character in the battle game.

Furthermore, the battle management processing unit 508a determines whether the display timing of the BOSS story screen 95 has arrived (P1-9). As a result, when the display timing of the BOSS story screen 95 has been reached, the battle management processing unit 508a determines whether "Do not skip" is set as the "BOSS story skip setting" in step P1-3 above. (P1-11). Note that in the above embodiment, after the start of the battle game (for example, the "1-15" battle game) on the last level belonging to the predetermined area (for example, the first area), the battle against the BOSS character is started. The case is shown in which the BOSS story screen 95 is displayed on the display 26 before the BOSS story screen 95 starts. However, the timing at which the BOSS story screen 95 is displayed on the display 26 is not limited to this. For example, the BOSS story screen 95 may be displayed multiple times on the display 26 in one battle game (for example, a “1-15” battle game). In this case, the BOSS story screen 95 is displayed after the battle game starts but before the battle with the BOSS character starts, and before the end of the battle game and after the battle with the BOSS character ends. It can be displayed on the display 26. In any case, at the timing when the BOSS story screen 95 is displayed on the display 26, or at the timing immediately before the BOSS story screen 95 is displayed on the display 26, the battle management processing unit 508a determines the display timing of the BOSS story screen 95. It may be determined that the value has been reached.

As a result, if "Do not skip" is set as "BOSS story skip setting" (YES on P1-11), the battle management processing unit 508a does not omit the display of the BOSS story screen 95, and the A BOSS story display process is executed in which effect images on the BOSS story screen 95 are sequentially displayed in accordance with the operation (P1-13). Furthermore, the battle management processing unit 508a moves the process to step P1-17, which will be described later.

Furthermore, if “Skip” is set as “BOSS story skip setting” (NO in P1-11), the battle management processing unit 508a executes a BOSS story skip process that omits the display of the BOSS story screen 95. (P1-15).

In addition, the battle management processing unit 508a determines whether the currently running battle game has already been cleared before, whether the auto progress function is used in the currently running battle game, and whether the "BOSS story skip setting" The BOSS story display process (P1-13 ) or BOSS story skip processing (P1-15) may be determined.

Specifically, for example, the currently running battle game has not been cleared before, and the auto progress function is being used in the currently running battle game, and the "BOSS story skip setting" If "Skip" is set, it can be determined that the BOSS story skip process (P1-15) is executed.

In addition, the currently running battle game has not been cleared before, the auto progression function is used in the currently running battle game, and "Do not skip" is set as "BOSS story skip setting". If set, it can be determined that the BOSS story display process (P1-13) is to be executed.

The battle management processing unit 508a also determines whether the player has performed an operation to stop the automatic progression function (P1-17). As a result, if the player performs an operation to stop the auto progression function (YES in P1-17), the battle management processing unit 508a executes auto progression stop processing to stop the auto progression function (P1-19). .

Furthermore, if the player has not performed an operation to stop the automatic progression function (NO in P1-17), the battle management processing unit 508a moves the process to step P1-21, which will be described later.

Furthermore, the battle management processing unit 508a determines whether the conditions for ending the battle game are satisfied (P1-21). Specifically, the battle management processing unit 508a starts the battle game when any of the following conditions is met: all friendly characters are wiped out, all enemy characters are wiped out, or the battle time of the battle game has elapsed. It is determined that the termination condition of is satisfied. Note that when the battle game termination condition is satisfied, the battle management processing unit 508a may transmit predetermined information including whether or not the battle game has been executed by automatic progression to the server 1000.

As a result, if the battle game termination condition is satisfied (P1-21: YES), the battle management processing unit 508a terminates the battle game and displays the first result screen 83 and the second result screen 85 (P1-21: YES). -23).

Further, if the battle game termination condition is not satisfied (NO in P1-21), the battle management processing unit 508a repeats the process from step P1-7.

Furthermore, the battle management processing unit 508a determines whether a condition for stopping the automatic progress function is satisfied (P1-25). Specifically, the battle management processing unit 508a refers to the stop conditions (stop information) for the auto progress function set in step P1-3 above, and determines whether any of the stop conditions for the auto progress function is satisfied. Determine.

For example, if "when story is released" is set as the "auto progress stop condition setting" and the above-mentioned main story is newly released based on the clearing of the battle game, the battle management processing unit 508a It is determined that the stop condition for the automatic advance function is satisfied.

In addition, when "immediately before the BOSS appearance quest" is set as the "auto progress stop condition setting", the condition for stopping the auto progress function is set in the battle game immediately before the battle game in which the BOSS character mentioned above appears. If the above is cleared, the battle management processing unit 508a determines that the condition for stopping the automatic progress function is satisfied.

In addition, if "Stop" is set as "Stop setting when 3-star clear is not achieved", and the condition for stopping the auto progression function is when the battle game is cleared using the auto progression function. If there is one or more ally characters whose life points are 0 when the game is cleared, the battle management processing unit 508a determines that the condition for stopping the automatic progression function is satisfied.

Further, if the battle game cannot be cleared, that is, if the battle game is defeated, the battle management processing unit 508a determines that the condition for stopping the automatic progress function is satisfied.

Further, the battle management processing unit 508a determines that the condition for stopping the automatic progress function is satisfied when the stamina possessed by the player is less than the stamina required to execute the next battle game.

In addition, the battle management processing unit 508a determines the condition for stopping the automatic progression function when the in-game currency (mana) owned by the player is less than the in-game currency (mana) required to execute the next battle game. is determined to have been established.

In addition, the battle management processing unit 508a controls the automatic progress when the battle game (for example, “60-15”) of the last layer belonging to the last area (for example, the 60th area) implemented in the game is cleared. It is determined that the function stop condition has been met.

As a result, if it is determined that the stop condition for the auto progression function is not satisfied (NO in P1-25), the battle management processing unit 508a starts the next battle game (P1-27) and repeats the above-mentioned process again. The process from step P1-7 is repeated.

Further, if it is determined that the conditions for stopping the auto progression function are satisfied (YES on P1-25), the battle management processing unit 508a stops the auto progression without starting the next battle game. Execute the stop processing (P1-29).

Although one aspect of the embodiment has been described above with reference to the accompanying drawings, it goes without saying that the present invention is not limited to the above embodiment. It is clear that those skilled in the art can come up with various modifications or modifications within the scope of the claims, and it is understood that these naturally fall within the technical scope of the present invention. be done.

Note that in the above embodiment, a case has been described in which the management process shown in FIG. 32 is executed on the player terminal 1 side. However, the present invention is not limited to this, and the management process shown in FIG. 32 may be executed on the server 1000 side. Alternatively, part of the management process may be executed on the player terminal 1 side, and the remaining processes may be executed on the server 1000 side. For example, at least a portion of the processes in step P1-7, step P1-, step P1-9, step P1-11, and step P1-21 may be executed on the server 1000 side.
The game nature and the processing at the player terminal 1 described in the above embodiment are merely examples. In any case, the information processing program may be one that causes a computer (in the embodiment, one or both of the player terminal 1 and the server 1000) to perform the following processing.

(Processing performed by a computer)
Play at least one of a plurality of predetermined games whose order is set in advance (in the embodiment, as an example, a plurality of battle games whose order is set from "1-1" to "1-15" of the main quest). Predetermined operations by the player (in the embodiment, for example, operation of the main quest operation section 73 of the main quest screen 72, operation of the challenge operation section 75 of the main quest selection screen 74, and operation of the next operation section of the party selection screen 77a for automatic progression) 79a, operation of the battle start operation section 103 of the auto progress setting screen 100, operation of the battle start operation section 103 of the auto progress setting screen 100a) (in the embodiment, as an example, P1-1) .
At least predetermined operations (in the embodiment, for example, the operation of the main quest operation section 73 of the main quest screen 72, the operation of the challenge operation section 75 of the main quest selection screen 74, the next operation section 79a of the automatic progression party selection screen 77a) , the operation of the battle start operation section 103 of the auto progress setting screen 100, the operation of the battle start operation section 103 of the auto progress setting screen 100a), the process of executing the selected predetermined game.
A process of executing an auto mode in which predetermined games are sequentially executed in order based on a predetermined opportunity without requiring a predetermined operation by the player (in the embodiment, as an example, P1-5 to P1-27).
In the auto mode, when a specific game included in a plurality of predetermined games (in the embodiment, as an example, a battle game in which a BOSS character set for each area appears) is executed, a predetermined effect (in the embodiment, As an example, a process that allows the player to set whether or not to execute the BOSS story screen 95 (in the embodiment, as an example, P1-33).
Predetermined operations (in the embodiment, for example, the operation of the main quest operation section 73 of the main quest screen 72, the operation of the challenge operation section 75 of the main quest selection screen 74, the operation of the next operation section 79a of the automatic progression party selection screen 77a) When a specific game is executed based on an input (operation of the battle start operation section 103 of the auto progress setting screen 100, operation of the battle start operation section 103 of the auto progress setting screen 100a), and a predetermined effect is executed. When a specific game is executed in auto mode with Processing for not performing the performance (in the embodiment, as an example, P1-9 to P1-15).
A process of stopping the auto mode when a predetermined termination condition is met (in the embodiment, as an example, P1-25 to P1-29).

Regarding the order set in advance for a plurality of predetermined games, in the above embodiment, as an example, the case where the order of the main quests is set from "1-1" to "1-15" is shown. Ta. However, it is not limited to this. For example, if a plurality of quests with different difficulty levels are set for one type of quest, the quests at the next stage (difficulty level) may be executed in order by automatic progression. A case where multiple quests with different difficulty levels are set for one type of quest means, for example, for a "1-1" battle game in the main quest, multiple quests with different difficulty levels such as Normal, Hard, and Very Hard are set for one type of quest. It is sufficient if the difficulty level is set. In this case, by clearing the "1-1" battle game with the Normal difficulty level, the "1-1" battle game with the Hard difficulty level will be unlocked, and the "1-1" battle game with the Hard difficulty level will be unlocked. By clearing the battle game, a battle game with a difficulty level of "1-1" of Very Hard may be released. For example, when using auto progression, "1-1" (Normal), "1-1" (Hard), "1-1" (Very Hard), "1-2" (Normal), "1 The battle game may be executed automatically in an order such as "-2" (Hard), "1-2" (Very Hard), etc. (preset order). Or, in the order (preset order) such as "1-1" (Hard), "1-2" (Hard), "1-3" (Hard), etc., that is, at the same stage in the main quest. (Difficulty level) battle games may be sequentially executed.

Furthermore, when a specific game in which the game has already been cleared is executed, a process (in the embodiment, as an example, P1-3) that allows the player to set whether or not to execute a predetermined effect is further executed. You can.

Further, a process that allows the player to set stop information that stops the auto mode when a specific game executed in the auto mode does not satisfy a predetermined clearing condition (in the embodiment, as an example, P1-3) may be further executed.
In addition, the predetermined end condition may include that the specific game executed in auto mode does not satisfy the predetermined clear condition (in the embodiment, as an example, clear 3 stars) while the stop information is set. included.

Further, for example, if the player wins a predetermined battle game and various contents such as a predetermined mini-game are released, the auto-progression end condition is satisfied in step P1-25 above. It may be determined that Note that it is also possible to include both various types of content such as a mini-game in which it is determined that the end condition for auto-progression is satisfied, and various content such as a mini-game in which it is determined that the end condition for auto-progress is not satisfied.

In the above embodiment, a so-called battle game in which an ally character competes against an enemy character is provided as an example of the game, but the specific content and game genre of the game are not limited to the above embodiment. For example, the present invention is applicable to all game genres such as roll playing games, shooting games, puzzle games, and rhythm games.

Furthermore, in the above embodiment, a case has been described in which the support character can be used in the main quest, but the support character may also be usable in the event quest.

Furthermore, in the above embodiment, the consideration required for the battle game is not limited to stamina, but also predetermined in-game currency, predetermined in-game tickets, predetermined items, etc. as compensation necessary for the battle game. You can also use it as

Further, in the above embodiment, the battle game screen 80 is displayed on the display 26 both when the auto-progress function is enabled and when the auto-progress function is disabled, but the auto-progress function is enabled. In such a case, a so-called skip function may be used to omit part or all of the display of the battle game screen 80 on the display 26.

Note that the information processing program for executing the processes in the above embodiment and various modifications may be stored in a computer-readable non-temporary storage medium and provided as the storage medium. Furthermore, a game terminal device including this storage medium may be provided. Further, the above embodiment and various modified examples may be an information processing method that implements each function and the steps shown in the flowchart.

1 Player terminal 1000 Server S Information processing system

Claims (5)

A process of enabling a player to select at least one of a plurality of predetermined games whose order is set in advance by a predetermined operation;
a process of executing the selected predetermined game based on at least the input of the predetermined operation;
A process of executing an auto mode in which the predetermined games are sequentially executed in the order without requiring the predetermined operation by the player based on a predetermined opportunity;
Processing that allows a player to set whether or not to execute a predetermined effect when a specific game included in the plurality of predetermined games is executed in the auto mode;
When the specific game is executed based on the input of the predetermined operation, and when the specific game is executed in the auto mode in a state where execution of the predetermined effect is set , the predetermined effect is executed. If the specific game is executed in the auto mode in a state where it is set not to execute the predetermined effect, the specific game is executed with the predetermined effect not executed. processing and
processing for stopping the auto mode when a predetermined termination condition is met;
Let the computer carry out the
By executing the auto mode, the predetermined games that have not yet been cleared can be executed sequentially based on the order ;
The predetermined game progresses as parameters related to the predetermined game change,
The predetermined performance is an information processing program in which the parameters do not change and the predetermined performance progresses according to player operations . a process of consuming a predetermined consideration in response to execution of the predetermined game;
During execution of the auto mode, when a predetermined operation unit is operated, a process of notifying the player of the total amount of the predetermined consideration consumed up to now;
The information processing program according to claim 1, further causing a computer to perform the following. Processing that allows a player to set stop information for stopping the auto mode when the specific game executed in the auto mode does not satisfy a predetermined clearing condition,
Furthermore, let the computer carry out the
3. The predetermined end condition includes that the specific game executed in the auto mode does not satisfy the predetermined clear condition while the stop information is set. information processing program. An information processing method performed by one or more computers, the method comprising:
The computer includes:
A process of enabling a player to select at least one of a plurality of predetermined games whose order is set in advance by a predetermined operation;
a process of executing the selected predetermined game based on at least the input of the predetermined operation;
A process of executing an auto mode in which the predetermined games are sequentially executed in the order without requiring the predetermined operation by the player based on a predetermined opportunity;
Processing that allows a player to set whether or not to execute a predetermined effect when a specific game included in the plurality of predetermined games is executed in the auto mode;
When the specific game is executed based on the input of the predetermined operation, and when the specific game is executed in the auto mode in a state where execution of the predetermined effect is set , the predetermined effect is executed. If the specific game is executed in the auto mode in a state where it is set not to execute the predetermined effect, the specific game is executed with the predetermined effect not executed. processing and
processing for stopping the auto mode when a predetermined termination condition is met;
carry out the
By executing the auto mode, the predetermined games that have not yet been cleared can be executed sequentially based on the order ;
The predetermined game progresses as parameters related to the predetermined game change,
The predetermined performance is an information processing method in which the parameter does not change and the predetermined performance is performed by a player's operation . An information processing system comprising one or more computers,
The computer includes:
A process of enabling a player to select at least one of a plurality of predetermined games whose order is set in advance by a predetermined operation;
a process of executing the selected predetermined game based on at least the input of the predetermined operation;
A process of executing an auto mode in which the predetermined games are sequentially executed in the order without requiring the predetermined operation by the player based on a predetermined opportunity;
Processing that allows a player to set whether or not to execute a predetermined effect when a specific game included in the plurality of predetermined games is executed in the auto mode;
When the specific game is executed based on the input of the predetermined operation, and when the specific game is executed in the auto mode in a state where execution of the predetermined effect is set , the predetermined effect is executed. If the specific game is executed in the auto mode in a state where it is set not to execute the predetermined effect, the specific game is executed with the predetermined effect not executed. processing and
processing for stopping the auto mode when a predetermined termination condition is met;
carry out the
By executing the auto mode, the predetermined games that have not yet been cleared can be executed sequentially based on the order ;
The predetermined game progresses as parameters related to the predetermined game change,
The information processing system allows the predetermined performance to proceed according to a player's operation without causing variations in the parameters .

Images