JP2022105681A - Game system, game device, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To combine mutually cooperative users.

SOLUTION: A game system for executing a game in which a plurality of users cooperate to have a match with an NPC includes: a reception unit that receives an operation of a first user; a storage unit that associates information for identifying the first user who has had the match with a first NPC with information for identifying a second user who has had the match with the first NPC and stores them as history information regarding the match; an extraction unit that extracts information for identifying the second user on the basis of the history information as request destination information, when the reception unit receives an operation requesting another user to participate in a match with a second NPC; and a transmission unit that transmits information requesting to participate in the match with the second NPC to a user terminal set with the information for identifying the second user extracted by the extraction unit, on the basis of the set information that is set in advance on the basis of the operation of the first user.

SELECTED DRAWING: Figure 11

COPYRIGHT: (C)2022,JPO&INPIT

Description

Patent Law Article 30, Paragraph 2 Application Applicable Announcement on Website (1) August 10, 2017 http: // pf. mbga. jp / 12011943, http: // sp. pf. mbga. jp / 12011943, (2) August 10, 2017 http: // cxw. dmkt-sp. jp /

The present invention relates to a game system, a game device, and a program.

There is a battle game in which an object used for a battle is set in a deck from a plurality of objects (for example, a character card) possessed by the user to play against an enemy. In such a battle game, there is a game in which a plurality of users cooperate to play against an NPC (Non Player Character) (see, for example, Patent Document 1).

Japanese Unexamined Patent Publication No. 2014-28079

In the battle with the NPC described in Patent Document 1, it is possible for a plurality of users to cooperate with each other to advance the game in an advantageous manner. However, for example, if the cooperation of other users cannot be obtained in a match against an NPC, the user cannot advance the game in an advantageous manner. Thus, in games, it may not be possible to combine users who are cooperative with each other.

One aspect of the present invention is to provide a game system, a game device, and a program that can combine users who are cooperative with each other.

Another object of the present invention is to provide a game system, a game device, and a program capable of exerting the effects described in the embodiments described later.

In order to solve the above-mentioned problems, one aspect of the present invention is a game system in which a plurality of users cooperate to play a game against an NPC, the reception unit accepting the operation of the first user, and the first NPC. The storage unit that stores the information for identifying the first user who has played against the first NPC and the information for identifying the second user who has played against the first NPC as history information regarding the battle, and the reception unit. When the operation of requesting another user to participate in the battle with the second NPC is accepted, the extraction unit that extracts the information for identifying the second user based on the history information as the request destination information. It is a game system to be equipped.

Further, one aspect of the present invention is a game device for executing a game in which a plurality of users cooperate to play a game against an NPC, a reception unit that receives operation information of the first user, and a first user who has played against the first NPC. The storage unit that stores information for identifying the second user who has played against the first NPC and the information for identifying the second user who has played against the first NPC as history information about the battle, and the reception unit move to the battle with the second NPC. It is a game device including an extraction unit that extracts information for identifying the second user based on the history information as request destination information when receiving operation information requesting other users to participate. ..

Further, one aspect of the present invention is a game device for executing a game in which a plurality of users cooperate to play a game against an NPC, and information for identifying a first user who has played against the first NPC, and the first NPC. According to the reception step of receiving the operation information of the first user in the computer of the game device provided with the storage unit that stores the information for identifying the second user who has played the match as the history information about the match, and the reception step. When the operation of requesting another user to participate in the battle with the second NPC is accepted, the extraction step of extracting the information for identifying the second user based on the history information as the request destination information. It is a program to be executed.

It is a system diagram which shows an example of the structure of the game system which concerns on 1st Embodiment. It is a hardware configuration diagram which shows an example of the hardware configuration of the game server which concerns on 1st Embodiment. It is a hardware configuration diagram which shows an example of the hardware configuration of the user terminal which concerns on 1st Embodiment. It is explanatory drawing which shows an example of the home screen of the cooperation mission game which concerns on 1st Embodiment. It is explanatory drawing which shows an example of the detailed confirmation screen of the cooperation mission game which concerns on 1st Embodiment. It is explanatory drawing which shows an example of the battle confirmation screen of the cooperation mission game which concerns on 1st Embodiment. It is explanatory drawing which shows an example of the participation request screen to the cooperation mission game which concerns on 1st Embodiment. It is explanatory drawing which shows an example of the participation request confirmation screen from another user which concerns on 1st Embodiment. It is explanatory drawing which shows an example of the automatic participation request setting screen to another user which concerns on 1st Embodiment. It is explanatory drawing which shows the other example of the participation request label which concerns on 1st Embodiment. It is a schematic block diagram which shows an example of the functional structure of the game server which concerns on 1st Embodiment. It is a figure which shows an example of the history information table which the history information storage part which concerns on 1st Embodiment stores. It is a schematic block diagram which shows an example of the functional structure of the user terminal which concerns on 1st Embodiment. It is a flowchart which shows an example of the game processing of the cooperative mission game which concerns on 1st Embodiment. It is a schematic block diagram which shows an example of the functional structure of the game server which concerns on 2nd Embodiment. It is a schematic block diagram which shows an example of the functional structure of the user terminal which concerns on 2nd Embodiment.

[First Embodiment]
Hereinafter, the first embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a system configuration diagram showing an example of the configuration of the game system 1 according to the present embodiment. The game system 1 includes a plurality of user terminals 10-n (n = 1, 2, ..., N: n is a natural number) and one or a plurality of game servers 30. Each of the plurality of user terminals 10-n and the one or a plurality of game servers 30 are connected via the network NW. Each of the user terminals 10-n is also referred to as a user terminal 10.

First, the outline of the game system 1 will be described. The game server 30 provides a game that can be executed on the user terminal 10. For example, the game server 30 provides a game control program (game control program) that can be executed on the user terminal 10 so that it can be downloaded from the user terminal 10. Further, the game server 30 stores various setting information and history information necessary for the game executed on the user terminal 10, and transmits the information to the user terminal 10 as needed. The information required for the game control program and the game is not limited to the game server 30, but may be stored by another server device and provided from the other server device to the user terminal 10.

The user terminal 10 functions as a game device by downloading a game control program from the game server 30 and executing the downloaded game control program. For example, the user terminal 10 is a computer device used by the user, and is applied to a PC (Personal Computer), a tablet PC, a mobile phone such as a smartphone or a feature phone, a mobile information terminal (PDA: Personal Digital Assistant), a game machine, or the like. can. In this embodiment, an example of the case where the user terminal 10 is a smartphone will be described.

In the present embodiment, each device of the game system 1 executes a game in which a plurality of users cooperate to play a game against an NPC (Non Player Character). An NPC is a character that does not require user operation and is controlled by a game process executed by a computer. The user terminal 10 accepts the operation of the first user. The game server 30 stores information for identifying the first user who has played against the first NPC and information for identifying the second user who has played against the first NPC as history information regarding the battle in association with each other. The history information is information on various game histories such as information on battle history with NPCs. The information on the battle history with the NPC includes information that can identify the NPC that has played against it (for example, identification information), information related to the NPC (for example, NPC attribute information, NPC level information, etc.), and a battle with the NPC. Information for identifying the user of the user who participated in the game, information on the contribution of each user in the battle with the NPC, information on the battle situation, and the like, and historical information about the game played against the NPC. When the user terminal 10 receives an operation instruction requesting another user to participate in the battle with the second NPC, the game server 30 requests information for identifying the second user based on the history information. Extract as.
As a result, when the first user requests participation in the battle with the second NPC, the game system 1 can extract the second user who has played with the first NPC that appeared in the past as the request destination. Since the first user and the second user have played against the same first NPC in the past, there is a possibility that they will cooperate with each other as those who have similar experiences.
That is, the game system 1 can combine users who cooperate with each other in the battle with the second NPC.

[Game server hardware configuration]
FIG. 2 is a hardware configuration diagram showing an example of the hardware configuration of the game server 30. The game server 30 includes, for example, a server CPU (Central Processing Unit) 31, a server communication unit 34, and a server storage unit 330, and is interconnected via a bus. The game server 30 communicates with the user terminal 10 and other devices connected via the network NW via the server communication unit 34.

The server CPU 31 executes various programs stored in the server storage unit 330 and controls each unit of the game server 30.
The server communication unit 34 includes, for example, a plurality of Ethernet (registered trademark) ports, a plurality of digital input / output ports such as USB, and wireless communication such as WiFi (registered trademark).

The server storage unit 330 includes, for example, an HDD (Hard Disk Drive), an SSD (Solid State Drive), an EEPROM (Electrically Erasable Programmable Read-Only Memory), a ROM (Read-One Memory), a ROM (Read-One Memory), and the like. .. The server storage unit 330 stores various information, images, programs (including a game control program) and the like processed by the game server 30 and the user terminal 10. The server storage unit 330 is not limited to the one built in the game server 30, and may be an external storage device connected by a digital input / output port such as USB. Further, the game server 30 may be configured to include a hardware configuration such as a speaker (not shown), a display unit, an input unit, an audio output terminal, a camera, a gyro sensor, and a GPS (Global Positioning System) receiving module.

[Hardware configuration of user terminal]
FIG. 3 is a hardware configuration diagram showing an example of the hardware configuration of the user terminal 10. The user terminal 10 includes, for example, a CPU (Central Processing Unit) 11, a communication unit 12, an input unit 13, a display unit 14, and a storage unit 15, and is interconnected via a bus. .. The user terminal 10 communicates with the game server 30 and other devices connected via the network NW via the communication unit 12.

The CPU 11 executes various programs stored in the storage unit 15 and controls each unit of the user terminal 10.
The communication unit 12 includes, for example, a plurality of Ethernet (registered trademark) ports, a plurality of digital input / output ports such as USB, wireless communication such as WiFi (registered trademark), and the like.
The input unit 13 is configured integrally with the display as, for example, a touch panel, and receives various instruction inputs by the user's operation. The input unit 13 may be another input device such as a keyboard, a mouse, a touch pad, a microphone into which various instructions are input by voice, a game controller, or the like.
The display unit 14 is a display for displaying information such as an image or text, and includes, for example, a liquid crystal display panel or an organic EL (Electroluminescence) display panel. The display unit 14 is not limited to the one built in the user terminal 10, and may be a separate housing.

The storage unit 15 includes, for example, an HDD (Hard Disk Drive), an SSD (Solid State Drive), an EEPROM (Electrically Erasable Programmable Read-Only Memory), a ROM (Read-Only Memory), a ROM (Read-One Memory), or the like. The storage unit 15 stores various information, images, programs (including a game control program) and the like processed by the user terminal 10. The storage unit 15 is not limited to the one built in the user terminal 10, and may be an external storage device connected by a digital input / output port such as USB. Further, the user terminal 10 may be configured to include a hardware configuration such as a speaker (not shown), an audio output terminal, a camera, a gyro sensor, and a GPS (Global Positioning System) receiving module.

[Game overview]
Next, an outline of an example of the game in this embodiment will be described.

In the present embodiment, the user terminal 10 executes a game control program for a battle game. In this battle game, the user operates the user terminal 10 to set a card used for a battle (hereinafter referred to as "battle") from a plurality of character cards possessed by the user in the deck. The user terminal 10 makes the character of the set character card and the enemy character appearing in the game play against each other based on the set value set in the card or the character and the operation by the user. Here, the character card is an example of an object that appears in the game and is recognized by the user by an image (text, still image, moving image, or the like). Further, the character is a person, an animal, an object (for example, a vehicle) or the like indicated by this object (that is, a character card).
In this battle game, the user terminal 10 grants one or a plurality of character cards to the user according to the progress of the game. For example, the user terminal 10 grants a character card as a reward when the battle in the game is won. Further, the user terminal 10 gives a character card by performing a card lottery. The user terminal 10 stores a plurality of character cards given to the user, and causes the user to select a character to be battled from the stored character cards.

