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

Abstract

An object of the present invention is to motivate a player to play by improving convenience for the player. The information processing program includes one or more game media, requires setting of formation information that satisfies a minimum condition of a predetermined parameter calculated based on the game content, and exceeds the minimum condition of the predetermined parameter. A process of setting organization information based on a player's operation, a process of progressing the specific content based on the set organization information, and automatically generating organization information for specific contents whose advantage increases as the number increases. Among the automatic organization functions, the first automatic organization function that gives priority to meeting the minimum requirements, and the second automatic organization function that gives priority to meeting the minimum requirements and increasing the degree of advantage, when the player and a process of generating organization information based on the selected automatic organization function. [Selection drawing] Fig. 12

Description

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

Conventionally, for example, as disclosed in Patent Document 1, after a player gives an instruction to execute a game, the game progresses automatically, and after a predetermined period of time has passed, the user is notified of the result of the automatic progress. A game of a genre called an idle game has been proposed.

Japanese Patent No. 6748838

In general, improving the convenience of a player involved in a game tends to motivate the player to play the game.

An object of the present invention is to provide an information processing program, an information processing method, and an information processing system capable of motivating a player to play by improving convenience for the player.

In order to solve the above problems, the information processing program
One or more game media are included, the setting of formation information that satisfies a minimum condition is required for a predetermined parameter calculated based on the game media, and the more the predetermined parameter exceeds the minimum condition, the higher the degree of advantage. a process of setting the organization information for specific content based on a player's operation;
a process of progressing the specific content based on the set organization information;
An automatic organization function that automatically generates the organization information, wherein a first automatic organization function that prioritizes meeting the minimum conditions at a minimum, and a priority that satisfies the minimum conditions and increases the degree of advantage. a process of generating the organization information based on the automatic organization function selected by the player among the second automatic organization functions;
is executed by a computer ,
the specific content includes a first specific content and a second specific content;
In the process of progressing the specific content,
the first specific content and the second specific content can be progressed at the same time;
Overlap between the game media included in the organization information set for the first specific content and the game media included in the organization information set for the second specific content is restricted. be .

a process of setting a preferred game medium based on a player's operation;
is further performed by the computer,
In the process of generating the organization information,
When the organization information is generated based on the first automatic organization function and the second automatic organization function, the organization information may be generated that preferentially includes the priority game media.

A process of permitting the progress of the specific content when the set organization information satisfies the minimum condition, and not permitting the progress of the specific content when the set organization information does not satisfy the minimum condition. of,
may be further performed by a computer.

In the process of progressing the specific content,
The time until the progress of the specific content is terminated may be shortened according to the degree to which the predetermined parameter exceeds the minimum condition.

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
One or more game media are included, the setting of formation information that satisfies a minimum condition is required for a predetermined parameter calculated based on the game media, and the more the predetermined parameter exceeds the minimum condition, the higher the degree of advantage. a process of setting the organization information for specific content based on a player's operation;
a process of progressing the specific content based on the set organization information;
An automatic organization function that automatically generates the organization information, wherein a first automatic organization function that prioritizes meeting the minimum conditions at a minimum, and a priority that satisfies the minimum conditions and increases the degree of advantage. a process of generating the organization information based on the automatic organization function selected by the player among the second automatic organization functions;
carry out
the specific content includes a first specific content and a second specific content;
In the process of progressing the specific content,
the first specific content and the second specific content can be progressed at the same time;
Overlap between the game media included in the organization information set for the first specific content and the game media included in the organization information set for the second specific content is restricted. be .

In order to solve the above problems, the information processing system
The computer is
One or more game media are included, the setting of formation information that satisfies a minimum condition is required for a predetermined parameter calculated based on the game media, and the more the predetermined parameter exceeds the minimum condition, the higher the degree of advantage. a process of setting the organization information for specific content based on a player's operation;
a process of progressing the specific content based on the set organization information;
An automatic organization function that automatically generates the organization information, wherein a first automatic organization function that prioritizes meeting the minimum conditions at a minimum, and a priority that satisfies the minimum conditions and increases the degree of advantage. a process of generating the organization information based on the automatic organization function selected by the player among the second automatic organization functions;
carry out
the specific content includes a first specific content and a second specific content;
In the process of progressing the specific content,
the first specific content and the second specific content can be progressed at the same time;
Overlap between the game media included in the organization information set for the first specific content and the game media included in the organization information set for the second specific content is restricted. be .

According to the present invention, it is possible to motivate the player to play by improving convenience for 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 the expedition top screen. FIG. 7B is a diagram illustrating an example of a dispatch destination selection screen. FIG. 8A is a diagram illustrating an example of a menu screen. FIG. 8B is a first diagram illustrating an example of a notification setting screen. FIG. 8C is a second diagram illustrating an example of the notification setting screen. FIG. 9A is a diagram illustrating an example of an expedition completion notification. FIG. 9B is a first diagram illustrating an example of the priority setting screen. FIG. 9C is a second diagram illustrating an example of the priority setting screen. FIG. 10A is a first diagram illustrating an example of the priority change first screen. FIG. 10B is a first diagram illustrating an example of the second priority change screen. FIG. 11A is a second diagram illustrating an example of the priority change second screen. FIG. 11B is a second diagram illustrating an example of the priority change first screen. FIG. 12A is a first diagram illustrating an example of an automatic organization setting screen. FIG. 12B is a second diagram illustrating an example of the automatic organization setting screen. FIG. 13A is a first diagram illustrating an example of the organization screen. FIG. 13B is a second diagram illustrating an example of the organization screen. FIG. 13C is a third diagram illustrating an example of the organization screen. FIG. 14A is a diagram illustrating an example of the organization screen when using the first automatic organization function. FIG. 14B is a diagram illustrating an example of the organization screen when using the second automatic organization function. FIG. 15A is a fourth diagram illustrating an example of the organization screen. FIG. 15B is a first diagram illustrating an example of the time reduction screen. FIG. 15C is a fifth diagram illustrating an example of the organization screen. FIG. 16A is a diagram illustrating an example of a confirmation screen. FIG. 16B is a diagram illustrating an example of an expedition start effect screen. FIG. 16C is a first diagram illustrating an example of the time reduction effect screen. FIG. 17A is a diagram illustrating an example of a dispatch destination selection screen during execution of an expedition game. FIG. 17B is a diagram illustrating an example of the time reduction screen during execution of the expedition game. FIG. 18A is a diagram illustrating an example of a confirmation screen for confirming with the player that the shortening function will be used during execution of the expedition game. FIG. 18B is a diagram illustrating an example of a dispatch destination selection screen displayed when the shortening function is used during execution of the expedition game. FIG. 19A is a diagram illustrating an example of a withdrawal confirmation screen. FIG. 19B is a diagram illustrating an example of an expedition withdrawal screen. FIG. 20A is a diagram for explaining an example of a dispatch destination selection screen when an expedition is completed. FIG. 20B is a diagram illustrating an example of an expedition completion screen. FIG. 21 is a diagram illustrating an example of a redispatch screen. FIG. 22A is a diagram illustrating an example of the expedition top screen when the expedition is completed. FIG. 22B is a diagram illustrating an example of a collective expedition completion screen. FIG. 23 is a diagram illustrating an example of a redispatch screen. FIG. 24A is a first diagram collectively illustrating an example of an expedition screen. FIG. 24B is a second diagram collectively illustrating an example of the expedition screen. FIG. 25 is a diagram illustrating an example of an expedition confirmation screen collectively. FIG. 26 is a diagram for explaining the configuration of a memory in a player terminal and functions as a computer. FIG. 27 is a diagram for explaining the configuration of a memory in a server and functions as a computer. FIG. 28 is a sequence diagram illustrating basic processing of the player terminal and server. FIG. 29 is a first flowchart for explaining setting processing in the player terminal. FIG. 30 is a second flowchart for explaining setting processing in the player terminal. FIG. 31 is a first flowchart for explaining individual dispatch processing in the player terminal. FIG. 32 is a second flowchart for explaining individual dispatch processing in the player terminal. FIG. 33 is a third flowchart for explaining individual dispatch processing in the player terminal. FIG. 34 is a flowchart for explaining re-dispatch processing in the player terminal. FIG. 35 is a first flow chart for explaining the collective expedition processing in the player terminal. FIG. 36 is a second flow chart for explaining the expedition process collectively in the player terminal. FIG. 37 is the third flow chart for explaining the expedition process collectively in the player terminal. FIG. 38 is a flowchart for explaining withdrawal processing in the player terminal. FIG. 39 is a flow chart for explaining the post-trip start time reduction processing in the player terminal. FIG. 40 is a flowchart for explaining expedition game progress processing in the server. FIG. 41 is a flowchart for explaining remuneration management processing in the server. FIG. 42 is a flowchart for explaining the expedition completion process in 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, an 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 ROM (Read Only Memory) or 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 one or a plurality of ally characters are organized and made to fight against enemy characters. In addition to the above-described battle game, the present embodiment provides a game of a genre called a so-called neglected game (referred to as an "expedition game" in the present embodiment) in which one or a plurality of formed teammates characters are dispatched. be. 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.

In the battle game, the player can form a party by selecting one or a plurality of owned friendly characters. 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.

Also, in the expedition game, the player can select one or a plurality of owned ally characters to form a party. A player can play an expedition game using an organized party. In the expedition game, a "expedition" is carried out in which friendly characters organized in a party are dispatched for a preset required time. Then, when the required time has passed, the expedition game is completed (cleared), and the player can obtain a reward. That is, in order to start the expedition game, it is necessary for the player to operate the player and start the game. On the other hand, the expedition game (specific content) that has been started does not require the player's operation or the start of the game to proceed, and has a game feature in which the game progresses over time.

In the expedition game, the objective is to dispatch a friendly character organized in a party for a predetermined required time and obtain a reward. Although details will be described later, in this embodiment, for example, multiple types of expedition games can be played. Depending on the type of expedition game, the difficulty level differs depending on the required time, party strength conditions, and the like.

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 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 . At least part of the 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. Progress information, battle game clear information, in-game currency information indicating the amount of in-game currency possessed by the player, item information indicating the type and amount of items possessed by the player, expedition game information indicating the progress of the expedition game And so on.

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.

On the other hand, in the present embodiment, the player can play the expedition game without consuming the above stamina. That is, for example, even if the stamina is depleted by playing the battle game, the expedition game can be executed. However, stamina consumption may be required to play the expedition game.

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.

Stars (ranks), experience points, and levels are associated with each other character and stored. 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 strength such as life points, offensive power, and defensive power are set for allied characters based on stars (ranks) and levels. The player can progress the battle game more advantageously as the strength of the ally character increases. Also, each base value set for the ally character increases as the number of stars (rank) increases and as the level increases.

On the teammate character confirmation screen 50, it is possible to equip (set) the equipment such as weapons and armor to the teammate 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 strength 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.

In this embodiment, a special item is provided for increasing the star (rank) of the ally character. The player can increase the stars (rank) of the ally character by consuming a special item corresponding to the ally character whose star (rank) is to be increased on the ally character confirmation screen 50 . Note that the player can acquire special items as a reward when completing (clearing) a battle game or an expedition game, which will be described later.

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 and a character story selection operation section 62 .

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).

Further, 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).

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 games provided are described. Here, five types of 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 expedition selection operation unit 71e labeled "expedition" 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. Further, when the expedition selection operation portion 71e is tapped, an expedition top screen 90 (FIG. 7A), which will be described later, is displayed on the display 26. FIG.

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

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 completed (cleared), stars are obtained according to the number of ally characters whose life points are 0 when the battle game is completed (cleared). For example, three stars are obtained when there is no friendly character whose life point is 0, and two stars are obtained when there is only one friendly character whose life point is 0. , 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 notified that this battle game has not been completed (cleared).

In the main quest, the condition for releasing the main quest is to complete (clear) the previous battle game. For example, in the example of FIG. 5A, by completing (clearing) up to the battle game "1-3", the battle game "1-4" is released. 5” and later) battle games have not yet been released.

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 activated. It is available.

Then, when the battle game ends normally (normally ends), 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.

Note that when the battle game is in the auto-activation state from the start to the end of the battle game and the special move is not manually used by the player, it is in the auto-activation state, otherwise it is in the manual activation 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, an expedition game according to this embodiment will be described. The expedition game according to this embodiment has the following game properties. First, the player selects at least one of dispatch destinations provided in advance. In addition, the player selects one or a plurality of owned ally characters to form a party. Then, the player dispatches the organized party to the selected destination. Then, when the required time set for each destination has passed, the expedition game is completed (cleared), and the player can obtain a reward.

As described above, when the player operates (tap) the expedition selection operation portion 71e of the quest screen 70 (FIG. 4B), the expedition top screen 90 (FIG. 7A) is displayed on the display . FIG. 7A is a diagram illustrating an example of the expedition top screen 90. FIG. In this embodiment, the expedition game is provided with a plurality of hierarchies to which a plurality of dispatch destinations belong. Specifically, four hierarchies of "hierarchy A", "hierarchy B", "hierarchy C", and "hierarchy D" are provided as a plurality of hierarchies. However, the number of layers is not limited to this.

As shown in FIG. 7A, a plurality of expedition layer selection operation sections 91 corresponding to a plurality of layers are displayed in the central portion of the expedition top screen 90 . Specifically, as shown in FIG. 7A, a first expedition layer selection operating section 91a labeled "Layer A", a second expedition layer selection operating section 91b labeled "Layer B", and a "Layer C" and a fourth expedition layer selection operation section 91d labeled "Tier D" are displayed.

When the player operates (tap) any one of the first expedition layer selection operation portion 91a to the fourth expedition layer selection operation portion 91d, a corresponding dispatch destination selection screen 100 (FIG. 7B), which will be described later, is displayed on the display 26. to be displayed.

A menu screen selection operation section 92 for displaying a menu screen 110 (FIG. 8A), which will be described later, is displayed at the top of the expedition top screen 90 .

In addition, at the top of the expedition top screen 90, a collective expedition selection operation section 93 for displaying a collective expedition screen 290 (FIG. 24A), which will be described later, is displayed.

Also, at the bottom of the expedition top screen 90, a collective expedition completion operation section 94 for displaying a collective expedition completion screen 270 (FIG. 22B), which will be described later, is displayed.

As described above, when the player operates (tap) the expedition hierarchy selection operation section 91 of the expedition top screen 90, the corresponding dispatch destination selection screen 100 (FIG. 7B) is displayed on the display . FIG. 7B is a diagram illustrating an example of the dispatch destination selection screen 100. As shown in FIG. Note that FIG. 7B shows the dispatch destination selection screen 100 displayed on the display 26 when the player operates (tap) the first expedition layer selection operating portion 91a of the expedition top screen 90 (FIG. 7A).

In this embodiment, four dispatch destinations, namely, “dispatch destination A-1,” “dispatch destination A-2,” “dispatch destination A-3,” and “dispatch destination A-4,” belong to “hierarchy A.” destination is provided. Similarly, four dispatch destinations are provided for each of “hierarchy B” to “hierarchy D”. However, the number of dispatch destinations belonging to each hierarchy is not limited to this, and the number of dispatch destinations belonging to each hierarchy may be the same or different.

As shown in FIG. 7B, a plurality of dispatch destination selection operation sections 101 corresponding to a plurality of dispatch destinations are displayed in the central portion of the dispatch destination selection screen 100 . Specifically, as shown in FIG. 7B, a first dispatch destination selection operation unit 101a labeled as "dispatch destination A-1" and a second dispatch destination selection operation unit labeled as "dispatch destination A-2" 101b, four operation units are displayed, namely, a third destination selection operation unit 101c labeled "dispatch destination A-3" and a fourth destination selection operation unit 101d labeled "dispatch destination A-4". be done.

In this embodiment, a difficulty level is set in advance for each destination in the expedition game. In this embodiment, three play conditions, ie, the required force, the maximum number of players, and the required time, are set in advance for each dispatch destination.

The required strength indicates the minimum requirement for the strength of the party, that is, the total strength of allied characters organized in the party. That is, when the strength of the party is equal to or greater than the required strength, the party can be dispatched to the destination. On the other hand, if the strength of the party is less than the required strength, the party cannot be dispatched to the destination. That is, it can be said that the higher the required strength, the higher the difficulty.

In other words, when the set organization information (party organization) satisfies the minimum requirements (required strength), the progress of the specific content (expedition game) is permitted, and the set organization information (party organization) is It can be said that progress of the specific content (expedition game) is not permitted unless the minimum requirement (required force) is satisfied.

The required time indicates the time required to complete (clear) the party dispatched to the destination. In this embodiment, the required time is shortened as the strength of the party dispatched to the dispatch destination increases. That is, it is possible to increase the fighting power of the party and shorten the required time by forming a party with friendly characters having relatively high fighting power among possessed friendly characters. However, the conditions for shortening the required time are not limited to the above contents. For example, the time may be shortened depending on the number of participants in the party, the level of allied characters, and the like, in addition to strength. Then, these may be targets of setting on an automatic organization setting screen 160 (Fig. 12A), which will be described later.

In other words, it is requested to set organization information that includes one or more game media (ally characters) and that a predetermined parameter (strength) calculated based on the game media (ally characters) satisfies a minimum condition, and the predetermined parameter Formation information (party formation) is set based on the player's operation for specific content (expedition game), in which the degree of advantage increases (required time is shortened) as (strength) exceeds the minimum requirement. . In addition, it is possible to shorten the time until the progress of the specific content (expedition game) ends according to the degree to which the predetermined parameter (party strength) exceeds the minimum requirement (required strength).

Also, the maximum number indicates the maximum number of allied characters that can be formed into a party to be dispatched to the dispatch destination. It can be said that the lower the maximum number of players, the higher the degree of difficulty. It should be noted that the minimum number of allied characters to be organized into a party to be dispatched to a dispatch destination may be further set as a play condition.

Specifically, for example, as shown in FIG. 7B, for "dispatch destination A-1", the required time is 1 hour and 30 minutes, the maximum number of players is 5, and the required strength is 800,000. is set. Also, for "dispatch destination A-2", the required time is 1 hour and 45 minutes, the maximum number of players is 6, and the required strength is 900,000. Also, for "dispatch destination A-3", the required time is 1 hour and 40 minutes, the maximum number of players is 2, and the required force is 700,000. Further, for "dispatch destination A-4", the required time is set to 4 hours, the maximum number of players is 12, and the required strength is set to 950,000 as play conditions.

When the player operates (tap) any one of the first dispatch destination selection operation unit 101a to the fourth dispatch destination selection operation unit 101d, a party to be dispatched to the dispatch destination of the corresponding type is organized. A formation screen 170 (FIG. 13A), which will be described later, is displayed on the display 26 .

Further, as shown in FIG. 7B, a cancel operation section 102 marked with "cancel" is displayed at the bottom of the dispatch destination selection screen 100. FIG. When the player operates (tap) the cancel operation unit 102, the display of the dispatch destination selection screen 100 ends, and the expedition top screen 90 (FIG. 7A) is displayed on the display 26. FIG.

Further, as described above, when the player operates (tap) the menu screen selection operation section 92 of the expedition top screen 90 (FIG. 7A), the menu screen 110 (FIG. 8A) is displayed on the display 26 . FIG. 8A is a diagram illustrating an example of the menu screen 110. As shown in FIG.

As shown in FIG. 8A, the menu screen 110 displays a notification setting operation section 111 labeled "notification setting". When the player operates (tap) the notification setting operation unit 111, a notification setting screen 120 (FIG. 8B), which will be described later, is displayed.

