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

Abstract

An object of the present invention is to reduce annoyance felt by a player. An information processing program includes a process for enabling selection of at least one of a plurality of predetermined games whose order is set in advance by a predetermined operation of the player, and a predetermined game selected based on at least an input of the predetermined operation. a process of executing a game; a process of executing an auto mode in which a predetermined game is sequentially executed based on a predetermined trigger without requiring a predetermined operation by the player; and a process of stopping the auto mode when the end condition of (1) is satisfied. [Selection drawing] Fig. 7

Description

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

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

Japanese Patent No. 7029011

However, when the player is repeatedly required to perform the work for automatic execution of the game to be automatically executed, the player may feel annoyed.

SUMMARY OF THE INVENTION An object of the present invention is to provide an information processing program, an information processing method, and an information processing system capable of reducing annoyance felt by a player.

In order to solve the above problems, the information processing program
a process of enabling at least one of a plurality of predetermined games whose order is set in advance to be selected by a player's 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 game is sequentially executed based on the order without requiring the predetermined operation by the player based on a predetermined trigger;
a process of increasing content viewable by a player based on at least execution of the predetermined game;
a process of stopping the auto mode when the content increases during execution of the auto mode;
is performed by a computer.

a process of requesting payment from a player in order to execute the predetermined game of 1;
a process of displaying the total price required for a plurality of predetermined games scheduled to be sequentially executed in the auto mode;
Furthermore, you may make a computer perform.

In order to solve the above problems, the information processing method includes:
An information processing method performed by one or more computers, comprising:
The computer is
a process of enabling at least one of a plurality of predetermined games whose order is set in advance to be selected by a player's 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 game is sequentially executed based on the order without requiring the predetermined operation by the player based on a predetermined trigger;
a process of increasing content viewable by a player based on at least execution of the predetermined game;
a process of stopping the auto mode when the content increases during execution of the auto mode;
carry out

In order to solve the above problems, the information processing system
An information processing system comprising one or more computers,
The computer is
a process of enabling at least one of a plurality of predetermined games whose order is set in advance to be selected by a player's 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 game is sequentially executed based on the order without requiring the predetermined operation by the player based on a predetermined trigger;
a process of increasing content viewable by a player based on at least execution of the predetermined game;
a process of stopping the auto mode when the content increases during execution of the auto mode;
carry out

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 for explaining the hardware configuration of the player terminal. FIG. 2B is a diagram for explaining 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 a teammate character confirmation screen. FIG. 4A is a diagram illustrating an example of a story screen. FIG. 4B is a diagram illustrating an example of a quest screen. FIG. 5A is a diagram illustrating an example of a main quest screen. FIG. 5B is a diagram illustrating an example of a main quest selection screen. FIG. 5C is a diagram illustrating an example of a party selection screen. FIG. 6A is a diagram illustrating an example of a battle game screen. FIG. 6B is a diagram illustrating an example of the first result screen. FIG. 6C is a diagram illustrating an example of the second result screen. FIG. 7A is a diagram illustrating an example of an event quest screen. FIG. 7B is a first diagram illustrating an example of the event quest selection screen. FIG. 7C is a second diagram illustrating an example of the event quest selection screen. FIG. 8A is a diagram for explaining an example of an auto advance party selection screen. FIG. 8B is a first diagram illustrating an example of the auto advance setting screen. FIG. 8C is a second diagram illustrating an example of the auto advance setting screen. FIG. 9A is a diagram for explaining an example of an auto progress setting screen when stamina is insufficient. FIG. 9B is a diagram illustrating an example of a stamina recovery dialog. FIG. 9C is a diagram illustrating an example of a stamina recovery result screen. FIG. 10A is a first diagram illustrating an example of a battle game screen during auto progress. FIG. 10B is a diagram illustrating an example of the first result screen during auto advance. FIG. 10C is a first diagram for explaining an example of the second result screen during auto advance. FIG. 11A is a second diagram illustrating an example of the battle game screen during auto progress. FIG. 11B is a second diagram illustrating an example of the second result screen during auto advance. FIG. 12A is a first diagram illustrating an example of an auto progress reward list display. FIG. 12B is a first diagram illustrating an example of story release display. FIG. 13A is a second diagram illustrating an example of an auto progress reward list display. FIG. 13B is a second diagram illustrating an example of story release display. FIG. 14A is a first diagram for explaining an example of the auto progress/stop display. FIG. 14B is a second diagram illustrating an example of the auto progress/stop display. FIG. 15 is a diagram for explaining the configuration of a memory in a player terminal and functions as a computer. FIG. 16 is a diagram for explaining the configuration of a memory in a server and functions as a computer. FIG. 17 is a sequence diagram illustrating basic processing of the player terminal and server. FIG. 18 is a first flowchart illustrating an example of quest preparation processing in the player terminal. FIG. 19 is a second flowchart illustrating an example of quest preparation processing in the player terminal. FIG. 20 is a first flowchart for explaining battle game management processing in a player terminal. FIG. 21 is a flowchart for explaining auto progress stop management processing in the player terminal. FIG. 22 is a flowchart for explaining the process during display of the battle game screen on the player terminal. FIG. 23 is a flowchart for explaining the process during display of the first result screen on the player terminal. FIG. 24 is a flowchart for explaining the process during display of the second result screen on the player terminal. FIG. 25 is a flowchart for explaining release story display processing on the player terminal.

One aspect of an 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 facilitating understanding, and do not limit the present invention unless otherwise specified. In the present specification and drawings, elements having substantially the same function and configuration are given the same reference numerals to omit redundant description, and elements that are not directly related to the present invention are omitted from the drawings. 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 including a player terminal 1 functioning as a client, that is, a game terminal, a server 1000, and a communication network N having communication base stations Na.

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

The player terminal 1 can establish communication with the server 1000 via the communication network N. FIG. 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 smart phones, mobile phones, tablet devices, personal computers, game machines, and the like. In this embodiment, a case where a smart phone is used as the player terminal 1 will be described.

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

The communication base station Na is connected to the communication network N, and transmits/receives information to/from the player terminal 1 by radio. The communication network N is composed of a mobile phone network, the Internet network, a LAN (Local Area Network), a dedicated line, etc., and realizes 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 for explaining the hardware configuration of the player terminal 1. As shown in FIG. FIG. 2B is a diagram for explaining the hardware configuration of the server 1000. As shown in FIG. 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.

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

The configurations and functions of the CPU 1010, the memory 1012, the bus 1014, the input/output interface 1016, the storage unit 1018, the communication unit 1020, the input unit 1022, and the output unit 1024 of the server 1000 are the same as those of the CPU 10, the memory 12, and the They are substantially the same as the bus 14 , input/output interface 16 , storage section 18 , communication section 20 , input section 22 and output section 24 . Therefore, the hardware configuration of the player terminal 1 will be described below, and the description 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 composed of 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 unit 18 , a communication unit 20 , an input unit 22 and an output unit 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, the programs and data stored in the storage unit 18 are loaded by the CPU 10 into the memory 12 (RAM).

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

The input unit 22 includes, for example, a touch panel through which player's operations are input (accepts operations), buttons, a keyboard, a mouse, a cross key, an analog controller, and the like. Also, 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 voice of the player. That is, the input unit 22 broadly includes a device capable of inputting the player's intention in an identifiable 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 unit 24 and a touch panel provided as an input unit 22 so as to overlap the display 26 .

(game content)
Next, the content of the game provided by the information processing system S (game device G) of this embodiment will be described using an example. In this embodiment, a so-called battle game is provided in which friendly characters battle enemy characters. In the game of this embodiment, a plurality of teammate characters are provided to the player from the management side of the game. For example, the player can possess a plurality of teammate characters obtained through a lottery called gacha, or teammate characters distributed by the management side.

The player can form a party by selecting a plurality of (here, five) ally characters owned by the player. A player can play a battle game using an organized party. In the battle game, the purpose of the battle game is for allied characters organized in a party to defeat (clear) enemy characters and obtain rewards. A player can play a plurality of types of battle games with different enemy characters and different degrees of difficulty.

FIG. 3A is a diagram showing an example of the home screen 40. As shown in FIG. FIG. 3B is a diagram showing an example of a teammate character confirmation screen 50. As shown in FIG. FIG. 4A is a diagram showing an example of the story screen 60. As shown in FIG. FIG. 4B is a diagram showing an example of the quest screen 70. As shown in FIG. The display 26 of the player terminal 1 displays game screens as shown in FIGS. 3A, 3B, 4A, and 4B. 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 to start the game, and a screen for the player to confirm various settings and 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 are normal screens. The normal screen includes a home screen 40 shown in FIG. 3A, a teammate 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), a menu screen, and a screen (not shown). A plurality of screens such as a title screen 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 the game starts). As shown in FIG. 3A, on the home screen 40, a menu bar 41 is displayed at the bottom of the display 26. As shown in FIG. 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", a teammate 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 marked with "quest", a gacha screen selection operation section 41e marked with "gacha", and a menu screen selection operation section 41f marked with "menu" are provided. In addition, in the menu bar 41, the operation section corresponding to each screen is highlighted so that the screen being displayed on the display 26 can be identified.

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