There are different types of character cards. The type is, for example, a character, a combination of a character and accompanying information. The user terminal 10 may have the user possess a plurality of different types of character cards, or may possess a plurality of cards of the same type.
For example, the user terminal 10 may have cards having different names (hereinafter, also referred to as “character names”) that can identify characters as different types of character cards. Further, the user terminal 10 may have at least one card having different incidental information as a different type of character card, even if the card has the same character. Here, the accompanying information is various information attached to the character card. The accompanying information includes, for example, a rarity indicating the rarity of the character card, an attribute indicating an attack that the character is good at, a skill indicating a special ability that the character can use, and the like. For example, the rarity is divided into seven stages of N, N +, R, R +, SR, SR +, and UR in order from the one with the lowest rarity to the one with the highest rarity. The higher the rarity of a character, the higher the value, for example, the higher the attack power value or the defense power value (or the higher the upper limit value). The user is more likely to advance the battle in an advantageous manner by using the card of the character with high rarity in the battle. The accompanying information may include a card ID that can identify the type of character card.

[Game screen]
Hereinafter, the outline of the battle game according to this embodiment will be described.

[Home Screen]
FIG. 4 is an explanatory diagram showing an example of a home screen of the cooperative mission game according to the present embodiment. In this figure, the home screen G10 is an example of a game screen that is a screen for operating and selecting a mission battle in a cooperative mission game, and is displayed according to the activation of this game.
Here, the cooperative mission game is, for example, a battle game in which a plurality of users cooperate to play against an NPC (Non Player Character (also referred to as “Raid Boss”)). In the cooperative mission game, by defeating the raid boss, character cards and items that can be used for the progress of the game can be obtained as rewards (also referred to as "mission rewards"). When the user plays against the raid boss, the user can request one or more other users to participate in the fight against the raid boss. When a user plays against a raid boss, or when a user receives a request from another user to participate in a battle with a raid boss and plays against the raid boss, it is possible to play against the raid boss by satisfying certain conditions. For example, the predetermined condition is a "challenge ticket", and if you have the necessary number of "challenge tickets" to play, you can play against the raid boss. For example, the raid boss has one or a plurality of types of raid bosses for each level such as levels Lv1, Lv2, Lv3, Lv4, and Lv5. The level (also referred to as "boss level") represents the difficulty level at which the user wins each raid boss. For example, the higher the level, the higher the difficulty level. The higher the difficulty level of the raid boss, the higher the initial HP (Hit Point (also referred to as "boss physical strength")), and the higher the defense power and attack power are set.

In the illustrated example, the possession challenge ticket information E10 representing the "challenge ticket" possessed by the user is displayed on the home screen G10. For example, five types of "challenge tickets" are displayed according to the level of the raid boss: challenge ticket Lv1, challenge ticket Lv2, challenge ticket Lv3, challenge ticket Lv4, and challenge ticket Lv5. It is displayed as "x25", "x15", "x0", "x0", and "x0". To play against each raid boss, a predetermined number of challenge tickets, for example, 5 cards are required according to the level of the raid boss. The "challenge ticket" can be obtained, for example, by distributing a predetermined number at the start of the event, distributing it as a login bonus, or purchasing it.

Further, the cooperation mission list E11 is displayed on the home screen G10. The cooperative mission list E11 displays a cooperative mission game in which a user can request other users to participate. In the illustrated example, the label E12 of the mission A and the label E16 of the mission B are displayed. On the label E12 of the mission A, the battle detail icon E13 with the raid boss A of the boss level Lv1, the status label E14 of the raid boss A, and the mission reward label E15 are displayed.
The battle detail icon E13 is an icon as an operator for confirming the details of the battle game with the raid boss A, for example, the mission reward and the like. The status label E14 displays the boss physical strength of the raid boss A, the level of the challenge ticket required for the battle with the raid boss A, and the number of challenge tickets required for the battle. In the illustrated example, the status label E14 displays "boss physical strength: 5000" as the boss physical strength of the raid boss A, and "challenge" as the level of the challenge ticket required for the battle with the raid boss and the number of challenge tickets required for the battle. Ticket [Lv1] x 5 "is displayed. The mission reward label E15 displays some of the items that can be obtained by defeating the raid boss in the cooperative mission game. The same applies to the label E16 of mission B. For example, if the number of challenge tickets is less than the predetermined number, a text E17 indicating that it is impossible to play against the raid boss is displayed on the status label, such as "Insufficient challenge tickets". You may.

[Detail confirmation screen]
FIG. 5 is an explanatory diagram showing an example of a detailed confirmation screen of the cooperative mission game according to the present embodiment.
In the illustrated example, the detail confirmation screen G20 is displayed when the user taps the battle detail icon E13 in FIG.
On the detailed confirmation screen G20, the label E20 of the mission A and the mission reward label E24 are displayed. On the label E20 of the mission A, the icon E21 of the raid boss A of the boss level Lv1, the status label E22 of the raid boss A, and the mission start icon E23 are displayed.
The icon E21 of the raid boss A is an image showing the boss level of the raid boss A and the raid boss to be opposed to the raid boss A. The status label E22 is a status label representing the initial HP of the raid boss A. The mission start icon E23 is an icon as an operator for starting a mission. When the user taps the mission start icon E23, a predetermined number of challenge tickets Lv1 are consumed and the battle confirmation screen is displayed. The mission reward label E24 displays the items that can be obtained by winning the battle game with the raid boss in the cooperative mission game, and the number of items that can be obtained.

[Battle confirmation screen]
FIG. 6 is an explanatory diagram showing an example of a battle confirmation screen of the cooperative mission game according to the present embodiment.
In the illustrated example, the battle confirmation screen G30 is displayed when the user taps the mission start icon E23 in FIG.
On the battle confirmation screen G30, "time limit; 01:00:00" indicating that the time limit label E30 that can play against the raid boss A is 1 hour is displayed, and the upper limit of the number of users that can play against the raid boss 30 is 30. "Number of participants; 1/30" is displayed as a person and one person representing the number of users who have played against the raid boss. When the time limit has passed, it will not be possible to battle with the raid boss. In this case, the mission reward is less than that of winning the battle game, or the reward cannot be obtained.

Further, on the battle confirmation screen G30, as the status label E31 of the raid boss A, "HP: 5000/5000" and an HP gauge that visually represents the amount of the HP value of the raid boss A are described. It means that the value is 5000 and the maximum value is 5000.
Further, on the battle confirmation screen G30, the battle start icon E32 is displayed as an operator for starting the battle with the raid boss A. The battle with the raid boss is started by the user tapping the battle start icon E32.
Further, the cost confirmation label E33 is displayed on the battle confirmation screen G30. The cost is a value required when setting a character card in a deck or when playing a cooperative mission game. The current value of the cost decreases when it is consumed by playing the above-mentioned cooperative mission game or the like, for example. The current value (consumed cost) of the cost recovers to a predetermined amount (for example, 1 or 5 or 10 or the total amount) after a predetermined time (for example, 3 minutes) has elapsed. It can also be recovered by using a cost drink, which is an item that recovers costs. The cost confirmation label E33 indicates that the start of the battle consumes "10", for example, the current value of the cost is reduced from "169" to "159".

Further, the participation request label E34 is displayed on the battle confirmation screen G30. Participation request label E34 includes all user icons E35 as controls for requesting all users as users requesting participation in the battle with the raid boss, and collaborators as controls for requesting cooperators. The icon E36 and the team icon E37 are displayed as controls for making the team a request destination. When the user taps the all user icons E35, a request to participate in the battle with the raid boss A is transmitted to a predetermined number of users randomly selected from all the users, for example, 29 people. In addition, when the user taps the collaborator icon E36, the users who have played against the raid boss that appeared in the past are extracted, and the extracted predetermined number of users, for example, 29, are played against the raid boss A. A request to participate in is sent. Further, when the user taps the team icon E37, users belonging to the same team as the team to which the user belongs are extracted, and a predetermined number of extracted users, for example, 29, are played against Raid Boss A. A request to participate in is sent. The participation request can be made before the user starts the battle with the raid boss A or after the user starts the battle with the raid boss A.