In addition, as shown in FIG. 8A, the menu screen 110 displays a priority setting operation section 112 labeled "priority setting". When the player operates (tap) the priority setting operation unit 112, a priority setting screen 130 (FIG. 9B), which will be described later, is displayed.

Further, as shown in FIG. 8A, the menu screen 110 displays an automatic knitting setting operation section 113 labeled "automatic knitting setting". When the player operates (tap) the automatic organization setting operation section 113, an automatic organization setting screen 160 (FIG. 12A), which will be described later, is displayed.

In addition, as shown in FIG. 8A, the menu screen 110 displays a close operation section 114 marked with "close". When the player operates (tap) the operation unit 114 to close, the display of the menu screen 110 ends, and the expedition top screen 90 (FIG. 7A) is displayed on the display 26 .

As described above, when the notification setting operation unit 111 is operated (tapped) by the player, the notification setting screen 120 (FIG. 8B) is displayed. FIG. 8B is a first diagram illustrating an example of the notification setting screen 120. FIG. Also, FIG. 8C is a second diagram illustrating an example of the notification setting screen 120 . FIG. 9A is a diagram illustrating an example of an expedition completion notification.

Although details will be described later, in this embodiment, a repeat dispatch function is provided. In the repeat dispatch function, the player can arbitrarily designate the number of times the organized party is to be dispatched to the dispatch destination (hereinafter referred to as the number of dispatches). In other words, for the expedition game (specific content), it is possible to set the number of execution times selected by the player from the predetermined number of times, ie, 1 time and 2 or more times. This makes it possible to improve the convenience of the player.

Further, in this embodiment, when the road trip game is completed (cleared), the player can receive a notification indicating that the road trip game has been completed (cleared) (hereinafter referred to as a road trip completion notification). . Specifically, in the case shown in FIG. 9A, a message M stating "The expedition is complete" is displayed at the top of the home screen 40 . Note that the characters displayed in the expedition completion notification are not limited to these. Also, the screen on which the message M is displayed is not limited to the home screen 40 . That is, while the game application is running, the message M is displayed at the top of the display 26 regardless of the type of screen being displayed.

On the notification setting screen 120 shown in FIGS. 8B and 8C, the player can arbitrarily set the execution trigger of the expedition completion notification. In other words, it is possible to set the execution trigger of the notification suggesting that the expedition game (specific content) has finished progressing based on the player's operation.

Specifically, regarding the execution trigger of the expedition completion notification, regardless of the number of dispatches designated by the player, the execution trigger of the expedition completion notification is the completion of one expedition game (hereinafter referred to as the first execution trigger). can be set as

In addition, regarding the execution trigger of the expedition completion notification, the player can set the fact that all the expedition games for the designated number of dispatches have been completed as the execution trigger of the expedition completion notification (hereinafter referred to as the second execution trigger).

In other words, it is possible to set the execution opportunity (second execution opportunity) to be the case where the expedition game (specific content) has completed the set number of executions. In addition, when the second execution opportunity is set and the specified number of dispatches is 1, an expedition completion notification ( notification) is executed. In addition, when the second execution opportunity is set and the specified number of dispatches is a plurality of times (for example, 3 times), a plurality of times (for example, 3 times) of the expedition game (specific content) An expedition completion notification (notification) is executed based on the completion of progress. In addition, when the second execution opportunity is set and the specified number of dispatches is multiple times (for example, 3 times), the expedition that is less than the specified number of dispatches (for example, 1 or 2 times) The expedition completion notification (notification) is not executed based on the completion of the progress of the game (specific content).

As shown in FIGS. 8B and 8C, in the central part of the notification setting screen 120, a first execution trigger selection section 121 corresponding to the first execution trigger and a second execution trigger selection section corresponding to the second execution trigger 122 is displayed. When the player operates (tap) the first execution trigger selection section 121, the first execution trigger selection section 121 is highlighted as shown in FIG. 8B. When the player operates (tap) the second execution trigger selection section 122, the second execution trigger selection section 122 is highlighted as shown in FIG. 8C. FIGS. 8B and 8C show a case where a black circle is displayed as highlighting in the first execution trigger selection section 121 or the second execution trigger selection section 122 according to the player's operation (tap). However, the content of highlighting is not limited to this. For example, as highlighting, a check mark may be displayed in the first execution trigger selection section 121 or the second execution trigger selection section 122 according to the player's operation (tap).

Also, as shown in FIGS. 8B and 8C , a setting operation section 123 labeled “setting” is displayed at the bottom of the notification setting screen 120 . When the first execution trigger selection section 121 is highlighted (FIG. 8B) and the player operates (tap) the setting operation section 123, the first execution trigger is set as the execution trigger for the expedition completion notification. be done. Further, when the second execution trigger selection section 122 is highlighted (FIG. 8C), when the player operates (tap) the setting operation section 123, the second execution trigger is set as the execution trigger for the expedition completion notification. It will be done.

Further, as shown in FIGS. 8B and 8C , a cancel operation section 124 marked with “cancel” is displayed at the bottom of the notification setting screen 120 . When the player operates (tap) the cancel operation unit 124 , the display of the notification setting screen 120 ends, and the menu screen 110 ( FIG. 8A ) is displayed on the display 26 .

Note that FIG. 9A shows the case where the message M is displayed when the home screen 40 is displayed on the display 26, but the message M is displayed when an execution trigger set by the player is established while the game application is running. It is sufficient if M is displayed.

That is, when the execution trigger set by the player is established while the game application is running, the message M may be displayed at the top of the display 26 regardless of the type of screen being displayed. For example, while the teammate character confirmation screen 50 ( FIG. 3B ) is displayed on the display 26 , the message M is displayed at the top of the teammate character confirmation screen 50 when an execution opportunity set by the player is established. Similarly, a story screen 60 (Fig. 4A), a quest screen 70 (Fig. 4B), a main quest screen 72 (Fig. 5A), a main quest selection screen 74 (Fig. 5B), a party selection screen 77 (Fig. 5C), a battle game screen. 80 (FIG. 6A), first result screen 83 (FIG. 6B), second result screen 85 (FIG. 6C), expedition top screen 90 (FIG. 7A), dispatch destination selection screen 100 (FIG. 7B), menu screen 110 (FIG. 8A), notification setting screen 120 (FIG. 8B), priority setting screen 130 (FIG. 9B), priority change first screen 140 (FIG. 10A), priority change second screen 150 (FIG. 10B), automatic organization setting screen 160 (FIG. 12A), organization screen 170 (FIG. 13A), time reduction screen 180 (FIG. 15B), confirmation screen 190 (FIG. 16A), expedition start effect screen 200 (FIG. 16B), time reduction effect screen 210 (FIG. 16C). , confirmation screen 220 (FIG. 18A), withdrawal confirmation screen 230 (FIG. 19A), expedition withdrawal screen 240 (FIG. 19B), expedition completion screen 250 (FIG. 20B), redispatch screen 260 (FIG. 21), collective expedition completion screen 270. (FIG. 22B), the redeployment screen 280 (FIG. 23), the collective expedition screen 290 (FIG. 24A), and the collective expedition confirmation screen 310 (FIG. 25) are displayed on the display 26, the execution set by the player When the trigger is established, a message M is displayed at the top of each screen being displayed.

Also, when the execution opportunity set by the player is established while the game application is not running, and when the game application is first started after the execution opportunity set by the player is established, the message M is displayed. You can do it.

Also, the message M may be displayed when an execution trigger set by the player is established while the game application is not running. In this case, the message M may be displayed in a predetermined notification area on the display 26 of the player terminal 1. FIG.

Further, as described above, when the player operates (tap) the priority setting operation section 112 of the menu screen 110 (FIG. 8A), the priority setting screen 130 is displayed on the display 26 . FIG. 9B is a first diagram illustrating an example of the priority setting screen 130. FIG. FIG. 9C is a second diagram illustrating an example of the priority setting screen 130. FIG.

As described above, in the present embodiment, special items can be obtained as rewards for completing (clearing) the expedition game. Specifically, among allied characters formed in the party dispatched to the completed (cleared) expedition game, a special item corresponding to the allied character set as a special item drop target that can obtain a special item is given at a predetermined probability. can be obtained with

In addition, in the present embodiment, as a reward for completing (clearing) the expedition game, it is possible to obtain normal items that can also be obtained when completing (clearing) the above-described battle game. In addition, in the present embodiment, as a reward for completing (clearing) the expedition game, special equipment that cannot be obtained by completing (clearing) the above-described battle game can be acquired with a predetermined probability. can. The player can equip (set) a desired ally character with special equipment. This makes it possible to motivate the player to play the expedition game.

It should be noted that an icon image indicating the special equipment obtainable at the dispatch destination may be displayed in association with the corresponding dispatch destination selection operation section 101 . As a result, the player can visually grasp the obtainable special equipment, and convenience can be improved.

In this embodiment, the player can form a party with the maximum number (for example, 5) of friendly characters set for each dispatch destination. A predetermined number of friendly characters (three in the present embodiment) among the friendly characters organized in the party can be set as special item drop targets.

That is, in the present embodiment, the player acquires the special item corresponding to the friendly character who is not set as a special item drop target among the friendly characters formed in the party dispatched to the completed (cleared) expedition game. can't However, the probability of obtaining a special item corresponding to a ally character not set as a special item drop target is higher than the probability of obtaining a special item corresponding to a ally character set as a special item drop target. may also be set low.

Further, although the details will be described later, in the present embodiment, an automatic formation function is provided for automatically forming a party to be dispatched to a dispatch destination. On the priority setting screen 130, when using the automatic organization function, the type of one or more friendly characters (hereinafter referred to as priority targets) to be preferentially set as special item drop targets, and their priorities (priority order ) can be set by the player.

As shown in FIGS. 9B and 9C , a list display section 131 is displayed in the center of the priority setting screen 130 . All teammate characters possessed by the player are displayed in the list display portion 131 . By operating (tapping) the friendly characters displayed in the list display portion 131, the player can set desired friendly characters (up to 15 characters in this embodiment) as priority targets. there is

9B and 9C show cases where the levels of each of the teammate characters displayed in the list display section 131 are displayed. However, the strength of each of the ally characters displayed in the list display section 131 may be displayed.

Also, as shown in FIGS. 9B and 9C, at the bottom of the priority setting screen 130, a priority target display section 132 for displaying a list of teammate characters set as priority targets is displayed. When the player operates (tap) an ally character displayed in the list display portion 131, the operated (tapped) ally character is highlighted as shown in FIG. 9C.

FIG. 9C shows a case where a teammate character operated (tapped) by the player is grayed out as highlighting. However, the content of highlighting is not limited to this. For example, as a highlight display, the ally character that is operated (tapped) by the player may be bordered thicker.

Then, the ally characters are displayed left aligned in the priority target display section 132 in the order in which they were operated (tapped). At this time, the priority of the teammate character displayed on the left side of the priority target display section 132 is set to the highest, and the priority of the teammate character displayed on the right side of the priority target display section 132 is set to the lowest.

Further, as shown in FIGS. 9B and 9C , a reset operation section 133 marked with “reset” is displayed in the center of the priority setting screen 130 . When the reset operation unit 133 is operated (tapped) by the player, the teammate character set as the priority target is reset, and the teammate character is highlighted in the list display unit 131 and the priority target display unit 132 shown in FIG. 9C. Allied characters displayed in are hidden.

Further, as shown in FIGS. 9B and 9C, in the lower right portion of the priority setting screen 130, there are a setting operation section 135 labeled "set" and a cancel operation section 136 labeled "cancel". Is displayed.

When the cancel operation unit 136 is operated (tapped) by the player, the content displayed on the priority setting screen 130 immediately before the cancel operation unit 136 is operated (tapped) is discarded. Also, the display of the priority setting screen 130 is finished, and the menu screen 110 (FIG. 8A) is displayed on the display 26 .

Further, when the setting operation unit 135 is operated (tapped) by the player, the priority of the teammate character is set according to the contents displayed on the priority setting screen 130 immediately before the operation (tap). Also, the display of the priority setting screen 130 is finished, and the menu screen 110 (FIG. 8A) is displayed on the display 26 .

In addition, as shown in FIGS. 9B and 9C, a priority change operation section 134 marked with "priority change" is displayed in the center of the priority setting screen 130. FIG. When the player operates (tap) the priority change operation unit 134 , a priority change first screen 140 ( FIG. 10A ), which will be described later, is displayed on the display 26 .

The player performs a predetermined operation on the first priority change screen 140 (FIG. 10A) and the second priority change screen 150 (FIGS. 10B and 11A), which will be described later, to give priority to the priority target ally character. You can change the degree. Specifically, by exchanging the priority of two friendly characters selected by the player (hereinafter referred to as a change-source friendly character and a change-destination friendly character) among the priority friendly characters, Priority can be changed.

FIG. 10A is a first diagram illustrating an example of the priority change first screen 140. FIG. FIG. 10B is a first diagram illustrating an example of the priority change second screen 150. FIG. FIG. 11A is a second diagram illustrating an example of the priority change second screen 150. FIG. FIG. 11B is a second diagram illustrating an example of the priority change first screen 140. FIG.

As shown in FIG. 10A , a priority target display section 141 is displayed in the center of the first priority change screen 140 . In the priority target display section 141, the teammate characters set as priority targets, that is, the teammate characters displayed in the priority target display section 132 are listed in order of priority. Further, as shown in FIG. 10A, in the priority target display section 141, each teammate character set as a priority target is provided with an identification display 141a that enables identification of the priority. FIG. 10A shows a case where a number (“1” to “15”) corresponding to the priority is given as the identification display 141a. That is, the higher the priority, the smaller the numerical value displayed. However, the content of the identification display 141a is not limited to this. For example, a symbol corresponding to priority may be displayed.

In addition, as shown in FIG. 10A, the priority change first screen 140 displays a close operation section 142 marked with "close". When the player operates (tap) the closing operation unit 142 , the priority change first screen 140 disappears and the priority setting screen 130 is displayed on the display 26 .

In addition, as shown in FIG. 10A, at the top of the priority change first screen 140, there is a message "Priority Change" for prompting the player to perform an operation to select the change source teammate character whose priority is to be changed. Please select a character to play." is displayed.

When the player operates (tap) any of the ally characters displayed in the priority target display section 141 of the priority change first screen 140, the operated (tapped) ally character is set as the change source ally character. be done. Further, the display on the display 26 is switched to the priority change second screen 150 shown in FIG. 10B.

As shown in FIG. 10B , the priority change second screen 150 continues to display the priority target display section 141 . As shown in FIG. 10B, in the priority target display portion 141 of the second priority change screen 150, the change source ally character is highlighted. FIG. 10B shows a case of thickening the border of the change source teammate character as a highlight display. However, the content of highlighting is not limited to this. For example, as the highlighting, the display size of the change source ally character may be increased.

In addition, as shown in FIG. 10B, in the upper part of the priority change second screen 150, a "change destination character" prompts the player to perform an operation for selecting a change destination teammate character whose priority is to be changed. Please select." is displayed.

When the player operates (tap) any of the ally characters other than the change source ally character displayed in the priority target display area 141 of the priority change second screen 150, the operated (tapped) ally character is It is set to the change destination ally character. Also, on the display 26, the display of the second priority change screen 150 is updated as shown in FIG. 11A.

Note that FIG. 9C described above shows a case where the maximum number (15) of friendly characters that can be set are set as priority targets. ) may be set as a priority target. Also, in the present embodiment, it is not essential to set a priority friendly character. In other words, the player can choose not to specifically set a priority target ally character.

As shown in FIG. 11A, in the priority target display portion 141 of the second priority change screen 150, both the change source ally character and the change destination ally character are highlighted so as to be identifiable. FIG. 11A shows a case where the border of the change-origin teammate character is thickened and the border of the change-destination teammate character is thickened and displayed with a dotted line as highlighting. However, the content of highlighting is not limited to this. For example, the highlighting may be performed by increasing the display size of the change source ally character and the change destination ally character.

Further, as shown in FIGS. 10B and 11A, a setting operation section 151 marked with "setting" is displayed at the bottom of the second priority change screen 150. FIG. As shown in FIG. 10B, the setting operation section 151 is displayed in an inoperable state before the change destination ally character is set. On the other hand, as shown in FIG. 11A, after the change destination teammate character is set, the setting operation section 151 is displayed in an operable state.

Further, as shown in FIGS. 10B and 11A, a cancel operation section 152 marked with "cancel" is displayed at the bottom of the second priority change screen 150. FIG. When the cancel operation unit 152 is operated (tapped) by the player, the second priority change screen 150 is hidden, and the first priority change screen 140 is displayed on the display 26 .

Further, when the player operates the setting operation unit 151, the priority of the ally character set as the source ally character and the ally character set as the destination ally character are switched. Further, the display 26 is switched to the priority change first screen 140 shown in FIG. The player is notified of the replacement.

As described above, the expedition game has a difficulty level set in advance. In this embodiment, three conditions of required force, maximum number of people, and required time are set in advance as the degree of difficulty for each dispatch destination.

Also, in this embodiment, it is possible to dispatch a party to each of a plurality of dispatch destinations. At this time, the party to be dispatched to each dispatch destination cannot include the same teammate character.

For example, when the purpose is to dispatch parties to many dispatch destinations at the same time, the player distributes friendly characters with relatively high strength to many parties so that the strength of each party meets the minimum necessary strength. should be organized as follows. In this case, it is possible to dispatch the party to many dispatch destinations at the same time, although the required time at each dispatch destination cannot be greatly shortened.

Further, for example, when the purpose is to shorten the required time at the dispatch destination, the player concentrates allied characters with relatively high strength in a small party. As a result, the strength of each party greatly exceeds the necessary strength. In this case, it is possible to shorten the required time at each dispatch destination instead of narrowing down the dispatch destinations to be dispatched at the same time.

As described above, when the player operates (tap) the automatic organization setting operation section 113 of the menu screen 110 (FIG. 8A), the automatic organization setting screen 160 (FIG. 12A) is displayed. FIG. 12A is a first diagram illustrating an example of the automatic organization setting screen 160. FIG. FIG. 12B is a second diagram illustrating an example of the automatic organization setting screen 160. FIG.

As described above, an automatic formation function is provided for automatically forming teammate characters to be dispatched to the destination selected by the player. In this embodiment, a first automatic organization function and a second automatic organization function are provided as automatic organization functions.

The first automatic formation function is a function for automatically forming ally characters by prioritizing that the strength of the party meets the minimum required strength. By using the first automatic organization function, the player can dispatch parties to a relatively large number of dispatch destinations at the same time.

The second automatic formation function is a function for automatically forming ally characters with priority given to increasing the strength of the party as much as possible. By using the second automatic organization function, the player can shorten the required time at the dispatch destination.

In other words, it is an automatic organization function that automatically generates organization information (organization of a party), a first automatic organization function that gives priority to meeting minimum requirements (minimum requirements for party strength), and a minimum The second automatic formation function that prioritizes satisfying the conditions (the party's strength exceeds the required strength) and increasing the degree of advantage (the party's strength exceeds the required strength and shortens the required time at the dispatch destination). Of these functions, it is possible to generate organization information (organization of a party) based on the automatic organization function selected by the player.