Further, when the gacha screen selection operation portion 41 e is tapped, a gacha screen (not shown) is displayed on the display 26 . Further, when the menu screen selection operation portion 41f is tapped, a menu screen (not shown) is displayed on the display 26. FIG. Although detailed explanation is omitted, on the gacha screen, it is possible to perform a gacha lottery in which a teammate character can be obtained by lottery. Also, on the menu screen, you can check game settings and various information.

A header display area 42 is provided in the upper part of the home screen 40 . Player information associated with the player ID is displayed in the header display area 42 . For example, the header display area 42 displays level information 42a indicating the player level and a stamina display bar 42b indicating the player's stamina. Also, 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, friend character identification information for identifying a friend character owned by the player (hereinafter referred to as friend character ID), level information 42a, stamina information displayed on the stamina display bar 42b, and a story to be described later. It includes progress information, battle game clear information, in-game currency information indicating the amount of in-game currency possessed by the player, and the like.

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 is set with a consumption value of stamina required for playing, the maximum number of times it can be executed per day, and the like. When playing a battle game in which a consumption value of stamina required for playing is set, the player consumes stamina to play the battle game. Therefore, the player cannot play the battle game when the stamina is insufficient.

Although detailed explanation is omitted, the player can obtain a predetermined value as a player experience value when winning the battle game. Each time the player experience value reaches a certain value, the player level increases. The upper limit of stamina is set for the player level. As the player level increases, the upper limit of stamina increases. Stamina recovers by a predetermined value (for example, 1 point) at regular intervals (for example, 5 minutes) within the range of 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 the user can visually grasp the remaining amount of stamina. Also, the stamina numerical value displayed at the bottom of the stamina display bar 42b, ie, "260/277" in the example of FIG. "260", which is stamina, is displayed.

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

That is, on the teammate character confirmation screen 50, all the teammate characters possessed by the player are displayed. A different ally character ID is assigned to each ally character. Then, when the player acquires a new ally character through, for example, a gacha lottery, the player ID of the player is associated with the ally character ID of the acquired ally character.

Information about the experience value and information about the level are stored in association with the ally character ID. The experience value increases when the player wins a battle game, which will be described later, or when a predetermined item is used. The level is set according to the experience value, and the level rises each time the experience value reaches a predetermined value. Each ally character has an upper limit of level, and the level increases only within the range up to the upper limit.

Base values of combat power such as life points, offensive power, and defensive power are set for allied characters based on their levels. The player can progress the battle game more advantageously as the combat power of the ally character increases. Also, each base value set for an ally character increases as the level increases.

In addition, it is possible to equip (set) equipment such as weapons and armor to the ally character. Each piece of equipment is set with an additional value for attack power, defense power, and the like. When equipment is equipped, the added value of each equipment is added to the above-mentioned base value, and the fighting power of the ally character can be increased. Information related to equipment such as weapons and armor is also associated with the teammate character ID and configured as part of the player information.

When the story screen selection operation portion 41c of the menu bar 41 is tapped, the story screen 60 shown in FIG. 4A is displayed on the display 26. FIG. 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 portion 61 in the story screen 60 is tapped, a main story screen (not shown) is displayed on the display 26 . On the main story screen, multiple main stories that are released according to the progress of the "main quest" described later are displayed. When a new main story is released by the player proceeding with a main quest, which will be described later, the player can view the released main story from a main story screen (not shown).

Also, when the character story selection operation section 62 in the story screen 60 shown in FIG. 4A is operated (tapped), character stories (not shown) that are released according to the degree of intimacy with the ally characters are displayed on the display 26. be.

It should be noted that the degree of intimacy with a ally character increases when the player wins a battle game, which will be described later, or when a predetermined item is used. The rank of intimacy increases each time the intimacy reaches a predetermined value. Note that an upper limit value is set for the rank of intimacy for the ally character, and the rank increases only within the range up to the upper limit value. When the friend character's intimacy reaches the upper limit, all character stories for that friend character are 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 according to the progress of "event quests" to be described later are displayed. When a new extra story is released by the player advancing an event quest described later, 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 portion 41d of the menu bar 41 is tapped, the quest screen 70 shown in FIG. 4B is displayed on the display 26. FIG. 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 provided battle games 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 unit 71 includes a main quest selection operation unit 71a labeled “main quest”, a guild battle selection operation unit 71b labeled “guild battle”, and a 1V1 battle selection operation unit labeled “1V1 battle”. An operation unit 71c, a 3V3 battle selection operation unit 71d labeled "3V3 battle", and an event quest selection operation unit 71e labeled "event" are included.

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

The "event quest" can be played by the player for 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. It will happen. In other words, the event quest selection operation section 71e is hidden except during the execution period of the "event quest", and the game type selection operation section 71 consists of the main quest selection operation section 71a, the guild battle selection operation section 71b, and the 1V1 battle selection operation section. The four game type selection operation sections 71, 71c and 71d of the 3V3 battle selection operation section, are displayed.

Note that some types of battle games have release conditions. Release conditions include, for example, that the player level is equal to or higher than a predetermined value, that another predetermined battle game has been cleared, and the like. In addition, a plurality of battle games (hierarchies or rounds) belong to each battle game type. Release conditions are also set for each of these battle games. 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 or not the battle game is released based on the game release information, and only the game type selection operation section 71 of the battle game that satisfies the release condition accepts the player's operation (tap). . Therefore, the player can only play the battle game that satisfies the release condition.

When the main quest selection operation portion 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.

FIG. 5A is a diagram illustrating an example of the main quest screen 72. As shown in FIG. FIG. 5B is a diagram illustrating an example of the main quest selection screen 74. As shown in FIG. FIG. 5C is a diagram illustrating an example of the party selection screen 77. As shown in FIG.

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 (hierarchies) belonging to the main quest.

Clear information of each battle game is also displayed on the main quest operation section 73 . Clear information is indicated by, for example, three stars. In the battle game belonging to the main quest, when the battle game is cleared, stars are obtained according to the number of ally characters whose life points are 0 when the battle game is cleared. For example, if there is no friendly character whose life point is 0, three stars are obtained, and if there is only one friendly character whose life point is 0, two stars are obtained. , when there are two or more allied 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 obtained. Also, in the battle game "1-4", not even one star has been obtained, and it is reported that this battle game has not been cleared.

In the main quest, clearing the previous battle game is set as a release condition. For example, in the example of FIG. 5A, by clearing up to the battle game "1-3", the battle game "1-4" is released. ) battle game has not been released yet.

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

Also, the main quest selection screen 74 displays the stamina after consuming the stamina when challenging the battle game. Here, it is displayed that the current stamina 260 changes to 252 as the stamina is consumed.

Also, on the main quest selection screen 74, there is a challenge operation section 75 marked with "challenge" for challenging the battle game, and a "cancel" for canceling the process corresponding to the currently displayed screen. A cancel operation section 76 marked with 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 cancelled.

On the other hand, when the challenge operation unit 75 is operated (tapped), a party selection screen 77 shown in FIG. 5C is displayed on the display 26. FIG. The party selection screen 77 displays all the ally characters possessed by the player, and also displays a selected ally character display area 78 for displaying the selected ally character below.

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

On the party selection screen 77 , when the player operates (tap) the displayed ally character, the operated (tapped) ally character is displayed in the selected ally character display area 78 . That is, here, an 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 organized by the player selecting a plurality of ally characters. It should be noted that the same ally character cannot be duplicated in the party organization.

When the party formation is completed and the battle start operation section 79 is operated (tapped), the battle game is started and the battle game screen 80 is displayed on the display 26 .

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

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

Here, an ally character display area 81 is provided at the bottom of the battle game screen 80, as shown in FIG. 6A. In the ally character display area 81, a life point 81a and a deathblow gauge 81b are displayed for each ally character. The deathblow gauge 81b rises when the ally character receives damage from the enemy character or damages the enemy character. Then, when the deathblow gauge 81b reaches a predetermined maximum value, the ally character can use the deathblow. A special move gives more damage points to an enemy character than a normal attack, recovers the life points of an ally character, or gives a special effect to an enemy character.