Further, the time bonus label E38 is displayed on the battle confirmation screen G30. The time bonus label E38 is set to a time shorter than the time limit displayed on the time limit label E30, for example, 10 minutes, and if the raid boss is defeated within 10 minutes from the start of the battle with the raid boss A, the time limit ( It represents the bonus time that you can get more mission rewards or higher value items than if you win the raid boss in 10 minutes or more and less than 1 hour.

[Participation request screen]
FIG. 7 is an explanatory diagram showing an example of a screen for requesting participation in the cooperative mission game according to the present embodiment.
The participation request screen G40 is a raid boss A for a predetermined number of users, for example, 29, randomly selected from all users by tapping all the user icons E35 in FIG. Displayed after the request to participate in the match is sent. On the participation request screen G40, "Request all users to participate!" Is displayed as a transmitted label E40 indicating that the participation request to a predetermined number of users randomly selected from all users has been transmitted. Will be done. Further, on the transmitted label E40, all user icons E41, collaborator icons E42, and team icons E43 are displayed so that additional operations cannot be performed. The time during which additional operations cannot be performed is preferably less than the time limit for playing against the raid boss, for example, 30 minutes, but this is not the case. Additional operations will be possible after an inoperable time has elapsed, and all user icons, collaborator icons, and team icons will be displayed so that you can request to participate in the battle with the raid boss again.

[Participation request confirmation screen]
Next, a request screen when a user is requested by another user to participate in a battle with a raid boss will be described.
FIG. 8 is an explanatory diagram showing an example of a participation request confirmation screen from another user according to the present embodiment.
On the participation request confirmation screen G60, the rescue label E60 of the user A indicating the participation request from the user A and the rescue label E62 of the user B representing the participation request from the user B are displayed. On the rescue label E60 of the user A, a character icon indicating that the raid boss to be opposed is the raid boss B and the boss level of the raid boss B is displayed. In addition, an HP gauge that visually represents the amount of the current HP value of the raid boss B is described. Here, the HP of the raid boss does not recover if it is within the time limit, and the HP value at the end of the immediately preceding battle becomes the HP value at the start of the immediately preceding battle. Further, the rescue label E60 of the user A displays the remaining time label E61 corresponding to the time limit related to the battle of the user A with the raid boss B (for example, the time limit label E30 shown in FIG. 6). The remaining time label E61 displays the remaining time that can be played against the raid boss B of the user A.
Since the rescue label E62 of the user B is the same as the rescue label E60 of the user A, the description thereof will be omitted. Here, the raid boss B in which the user A fights and the raid boss B in which the user B fights are the same difficulty and the same type of raid boss, but the battle with the same raid boss as a mission to the user A and the user B is independent. It has occurred, and the HP of the raid boss is also managed independently.

[Automatic participation request setting screen]
Next, a setting screen for automatically requesting other users to participate in the battle with the raid boss will be described.
FIG. 9 is an explanatory diagram showing an example of an automatic participation request setting screen for other users according to the present embodiment.
Although an example of the case where the participation request is transmitted according to the user operation has been described with reference to FIG. 6, the participation request may be automatically transmitted by the user's preset setting. The details will be described using the automatic participation request setting screen G70.
On the automatic participation request setting screen G70, a boss level setting icon E70, a boss attribute setting icon E71 indicating the attributes of the raid boss, a time zone setting icon E72 indicating the time zone for executing automatic rescue, and a destination for sending the participation request are displayed. The rescue request destination setting icon E73 indicating the above is displayed.

The boss level setting icon E70 is an icon as a pull-down type operator for setting the level condition of the boss when requesting participation from another user without the need for operation by the user. The boss level setting icon E70 is an icon as an operator that can be selected from five options of, for example, level 1 or higher, level 2 or higher, level 3 or higher, level 4 or higher, and level 5. The boss attribute setting icon E71 is an icon as a pull-down type operator that sets the attribute condition of the boss when requesting participation from another user without the need for operation by the user. Here, the attribute of the boss is an example of the attribute information of the raid boss, and is an attribute set for each raid boss like the attribute of the character card. Depending on the combination of the attributes of the raid boss and the attributes of the character card, there are superiority and inferiority in the battle with the raid boss. For example, boss attributes include red, blue, yellow, and orange. In other words, the attribute information of the raid boss is, for example, information regarding the superiority or inferiority of the battle. The amount or the amount of damage from the opponent affects the superiority or inferiority of the opponent, and the number of attacks on the opponent or the number of attacks from the opponent affects the superiority or inferiority of the opponent.

At the time of battle, there are advantages and disadvantages to the battle depending on the combination of attributes. For example, if the character card used by the user is red, it is advantageous for the blue boss (for example, the amount of damage to the opponent is large, or the amount of damage from the opponent is small, to the opponent. If the number of attacks is increased or the number of attacks from the opponent is small) and the character card used by the user is blue, it is advantageous for the yellow boss and is used by the user. When the character card has the yellow attribute, it is advantageous to the boss with the orange attribute, and when the character card used by the user has the orange attribute, it is advantageous to the boss with the red attribute. In contrast to this, for example, if the character card used by the user has a blue attribute, it is disadvantageous to the red attribute boss (for example, the amount of damage to the opponent is small, or the amount of damage from the opponent is large. Etc.), and if the character card used by the user has a yellow attribute, it is disadvantageous to the blue attribute boss, and if the character card used by the user has an orange attribute, it is disadvantageous to the yellow attribute boss. If the character card used by the user has a red attribute, it is advantageous for the boss with an orange attribute.
For example, the red attribute and the orange attribute may be set as related attributes (also referred to as the same attribute) so that there is no advantage or disadvantage in the battle.

The boss attribute setting icon E71 is, for example, an icon as an operator that can be selected from four options of red, blue, yellow, and no designation.
The time zone setting icon E72 is an icon as a pull-down type operator for setting a time zone condition when requesting participation from another user without the need for operation by the user. The time zone setting icon E72 can be selected from, for example, 6:00 to 12:00, 12:00 to 18:00, 18:00 to 24:00, 24:00 to 6:00, and five options without designation. An icon as a possible operator.

The rescue request destination setting icon E73 is an icon as a pull-down type operator for setting a rescue destination when requesting participation from another user without the need for operation by the user. The rescue request destination setting icon E73 is an icon as an operator that can be selected from, for example, three options of all users, cooperators, and teams.
The automatic participation request is set when the user and the raid boss who meet one or more of the conditions set by the boss level setting icon E70, the boss attribute setting icon E71, and the time zone setting icon E72 play against each other. It may be sent to the rescue request destination set by the icon E73.
In addition, the automatic participation request is a rescue request destination setting icon when the raid boss who satisfies all of the conditions set by the boss level setting icon E70, the boss attribute setting icon E71, and the time zone setting icon E72 and the user play against each other. It may be sent to the relief request destination set in E73.

[Participation request label]
Next, another example of the participation request label E34 shown in FIG. 6 will be described.
FIG. 10 is an explanatory diagram showing another example of the participation request label according to the present embodiment.
In addition, the participation request label E80 is displayed on the battle confirmation screen. The illustrated example is the battle confirmation screen G80 of the portion of the battle confirmation screen G30 shown in FIG. 6 on which the participation request label E34 is displayed. On the participation request label E80, as a user requesting participation in the battle with the raid boss, all user icons E81 as an operation element for making all users the request destination, and a collaborator as the operation element for making the collaborator the request destination. The icon E82 and the team icon E84 are displayed as controls for making the team a request destination. When a user taps all user icons E81, a request to participate in a battle with Raid Boss A is transmitted to a predetermined number of users randomly selected from all users, for example, 29 people. To. In addition, by tapping the collaborator icon E82 by the user, users who have played against the raid boss that appeared in the past are extracted, and the extracted predetermined number of users are requested to participate in the battle with the raid boss A. Is sent. In addition, when the user taps the team icon E84, users belonging to the same team as the team to which the user belongs are extracted, and the extracted predetermined number of users are requested to participate in the battle with Raid Boss A. Is sent. At this time, the number of active users among the users who played against the raid boss that appeared in the past and the number of active users among the users belonging to the same team as the team to which the user belongs are displayed on each of the collaborator icon E82 and the team icon E84. You may. In the illustrated example, the collaborator icon E82 displays the number of active users among the users who have played against the raid boss that appeared in the past, for example, the number label E83 representing eight people, and the team icon E84 indicates the team to which the user belongs. The number of active users among the users belonging to the same team as, for example, the number label E85 representing 5 people is displayed. Here, the active user is a user who has accessed the game within a predetermined time from the current time, for example, within 10 minutes.

[Game system configuration]
Next, an example of the functional configuration of the user terminal 10 and the game server 30 included in the game system 1 will be described.

[Game server function configuration]
FIG. 11 is a schematic block diagram showing an example of the functional configuration of the game server 30 according to the present embodiment.
The game server 30 includes a server control unit 310 as a functional configuration realized by the server CPU 31 executing a game control program stored in the server storage unit 330. The game server 30 includes a server storage unit 330 and a server communication unit 34 in addition to the server control unit 310.

The server communication unit 34 is configured to include, for example, a plurality of Ethernet (registered trademark) ports, a plurality of digital input / output ports such as USB, and the like, and is connected to a user terminal 10 or another device connected via a network NW. Communicate.

The server storage unit 330 includes, for example, an HDD, SSD, EEPROM, ROM, RAM, etc., and includes various information, images, programs, etc. processed by the game server 30, user information acquired from the user terminal 10, and the user terminal 10. Stores various setting information and history information required for processing the executed game. The server storage unit 330 is not limited to the one built in the game server 30, and may be an external storage device connected by a digital input / output port such as USB. Here, the user information is, for example, identification information that identifies a user. For example, the user information has a user ID uniquely assigned to each user, and various parameters in the user's game, a character card that the user can use in the game, and the like are stored in association with each other. The user information is not limited to the user ID but may be a user name or the like as long as the user can be identified.

Next, various setting information and history information of the game stored in the server storage unit 330 will be described in detail. For example, the server storage unit 330 includes a user data storage unit 331, a boss information storage unit 332, a history information storage unit 333, and a team information storage unit 334.

The user data storage unit 331 stores in-game user data related to the user who plays the game on the user terminal 10. The user data storage unit 331 stores the user ID, the user name, the user level, the cost, and the access time in association with each other. The user ID is identification information that identifies the user. The user name is the name of the user, such as a nickname registered in the game. The user level and cost are the above-mentioned user level and cost. The user data storage unit 331 may store a character image for each user such as an avatar in association with the user ID. The access time is information representing the time when the user accesses the game, for example, the time when the user authentication is performed from the user terminal 10 to the game server 30 when the game is started on the user terminal 10, or the user. Information such as the time when the game is started on the terminal 10. The time referred to here includes information such as hours, minutes, and seconds in addition to the year, month, and day.

The boss information storage unit 332 stores the raid boss information in association with the boss ID. The raid boss information includes a raid boss name, a character image, raid boss attribute information (for example, boss attribute), raid boss level information (for example, boss level), initial HP, and the like. Here, the level information is information indicating the difficulty level of the battle. The information indicating the difficulty level of the battle is, for example, information on the ease of subjugation when playing against the NPC, for example, the number of attacks required to subdue the NPC, the amount of damage caused by the attack, or the consumption. It is a measure related to cost, etc. Further, the information indicating the difficulty level of the battle may be, for example, information that gradually expresses a scale related to the number of attacks required to subdue the NPC, the amount of damage caused by the attacks, the cost to be consumed, and the like. ..

In the history information storage unit 333, as history information, the boss ID of the raid boss who fought in the cooperative mission game, the boss level, the boss attribute, the relief status, the battle status information (for example, the battle status), and the battle with the raid boss The user ID of the participating user is stored in association with the user ID. The battle status information is information on the progress status of the battle in the battle with the NPC, and is information indicating what the current state in the battle with the NPC is. The history information storage unit 333 may store the history information for each user, or may store the history information as one table for the entire game without distinguishing between the users. The history information will be described with reference to FIG.

FIG. 12 is a diagram showing an example of a history information table stored in the history information storage unit according to the present embodiment. The illustrated example is an example in which the history information table is stored for each user. The history information storage unit 333 has a boss ID representing the ID of the raid boss, a boss level representing the level of the raid boss, a boss attribute representing the attribute of the raid boss, and a request for participation to another user or a request for relief from another user. The rescue status indicating the status, the battle situation indicating the battle situation with the raid boss, and one or more user IDs as the participants who played against the raid boss in response to the request to participate in the battle with the raid boss are stored in association with each other. Store the history information as a history information table.

A value representing each boss level is stored in the boss level. In the rescue status, a value corresponding to each rescue status is stored as a "request" when another user is requested to participate, and as a "receive" when another user receives a rescue request. In the boss attribute, values corresponding to each boss attribute such as "red", "blue", "yellow", etc. are stored. In the battle situation, "subjugated" indicating that the user has won the raid boss, "escape" indicating that the user could not win the raid boss within the time limit, and being in a battle with the raid boss. As "in battle", the value corresponding to each battle situation is stored. The user ID 1 stores the user ID of the first user who has played against the raid boss and the contribution information (for example, contribution) of the user.

Contribution information is, for example, information on the contribution of each user in a battle with an NPC or points according to the contribution.
The degree of contribution is, for example, points (points) according to the damage points given to the HP of the raid boss, the number of defeated raid bosses for each user or points according to the number, and the defeated raid bosses for each user. Among them, the contribution of each user in the battle with the raid boss, such as the value of the highest boss level or the points according to the boss level, the number of battles with the past raid boss for each user, or the points according to the number of battles, or the said. Points etc. according to the degree of contribution. In this embodiment, an example will be described in which the degree of contribution is a point corresponding to a damage point or the like. The user ID 2 stores the user ID of the second user who has played against the raid boss and the degree of contribution of the user. The same applies to user ID 3 and later. The history information storage unit 333 may store the time limit, the elapsed time (remaining time), and the like in the battle with the raid boss as the history information.

For example, the server control unit 310 extracts the boss ID, the boss level, and the boss attribute from the boss information storage unit 332 and stores them as history information in the history information table. Further, the server control unit 310 stores the rescue status and the battle status with the raid boss as history information in the history information table in association with the boss ID for each user ID of the user who has played against the raid boss of each boss ID. .. Further, the server control unit 310 stores the user ID of the user extracted as the request destination information described later in the history information table in association with the boss ID as the history information. In this way, the server control unit 310 generates history information, and stores the generated history information in the history information storage unit 333.

Returning to FIG. 11, the team information storage unit 334 stores team information in which the team ID for each team and the user ID of the user belonging to the team are associated with each other. In addition, the team information storage unit 334 may directly associate and store the user IDs instead of the team information, or may store a list in which the user IDs of a certain user and the user IDs of other users are associated with each other. , May be stored for each user.

The server control unit 310 controls each unit of the game server 30. The server control unit 310 acquires user information from the user terminal 10 in response to a request from the user terminal 10, and stores the acquired user information in the server storage unit 330. Further, the server control unit 310 acquires various setting information and history information necessary for processing the game executed on the user terminal 10 in response to a request from the user terminal 10, and obtains the acquired various setting information and history information. It is stored in the server storage unit 330 in association with the user information. Further, the server control unit 310 reads the above-mentioned various setting information and history information from the server storage unit 330 and transmits the above-mentioned various setting information and history information to the user terminal 10 in response to a request from the user terminal 10. Further, the server control unit 310 extracts the request destination information based on the history information stored in the history information storage unit 333 according to the instruction from the user terminal 10. It will be explained in more detail.

The server control unit 310 includes an extraction unit 320.
When the extraction unit 320 receives the operation information for selecting the participation request destination from the user terminal 10, the extraction unit 320 extracts the history information from the server storage unit 330. The extraction unit 320 extracts the user ID of the user who requests participation as the request destination information based on the extracted history information. The extraction unit 320 transmits a request for participation in the battle with the raid boss to the other user terminal 10 via the server communication unit 34 to the user with the user ID included in the request destination information. The processing of the extraction unit 320 will be described in more detail.

The extraction unit 320 includes an attribute information extraction unit 321, a level information extraction unit 322, a contribution information extraction unit 323, a battle situation information extraction unit 324, a team information extraction unit 325, and a time information extraction unit 326. Be prepared.
The attribute information extraction unit 321 extracts from the history information a predetermined relationship with the attribute of the current raid boss, for example, the user ID of the user who has played against the raid boss of the same attribute as the request destination information. Even if the attribute information extraction unit 321 extracts from the history information the user ID of the user who has played against the current raid boss attribute and a predetermined relationship, for example, a related attribute, for example, the raid boss of the related attribute, as the request destination information. Alternatively, the user ID of the user, which is an attribute of the character card that is not disadvantageous to the attribute of the current raid boss, may be extracted as the request destination information.

The level information extraction unit 322 extracts from the history information a predetermined relationship with the current level of the raid boss, for example, the user ID of the user who has played against the raid boss of the same level as the request destination information.

From the history information, the level information extraction unit 322 requests the user ID of a user who has a predetermined relationship with the current raid boss level, for example, a user ID having a battle with a raid boss having a level higher than the current raid boss level. Or, the user ID of a user who has played against a raid boss whose level is lower than the current level of the raid boss and who has played a large number of battles with the raid boss may be extracted as request destination information. good.
The level information extraction unit 322 is a user of a user whose user ID is extracted as request destination information by the attribute information extraction unit 321 and has a predetermined relationship with the current raid boss level, for example, a user who has played against a raid boss of the same level. The ID may be extracted as request destination information.

The contribution information extraction unit 323 extracts the contribution of each user in the battle with the past raid boss from the history information, and obtains the user ID of the user whose contribution is in a predetermined state, for example, the contribution is higher than the predetermined value. Extract as request destination information.
The contribution information extraction unit 323 extracts the contribution of each user in the battle with the past raid boss from the history information, and requests the user ID in the predetermined state of the contribution, for example, in the order of the user with the highest contribution. It may be extracted as information, or the user ID of a user whose contribution degree is within a predetermined range, for example, a predetermined value + 5% to a predetermined value −5% may be extracted as request destination information. In the contribution information extraction unit 323, among the user IDs included in the request destination information extracted by either or both of the attribute information extraction unit 321 and the level information extraction unit 322, the contribution degree in the past battle with the raid boss is The user ID of a high user may be extracted as the request destination information.

The battle status information extraction unit 324 extracts from the history information a user ID whose battle status is a predetermined state, for example, "subjugated" in a battle with a past raid boss as request destination information. The battle status information extraction unit 324 is a past raid boss among the user IDs included in the request destination information extracted by any or all of the attribute information extraction unit 321 and the level information extraction unit 322 and the contribution information extraction unit 323. In the battle with, the user ID whose battle status is a predetermined state, for example, "subjugated" may be extracted as the request destination information.
The battle status information extraction unit 324 may extract the request destination information by excluding the user ID of the user whose battle status is a predetermined state, for example, "escape" in the battle with the raid boss in the past.
In addition, the battle status information extraction unit 324 uses the user ID of the user who has played against the raid boss, which has a short time to win the raid boss (the battle status status has been subdued), as the request destination information in the battle with the raid boss in the past. It may be extracted.

The team information extraction unit 325 refers to the team information stored in the team information storage unit 334, and extracts a predetermined relationship between the user ID and the user ID, for example, the user ID associated with the user ID, as the request destination information from the history information. More specifically, the team information extraction unit 325 refers to the team information from the history information, and requests a predetermined relationship with the user ID, for example, a user ID belonging to the same team or a user ID belonging to a different team. Extract as. The team information extraction unit 325 is a user ID included in the request destination information extracted by any or all of the attribute information extraction unit 321, the level information extraction unit 322, the contribution degree information extraction unit 323, and the battle status information extraction unit 324. Among them, a user ID having a predetermined relationship with the user ID and belonging to the same team or a different team may be extracted as request destination information.

The time information extraction unit 326 extracts the user ID of the user whose access time included in the user data stored in the user data storage unit 331 is within a predetermined time from the current time, for example, within 10 minutes as the request destination information. The time information extraction unit 326 is a request destination extracted by any or all of the attribute information extraction unit 321, the level information extraction unit 322, the contribution information extraction unit 323, the battle situation information extraction unit 324, and the team information extraction unit 325. Among the user IDs included in the information, the user IDs of users whose access time is within a predetermined time, for example, 10 minutes or less may be extracted as request destination information.

An example of the case where the extraction unit 320 includes an attribute information extraction unit 321, a level information extraction unit 322, a contribution information extraction unit 323, a battle status information extraction unit 324, a team information extraction unit 325, and a time information extraction unit 326. As described above, the configuration includes only a part of the attribute information extraction unit 321, the level information extraction unit 322, the contribution information extraction unit 323, the battle status information extraction unit 324, the team information extraction unit 325, and the time information extraction unit 326. May be.

[Functional configuration of user terminal]
FIG. 13 is a schematic block diagram showing an example of the functional configuration of the user terminal 10 according to the present embodiment.
The user terminal 10 includes a communication unit 12, an input unit 13, a display unit 14, a storage unit 15, and a control unit 110.
The user terminal 10 includes a control unit 110 as a functional configuration realized by the CPU 11 executing a game control program stored in the storage unit 15. The control unit 110 processes the game based on the game control program according to the user's operation on the input unit 13. The control unit 110 causes the display unit 14 to display a game screen corresponding to the processing of the game. Further, the control unit 110 transmits various setting information and history information according to the processing of the game to the game server 30 via the communication unit 12, and also sends various setting information and history information to the communication unit 12 as necessary. Is acquired (extracted) from the game server 30 via. A part or all of the control unit 110 may be realized as an integrated circuit of hardware such as an LSI (Large Scale Integration) or an ASIC (Application Specific Integrated Circuit).

For example, the control unit 110 controls the above-mentioned cooperative mission battle game. Specifically, character cards are given, mission rewards are given, card composition, deck organization, game processing such as battles and cooperative mission games, and various game screens are displayed according to those game processing. Here, the configuration of the cooperative mission game will be described in detail. For example, the control unit 110 includes a reception unit 120, a game processing unit 130, a display control unit 140, a presentation unit 160, a setting unit 170, and a specific unit 180.

The reception unit 120 receives various instructions input to the input unit 13 by the user's operation. For example, the reception unit 120 receives an instruction to select a participation request destination based on the user operation of requesting all users, cooperators, or team users to participate in the battle with the raid boss. The reception unit 120 may receive an instruction based on the user's operation on the presentation by the presentation unit 160.

The game processing unit 130 controls to execute the game. The game processing unit 130 performs game processing such as granting character cards, granting mission rewards, card composition, deck organization, and battle. The game processing unit 130 may perform substantial processing for advancing each game on its own device, or may perform auxiliary processing for advancing each game on the game server 30. For example, the game processing unit 130 may complete the processing for advancing the game only by its own device. In the present embodiment, as an example, a case where the game server 30 performs substantial game processing will be described.

The display control unit 140 performs display control for displaying various game screens on the display unit 14. Specifically, the display control unit 140 generates a game screen. The display control unit 140 outputs the generated image data of the game screen to the display unit 14 to display the game screen.

The presentation unit 160 presents various information to the user. The presentation unit 160 will be described in more detail. The presentation unit 160 includes a first presentation unit 161 and a second presentation unit 162.
The first presentation unit 161 receives the request destination information from the game server 30. The first presentation unit 161 acquires related information corresponding to the user ID included in the request destination information, for example, an image of an avatar from the game server 30, and presents the acquired image of the avatar as an operator selectable by the user. do. Here, the related information corresponding to the user ID (related information corresponding to the information for identifying the user) is the corresponding information such as an image and a user name associated with the user's identification information. The correspondence information represents, for example, an image of an avatar corresponding to a user ID (user's icon image), a user name corresponding to the user ID, an image of a deck character card corresponding to the user ID, the user ID itself, and the user ID. Information associated with a user ID such as a character string. Presenting in a selectable manner (presenting in a selectable manner) means, for example, presenting correspondence information as an operator.