On the automatic organization setting screen 160, the player can set whether to use the first automatic organization function or the second automatic organization function as the automatic organization function. As shown in FIGS. 12A and 12B, in the central part of the automatic organization setting screen 160, there are a first automatic organization function selection section 161 corresponding to the first automatic organization function, and a second automatic organization function selection section 161 corresponding to the second automatic organization function. An automatic organization function selection section 162 is displayed. When the player operates (tap) the first automatic organization function selection section 161, the first automatic organization function selection section 161 is highlighted as shown in FIG. 12A. Also, when the player operates (tap) the second automatic organization function selection section 162, the second automatic organization function selection section 162 is highlighted as shown in FIG. 12B. FIGS. 12A and 12B show a case where a black circle is displayed in the first automatic organization function selection section 161 or the second automatic organization function selection section 162 according to the player's operation (tap) as highlighting. However, the content of highlighting is not limited to this. For example, as highlighting, a check mark may be displayed in the first automatic organizing function selection section 161 or the second automatic organizing function selection section 162 according to the player's operation (tapping).

Further, as shown in FIGS. 12A and 12B , a setting operation section 163 marked with “setting” is displayed at the bottom of the automatic knitting setting screen 160 . When the first automatic organization function selection unit 161 is highlighted (FIG. 12A) and the player operates (tap) the setting operation unit 163, the first automatic organization function is set as the automatic organization function. be. Further, when the second automatic organization function selection section 162 is highlighted (FIG. 12B) and the player operates (tap) the setting operation section 163, the second automatic organization function is set as the automatic organization function. The Rukoto. Further, when the player operates (tap) the setting operation section 163, the display of the automatic organization setting screen 160 ends, and the menu screen 110 (FIG. 8A) is displayed on the display 26. FIG.

Further, as described above, when the player operates (tap) any of the dispatch destination selection operation sections 101 of the dispatch destination selection screen 100 (FIG. 7B), the party to be dispatched to the dispatch destination of the corresponding type is organized. A formation screen 170 (FIG. 13A) for performing is displayed on the display 26 .

FIG. 13A is a first diagram illustrating an example of the organization screen 170. FIG. FIG. 13B is a second diagram illustrating an example of the organization screen 170. As shown in FIG. Note that FIG. 13B shows a case where the strength of the party organized by the player is the same as the required strength. FIG. 13C is a third diagram illustrating an example of the organization screen 170. FIG. Note that FIG. 13C shows a case where the strength of the party organized by the player exceeds the required strength.

A case will be described below in which the first dispatch destination selection operation unit 101a corresponding to "dispatch destination A-1" is operated (tapped) and the formation screen 170 is displayed. As described above, for "dispatch destination A-1", the required time is set to 1 hour and 30 minutes, the maximum number of players is 5, and the required force is 800,000.

As shown in FIG. 13A, the formation screen 170 displays a list display portion 171 that displays a list of allied characters that can be formed into a party. By operating (tapping) an ally character displayed in the list display section 171, the player can organize a desired ally character into a party.

FIG. 13A shows a case where the levels of each teammate character displayed in the list display section 171 are displayed. However, the strength of each of the ally characters displayed in the list display section 171 may be displayed.

It should be noted that, as described above, in the present embodiment, it is not possible to duplicate the same ally character at each of a plurality of dispatch destinations. Therefore, if there is an ally character (hereinafter referred to as a non-organizable character) organized in a party that has already been dispatched to another dispatch destination, a non-organizable character 171x is attached to the non-organizable character. . In other words, it is possible to inform the player of characters that cannot be organized by means of the impossible-to-organize display 171x.

Further, as shown in FIG. 13A, the formation screen 170 displays a drop target display portion 172a and a non-drop target display portion 172b. In the drop target display section 172a, ally characters organized as special item drop targets from which special items can be obtained are displayed. Also, in the non-drop target display portion 172b, ally characters organized other than the special item drop target from which the special item can be obtained are displayed.

When the player operates (tap) an ally character displayed in the list display portion 171, the operated (tapped) ally character is highlighted as shown in FIGS. 13B and 13C. FIG. 13B and FIG. 13C show a case where a teammate character operated (tapped) by the player is grayed out as highlighting. However, the content of highlighting is not limited to this. For example, as a highlight display, the ally character that is operated (tapped) by the player may be bordered thicker.

Then, the friendly characters are displayed in the drop target display portion 172a and the non-drop target display portion 172b in the order in which they were operated (tapped), aligned to the left.

In addition, as shown in FIGS. 13B and 13C, the highlighted ally characters in the list display portion 171 are provided with an identification display 171a that makes it possible to identify the order in which they were operated (tapped). FIGS. 13B and 13C show a case where numbers (“1” to “15”) corresponding to the order of operation (tapping) are attached as the identification display 171a. That is, the earlier the operation (tap) is made, the smaller the value of the number displayed. However, the content of the identification display 171a is not limited to this. For example, symbols may be displayed according to the order in which they were operated (tapped).

In addition, the player can remove the operated (tapped) ally character from the currently organized party by again operating (tapping) the ally character in the highlighted list display portion 171 .

The organization screen 170 also displays a required strength display portion 173a. In the required strength display section 173a, the required strength set for the dispatch destination (here, "dispatch destination A-1") is displayed in the denominator, and the strength of the party being formed is displayed in the numerator. Specifically, for example, in the case of FIG. 13B, the strength of the party organized by the player, 800,000, is displayed as the numerator in the required strength display section 173a, and the required strength, 800,000, is displayed in the required strength display section 173a. displayed in the denominator. In the case of FIG. 13C, the strength of the party formed by the player, 1,200,000, is displayed in the numerator of the required strength display section 173a, and the necessary strength, 800,000, is displayed in the denominator of the strength display section 173a.

The organization screen 170 also displays a required time display section 173b. The required time display section 173b displays the required time set for the dispatch destination (here, “dispatch destination A-1”). Specifically, for example, in the case of FIG. 13B, the required time of 1 hour and 30 minutes is displayed in the required time display section 173b. When the required time is shortened according to the strength of the formed party, as shown in FIG. The required time (eg, -30 minutes) is displayed in the required time display section 173b.

The formation screen 170 also displays a maximum number of persons display section 173c. In the maximum number of persons display section 173c, the maximum number of persons set for the dispatch destination (here, "dispatch destination A-1") is displayed in the denominator, and the number of persons in the party being formed is displayed in the numerator. Specifically, for example, before the player organizes allied characters, as shown in FIG. 13A, "0", which is the number of allied characters organized by the player, is displayed in the numerator of the maximum number of persons display section 173c. , "5", which is the maximum number of persons, is displayed in the denominator of the maximum number of persons display section 173c. Further, when the player organizes five teammate characters, as shown in FIGS. 13B and 13C, "5", which is the number of teammate characters organized by the player, is displayed in the numerator of the maximum number display section 173c. , "5", which is the maximum number of persons, is displayed in the denominator of the maximum number of persons display section 173c.

As described above, in the present embodiment, an automatic formation function is provided for automatically forming a party to be dispatched to a dispatch destination. As shown in FIG. 13A, the composition screen 170 displays an automatic composition operation section 174 for using the automatic composition function. When the automatic organization operation unit 174 is operated (tapped) by the player, the type of automatic organization function (first automatic organization function or second Automatic organization function) is used, and the party is automatically organized.

FIG. 14A is a diagram illustrating an example of the organization screen 170 when using the first automatic organization function. When the first automatic organization function is used, as shown in FIG. 14A, among allied characters set as priority targets by the player, three allied characters with high priority are preferentially organized into a party, It is displayed in the drop target display section 172a. In addition, if there is already a party dispatched to another dispatch destination, among the allied characters set as priority targets, the three allied characters with high priority, excluding characters that cannot be formed, will be given priority to the party. is organized into

Furthermore, as shown in FIG. 14A, ally characters not set as priority targets are organized and displayed in the non-drop target display portion 172b so that the strength of the party meets the minimum required strength. In addition, if there is a party that has already been dispatched to another dispatch destination, friendly characters excluding priority targets and non-organizable characters will be organized into the party so that the party's strength meets the minimum required strength. .

In the case shown in FIG. 14A, a party consisting of three friendly characters displayed in the drop target display section 172a and one friendly character displayed in the non-drop target display section 172b is organized.

Specifically, in this embodiment, when the first automatic organization function is used, first, three teammate characters with high priority, excluding non-organizable characters, are preferentially organized into a party. Then, when the total strength of these three ally characters reaches the required strength, only these three ally characters are organized in the party organized by the first automatic organization function.

On the other hand, if the total strength of the three ally characters does not reach the required strength, ally characters not set as priority targets are organized into the party. Specifically, among allied characters that are not set as priority targets and that can be formed, allied characters with greater strength are organized in order until the strength of the party meets the required strength. That is, the total number of allied characters organized into a party using the first automatic organization function is an indefinite value (a value between 3 and the maximum number of characters).

However, it is not limited to this, and when the first automatic organization function is used, ally characters with high priority, excluding characters that cannot be organized, can be organized in order until the strength of the party meets the required strength. good. That is, as a result of organizing allied characters with higher priority in order, excluding non-organizable characters, if one or two characters reach the required strength, only these one or two allied characters are organized into the party. You can do it.

FIG. 14B is a diagram illustrating an example of the organization screen 170 when using the second automatic organization function. When the second automatic organization function is used, as shown in FIG. 14B, among allied characters set as priority targets by the player, three highly prioritized allied characters are preferentially organized into a party, It is displayed in the drop target display section 172a. In addition, if there is already a party dispatched to another dispatch destination, among the allied characters set as priority targets, the three allied characters with high priority, excluding characters that cannot be formed, will be given priority to the party. is organized into

Furthermore, as shown in FIG. 14B, allied characters that are not set as priority targets are organized and displayed in the non-drop target display portion 172b so as to give priority to increasing the strength of the party as much as possible. In addition, if there is a party that has already been dispatched to another dispatch destination, allied characters excluding priority targets and non-organizable characters will be organized into the party so that the party's strength exceeds the required strength. be done.

That is, in the case shown in FIG. 14B, a party consisting of three friendly characters displayed in the drop target display section 172a and two friendly characters displayed in the non-drop target display section 172b is organized.

Specifically, in this embodiment, when the second automatic organization function is used, first, three teammate characters with high priority, excluding non-organizable characters, are preferentially organized into a party. Furthermore, ally characters that are not set as priority targets are organized into the party. Specifically, among allied characters that are not set as priority targets and that can be organized, allied characters with high strength are organized up to the maximum number of allied characters that can be organized. In other words, the party formed by the second automatic formation function has the maximum number of allied characters.

As described above, in the present embodiment, it is not essential to set a priority friendly character. When the first automatic organization function is used when the priority target ally character is not set, the ally character is organized so that the strength of the party meets the minimum required strength. Specifically, for example, among allied characters that can be formed, allied characters with higher strength may be organized in order until the strength of the party satisfies the required strength. In this case, the total number of allied characters organized in the party is an indefinite value. In other words, when the party's strength reaches the required strength at the stage of organizing three friendly characters with high strength among allied characters that can be formed, the party formed by the first automatic formation function has Only these three ally characters are organized.

In addition, when the priority target ally character is not set, when the second automatic organization function is used, the ally character is organized so as to give priority to increasing the strength of the party as much as possible. Specifically, for example, among allied characters that can be organized, allied characters with high strength are organized up to the maximum number of allied characters that can be organized. In other words, the party formed by the second automatic formation function has the maximum number of allied characters.

In addition, as described above, in this embodiment, a repeat dispatch function is provided that allows the player to arbitrarily designate the number of dispatch times for dispatching the formed party to the dispatch destination. FIG. 15A is a fourth diagram illustrating an example of the organization screen 170. FIG. As shown in FIG. 15A, the formation screen 170 displays a repeat dispatch number display section 175, a repeat dispatch number increase operation section 175a, and a repeat dispatch number decrease operation section 175b.

The number of dispatches being set is displayed in the repeat dispatch number display section 175 . When the player operates (tap) the repeat dispatch count increase operation unit 175a, the dispatch count is incremented by one, and the display of the repeat dispatch count display unit 175 is updated. Further, when the player operates (tap) the repeat dispatch count reduction operation section 175b, the dispatch count is decreased by one, and the display of the repeat dispatch count display section 175 is updated. In this embodiment, the minimum number of times of dispatch displayed in the repeated dispatch number display section 175 is one.

When the number of dispatches is set to a plurality of times, as shown in FIG. 15A, the required time displayed in the required time display section 173b is updated according to the set number of dispatches. For example, if the required time for one dispatch is 1 hour and 30 minutes, and the number of dispatches is set to 4, the display is updated to 6 hours as shown in FIG. 15A.

Further, as described above, in the expedition game, the time required for one dispatch is set to be relatively longer than the time required for one battle game. Therefore, in this embodiment, in addition to increasing the strength of the party and shortening the required time, a time shortening function is provided to shorten the required time in the expedition game. That is, in the present embodiment, both shortening the required time by increasing the strength of the party and using the time shortening function can be used at the same time.

As shown in FIG. 15A , a time reduction operation section 176 is displayed on the organization screen 170 . When the player operates (tap) the time reduction operation unit 176 , a time reduction screen 180 to be described later is displayed on the display 26 .

FIG. 15B is a first diagram illustrating an example of the time reduction screen 180. FIG. In this embodiment, as the time reduction function, a first time reduction function is provided in which a predetermined item (time reduction ticket) owned by the player is used to reduce the required time. Specifically, the player can reduce the required time by one hour by consuming one time reduction ticket. Note that a limit may be set on the number of consumable time reduction tickets within a preset period. For example, up to 99 time-saving tickets may be expendable per day. In this case, it is possible to reduce the required time up to 99 hours per day by consuming time reduction tickets.

As shown in FIG. 15B, the time reduction screen 180 displays a reduction number display section 181, a reduction number increase operation section 181a, and a reduction number reduction operation section 181b relating to the first time reduction function.

The reduced number of times display section 181 displays the number of time reduction tickets consumed. When the player operates (tap) the number-of-reduction increase operation section 181a, the number of consumed time-reduction tickets is increased by one, and the display of the number-of-reduction display section 181 is updated. Further, when the player operates (tap) the number-of-reduction reduction operation unit 181b, the number of consumed time-reduction tickets is reduced by one, and the display of the number-of-reduction display unit 181 is updated. Note that in the present embodiment, the minimum value of the consumed number of time reduction tickets displayed in the reduction number display section 181 is zero.

In addition, in this embodiment, as a time reduction function, a second time reduction function is provided in which the required time is reduced by using a predetermined in-game currency (jewel) owned by the player. Specifically, the player can reduce the required time by one hour by consuming a predetermined number of jewels once. Note that the number of jewels required to shorten the time by one hour is not a fixed value, but may be varied. For example, the number of jewels required may be increased as the number of times increases, such as 80 jewels for the first time, 100 jewels for the second time, and 120 jewels for the third time.

Note that a limit may be set on the number of times a predetermined number of jewels are consumed to shorten the required time within a preset period. For example, up to 99 times per day, it may be possible to reduce the required time by consuming a predetermined number of jewels. In this case, it is possible to shorten the required time up to 99 hours per day by consuming jewels.

As shown in FIG. 15B, the time reduction screen 180 displays a reduction number display section 182, a reduction number increase operation section 182a, and a reduction number reduction operation section 182b relating to the second time reduction function.

The shortened number display section 182 displays the number of times a predetermined number of jewels have been consumed. When the player operates (tap) the number-of-shortenings increase operation section 182a, the number of consumptions of the predetermined number of jewels is increased by one, and the display of the number-of-savings display section 182 is updated. Further, when the player operates (tap) the reduction number reduction operation section 182b, the consumption number of the predetermined number of jewels is reduced by one, and the display of the reduction number display section 182 is updated. Note that in the present embodiment, the number of consumptions of the predetermined number of jewels displayed in the reduction number display section 182 is zero.

A required time display portion 183 is also displayed on the time reduction screen 180 . As shown in FIG. 15B, when the player inputs to consume two time reduction tickets and consume a predetermined number of jewels twice, the required time display section 183 displays the required time before reduction (for example, , 6 hours), the required time after reduction (eg, 2 hours), and the time reduced from the required time before reduction (eg, -4 hours) are displayed.

In addition, as shown in FIG. 15B, the time reduction screen 180 displays a setting operation section 184 labeled "SET" and a cancel operation section 185 labeled "CANCEL".

Further, when the player operates (tap) the cancel operation portion 185 of the time reduction screen 180, the contents displayed on the time reduction screen 180 immediately before the operation (tap) are discarded. Also, the display of the time reduction screen 180 ends, and the organization screen 170 (FIG. 15A) immediately before the time reduction operation unit 176 is operated (tapped) is displayed on the display 26 .

Further, when the setting operation unit 184 is operated (tapped) by the player, the time reduction function is set with the contents displayed on the time reduction screen 180 immediately before the operation (tap). Also, the display of the time reduction screen 180 ends, and the organization screen 170 (FIG. 15C) is displayed on the display 26 .

FIG. 15C is a fifth diagram illustrating an example of the organization screen 170. FIG. FIG. 15C shows the organization screen 170 displayed on the display 26 when the player operates (tap) the setting operation section 184 of the time reduction screen 180 shown in FIG. 15B. As shown in FIG. 15C, the required time display section 173b of the organization screen 170 displays the required time before shortening (for example, 6 hours) and (eg, 2 hours) and the time reduced from the required time before reduction (eg, -4 hours) are displayed.

In addition, as shown in FIG. 15C, the organization screen 170 displays a dispatch operation section 177 marked with "dispatch" and a cancel operation section 178 marked with "cancel".

When the player operates (tap) the cancel operation section 178, the contents displayed on the formation screen 170 immediately before the operation (tap) are discarded. Also, the display of the organization screen 170 is ended, and the dispatch destination selection screen 100 (FIG. 7B) is displayed on the display 26 .

Further, when the strength of the party falls below the required strength, as shown in FIG. 13A, the dispatch operation section 177 is displayed in an inoperable state on the formation screen 170 . On the other hand, when the strength of the party is greater than or equal to the required strength, the dispatch operation section 177 is operable on the formation screen 170 as shown in FIGS. is displayed.

As shown in FIG. 15C, when the use of the time reduction function is set and the player operates (tap) the dispatch operation unit 177 that is operable on the organization screen 170, a confirmation screen 190 (FIG. 16A) is displayed. displayed on the display 26. In addition, when the use of the time reduction function is not set, when the player operates (tap) the dispatch operation unit 177 in an operable state on the formation screen 170, a confirmation screen 190 (FIG. 16A) on the display 26 is displayed. No display is performed, and an expedition start effect screen 200 (FIG. 16B), which will be described later, is displayed on the display 26 for a predetermined period of time to notify the start of the expedition game.

FIG. 16A is a diagram illustrating an example of a confirmation screen 190. FIG. As shown in FIG. 16A, on the confirmation screen 190, the player is notified that time reduction tickets and jewels are consumed by using the time reduction function.

In the case of FIG. 16A, the required time required for one dispatch to "dispatch destination A-1" is 1 hour and 30 minutes, and the number of dispatches is set to 4, so the total required time is 6 hours. is displayed. Then, it is displayed that the expedition time is shortened by 4 hours by using the time shortening function. When the expedition game is started under this condition, the first two dispatches are immediately completed (cleared) by the time reduction function. Then, the third dispatch is shortened by one hour, and the remaining required time is 30 minutes. Moreover, the required time for the fourth dispatch is 1 hour and 30 minutes without shortening the time. That is, when the time shortening function is used, the time is shortened in order from the shortest number of dispatches among the repeatedly executed dispatches.

Further, as shown in FIG. 16A, the confirmation screen 190 displays an OK operation section 191 labeled "OK" and a cancel operation section 192 labeled "Cancel". When 192 is operated (tapped) by the player, the display of the confirmation screen 190 ends, and the organization screen 170 (FIG. 15C) immediately before the dispatch operation section 177 is operated (tapped) is displayed on the display 26 .