Here, two patterns are provided for the method of using the deathblow. One is a method in which the player operates (tap) a friend character displayed in the friend character display area 81 and whose deathblow gauge 81b has reached the maximum value. The other is a method in which when the deathblow gauge 81b reaches the maximum value in the auto activated state, the ally character uses the deathblow under computer control. Note that the battle game screen 80 displays an auto-selection operation section 82, and the player can switch between the auto-activation state and the manual activation state by operating the auto-selection operation section 82. When the auto selection operation unit 82 is operated (tapped) in the manual activation state, the auto activation state in which the deathblow is automatically used is entered. Further, when the automatic selection operation unit 82 is operated (tapped) in the automatic activation state, a manual activation state in which the deathblow is manually used is entered. Even in the auto activation state, when the special move gauge 81b has reached the maximum value and the special move is not being used under computer control, if the player operates (tap) the ally character, the special move is performed. It is available.

Then, when the battle game ends normally (normally ended), the first result screen 83 is displayed on the display 26 as shown in FIG. 6B. FIG. 6B shows, as an example, the first result screen 83 when the teammate character wins.

At least part of the game result information of the battle game is displayed on the first result screen 83 . Further, on the first result screen 83, a next operation section 84 marked with "next" is displayed.

Next, when the operation unit 84 is operated (tapped), the second result screen 85 shown in FIG. 6C is displayed on the display 26 .

At least part of the game result information of the battle game is displayed on the second result screen 85 . Further, on the second result screen 85, a next operation section 86 marked with "next" is displayed. Further, when the operation unit 86 is operated (tapped) next time, the display of 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 operation unit 86 is operated (tapped) next, the main quest screen 72 shown in FIG. 5A is displayed on the display 26 .

The game result information includes the friendly character ID (party) of the friendly character, the enemy character ID of the enemy character, and information on the remaining status of the friendly character and the enemy character at the end of the battle (when the life point becomes 0 at the end of the battle game). or not), damage points given (total value), player operation information (manual activation state or auto activation state), battle log ID, battle game type information (main quest, guild battle, etc.), battle game type (clear information, battle game hierarchy, etc.), given item information, etc. are included.

In addition, whether the manual activation state or the automatic activation state is in the auto activation state from the start to the end of the battle game, and if the deathblow is not manually used by the player, it will be in the auto activation state. Activated state. Also, a battle log ID is uniquely assigned to each battle game. Also, the information associated with each type of battle game has different contents for each type of battle game.

Next, the event quest will be explained. Since the event quest is the same as the main quest in the basic part of the battle game, overlapping explanations will be omitted, and different parts from the main quest will be explained.

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

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 (hierarchies) belonging to the event quest.

The event quest operation section 173 also displays the clear information of each battle game in the same manner as the main quest described above.

Also, in the event quest, as with the main quest described above, clearing the previous battle game is set as a release condition. For example, in the example of FIG. 7A, 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 battle game “1-1” is operated (tapped), the event quest selection screen 174 shown in FIG. 7B is displayed on the display 26. FIG. 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) obtainable in the battle game.

In this embodiment, the event quest includes 15 battle games from "1-1" to "1-15". As described above, the event quest can be played by the player only during a preset period (for example, 10 days). Therefore, the difficulty level of the battle game is set relatively low so that not only advanced players but also beginner players can enjoy it. Beginner players experience victory or defeat in each battle game of event quests, since the development status of allied characters is inferior to that of advanced players. I will go.

On the other hand, advanced players may feel tired because they need to play many battle games with a low degree of difficulty and an extremely low risk of defeat. Therefore, in the present embodiment, an auto-advance function is provided that makes it possible to reduce the annoyance of the player by automatically executing the battle games in the event quest in sequence.

As shown in FIG. 7B, the event quest selection screen 174 is provided with a check box for activating the auto progress function. It is possible to switch to invalid.

That is, as shown in FIG. 7B, when the check box is checked, the auto advance function is enabled, and as shown in FIG. 7C, when the check box is not checked, the auto advance function is activated. Progress function is disabled.

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

Also, as shown in FIG. 7B, the event quest selection screen 174 includes an operation section marked with "AUTO", which indicates that a friendly character uses a special move in an automatic activation state in a battle game that is automatically progressing. In addition, an operation unit marked with "not used" is displayed to indicate that the ally character is not allowed to use the special move in the battle game that is automatically progressing. By selecting one of these operation units, the player can change whether or not the special move is automatically activated in the battle game during automatic progress.

In addition, the event quest selection screen 174 displays the stamina after consumption when the battle game is challenged by consuming the stamina. As shown in FIG. 7B, when the auto progress function is enabled, 15 battle games are scheduled to be executed sequentially from "1-1" to "1-15", so the current stamina 260 , the stamina will be consumed and will change to 140. In other words, it displays the total cost required for a plurality of predetermined games (battle games) scheduled to be sequentially executed in the auto mode (auto progression function).

Also, as shown in FIG. 7C, when the auto progress function is disabled, only the "1-1" battle game is scheduled to be executed, so stamina is consumed from the current stamina 260, 252 is displayed.

In addition, in the event quest selection screen 174 when the auto-advance function shown in FIG. It is also possible to notify that it is not an object to be operated.

Also, on the event quest selection screen 174 in FIGS. 7B and 7B, the above check box for switching between enabling and disabling the auto progress function is displayed, and the auto activation state of the deathblow in the battle game during auto progress is set. The operation unit for changing the presence/absence of the display related to the stamina required for the battle games scheduled to be executed sequentially by the auto-progress function can be displayed on the auto-progress setting screen 180 (FIGS. 8B and 8C) described later and the stamina You may make it display on the lack automatic progress setting screen 190 (FIG. 9A).

Also, on the event quest selection screen 174, there is a challenge operation section 75 labeled "challenge" for challenging the battle game, and a "cancel" for canceling the process corresponding to the currently displayed screen. A cancel operation section 76 marked with is displayed.

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

In addition, when the auto progress function is disabled, that is, when the challenge operation section 75 of FIG. be. On the other hand, when the auto progress function is activated, that is, when the challenge operation section 75 of FIG. 7B is operated (tapped), the auto progress party selection screen 177 (FIG. 8A) is displayed on the display 26 .

FIG. 8A is a diagram illustrating an example of the party selection screen 177 for auto advance. As shown in FIG. 8A, on the auto advance party selection screen 177, a selected teammate character display area 78 and a cancel operation section 76 are displayed in the same manner as the party selection screen 77 described above.

In addition, an OK operation section 179 marked with "OK" is displayed on the party selection screen 177 for auto advance. Also, at the bottom of the OK operation section 179, a caution display stating "*auto progress setting in progress" is displayed.

When the formation of the party is completed and the OK operation section 179 is operated (tapped), an auto progress setting screen 180 (FIG. 8B) or an auto progress setting screen 190 when stamina is insufficient (FIG. 9A) is displayed on the display 26 .

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

Also, as described above, in this embodiment, the story may be released according to the progress of the "event quest". Specifically, when the player wins a predetermined battle game in the "event quest", the number of stories that the player can view increases.

Therefore, if you progress all the battle games from "1-1" to "1-15" at once in "Event Quest" using the auto progress function, when the conditions for releasing the story are satisfied, Players cannot browse the story quickly. Therefore, the player who is looking forward to viewing the story may feel disappointed.

Also, if you progress all the battle games from "1-1" to "1-15" at once in the "event quest" using the auto progress function, the stage where the battle game of "1-15" has ended So, many stories can be released at once. In such a case, for example, since stories that are originally released sequentially are released all at once, the development of the story may be spoiled from the story title or the like.

Therefore, in the present embodiment, even when the auto-advancement function is enabled, an auto-advancement stop function at story release is provided to stop the auto-advancement function when a new story is released.

As shown in FIG. 8B, the auto progress setting screen 180 is provided with a check box for validating the auto progress stop function when the story is released. By operating (tapping) the check box, the player can switch between enabling and disabling the automatic progress stop function when the story is released.

That is, as shown in FIG. 8B, when a check mark is displayed in the check box labeled "stop", the auto-progress stop function is enabled when the story is released. Also, as shown in FIG. 8C, when a check mark is displayed in the check box labeled "do not stop", the auto progress stop function when releasing the story is disabled.

In this embodiment, when the story is newly released, the case where the auto-progression stop function is provided to stop the auto-progression function when the story is released has been shown, but it is not limited to this. For example, when the player level rises, when predetermined content other than the story is released, when a predetermined time (for example, 30 minutes) elapses, the auto-progress may be stopped. 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" can be, for example, when the amount of content that can be purchased with in-game currency increases.

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

When the cancel operation section 181 is operated (tapped), the auto advance party selection screen 177 is displayed on the display 26 .

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