The first presentation unit 161 acquires related information corresponding to the user ID included in the request destination information, for example, a user name from the game server 30, and presents the acquired user name as an operator selectable by the user. Alternatively, related information corresponding to the user ID, for example, an image of the user's character guard may be acquired from the game server 30, and the acquired image of the user's character guard may be presented as an operator selectable by the user. May be good.

The second presentation unit 162 acquires related information corresponding to the user ID including the request destination information, for example, an image of an avatar from the game server 30. Further, the second presentation unit 162 acquires the contribution degree information corresponding to the user ID included in the request destination information from the history information. The second presentation unit 162 presents the acquired image of the avatar and the contribution degree information as an operator that can be selected by the user in association with each other. Corresponding the image of the avatar with the contribution information ((associating the related information (correspondence information) corresponding to the information for identifying the user with the contribution information) means superimposing the contribution information on the correspondence information. Contribution information is attached to the correspondence information, such as an image generated as described above or an image generated so that the correspondence between the correspondence information and the contribution information can be visually recognized.
In addition, the second presentation unit 162 acquires the user name, the image of the user's character card, the contribution degree information, the number of battles with the past raid boss, etc. from the game server 30, and the acquired user name and the user. It may be presented as an operator selectable by the user in association with the image of the character card or the like, the contribution degree information, the number of battles with the raid boss in the past, and the like.

In this embodiment, an example of the case where the presentation unit 160 is provided will be described, but the user terminal 10 does not have to include the presentation unit 160. In this case, the game server 30 may send a request to participate in the battle with the raid boss to the user terminal 10 of the user ID included in the request destination information based on the request destination information.

The setting unit 170 transmits the information input on the automatic participation request setting screen shown in FIG. 9 to the game server 30 and sets it as a condition for extracting the request destination information by the game server 30. In this embodiment, an example of the case where the setting unit 170 is provided will be described, but the user terminal 10 does not have to include the setting unit 170. In this case, the game server 30 may extract the request destination information based on the extraction conditions set in advance.

The specific unit 180 identifies which user ID the instruction is based on the instruction corresponding to the user operation for the presentation of the presentation unit 160. The identification unit 180 transmits information that can identify the specified user ID to the game server 30. In this embodiment, an example of the case where the specific unit 180 is provided will be described, but the user terminal 10 does not have to include the specific unit 180. Further, when the specific unit 180 is provided, the game server 30 does not make a participation request based on the request destination information extracted by the game server 30, but makes a participation request based on the request destination information specified by the specific unit 180. May be good.

Next, the operation of the cooperative mission game executed by the user terminal 10 according to the present embodiment will be described.

[Operation of game processing]
FIG. 14 is a flowchart showing an example of game processing of the cooperative mission game according to the present embodiment.
First, the display control unit 140 displays the home screen G10 on the display unit 14 when the cooperative mission game is started (step S100).
Next, the control unit 110 determines whether or not the operation instruction for requesting another user to participate in the battle with the raid boss has been received via the input unit 13 by the user's operation on the home screen G10 (step S102). ..

Here, the operation instruction for requesting other users to participate in the battle with the raid boss is, for example, an operation for making all user icons E35 as an operator for making all users the request destination, and an operation for making a collaborator a request destination. It is instructed by a tap operation on either the collaborator icon E36 as a child or the team icon E37 as an operator for making the team a request destination. When it is determined in step S102 that an operation instruction for requesting participation in the battle with the raid boss has been received (step S102: YES), the control unit 110 extracts any request destination information. The end process includes various setting processes based on the progress of the game immediately before the end and a process of transmitting history information and the like to the game server 30 as needed.

On the other hand, if it is determined in step S102 that the operation instruction for requesting participation in the battle with the raid boss is not accepted (step S102: NO), the control unit 110 ends the participation request. The end process includes various setting processes and a process of transmitting history information and the like to the game server 30 as needed.
Next, in step S102, when it is determined that the operation instruction requesting the other user to participate in the battle with the raid boss is accepted (step S102: YES), the control unit 110 sends the battle with the raid boss to the other user. It is determined whether or not the operation instruction requesting the participation of the user is an instruction to request all users (step S104).

In step S104, when it is determined that the reception unit 120 has received the instruction to request all users via the input unit 13 (step S104: YES), the control unit 110 requests all users to the game server 30. Send the operation information. The extraction unit 320, which has received the operation information for all users as the request destination, randomly extracts a predetermined number of user IDs as the request destination information from the user IDs of all the users (step S106).
The extraction unit 320 transmits as a participation request to the user terminal 10 of the user ID included in the extracted request destination information via the server communication unit 34 (step S108).
After that, the control unit 110 executes the termination process.

On the other hand, when it is determined in step S104 that the reception unit 120 has not received an instruction for all users as a request destination via the input unit 13 (step S104: NO), the reception unit 120 inputs the control unit 110. It is determined whether or not the instruction to the team as the request destination is received through the unit 13 (step S110).
In step S110, when it is determined that the reception unit 120 has received the instruction to request the team via the input unit 13 (step S110: YES), the control unit 110 makes the team the request destination to the game server 30. Send operation information. The extraction unit 320 that has received the operation information for which the team is the request destination extracts the team information (step S112). Then, the extraction unit 320 refers to the extracted team information and extracts the user ID belonging to the same team as the request destination information (step S114).
The extraction unit 320 transmits as a participation request to the user terminal 10 of the user ID included in the extracted request destination information via the server communication unit 34 (step S116).
After that, the control unit 110 executes the termination process.

On the other hand, when it is determined in step S110 that the reception unit 120 has not received an instruction to request the team via the input unit 13 (step S110: NO), the reception unit 120 is the input unit of the control unit 110. It is determined whether or not the instruction to the collaborator as the request destination is received through 13 (step S118).
When it is determined in step S118 that the reception unit 120 has received the instruction to request the cooperator via the input unit 13 (step S118: YES), the control unit 110 requests the cooperator from the game server 30. Send the operation information. The extraction unit 320 that has received the operation information for which the collaborator is the request destination extracts the history information (step S120). Then, a part or all of the attribute information extraction unit 321, the level information extraction unit 322, the contribution information extraction unit 323, the battle situation information extraction unit 324, the team information extraction unit 325, and the time information extraction unit 326 are predetermined conditions. The user ID that satisfies the conditions is extracted as the request destination information (step S122). The predetermined conditions are the above-mentioned attributes of the current raid boss and a predetermined relationship, for example, a user ID of a user who has played against a raid boss of the same attribute, a predetermined relationship with the level of the current raid boss, for example, a raid boss of the same level. The user ID of the user and the contribution of each user in the battle with the past raid boss are extracted, and the battle situation is in a predetermined state, for example, the user ID of the user with a high contribution and the battle with the past raid boss. A user ID that is in a predetermined state, for example, "subjugated", a user ID associated with the user ID, for example, a user ID associated with the user ID, a user ID of a user whose access time is within a predetermined time, for example, within 10 minutes, etc. It is a condition.

The extraction unit 320 transmits as a participation request to the user terminal 10 of the user ID included in the extracted request destination information via the server communication unit 34 (step S124).
After that, the control unit 110 executes the termination process.

[Summary of the first embodiment]
(1) As described above, the game system 1 according to the present embodiment is a game system 1 in which a plurality of users cooperate to execute a game in which a game is played against an NPC, and is a reception desk that accepts an operation of a first user. Information for identifying the first user who has played against the first NPC (for example, a past raid boss) (for example, a user ID) and information for identifying a second user who has played against the first NPC (for example, for example). The storage unit (for example, the server storage unit 330) that associates with the user ID of another user and stores it as history information about the battle, and the reception unit 120 enters the battle with the second NPC (for example, the current raid boss). When the operation of requesting participation from another user is accepted, the extraction unit 320 is provided with information for identifying the second user based on the history information as the request destination information.

As a result, when the first user requests participation in the battle with the second NPC, the game system 1 can extract the second user who has played with the first NPC that appeared in the past as the request destination. Since the first user and the second user have a history of playing against the same first NPC in the past, there is a high possibility that they will cooperate with each other.
That is, the game system 1 can combine users who have similar battle experience with users who cooperate with each other in a battle with the second NPC.
For example, when the game system 1 requests participation in a battle with a second boss (an example of a second NPC), the request destination is based on historical information with the first boss (an example of the first NPC) in cooperation with the past. Can be decided. In this way, the game system 1 requests relief based on the history information of past battles.
As a result, the game system 1 has played against the participation request user (an example of the second user) in response to the participation request and the participation request user (an example of the first user) in response to the participation request. The possibility of subduing the second boss by the user (an example of the second user) can be improved as compared with the case where the second boss is not based on the history information.
Further, the game system 1 can also use this participation request as an opportunity to activate communication between the user who requested the participation and the user who received the participation request.

(2) Further, in the game system 1 according to the present embodiment, the information for identifying the second user included in the history information is the attribute information of the first NPC in which the second user has played (for example, the attribute information of the past raid boss). ), The extraction unit 320 extracts the request destination information based on the attribute information of the first NPC and the attribute information of the second NPC (for example, the attribute information of the current raid boss), and the attribute information of the first NPC. , And the attribute information of the second NPC are information representing the attribute of the first NPC and information representing the attribute of the second NPC, respectively.