Further, when the player operates (tap) the OK operation unit 191, the expedition game is started. Then, an expedition start effect screen 200 (FIG. 16B), which will be described later, is displayed on the display 26 for a predetermined period of time to notify the start of the expedition game.

FIG. 16B is a diagram illustrating an example of an expedition start effect screen 200. As shown in FIG. As shown in FIG. 16B, on the road trip start effect screen 200, a predetermined effect image is displayed for a predetermined time (for example, 3 seconds) to inform the player that the road trip game has started. The expedition start effect screen 200 displays teammate characters dispatched to the expedition. Specifically, for example, all the friendly characters organized in the party, or a predetermined number of friendly characters out of the friendly characters organized in the party, are displayed on the expedition start effect screen 200 .

After a predetermined time (for example, 3 seconds) has passed, the display of the expedition start effect screen 200 on the display 26 ends. When the use of the time reduction function is set for the expedition game that has started, a time reduction effect screen 210 shown in FIG. 16C, which will be described later, is displayed on the display 26 for a predetermined period of time. Note that if use of the time reduction function is not set for the started expedition game, a dispatch destination selection screen 100 shown in FIG. 17A to be described later is displayed on the display .

FIG. 16C is a diagram illustrating an example of the time reduction effect screen 210. As shown in FIG. As shown in FIG. 16C, on the time reduction effect screen 210, a predetermined effect image for informing the player that the time reduction function has been used for the expedition game that has started is displayed for a predetermined time (for example, 3 seconds). displayed.

After a predetermined time (for example, 3 seconds) has passed, the display of the time reduction effect screen 210 on the display 26 ends. Then, a dispatch destination selection screen 100 shown in FIG. 17A, which will be described later, is displayed on the display 26 .

FIG. 17A is a diagram illustrating an example of the dispatch destination selection screen 100 during execution of the expedition game. FIG. 17B is a diagram showing an example of the time reduction screen 180 during execution of the expedition game. As shown in FIG. 17A, on the dispatch destination selection screen 100 during execution of the expedition game, an expedition in progress display 103 is displayed below the dispatch destination selection operation section 101 corresponding to the dispatch destination during execution of the expedition game.

Further, as shown in FIG. 17A, on the dispatch destination selection screen 100 during execution of the expedition game, a representative character 100a is displayed in the dispatch destination selection operation section 101 corresponding to the dispatch destination during execution of the expedition game. In this embodiment, when a party to be dispatched to a dispatch destination is organized as the representative character 100a, the formation screen 170 displays the D ally character. However, the present invention is not limited to this, and when a party to be dispatched to a dispatch destination is organized, the representative character 100a may be the ally character with the highest strength among the organized ally characters.

FIG. 17A shows a case where a party is dispatched to "dispatch destination A-1" and an expedition game is being executed. In this case, an expedition in progress display 103 is displayed at the bottom of the first dispatch destination selection operation section 101a.

As shown in FIG. 17A, the expedition in progress display 103 displays the remaining time until the "dispatch destination A-1" in which the expedition game is being executed is completed (cleared). Here, the case where the remaining time is displayed as 2 hours is shown.

In addition, as shown in FIG. 17A, the expedition display 103 displays a time reduction operation section 104 marked with "time reduction" and a withdrawal operation section 105 marked with "withdrawal". As described above, in this embodiment, when dispatching a party to a dispatch destination, the player can use the time reduction function to reduce the remaining time required. In this embodiment, the time reduction function can be used even after the expedition game has started. When the player taps the time reduction operation unit 104, a time reduction screen 180 (FIG. 17B) is displayed on the display 26. FIG. The time reduction screen 180 of FIG. 17B has the same functions as the time reduction screen 180 of FIG. 15B described above.

That is, as shown in FIG. 17B , the time reduction screen 180 displays a first time reduction function that uses the time reduction ticket owned by the player to reduce the remaining time required for the expedition game after the start of execution. A reduction number display section 181, a reduction number increase operation section 181a, and a reduction number reduction operation section 181b are displayed.

The reduced number of times display section 181 displays the number of time reduction tickets consumed. When the player operates (tap) the number-of-reduction increase operation section 181a, the number of consumed time-reduction tickets is increased by one, and the display of the number-of-reduction display section 181 is updated. Further, when the player operates (tap) the number-of-reduction reduction operation unit 181b, the number of consumed time-reduction tickets is reduced by one, and the display of the number-of-reduction display unit 181 is updated.

Further, as shown in FIG. 17B, the time reduction screen 180 displays the number of reductions related to the second time reduction function that uses the jewels owned by the player to reduce the remaining time required for the expedition game after the start of execution. A display section 182, a reduction number increase operation section 182a, and a reduction number reduction operation section 182b are displayed.

The shortened number display section 182 displays the number of times a predetermined number of jewels have been consumed. When the player operates (tap) the number-of-shortenings increase operation section 182a, the number of consumptions of the predetermined number of jewels is increased by one, and the display of the number-of-savings display section 182 is updated. Further, when the player operates (tap) the reduction number reduction operation section 182b, the consumption number of the predetermined number of jewels is reduced by one, and the display of the reduction number display section 182 is updated.

A required time display portion 183 is also displayed on the time reduction screen 180 . As shown in FIG. 17B, when the player inputs that one time reduction ticket is consumed and a predetermined number of jewels are not consumed, the required time display section 183 displays the remaining required time before reduction ( For example, 2 hours), the remaining required time after shortening (eg, 1 hour), and the time shortened from the remaining required time before shortening (eg, −1 hour) are displayed.

In addition, as shown in FIG. 17B, the time reduction screen 180 displays a shortening operation section 184a marked with "shorten" and a cancel operation section 185 marked with "cancel".

Further, when the player operates (tap) the cancel operation portion 185 of the time reduction screen 180, the contents displayed on the time reduction screen 180 immediately before the operation (tap) are discarded. Also, the display of the time reduction screen 180 ends, and the dispatch destination selection screen 100 (FIG. 17A) is displayed on the display 26 .

Also, when the shortening operation unit 184a is operated (tapped) by the player, the content displayed on the time shortening screen 180 immediately before the operation (tapping) is used to confirm with the player that the time shortening function will be used. confirmation screen 220 (FIG. 18A) is displayed. FIG. 18A is a diagram illustrating an example of a confirmation screen 220 for confirming with the player that the shortening function will be used during execution of the expedition game.

As shown in FIG. 18A, on the confirmation screen 220, the player is notified that time reduction tickets and jewels are consumed by using the time reduction function.

In addition, as shown in FIG. 18A, the confirmation screen 220 displays a shortened operation section 221 marked with "Shortcut" and a canceled operation section 222 marked with "Cancel". When 222 is operated (tapped) by the player, display of the confirmation screen 190 ends, and the time shortening screen 180 (FIG. 17B) immediately before the shortening operation section 184a is operated (tapped) is displayed on the display 26 .

When the player operates (tap) the shortening operation unit 221, the shortening function is used, and the time shortening effect screen 210 shown in FIG. 16C is displayed on the display 26 for a predetermined time. When the predetermined time has passed, the display of the time reduction effect screen 210 on the display 26 ends. Then, a dispatch destination selection screen 100 shown in FIG. 18B, which will be described later, is displayed on the display 26 .

FIG. 18B is a diagram illustrating an example of the dispatch destination selection screen 100 displayed when the shortening function is used during execution of the expedition game. As shown in FIG. 18B, the expedition in progress display 103 of the dispatch destination selection screen 100 displays the remaining time until the "dispatch destination A-1" in which the expedition game is being executed is completed (cleared). Here, a case where the remaining time is shortened by one hour by the shortening function and the remaining time is displayed as one hour is shown.

Also, as described above, in this embodiment, it is not possible to organize the same teammate character redundantly at each of a plurality of dispatch destinations. That is, when a predetermined ally character is dispatched to the expedition game being executed, the predetermined ally character cannot be dispatched to another dispatch destination. Therefore, in this embodiment, the player is provided with a withdrawal function that allows the player to withdraw the party from the expedition game that is being executed and stop the expedition game that is being executed. By using the withdrawal function, it becomes possible to dispatch a predetermined friend character desired by the player to another dispatch destination.

As shown in FIG. 18B, the expedition in progress display 103 of the dispatch destination selection screen 100 displays a withdrawal operation section 105 labeled "withdrawal". When the player operates (tap) the withdrawal operation unit 105, a withdrawal confirmation screen 230 (FIG. 19A) for confirming the use of the withdrawal function by the player is displayed on the display .

FIG. 19A is a diagram illustrating an example of a withdrawal confirmation screen 230. FIG. As shown in FIG. 19A, on the withdrawal confirmation screen 230, when the withdrawal function is used, rewards for expedition games that have not been completed (cleared) cannot be obtained, and the remaining time of the required time is reset. The player is notified that the time reduction tickets and jewels used for the event will not be returned. It should be noted that when the above-mentioned repeated dispatch function is used and multiple dispatches to the dispatch destination are set, and the above-mentioned withdrawal function is used, the player can It is possible to receive rewards for expedition games that have already been completed (cleared).

As shown in FIG. 19A, the withdrawal confirmation screen 230 displays a cancel operation section 231 labeled "cancel" and an OK operation section 232 labeled "OK". When the player operates (tap) the cancel operation unit 231, the display of the withdrawal confirmation screen 230 ends without using the withdrawal function. Then, the dispatch destination selection screen 100 (FIG. 18B) is displayed on the display 26 again.

Further, when the player operates (tap) the OK operation section 232, the withdrawal function is used and the expedition withdrawal screen 240 (FIG. 19B) is displayed on the display 26. FIG.

FIG. 19B is a diagram illustrating an example of an expedition withdrawal screen 240. As shown in FIG. As shown in FIG. 19B, on the expedition withdrawal screen 240, the player is notified that the withdrawal has been made from the dispatch destination of the type corresponding to the withdrawal operation section 105 (FIG. 18B) operated by the player. In FIG. 19B, the player is informed that the player has withdrawn from "dispatch destination A-1".

Further, as shown in FIG. 19B, the expedition withdrawal screen 240 displays a close operation section 241 marked with "close". When the player operates (tap) the operation unit 241 to close, the display of the expedition withdrawal screen 240 ends, and the dispatch destination selection screen 100 (FIG. 7B) is displayed on the display 26 . In addition, on the dispatch destination selection screen 100 displayed at this time, the expedition display 103 (FIG. 17A) corresponding to the dispatch destination that has withdrawn is not displayed.

The expedition game is completed (cleared) when the required time elapses without using the withdrawal function. FIG. 20A is a diagram illustrating an example of the dispatch destination selection screen 100 when the tour is completed. FIG. 20A shows a case where "dispatch destination A-1" is completed (cleared).

As shown in FIG. 20A, on the dispatch destination selection screen 100, an expedition completion display 106 is displayed at the bottom of the dispatch destination selection operation section 101 corresponding to the dispatch destination that has been completed (cleared). Further, as shown in FIG. 20A, the expedition completion display 106 displays a result confirmation operation section 107 labeled "result confirmation". When the player operates (tap) the result confirmation operation unit 107, an expedition completion screen 250 (FIG. 20B) is displayed on the display .

FIG. 20B is a diagram illustrating an example of an expedition completion screen 250. As shown in FIG. As shown in FIG. 20B, on the expedition completion screen 250, a list of rewards obtained at dispatch destinations of a type corresponding to the result confirmation operation section 107 (FIG. 20A) operated (tapped) by the player is displayed. Also, when the expedition completion screen 250 is displayed, the player can complete receiving the reward obtained at the dispatch destination. FIG. 20B shows a case where a list of rewards obtained by completing (clearing) "dispatch destination A-1" is displayed.

In addition, as shown in FIG. 20B, the expedition completion screen 250 displays a non-redeployment operation unit 251 labeled "not redeployed" and a redeployment operation unit 252 labeled "redeployment". be done. When the player taps the non-redispatch operation unit 251, the display of the expedition completion screen 250 ends, and the dispatch destination selection screen 100 (FIG. 7B) is displayed on the display 26. FIG. That is, since the player has received the reward obtained by completing (clearing) "dispatch destination A-1", the expedition completion display 106 (FIG. 20A) is hidden.

Further, when the player operates (tap) the redispatch operation unit 252, a redispatch screen 260 (FIG. 21) for redispatching the same party to the same dispatch destination is displayed on the display 26. FIG.

FIG. 21 is a diagram illustrating an example of the redispatch screen 260. As shown in FIG. As shown in FIG. 21 , a dispatch destination display section 261 is displayed on the redispatch screen 260 . The dispatch destination display section 261 displays the dispatch destination type (here, "dispatch destination A-1") and the play conditions (required strength, maximum number of players, required time) corresponding to the dispatch destination type.

As shown in FIG. 21 , a party display section 262 is displayed in the dispatch destination display section 261 . The party display portion 262 displays friendly characters of the same composition as the party dispatched to the dispatch destination last time. It should be noted that the party display section 262 may display at least a portion of all teammate characters forming a party.

Also, in the present embodiment, a repeat dispatch function can be used on the re-dispatch screen 260 . In this embodiment, the re-dispatch screen 260 shows a case where the repeat dispatch function can be used, but the time reduction function cannot be used. However, the present invention is not limited to this, and both the repeat dispatch function and the time reduction function may be enabled on the re-dispatch screen 260 .

As shown in FIG. 21, the dispatch destination display section 261 displays a repeat dispatch number display section 264, a repeat dispatch number increase operation section 264a, and a repeat dispatch number decrease operation section 264b.

The number of dispatches being set is displayed in the repeat dispatch number display section 264 . When the player operates (tap) the repeat dispatch count increase operation unit 264a, the dispatch count is incremented by one, and the display of the repeat dispatch count display unit 264 is updated. Further, when the player operates (tap) the repeat dispatch count reduction operation section 264b, the dispatch count is decreased by one, and the display of the repeat dispatch count display section 264 is updated. In this embodiment, the minimum number of times of dispatch displayed in the repeated dispatch number display section 264 is one.

Further, as shown in FIG. 21, the redispatch screen 260 displays a cancel operation section 265 labeled "cancel" and a dispatch operation section 266 labeled "dispatch". When the player operates (tap) the cancel operation unit 265, the contents displayed on the redispatch screen 260 immediately before the operation (tap) are discarded. Further, the display of the redispatch screen 260 ends, and the expedition completion screen 250 (FIG. 20B) immediately before the redispatch operation unit 252 (FIG. 20B) is operated (tapped) is displayed on the display 26 .

Further, when the dispatch operation unit 266 is operated (tapped) by the player, the expedition game is started. Then, the expedition start effect screen 200 (FIG. 16B) is displayed on the display 26 for a predetermined period of time to notify the start of the expedition game. After a predetermined period of time has passed, the display of the expedition start effect screen 200 (FIG. 16B) on the display 26 ends, and the dispatch destination selection screen 100 (FIG. 17A) is displayed on the display 26 .

FIG. 22A is a diagram illustrating an example of the expedition top screen 90 when the expedition is completed. As shown in FIG. 22A, when there is an expedition game for which the receipt of the reward has not been completed or an expedition game in progress, the representative character 100a is displayed. Note that the expedition top screen 90 may display an operation unit for displaying a list of parties formed for the expedition game for which the receipt of the reward has not been completed or for the expedition game in progress. Also, from this party list display, it may be possible to check the result of the expedition destination game corresponding to each dispatch destination, that is, receive the reward.

Note that FIG. 22A shows a case where "dispatch destination A-1" and "dispatch destination A-2" are completed (cleared). When the player operates (tap) the collective expedition completion operation unit 94 , a collective expedition completion screen 270 ( FIG. 22B ) is displayed on the display 26 . If there are one or more expedition games for which the receipt of rewards has not been completed, an identification display indicating that there are one or more expedition games for which the receipt of rewards has not been completed is displayed on the collective expedition completion operation section 94. You may Specifically, as the identification display, a number indicating the number of expedition games for which receipt of rewards has not been completed may be displayed. Alternatively, as an identification display, specifically, a symbol indicating that there is an expedition game for which payment of the reward has not been completed may be displayed.

As described above, when the player operates (tap) the collective expedition completion operation section 94 , the collective expedition completion screen 270 ( FIG. 22B ) is displayed on the display 26 . FIG. 22B is a diagram illustrating an example of a collective expedition completion screen 270. As shown in FIG. As shown in FIG. 22B, the collective expedition completion screen 270 displays a list of rewards obtained at all dispatch destinations for which the required time has passed, the expedition game has been completed, and the receipt of the reward has not been completed.

Also, when the collective expedition completion screen 270 is displayed, the player can complete receiving the rewards obtained at these dispatch destinations. FIG. 22B shows a case where a list of rewards obtained by completing (clearing) "dispatch destination A-1" and "dispatch destination A-2" is displayed.

In addition, as shown in FIG. 22B, on the collective expedition completion screen 270, there are a non-redeployment operation unit 271 marked "not redeployed" and a redeployment operation unit 272 marked "redeployed". Is displayed. When the player taps the non-redeployment operation section 271 , the display of the expedition completion screen 250 ends and the expedition top screen 90 ( FIG. 7A ) is displayed on the display 26 . That is, the representative character 100a (FIG. 22A) is hidden because the player has received the reward obtained by completing (clearing) "dispatch destination A-1" and "A-2".

Further, when the player operates (tap) the redispatch operation unit 272, a redispatch screen 280 (FIG. 23) for redispatching the same party to the same dispatch destination is displayed on the display 26. FIG.

FIG. 23 is a diagram illustrating an example of the redispatch screen 280. As shown in FIG. As shown in FIG. 23, the redispatch screen 280 displays a dispatch destination display section 281 for each type of dispatch destination. The dispatch destination display section 281 displays the dispatch destination type and the play conditions (required force, maximum number of players, required time) corresponding to the dispatch destination type.

Also, as shown in FIG. 23, a party display section 282 is displayed in the dispatch destination display section 281 . The party display section 282 displays friendly characters of the same composition as the party dispatched to the dispatch destination last time. It should be noted that the party display section 282 may display at least a portion of all teammate characters forming a party.

In addition, as shown in FIG. By operating (tapping) the check column 283 , the player can switch whether or not to re-dispatch to the dispatch destination of the type corresponding to the check column 283 .

In addition, in this embodiment, a repeat dispatch function can be used on the re-dispatch screen 280 . In this embodiment, the re-dispatch screen 280 shows a case where the repeat dispatch function can be used, but the time reduction function cannot be used. However, the present invention is not limited to this, and both the repeat dispatch function and the time reduction function may be enabled on the re-dispatch screen 280 .

As shown in FIG. 23, the dispatch destination display section 281 displays a repeat dispatch number display section 284, a repeat dispatch number increase operation section 284a, and a repeat dispatch number decrease operation section 284b.

The number of dispatches being set is displayed in the repeat dispatch number display section 284 . When the player operates (tap) the repeat dispatch count increase operation unit 284a, the dispatch count is incremented by one, and the display of the repeat dispatch count display unit 284 is updated. Further, when the player operates (tap) the repeat dispatch count reduction operation section 284b, the dispatch count is decreased by one, and the display of the repeat dispatch count display section 284 is updated. In this embodiment, the minimum number of times of dispatch displayed in the repeated dispatch number display section 284 is one.

Further, as shown in FIG. 23, the redispatch screen 280 displays a cancel operation section 285 labeled "cancel" and a dispatch operation section 286 labeled "dispatch". When the player operates (tap) the cancel operation unit 285, the contents displayed on the redispatch screen 280 immediately before the operation (tap) are discarded. Also, the display of the redispatch screen 280 ends, and the collective expedition completion screen 270 (FIG. 22B) immediately before the redispatch operation unit 272 (FIG. 22B) is operated (tapped) is displayed on the display 26 .