FIG. 9A is a diagram illustrating an example of an auto advance setting screen 190 when stamina is insufficient. FIG. 9B is a diagram illustrating an example of the stamina recovery dialogue 200. As shown in FIG. FIG. 9C is a diagram illustrating an example of the stamina recovery result screen 210. As shown in FIG. When the party formation is completed and the OK operation section 179 is operated (tapped), if the total consumed stamina is less than the current stamina, an auto progression setting screen 190 when stamina is insufficient shown in FIG. 9A appears on the display 26. to be displayed.

As shown in FIG. 9A, the stamina-insufficient auto progress setting screen 190 displays the current stamina (here, 60) and the total consumed stamina in the same way as the auto progress setting screen 180 (FIG. 8B). be. Furthermore, in the stamina shortage auto progress setting screen 190, it is displayed that the stamina is insufficient to clear the 15 battle games from "1-1" to "1-15".

Further, in the stamina-insufficient auto-advance setting screen 190, similarly to the above-described auto-advance setting screen 180 (FIG. 8B), a check box is provided for enabling the auto-advance stop function when the story is released.

In addition, on the stamina shortage auto progress setting screen 190, there is a cancel operation section 191 marked "cancel", a next operation section 192 marked "next without recovery", and a next operation section 192 marked "recover". A recovery operation section 193 is displayed.

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

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

Further, when the recovery operation unit 193 is operated (tapped), a stamina recovery dialog 200 shown in FIG. 9B is displayed on the display 26. FIG. As shown in FIG. 9B, the stamina recovery dialog 200 includes the number of in-game currency consumed to recover stamina, the number of in-game currency possessed by the player, the amount of stamina to be recovered, and the amount of stamina recovered. A confirmation to do so will be displayed.

Also, in the stamina recovery dialog 200, a cancel operation section 201 labeled "cancel" and an OK operation section 202 labeled "OK" are displayed.

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

Further, when the OK operation unit 202 is operated (tapped), the in-game currency owned by the player is consumed and stamina is recovered, and the stamina recovery result screen shown in FIG. 9C is displayed on the display 26. 210 is displayed.

As shown in FIG. 9C, on the stamina recovery result screen 210, the number of in-game currency consumed to recover stamina, the change in the number of in-game currency possessed by the player, the The amount of stamina and the notification that stamina has been restored are displayed.

Also, on the stamina recovery result screen 210, an OK operation section 211 marked with "OK" is displayed. When the OK operation unit 211 is operated, the automatic progress setting screen 180 is displayed on the display 26 .

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

As with the main quest described above, the first result screen 83 and the second result screen 85 are displayed on the display 26 when the conditions for ending the battle game are satisfied.

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

Also, during auto progress, the player cannot manually activate the special move of the ally character. Further, during automatic progression, even if the player operates (tap) the automatic selection operation section 82, switching between the automatic activation state and the manual activation state cannot be performed.

Further, during auto progress, when a predetermined time (for example, one second) elapses after the first result screen 83 is displayed, the operation unit 84 is operated next to the first result screen 83. It is regarded as having been (tapped), and the display on the display 26 automatically transitions to the second result screen 85 . At this time, the next operation unit 84 marked with "next" is displayed in the dark, and may be notified that it is not an operation target.

Further, during auto progress, when a predetermined time (for example, one second) elapses after the second result screen 85 is displayed, the operation unit 86 is operated next to the second result screen 85. It is regarded as having been (tapped), and the display of the second result screen 85 on the display 26 ends. At this time, the next operation unit 86 marked with "next" is displayed in the dark, and may be notified that it is not an operation target.

Therefore, at the time of auto progress, even if the player operates (tap) the next operation section 84 of the first result screen 83 and the next operation section 86 of the second result screen 85, screen transition is performed. I can't do it.

FIG. 11A is a second diagram illustrating an example of the battle game screen 80 during auto progress. FIG. 11B is a second diagram illustrating an example of the second result screen 85 during auto advance. FIG. 12A is a first diagram illustrating an example of an auto progress reward list display 220. FIG. FIG. 12B is a first diagram illustrating an example of the story release display 230. FIG. In the event that the auto progress stop function is disabled during auto progress and when the story is released, when the display of the second result screen 85 ends, the next battle game in the event quest (here, "1-2" ) is automatically started. After that, the battle game screen 80, the first result screen 83, and the second result screen 85 are similarly displayed, and the event quest battle game is executed until "1-15".

That is, on the display 26, the next quest is displayed without going through the display of the event quest screen 172, the event quest selection screen 174, the auto progress party selection screen 177, the auto progress setting screen 180, and the auto progress setting screen 190 when the stamina is insufficient. It will start.

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

Finally, as shown in FIG. 11B, the display 26 displays the second result screen 85 for the event quest "1-15" battle game. In addition, on the second result screen 85, a pop-up display is displayed to notify that the auto progress has ended, and in the pop-up display, the number and types of battle games cleared and the total number of stamina consumed by the player are displayed. You may make it display.

When the display of the second result screen 85 ends, as shown in FIG. 12A, an event quest screen 172 is displayed on the display 26, and an auto progress reward list display 220 is displayed superimposed on the event quest screen 172. be.

As shown in FIG. 12A, in the auto progress reward list display 220, a list of items (rewards) acquired during auto progress is displayed.

Also, in the auto progress reward list display 220, a close operation section 221 marked with "close" is displayed. When the close operation unit 221 is operated (tapped), a story release display 230 is displayed on the display 26 as shown in FIG. 12B.

As shown in FIG. 12B, in the story release display 230, a newly released story operation section 231 for viewing newly released stories during auto-progress and a close operation section 232 labeled "close" are displayed. be done. When the newly released story operation section 231 is operated (tapped), the contents of each story can be viewed.

It should be noted that in order to view a newly released story during auto progression, it is possible to view it from the above-described extra story screen (not shown) without operating the newly released story operation section 231 .

FIG. 13A is a diagram illustrating an example of an auto progress reward list display 220. FIG. FIG. 13B is a diagram illustrating an example of the story release display 230. As shown in FIG. Suppose that a predetermined release condition is established during auto-progress and when the auto-progress stop function at story release is set to be valid. Here, as the release condition, the player has won a predetermined battle game and the number of stories that the player can view has increased. In this case, when the display of the second result screen 85 ends, the next battle game in the event quest does not start, and the auto progress is stopped.

At this time, as shown in FIG. 13A, the items (rewards) acquired by the player up to the time when the auto progress was stopped are listed in the auto progress 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 so that the story that was newly released at the time when the auto progress was stopped can be browsed.

FIG. 14A is a first diagram illustrating an example of the auto-advance stop display 240. FIG. FIG. 14B is a second diagram illustrating an example of the auto progress/stop display 240. As shown in FIG. During auto progress, if an operation (tap) is performed on the teammate character display area 81 of the battle game screen 80 or an operation (tap) is performed on the auto selection operation section 82, the battle game is temporarily stopped. In addition to these, please add that it may be possible to stop by operating (tapping) a predetermined place on each screen. For example, the battle game may be temporarily stopped when a menu operation unit (not shown) for displaying a menu screen (not shown) is operated (tapped). Also, the battle game may be temporarily stopped when a predetermined peripheral area of each operation unit is operated (tapped) instead of the operation unit itself. As described above, during auto progress, the player manually activates the deathblow of a friendly character on the battle game screen 80, and the auto activation state based on the player's operation (tap) on the auto selection operation section 82. It is not possible to switch to the manual activation state. When the battle game is stopped, an auto-progress stop display 240 shown in FIG. 14A is superimposed on the battle game screen 80 .

Similarly, during auto-advance, when an operation (tap) is performed on the next operation unit 84 of the first result screen 83 or the next operation unit 86 of the second result screen 85, the auto-advancement is stopped as shown in FIG. 14B. The display 240 is displayed so as to be superimposed on the first result screen 83 and the second result screen 85 being displayed.

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

When the cancel operation unit 241 is operated (tapped), the auto progress stop display 240 disappears on the display 26 . In addition, with the display of the auto-progress stop display 240, the temporarily stopped battle game is restarted by auto-progress.

Further, when the OK operation section 242 is operated (tapped), the automatic progress stop display 240 disappears on the display 26, and the battle game is restarted with the automatic progress stopped. Along with this, the auto progress display 215 displayed on the battle game screen 80, the first result screen 83, or the second result screen 85 is also hidden.

Further, when the automatic progress is stopped, the automatic screen transition in the first result screen 83 and the second result screen 85 is not executed either. When the automatic progression is stopped, when the player operates (tap) the operation unit 84 next to the first result screen 83 , the second result screen 85 is displayed on the display 26 . Then, when the operation unit 86 is operated (tapped) by the player next to the second result screen 85, the display of the second result screen 85 on the display 26 ends. Then, since the auto progress 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 time when the auto progress was stopped are listed in the auto progress reward list display 220 . Further, when the close operation unit 221 is operated (tapped), a story release display 230 is displayed on the display 26 to allow browsing of the story that was newly released when the auto progress was stopped.