Thereby, the game system 1 can appropriately extract the information for identifying the second user included in the history information according to the attribute of the NPC. In addition, the game system 1 can extract information for identifying a second user who is likely to be advantageous to the attributes of the NPC.

(3) Further, in the game system 1 according to the present embodiment, the information for identifying the second user included in the history information is associated with the level information of the first NPC in which the second user has played, and the extraction unit 320 is used. Request destination information is extracted based on the level information of the first NPC and the level information of the second NPC, and the level information of the first NPC and the level information of the second NPC are information on the difficulty level of the battle with the NPC. ..

As a result, the game system 1 can appropriately extract the request destinations according to the level of the NPCs to be played against. In addition, the game system 1 can extract information that identifies a second user who is easier to subdue (which is likely to be advantageous in the battle with the NPC) when the game is played against the NPC.

(4) Further, in the game system 1 according to the present embodiment, the information for identifying the second user included in the history information is associated with the contribution information regarding the battle of the second user with the first NPC, and the extraction unit 320. Extracts request destination information based on contribution information.

As a result, the game system 1 can extract, for example, a second user having a high degree of contribution. The second user with a high degree of contribution is likely to have played against NPCs multiple times in the past, or is likely to be using a deck configuration with character cards with high offensive and defensive power, so NPCs. There is a high possibility that it will be advantageous for the match against. Therefore, the game system 1 can extract the identification information of the second user, which is advantageous for the battle with the NPC.

(5) Further, in the game system 1 according to the present embodiment, the information for identifying the second user included in the history information is associated with the battle status information of the first NPC in which the second user has played, and the extraction unit 320 is used. , The request destination information is extracted based on the battle situation information included in the history information.

As a result, the game system 1 can extract a user according to the battle situation with the past NPC as a request destination. Specifically, the game system 1 provides information for identifying a second user who has cooperated in a past battle with an NPC, for example, even when the remaining time of the battle with the NPC is short. Information that identifies a second user who has subdued NPCs multiple times can be extracted. Further, since the game system 1 can extract information for identifying the second user excluding the user who could not be subdued by the battle situation information, the identification information of the second user which is advantageous for the battle with the NPC Can be extracted.

(6) Further, in the game system 1 according to the present embodiment, the extraction unit 320 extracts the request destination information by excluding the information for identifying the identifiable second user from the information for identifying the first user. do.

As a result, the game system 1 can extract a desired user as a request destination. For example, the game system 1 may extract information for identifying a second user, such as the same team as the first user, a different team, a friend, etc., which is associated with the information for identifying the first user. can. When extracting information for identifying a friend or a second user of the same team, the relationship between the team member and the first user can be improved. When extracting information to identify a second user on a different team, it is possible to provide an opportunity to belong to a friend or the same team. A friend is a relationship in which users can connect and communicate with each other on social media and games.

(7) Further, in the game system 1 according to the present embodiment, the storage unit (for example, the server storage unit 330) further stores a plurality of team information associated with information for identifying the user, and the extraction unit 320 further stores the team information. , Information for identifying the second user of the second user who belongs to a team different from the team of the first user is extracted as the request destination information based on the team information.

As a result, the game system 1 can utilize the transfer to another team or the like. Information for identifying a second user associated with information for identifying the same team as the first user, a different team, and the first user can be extracted. F. When extracting information for identifying a second user of the same team, the relationship between the team member and the first user can be improved. When extracting information for identifying a second user of a different team, it is possible to provide an opportunity to belong to the same team (an opportunity to transfer a team).

(8) Further, in the game system 1 according to the present embodiment, the storage unit (for example, the server storage unit 330) further stores a plurality of team information associated with information for identifying the user, and the extraction unit 320 further stores the team information. , Extract request destination information based on the number of information to identify the user associated with the team information.

Thereby, the game system 1 can provide an opportunity to transfer from a team having few team members or a team having many team members to another team, for example.

(9) Further, in the game system 1 of the present embodiment, the extraction unit 320 extracts the request destination information based on the information regarding the access time to the game associated with the information for identifying the second user.

As a result, the game system 1 can extract the active user as the request destination. Specifically, since the information for identifying the second user who is the active user or the second user can be extracted, the second user who is likely to be able to subdue the NPC faster and faster. Information for identifying the user can be extracted.

(10) In the game system 1 of the present embodiment, the game system 1 includes a first presentation unit 161 that presents related information corresponding to the information for identifying the second user extracted by the extraction unit 320 in a selectable manner. A specific unit for specifying a request transmission destination based on an operation on the related information presented by the first presentation unit 161 of the first user is provided.