Further, when the dispatch operation unit 286 is operated (tapped) by the player, the expedition game is started. Then, the expedition start effect screen 200 (FIG. 16B) is displayed on the display 26 for a predetermined period of time to notify the start of the expedition game. After a predetermined period of time has elapsed, the display of the expedition start effect screen 200 (FIG. 16B) on the display 26 ends, and the expedition top screen 90 (FIG. 22A) is displayed on the display 26 .

Also, as described above, in this embodiment, it is possible to dispatch a party to each of a plurality of dispatch destinations. Specifically, the desired dispatch destination is selected on the dispatch destination selection screen 100 (FIG. 7B), the party is organized on the formation screen 170 (FIGS. 13A and 13B), and the dispatch operation unit 177 is operated. By repeating the above, it is possible to dispatch a party to each of a plurality of dispatch destinations. However, in the above method, when dispatching a party to each of a large number of dispatch destinations, the player's operation becomes complicated, so there is a possibility that the player's convenience is reduced.

Therefore, in this embodiment, an expedition function is provided collectively as a function for facilitating the dispatch of a party to each of a plurality of dispatch destinations. At the top of the expedition top screen 90 (FIG. 7A), an expedition selection operation section 93 is collectively displayed. When the player operates (tap) the collective expedition selection operation unit 93, the collective expedition screen 290 (FIG. 24A) for using the collective expedition function is displayed on the display 26. FIG.

FIG. 24A is a first diagram collectively illustrating an example of an expedition screen 290. FIG. FIG. 24B is a second diagram collectively illustrating an example of the expedition screen 290. As shown in FIG. As shown in FIG. 24A, in the central part of the expedition screen 290, one or a plurality of dispatch destination display portions 291 corresponding to the types of dispatch destinations are displayed. In the initial state, dispatch destination display sections 291 corresponding to all dispatch destination types are collectively displayed on the expedition screen 290 .

Also, in the dispatch destination display section 291, the player can form a party to be dispatched to each dispatch destination. In addition, the dispatch destination display section 291 displays a manual organization operation section 292 labeled "manual organization" and an automatic organization operation section 293 labeled "automatic organization". When the player operates (tap) the manual organization operation section 292 , an unillustrated organization screen for an expedition is collectively displayed on the display 26 . On the expedition-use organization screen (not shown), it is possible to set the organization of the party based on the player's operation. The display contents and functions of the organization screen (not shown) for the collective expedition can be the same as those of the organization screen 170 .

Further, when the player operates (tap) the automatic organization operation unit 293, the type of automatic organization function (first automatic organization function or second automatic formation function) is used, and the party is automatically formed.

Further, the dispatch destination display section 291 is provided with a special drop item target display section 294 . When a party is organized as described above, teammate characters set as special item drop targets from which special items can be obtained are displayed in the special drop item target display section 294, as shown in FIG. 24B.

In addition, in this embodiment, a repeat dispatch function can be used on the collective expedition screen 290 . As shown in FIG. 24A, the dispatch destination display section 291 displays a repeat dispatch number display section 295, a repeat dispatch number increase operation section 295a, and a repeat dispatch number decrease operation section 295b.

The number of dispatches being set is displayed in the repeat dispatch number display section 295 . When the player operates (tap) the repeat dispatch count increase operation unit 295a, the dispatch count is increased by one, and the display of the repeat dispatch count display unit 295 is updated. Further, when the player operates (tap) the repeat dispatch count reduction operation section 295b, the dispatch count is decreased by one, and the display of the repeat dispatch count display section 295 is updated. In this embodiment, the minimum number of dispatches displayed in the repeat dispatch number display section 295 is one.

Also, in the present embodiment, a time reduction function can be used on the collective expedition screen 290 . As shown in FIG. 24A, the dispatch destination display section 291 displays a time reduction operation section 296 marked with "time reduction".

When the player taps the time reduction operation unit 296, a time reduction screen (not shown) for the expedition is collectively displayed on the display 26. FIG. On the expedition time reduction screen (not shown), it is possible to make detailed settings for the time reduction function based on the player's operation. The display contents and functions of the time reduction screen (not shown) collectively for the expedition can be the same as the time reduction screen 180 .

Further, as shown in FIG. 24A, the dispatch destination display section 291 displays a clear operation section 297 marked with "clear". When the player operates (tap) the clear operation section 297, the organization contents of the dispatch destination of the type corresponding to the operated (tapped) clear operation section 297 are discarded. Also, the ally character displayed in the special drop item target display portion 294 is hidden.

In addition, as shown in FIG. 24A , the collective expedition screen 290 displays an organization clear operation section 298 marked with “organization clear”. When the player operates (tap) the formation clear operation section 298, the formation contents of all dispatch destinations displayed on the expedition screen 290 are collectively discarded. Also, the ally character displayed in the special drop item target display portion 294 is hidden.

In addition, as shown in FIG. 24A, the dispatch destination display portion 291 displays a check box 299 . By operating (tapping) the check column 299 , the player can switch whether to dispatch to the dispatch destination of the type corresponding to the check column 299 .

In addition, as shown in FIG. 24A, the collective expedition screen 290 displays an all-check-clear operation section 300 labeled "clear all checks". When the player operates (tap) the check clearing operation unit 300, all the check boxes 299 displayed on the expedition screen 290 are cleared.

In addition, as shown in FIG. 24A, the expedition screen 290 displays a priority setting operation section 301 labeled "priority setting". When the player operates (tap) the priority setting operation unit 301 , the above-described priority setting screen 130 ( FIG. 9B ) is displayed on the display 26 . When the priority is set on the priority setting screen 130, the display of the priority setting screen 130 ends, and the expedition screen 290 is collectively displayed on the display 26. FIG.

In addition, as shown in FIG. 24A , the collective expedition screen 290 displays a first narrowing display operation section 302 for narrowing down the dispatch destination display section 291 displayed on the collective expedition screen 290 .

When the player taps the first narrowing-down display operation unit 302, narrowing down can be performed according to the type of dispatch destination. For example, the display may be narrowed down for each hierarchy to which the dispatch destination belongs. Further, for example, as the types of dispatch destinations, the above-described normal dispatch destinations always selectable by the player, and the first special dispatch destination and second special dispatch destination selectable only when a preset appearance condition is met. You may provide a tip. For example, when the first special dispatch destination uses a predetermined item, the appearance condition is satisfied and the player can dispatch the party. Also, when the second special dispatch destination completes (clears) the expedition game and receives the reward, a lottery is executed. . Then, it may be possible to switch among a case of narrowing down and displaying only the normal dispatch destination, a case of narrowing down and displaying only the first special dispatching destination, and a case of narrowing down and displaying only the second special dispatch destination.

Further, as shown in FIG. 24A , the collective expedition screen 290 displays a second narrowing display operation section 303 for narrowing down the dispatch destination display section 291 displayed on the collective expedition screen 290 .

By tapping the second narrowed-down display operation unit 303, the player can narrow down the display by displaying only dispatch destinations whose check boxes have been checked, and display all dispatch destinations regardless of whether the check box 299 is checked. It is possible to switch between displaying dispatch destinations by type.

In addition, as shown in FIG. 24A, a search tab 304 is displayed on the expedition screen 290 as a whole. Also, in the search tab 304, a search operation section 304a labeled "search" and three item selection fields 304b are displayed. When the player operates (tap) one of the item selection fields 304 b , an item selection screen (not shown) is displayed on the display 26 . On an item selection screen (not shown), the player can select up to three desired items (special equipment and normal items).

Further, for example, when a campaign is carried out in an expedition game, only dispatch destinations corresponding to the campaign being carried out may be narrowed down and displayed. Note that the campaign is executed over a preset period (for example, 10 days). Further, a predetermined icon indicating that the dispatch destination is targeted for the campaign may be displayed on the dispatch destination display section 291 of the dispatch destination targeted for the campaign. Note that the content of the campaign is not particularly limited. For example, it can be a campaign that increases the required time that is shortened when the party exceeds the required strength, or a campaign that increases the reward given to the player when the expedition destination game is completed (cleared). For example, when multiple types of campaigns are being executed at the same time, multiple icons corresponding to the respective campaigns may be displayed on the dispatch destination display section 291 .

Then, on the item selection screen (not shown), the item selected by the player is displayed in the item selection column 304b. When the player operates (tap) the search operation unit 304a while items are displayed in the item selection column 304b, the items displayed in the item selection column 304b correspond to dispatch destinations that can be acquired. The dispatch destination display section 291 is collectively displayed on the expedition screen 290 as a list.

In addition, in the present embodiment, the contents displayed collectively on the expedition screen 290 are saved in association with the preset. As shown in FIG. 24A , a preset switching operation section 305 is displayed at the top of the expedition screen 290 . In this embodiment, a total of nine presets are prepared. When the preset switching operation unit 305 is operated (tapped) by the player, an expedition screen 290 is displayed on the display 26 with the contents saved in association with the operated (tapped) preset. This makes it possible to improve convenience for the player.

In addition, as shown in FIG. 24A, on the expedition screen 290, a cancel operation section 306 marked with "cancel" is displayed. When the player operates (tap) the cancel operation unit 306 , the display of the expedition screen 290 is ended collectively, and the expedition top screen 90 ( FIG. 7A ) is displayed on the display 26 .

In addition, as shown in FIGS. 24A and 24B, the collective expedition screen 290 displays a collective expedition operating unit 307 labeled with “collective expedition”. As shown in FIG. 24A, when no check is entered in any of the check boxes 299 of the dispatch destination display section 291 displayed on the collective expedition screen 290, the collective expedition operating section 307 cannot be operated. displayed in good condition. In addition, even if the strength of the party organized in the dispatch destination display section 291 with a check input in the check column 299 falls below the necessary strength set for the corresponding dispatch destination, the expedition operation unit 307 operates collectively. Displayed as impossible.

On the other hand, if the strength of the party organized in the dispatch destination display section 291 whose check box 299 is checked is greater than or equal to the necessary strength set for the corresponding dispatch destination, as shown in FIG. 24B, Together, the expedition operation unit 307 is displayed in an operable state. When the player operates (tap) the collective expedition operation unit 307 in an operable state, the collective expedition confirmation screen 310 (FIG. 25) is displayed on the display 26 .

FIG. 25 is a diagram illustrating an example of an expedition confirmation screen 310 collectively. The collective expedition confirmation screen 310 notifies the player that the time reduction ticket or jewels will be consumed if the use of the time reduction function is set on the collective expedition screen 290 . Also, on the collective expedition confirmation screen 310 , various setting contents for each dispatch destination whose check box 299 of the collective expedition screen 290 is checked are notified. Note that if use of the time reduction function is not set on the collective expedition screen 290, time reduction tickets and jewels will not be consumed. Only the various setting contents for each are notified.

In addition, as shown in FIG. 25, on the expedition confirmation screen 310, a cancel operation section 311 marked with "cancel" is displayed. When the player operates (tap) the cancel operation unit 311, the display of the collective expedition confirmation screen 310 ends, and the collective expedition screen 290 (FIG. 24B) immediately before the collective expedition confirmation screen 310 is displayed is displayed. displayed on the display 26.

In addition, as shown in FIG. 25, on the collective expedition confirmation screen 310, a collective expedition operation section 312 marked with “collective expedition” is displayed. When the player collectively operates (tap) the expedition operation unit 312, the expedition game is started. Then, the expedition start effect screen 200 (FIG. 16B) is displayed on the display 26 for a predetermined period of time to notify the start of the expedition game. The expedition start effect screen 200 displays teammate characters dispatched to the expedition. Specifically, for example, all the friendly characters organized in the party, or a predetermined number of friendly characters out of the friendly characters organized in the party, are displayed on the expedition start effect screen 200 . For example, when the expedition function is collectively used to dispatch a party to each of five dispatch destinations, some or all of the friendly characters belonging to each of the five parties are displayed on the expedition start effect screen 200. The Rukoto. That is, it can be said that the larger the number of dispatch destinations collectively selected in the expedition function, the greater the number of predetermined characters displayed on the expedition start effect screen 200 .

Then, when a predetermined time has passed, the display of the expedition start effect screen 200 on the display 26 ends.

Then, when the use of the time reduction function is set for the expedition game that has started, the time reduction effect screen 210 is displayed on the display 26 for a predetermined period of time. Note that if use of the time reduction function is not set for the started expedition game, the expedition top screen 90 (FIG. 22A) is displayed on the display 26 . Further, when the predetermined time has passed, the display of the time reduction effect screen 210 on the display 26 ends. An expedition top screen 90 (FIG. 22A) is then displayed on the display 26 .

In this way, the player can grasp the dispatch destination where the item desired by the player can be acquired only by selecting the desired item and using the search operation unit 304a. For each of the dispatch destinations displayed, simply by forming a party, selecting the number of dispatches, and checking the check box 299, the expedition game for the selected number of dispatches can be collectively performed for one or a plurality of checked dispatch destinations. can start running. This facilitates item collection and saves the player time and effort.

Next, the functional configurations of the player terminal 1 and the server 1000 for executing the expedition game will be described. Note that description of the functional configurations of the player terminal 1 and the server 1000 relating to the battle game will be omitted.

(Control processing in player terminal 1 and server 1000)
FIG. 26 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 expedition 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. 27 is a diagram illustrating the configuration of memory 1012 in server 1000 and its function as a computer. A game control program 1500 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 for the expedition 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 1000A includes a game control unit 1500a.

Specifically, the CPU 1010 operates the game control program 1500 and causes the computer to function as the game control section 1500a. Part of the processing related to the expedition game performed by the terminal-side control unit 1A and the server-side control unit 1000A will be described below. The description of the battle game processing performed by the terminal-side control unit 1A and the server-side control unit 1000A will be omitted.

(Communication processing between player terminal 1 and server 1000)
FIG. 28 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 setting process (P2) is executed for receiving various settings for the expedition game.

FIG. 29 is a first flowchart for explaining the setting process (P2) in the player terminal 1. FIG. Also, FIG. 30 is a second flowchart for explaining the setting process (P2) in the player terminal 1. As shown in FIG. As shown in FIG. 29, the game control unit 500a determines whether or not the player has operated (tapped) the menu screen selection operation unit 92 of the expedition top screen 90 (FIG. 7A) (P2-1).

When the menu screen selection operation unit 92 is operated (tapped) (YES in P2-1), the game control unit 500a displays the menu screen 110 (FIG. 8A) on the display 26 (P2-2), End the setting process.

When the menu screen selection operation unit 92 is not operated (tapped) (NO in P2-1), the game control unit 500a determines whether the menu screen 110 is displayed on the display 26 ( P2-3).

When the menu screen 110 is displayed on the display 26 (YES in P2-3), the game control unit 500a determines whether or not the player's operation (tap) has been detected (P2-4).

If the player's operation (tap) on the menu screen 110 is not detected (NO in P2-4), the game control unit 500a terminates the setting process.

Further, when the player's operation (tap) on the menu screen 110 is detected (YES in P2-4), the game control unit 500a performs display switching processing for switching the display of the display 26 according to the player's operation (tap). (P2-5) is executed to terminate the setting process.

Specifically, when an operation (tap) of the notification setting operation unit 111 of the menu screen 110 is detected, the game control unit 500a displays the notification setting screen 120 (FIG. 8B) on the display 26. FIG. Further, when an operation (tap) of the priority setting operation section 112 of the menu screen 110 is detected, the game control section 500a displays the priority setting screen 130 (FIG. 9B) on the display 26. FIG. Further, when an operation (tap) of the automatic organization setting operation section 113 of the menu screen 110 is detected, the game control section 500a displays an automatic organization setting screen 160 on the display 26. FIG. Also, when an operation (tap) of the operation unit 114 to close the menu screen 110 is detected, the game control unit 500a ends the display of the menu screen 110 on the display 26 .

When the menu screen 110 is not displayed on the display 26 (NO in P2-3), the game control unit 500a determines whether the notification setting screen 120 is displayed on the display 26 (P2- 6).

When the notification setting screen 120 is displayed on the display 26 (YES in P2-6), the game control unit 500a determines whether or not the player's operation (tap) has been detected (P2-7).

If the player's operation (tap) on the notification setting screen 120 is not detected (NO in P2-7), the game control section 500a terminates the setting process.

Further, when the player's operation (tap) on the notification setting screen 120 is detected (YES in P2-7), the game control unit 500a determines that the player's operation (tap) detected in step P2-7 is notified. It is determined whether or not the operation is for the setting operation section 123 of the setting screen 120 (P2-8).

If the operation is not for the setting operation section 123 of the notification setting screen 120 (NO in P2-8), the game control section 500a shifts the process to step P2-10, which will be described later.

If the operation is for the setting operation unit 123 of the notification setting screen 120 (YES in P2-8), the game control unit 500a stores the expedition completion notification execution trigger set by the player as setting information in the information storage unit 550. (P2-9).

In addition, the game control unit 500a executes a display switching process (P2-10) for switching the display of the display 26 according to the player's operation (tapping) on the notification setting screen 120, and ends the setting process.

Specifically, the game control section 500a highlights the first execution trigger selection section 121 when the first execution trigger selection section 121 of the notification setting screen 120 is operated (tapped). Further, when the second execution trigger selection section 122 of the notification setting screen 120 is operated (tapped), the game control section 500a highlights the second execution trigger selection section 122 . Further, the game control unit 500a terminates the display of the notification setting screen 120 when the cancel operation unit 124 of the notification setting screen 120 is operated (tapped).

Further, when the notification setting screen 120 is not displayed on the display 26 (NO in P2-6), the game control unit 500a displays the priority setting screen 130 (FIG. 9B) on the display 26 as shown in FIG. It is determined whether or not it is set (P2-11).

When the priority setting screen 130 is displayed on the display 26 (YES in P2-11), the game control section 500a determines whether or not the player's operation (tap) has been detected (P2-12).

If the player's operation (tap) on the priority setting screen 130 is not detected (NO in P2-12), the game control section 500a terminates the setting process.

Further, when the player's operation (tap) on the priority setting screen 130 is detected (YES in P2-12), the game control unit 500a determines that the player's operation (tap) detected in step P2-12 is It is determined whether or not the operation is for the setting operation section 135 of the priority setting screen 130 (P2-13).

If the operation is not for the setting operation section 135 of the priority setting screen 130 (NO in P2-13), the game control section 500a shifts the processing to step P2-15, which will be described later.

In addition, if the operation is performed on the setting operation section 135 of the priority setting screen 130 (YES in P2-13), the game control section 500a stores the content of the priority setting set by the player in the information storage section 550 as setting information. Store (P2-14).

In addition, the game control unit 500a executes a display switching process (P2-15) for switching the display of the display 26 according to the player's operation (tapping) on the priority setting screen 130, and ends the setting process.

Specifically, when an operation (tap) is performed on an ally character displayed in the list display portion 131 of the priority setting screen 130, the game control unit 500a determines whether the operated (tapped) ally character is displayed. perform highlighting. In addition, the game control unit 500a displays the teammate characters left aligned in the priority target display unit 132 in the order in which they were operated (tapped). Further, when the reset operation unit 133 of the priority setting screen 130 is operated (tapped), the game control unit 500a resets the teammate character set as a priority target, The characters are highlighted and the teammate characters displayed in the priority target display section 132 are hidden. Further, the game control unit 500a displays a priority change first screen 140 (FIG. 10A) on the display 26 when the priority change operation unit 134 of the priority setting screen 130 is operated (tapped). . Further, the game control unit 500a terminates the display of the priority setting screen 130 when the cancel operation unit 136 or the setting operation unit 135 of the priority setting screen 130 is operated (tapped).