Next, functional configurations of the player terminal 1 and the server 1000 for executing the battle game of the main quest and event quest will be described.

(Control processing in player terminal 1 and server 1000)
FIG. 15 is a diagram for explaining the configuration of the memory 12 in the player terminal 1 and its function as a computer. A game control program 500 is stored in the program storage area 12a. The above program stored in the program storage area 12a is merely an example, and many other programs are stored in the program storage area 12a.

The data storage area 12b is provided with an information storage section 550 that stores various information for the battle game. Note that the above storage section provided in the data storage area 12b is an example, and a large number of other storage sections are provided in the data storage area 12b.

The CPU 10 operates each program stored in the program storage area 12a and updates the data in each storage section of the data storage area 12b. The CPU 10 causes the player terminal 1 (computer) to function as the terminal-side control section 1A by operating each program stored in the program storage area 12a. The terminal-side control section 1A includes a game control section 500a.

Specifically, the CPU 10 operates the game control program 500 to cause the computer to function as a game control section 500a.

FIG. 16 is a diagram illustrating the configuration of memory 1012 in server 1000 and its function as a computer. A game control program 150 is stored in the program storage area 1012a. The above program stored in the program storage area 1012a is only an example, and many other programs are stored in the program storage area 1012a.

The data storage area 1012b is provided with an information storage section 1550 that stores various information of the battle game. Note that the above storage section provided in the data storage area 1012b is an example, and a large number of other storage sections are provided in the data storage area 1012b.

CPU 1010 operates each program stored in program storage area 1012a and updates data in each storage unit in data storage area 1012b. CPU 1010 causes server 1000 (computer) to function as server-side control unit 1000A by operating each program stored in program storage area 1012a. The server-side control unit 100A includes a game control unit 1500a.

Specifically, the CPU 110 operates the game control program 150 to cause the computer to function as the game control section 1500a. Part of the processing performed by the terminal-side control section 1A and the server-side control section 1000A will be described below.

(Communication processing between player terminal 1 and server 1000)
FIG. 17 is a sequence diagram illustrating basic processing of the player terminal 1 and the server 1000. FIG. In the following description, processing in the player terminal 1 will be indicated as Pn (n is an arbitrary integer). Also, processing in the server 1000 is represented by Sn (n is an arbitrary integer).

In the player terminal 1, when the player performs a login operation such as activating a game application, the terminal-side control section 1A transmits login information to the server 1000 (P1).

In the server 1000, when the login information is received, the server-side control unit 1000A performs login management processing for causing the player terminal 1 to receive (acquire) the player information and game information stored in the server 1000 (S1 ).

When the player terminal 1 receives (acquires) player information from the server 1000 , the terminal-side control section 1</b>A stores the received player information and game information in the information storage section 550 .

Also, in the player terminal 1, a quest preparation process (P2) is executed for accepting a battle game start operation such as a main quest or an event quest.

FIG. 18 is a first flowchart illustrating an example of the quest preparation process (P2) in the player terminal 1. FIG. 19 is a second flowchart illustrating an example of the quest preparation process (P2) in the player terminal 1. FIG. As shown in FIG. 18, the game control unit 500a of the player terminal 1 determines whether or not the main quest operation unit 73 of the main quest screen 72 has been operated (tapped) (P2-1).

As a result, when the main quest operation unit 73 is operated (tapped) (YES in P2-1), the game control unit 500a of the player terminal 1 responds to the tapped (operated) main quest operation unit 73. The main quest selection screen 74 is displayed on the display 26 (P2-2), and the quest preparation process ends.

When the main quest operation unit 73 is not operated (tapped) (NO in P2-1), the game control unit 500a of the player terminal 1 causes the event quest operation unit 173 of the event quest screen 172 to be operated (tapped). ) is determined (P2-3).

As a result, when the event quest operation unit 173 is operated (tapped) (YES in P2-3), the game control unit 500a of the player terminal 1 derives the total consumed stamina and stores it in the information storage unit 550. (P2-4).

Further, the game control unit 500a of the player terminal 1 displays the event quest selection screen 174 on the display 26 based on the total consumed stamina derived in step P2-4 (P2-5), and ends the quest preparation process. do.

Further, when the event quest operation unit 173 is not operated (tapped) (NO in P2-3), the game control unit 500a of the player terminal 1 displays the main quest selection screen 74 or the event quest selection screen 174. It is determined whether or not the challenge operation section 75 has been operated (tapped) (P2-6).

As a result, when the main quest selection screen 74 or the challenge operation section 75 of the event quest selection screen 174 is operated (tapped) (YES in P2-6), the game control section 500a of the player terminal 1 executes the event In the quest selection screen 174, it is determined whether or not a check has been entered in the item of auto progress, that is, whether or not auto progress has been set (P2-7).

As a result, if auto-advance is set, that is, if a check has been entered in the auto-advance item on the event quest selection screen 174 (YES at P2-7), the game control unit 500a of the player terminal 1 stores (updates) the setting contents of the auto advance in the information storage unit 550 (P2-8). In step P2-5 above, by referring to the setting contents of auto progression stored in the information storage unit 550, the same content as the setting contents of auto progression that was stored when the previous event quest was executed, An event quest selection screen 174 can be displayed on the display 26 .

In addition, the game control unit 500a of the player terminal 1 turns on the auto-progress setting flag and the auto-progress reward list display flag indicating that the execution of the event quest is determined with the auto-progress enabled (P2-9, P2-10).

In addition, the game control unit 500a of the player terminal 1 displays the auto progress party selection screen 177 on the display 26 (P2-11), and ends the quest preparation process.

Also, if auto progress is not set (NO in P2-7), that is, if a check has not been entered in the auto progress item on the event quest selection screen 174, and if the main quest selection screen 74 has a challenge operation When the part 75 is operated (tapped), the game control part 500a of the player terminal 1 displays the party selection screen 77 on the display 26 (P2-12), and ends the quest preparation process.

Further, the game control section 500a of the player terminal 1 determines whether or not the OK operation section 179 of the auto progress party selection screen 177 has been operated (tapped) (P2-13).

As a result, when the OK operation section 179 of the party selection screen 177 for auto progress is operated (tapped) (YES in P2-13), the game control section 500a of the player terminal 1 derives in step P2-4. With reference to the total consumed stamina and the stamina information stored in the information storage unit 550, it is determined whether or not the total consumed stamina is equal to or less than the current stamina of the player (P2-14).

As a result, if the total consumed stamina is equal to or less than the player's current stamina (YES in P2-14), the game control unit 500a of the player terminal 1 displays the auto progress setting screen 180 on the display 26 (P2 -15), the quest preparation process ends.

Also, if the total consumed stamina is not equal to or less than the current stamina of the player (NO in P2-14), the game control unit 500a of the player terminal 1 displays the stamina shortage auto progress setting screen 190 on the display 26 ( P2-16), the quest preparation process ends.

Further, when the OK operation section 179 of the party selection screen 177 for auto progress is not operated (tapped) (NO in P2-13), the game control section 500a of the player terminal 1 displays the auto progress setting screen when stamina is insufficient. It is determined whether or not the recovery operation unit 193 of 190 has been operated (P2-17).

As a result, when the recovery operation section 193 of the stamina shortage auto progress setting screen 190 is operated (YES in P2-17), the game control section 500a of the player terminal 1 displays the stamina recovery dialog 200 on the display 26. is displayed (P2-18), and the quest preparation process ends.

Further, if the recovery operation section 193 of the stamina shortage auto progress setting screen 190 is not operated (NO in P2-17), the game control section 500a of the player terminal 1 displays the OK operation section of the stamina recovery dialogue 200. 202 is operated (tapped) (P2-19).

As a result, if the OK operation unit 202 of the stamina recovery dialogue 200 is operated (tapped) (YES in P2-19), the game control unit 500a of the player terminal 1 will pay for the in-game currency owned by the player. to perform a stamina recovery process to restore the player's stamina. Specifically, in-game currency information and stamina information included in the player information are updated.

Also, the game control unit 500a of the player terminal 1 displays the stamina recovery result screen 210 on the display 26, and ends the quest preparation process.

Further, when the OK operation section 202 of the stamina recovery dialog 200 is not operated (tapped) (NO in P2-19), the game control section 500a of the player terminal 1 displays the OK operation section 211 of the stamina recovery result screen 210. is operated (tapped) (P2-22).

As a result, when the OK operation section 211 of the stamina recovery result screen 210 is operated (tapped) (YES in P2-22), the game control section 500a of the player terminal 1 displays the auto progress setting screen 180 on the display 26. is displayed (P2-23), and the quest preparation process ends.