As a result, the game system 1 can extract a desired user as a request destination. Specifically, since the game system 1 allows the user to select which second user is requested to participate, information for identifying the second user according to the user's request is extracted. can do.

(11) In the game system 1 of the present embodiment, based on the operation of the first user, the attribute information of the first NPC, the attribute information of the second NPC, the level information of the first NPC, the level information of the second NPC, and the battle situation of the first NPC. Further, a setting unit 170 for setting at least one of the information and the battle status information of the second NPC as a condition is further provided, and at least of the attribute information of the second NPC, the level information of the second NPC, and the battle status information of the second NPC. Information that requests the user terminal 10 in which the information for identifying the second user extracted by the extraction unit 320 is set based on the comparison with one piece of information to participate in the battle with the second NPC. A transmission unit (server communication unit 34) for transmitting information is provided.

As a result, the game system 1 can extract information for identifying a second user who satisfies a preset condition, so that user operations such as selection of a request destination can be omitted. Therefore, it is possible to improve the operability of the user in the game.

(12) Further, in the game system 1 of the present embodiment, based on the history information, the information regarding the information for identifying the second user is combined with the contribution degree information associated with the information for identifying the second user. A second presentation unit 162 that is associated and presented is provided.

As a result, the game system 1 allows the user to select a user with a high degree of contribution, so that the game entertainment can be improved. Specifically, the game system 1 allows the user to select which second user to request participation while checking the contribution information, so that the second user meets the user's request. Information for identifying, for example, information for identifying a second user of a user with a higher contribution can be extracted.

(13) Further, in the game system 1 of the present embodiment, the user terminal in which the information for identifying the second user extracted by the extraction unit 150 is set is requested to participate in the battle with the second NPC. A second presenting unit 162 that presents information in a manner capable of instructing transmission is provided, and the second presenting unit presents a number based on the information regarding the access time.

As a result, the game system 1 can select a request destination in which the user has more active users in the battle with the NPC, for example, according to the time limit in the battle with the NPC. In addition, since it is possible to select a request destination with more active users, it is possible to extract information for identifying a second user who is likely to be able to subdue NPCs earlier.

(14) Further, in the game device (for example, the game server 30) in the present embodiment, the game device is a game device in which a plurality of users cooperate to play a game against an NPC, and the game device (for example, the game server 30). Is a reception unit (server communication unit 34) that receives operation information of the first user, information for identifying the first user who has played against the first NPC, and information for identifying the second user who has played against the first NPC. The storage unit (server storage unit 330) that stores the information as history information related to the battle and the reception unit (server communication unit 34) request the other users to participate in the battle with the second NPC. When received, the extraction unit 320 is provided with information for identifying the second user based on the history information as request destination information.

By doing so, in the game device, even a user who cannot obtain the cooperation of another user in the battle with the NPC can request the other user to participate in the battle with the NPC. It is possible to improve the game entertainment of. In addition, by using the history information, it is possible to extract other users who are advantageous to the user in the battle with the NPC as the request destination.
For example, conventionally, a user who is not blessed with a cooperative user may not be able to obtain cooperation from other users in a battle with an NPC, which may lead to a decrease in the user's play interest. In this embodiment, such a conventional problem can be solved.

Further, when the first user requests participation in the battle with the second NPC, the game server 30 can extract the second user who has played against the same first NPC as the request destination. Since the first user and the second user have a history of playing against the same first NPC in the past, there is a high possibility that they will cooperate with each other.
That is, the game server 30 can combine users who have similar battle experience with users who cooperate with each other in the battle with the second NPC.
For example, when the game server 30 requests participation in a battle with the second boss (an example of the second NPC), the game server 30 cooperates in the past and requests the request destination based on the history information with the first boss (an example of the first NPC). Can be decided. In this way, the game server 30 requests relief based on the history information of past battles.
As a result, the game server 30 has played against the participation request user (an example of the second user) in response to the participation request and the participation request user (an example of the first user) in response to the participation request. The possibility of subduing the second boss by the user (an example of the second user) can be improved as compared with the case where the second boss is not based on the history information.
Further, the game server 30 can also use this participation request as an opportunity to activate communication between the user who requested the participation and the user who received the participation request.

Hereinafter, the second embodiment of the present invention will be described with reference to the drawings.
[Second Embodiment]
In the second embodiment, the case where the user terminal 10 includes the extraction unit 150 instead of the extraction unit 320 provided in the game server 30 will be described in the first embodiment. By doing so, the processing load on the game server 30 can be reduced. In the second embodiment, the parts different from the first embodiment will be mainly described.

[Game server function configuration]
FIG. 15 is a schematic block diagram showing an example of the functional configuration of the game server 30A according to the present embodiment.
The game server 30A includes a server control unit 310, a server communication unit 34, and a server storage unit 330.
Comparing the functional configuration of the game server 30 according to the first embodiment with the functional configuration of the game server 30A according to the second embodiment, the difference is that the game server 30A does not include the extraction unit 320. Since the other configurations are the same as those of the game server 30, the description thereof will be omitted.

[Functional configuration of user terminal]
FIG. 16 is a schematic block diagram showing an example of the functional configuration of the user terminal 10A according to the present embodiment.
The user terminal 10A includes a communication unit 12, an input unit 13, a display unit 14, a storage unit 15, and a control unit 110.
Here, comparing the functional configuration of the user terminal 10 according to the first embodiment with the functional configuration of the user terminal 10A according to the second embodiment, the control unit 110 of the user terminal 10A includes the extraction unit 150. Is different. Since the other configurations are the same, the parts different from the first embodiment will be mainly described.

For example, the control unit 110 controls the above-mentioned cooperative mission battle game. Specifically, character cards are given, mission rewards are given, card composition, deck organization, game processing such as battles and cooperative mission games, and various game screens are displayed according to those game processing. Here, the configuration of the cooperative mission game will be described in detail. For example, the control unit 110 includes a reception unit 120, a game processing unit 130, a display control unit 140, an extraction unit 150, a presentation unit 160, a setting unit 170, and a specific unit 180.

When the reception unit 120 receives an instruction to select a participation request destination, the extraction unit 150 acquires history information from the game server 30 via the communication unit 12. The extraction unit 150 extracts the user ID of the user requesting participation as the request destination information based on the acquired history information. The extraction unit 150 transmits the extracted request destination information to the communication unit 12 and the game server 30. Upon receiving the request destination information, the game server 30 transmits a request for participation in the battle with the raid boss to the user with the user ID included in the request destination information. The processing of the extraction unit 150 will be described in more detail.

The extraction unit 150 includes an attribute information extraction unit 151, a level information extraction unit 152, a contribution information extraction unit 153, a battle situation information extraction unit 154, a team information extraction unit 155, and a time information extraction unit 156. Be prepared.
The attribute information extraction unit 151 extracts the user ID of the user who has played against the raid boss of the same attribute, for example, the user ID of the user who has played against the raid boss of the same attribute, as the request destination information, from the acquired history information. Even if the attribute information extraction unit 151 extracts from the history information the user ID of the user who has played against the current raid boss attribute and a predetermined relationship, for example, a related attribute, for example, the raid boss of the related attribute, as the request destination information. Alternatively, the user ID of the user, which is an attribute of the character card that is not disadvantageous to the attribute of the current raid boss, may be extracted as the request destination information.

The level information extraction unit 152 extracts from the acquired history information a predetermined relationship with the current raid boss level, for example, a user ID of a user who has played against a raid boss of the same level as request destination information.

From the history information, the level information extraction unit 152 requests the user ID of a user who has a predetermined relationship with the current raid boss level, for example, a user ID having a battle with a raid boss having a level higher than the current raid boss level. Or, the user ID of a user who has played against a raid boss whose level is lower than the current level of the raid boss and who has played a large number of battles with the raid boss may be extracted as request destination information. good.
The level information extraction unit 152 is a user of a user whose user ID is extracted as request destination information by the attribute information extraction unit 151 and has a predetermined relationship with the current raid boss level, for example, a user who has played against a raid boss of the same level. The ID may be extracted as request destination information.

The contribution information extraction unit 153 extracts the contribution of each user in the battle with the past raid boss from the acquired history information, and the user of the user whose contribution is in a predetermined state, for example, the contribution is higher than the predetermined value. The ID is extracted as the request destination information.
The contribution information extraction unit 153 extracts the contribution of each user in the battle with the past raid boss from the history information, and requests the user ID in the predetermined state of the contribution, for example, in the order of the user with the highest contribution. It may be extracted as information, or the user ID of a user whose contribution degree is within a predetermined range, for example, a predetermined value + 5% to a predetermined value −5% may be extracted as request destination information. In the contribution information extraction unit 153, among the user IDs included in the request destination information extracted by either or both of the attribute information extraction unit 151 and the level information extraction unit 152, the contribution degree in the past battle with the raid boss is The user ID of a high user may be extracted as the request destination information.

The battle status information extraction unit 154 extracts from the acquired history information a user ID whose battle status is a predetermined state, for example, "subjugated" in a battle with a raid boss in the past, as request destination information.
The battle status information extraction unit 154 is a past raid boss among the user IDs included in the request destination information extracted by any or all of the attribute information extraction unit 151, the level information extraction unit 152, and the contribution information extraction unit 153. In the battle with, the user ID whose battle status is a predetermined state, for example, "subjugated" may be extracted as the request destination information.
The battle status information extraction unit 154 may extract the request destination information by excluding the user ID of the user whose battle status is a predetermined state, for example, "escape" in the battle with the raid boss in the past.
The battle status information extraction unit 154 uses the user ID of the user who has played against the raid boss, which has a short time to win the raid boss (the battle status has been subdued) in the past battle with the raid boss, as the request destination information. It may be extracted.

The team information extraction unit 155 refers to the team information acquired from the game server 30A, and extracts a predetermined relationship between the user ID and the user ID, for example, the user ID associated with the user ID, as the request destination information from the history information. More specifically, the team information extraction unit 155 requests a predetermined relationship with the user ID, for example, a user ID belonging to the same team or a user ID belonging to a different team, with reference to the team information from the acquired history information. Extract as destination information. The team information extraction unit 155 is a user ID included in the request destination information extracted by any or all of the attribute information extraction unit 151, the level information extraction unit 152, the contribution information extraction unit 153, and the battle status information extraction unit 154. Among them, a user ID having a predetermined relationship with the user ID and belonging to the same team or a different team may be extracted as request destination information.

The time information extraction unit 156 extracts the user ID of the user whose access time included in the user data acquired from the game server 30A is within a predetermined time, for example, 10 minutes or less, as the request destination information. The time information extraction unit 156 is a request destination extracted by any or all of the attribute information extraction unit 151, the level information extraction unit 152, the contribution information extraction unit 153, the battle situation information extraction unit 154, and the team information extraction unit 155. Among the user IDs included in the information, the user IDs of users whose access time is within a predetermined time, for example, 10 minutes or less may be extracted as request destination information.

An example of the case where the extraction unit 150 includes an attribute information extraction unit 151, a level information extraction unit 152, a contribution information extraction unit 153, a battle status information extraction unit 154, a team information extraction unit 155, and a time information extraction unit 156. As described above, the configuration includes only a part of the attribute information extraction unit 151, the level information extraction unit 152, the contribution information extraction unit 153, the battle situation information extraction unit 154, the team information extraction unit 155, and the time information extraction unit 156. May be.

Since the operation of the cooperative mission game executed by the user terminal 10A according to the present embodiment is the same as the game processing described with reference to FIG. 13, description and illustration are omitted.