Further, when the priority setting screen 130 is not displayed on the display 26 (NO in P2-11), the game control unit 500a displays the priority change first screen 140 (FIG. 10B) or the priority change It is determined whether the second screen 150 (FIG. 10B) is displayed (P2-16).

When the first priority change screen 140 or the second priority change screen 150 is displayed on the display 26 (YES in P2-16), the game control unit 500a detects the player's operation (tap). (P2-17).

If the player's operation (tap) on the first priority change screen 140 or the second priority change screen 150 is not detected (NO in P2-17), the game control section 500a ends the setting process.

Further, when the player's operation (tap) on the first priority change screen 140 or the second priority change screen 150 is detected (YES in P2-17), the game control unit 500a performs the above step P2-17. It is determined whether or not the player's operation (tap) detected in is an operation on the setting operation section 151 of the second priority change screen 150 (P2-18).

If the operation is not for the setting operation section 151 of the second priority change screen 150 (NO in P2-18), the game control section 500a shifts the processing to step P2-20, which will be described later.

If the operation is performed on the setting operation section 151 of the second priority change screen 150 (YES in P2-18), the game control section 500a controls the ally character set as the source ally character and the destination ally character. exchanges the priority of the ally character set in (P2-19).

In addition, the game control unit 500a performs display switching processing (P2-20) for switching the display of the display 26 according to the player's operation (tapping) on the first priority change screen 140 or the second priority change screen 150. to end the setting process.

Specifically, the game control unit 500a terminates the display of the first priority change screen 140 when an operation (tap) of the operation unit 142 for closing the first priority change screen 140 is performed. Further, the game control unit 500a displays the second priority change screen 150 when an operation (tap) is performed on a teammate character displayed in the priority target display unit 141 of the first priority change screen 140. 26. In addition, when displaying the second priority change screen 150 , the game control unit 500 a highlights the ally character operated (tapped) on the first priority change screen 140 . Further, when an operation (tap) is performed on a teammate character displayed in the priority target display unit 141 of the priority change second screen 150, the game control unit 500a determines whether the operated (tapped) teammate character perform highlighting. Further, when the cancel operation unit 152 is operated (tapped), the game control unit 500a terminates the display of the second priority change screen 150 and displays the first priority change screen 140 on the display 26. do.

Further, when the first priority change screen 140 or the second priority change screen 150 is not displayed on the display 26 (NO in P2-16), the game control unit 500a causes the display 26 to set automatic organization. It is determined whether or not the screen 160 is displayed (P2-21).

When the automatic organization setting screen 160 is displayed on the display 26 (YES in P2-21), the game control unit 500a determines whether or not the player's operation (tap) has been detected (P2-22).

If the player's operation (tap) on the automatic organization setting screen 160 is not detected (NO in P2-22), the game control section 500a terminates the setting process.

Further, when the player's operation (tap) on the automatic organization setting screen 160 is detected (YES in P2-22), the game control unit 500a detects that the player's operation (tap) detected in step P2-22 is It is determined whether or not the operation is for the setting operation section 163 of the automatic organization setting screen 160 (P2-23).

If the operation is not for the setting operation section 163 of the automatic organization setting screen 160 (NO in P2-23), the game control section 500a shifts the processing to step P2-25, which will be described later.

Further, if the operation is for the setting operation section 163 of the automatic organization setting screen 160 (YES in P2-23), the game control section 500a selects the first automatic organization function or the second automatic organization function as the automatic organization function according to the player. setting information indicating which of the above is set is stored in the information storage unit 550 (P2-24).

In addition, the game control unit 500a executes a display switching process (P2-25) for switching the display of the display 26 according to the player's operation (tapping) on the automatic organization setting screen 160, and ends the setting process.

Specifically, the game control unit 500a highlights the first automatic organization function selection unit 161 when the first automatic organization function selection unit 161 of the automatic organization setting screen 160 is operated (tapped). conduct. Further, the game control unit 500a highlights the second automatic organization function selection unit 162 when the second automatic organization function selection unit 162 of the automatic organization setting screen 160 is operated (tapped). Further, the game control unit 500a terminates the display of the automatic organization setting screen 160 when the operation (tap) of the setting operation part 163 of the automatic organization setting screen 160 is performed.

Returning to FIG. 28, on the player terminal 1, the player selects a desired dispatch destination on the dispatch destination selection screen 100 (FIG. 7B), dispatches the party to the dispatch destination, and starts execution of the expedition game. Dispatch processing (P3) is executed.

FIG. 31 is a first flow chart for explaining the individual dispatching process (P3) in the player terminal 1. FIG. FIG. 32 is a second flowchart for explaining the individual dispatching process (P3) in the player terminal 1. FIG. FIG. 33 is a third flowchart for explaining the individual dispatching process (P3) in the player terminal 1. FIG. As shown in FIG. 31, the game control unit 500a determines whether or not any dispatch destination selection operating unit 101 of the dispatch destination selection screen 100 (FIG. 7B) has been operated (tapped) (P3-1).

If any of the dispatch destination selection operation units 101 on the dispatch destination selection screen 100 is operated (tapped) (YES in P3-1), the game control unit 500a selects the dispatch destination selection operation unit that was operated (tapped). The organization screen 170 corresponding to 101 is displayed on the display 26 (P3-2), and the individual dispatch processing is terminated.

Further, when the dispatch destination selection operation unit 101 is not operated (tapped) (NO in P3-1), the game control unit 500a operates (tap) the teammate characters displayed in the list display unit 171 of the formation screen 170. ) has been performed, that is, whether the player has manually formed a party (P3-3).

If an ally character displayed in the list display portion 171 of the formation screen 170 has been operated (tapped) (YES in P3-3), the game control portion 500a proceeds to step P3-7, which will be described later. Move.

Further, when the teammate character displayed in the list display portion 171 of the organization screen 170 is not operated (tapped) (NO in P3-3), the game control unit 500a controls the automatic organization operation portion of the organization screen 170. It is determined whether or not the operation (tap) of 174 has been performed (P3-4).

When the automatic organization operation section 174 of the organization screen 170 is operated (tapped) (YES in P3-4), the game control section 500a confirms the setting information related to the automatic organization function stored in the information storage section 550. (P3-5).

In addition, the game control unit 500a activates the type of automatic organization function (first automatic organization function or second automatic organization function) set by the player based on the setting information regarding the automatic organization function confirmed in step P3-5. is used to execute automatic formation processing for automatically forming a party (P3-6).

Specifically, when the first automatic organization function is used, the game control unit 500a first preferentially organizes three teammate characters with high priority into a party, excluding non-organizable characters. Then, when the total strength of the three ally characters has reached the required strength, the game control section 500a ends formation of the party. On the other hand, if the total strength of the three teammate characters does not reach the required strength, the game control unit 500a further organizes teammate characters not set as priority targets into the party. Specifically, among allied characters that are not set as priority targets and that can be formed, allied characters with greater strength are organized in order until the strength of the party meets the required strength.

Also, when the second automatic organization function is used, the game control unit 500a preferentially organizes three teammate characters with high priority into a party, excluding non-organizable characters. Further, the game control unit 500a organizes, among allied characters that are not set as priority targets and that can be organized, allied characters with high fighting power up to the maximum number of allied characters that can be organized.

Further, when the first automatic formation function is used when the priority target ally character has not been set, the game control unit 500a selects a ally character with a large strength among the ally characters that can be organized as a member of the party. Organize in order until the strength meets the required strength.

Further, when the priority target ally character is not set, when the second automatic formation function is used, the game control unit 500a can organize a ally character with a large strength among the ally characters that can be formed. Organize up to the maximum number of people.

In addition, the game control section 500a controls the drop target display section 172a and non The display of the drop object display section 172b is updated (P3-7).

Further, the game control unit 500a controls the maximum number of people display section 173c of the formation screen 170 based on the display contents of the drop target display section 172a and the non-drop target display section 172b of the formation screen 170 updated in step P3-7. Update the display (P3-8).

In addition, the game control unit 500a derives the strength of the formed party based on the display contents of the drop target display unit 172a and the non-drop target display unit 172b of the formation screen 170 updated in step P3-7 ( P3-9).

Also, the game control section 500a updates the display of the required strength display section 173a based on the strength of the party derived in step P3-9 (P3-10).

Also, the game control unit 500a derives the required time to be shortened based on the strength of the party derived in step P3-9 (P3-11). Here, the higher the strength of the organized party, the larger the value of the shortened required time.

Further, the game control unit 500a updates the display of the required time display unit 173b according to the shortened required time derived in step P3-11 (P3-12), and terminates the individual dispatch process.

Further, when the operation (tap) of the automatic organization operation section 174 of the organization screen 170 is not performed (NO in P3-4), as shown in FIG. It is determined whether or not the operation (tap) of the number-of-times increase operation unit 175a or the number-of-repeat dispatch number reduction operation unit 175b has been performed (P3-13).

When the operation (tap) of the repeat dispatch count increase operation portion 175a or the repeat dispatch count decrease operation portion 175b of the organization screen 170 is performed (YES in P3-13), the game control unit 500a confirms that the operation (tap) has been performed. The display of the repeat dispatch number display section 175 is updated according to the repeated dispatch number increase operation section 175a or the repeat dispatch number decrease operation section 175b (P3-14).

Specifically, when the repeat dispatch count increase operation unit 175a is operated (tapped), the game control unit 500a increases the dispatch count displayed in the repeat dispatch count display unit 175 by one. Further, when the repeat dispatch count decrease operation unit 175b is operated (tapped), the game control unit 500a decreases the dispatch count displayed in the repeat dispatch count display unit 175 by one.

In addition, the game control unit 500a derives the required time based on the number of times of dispatch displayed on the repeated dispatch number display unit 175 updated in step P3-14 (P3-15). Here, for example, if the required time required for one dispatch is 1 hour and 30 minutes, the game control unit 500a derives 6 hours as the required time if the number of dispatches is set to 4 times.

Further, the game control section 500a updates the display of the required time display section 173b based on the required time derived in step P3-15 (P3-16), and terminates the individual dispatch process.

Further, when the operation (tap) of the repeat dispatch number increase operation section 175a or the repeat dispatch number decrease operation section 175b of the organization screen 170 is not performed (NO in P3-13), the game control section 500a displays the organization screen. It is determined whether or not the operation (tap) of the time reduction operation unit 176 of 170 has been performed (P3-17).

When the operation (tap) of the time reduction operation section 176 of the organization screen 170 is performed (YES in P3-17), the game control section 500a displays the time reduction screen 180 on the display 26 (P3-18), End the individual dispatch process.

Further, when the operation (tap) of the time reduction operation unit 176 of the time reduction screen 180 is not performed (NO in P3-17), the game control unit 500a controls the number of times of reduction increase operation unit 181a of the time reduction screen 180, It is determined whether or not an operation (tap) has been performed on the number-of-times reduction operation section 181b, the number-of-reduction increase operation section 182a, or the number-of-reduction decrease operation section 182b (P3-19).

If an operation (tap) is performed on the shortening frequency increase operation unit 181a, the shortening frequency decrease operation unit 181b, the shortening frequency increase operation unit 182a, or the shortening frequency decrease operation unit 182b of the time reduction screen 180 (YES in P3-19) ), the game control unit 500a updates the display of the shortened number display unit 181 or the shortened number display unit 182 according to the operation unit operated (tapped) (P3-20).

Specifically, when the number-of-shortenings increasing operation unit 181a or the number-of-shortenings increasing operation unit 182a is operated (tapped), the game control unit 500a is displayed on the number-of-shortenings display unit 181 or the number-of-shortenings display unit 182. Increases shortening count by 1.

Further, when the shortening count decrease operation unit 181b or the shortening count decrease operation unit 182b is operated (tapped), the game control unit 500a changes the shortening count displayed in the shortening count display unit 181 or the shortening count display unit 182. Decrease once.

Further, the game control section 500a derives the required time based on the number of times of reduction displayed in the number of times of reduction display section 181 or the number of times of reduction display 182 updated in step P3-20 (P3-21). The game control unit 500a derives the required time so that the required time is shortened by one hour with one reduction. For example, if the required time is 6 hours and the total number of times of reduction displayed in the reduction times display section 181 and the reduction times display section 182 is 4 times, the game control section 500a shortens the time by 4 hours, Derive that the time is 2 hours.

Further, the game control unit 500a updates the display of the required time display unit 183 based on the required time derived in step P3-21 (P3-22), and terminates the individual dispatch processing.

Further, when the operation (tap) of the shortening number increase operation section 181a, the shortening number decrease operation section 181b, the shortening number increase operation section 182a, or the shortening number decrease operation section 182b of the time reduction screen 180 is not performed (P3- 19 NO), the game control unit 500a determines whether or not the cancel operation unit 185 of the time reduction screen 180 has been operated (tapped) (P3-23).

When the cancellation operation unit 185 of the time reduction screen 180 is operated (tapped) (YES in P3-17), the game control unit 500a executes display switching processing for ending the display of the time reduction screen 180 on the display 26. (P3-24) to terminate the individual dispatching process.

Further, when the cancel operation unit 185 of the time reduction screen 180 is not operated (tapped) (NO in P3-17), the game control unit 500a operates (tap) the setting operation unit 184 of the time reduction screen 180. is performed (P3-25).

When the setting operation unit 184 of the time reduction screen 180 is operated (tapped) (YES in P3-25), the game control unit 500a changes the content displayed on the time reduction screen 180 to the time reduction function. It is stored in the information storage unit 550 as abbreviated information (P3-26). For example, the time reduction information includes the consumption number of time reduction tickets and the number of consumptions of a predetermined number of jewels.

In addition, the game control unit 500a terminates the display of the time reduction screen 180, executes display switching processing to display the formation screen 170 (FIG. 15C) on the display 26 (P3-27), and terminates the individual dispatch processing. do. At this time, the game control unit 500a determines the required time before shortening (for example, 6 hours), the required time after shortening (for example, 2 hours), Then, the time shortened from the required time before shortening (for example, -4 hours) is displayed in the required time display section 173b of the organization screen 170. FIG.

Further, when the setting operation portion 184 of the time reduction screen 180 is not operated (tapped) (NO in P3-25), as shown in FIG. It is determined whether or not the operation (tap) of 178 has been performed (P3-28).

When the cancel operation unit 178 of the organization screen 170 is operated (tapped) (YES in P3-28), the game control unit 500a executes a display switching process for ending the display of the organization screen 170 on the display 26 ( P3-29), the individual dispatching process ends.

Further, when the cancel operation unit 178 of the organization screen 170 is not operated (tapped) (NO in P3-28), the game control unit 500a determines that the dispatch operation unit 177 of the organization screen 170 is operated (tapped). It is determined whether or not it has been broken (P3-30).

When the operation (tap) of the dispatch operation unit 177 of the organization screen 170 is performed (YES in P3-30), the game control unit 500a determines whether the time reduction function is being used, that is, in step P3-26. , it is determined whether or not the time reduction information related to the time reduction function is stored (P3-31).

If the time reduction function is used (YES in P3-31), the game control unit 500a displays the confirmation screen 190 on the display 26 (P3-32), and terminates the individual dispatch process.

Also, if the time reduction function is not used (NO in P3-31), the game control unit 500a shifts the process to step P3-36, which will be described later.

Further, when the operation (tap) of the dispatch operation unit 177 of the formation screen 170 has not been performed (NO in P3-30), the game control unit 500a operates (tap) the cancel operation unit 192 of the confirmation screen 190. It is determined whether or not it has been broken (P3-33).

If the cancellation operation unit 192 of the confirmation screen 190 is operated (tapped) (YES in P3-33), the game control unit 500a executes a display switching process for ending the display of the confirmation screen 190 on the display 26 ( P3-34), the individual dispatching process ends.

Further, when the cancel operation portion 192 of the confirmation screen 190 is not operated (tapped) (NO in P3-33), the game control portion 500a determines that the OK operation portion 191 of the confirmation screen 190 is operated (tapped). It is determined whether or not it has been broken (P3-35).

When the OK operation section 191 of the confirmation screen 190 is operated (tapped) (YES in P3-35), the game control section 500a shifts the process to step P3-36, which will be described later.

If the OK operation section 191 of the confirmation screen 190 is not operated (tapped) (NO in P3-35), the game control section 500a ends the individual dispatch process.

The game control unit 500a transmits expedition start information to the server 1000 (P3-36). The expedition start information includes, for example, dispatch destination information regarding the dispatch destination, repetition number information regarding the number of repetitions, party organization information regarding the types of allied characters organized in the party, whether or not the time reduction function is used, and time reduction. It includes information such as time reduction when the use of the function is set.

Further, the game control section 500a executes display switching processing for switching the display of the display 26 (P3-37), and terminates the individual dispatch processing. Specifically, the game control unit 500a displays the expedition start effect screen 200 (FIG. 16B) on the display 26 for a predetermined period of time. When the use of the time shortening function is set, the time shortening effect screen 210 (FIG. 16C) is displayed on the display 26 for a predetermined time after the expedition start effect screen 200 is finished. After that, the game control unit 500a displays the dispatch destination selection screen 100 (FIG. 17A) on the display 26. FIG.

Returning to FIG. 28, on the player terminal 1, on the re-dispatch screen 260 (FIG. 21) or the re-dispatch screen 280 (FIG. 23), for the expedition game that has been completed (cleared), the party of the same formation is dispatched again to the same dispatch destination. A re-dispatching process (P4) is executed.

FIG. 34 is a flowchart for explaining the re-dispatching process (P4) in the player terminal 1. FIG. As shown in FIG. 34, the game control section 500a determines whether or not the re-dispatch screen 260 or the re-dispatch screen 280 is displayed on the display 26 (P4-1).

If the re-dispatch screen 260 or the re-dispatch screen 280 is not displayed on the display 26 (NO in P4-1), the game control unit 500a terminates the re-dispatch process.

Further, when the re-dispatch screen 260 or the re-dispatch screen 280 is displayed on the display 26 (YES in P4-1), the game control unit 500a controls the repeat dispatch count increase operation unit 264a of the re-dispatch screen 260, repeat It is determined whether or not an operation (tap) has been performed on the dispatch number reduction operation section 264b, the repeat dispatch number increase operation section 284a of the re-dispatch screen 280, or the repeat dispatch number reduction operation section 284b (P4-2). .

Operation of the repeat dispatch number increase operation section 264a and the repeat dispatch number decrease operation section 264b of the re-dispatch screen 260, the repeat dispatch number increase operation section 284a or the repeat dispatch number decrease operation section 284b of the re-dispatch screen 280 ( tap) has been performed (YES in P4-2), the game control unit 500a displays the repeat dispatch count display unit 264 of the re-dispatch screen 260 or the re-dispatch The display of the repeated dispatch number display section 284 of the screen 280 is updated (P4-3).

In addition, the game control unit 500a, based on the number of dispatches displayed in the repeat dispatch number display section 264 of the re-dispatch screen 260 or the repeat dispatch number display section 284 of the re-dispatch screen 280 updated in step P4-3, Then, the required time is derived (P4-4).

Further, the game control section 500a displays the required time on the dispatch destination display section 261 of the re-dispatch screen 260 or the dispatch destination display section 281 of the re-dispatch screen 280 based on the required time derived in step P4-4. is updated (P4-5), and the redispatching process ends.