Further, when the OK operation section 211 of the stamina recovery result screen 210 is not operated (tapped) (NO in P2-22), the game control section 500a of the player terminal 1 controls the battle start operation section of the party selection screen 77. 79 or whether or not the battle start operation section 182 of the auto progress setting screen 180 has been operated (tapped) (P2-24).

As a result, if the battle start operation section 79 of the party selection screen 77 or the battle start operation section 182 of the auto progress setting screen 180 is not operated (tapped) (NO in P2-24), the player terminal 1 The game control unit 500a determines whether or not the operation unit 192 has been operated (tapped) next to the auto advance setting screen 190 when stamina is insufficient (P2-25).

As a result, if the operation unit 192 is not operated (tapped) next to the stamina shortage auto progress setting screen 190 (NO in P2-25), the game control unit 500a of the player terminal 1 performs the quest preparation process. exit.

Also, when the battle start operation section 79 of the party selection screen 77 or the battle start operation section 182 of the auto progress setting screen 180 is operated (tapped) (YES in P2-24), and when the stamina is insufficient auto progress setting When the operation unit 192 is operated (tapped) next to the screen 190 (YES in P2-25), the game control unit 500a of the player terminal 1 supplies the player with the stamina required to start the battle game. While stamina is consumed, start information including party information selected by the player, battle game type information, etc. is transmitted to the server 1000, and the quest preparation process ends.

Returning to FIG. 17, when the start information is received, the server 1000 sets the battle game start information necessary for starting the battle game so that the player terminal 1 can acquire it (S2).

Then, when the player terminal 1 receives (obtains) the battle game start information, it performs battle game start processing for starting the battle game (P3). Here, for example, an area of the memory 12 for progressing the battle game is secured, a predetermined program is read from the storage unit 18 to the memory 12, and a battle game screen 80 is displayed on the display 26.

Thereafter, battle game management processing for managing the battle game is performed in the player terminal 1 (P4). In this battle game management process, an update process for updating various information is repeatedly executed on a frame-by-frame basis. The number of frames is not particularly limited. For example, the number of frames per second is 30-60. Therefore, during the battle game, information is updated in the player terminal 1 at intervals of about 16 ms (milliseconds) to 33 ms.

FIG. 20 is a first flowchart illustrating an example of battle game management processing in the player terminal 1. FIG. As shown in FIG. 20, the game control unit 500a of the player terminal 1 executes auto-progress stop management processing for managing stop of auto-progress in the battle game being executed (P40). The details of the automatic progress stop management process will be described later.

Also, the game control unit 500a of the player terminal 1 determines whether or not the battle game screen 80 is being displayed on the display 26 (P4-1).

As a result, if the battle game screen 80 is being displayed (YES in P4-1), the game control unit 500a of the player terminal 1 executes the battle game screen displaying process for managing the progress of the battle game being executed. Execute (P41) and terminate the battle game management process. The details of the process during display of the battle game screen will be described later.

If the battle game screen 80 is not being displayed (NO in P4-1), the game control unit 500a of the player terminal 1 determines whether the new story release information set in the server 1000 has been newly acquired. is determined (P4-2).

As a result, when new story release information is newly acquired (YES in P4-2), the game control section 500a of the player terminal 1 stores the story new release information in the information storage section 550 (P4-3). , the battle game management process ends. Note that the new story release information indicates that when a predetermined release condition is met, more specifically, the player wins a predetermined battle game, and the number of stories that the player can browse increases. This information is set in the server 1000 so that the player terminal 1 can acquire it.

Further, when the story new release information is not newly acquired (NO in P4-2), the game control unit 500a of the player terminal 1 determines whether the first result screen 83 is being displayed on the display 26. (P4-4).

As a result, when the first result screen 83 is being displayed (YES in P4-4), the game control unit 500a of the player terminal 1 manages the display of the first result screen 83. Processing is executed (P42), and the battle game management processing ends. The details of the process during display of the first result screen will be described later.

When the first result screen 83 is not being displayed (NO in P4-4), the game control unit 500a of the player terminal 1 determines whether the second result screen 85 is being displayed on the display 26. is determined (P4-5).

As a result, when the second result screen 85 is being displayed (YES in P4-5), the game control unit 500a of the player terminal 1 manages the display of the second result screen 85. Processing is executed (P43), and the battle game management processing ends. The details of the process during display of the second result screen will be described later.

If the second result screen 85 is not being displayed (NO in P4-5), the game control section 500a of the player terminal 1 terminates the battle game management process.

FIG. 21 is a flow chart for explaining the auto progress stop management process (P40) in the player terminal 1. FIG. As shown in FIG. 21, the game control unit 500a of the player terminal 1 determines whether or not the auto progress setting flag is ON (P40-1).

As a result, if the auto progress setting flag is not ON (NO in P40-1), the game control section 500a of the player terminal 1 terminates the auto progress stop management process.

If the auto progress setting flag is ON (YES in P40-1), the game control unit 500a of the player terminal 1 displays the auto progress display 215 on the display 26 (P40-2).

Further, the game control unit 500a of the player terminal 1 determines whether or not a predetermined area has been operated (tapped) (P40-3). Specifically, the game control section 500a of the player terminal 1 includes, for example, an area including the teammate character display area 81 and the auto selection operation section 82 in the battle game screen 80, and a next operation section 84 in the first result screen 83. It is determined whether or not any of the regions including the next operation section 86 on the second result screen 85 has been operated (tapped) (P40-3).

As a result, when a predetermined area is operated (tapped) (YES in P40-3), the game control unit 500a of the player terminal 1 displays an auto progress stop display 240 on the display 26 ( P40-4), the auto progress stop management process is ended.

Further, when a predetermined region has not been operated (tapped) (NO in P40-3), the game control unit 500a of the player terminal 1 causes the OK operation unit 242 of the automatic progress stop display 240 to operate. It is determined whether or not it has been (tapped) (P40-5).

As a result, when the OK operation unit 242 of the auto progress stop display 240 is operated (tapped) (YES in P40-5), the game control unit 500a of the player terminal 1 closes the auto progress stop display 240 on the display 26. The display is hidden (P40-6), the auto progress setting flag is turned off (P40-7), the auto progress display 215 on the display 26 is hidden (P40-8), and the auto progress stop management process is terminated.

Further, when the OK operation unit 242 of the auto progress stop display 240 is not operated (tapped) (NO in P40-5), the game control unit 500a of the player terminal 1 terminates the auto progress stop management process. .

FIG. 22 is a flowchart for explaining the process during battle screen display (P41) in the player terminal 1. FIG. As shown in FIG. 22, the game control unit 500a of the player terminal 1 executes arithmetic processing for changing various parameters (P41-1). As the arithmetic processing, for example, damage arithmetic processing is performed when an ally character attacks an enemy character and when an enemy character attacks an ally character.

The game control unit 500a of the player terminal 1 also executes animation drawing processing for drawing various actions of each friend character and each enemy character in the battle game (P41-2).

Further, the game control unit 500a of the player terminal 1 determines whether or not the teammate character display area 81 has been operated (tapped) (P41-3).

As a result, if an operation (tap) has been performed on the teammate character display area 81 (YES in P41-3), the game control section 500a of the player terminal 1 displays the teammate character display area where the operation (tap) has been performed. It is determined whether or not a predetermined condition for exercising a "special move" is satisfied for 81 allied characters (P41-4).

As a result, if the predetermined condition is satisfied for the teammate character in the teammate character display area 81 that has been operated (tapped) (YES in P41-4), the game control unit 500a of the player terminal 1 performs the following operation. Then, the process moves to step P41-8.

In addition, when the operation (tap) of the teammate character display area 81 is not performed (NO in P41-3), or when the operation (tap) is performed for the teammate character in the teammate character display area 81, the predetermined condition is satisfied. If not (NO in P41-4), the game control unit 500a of the player terminal 1 determines that there is a friendly character that satisfies a predetermined condition that allows the execution of the "special move" for each friendly character in the battle game. Specifically, it is determined whether or not there is an ally character whose special move gauge 81b has reached the maximum value (P41-5).

As a result, if there is an ally character for which the predetermined condition is satisfied (YES in P41-5), the game control unit 500a of the player terminal 1 enters an auto activation state in which the deathblow is automatically used in the battle game. (P41-6).

As a result, if the automatic activation state is not set (NO in P41-6), the game control unit 500a of the player terminal 1 terminates the battle screen displaying process.

If it is in the auto activation state (YES in P41-6), the game control unit 500a of the player terminal 1 determines whether or not it is the activation timing at which the deathblow can be activated under computer control (P41-6). 7). For example, the timing when the fighting time of the battle game remains and the special move is not being activated by another ally character is the activation timing at which the special move can be activated.