[Summary of the second embodiment]
(1) As described above, the game system 1 according to the present embodiment is a game system 1 in which a plurality of users cooperate to execute a game in which a game is played against an NPC, and is a reception desk that accepts an operation of a first user. Information for identifying the first user who has played against the first NPC (for example, a past raid boss) (for example, a user ID) and information for identifying a second user who has played against the first NPC (for example, for example). The storage unit (for example, the server storage unit 330) that associates with the user ID of another user and stores it as history information about the battle, and the reception unit 120 enters the battle with the second NPC (for example, the current raid boss). When an operation for requesting participation from another user is accepted, the extraction unit 150 for extracting information for identifying the second user based on the history information as request destination information is provided.

As a result, when the first user requests participation in the battle with the second NPC, the game system 1 can extract the second user who has played with the first NPC that appeared in the past as the request destination. Since the first user and the second user have a history of playing against the same first NPC in the past, there is a high possibility that they will cooperate with each other.
That is, the game system 1 can combine users who have similar battle experience with users who cooperate with each other in a battle with the second NPC.
For example, when the game system 1 requests participation in a battle with a second boss (an example of a second NPC), the request destination is based on historical information with the first boss (an example of the first NPC) in cooperation with the past. Can be decided. In this way, the game system 1 requests relief based on the history information of past battles.
As a result, the game system 1 has played against the participation request user (an example of the second user) in response to the participation request and the participation request user (an example of the first user) in response to the participation request. The possibility of subduing the second boss by the user (an example of the second user) can be improved as compared with the case where the second boss is not based on the history information.
Further, the game system 1 can also use this participation request as an opportunity to activate communication between the user who requested the participation and the user who received the participation request.

(2) Further, in the game system 1 according to the present embodiment, the information for identifying the second user included in the history information is the attribute information of the first NPC in which the second user has played (for example, the attribute information of the past raid boss). ), The extraction unit 150 extracts the request destination information based on the attribute information of the first NPC and the attribute information of the second NPC (for example, the attribute information of the current raid boss), and the attribute information of the first NPC. , And the attribute information of the second NPC are information representing the attribute of the first NPC and information representing the attribute of the second NPC, respectively.

Thereby, the game system 1 can appropriately extract the information for identifying the second user included in the history information according to the attribute of the NPC. In addition, the game system 1 can extract information for identifying a second user who is likely to be advantageous to the attributes of the NPC.

(3) Further, in the game system 1 according to the present embodiment, the information for identifying the second user included in the history information is associated with the level information of the first NPC in which the second user has played, and the extraction unit 150 is used. Request destination information is extracted based on the level information of the first NPC and the level information of the second NPC, and the level information of the first NPC and the level information of the second NPC are information on the difficulty level of the battle with the NPC. ..

As a result, the game system 1 can appropriately extract the request destinations according to the level of the NPCs to be played against. In addition, the game system 1 can extract information that identifies a second user who is easier to subdue (which is likely to be advantageous in the battle with the NPC) when the game is played against the NPC.

(4) Further, in the game system 1 according to the present embodiment, the information for identifying the second user included in the history information is associated with the contribution information regarding the battle of the second user with the first NPC, and the extraction unit 150. Extracts request destination information based on contribution information.

As a result, the game system 1 can extract, for example, a second user having a high degree of contribution. The second user with a high degree of contribution is likely to have played against NPCs multiple times in the past, or is likely to be using a deck configuration with character cards with high offensive and defensive power, so NPCs. There is a high possibility that it will be advantageous for the match against. Therefore, the game system 1 can extract the identification information of the second user, which is advantageous for the battle with the NPC.

(5) Further, in the game system 1 according to the present embodiment, the information for identifying the second user included in the history information is associated with the battle status information of the first NPC in which the second user has played, and the extraction unit 150 is used. , The request destination information is extracted based on the battle situation information included in the history information. Further, since the game system 1 can extract information for identifying the second user excluding the user who could not be subdued by the battle situation information, the identification information of the second user which is advantageous for the battle with the NPC Can be extracted.

As a result, the game system 1 can extract a user according to the battle situation with the past NPC as a request destination. Specifically, the game system 1 provides information for identifying a second user who has cooperated in a past battle with an NPC, for example, even when the remaining time of the battle with the NPC is short. Information that identifies a second user who has subdued NPCs multiple times can be extracted.

(6) Further, in the game system 1 according to the present embodiment, the extraction unit 150 extracts the request destination information by excluding the information for identifying the identifiable second user from the information for identifying the first user. do.

As a result, the game system 1 can extract a desired user as a request destination. For example, the game system 1 may extract information for identifying a second user, such as the same team as the first user, a different team, a friend, etc., which is associated with the information for identifying the first user. can. When extracting information for identifying a friend or a second user of the same team, the relationship between the team member and the first user can be improved. When extracting information to identify a second user on a different team, it is possible to provide an opportunity to belong to a friend or the same team. A friend is a relationship in which users can connect and communicate with each other on social media and games.

(7) Further, in the game system 1 according to the present embodiment, the storage unit (for example, the server storage unit 330) further stores a plurality of team information associated with information for identifying the user, and the extraction unit 150 further stores the team information. , Information for identifying the second user of the second user who belongs to a team different from the team of the first user is extracted as the request destination information based on the team information.

As a result, the game system 1 can utilize the transfer to another team or the like. Information for identifying a second user associated with information for identifying the same team as the first user, a different team, and the first user can be extracted. F. When extracting information for identifying a second user of the same team, the relationship between the team member and the first user can be improved. When extracting information for identifying a second user of a different team, it is possible to provide an opportunity to belong to the same team (an opportunity to transfer a team).

(8) Further, in the game system 1 according to the present embodiment, the storage unit (for example, the server storage unit 330) further stores a plurality of team information associated with information for identifying the user, and the extraction unit 150 further stores the team information. , Extract request destination information based on the number of information to identify the user associated with the team information.

Thereby, the game system 1 can provide an opportunity to transfer from a team having few team members or a team having many team members to another team, for example.

(9) Further, in the game system 1 of the present embodiment, the extraction unit 150 extracts the request destination information based on the information regarding the access time to the game associated with the information for identifying the second user.

As a result, the game system 1 can extract the active user as the request destination. Specifically, since the information for identifying the second user who is the active user or the second user can be extracted, the second user who is likely to be able to subdue the NPC faster and faster. Information for identifying the user can be extracted.

(10) In the game system 1 of the present embodiment, the game system 1 includes a first presentation unit 161 that presents related information corresponding to the information for identifying the second user extracted by the extraction unit 150 in a selectable manner. A specific unit for specifying a request transmission destination based on an operation on the related information presented by the first presentation unit 161 of the first user is provided.

As a result, the game system 1 can extract a desired user as a request destination. Specifically, since the game system 1 allows the user to select which second user is requested to participate, information for identifying the second user according to the user's request is extracted. can do.

(11) In the game system 1 of the present embodiment, based on the operation of the first user, the attribute information of the first NPC, the attribute information of the second NPC, the level information of the first NPC, the level information of the second NPC, and the battle situation of the first NPC. Further, a setting unit 170 for setting at least one of the information and the battle status information of the second NPC as a condition is further provided, and at least of the attribute information of the second NPC, the level information of the second NPC, and the battle status information of the second NPC. Information requesting the user terminal 10 in which the information for identifying the second user extracted by the extraction unit 150 is set based on the comparison with one piece of information to participate in the battle with the second NPC. A transmission unit (server communication unit 34) for transmitting information is provided.

As a result, the game system 1 can extract information for identifying a second user who satisfies a preset condition, so that user operations such as selection of a request destination can be omitted. Therefore, it is possible to improve the operability of the user in the game.

(12) Further, in the game system 1 of the present embodiment, based on the history information, the information regarding the information for identifying the second user is combined with the contribution degree information associated with the information for identifying the second user. A second presentation unit 162 that is associated and presented is provided.

As a result, the game system 1 allows the user to select a user with a high degree of contribution, so that the game entertainment can be improved. Specifically, the game system 1 allows the user to select which second user to request participation while checking the contribution information, so that the second user meets the user's request. Information for identifying, for example, information for identifying a second user of a user with a higher contribution can be extracted.

(13) Further, in the game system 1 of the present embodiment, the user terminal in which the information for identifying the second user extracted by the extraction unit 150 is set is requested to participate in the battle with the second NPC. A second presenting unit 162 that presents information in a manner capable of instructing transmission is provided, and the second presenting unit presents a number based on the information regarding the access time.

As a result, the game system 1 can select a request destination in which the user has more active users in the battle with the NPC, for example, according to the time limit in the battle with the NPC. In addition, since it is possible to select a request destination with more active users, it is possible to extract information for identifying a second user who is likely to be able to subdue NPCs earlier.

[Modification example]
Although the embodiments of the present invention have been described in detail with reference to the drawings, the specific configuration is not limited to the above-described embodiments, and includes designs and the like within a range that does not deviate from the gist of the present invention. For example, the configurations described in the first embodiment described above can be arbitrarily combined.
For example, the user terminals 10 and 10A and a part or all of the functional configurations of the game servers 30 and 30A may be provided in one device. Further, another device may include a part of each functional configuration of the user terminals 10 and 10A and the game servers 30 and 30A.

Further, a program for realizing a part or all of the functions of the control unit 110 or the server control unit 310 described above is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into the computer system. Then, the processing as the control unit 110 or the server control unit 310 may be performed by executing the process. Here, "loading and executing a program recorded on a recording medium into a computer system" includes installing the program in the computer system. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. Further, the "computer system" may include a plurality of computer devices connected via a network including a communication line such as the Internet, WAN, LAN, and a dedicated line. Further, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, or a CD-ROM, and a storage device such as a hard disk built in a computer system. As described above, the recording medium in which the program is stored may be a non-transient recording medium such as a CD-ROM. The recording medium also includes an internal or external recording medium accessible from the distribution server for distributing the program. The code of the program stored in the recording medium of the distribution server may be different from the code of the program in a format that can be executed by the user terminal. That is, the format stored in the distribution server does not matter as long as it can be downloaded from the distribution server and installed in a form that can be executed by the terminal device. It should be noted that the configuration in which the program is divided into a plurality of parts and downloaded at different timings and then combined by the user terminal, or the distribution server for distributing each of the divided programs may be different. Furthermore, a "computer-readable recording medium" is a volatile memory (RAM) inside a computer system that serves as a server or client when a program is transmitted via a network, and holds the program for a certain period of time. It shall include things. Further, the above program may be for realizing a part of the above-mentioned functions. Further, a so-called difference file (difference program) may be used, which can realize the above-mentioned function in combination with a program already recorded in the computer system.

For example, the extraction unit 320 and the extraction unit 150 calculate the number of battles for each raid boss of each user based on the history information, and according to the number of battles between the raid bosses to be battled from now on and the raid bosses who have played in the same past, for example. , The user ID of the user who has a large number of battles may be extracted as the request destination information.
As a result, users who have abundant experience in fighting with raid bosses that have appeared in the past can be extracted as request destinations, and users who cooperate with each other can be combined.

[Additional Notes]
From the above description, the present invention can be grasped as follows, for example. Reference numerals in the accompanying drawings are added in parentheses for convenience in order to facilitate understanding of the present invention, but the present invention is not limited to the illustrated embodiment.

(Appendix 1) The game system (1) according to one aspect of the present invention is a game system (1) in which a plurality of users cooperate to play a game against an NPC (for example, a raid boss), and is a game system (1) of the first user. Information for identifying the reception unit (reception unit 120, server communication unit 34) that accepts operations, the first user who has played against the first NPC (for example, a past raid boss), and the second user who has played against the first NPC. The storage unit (server storage unit 330) and the reception unit (reception unit 120, server communication unit 34), which store information for associating with the information to be stored as history information related to the battle, participate in the battle with the second NPC. When an operation requested to another user is accepted, an extraction unit (extraction unit 150, extraction unit 320) that extracts information for identifying the second user based on the history information as request destination information is provided. Be prepared.