In addition, the repeat dispatch number increase operation section 264a and the repeat dispatch number decrease operation section 264b of the re-dispatch screen 260, the repeat dispatch number increase operation section 284a of the re-dispatch screen 280, or the repeat dispatch number decrease operation section 284b If no operation (tap) has been performed (NO in P4-2), the game control unit 500a determines whether or not an operation (tap) has been performed in the check box 283 of the redispatch screen 280 (P4-6). ).

If the check column 283 of the redispatch screen 280 is operated (tapped) (YES in P4-6), the game control unit 500a determines whether a check mark is displayed in the check column 283 where the operation (tapped) is performed. Display switching processing for switching is executed (P4-7), and the redispatch processing ends.

Further, the game control unit 500a determines whether or not the cancel operation unit 265 of the re-dispatch screen 260 or the cancel operation unit 285 of the re-dispatch screen 280 has been operated (tapped) (P4-8).

When the cancellation operation part 265 of the re-dispatch screen 260 or the cancel operation part 285 of the re-dispatch screen 280 is operated (tapped) (YES in P4-8), the game control unit 500a A display switching process for ending the display of the screen 260 or the redispatch screen 280 is executed (P4-9), and the redispatch process ends.

The game control unit 500a also determines whether the dispatch operation unit 266 of the re-dispatch screen 260 or the dispatch operation unit 286 of the re-dispatch screen 280 has been tapped (P4-10).

When dispatch operation unit 266 or dispatch operation unit 286 is tapped (YES in P4-10), game control unit 500a transmits expedition start information to server 1000 (P4-11).

In addition, the game control unit 500a executes display switching processing for switching the display of the display 26 (P4-12), and terminates the redispatch processing. Specifically, in the display switching process, the game control unit 500a displays the expedition start effect screen 200 (FIG. 16B) on the display 26 for a predetermined period of time.

Returning to FIG. 28, the player terminal 1 executes collective expedition processing (P5) for using the collective expedition function. FIG. 35 is a first flow chart for collectively explaining the expedition processing (P5) in the player terminal 1. FIG. FIG. 36 is a second flow chart for collectively explaining the expedition processing (P5) in the player terminal 1. FIG. FIG. 37 is a third flow chart for collectively explaining the expedition processing (P5) in the player terminal 1. FIG. As shown in FIG. 35, the game control unit 500a determines whether or not an operation (tap) has been performed on the collective tour selection operation unit 93 on the tour top screen 90 (FIG. 7A) (P5-1).

When the collective expedition selection operation unit 93 is operated (tapped) (YES in P5-1), the game control unit 500a displays the collective expedition screen 290 (FIG. 24A) on the display 26, End expedition processing.

Further, when the operation (tap) of the collective tour selection operation unit 93 is not performed (NO in P5-1), the game control unit 500a determines that the operation of the manual organization operation unit 292 of the collective tour screen 290 is not performed. (P5-3).

When the manual organization operation section 292 of the expedition screen 290 is operated collectively (YES in P5-3), the game control section 500a displays a manual organization screen (not shown) on the display 26 (P5-4), The collective expedition processing ends.

Further, when the operation of the manual organization operation section 292 of the collective expedition screen 290 has not been performed (NO in P5-3), the game control section 500a determines whether the completion operation on the manual organization screen (not shown) has been performed. It is determined whether or not (P5-5).

When the completion operation is performed on the manual organization screen (not shown) (YES in P5-5), the game control section 500a shifts the process to step P5-9, which will be described later.

Further, when the completion operation on the manual organization screen (not shown) is not performed (NO in P5-5), the game control section 500a collectively operates (tap) the automatic organization operation section 293 of the expedition screen 290. (P5-6).

When the automatic organization operation section 293 of the expedition screen 290 is operated (tapped) (YES in P5-6), the game control section 500a confirms the setting information related to the automatic organization function stored in the information storage section 550. (P5-7).

In addition, the game control unit 500a activates the type of automatic organization function (first automatic organization function or second automatic organization function) set by the player based on the setting information regarding the automatic organization function confirmed in step P5-7. Execute the automatic organization process to automatically organize the party (P5-8).

In addition, the game control unit 500a collectively displays special drop item targets on the expedition screen 290 according to the manual party formation performed by the player or the party formation automatically formed by using the automatic formation function. The display of the section 294 is updated (P5-9).

In addition, the game control unit 500a derives the strength of the formed party based on the manual party formation performed by the player or the party formation automatically formed by using the automatic formation function (P5 -10).

Also, the game control unit 500a derives the required time to be shortened based on the strength of the party derived in step P5-10 (P5-11). Here, the higher the strength of the organized party, the larger the value of the shortened required time.

In addition, the game control section 500a collectively updates the display of the required time displayed on the dispatch destination display section 291 of the expedition screen 290 according to the shortened required time derived in step P5-11 (P5- 12) End the collective expedition process.

When the automatic organization operation unit 293 of the collective expedition screen 290 is not operated (tapped) (NO in P5-6), the game control unit 500a repeats the collective expedition screen 290 as shown in FIG. It is determined whether or not the operation (tap) of the return dispatch frequency increase operation unit 295a or the repeat dispatch frequency decrease operation unit 295b has been performed (P5-13).

When the operation (tap) of the repeat dispatch count increase operation unit 295a or the repeat dispatch count decrease operation unit 295b of the expedition screen 290 is performed (YES in P5-13), the game control unit 500a performs the operation (tap). ) is performed, the display of the repeat dispatch number display section 295 is updated according to the repeat dispatch number increase operation section 295a or the repeat dispatch number decrease operation section 295b of the expedition screen 290 (P5-14). .

Further, the game control unit 500a derives the required time based on the number of dispatches displayed on the repeat dispatch number display unit 295 updated in step P5-14 (P5-15).

Further, the game control section 500a collectively updates the display of the required time in the dispatch destination display section 291 of the expedition screen 290 based on the required time derived in step P5-15 (P5-16). to end the expedition process.

Further, when the operation (tap) of the repeat dispatch count increase operation portion 295a or the repeat dispatch count decrease operation portion 295b of the expedition screen 290 is not performed (NO in P5-13), the game control unit 500a Collectively, it is determined whether or not the operation (tap) of the time reduction operation section 296 of the expedition screen 290 has been performed (P5-17).

When the operation (tap) of the time reduction operation unit 296 is performed (YES in P5-17), the game control unit 500a collectively displays a time reduction screen (not shown) for the expedition on the display 26 (P5-18 ), the expedition process ends.

The game control unit 500a determines whether or not the completion operation on the time reduction screen (not shown) for the collective expedition has been performed (P5-19).

When the completion operation on the expedition time reduction screen (not shown) is performed (YES in P5-19), the game control unit 500a derives the required time based on the use of the set time reduction function. (P5-20).

The game control unit 500a derives the required time so that the required time is shortened by one hour with one reduction. For example, if the required time is 6 hours and the total number of times of reduction displayed on the reduction times display section 181 and the reduction times display section 182 is 4 times, the game control section 500a will reduce the time by 4 hours. , that the required time is 2 hours.

Further, the game control section 500a collectively updates the display of the required time in the dispatch destination display section 291 of the expedition screen 290 based on the required time derived in step P5-20 (P5-21). to end the expedition process.

Further, if the completion operation on the time reduction screen (not shown) for the collective expedition is not performed (NO in P5-19), the game control unit 500a operates the check box 299 of the collective expedition screen 290. It is determined whether (tapping) has been performed (P5-22).

If the check field 299 of the collective expedition screen 290 has been operated (tapped) (YES in P5-22), the game control unit 500a selects the check field of the collective expedition screen 290 that has been operated (tapped). 299, the display switching process for switching the presence or absence of the check mark display is executed (P5-23), and the collective expedition process ends.

Further, if the operation (tapping) of the check box 299 of the collective expedition screen 290 is not performed (NO in P5-22), the game control unit 500a cancels the collective expedition screen 290 as shown in FIG. It is determined whether or not an operation (tap) has been performed on the operation unit 306 (P5-24).

When the cancel operation unit 306 of the collective expedition screen 290 is operated (tapped) (YES in P5-24), the game control unit 500a switches the display on the display 26 to end the display of the collective expedition screen 290. The processing is executed (P5-25), and the collective expedition processing ends.

Further, when the operation (tap) of the cancel operation unit 306 of the collective expedition screen 290 is not performed (NO in P5-24), the game control unit 500a cancels the collective expedition operation unit 307 of the collective expedition screen 290. (P5-26).

When the collective expedition operation unit 307 of the collective expedition screen 290 is operated (tapped) (YES in P5-26), the game control unit 500a transmits the expedition start information to the server 1000 (P5-27). ). The expedition start information includes, for example, dispatch destination information regarding each dispatch destination, repetition number information regarding the repetition number of each dispatch destination, party organization information regarding the types of allied characters formed in each dispatch destination party, It includes whether or not the time reduction function is used for each dispatch destination, and time reduction information when use of the time reduction function is set for each dispatch destination.

In addition, the game control unit 500a executes a display switching process for switching the display of the display 26 (P5-28), and terminates the collective expedition process. Specifically, in the display switching process, the game control unit 500a displays the expedition start effect screen 200 (FIG. 16B) on the display 26 for a predetermined period of time. In addition, when the use of the time reduction function is set, the display of the expedition start effect screen 200 is ended, and then the time reduction effect screen 210 (FIG. 16C) is displayed on the display 26 for a predetermined time. . After that, the game control unit 500a displays the expedition top screen 90 (FIG. 7A) on the display 26. FIG.

Returning to FIG. 28, the player terminal 1 executes withdrawal processing (P6) for using the withdrawal function. FIG. 38 is a flowchart for explaining withdrawal processing (P6) in the player terminal 1. FIG. As shown in FIG. 38, the game control unit 500a determines whether or not the withdrawal operation unit 105 of the dispatch destination selection screen 100 (FIG. 17A) has been operated (tapped) (P6-1).

When the withdrawal operation unit 105 of the dispatch destination selection screen 100 is operated (tapped) (YES in P6-1), the game control unit 500a displays the withdrawal confirmation screen 230 on the display 26 (P6-2), End the withdrawal process.

Further, when the withdrawal operation section 105 of the dispatch destination selection screen 100 is not operated (tapped) (NO in P6-1), the game control section 500a operates (tap) the cancel operation section 231 of the withdrawal confirmation screen 230. ) has been performed (P6-3).

When the cancellation operation section 231 of the withdrawal confirmation screen 230 is operated (tapped) (YES in P6-3), the game control section 500a executes display switching processing for ending the display of the withdrawal confirmation screen 230 on the display 26. (P6-4) to end the withdrawal process.

Further, when the cancellation operation section 231 of the withdrawal confirmation screen 230 is not operated (tapped) (NO in P6-3), the game control section 500a operates (tap) the OK operation section 232 of the withdrawal confirmation screen 230. is performed (P6-5).

When the OK operation section 232 of the withdrawal confirmation screen 230 is operated (tapped) (YES in P6-5), the game control section 500a transmits withdrawal information to the server 1000 (P6-7). The withdrawal information includes, for example, dispatch destination information regarding the dispatch destination to be withdrawn.

In addition, the game control unit 500a displays the expedition withdrawal screen 240 on the display 26 (P6-7), and terminates the withdrawal processing.

Further, when the OK operation section 232 of the withdrawal confirmation screen 230 is not operated (tapped) (NO in P6-5), the game control section 500a operates (tap) the close operation section 241 of the expedition withdrawal screen 240. It is determined whether or not it has been done (P6-8).

When the operation unit 241 for closing the expedition withdrawal screen 240 is operated (tapped) (YES in P6-8), the game control unit 500a executes display switching processing for ending the display of the expedition withdrawal screen 240 (P6-9). ) to terminate the withdrawal process.

Also, if the close operation unit 241 of the expedition withdrawal screen 240 is not operated (tapped) (NO in P6-8), the game control unit 500a ends the withdrawal processing.

Returning to FIG. 28, in the player terminal 1, after the start of the road trip game, the time reduction process after the start of the road trip (P7) for using the time reduction function is executed. FIG. 39 is a flowchart for explaining the post-trip start time reduction processing (P7) in the player terminal 1. FIG. As shown in FIG. 39, the game control unit 500a determines whether or not the time reduction operation unit 104 of the dispatch destination selection screen 100 (FIG. 17A) has been operated (tapped) (P7-1).

When the time reduction operation unit 104 of the dispatch destination selection screen 100 is operated (tapped) (YES in P7-1), the game control unit 500a displays the time reduction screen 180 (FIG. 17B) on the display 26. (P7-2) After the start of the expedition, the time reduction process is terminated.

Further, when the operation (tap) of the time reduction operation unit 104 of the dispatch destination selection screen 100 is not performed (NO in P7-1), the game control unit 500a increases the number of times of reduction of the time reduction screen 180 (FIG. 17B). It is determined whether or not an operation (tap) has been performed on the operating portion 181a, the reduction in the number of shortening operation portions 181b, the increase in the number of shortening operation portions 182a, or the decrease in the number of shortening operation portions 182b (P7-3).

When an operation (tap) is performed on the number of shortening increase operation section 181a, the number of shortening decrease operation section 181b, the number of shortening increase operation section 182a, or the number of shortening decrease operation section 182b of the time reduction screen 180 (FIG. 17B) (P7 -3 YES), the game control unit 500a controls the time reduction screen 180 (FIG. 17B) on which the operation (tap) has been performed. Alternatively, the display of the reduction number display section 181 or the reduction number display section 182 is updated according to the reduction number reduction operation section 182b (P7-4).

In addition, the game control unit 500a determines the required time based on the number of times of reduction displayed in the number of times of reduction display section 181 or the number of times of reduction display 182 of the time reduction screen 180 (FIG. 17B) updated in step P7-4. Derivation is performed (P7-5).

Further, the game control unit 500a updates the display of the required time display unit 183 of the time reduction screen 180 (FIG. 17B) based on the required time derived in step P7-5 (P7-6), and After the start, the time reduction processing is terminated.

Further, operation (tap) of the shortening frequency increase operation unit 181a, the shortening frequency decreasing operation unit 181b, the shortening frequency increasing operation unit 182a, or the shortening frequency decreasing operation unit 182b of the time shortening screen 180 of the time shortening screen 180 (FIG. 17B) is not performed (NO in P7-3), the game control section 500a determines whether or not the operation (tap) of the shortening operation section 184a of the time shortening screen 180 (FIG. 17B) has been performed (P7- 7).

When the operation (tap) of the shortening operation unit 184a of the time shortening screen 180 (FIG. 17B) is performed (YES in P7-7), the game control unit 500a displays the confirmation screen 220 on the display 26 (P7-8 ), the time reduction process is terminated after the start of the expedition.

Further, when the operation (tap) of the shortening operation section 184a of the time shortening screen 180 (FIG. 17B) is not performed (NO in P7-7), the game control section 500a cancels the time shortening screen 180 (FIG. 17B). It is determined whether or not an operation (tap) has been performed on the operation unit 185 or the cancel operation unit 222 of the confirmation screen 220 (FIG. 18A) (P7-9).

When the cancel operation unit 185 of the time reduction screen 180 (FIG. 17B) or the cancel operation unit 222 of the confirmation screen 220 (FIG. 18A) is operated (tapped) (YES in P7-9), the game control unit 500a executes a display switching process for ending the display of the time reduction screen 180 or the confirmation screen 220 (P7-10), and ends the time reduction process after the start of the expedition.

Also, if the operation (tap) of the cancel operation unit 185 of the time reduction screen 180 (FIG. 17B) or the cancel operation unit 222 of the confirmation screen 220 (FIG. 18A) is not performed (NO in P7-9), the game The control unit 500a determines whether or not an operation (tap) has been performed on the shortened operation unit 221 of the confirmation screen 220 (FIG. 18A) (P7-11).

If the operation (tap) of the shortening operation unit 221 of the confirmation screen 220 (FIG. 18A) is performed (YES in P7-11), the game control unit 500a transmits the time shortening information after the start of the expedition to the server 1000 ( P7-12). The post-expedition time reduction information includes, for example, dispatch destination information regarding dispatch destinations, the number of time reduction tickets consumed, and time reduction information including the number of consumptions of a predetermined number of jewels.

Further, the game control section 500a executes display switching processing for ending the display of the confirmation screen 220 on the display 26 (P7-13), and ends the time reduction processing after the start of the expedition.

Returning to FIG. 28, the server 1000 executes an expedition game progress process (S2) for managing the progress of the expedition game. FIG. 40 is a flowchart for explaining the road trip game progress processing (S2) in the server 1000. FIG. As shown in FIG. 40, the game control unit 1500a of the server 1000 subtracts the timer value of the expedition timer that counts the time until the expedition game in progress is completed (cleared) (S2-1).

Also, the game control unit 1500a of the server 1000 determines whether or not it has received expedition start information from the player terminal 1 (S2-2).

When the expedition start information is received (YES in S2-2), the game control unit 1500a of the server 1000 executes the expedition game start processing for starting the progress of the expedition game based on the received expedition start information (S2-2). 3).

Specifically, for example, the game control unit 1500a of the server 1000 derives the required time corresponding to each dispatch destination specified by the expedition start information, and sets the expedition timer. That is, the required time corresponding to the dispatch destination is derived based on the strength of the party set for the dispatch destination and the required strength set for the dispatch destination. When a plurality of dispatch destinations are designated by the expedition start information, the game control section 1500a of the server 1000 sets the expedition timer for each of the designated dispatch destinations. Further, when a plurality of repetition times are specified for the dispatch destination by the repetition number information included in the expedition start information, the game control unit 1500a of the server 1000 sets the repetition number information to the dispatch destination. are stored in the information storage unit 1550 of the server 1000 in association with each other. It should be noted that the game control unit 1500a of the server 1000 subtracts the number of repetitions set in the number of repetitions information each time the expedition game for the dispatch destination is completed.

Also, the game control unit 1500a of the server 1000 executes time reduction processing (S2-4), and shifts the processing to step S2-7, which will be described later. Specifically, the game control unit 1500a of the server 1000 controls the dispatch destination for which progress of the expedition game is started in step S2-3, if the use of the time reduction function is designated, the time reduction function included in the expedition start information Based on the shortening information, the timer value of the expedition timer corresponding to the dispatch destination is shortened. In addition, when time reduction tickets are used, a process for consuming the number of time reduction tickets to be used is performed.

Further, if the tour start information has not been received (NO in S2-2), the game control unit 1500a of the server 1000 determines whether or not the tour start time reduction information has been received from the player terminal 1 (S2- 5).

When the time reduction information after the start of the tour is received from the player terminal 1 (YES in S2-5), the game control section 1500a of the server 1000 executes the time reduction processing (S2-6). Specifically, the game control unit 1500a of the server 1000 sets the timer value of the expedition timer corresponding to the destination specified based on the dispatch destination information included in the received time reduction information after the start of the expedition to the time after the start of the expedition. It is shortened based on the time shortening information included in the shortening information.

In addition, the game control unit 1500a of the server 1000 determines whether or not there is an expedition game for which a predetermined end condition is satisfied (S2-7). Specifically, the game control unit 1500a of the server 1000 sets the timer value to 0 as a result of the subtraction in step S2-1 or as a result of the time reduction processing in steps S2-4 and S2-6. Determines whether an expedition timer exists.

If there is an expedition game for which a predetermined end condition is satisfied (YES in S2-7), the game control unit 1500a of the server 1000 sends expedition completion information corresponding to the expedition game for which the end condition is satisfied to the player. Terminal 1 is set to be obtainable (S2-8). In the expedition completion information, the end condition is satisfied, dispatch destination information regarding the dispatch destination of the expedition game that has been completed (cleared). , final expedition information indicating whether or not it is the last expedition game of the specified number of repetitions, and party formation information regarding the types of allied characters formed in the party dispatched to the dispatch destination. .