As a result, if a predetermined condition is satisfied for the friendly character in the friendly character display area 81 that has been operated (tapped) (YES in P41-4), or the execution timing at which the deathblow can be executed by computer control is determined. (YES in P41-7), the game control unit 500a of the player terminal 1 executes the special move activation process of determining the activation of the "special move" preset for the processing target teammate character. (P41-8), the process during display of the battle screen ends. In addition, in the deathblow technique activation process, a deathblow gauge change process for changing the value of the deathblow gauge 81b is executed along with the activation of the "special move".

It should be noted that if the auto selection operation section 82 or the teammate character display area 81 is operated while the auto progress is set, the auto progress stop display 240 will be displayed on the display 26 in steps P40-1 to P40-4. will be displayed in That is, if the determination in step P41-3 is YES, it means that the automatic advance is not set. Therefore, when the auto progression is set, the special move is not activated manually by the player.

Further, if there is no teammate character for which the predetermined condition is established (NO in P41-5) and if it is not the activation timing (NO in P41-7), the game control unit 500a of the player terminal 1 starts the battle game. It is determined whether or not the termination condition is satisfied (P41-9). For example, it is determined that the end condition of the battle game is established when any one of the following conditions is satisfied: allied characters are annihilated, enemy characters are annihilated, or the fighting time of the battle game has elapsed.

As a result, if the battle game end condition is satisfied (YES in P41-9), the game control section 500a of the player terminal 1 sends the game result information indicating the result of the battle game for which the end condition is satisfied to the server 1000. (P41-10), the first result screen 83 is displayed on the display 26 based at least on the game result information (P41-11), and the process during the battle screen display ends.

Returning to FIG. 17, when acquiring the game result information, the server 1000 updates the player information (S3). In addition, based on the acquired game result information, the server 1000 sets story new release information and allows the player to win a predetermined battle game and the number of stories that the player can view increases. A story release management process that can be acquired by the terminal 1 is executed (S4).

FIG. 23 is a flowchart for explaining the processing during display of the first result screen (P42) in the player terminal 1. FIG. As shown in FIG. 23, the game control unit 500a of the player terminal 1 determines whether or not the auto progress setting flag is ON (P42-1).

As a result, when the auto progress setting flag is ON (YES in P42-1), the game control section 500a of the player terminal 1 determines whether or not a predetermined screen transition condition is satisfied (P42 -2). Specifically, for example, when a predetermined time (for example, 1 second) has passed since the first result screen 83 was displayed, it is determined that the screen transition condition has been satisfied.

As a result, if the screen transition condition is not satisfied (NO in P42-2), the process during display of the first result screen is terminated.

If the auto progress setting flag is not ON (NO in P42-1), the game control unit 500a of the player terminal 1 determines whether the operation unit 84 has been operated (tapped) after the first result screen 83. (P42-3).

As a result, if the operation unit 84 has not been operated (tapped) next to the first result screen 83 (NO in P42-3), the game control unit 500a of the player terminal 1 continues to display the first result screen. End the process.

Further, when the screen transition condition is established (YES in P42-2), and when the operation unit 84 is operated (tapped) to the next of the first result screen 83 (YES in P42-3), the player terminal 1 displays the second result screen 85 on the display 26 (P42-4), and ends the process during display of the first result screen.

FIG. 24 is a flowchart for explaining the second result screen displaying process (P43) in the player terminal 1. FIG. As shown in FIG. 24, the game control unit 500a of the player terminal 1 determines whether or not the auto progress setting flag is ON (P43-1).

As a result, if the auto progress setting flag is not ON (NO in P43-1), the game control unit 500a of the player terminal 1 checks whether the operation unit 84 has been operated after the second result screen 85. Judgment (P43-2).

As a result, when the operation unit 84 is operated after the second result screen 85 (YES in P43-2), the game control unit 500a of the player terminal 1 shifts the processing to step P43-7 described later.

Further, when the operation unit 84 has not been operated after the second result screen 85 (NO in P43-2), the game control unit 500a of the player terminal 1 terminates the process during display of the second result screen. .

Further, when the auto progress setting flag is ON (YES in P43-1), the game control unit 500a of the player terminal 1 determines whether or not a predetermined screen transition condition is established (P43- 3). For example, when a predetermined time (for example, 1 second) has passed since the second result screen 85 was displayed, it is determined that the screen transition condition has been met.

As a result, if the screen transition condition is not satisfied (NO in P43-3), the second result screen displaying process is ended.

Further, when the screen transition condition is established (YES in P43-3), the game control unit 500a of the player terminal 1 refers to the information storage unit 550, confirms the story new release information (P43-4), and , Confirm the setting contents of auto progress (P43-5).

Further, the game control section 500a of the player terminal 1 determines whether or not a predetermined auto progress condition is established (P43-6). Specifically, the setting contents of the auto progress confirmed in the above step P43-5 is the setting to stop the auto progress when the story is released, and the story new release information is stored in the above step P43-4. When this is confirmed, it is determined that the auto advance condition is not satisfied. On the other hand, if the setting contents of auto progress confirmed in step P43-5 do not stop the auto progress when the story is released, it is determined that the auto progress condition is met. Also, when the amount of stamina of the player falls below the amount of stamina required for playing the next battle game, it is determined that the auto progress condition is not established.

As a result, when the auto progress condition is established (YES in P43-6), the game control section 500a of the player terminal 1 shifts the process to step P43-12, which will be described later.

Further, when the operation unit 84 is operated next to the second result screen 85 (YES in P43-2), and when the auto progress condition is not satisfied (NO in P43-6), the player terminal 1 , the game control unit 500a terminates the display of the second result screen 85 on the display . At this time, on the display 26, when the display of the second result screen 85 of the main quest is finished, the main quest screen 72 is displayed, and when the display of the second result screen 85 of the event quest is finished, , the event quest screen 172 is displayed.

Also, the game control unit 500a of the player terminal 1 determines whether or not the auto progress reward list display flag is ON (P43-8).

As a result, if the auto progress reward list display flag is not ON (NO in P43-8), the game control section 500a of the player terminal 1 terminates the process during display of the second result screen.

Further, when the auto progress reward list display flag is ON (YES in P43-8), the game control unit 500a of the player terminal 1 turns off the auto progress reward list display flag (P43-9), and the auto progress reward list display flag is turned off. The setting flag is turned off (P43-10), the auto progress reward list display 220 is displayed on the display 26 (P43-11), and the process during display of the second result screen ends.

Further, when the auto progress condition is satisfied (YES in P43-6), the game control unit 500a of the player terminal 1 terminates the display of the second result screen 85 on the display 26 (P43-12), Start information for starting the battle game of the next event quest in a predetermined order is transmitted to the server 1000 (P43-13), and the process during display of the second result screen ends.

Returning to FIG. 17, when the battle game management process ends, the player terminal 1 executes the release story display process (P5).

FIG. 25 is a flowchart for explaining release story display processing (P5) in the player terminal 1. FIG. As shown in FIG. 25, the game control unit 500a of the player terminal 1 determines whether or not the story release display 230 is being displayed on the display 26 (P5-1).

As a result, if the story release display 230 is being displayed (YES in P5-1), the game control unit 500a of the player terminal 1 determines whether the closing operation unit 232 of the story release display 230 has been operated (tapped). (P5-2).

As a result, when the operation unit 232 to close the story release display 230 is operated (tapped) (YES in P5-2), the game control unit 500a of the player terminal 1 hides the story release display 230 (P5 -3), terminate the release story display process.

Further, when the close operation unit 232 of the story release display 230 is not operated (tapped) (NO in P5-2), the game control unit 500a of the player terminal 1 causes the new release story operation unit 231 to be operated (tapped). ) is determined (P5-4).

As a result, when the newly released story operation section 231 is operated (tapped), the game control section 500a of the player terminal 1 corresponds to the newly released story operation section 231 operated (tapped) in step P5-4. The story to be released is displayed on the display 26 (P5-4), and the release story display process ends.

Further, when the story release display 230 is not being displayed (NO in P5-1), the game control unit 500a of the player terminal 1 determines whether the auto progress reward list display 220 is being displayed on the display 26. is determined (P5-6).

As a result, when the auto progress reward list display 220 is not being displayed (NO in P5-6), the game control unit 500a of the player terminal 1 makes a screen transition to the main quest screen 72 or the event quest screen 172. It is determined whether or not it is time (P5-7).

As a result, if the screen is not transitioning to the main quest screen 72 or the event quest screen 172 (NO in P5-7), the game control unit 500a of the player terminal 1 terminates the release story display process. .

Further, when the screen transition is to the main quest screen 72 or the event quest screen 172 (YES in P5-7), the game control section 500a of the player terminal 1 causes the process to proceed to step P5-10, which will be described later. Move.