According to the configuration of Appendix 1, when the first user requests participation in the battle with the second NPC, the game system 1 can extract the second user who has played against the same first NPC as the request destination. Since the first user and the second user have a history of playing against the same first NPC in the past, there is a high possibility that they will cooperate with each other.
That is, the game system 1 can combine users who have similar battle experience with users who cooperate with each other in a battle with the second NPC.

(Appendix 2) Further, one aspect of the present invention is the game system (1) described in the appendix 1, and the information for identifying the second user included in the history information is played against the second user. The extraction unit (extraction unit 150, extraction unit 320) extracts the request destination information based on the attribute information of the first NPC and the attribute information of the second NPC, and is associated with the attribute information of the first NPC. The attribute information of the first NPC and the attribute information of the second NPC are information representing the attributes of the first NPC and information representing the attributes of the second NPC, respectively.

According to the configuration of Appendix 2, the game system 1 can extract the request destination information based on the attributes of the first NPC and the attributes of the second NPC, so that the second user who is advantageous in the battle with the second NPC can be selected. Can be extracted.

(Appendix 3) Further, one aspect of the present invention is the game system according to the appendix 1 or the appendix 2. The information for identifying the second user included in the history information is the second user. The extraction unit (extraction unit 150, extraction unit 320) is associated with the level information of the first NPC in which the player has played, and the extraction unit (extraction unit 150, extraction unit 320) obtains the request destination information based on the level information of the first NPC and the level information of the second NPC. The extracted level information of the first NPC and the level information of the second NPC are information regarding the difficulty level of the battle with the NPC.

According to the configuration of Appendix 3, the game system 1 can appropriately extract the request destination from the history information according to the level information of the NPCs to be played against.

(Appendix 4) Further, one aspect of the present invention is the game system (1) according to any one of the appendices 1 to 3, and is information for identifying a second user included in the history information. Is associated with the contribution information regarding the battle of the second user with the first NPC, and the extraction unit (extraction unit 150, extraction unit 320) extracts the request destination information based on the contribution information.

According to the configuration of the appendix 4, the game system 1 can extract a user who cooperates in the battle with the NPC from the history information as a request destination according to the contribution information.

(Appendix 5) Further, one aspect of the present invention is the game system (1) according to any one of the appendices 1 to 4, and is information for identifying a second user included in the history information. Is associated with the battle status information of the first NPC in which the second user has played, and the extraction unit (extraction unit 150, extraction unit 320) has the request destination information based on the battle status information included in the history information. To extract.

According to the configuration of the appendix 5, the game system 1 can extract a user corresponding to the past battle situation information with the NPC as a request destination from the history information.

(Appendix 6) Further, one aspect of the present invention is the game system (1) according to any one of the appendices 1 to 5, wherein the extraction unit (extraction unit 150, extraction unit 320) is described above. The request destination information is extracted by excluding the information for identifying the identifiable second user from the information for identifying the first user.

According to the configuration of Appendix 6, the game system 1 can extract a desired user as a request destination.

(Appendix 7) Further, one aspect of the present invention is the game system (1) according to any one of the appendices 1 to 6, wherein the storage unit (server storage unit 330) is a plurality of users. The team information associated with the information for identifying the user is further stored, and the extraction unit (extraction unit 150, extraction unit 320) belongs to a team different from the team of the first user based on the team information. Information for identifying the second user of the second user is extracted as the request destination information.

According to the configuration of Appendix 7, the game system 1 can utilize transfer to another team or the like.

(Appendix 8) Further, one aspect of the present invention is the game system (1) according to any one of the appendices 1 to 7, wherein the storage unit (server storage unit 330) is a plurality of users. The team information associated with the information for identifying the team information is further stored, and the extraction unit (extraction unit 150, extraction unit 320) is based on the number of information for identifying the user associated with the team information. The request destination information is extracted.

According to the configuration of Appendix 8, the game system 1 can provide an opportunity to transfer from a team with few team members or a team with many team members to another team.

(Appendix 9) Further, one aspect of the present invention is the game system (1) according to any one of the appendices 1 to 8, wherein the extraction unit (extraction unit 150, extraction unit 320) is described above. The request destination information is extracted based on the information regarding the access time to the game associated with the information for identifying the second user.

According to the configuration of Appendix 9, the game system 1 can extract an active user as a request destination.

(Appendix 10) Further, one aspect of the present invention is the game system (1) according to any one of the appendices 1 to 9, which is extracted by the extraction unit (extraction unit 150, extraction unit 320). The first presenting unit (161) of the first user is provided with a first presenting unit (161) that presents related information corresponding to the information for identifying the second user in a selectable manner. A specific unit (180) for specifying a request transmission destination based on an operation for the presented related information is provided.

According to the configuration of Appendix 10, the game system 1 can extract a desired user as a request destination.

(Appendix 11) Further, one aspect of the present invention is the game system according to any one of the appendices 1 to 10, and the attribute information of the first NPC, the attribute information of the first NPC, based on the operation of the first user. A setting unit that sets at least one of the attribute information of the second NPC, the level information of the first NPC, the level information of the second NPC, the battle status information of the first NPC, and the battle status information of the second NPC as a condition ( 170) is further provided, and the extraction unit (based on the comparison between the attribute information of the second NPC, the level information of the second NPC, and the battle status information of the second NPC, and the conditions. A transmission unit that transmits information requesting participation in the battle with the second NPC to the user terminal (10) in which information for identifying the second user extracted by the extraction unit 150 and the extraction unit 320) is set. (Communication unit 12) is provided.

According to the configuration of Appendix 11, the game system 1 can omit user operations such as selection of a request destination by setting conditions in advance for the game.

(Appendix 12) Further, one aspect of the present invention is the game system according to any one of the appendices 1 to 11, and is information on information for identifying a second user based on the history information. Is provided with a second presentation unit (162) that presents the information in association with the contribution information associated with the information for identifying the second user.

According to the configuration of Appendix 12, the game system 1 allows the user to select a user with a high degree of contribution, so that the game entertainment can be improved.

(Appendix 13) Further, one aspect of the present invention is the game system (1) according to any one of the appendices 1 to 12, which is extracted by the extraction unit (extraction unit 150, extraction unit 320). A second presentation unit (162) that presents information requesting participation in a battle with the second NPC to a user terminal in which information for identifying the second user is set in a manner capable of instructing transmission. The second presentation unit (162) presents a number based on the information regarding the access time.

According to the configuration of the appendix 13, the game system 1 can confirm how many request destinations exist.

(Appendix 14) Further, the game device (game server 30) according to one aspect of the present invention is a game device in which a plurality of users cooperate to execute a game in which a game is played against an NPC, and the operation information of the first user is obtained. The reception unit (reception unit 120, server communication unit 34), the information for identifying the first user who played against the first NPC, and the information for identifying the second user who played against the first NPC are associated with each other. Operation information that the storage unit (server storage unit 330) that stores as history information about the battle and the reception unit (reception unit 120, server communication unit 34) request other users to participate in the battle with the second NPC. When the above is received, an extraction unit (extraction unit 150, extraction unit 320) that extracts information for identifying the second user based on the history information as request destination information is provided.

According to the configuration of Appendix 14, the game system device can request other users to participate in the battle with the NPC even if the user cannot obtain the cooperation of the other user in the battle with the NPC. It is possible to improve the user's game entertainment. In addition, by using the history information, it is possible to extract other users who are advantageous to the user in the battle with the NPC as the request destination.

(Appendix 15) Further, the program according to one aspect of the present invention is a game device (game server 30) in which a plurality of users cooperate to execute a game against an NPC, and the first user who has played against the first NPC. In a computer of a game device including a storage unit (server storage unit 330) that stores information for identifying a match and information for identifying a second user who has played against the first NPC as history information related to the match. When the reception step (step S102) for receiving the operation information of the first user and the operation of requesting another user to participate in the battle with the second NPC are received by the reception step, the operation is received based on the history information. An extraction step (steps S106, S114, S122) for extracting information for identifying the second user as request destination information is executed.

According to the configuration of Appendix 15, even a user who cannot obtain the cooperation of another user in the battle with the NPC can request the other user to participate in the battle with the NPC. Can be improved. In addition, by using the history information, it is possible to extract other users who are advantageous to the user in the battle with the NPC as the request destination.

1 game system, 10, 10A user terminal, 11 CPU, 12 communication unit, 13 input unit, 14 display unit, 15 storage unit, 30, 30A game server, 31 server CPU, 310 server control unit, 320 extraction unit, 321 attributes Information extraction unit, 322 level information extraction unit, 323 contribution level information extraction unit, 324 battle status information extraction unit, 325 team information extraction unit, 326 time information extraction unit, 34 server communication unit, 330 server storage unit, 331 user data storage unit. 332 Boss information storage unit 333 History information storage unit 334 Team information storage unit 110 Control unit, 120 Reception unit, 130 Game processing unit, 140 Display control unit, 150 Extraction unit, 160 Presentation unit, 161 First presentation Part, 162 Second presentation part, 170 Setting part, 180 Specific part

Claims (5)

A game system in which multiple users cooperate to play a game against an NPC.
A storage unit that stores information for identifying the first user who has played against the first NPC and information for identifying the second user who has played against the first NPC as history information regarding the battle.
It is a condition for requesting another user to participate in the battle with the second NPC without requiring an operation of requesting the other user to participate in the battle with the second NPC, and is preset by the first user. When the said condition is satisfied, the extraction unit that extracts the information for identifying the second user based on the history information as the request destination information, and the extraction unit.
A transmission unit that transmits information requesting participation in a battle with the second NPC to a user terminal in which information for identifying the second user extracted by the extraction unit is set.
A game system equipped with. The extraction unit extracts the request destination information based on the attribute information of the first NPC and the attribute information of the second NPC.
The game system according to claim 1. The extraction unit extracts the request destination information based on the level information regarding the difficulty level of the battle with the first NPC and the level information regarding the difficulty level of the battle with the second NPC.
The game system according to claim 1 or 2. A game device in which multiple users cooperate to play a game against an NPC.
A storage unit that stores information for identifying the first user who has played against the first NPC and information for identifying the second user who has played against the first NPC as history information regarding the battle.
It is a condition for requesting another user to participate in the battle with the second NPC without requiring an operation of requesting the other user to participate in the battle with the second NPC, and is preset by the first user. When the said condition is satisfied, the extraction unit that extracts the information for identifying the second user based on the history information as the request destination information, and the extraction unit.
A transmission unit that transmits information requesting participation in a battle with the second NPC to a user terminal in which information for identifying the second user extracted by the extraction unit is set.
A game device equipped with. A game device in which a plurality of users cooperate to execute a game against an NPC, and information for identifying a first user who has played against the first NPC and to identify a second user who has played against the first NPC. In the computer of the game device equipped with a storage unit that stores the information of the game as history information related to the battle.
It is a condition for requesting another user to participate in the battle with the second NPC without requiring an operation of requesting the other user to participate in the battle with the second NPC, and is preset by the first user. When the said condition is satisfied, the extraction step of extracting the information for identifying the second user based on the history information as the request destination information, and the extraction step.
A transmission step of transmitting information requesting participation in a battle with the second NPC to a user terminal in which information for identifying the second user extracted by the extraction step is set, and a transmission step.
A program to execute.

Images