In addition, the game control unit 1500a of the server 1000 determines whether or not information on the number of times of repetition is stored for the dispatch destination for which the termination condition is satisfied in step S2-7 (S2-9).

In step S2-7, if the number of repetitions information is stored for the dispatched destination for which the end condition is satisfied (YES in S2-9), the game control unit 1500a of the server 1000 controls the expedition to the dispatched destination. An expedition game start process for starting the progress of the game is executed (S2-10), and the expedition game progress process ends. At this time, as described above, the game control unit 1500a of the server 1000 subtracts the number of repetitions set in the number-of-repetitions information in accordance with the start of the expedition game for the dispatch destination. .

Further, in step S2-7, if no repeat number information is stored for the dispatch destination for which the end condition is satisfied (NO in S2-9), the game control unit 1500a of the server 1000 executes the expedition game. End progress processing.

Further, if there is no expedition game satisfying the preset end condition (NO in S2-7), the game control unit 1500a of the server 1000 determines whether withdrawal information has been received from the player terminal 1. (S2-11).

When withdrawal information is received from the player terminal 1 (YES in S2-11), the game control unit 1500a of the server 1000 executes withdrawal processing for stopping the expedition game in progress, and ends the expedition game progress processing. do. Specifically, the game control unit 1500a of the server 1000 discards the expedition timer corresponding to the dispatch destination specified by the dispatch destination information included in the withdrawal information. As a result, the running expedition game is stopped.

If withdrawal information has not been received from the player terminal 1 (NO in S2-11), the game control unit 1500a of the server 1000 terminates the expedition game progression process.

Returning to FIG. 28, the server 1000 executes reward management processing (S3) for determining the content of the reward to be given to the player in response to the completion (clearance) of the expedition game. FIG. 41 is a flow chart for explaining the remuneration management process (S3) in the server 1000. FIG. As shown in FIG. 41, the game control unit 1500a of the server 1000 determines whether or not remuneration request information has been received from the player terminal 1 (S3-1).

When the reward request information is received from the player terminal 1 (YES in S3-1), the game control section 1500a of the server 1000 confirms the organization information included in the reward request information (S3-2).

The game control unit 1500a of the server 1000 confirms teammate characters set as special item drop targets based on the organization information confirmed in step S3-2 (S3-3).

The game control unit 1500a of the server 1000 executes special item lottery processing (S3-4). Specifically, the game control unit 1500a of the server 1000 corresponds to each of the teammate characters set as special item drop targets confirmed in step S3-3, based on a predetermined lottery table set in advance. Whether or not special items will be given will be determined by lottery.

The game control unit 1500a of the server 1000 executes special equipment lottery processing (S3-5). Specifically, the game control unit 1500a of the server 1000 determines by lottery whether or not the special equipment is given based on a predetermined lottery table set in advance.

The game control unit 1500a of the server 1000 executes normal item lottery processing (S3-6). Specifically, the game control unit 1500a of the server 1000 determines by lottery whether or not to give the normal item based on a predetermined lottery table set in advance.

The game control unit 1500a of the server 1000 completes the processing from step S3-2 to step S3-6 for all dispatch destinations (processing targets) specified by the dispatch destination information included in the received remuneration request information. (S3-7).

If the processing for all processing targets has not been completed (NO in S3-7), the game control unit 1500a of the server 1000 controls the processing targets for which the processing has not been completed from steps S3-2 to S3-6. Execute the process up to

Further, when the processing for all the processing targets is completed (YES in S3-7), the game control unit 1500a of the server 1000 outputs at least the execution results of the lottery processing in steps S3-4 to S3-6. The included remuneration determination information is set so that it can be acquired by the player terminal 1 (S3-8), and the remuneration management process ends.

Returning to FIG. 28, at the player terminal 1, when the required time has passed, the expedition completion process (P8) is executed to obtain a reward for the completed (cleared) expedition game. Also, in the expedition completion process (P8), the execution of the expedition completion notification is managed.

FIG. 42 is a flowchart for explaining the expedition completion process (P8) in the player terminal 1. FIG. As shown in FIG. 42, the game control section 500a determines whether or not the expedition completion information set in the server 1000 is newly acquired (P8-1).

When new tour completion information set in the server 1000 is acquired (YES in P8-1), the game control unit 500a stores the acquired tour completion information in the information storage unit 550 (P8-2).

In addition, the game control unit 500a confirms the setting information related to the execution trigger of the expedition completion notification stored in the information storage unit 550 (P8-3).

The game control unit 500a determines whether or not it is the notification timing of the expedition game corresponding to the expedition completion information stored in step P8-2, based on the setting information regarding the execution trigger of the expedition completion notification confirmed in step P8-3. (P8-4).

Specifically, the game control unit 500a determines that it is time to notify the tour completion game when the first execution trigger is set as the execution trigger for the tour completion notification.

Further, when the second execution trigger is set as the execution trigger for the expedition completion notification, the game control unit 500a sets the final expedition information indicating that the expedition game is the last one with the specified number of repetitions. If it is included in the completion information, it is determined that it is time to notify the expedition game.

If it is determined that it is time to notify (YES in P8-4), the game control unit 500a displays a message M (FIG. 9A) on the upper part of the display 26 as an expedition completion notification (P8-5). End the completion process. As described above, the screen on which the message M is displayed is not limited to the home screen 40, and the game control unit 500a, while the game application is running, A message M is displayed on the upper part of the display 26 .

Further, when the expedition completion information set in the server 1000 is not newly acquired (NO in P8-1), the game control unit 500a causes the result confirmation operation unit 107 of the destination selection screen 100 (FIG. 20A) to operate. It is determined whether or not it is (tapped) (P8-6).

When the result confirmation operation section 107 of the dispatch destination selection screen 100 (FIG. 20A) is operated (tapped) (YES in P8-6), the game control section 500a shifts the process to P8-8 described later.

Further, when the result confirmation operation section 107 of the dispatch destination selection screen 100 (FIG. 20A) is not operated (tapped) (NO in P8-6), the game control section 500a collectively displays the tour top screen 90 (FIG. 22A). It is determined whether or not the expedition completion operation section 94 has been operated (tapped) (P8-7).

When the collective expedition completion operation section 94 of the expedition top screen 90 (FIG. 22A) is operated (tapped) (YES in P8-7), the game control section 500a shifts the process to step P8-7, which will be described later.

The game control unit 500a transmits reward request information to the server 1000 (P8-8), and terminates the expedition completion process. When the result confirmation operation unit 107 is operated, the remuneration request information includes dispatch destination information related to the dispatch destination corresponding to the result confirmation operation unit 107, organization information set for the dispatch destination, and the like. Also, when the collective expedition completion operation unit 94 is operated, the remuneration request information includes dispatch destination information regarding each dispatch destination for which receipt of the reward has not been completed, and organization information set for each of the dispatch destinations. etc. are included.

Further, when the collective expedition completion operation section 94 on the expedition top screen 90 (FIG. 22A) is not operated (tapped) (NO in P8-7), the game control section 500a determines the reward set in the server 1000. It is determined whether or not information has been newly acquired (P8-9).

When the reward determination information set in the server 1000 is newly acquired (YES in P8-9), the game control unit 500a stores the acquired reward determination information in the information storage unit 550, and performs reward receipt processing for obtaining a reward. (P8-10).

In addition, the game control unit 500a displays the expedition completion screen 250 (FIG. 20B) or the collective expedition completion screen 270 (FIG. 22B) on the display 26 (P8-11), and terminates the expedition completion processing. Specifically, the game control unit 500a displays a list of the rewards obtained in step P8-10 on the expedition completion screen 250 or the collective expedition completion screen 270. FIG.

In addition, the game control unit 500a determines whether or not the non-redeployment operation unit 251 of the expedition completion screen 250 or the non-redeployment operation unit 271 of the collective expedition completion screen 270 has been operated (tapped) (P8-12). ).

When the non-redeployment operation unit 251 of the expedition completion screen 250 or the non-redeployment operation unit 271 of the collective expedition completion screen 270 is operated (tapped) (NO in P8-12), the game control unit 500a Display switching processing for hiding the expedition completion screen 250 or the non-redispatch operation section 251 is executed (P8-13), and the expedition completion processing is terminated.

If the non-redeployment operation section 251 of the expedition completion screen 250 or the non-redeployment operation section 271 of the collective expedition completion screen 270 is not operated (tapped) (NO in P8-12), the game control section The 500a determines whether or not the redispatch operation unit 252 of the expedition completion screen 250 or the redispatch operation unit 272 of the collective expedition completion screen 270 has been operated (tapped) (P8-14).

When the redispatch operation unit 252 of the expedition completion screen 250 or the redispatch operation unit 272 of the collective expedition completion screen 270 is operated (tapped) (YES in P8-14), the game control unit 500a completes the expedition. Based on the dispatch destination information included in the information, the re-dispatch screen 260 (FIG. 21) or the re-dispatch screen 280 (FIG. 23) is displayed on the display 26, and the expedition completion processing is terminated.

Further, when the redispatch operation unit 252 of the expedition completion screen 250 or the redispatch operation unit 272 of the collective expedition completion screen 270 is not operated (tapped) (NO in P8-14), the game control unit 500a , terminates the expedition completion process.

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 1000 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 1000 in the embodiment) to perform the following processes.

(Processing to be executed by a computer)
Once and twice or more for specific content (in the embodiment, an expedition game as an example) in which the game progresses with the passage of time without requiring the player's operation and the start of the game to progress the game. A process of setting the number of times selected by the player from among the predetermined number of times as the number of times of execution (steps P3, P4, and P5 as an example in the embodiment).
A process (in the embodiment, as an example, S2) of progressing the specific content (in the embodiment, as an example, an expedition game) based on the set number of times of execution.

A process of setting a trigger for executing a notification (in an embodiment, a message M as an example) indicating that progress of specific content (in the embodiment, an expedition game as an example) has ended, based on a player's operation (an embodiment Then, as an example, P2).
A process (P8 in the embodiment as an example) of executing a notification (as an example message M in the embodiment) based on the set execution trigger.

In the processing (in the embodiment, as an example, P2) for setting the notification execution trigger, the execution trigger ( In the embodiment, as an example, it can be set as a second execution trigger.

In the process (in the embodiment, as an example, P8) of executing the notification (in the embodiment, as an example, message M), when the set number of times of execution is 1, the specified content (in the embodiment, as an example, As an example, the notification is executed based on the end of the progress of the expedition game), and when the set number of times of execution is multiple times, the execution of the specific content (in the embodiment, the expedition game as an example) is performed multiple times. Run a notification based on progress being completed.

In the process (P8 in the embodiment, as an example) of executing a notification (in the embodiment, the message M as an example), when the number of times of execution is set to be multiple times, specific content less than the number of times of execution (in the embodiment, , as an example, when the progress of the expedition game) is finished, the notification is not executed.

One or more game media (in the embodiment, as an example, a friendly character) are included, and a predetermined parameter (in the embodiment, as an example, strength) calculated based on the game media is a minimum condition (in the embodiment, as an example, It is requested to set organization information (in the embodiment, the organization of the party as an example) that satisfies the minimum condition of the strength of the party), and a predetermined parameter (in the embodiment, as an example, the strength) is the minimum condition (in the embodiment, As an example, organization information (in the embodiment, an organization of the party) (in the embodiment, as an example, steps P3, P4, and P5).
Processing (in the embodiment, as an example, S2) of progressing the specific content (in the embodiment, as an example, an expedition game) based on the set organization information.
An automatic organization function that automatically generates organization information (in the embodiment, the organization of a party as an example), and prioritizes meeting minimum requirements (in the embodiment, the minimum requirement for party strength as an example). Satisfying the first automatic organization function and the minimum conditions (in the embodiment, as an example, the minimum conditions for the strength of the party), and increasing the degree of advantage (the strength of the party exceeds the required strength, the required time at the dispatch destination A process of generating organization information based on the automatic organization function selected by the player from among the second automatic organization functions that give priority to shortening the time (steps P3, P4, and P5 in the embodiment as an example).

In the process (in the embodiment, as an example, S2) of progressing the specific content (in the embodiment, as an example, an expedition game), the player's operation and the start of the game are not required for the progress of the game. (In the embodiment, an expedition game is played as an example).

When the set organization information (in the embodiment, the organization of the party as an example) satisfies the minimum condition (in the embodiment, the minimum condition of the strength of the party as an example), specific content (in the embodiment, as an example, Expedition game) is allowed to progress, and if the set organization information (in the embodiment, the organization of the party as an example) does not satisfy the minimum condition (in the embodiment, the minimum condition of the strength of the party as an example), the specified Processing (steps P3, P4, and P5 in the embodiment as an example) for not permitting progress of the content (an expedition game as an example in the embodiment).

In the process (in the embodiment, as an example, S2) of progressing the specific content (in the embodiment, as an example, an expedition game), a predetermined parameter (in the embodiment, as an example, strength) is a minimum condition (in the embodiment, as an example) , the time until progress of specific content (in the embodiment, an expedition game as an example) is shortened according to the degree of exceeding the party's minimum strength).

In the above embodiment, the higher the strength of the party to be dispatched to the destination, the shorter the required time is, thereby increasing the advantage of the player. However, the present invention is not limited to this. For example, if the strength of the party dispatched to the dispatch destination exceeds the required strength, the reward earned by the player may be increased. Further, for example, the reward earned by the player may be increased according to the degree to which the strength of the party to be dispatched to the dispatch destination exceeds the required strength. Also, both the reduction of the required time and the increase of the reward may be implemented according to the strength of the party. Alternatively, either shortening the required time or increasing the reward may be implemented according to the strength of the party.

Also, an upper limit may be set for the number of parties that can be dispatched to the destination at the same time. For example, if the total number of parties corresponding to expedition games that have not yet received rewards and the number of parties corresponding to expedition games that are in progress reaches the preset upper limit, a new party will be created. Dispatch may be disabled. In this case, by using the withdrawal function or completing the reception of the reward, it becomes possible to dispatch a new party.

Further, in the above embodiment, it has been shown that it is possible to shorten the time required for the expedition game by consuming the time reduction ticket, but the time reduction ticket can also be used for the battle game. may be made possible. For example, the player can set whether or not to use time reduction tickets and the number of tickets to be used on the main quest selection screen 74 (FIG. 5B). In this case, if one time reduction ticket is used, execution of one battle game is omitted (skipped). Specifically, when the use of the time reduction ticket is set on the main quest selection screen 74 (FIG. 5B), the party selection screen 77 (FIG. 5C), the battle game screen 80 (FIG. 6A), and the first result screen 83 are displayed. (FIG. 6B) may be omitted (abbreviated) and the second result screen 85 (FIG. 6C) may be displayed on the display 26 .

The game application, for example, uses a notification mechanism (e.g., Notification API) provided by the operating system (OS) of the smartphone to send a push notification, and displays "The expedition has been completed" on the notification screen of the smartphone. It is also possible to display a message M stating "Done".

Specifically, the player can arbitrarily set the push notification execution trigger, similar to the setting of the expedition completion notification execution trigger in the above-described embodiment. That is, regardless of the number of dispatches specified, the player can use the completion of one expedition game as the push notification execution trigger (first execution trigger) or the specified number of dispatches. It is possible to arbitrarily set any of the execution triggers (second execution triggers) of the expedition completion notification that the expedition game is all completed.

In the above-described embodiment, as an example of the game, an expedition game is provided in which organized friendly characters are dispatched to a dispatch destination desired by the player. It is not limited to the embodiment. For example, it is applicable to all game genres such as Roll Playing Game, Shooting Game, Puzzle Game, and Rhythm Game.

For example, when applied to the Roll Playing Game, a predetermined quest in which a battle game with a predetermined enemy character is executed in the Roll Playing Game corresponds to the expedition game. In this case, a minimum condition (minimum strength of the party) is provided to challenge a predetermined quest, and the more the strength of the player's party exceeds the minimum strength, the higher the player's advantage in the predetermined quest. Further, as a specific method of increasing the degree of advantage, it is possible to increase the power of a friend character, weaken an enemy character, or increase the reward for clearing a quest.

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 (6)

One or more game media are included, the setting of formation information that satisfies a minimum condition is required for a predetermined parameter calculated based on the game media, and the more the predetermined parameter exceeds the minimum condition, the higher the degree of advantage. a process of setting the organization information for specific content based on a player's operation;
a process of progressing the specific content based on the set organization information;
An automatic organization function that automatically generates the organization information, wherein a first automatic organization function that prioritizes meeting the minimum conditions at a minimum, and a priority that satisfies the minimum conditions and increases the degree of advantage. a process of generating the organization information based on the automatic organization function selected by the player among the second automatic organization functions;
is executed by a computer ,
the specific content includes a first specific content and a second specific content;
In the process of progressing the specific content,
the first specific content and the second specific content can be progressed at the same time;
Overlap between the game media included in the organization information set for the first specific content and the game media included in the organization information set for the second specific content is restricted. information processing program. a process of setting a preferred game medium based on a player's operation;
is further executed by the computer,
In the process of generating the organization information,
2. The information processing program according to claim 1, wherein when generating said organization information based on said first automatic organization function and said second automatic organization function, said organization information preferentially including said priority game media is generated. A process of permitting the progress of the specific content when the set organization information satisfies the minimum condition, and not permitting the progress of the specific content when the set organization information does not satisfy the minimum condition. of,
3. The information processing program according to claim 1 or 2, further causing the computer to perform: In the process of progressing the specific content,
3. The information processing program according to claim 1, wherein the time until progress of the specific content is finished is shortened according to the degree to which the predetermined parameter exceeds the minimum condition. An information processing method performed by one or more computers, comprising:
The computer is
One or more game media are included, the setting of formation information that satisfies a minimum condition is required for a predetermined parameter calculated based on the game media, and the more the predetermined parameter exceeds the minimum condition, the higher the degree of advantage. a process of setting the organization information for specific content based on a player's operation;
a process of progressing the specific content based on the set organization information;
An automatic organization function that automatically generates the organization information, wherein a first automatic organization function that prioritizes meeting the minimum conditions at a minimum, and a priority that satisfies the minimum conditions and increases the degree of advantage. a process of generating the organization information based on the automatic organization function selected by the player among the second automatic organization functions;
carry out
the specific content includes a first specific content and a second specific content;
In the process of progressing the specific content,
the first specific content and the second specific content can be progressed at the same time;
Overlap between the game media included in the organization information set for the first specific content and the game media included in the organization information set for the second specific content is restricted. information processing method. An information processing system comprising one or more computers,
The computer is
One or more game media are included, the setting of formation information that satisfies a minimum condition is required for a predetermined parameter calculated based on the game media, and the more the predetermined parameter exceeds the minimum condition, the higher the degree of advantage. a process of setting the organization information for specific content based on a player's operation;
a process of progressing the specific content based on the set organization information;
An automatic organization function that automatically generates the organization information, wherein a first automatic organization function that prioritizes meeting the minimum conditions at a minimum, and a priority that satisfies the minimum conditions and increases the degree of advantage. a process of generating the organization information based on the automatic organization function selected by the player among the second automatic organization functions;
carry out
the specific content includes a first specific content and a second specific content;
In the process of progressing the specific content,
the first specific content and the second specific content can be progressed at the same time;
Overlap between the game media included in the organization information set for the first specific content and the game media included in the organization information set for the second specific content is restricted. information processing system.

Images