Further, when the auto progress reward list display 220 is being displayed (YES in P5-6), the game control unit 500a of the player terminal 1 determines whether the operation unit 221 for closing the auto progress reward list display 220 has been operated. (P5-8).

As a result, if the closing operation unit 221 of the auto progress reward list display 220 has not been operated (NO in P5-8), the game control unit 500a of the player terminal 1 terminates the release story display processing.

Further, when the operation unit 221 for closing the auto progress reward list display 220 is operated (YES in P5-8), the game control unit 500a of the player terminal 1 hides the display of the auto progress reward list display 220. (P5-9).

Also, the game control unit 500a of the player terminal 1 refers to the information storage unit 550 and determines whether or not story new release information is stored (P5-10).

As a result, if the story new release information is not stored (NO in P5-10), the game control section 500a of the player terminal 1 terminates the release story display process.

Further, if the story new release information is stored (YES in P5-10), the game control unit 500a of the player terminal 1 displays the story release display 230 on the display 26 based on the story new release information. At the same time as displaying (P5-11), the new story release information is cleared (deleted) (P5-12), and the release story display processing ends.

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 obvious that a person skilled in the art can conceive of various modifications or modifications within the scope of the claims, and it is understood that these also belong to the technical scope of the present invention. be done.

The game features and the processing in the player terminal 1 and the server 100 described in the above embodiment are merely examples. In any case, the information processing program may cause the computer (either or both of the player terminal 1 and the server 100 in the embodiment) to perform the following processes.

(Processing to be executed by a computer)
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 in which the order of event quests "1-1" to "1-15" is set) A predetermined operation of the player (in the embodiment, as an example, an operation of the event quest operation section 173 of the event quest screen 172, an operation of the challenge operation section 75 of the event quest selection screen 174, an OK operation section 179 of the auto progression party selection screen 177 operation, operation of the battle start operation unit 182 of the auto progress setting screen 180, and operation of the next operation unit 192 of the auto progress setting screen 190 when the stamina is insufficient). as, P2).
At least a predetermined operation (in the embodiment, as an example, operation of the event quest operation unit 173 of the event quest screen 172, operation of the challenge operation unit 75 of the event quest selection screen 174, operation of the OK operation unit 179 of the auto progress party selection screen 177 operation, operation of the battle start operation unit 182 of the auto progress setting screen 180, operation of the next operation unit 192 of the auto progress setting screen 190 when stamina is insufficient), the selected predetermined game is executed based on the input. (P2, P3, P4 as an example in the embodiment).
A predetermined trigger (in the embodiment, as an example, the challenge operation unit 75 is operated (tapped) while the check box in FIG. 7B is checked, and then the battle start operation unit 182 in FIG. 8B is performed), an auto mode (in the embodiment, as an example, auto progress) is executed in which predetermined games are sequentially executed in order without requiring a predetermined operation by the player. Processing (P3, P4 as an example in the embodiment).
A predetermined end condition (in the embodiment, as an example, when the player wins a predetermined battle game when the auto-progress stop function when the story is released is set to be valid, and the story that the player can view becomes or when the OK operation section 242 of the auto progress/stop display 240 is operated (tapped), the process of stopping the auto mode (in the embodiment, as an example, P4).

Further, in the above-described embodiment, when the auto-progress function is set to be valid as a predetermined end condition, and when the auto-progress stop function when the story is released is set to be valid, a predetermined , and the number of stories that the player can browse increases, or the OK operation section 242 of the auto-progress stop display 240 is operated (tapped), but the case is limited to this. isn't it. For example, when the auto-progress function is enabled and the auto-progress stop function is enabled when the story is released, and when the auto-progress stop function is disabled when the story is released A termination condition that satisfies both may be provided.

For example, when the player wins a predetermined battle game, when a predetermined mini-game is released, when the story release auto progress stop function is enabled, and when the story release The auto-advancement may be stopped in both cases when the auto-advancement stop function is disabled. In this case, when the automatic screen transition in the second result screen 85 is performed, the screen may be transitioned to the above-described predetermined mini-game execution screen. Alternatively, the event quest screen 172 may notify the release of the above-described predetermined mini-game.

Also, "When the auto-progress function is enabled and the auto-progress stop function when the story is released is enabled, the player wins a predetermined battle game, and the player can view "When the story increases", "When the OK operation unit 242 of the auto progress stop display 240 is operated (tapped)", and "When the player wins a predetermined predetermined battle game, a predetermined mini "When the game is released" may be provided as end conditions, or any one condition or any two conditions may be set as end conditions. It should be noted that both the release of the mini-game that satisfies the termination condition and the release of the mini-game that does not satisfy the termination condition may be provided.

In the above embodiment, as an example of the game, a so-called battle game in which a friendly character battles an enemy character is provided, but the specific content and game genre of the game are not limited to the above embodiment. For example, it is applicable to all game genres such as Roll Playing Game, Shooting Game, Puzzle Game, and Rhythm Game.

Moreover, based on at least the execution of the predetermined game, a process (S4, P5 in the embodiment as an example) of increasing the content (in the embodiment as an example a story) that can be browsed by the player is further executed. You may

Further, the process of stopping the auto mode may stop the auto mode being executed when the amount of content that can be viewed by the player increases during the execution of the auto mode (in the embodiment, as an example, P4 ).

In addition, a process (in the embodiment, P2 as an example) of requesting the player to pay for the execution of one predetermined game may be further executed.
In addition, a process (in the embodiment, P2 as an example) of displaying the total price required for a plurality of predetermined games scheduled to be sequentially executed in the auto mode may be further executed.

Also, in the above embodiment, the auto-advancement function is usable in event quests, but it may also be usable in main quests in the above embodiment.

Also, the auto-advance function may be available for other than "1-1" in main quests and event quests. For example, in "1-3" in the main quest or event quest, the auto progression function may be enabled to start the battle game. In this case, for example, when the display of the second result screen 85 of the battle game "1-3" ends, the battle game "1-4" is automatically started, and thereafter, similarly, "1-15" is displayed. Until then, the battle game will be automatically executed. In this case, the game control unit 500a of the player terminal 1 may calculate and display the total consumed stamina from "1-3" to "1-15". That is, the game control unit 500a of the player terminal 1 may calculate the total stamina consumption from the battle game selected by the player to the last battle game scheduled to be executed sequentially thereafter, and display it on the display 26.

Also, in the above embodiment, when the auto-progress function is enabled and the auto-progress stop function is enabled when the story is released, and when the auto-progress function is enabled and the auto-progress stop function is disabled when the story is released, The event quest selection screen 174, the auto progress setting screen 180, the lack of stamina auto progress setting screen 190, and the stamina recovery dialog 200 show the case where the total consumed stamina displayed is the same, but it is not limited to this. do not have. For example, if the auto-progress function is enabled and the auto-progress stop function is enabled when the story is released, the necessary compensation for the battle game until the auto-progress stops based on the story release is displayed as the total consumed stamina. It is also possible to

Further, in the above-described embodiment, the compensation required for the battle game is not limited to stamina, but a predetermined in-game currency, a predetermined in-game ticket, a predetermined item, or the like, as a compensation required for the battle game. may be

In the above embodiment, the battle game screen 80 is displayed on the display 26 both when the auto progress function is valid and when the auto progress function is invalid. 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 .

The information processing program for executing the processes in the above embodiments 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-described embodiment and various modifications 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 (4)

a process of enabling at least one of a plurality of predetermined games whose order is set in advance to be selected by a player's 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 game is sequentially executed based on the order without requiring the predetermined operation by the player based on a predetermined trigger;
a process of increasing content viewable by a player based on at least execution of the predetermined game;
a process of stopping the auto mode when the content increases during execution of the auto mode;
An information processing program that causes a computer to carry out a process of requesting payment from a player in order to execute the predetermined game of 1;
a process of displaying the total price required for a plurality of predetermined games scheduled to be sequentially executed in the auto mode;
2. The information processing program according to claim 1, further causing the computer to perform: An information processing method performed by one or more computers, comprising:
The computer is
a process of enabling at least one of a plurality of predetermined games whose order is set in advance to be selected by a player's 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 game is sequentially executed based on the order without requiring the predetermined operation by the player based on a predetermined trigger;
a process of increasing content viewable by a player based on at least execution of the predetermined game;
a process of stopping the auto mode when the content increases during execution of the auto mode;
Information processing method to carry out An information processing system comprising one or more computers,
The computer is
a process of enabling at least one of a plurality of predetermined games whose order is set in advance to be selected by a player's 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 game is sequentially executed based on the order without requiring the predetermined operation by the player based on a predetermined trigger;
a process of increasing content viewable by a player based on at least execution of the predetermined game;
a process of stopping the auto mode when the content increases during execution of the auto mode;
Information processing system that carries out

Images