Game program, game device, and game system

Abstract

To provide a game program, a game device, and a game system capable of improving construction of a relationship with other matched users.SOLUTION: A game program allows a control part 23 (computer) of a server device 2 to function as matching means 237 for matching plural users for executing a second game part on the basis of progress of a first game part, and as registration means 235 that registers a user relationship between a first user and a second user included in plural users and updates a user relationship in the second game part, and the matching means 237 matches plural users for executing a third game part on the basis of progress of the first game part and the updated user relationship when the third game part is started following the second game part.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a game program, a game device, and a game system. [Background technology]

[0002] Conventionally, there are games in which a plurality of users are grouped and the grouped users can play against each other or cooperate with each other. For example, Patent Document 1 discloses a control method for grouping a plurality of users (players) into two or more groups and holding a ranking match to determine the ranking of users within the group. This control method discloses grouping based on game points that are associated with the progress of the game. This control method also discloses that the groups are then shuffled and the next ranking match is repeatedly held. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2016-220834 A Summary of the Invention [Problem to be solved by the invention]

[0004] In the above conventional technology, since users matched to the same group compete with each other to determine rankings, it is difficult to build a relationship with other users that deepens the relationship. Therefore, in the conventional technology, there is room for improvement in building a relationship with other users matched to the same group, etc., due to the progress of the game, etc.

[0005] The present disclosure provides a game program, a game device, and a game system that can improve the building of relationships with other matched users. [Means for solving the problem]

[0006] A first aspect includes a computer comprising: a matching means for matching a plurality of users for executing a second game part based on the progress of the first game part; a registration means for registering a user relationship between a first user and a second user included in the plurality of users, the registration means functioning as a registration means for updating the user relationship in the second game part; the matching means, when a third game part is started following the second game part, matches a plurality of users for executing the third game part based on the progress of the first game part and the updated user relationships; It is a game program.

[0007] In the first aspect, the computer includes: In response to the user relationship being updated to the first relationship in the second game part, the device can function as an awarding means for awarding a benefit to the first user or the second user in the first game part or the second game part.

[0008] In the first aspect, the computer includes: As the benefit, the device can function as a game execution means that permits the first user to control a game based on game information of the second user.

[0009] Also, in the first aspect, the granting means can determine the value of the benefit or the amount of the benefit depending on the number of the first relationships.

[0010] In the first aspect, the computer includes: The display control means can function as a display control means for displaying a notification screen notifying the granting of the benefit, and for displaying an update screen for further updating the relationship between the first user and a user different from the second user to the first relationship after displaying the notification screen and before the benefit is granted.

[0011] In a first aspect, the registration means updates the user relationship in a fourth game part that progresses independently of the first game part and the second game part, After the user relationships are updated, when the third game part is started, the matching means can match a plurality of users to perform the third game part based on the progress of the first game and the updated user relationships.

[0012] In the first aspect, the method further comprises causing the computer to function as a receiving unit that receives a request for updating the user relationship from the first user, the registration means, when the update request is accepted in the fourth game part, updates and registers the user relationship to at least one of a first relationship not requiring consent of the second user, or a second relationship or a third relationship requiring consent of the second user; causing the computer to function as a game execution means for permitting the first user to control a game based on game information of the second user in the fourth game part in response to the user relationship being updated to the second relationship; The matching means can enable matching between the first user and the second user in the third game part, on condition that the user relationship has been updated to the third relationship.

[0013] In addition, in a first aspect, the receiving means can receive a request to update the user relationship to the third relationship in the fourth game part, with the permission condition being that the user relationship has been updated to the first relationship or the second relationship.

[0014] The second aspect is a matching unit that matches a plurality of users for executing a second game part based on the progress of the first game part; a registration unit which is a registration means for registering a user relationship between a first user and a second user included in the plurality of users and which updates the user relationship in the second game part; the matching unit, when a third game part is started following the second game part, matches a plurality of users for executing the third game part based on the progress of the first game part and the updated user relationships; It is a server device.

[0015] The third aspect is a matching unit that matches a plurality of users for executing a second game part based on the progress of the first game part; a registration unit which is a registration means for registering a user relationship between a first user and a second user included in the plurality of users and which updates the user relationship in the second game part; the matching unit, when a third game part is started following the second game part, matches a plurality of users for executing the third game part based on the progress of the first game part and the updated user relationships; It is a game system.

[0016] According to the present disclosure, a game program, a game device, and a game system are provided that can improve the building of relationships with other matched users. [Brief description of the drawings]

[0017] [Figure 1] 1 is a block diagram showing a configuration of a game system according to an embodiment of the present invention. [Diagram 2] 11A and 11B are schematic diagrams for explaining examples of relationship levels and their effects in the present embodiment. [Diagram 3] 10A and 10B are schematic diagrams for explaining examples of relationship levels and their conditions in the present embodiment. [Figure 4] 4 is a schematic diagram for explaining an example of a game part in the present embodiment. FIG. [Diagram 5] 5 is a schematic diagram for explaining an example of the flow of a game part in the present embodiment. FIG. [Figure 6] 11 is a schematic diagram for explaining an example of team composition in a game part in this embodiment. FIG. [Figure 7] 13 is an example of a screen that is displayed on a display during a game. [Figure 8] 13 is an example of a screen that is displayed on a display during a game. [Figure 9] 13 is an example of a screen that is displayed on a display during a game. [Figure 10] 13 is an example of a screen that is displayed on a display during a game. [Figure 11] 13 is an example of a screen that is displayed on a display during a game. [Figure 12] 13 is an example of a screen that is displayed on a display during a game. [Figure 13] 13 is an example of a screen that is displayed on a display during a game. [Figure 14] 13 is an example of a screen that is displayed on a display during a game. [Figure 15] 13 is an example of a screen that is displayed on a display during a game. [Figure 16] FIG. 2 is a flow chart showing a series of operations of the game system in the present embodiment. [Figure 17] FIG. 2 is a flow chart showing a series of operations of the game system in the present embodiment. [Figure 18] FIG. 2 is a sequence diagram showing a series of operations of the game system in this embodiment. [Figure 19] FIG. 2 is a sequence diagram showing a series of operations of the game system in this embodiment. [Figure 20] 13 is an example of a screen that is displayed on a display during a game. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] A game system 1 according to an embodiment of the present disclosure will be described with reference to the drawings.

[0019] <Game Description> In the game system 1 shown in FIG. 1, a server device 2 and a plurality of game devices 5 are communicably connected to each other via a communication network 6, and a game is executed on the game devices 5.

[0020] The game according to this embodiment is an online game executed by the game system 1. In this game, a user of the game device 5 causes one or more player characters (corresponding to objects) to act in a virtual game space, and causes the player characters to fight against enemy characters that are non-player characters.

[0021] In the game system 1, relationships between users, such as between a first user and a second user (hereinafter also referred to as "user relationships"), can be built in stages in the same way as real human relationships are built by registering the user relationships in a list indicating the user relationships. Specifically, in the game system 1, user relationships are divided into levels (hereinafter these levels are also referred to as "relationship levels"). In the game system 1, conditions for requesting registration of a user relationship (hereinafter also referred to as "request conditions") and conditions for registering the requested user relationship (hereinafter also referred to as "registration conditions") are set according to each relationship level. Then, in the game system 1, advantageous effects are provided to users according to each relationship level.

[0022] The above-mentioned "list indicating user relationships" includes, for example, the following lists (1) to (6). (1) First user's follow list: one aspect of the first list of the first user, which is a list in which the first user registers users whom the first user follows (hereinafter, also referred to as "following users"). (2) Second user's follow list: one aspect of the second list of the second user, which is a list that registers the second user's following users. (3) Friend list of first user: This is one aspect of the third list of the first user, and is a list that registers users who are friends with the first user (hereinafter, also referred to as "friend users"). (4) Friend list of second user: one aspect of the fourth list of the second user, which is a list that registers friend users of the second user. (5) Partner list of first user: This is one aspect of the fifth list of the first user, and is a list for registering users who are in a partner relationship with the first user (hereinafter, also referred to as "partner users"). (6) Partner list of second user: This is one embodiment of the sixth list of the second user, and is a list for registering partner users of the second user.

[0023] Here, an example of the relationship level will be described with reference to Figs. 2 and 3. Fig. 2 is a table showing an example of the relationship level and its effect. As shown in Fig. 2, an example in which the relationship level is set in four stages from 1 to 4 will be described, but the relationship level is not limited to this. In addition, in the "Description of Relationship Level" column of the table, an example of the specific content of each relationship is described. For example, a one-sided follow relationship is set as relationship level 1. In addition, in the "Effect" column of the table, an example of the effect in the game caused by each relationship is described. For example, as an effect of relationship level 1, it becomes possible to see information such as the progress of the follower and to rent the follower's player character. In addition, this effect in the game may differ between the normal part and the event part.

[0024] "Follow" refers to a relationship in which information such as the progress of the game of the other user can be tracked. Also, the follow relationship can be registered without the consent of the other user. "One-sided follow" refers to, for example, a state in which a first user follows a second user but the second user does not follow the first user, or vice versa. Also, "mutual follow" refers to a state in which a first user follows a second user and the second user follows the first user, that is, a state in which the first user and the second user follow each other. The follow relationship is one aspect of the first relationship.

[0025] A "friend" is a relationship in which you can play against or cooperate with the other user in multiplayer. Also, friends can be registered with the other user's consent. Because registration requires the other user's consent, a friend relationship is never one-sided, but is always mutual. A friend relationship is one form of the second relationship.

[0026] "Partner" refers to a relationship that is limited to a specific event, and allows users to play against or cooperate with each other in multiplayer only during a specified period, such as the duration of the event. Partners are also in a relationship where users are matched into the same matching group for event-limited multiplayer at a specific event. Partners can also be registered with the consent of the other user. For this reason, a partner relationship is never one-sided, since registration requires the consent of the other user, and is always mutual. A partner relationship is one aspect of the third relationship.

[0027] A "normal part" is one of the game parts, and is a game part that a user normally progresses through in a game. A normal part may be, for example, a game part that is the main part of a game. An "event part" is one of the game parts, and is a game part that occurs as an event in a game (for example, non-regularly, accidentally, or for a limited period of time). An event part may be, for example, a secondary game part in a game.

[0028] A "game part" is content that a user can play within a game. Game parts include, for example, quests (tasks or goals in a game), mini-games, missions (missions in a game), events, and the like.

[0029] FIG. 3 is a table showing an example of relationship levels and conditions for each relationship level. As shown in FIG. 3, required conditions and registration conditions are set for each relationship level. For example, in the case of relationship level 3, in order for a user to request friend registration, the required condition is that the user relationship with the other user must be one-sided follow or mutual follow. In addition, in the case of relationship level 3, even if the user can make this registration request, in order for the friend registration to be made, the other user must agree to this registration request as a registration condition.

[0030] Now, with reference to FIG. 4, an example of each of the normal part and the event part, which are game parts in this embodiment, will be described.

[0031] As shown in FIG. 4, in the normal part, the user can obtain and develop player characters by performing gacha and clearing quests. In addition, in the normal part, the user can register user relationships in stages, from follow, to friend, and to partner. Once a friend is registered, multiplay with the other user in the normal part as shown in FIG. 3 (referred to as "normal multiplay" in FIG. 4) becomes possible.

[0032] "Gacha" is a method in which the server device 2 selects arbitrary game media by lottery from the lottery list 222 based on a predetermined selection ratio. The arbitrary selected game media is given to the user's game device 5. "The game media selected by gacha is given to the user / the user owns it" is synonymous with "the game media selected by the lottery process is associated / is associated with identification information indicating the user."

[0033] An event part is a game part included in an event held for a limited time (hereinafter also referred to as a "limited event"). An event part can be divided into a game part for solo play (hereinafter also referred to as a "solo part") and a game part for multiplayer play (hereinafter also referred to as a "multipart"). In this embodiment, the solo part includes multiple stages (hereinafter also referred to as "layers"). The solo part is one aspect of the first game part. Moreover, the multipart is one aspect of the second game part. The second game part is a game part different from the first game part, and is a game part played by multiple matched users.

[0034] In the solo part, for example, a search-type game can be played solo. In this search-type game, the user can move the player character within a predetermined field as a solo play by consuming stamina dedicated to the event part. In addition, in this search-type game, the user can obtain game media in the event part (for example, an item exclusive to the event part, etc.).

[0035] In the solo part, an event may occur in which the user's party encounters another user's party while exploring. In addition, for other users who are one-sided followers, mutual followers, or friends, the encounter rate may be set to be higher as a benefit described later. In the solo part, the user can stock up to a predetermined number of parties of the other users encountered for battles with floor bosses described later. Hereinafter, these stocked parties of other users are also referred to as "friend parties." In other words, in the solo part, by encountering other users and stocking them as friend parties, it is possible to generate advantageous effects from friends in the normal part (for example, challenging a quest in cooperation with friends).

[0036] In the solo part, an enemy character (hereinafter also referred to as a "level boss") is set as the boss for each level, and when the user's party progresses to a certain progress rate for each level (100% in this example), the party encounters the level boss, and a battle event occurs to defeat (hereinafter also referred to as "subjugating") the level boss. In this battle event, the user can add a friend party stored in their party to battle the level boss.

[0037] In the multi-part, a mission (for example, a raid mission) is performed in cooperation with other users. In the multi-part, the objective is to defeat a boss (hereinafter also referred to as a "raid boss") different from the hierarchical boss in cooperation with other users. In the multi-part, first, at the start of the multi-part, a plurality of users for executing the multi-part are matched, and the matched plurality of users are grouped. Next, a team is formed with members who will participate in the multi-part among the grouped plurality of users (hereinafter also referred to as "group members"). The members of this formed team (hereinafter also referred to as "team members") fight against the raid boss. The user relationship between the team members is registered as a partner relationship limited to the event part. That is, in the event part, during cooperative play with other users, it is possible to register a user relationship based on the event part-limited conditions (required conditions or registration conditions), or to register a user relationship (partner) limited to the event part.

[0038] The multi-part, in which team members battle the raid boss, ends after a certain amount of time has passed since it began. When the multi-part ends, the group formed by matching (hereinafter also referred to as the "matching group") is disbanded. When the matching group is disbanded, users are ranked within the matching group according to the amount of damage each user inflicted on the raid boss. In addition, each user is given a benefit (reward) according to this amount of damage. When the next multi-part begins, multiple users are matched and grouped again. Also, if a partner, a user relationship exclusive to the event part, is registered, the user will be matched to the same matching group in the next multi-part.

[0039] Returning to Fig. 1, the description will continue. The above-mentioned games are played using a game device 5, which is a home game console such as PlayStation (registered trademark), a portable game console such as Nintendo Switch (registered trademark), or an electronic device such as a personal computer, a smartphone, or a tablet. In the following, a case where the game device 5 is a smartphone will be exemplified.

[0040] <Overview of Game System 1> The game system 1 is made up of a server device 2 and a plurality of game devices 5. The server device 2 stores game programs and game data, and manages the game data of the game devices 5 (for each account information described below).

[0041] The game data is data for executing a game on the game device 5, and includes, for example, a player character operated by a user, other game space objects (objects constituting the terrain and field of the game space, and NPC (non player character) objects such as enemy characters), and operation data for automatically operating enemy characters.

[0042] The game device 5 executes a predetermined game based on the user's operation. To this end, the game device 5 receives (specifically, downloads and installs) a game program and game data from the server device 2 via the communication network 6. Each user is assigned account information including identification information and a password in association with the game device 5. This account information is transmitted from the game device 5 to the server device 2 at the time of login, and is used for user authentication in the server device 2.

[0043] After user authentication, mutual communication between the server device 2 and the game device 5 becomes possible. After logging in, the game device 5 receives data required for game progress (data related to the game progress status) from the server device 2, and progresses the game while outputting game images and sounds to the display 61 and the speaker 62 based on the user's operation.

[0044] <Configuration of Game System 1> Hereinafter, the hardware configuration of the server device 2 and the game devices 5 will be described with reference to Fig. 1. Note that each of the multiple game devices 5 has the same configuration.

[0045] <Configuration of server device 2> 1, the server device 2 includes a network interface 21, a storage unit 22, and a control unit 23. The network interface 21 and the storage unit 22 are electrically connected to the control unit 23 via a bus 29.

[0046] The network interface 21 is communicatively connected to each game device 5 via a communication network 6 such as the Internet or a LAN.

[0047] The storage unit 22 is composed of a hard disk drive (HDD), a random access memory (RAM), a read only memory (ROM), a solid state drive (SSD), etc. The storage unit 22 stores various programs including a part of the game program according to the present embodiment, as well as various data such as a user DB 221 and a lottery list 222.

[0048] In the user DB 221, for each identification number of a user playing a game, information (status, etc.) about the player character operated by the user, the amount of consumable media that can be used in the virtual game space, information about parameters, etc. are stored in association with each other. Hereinafter, this information is collectively referred to as "user information."

[0049] "Consumable media" refers to currency, points, etc. that can be used within the virtual game space and are consumed within the game to progress in the game. Consumable media are given to users as rewards for clearing quests or by paying in real life.

[0050] The lottery list 222 is used when the lottery execution means 233 (described later) performs a lottery process generally called gacha, and includes multiple pieces of information about the game media to be selected. The lottery list 222 associates information about the game media (such as name, ability parameters, rarity, and level) with a selection rate by lottery. In addition, when the game media is a player character, the parameters include, for example, fighting power, HP, attack power, defense power, intelligence, speed, and the like.

[0051] "Game media" refers to electronic data that represents elements related to a game, including the name of the character used as the player character, items (weapons, armor, tools) used by the player character in the virtual game space, etc. Users can obtain game media by directly purchasing it for a fee, clearing a quest, or by a lottery method called gacha. The obtained game media is stored and managed in the user DB 221 in association with the identification information of the user who has come to own the game media.

[0052] The control unit 23 is configured with a microcomputer including a CPU and a semiconductor memory, and controls the operation of the device 2 itself.

[0053] The control unit 23 executes various programs to function as an information processing means 231, a checking means 232, a lottery execution means 233, a receiving means 234, a registration means 235, an execution control means 236, a matching means 237, and an awarding means 238.

[0054] -Information processing means- The information processing means 231 transmits and receives various data to and from each game device 5. Main data received by the information processing means 231 include download request information for a game program, a gacha lottery request in response to a user operation, a request to execute / end a game part, account information, game data, etc. Main data transmitted by the information processing means 231 include information for confirming that the game device 5 has received the game program, information on the game media obtained by the gacha, etc.

[0055] -Method of verification- The verification means 232 uses the user identification information received from the game device 5 to authenticate the user account.

[0056] -Lottery execution method- In response to a gacha lottery request, the lottery execution means 233 selects one or more game media by lottery from the lottery list 222 based on the selection probability for each game medium. The lottery execution means 233 associates information about the selected game media with identification information of the user who performed the operation that is the source of the lottery request in the user DB 221. As a result, the game media that the user won as a result of their own gacha draw are awarded to the user.

[0057] -Method of reception- The receiving means 234 receives various requests from users to the server device 2. The receiving means 234 includes a first receiving means 2341 and a second receiving means 2342. The receiving means 234 receives a request from the first user to register in the follow list of the second user. The receiving means 234 also receives a request from the second user to register in the follow list of the first user. The receiving means 234 receives, for example, a request from the first user to register in each of the above lists (1), (3), and (5) of the first user. In other words, the receiving means 234 receives a request to update the user relationship from the first user.

[0058] -First reception method- The first reception means 2341 is capable of receiving a request for registration of the second user in the friend list (third list) of the first user as a registration-related process. When the first reception means 2341 is thus capable of receiving, the first reception means 2341 receives a request for registration of the second user in the friend list of the first user from the first user. Furthermore, the first reception means 2341 is capable of receiving a request for registration of the first user in the friend list (fourth list) of the second user as a registration-related process. When the first reception means 2341 is thus capable of receiving, the first reception means 2341 receives a request for registration of the first user in the friend list of the second user from the second user. When the first reception means 2341 receives these registration requests, it inquires of the first user or the second user to whom the registration is to be made whether or not to accept these registration requests.

[0059] "Registration-related processing" refers to processing related to registering a second user or a first user in the friend list of a first user or a second user. Registration-related processing includes, for example, (a) processing for enabling acceptance of a friend registration request, (b) processing for increasing benefits granted based on user relationships, and (c) processing for updating the display mode of a UI for requesting friend registration.

[0060] According to the above configuration, the first receiving means 2341 can accept a request to register a friend on the condition that the second user follows the first user or the second user follows the first user. Therefore, according to the above configuration, the first receiving means 2341 can accept a request to register a friend at a higher relationship level if the user relationship is in a follow state. Therefore, according to the above configuration, the first receiving means 2341 can build a user relationship in stages from a follow to a friend.

[0061] The first receiving means 2341 receives, for example, from a first user a request to deregister a second user from the friend list of the first user. Also, the first receiving means 2341 receives, for example, from a second user a request to deregister the first user from the friend list of the second user.

[0062] -Second method of reception- In the normal part, the second receiving means 2342 is capable of receiving a request for registration of the second user in the partner list (fifth list) of the first user on the condition that the first user and the second user are mutually registered in the follow list (second list) of the second user and the follow list (first list) of the first user, or the second user is registered in the friend list (third list) of the first user. When the second receiving means 2342 is thus capable of receiving, it receives a request for registration in the partner list of the first user from the second user.

[0063] According to the above configuration, the second reception means 2342 can accept a request to register a partner on the condition that the first user and the second user are mutually following or are friends. Therefore, according to the above configuration, the second reception means 2342 can accept a request to register a partner at a higher relationship level if the user relationship is mutually following or friends. Therefore, according to the above configuration, the second reception means 2342 can build a user relationship from mutual following to partner by skipping one step or from friends to partner in stages.

[0064] The second accepting means 2342 may be capable of accepting a request for registering the second user in the partner list (fifth list) of the first user on condition that a limited event starts, for example.

[0065] According to the above configuration, the second reception means 2342 can build a user relationship to a partner by skipping a step, limited to the period during which the limited event is held. According to the above configuration, the second reception means 2342 can, for example, create the construction of a special user relationship for a limited time while playing cooperatively with other users in an event part that is a limited event, thereby increasing interest.

[0066] The second receiving unit 2342 receives, for example, from a first user a request to deregister a second user from the partner list of the first user. Also, the second receiving unit 2342 receives, for example, from a second user a request to deregister the first user from the partner list of the second user.

[0067] -Method of registration- The registration means 235 registers user relationships between a plurality of users in the user DB 221 or the like. In other words, when a request for updating a user relationship is accepted by the acceptance means 234, the registration means 235 updates and registers the user relationship to at least one of a follow relationship (first relationship) that does not require the consent of the second user, or a friend relationship (second relationship) or a partner relationship (third relationship) that requires the consent of the second user. The registration means 235 includes a first registration means 2351, a second registration means 2352, a third registration means 2353, and a fifth registration means 2354.

[0068] The registration means 235 registers the user relationship between a first user and a second user included in the multiple users matched by the matching means 237 described below. In addition, the registration means 235 updates the user relationship in the solo part (first game part) and the multi-part (second game part).

[0069] -First registration method- The first registration means 2351 registers the second user in the follow list (first list) of the first user without the consent of the second user. For example, when the reception means 234 receives a request from the first user to register the second user in the follow list of the first user, the first registration means 2351 registers the second user in the follow list of the first user in response to the received registration request. In this way, the first registration means 2351 registers the relationship in which the first user follows the second user.

[0070] -Second registration method- The second registration means 2352 registers the first user in the follow list (second list) of the second user without the consent of the first user. For example, when the reception means 234 receives a request from the second user to register the first user in the follow list of the second user, the second registration means 2352 registers the first user in the follow list of the second user in response to the received registration request. In this way, the second registration means 2352 registers the relationship in which the second user follows the first user.

[0071] -Third registration method- The third registration means 2353 registers the second user in the friend list (third list) of the first user in response to the second user's consent, and registers the first user in the friend list (fourth list) of the second user. For example, when the first reception means 2341 inquires of the second user whether or not the second user consents to registering the second user in the friend list of the first user and the response is "Agree", the third registration means 2353 registers the second user in the friend list of the first user. In addition to this registration, the third registration means 2353 also registers the first user in the friend list of the second user.

[0072] The third registration means 2353 performs a process associated with the registration when the second user is registered in the friend list (third list) of the first user as a registration-related process. The "processing associated with registration" may be, for example, a process of increasing the benefits (e.g., rewards for defeating a raid boss) granted by the granting means 238 to the first user and / or second user in response to the second user being registered on the friend list of the first user.

[0073] According to the above configuration, the third registration means 2353 can urge the user to register a friend by executing a process associated with the registration, such as increasing the benefits given to the user in response to the friend registration.

[0074] For example, the third registration means 2353 cancels the registration of the second user from the partner list of the first user and cancels the registration of the first user from the partner list of the second user in response to the first reception means 2341 receiving a request to cancel the registration of the second user from the partner list of the first user. Conversely, the third registration means 2353 cancels the registration of the first user from the partner list of the second user and cancels the registration of the second user from the partner list of the first user in response to the first reception means 2341 receiving a request to cancel the registration of the first user from the partner list of the second user.

[0075] - Fifth registration method - The fifth registration means 2354 registers the second user in the partner list (fifth list) of the first user in response to the second user's consent, and registers the first user in the partner list (sixth list) of the second user. For example, when the second reception means 2342 inquires of the second user whether or not the second user consents to registering the second user in the partner list of the first user and the response is "Agree", the fifth registration means 2354 registers the second user in the partner list of the first user. In addition to this registration, the fifth registration means 2354 also registers the first user in the partner list of the second user.

[0076] According to the above configuration, the fifth registration means 2354 can establish a partner relationship in response to the consent of the other user. Therefore, according to the above configuration, the fifth registration means 2354 can establish a partner relationship in which the effect of the relationship is greater than that of a follow relationship after obtaining the consent of the other user.

[0077] The fifth registration means 2354 may, for example, in a limited event, register the second user in the partner list of the first user and register the first user in the partner list of the second user, on the condition that the first user and the second user are members of the same team participating in multiple parts, instead of the consent of the second user.

[0078] The fifth registration means 2354 cancels the registration of the second user from the partner list of the first user in response to the end of the limited event, and also cancels the registration of the first user from the partner list (sixth list) of the second user.

[0079] According to the above configuration, the fifth registration means 2354 can set the partner relationship to be valid only during the limited event. Therefore, according to the above configuration, the fifth registration means 2354 can differentiate the partner relationship from the friend relationship and create a sense of exclusivity in the partner relationship.

[0080] -Execution control means- The execution control means 236 causes each means to execute registration-related processing on the condition that the second user is registered in the follow list (first list) of the first user, or the first user is registered in the follow list (second list) of the second user.

[0081] According to the above configuration, the execution control means 236 can execute a process related to friend registration on the condition that a follow is registered. Therefore, according to the above configuration, the execution control means 236 can encourage the building of a step-by-step user relationship from a follow to a friend.

[0082] -Matching method- The matching means 237 matches a plurality of users for executing the multi-part (second game part) based on the progress of the solo part (first game part). For example, the matching means 237 may use users whose progress in the solo part is within a predetermined range as a population, and match group members for executing the next event part by lottery from the population. This "user whose progress in the solo part is within a predetermined range" is, for example, a user who is in the same hierarchical level in the solo part and whose progress rate is within a predetermined range.

[0083] When the next multi-part (third game part) is started following the multi-part (second game part), the matching means 237 matches a plurality of users to execute the next event part based on the progress of the solo part (first game part) and the user relationship updated in the event part by the registration means 235. For example, the matching means 237 may match group members to execute the next event part by drawing a lottery from a population of (A) users whose progress rate of the solo part is within a predetermined range, (B) users in a follow relationship, or (C) users in a friend relationship. In addition, the matching means 237 may draw a lottery by setting a drawing frame for each of (A) to (C), such as X people in (A) and Y people in (B) or (C).

[0084] According to the above configuration, the matching means 237 can match users who have built a relationship in a matched multi-part in the next multi-part that is subsequently started. Also, according to the above configuration, the matching means 237 can match users in a multi-part according to the progress of the game parts including the solo part. Therefore, according to the above configuration, the matching means 237 can further deepen the user relationship through successive multi-parts (for example, aiming to conquer a limited event together, etc.), and can also encourage encounters with other users. Therefore, according to the above configuration, the matching means 237 can improve the building of a relationship with other matched users.

[0085] For example, when the user relationship between the first user and the second user is a partner relationship (third relationship), the matching means 237 matches the first user and the second user into the same group in the multipart.

[0086] -Method of granting- The granting means 238 grants a benefit to the first user or the second user in the solo part (first game part) or the multi-part in response to the user relationship being updated to a follow relationship (first relationship) in the multi-part (second game part).

[0087] According to the above configuration, the granting means 238 grants a privilege to a user in response to the establishment of a follow relationship or the like from a state in which the user relationship was not related, thereby encouraging the user to establish a user relationship such as a follow relationship.

[0088] The granting means 238 determines the value or amount of the reward depending on the number of follow relationships (first relationships).

[0089] According to the above configuration, the granting means 238 determines the value of the reward or the amount of the reward according to the number of user relationships such as follow relationships, so that the user can be motivated to build follow relationships in order to obtain more rewards or more valuable rewards. Therefore, according to the above configuration, the granting means 238 can further encourage the user to build user relationships such as follow relationships.

[0090] -Game execution means- The game execution means 239 permits a specific game control to the first user or the second user based on the registered user relationship. The game execution means 239 includes a first game execution means 2391 and a second game execution means 2392.

[0091] -First game execution means- The first game executing means 2391 permits the first user to control the first game, on condition that the second user is registered on the follow list (first list) of the first user, regardless of whether the first user is registered on the follow list (second list) of the second user.

[0092] The "first game control" refers to control over a game played by a first user, and is not, for example, conditioned on the first user and the second user being communicatively connected. The first game control may be, for example, game control based on the game information of the second user. Here, the "game control based on the game information of the second user" refers to, for example, control that temporarily enables the first user to play using the game media (such as a player character or items) of the second user (for example, so-called character rental, etc.).

[0093] The first game executing means 2391 may, for example, permit the first user to control the first game (game control based on the game information of the second user) as a privilege granted by the granting means 238 described below.

[0094] According to the above configuration, the execution control means 236 can permit the first user to use the game information of the second user as a privilege of stepping up (updating) the user relationship between the first user and the second user. Therefore, according to the above configuration, the execution control means 236 can encourage the first user to actively build a user relationship with other users who wish to use the game information. Furthermore, according to the above configuration, the user can share his / her game information with other users by stepping up the user relationship. Therefore, according to the above configuration, the execution control means 236 makes it possible to deepen the relationship between users.

[0095] -Second game execution means- The second game executing means 2392 permits the first user to control the second game on the condition that the second user is registered on the friend list (third list) of the first user.

[0096] The "second game control" is a control for a game played by a first user, and is a game control different from the first game control. The second game control is, for example, on the condition that the first user and the second user are connected to be able to communicate with each other. "The first user and the second user are connected to be able to communicate with each other" includes a state in which the first user's game device 5 is connected to the server device 2 and the second user's game device 5 is connected to the server device 2, and the second user's game device 5 is connected to the server device 2, and the like, and the like. The second game control is, for example, a control that enables a multiplay by communication between the first user and the second user. Note that this multiplay may be, for example, a case in which the first user and the second user play in a synchronized manner with the progress of the game, or may be asynchronously.

[0097] According to the above configuration, the second game executing means 2392 can permit game control (second game control) different from the first game control permitted by follow registration, on the condition that a friend is registered. Therefore, according to the above configuration, the second game executing means 2392 can differentiate between a relationship that can be registered without the other party's consent (follow relationship) and a relationship that requires consent (friend relationship) by changing the permitted game control. Therefore, according to the above configuration, by making such a distinction, a gradual user relationship (a friend relationship is more effective than a follow relationship) can be built, and interest in building relationships with other users can be improved.

[0098] According to the above configuration, the second game executing means 2392 can permit game control on the condition that the first user and the second user are connected via a network, with the condition that the friend is registered. Therefore, according to the above configuration, the second game executing means 2392 can permit second game control with a higher degree of permitted control depending on the friend having a higher relationship level, compared to the first game control on the condition that the follow is registered and not the condition that the first user and the second user are connected via a network.

[0099] <Matching means and game execution means> Here, an example of the processing of the matching means 237 and the game execution means 239 will be described with reference to Figs. 5 and 6. Fig. 5 is a diagram showing an example of the flow of the event part. Fig. 6 is a diagram showing an example of team organization by group members, etc. In this example, an example will be described in which a limited event starts at a specified start time (11:00) and ends at a specified end time (12:00) for each day during the event period.

[0100] (1) As shown in FIG. 5, upon arrival of the specified start time (11:00) on Xth day (X: natural number) during the limited event period, the matching means 237 matches and groups multiple users for performing multi-parts based on the progress of the solo parts.

[0101] (2) The execution control means 236 generates an event in which one of the group members encounters a raid boss in the solo part. When the execution control means 236 generates the event in which the group member encounters the raid boss, the execution control means 236 starts the multipart.

[0102] In the case of multipart, the execution control means 236 executes the following processes. The audio control means 563 and / or the display control means 564 of the game devices 5 of the other group members notify the other group members that they have encountered the raid boss. Each group member can freely participate in this multipart. When a group member who wants to participate in a multipart makes a request to participate in this multipart, the second reception means 2342 receives this request. The second reception means 2342 also receives this received request as a request to register the user in the partner list. In other words, when a user joins a team, the user is automatically registered as a partner with the other members of the team. The execution control means 236 accumulates the amount of damage done to the raid boss by each team member. When the total of the accumulated damage amounts reduces the raid boss's HP to 0, the execution control means 236 determines that the team has succeeded in defeating the raid boss. - It will be possible to accept requests to become friends or partners with team members even if there is no user relationship such as a follow relationship.

[0103] (3) When the specified end time (12:00) of the Xth day arrives and the multi-part ends, the game execution means 239 causes the undefeated raid boss to retreat. The granting means 238 calculates and grants a reward according to the amount of damage inflicted on the raid boss as follows: The awarding means 238 determines the ranking of the group members according to the amount of damage each of them inflicts on the raid boss. The awarding means 238 awards rewards to each team member according to the ranking. The granting means 238 distributes rewards to team members according to their contributions to defeating the raid boss. The reward providing means 238 increases the reward to be provided according to the number of following / followers of each team member.

[0104] When a raid boss is defeated, the display control means 564 displays a notice screen or an update screen, which will be described later, encouraging team members to follow up.

[0105] (4) When the specified start time of the X+1th day during the limited event has arrived, the matching means 237 matches and groups multiple users to perform the multi-part based on the progress of the solo part, as in the previous day. The matching means 237 matches users who were members of the same team last time, i.e., users who are partners, to the same matching group.

[0106] As shown in Fig. 6, when the multi-part (indicated as "Guardian Dragon Battle" in Fig. 6) starts, the matching means 237 matches and groups a plurality of users based on the progress of the solo part, etc. When the matching means 237 creates a matching group in this way, if user A, who is one of the group members, requests the creation of a team, the second reception means 2342 receives this request. When the second reception means 2342 receives this request, the fifth registration means 2354 registers the team created by user A (hereinafter also referred to as "team A").

[0107] User A can invite other group members (users B and C) to join team A. When the second reception means 2342 receives a request from user A to invite other members, it inquires of the other members whether or not they will accept the request, i.e., whether or not they will join team A. The second reception means 2342 also accepts the invitation request as a request for registration in the partner list of user A. When the second reception means 2342 receives "accept" from user B in response to the inquiry, the fifth registration means 2354 registers user B as a team member of team A in response to user B's acceptance. That is, the fifth registration means 2354 registers user B in the partner list of user A and registers user A in the partner list of user B in response to user B's acceptance.

[0108] User A can also invite a user (user D) who is not a group member to join team A. However, if the user is not a group member, the invitation is limited to users who are in a mutual follow or friend relationship. Furthermore, user D can only participate as a team member from the next multipart after accepting the invitation from user A and registering as a partner. When the next multipart starts, the matching means 237 matches team members users A, B, and D to be in the same team.

[0109] <Configuration of Game Device 5> Returning to Fig. 1, the explanation will be continued. A display 61, a speaker 62, and a touch pad 63 are externally connected or built into the game device 5. The game device 5 also has a network interface 51, a graphics processing unit 52, an audio processing unit 53, an operation unit 54, a storage unit 55, and a control unit 56. The network interface 51, the graphics processing unit 52, the audio processing unit 53, the operation unit 54, and the storage unit 55 are electrically connected to the control unit 56 via a bus 59.

[0110] The network interface 51 is communicatively connected to a communication network 6 in order to transmit and receive various data between the game device 5 and the server device 2.

[0111] The graphics processing unit 52 renders game images including characters and various objects related to the virtual game space in a moving image format in accordance with game image information output from the control unit 56. The graphics processing unit 52 is connected to a display 61, for example, a liquid crystal type, and the game images rendered in a moving image format are displayed on the display 61 as a game screen.

[0112] The audio processing unit 53 is connected to a speaker 62 , and reproduces and synthesizes game sounds in accordance with instructions from the control unit 56 , and outputs the sounds from the speaker 62 .

[0113] The operation unit 54 is connected to the touch pad 63, and transmits and receives data related to operation inputs to and from the touch pad 63. The user touches the touch pad 63 to input operation signals to the game device 5.

[0114] The storage unit 55 is composed of an HDD, an SSD, a RAM, a ROM, etc. The storage unit 55 stores game data downloaded from the server device 2, various programs including a part of the game program, account information of the own device 5, etc.

[0115] The storage unit 55 may store, for example, user information. The user information is at least a part of information in a user DB 221 stored in the storage unit 22 of the server device 2. A master of the user information is managed in the user DB 221, and the storage unit 55 of the game device 5 stores at least a part of the information of the master distributed from the server device 2.

[0116] The control unit 56 is configured with a microcomputer including a CPU and a semiconductor memory, and controls the operation of the device 5 itself.

[0117] The control unit 56 executes various programs to function as a communication means 561, a game execution means 562, an audio control means 563, and a display control means 564.

[0118] -Means of communication 561- The communication unit 561 is a function for communicating with the server device 2 via the network interface 51 .

[0119] The communication means 561 generates and transmits information that can be grasped by the server device 2 in response to various operation signals received by the operation unit 54 from the touch pad 63. For example, the communication means 561 transmits account information, download request information for new game data, a gacha execution request, a quest execution request, and the like to the server device 2. In addition, the communication means 561 receives from the server device 2 new game data transmitted from the server device 2 in response to the download request information, information regarding the game media selected by the lottery process, and the like.

[0120] -Game execution means- The game execution means 562 reads data such as virtual game space objects and textures included in the game data from the storage unit 55 in accordance with the operation of the touchpad 63 by the user of the own device 5, or uses the data received from the server device 2 to generate two-dimensional or three-dimensional game image information while executing a game program. As the game image information is processed by the graphics processing unit 52, the processed game images are successively displayed on the display 61.

[0121] The game execution means 562 then places a character on the game image in accordance with an operation of the user of the player's device 5, and controls the behavior of the character in the virtual game space in accordance with the user's operation and the progress of the game. For example, the game execution means 562 executes a quest in the game in accordance with an operation of the user via the touchpad 63 (hereinafter simply referred to as "user operation"). The game execution means 562 also causes the player character to use game media selected by the user in accordance with the user operation.

[0122] The game execution means 562 executes all or part of the game control permitted by the game execution means 239 of the server device 2 .

[0123] -Voice control means- The audio control means 563 controls audio output from the speaker 62 in response to operations by the user of the own device 5 during game execution.

[0124] -Display control means- When executing the game, the display control means 564 controls the display output of the display 61 in response to operations by the user of the player's device 5. The display control means 564 includes a presentation means 5641. The display control means 564 causes the display 61 to display, for example, a profile screen 610, a follow / follower screen 620, a friend request screen 630, a solo part play screen 640, a follow progress screen 650, a group member screen 660, a preview screen 670, an update screen 680, and the like, which will be described later.

[0125] As a registration-related process, the display control means 564 changes the display mode of a screen (hereinafter, also referred to as a "registration screen") for accepting a request to register a second user to the friend list (third list) of the first user. In other words, the registration screen is a screen for registering a friend. The registration screen includes, for example, a profile screen 610, a following / follower screen 620, a following progress screen 650, and / or a group member screen 660. For example, the display control means 564 may change the display mode so as to enable a button (for example, a relationship request button (friend request button) described later) for accepting a request to register a second user to the friend list of the first user on the registration screen. This "changing the display mode so as to enable" includes, for example, changing the relationship request button from a follow request button to a friend request button, changing the friend request button from hidden to visible, or changing the friend request button from unselectable (grayed out) to selectable.

[0126] According to the above configuration, the display control unit 564 can change the display mode of the registration screen for registering friends on the condition that a follow is registered. Therefore, according to the above configuration, the display control unit 564 can encourage users to build user relationships in stages.

[0127] The display control means 564 may further change the display mode of the registration screen between a case where the first user and the second user are mutually registered in the second user's follow list (second list) and the second user's follow list (first list) and a case where either the first user or the second user is registered in the second user's follow list or the first user's follow (first list). For example, when both users are registered in the follow list, that is, in the case of mutual following, the display control means 564 may display an icon indicating mutual following (for example, a mutual following icon described later) on the registration screen.

[0128] According to the above configuration, the display control means 564 can make it possible for the user to distinguish that two people are following each other by changing the display mode depending on whether the two people are following each other or one-way when registering a friend. Therefore, according to the above configuration, the display control means 564 can further encourage the user to register a friend when the two people are following each other, that is, when the two people are in a mutual relationship.

[0129] The display control means 564 displays a screen (hereinafter also referred to as a "notification screen") notifying that a special benefit will be given because the user relationship between the first user and the second user has been updated to a follow relationship (first relationship). After displaying the notification screen, the display control means 564 also displays an update screen for further updating the relationship between the first user and a user different from the second user to a follow relationship before the special benefit is given.

[0130] According to the above configuration, the display control means 564 can prompt the first user to further update the user relationship with a user other than the second user to a follow relationship before a benefit is granted as a result of the first user becoming in a follow relationship with the second user. Therefore, according to the above configuration, the display control means 564 can prompt the first user to update the user relationship with another user to a follow relationship at a more effective timing before the benefit is actually granted by notifying the first user that the benefit will be granted.

[0131] <Display control means and reception means> Here, examples of the processing of the display control means 564 and the reception means 234 will be described with reference to Figs. 7 to 15. Examples of screens displayed in common in the normal part and the event part will be described with reference to Figs. 7 to 10. Examples of screens displayed in the event part will be described with reference to Figs. 11 to 15. In these examples, the first user is user A, and the second user is user B. Also, an example of a screen when user A follows user B will be described with reference to Fig. 7, an example of a screen after user A follows user B with reference to Fig. 8, and an example of a screen after user B follows back user A with reference to Fig. 9.

[0132] As shown in Fig. 7, the display control means 564 displays a profile screen 610 on the display 61 of user A. The profile screen 610 is a screen for displaying the profile of each user. This profile includes information on people followed by each user, people who follow each user (followers), people who are friends with each user, and / or people who are partners with each user. The profile screen 610 includes a relationship summary display area 611 and a relationship request button 612.

[0133] The relationship summary display area 611 is an area that displays a summary of the user relationships registered by each user. The relationship summary display area 611 displays, for example, the number of people each user is following, the number of followers, the number of friends, and the number of partners.

[0134] The relationship request button 612 is a button for requesting the registration of a user relationship (follow, in this example) with a user (user B, in this example) displayed on the profile screen. When the relationship request button is pressed by user A, the display control means 564 transmits a request for registration of the specified relationship (follow) to the server device 2 via the network interface 51. When the server device 2 receives this registration request, the reception means 234 receives a request for registration of user B in the follow list of user A. The second registration means 2352 registers user B in the follow list of user A. In addition, when user B is registered in the follow list of user A, the reception means 234 enables a request for registration of user B in the friend list of user A and a request for registration of user A in the friend list of user B to be accepted as registration-related processing.

[0135] As shown in Fig. 8 and Fig. 9, the display control means 564 causes a following / followers screen 620 to be displayed on the display 61 of user A. The following / followers screen 620 includes a following display area 620a of Fig. 8 and a follower display area 620b of Fig. 9. On the following / followers screen 620, the display contents can be switched by specifying the tabs of the following display area 620a and the follower display area 620b.

[0136] 8, the follow display area 620a is an area that displays users followed by user A. The follow display area 620a includes a follow summary display area 620a1 and a follow list display area 620a2.

[0137] The follow summary display area 620a1 displays the number of users followed by user A. The follow list display area 620a2 displays a list of users followed by user A. For each user item displayed in the list, the follow list display area 620a2 displays the relationship level between user A and that user (e.g., one-sided follow or mutual follow) and a relationship request button for requesting registration of a user relationship of a higher relationship level. For example, for the item of user B, the follow list display area 620a2 displays a friend request button 620a21 for requesting registration of a friend with a relationship level of follow or higher as the relationship request button.

[0138] The friend request button 620a21 is a button for registering a friend relationship. When the friend request button 620a21 is pressed by user A, the display control means 564 transmits a friend registration request to the server device 2 via the network interface 51. When the server device 2 receives this friend registration request, the first reception means 2341 receives a request to register user B in the friend list of user A. When the first reception means 2341 receives this friend registration request, it causes the display control means 564 to display a friend request screen 630 of FIG. 10 on the display 61 of user B in order to inquire of user B about the acceptance of the friend registration request.

[0139] 9, the follower display area 620b is an area that displays people (followers) who follow the user A. The follower display area 620b includes a follower summary display area 620b1 and a follower list display area 620b2.

[0140] The follower summary display area 620b1 displays the number of user A's followers.

[0141] The follower list display area 620b2 displays the followers of user A in a list. In the item of each user displayed in the list, the follower list display area 620b2 displays the user relationship between user A and the user and a relationship request button for requesting registration of a user relationship of a higher relationship level. For example, when the user relationship between user A and user B is mutual follow, the follower list display area 620b2 displays a mutual follow icon 620b21 including the text "mutual". Also, for example, when the user relationship between user A and user X is in a one-sided follow state from user X, the follower list display area 620b2 displays a follow request button 620a22 for requesting registration of follow to make it a mutual follow, which is a relationship level higher than one-sided follow, and a friend request button 620a23 for requesting registration of a friend.

[0142] 10, the display control means 564 causes a friend request screen 630 to be displayed on the display 61 of the user B. The friend request screen 630 is a screen for inquiring of the user B as to whether to accept a friend registration request from the user A. The friend request screen 630 includes an OK button 631, a hold button 632, and a profile display button 633.

[0143] When the OK button 631 is pressed by user B, the display control means 564 transmits a response of consent from user B to the above-mentioned consent inquiry to the server device 2 via the network interface 51. When the server device 2 receives this response of consent from user B, the third registration means 2353 registers user B in the friend list of user A and registers user A in the friend list of user B in response to this consent from user B.

[0144] When the hold button 632 is pressed by user B, the display control means 564 transmits a hold response from user B to the above-mentioned inquiry of consent to the server device 2 via the network interface 51. When the server device 2 receives this hold response from user B, the registration means 235 causes the display control means 564 to notify user A of the hold.

[0145] When the profile display button 633 is pressed, the display control means 564 transitions to a profile screen of user A (not shown).

[0146] 11, the display control means 564 displays a solo part play screen 640 on the display 61. The solo part play screen 640 includes a progress area 641, a friend party number display icon 642, a hierarchical boss display area 643, and a raid boss display area 644.

[0147] The progress area 641 is an area for progressing through the solo part. As the user presses the progress area 641, stamina is consumed and progress advances. When progress for each layer reaches a predetermined progress rate (100%), the game execution means 239 causes an event in which a layer boss appears. When an event in which a layer boss appears occurs, the display control means 564 causes a layer boss icon (not shown) to be displayed in the layer boss display area 643. When the displayed layer boss icon is pressed, the game execution means 239 starts a battle event with the layer boss.

[0148] The friend party number display icon 642 displays the number of friend parties that user A has in stock.

[0149] When a raid mission is started and an event occurs in which one of the users in the matching group encounters a raid boss, the display control means 564 displays a raid boss icon (not shown) in the raid boss display area 644. When the displayed raid boss icon is pressed, the game execution means 239 starts a battle event with the raid boss.

[0150] 12, in the event part, the display control means 564 causes a follow progress screen 650 to be displayed on the display 61. The follow progress screen 650 includes a follow progress list display area 651.

[0151] The follow progress list display area 651 displays the progress in the event part of each user being followed (hereinafter also referred to as "each following user"). In the follow progress list display area 651, each following user is displayed divided by the hierarchical level in which they currently reside. For the item of user I, the follow progress list display area 651 displays, as relationship request buttons, a friend request button 6511 for requesting the registration of a friend with a relationship level of follow or higher, and a partner request button 6512 for requesting the registration of a partner limited to the event part.

[0152] The partner request button 6512 is a button for registering a partner relationship. When the partner request button 6512 is pressed by user A, the display control means 564 transmits a request for partner registration to the server device 2 via the network interface 51. When the server device 2 receives the request for partner registration, the reception means 234 receives a request for registration of user I in the partner list of user A. When the reception means 234 receives the request for partner registration, the display control means 564 causes the display control means 564 to display a partner request screen (not shown) on the display 61 of user I in order to inquire of user I whether or not to accept the request for partner registration, similar to the case of friends. When user I responds to the request by accepting the request on the partner request screen, user I is registered in the partner list of user A in response to user I's acceptance, and user A is registered in the partner list of user I.

[0153] 13, the display control means 564 displays a group member screen 660 on the display 61. The group member screen 660 is a screen for displaying members grouped in an event part. The group member screen 660 includes a matching period display area 661 and a member list display area 662.

[0154] The matching period display area 661 displays the period during which the current (at the time of display; the same applies below) matching (grouping) is valid in the multipart (hereinafter also referred to as the "matching period").

[0155] Member list display area 662 displays, for each user of group members displayed in the list, the user name, the relationship level with that user, and a relationship request button for requesting registration of a user relationship of a higher relationship level.

[0156] For example, in the item for user C, the member list display area 662 displays a follow request button 6621 for requesting registration of a follow since there is currently no user relationship.

[0157] For example, for user D, the member list display area 662 displays a one-sided follow icon 6622 indicating the current one-sided follow relationship, and also displays a friend request button 6623 for requesting registration of a friend, which is a higher relationship level, and a partner request button 6624 for requesting registration of a partner.

[0158] For example, for User F, the member list display area 662 displays a mutual follow icon 6625 indicating the current mutual follow relationship, and also displays a friend request button 6626 for requesting registration of a friend, which is a higher relationship level, and a partner request button 6627 for requesting registration of a partner.

[0159] For example, in the user G entry, the member list display area 662 displays a friend icon 6628 indicating the current friend relationship, and also displays a partner request button 6629 for requesting registration of a partner, which is a higher relationship level.

[0160] 14, the display control means 564 displays a notice screen 670 on the display 61. The notice screen 670 is a screen for notifying the user that a benefit (a reward in this example) will be given in response to the update to the follow relationship in the event part. The notice screen 670 includes a notice display area 671 and an update promotion display area 672.

[0161] The notice display area 671 displays a message notifying the user that a special benefit will be given and an image showing the special benefit to be given.

[0162] The update prompting display area 672 is an area for prompting the updating of the user relationship to a follow relationship. The update prompting display area 672 includes a message prompting the updating of the follow relationship, such as "If you follow x more people, the current subjugation reward will be x times more," and an update screen button 6721 for displaying an update screen 680. When the update screen button 6721 is pressed by the user A, the display control means 564 causes the update screen 680 to be displayed on the display 61.

[0163] 15, the display control means 564 causes an update screen 680 to be displayed on the display 61. The update screen 680 includes a group member list display area 681.

[0164] The group member list display area 681 displays, in the item of each group member displayed in the list, the relationship level between the user A and the user and a relationship request button for requesting registration of a relationship level higher than that. The group member list display area 681 may, for example, hide members for whom a user relationship of a relationship level of follow or higher has already been registered. In this case, the group member list display area 681 may limit the relationship request button for each group member item to a follow request button. As another example, although not shown, the group member list display area 681 may, for example, hide members for whom a user relationship of a relationship level of friend or higher has been registered. In this case, the group member list display area 681 may limit the relationship request button for each group member item to a follow request button and a friend request button. Also, although not shown, the group member list display area 681 may, for example, display the contribution level, such as the amount of damage inflicted on a raid boss, in the item of each group member displayed in the list.

[0165] <Operation flow of game system 1> 16 to 19, examples of process flows and interactions executed by the game system 1 will be described.

[0166] 16 is a flow diagram showing an example of a flow from a process of accepting a request from a first user to register a follow for a second user to a process of permitting second game control via friend registration. As shown in FIG. 16, first, the accepting means 234 of the server device 2 accepts, from the first user, a request to register the second user in the follow list (first list) of the first user (step st1).

[0167] Next, the first registration means 2351 registers the second user in the follow list of the first user without the consent of the second user (step st2).

[0168] Next, the first game executing means 2391 permits the first user to control the first game, regardless of whether the first user is registered on the second user's follow list (second list), on the condition that the second user is registered on the first user's follow list (step st3).

[0169] Next, the execution control means 236 executes a registration-related process for registering the second user in the friend list (third list) of the first user, on condition that the second user is registered in the follow list of the first user, or the first user is registered in the follow list of the second user (step st4). In this example, as the registration-related process, the first reception means 2341 enables reception of a request for registering the second user in the friend list of the first user.

[0170] Next, the first reception means 2341 receives a request to register the second user in the friend list of the first user (step st5).

[0171] Next, the first reception means 2341 inquires of the second user about consent to the above-mentioned registration request, and obtains consent as a response to the inquiry (step st6).

[0172] Next, the third registration means 2353 registers the second user in the friend list of the first user in response to the consent of the second user (step st7).

[0173] Next, the third registration means 2353 registers the second user in the friend list of the first user, and also registers the first user in the friend list (fourth list) of the second user (step st8).

[0174] Next, the second game executing means 2392 permits the first user to control the second game on the condition that the second user is registered in the friend list of the first user (step st9).

[0175] Fig. 17 is a flow diagram showing an example of a flow from a matching process of a plurality of users at the start of an event part to the start of the next event part. As shown in Fig. 17, the matching means 237 of the server device 2 matches a plurality of users for executing a multi-part (second game part) based on the progress of the solo part (first game part) (step st11).

[0176] Next, the game execution means 239 starts the multipart (step st12).

[0177] Next, the registration means 235 updates the user relationship in the started multipart (step st13).

[0178] Next, the game execution means 239 ends the multipart (step st14).

[0179] Next, when the next multi-part starts following the completed multi-part, the matching means 237 matches multiple users to perform the next multi-part based on the progress of the solo part and the updated user relationships (step st15).

[0180] Fig. 18 is a sequence diagram showing the flow and interactions from the process of accepting a request from user A to register user B as a follower, through friend registration, to the process of allowing users A and B to control the second game. In this example, the first user is user A and the second user is user B. As shown in Fig. 18, first, the game execution means 562 of the game device 5a of user A accepts a request from user A to register user B in the follow list of user A (step st21).

[0181] Next, when the game execution means 562 receives a request from the user A to register the user B in the follow list of the user A, the game execution means 562 transmits this registration request to the server device 2 (step st22).

[0182] Next, the accepting means 234 of the server device 2 accepts the request to register user B in the follow list of user A (step st23).

[0183] Next, in response to the received request for registration of user B in the follow list of user A, the first registration means 2351 registers user B in the follow list of user A without user B's consent (step st24).

[0184] Next, the first game executing means 2391 permits user A to control the first game, on the condition that user B is registered on user A's follow list, regardless of whether user A is registered on user B's follow list (step st25).

[0185] Next, the first reception means 2341 enables reception of requests for registration of user B and user A in the friend lists of user A and user B, respectively (step st26).

[0186] Next, the receiving means 234 responds with the result of the received follow registration request (follow registration completed) to each of the game device 5a and the game device 5b of user B (steps st27 and st28).

[0187] Next, the display control means 564 of the game device 5a changes the display mode of the registration screen in accordance with the result of the response to the follow registration request (step st29). Similarly, the display control means 564 of the game device 5b also changes the display mode of the registration screen in accordance with the result of the response to the follow registration request (step st30).

[0188] Next, the game execution means 562 of the game device 5a receives a request from the user A to register the user B in the friend list of the user A (step st31).

[0189] Next, when the game execution means 562 of the game device 5a receives a request from the user A to register the user B in the friend list of the user A, the game execution means 562 transmits this registration request to the server device 2 (step st32).

[0190] Next, the first reception means 2341 receives a request to register the user B in the friend list of the user A (step st33).

[0191] Next, the first reception means 2341 inquires of the game device 5b about whether or not the request for registering the user B in the friend list of the user A is approved (step st34).

[0192] Next, the game execution means 562 of the game device 5b receives a response to the inquiry about the consent from the user B (step st35).

[0193] Next, upon receiving a response to the inquiry about consent from the user B, the game execution means 562 of the game device 5a transmits this response to the server device 2 (step st36).

[0194] Next, if the response from user B is "accepted", the server device 2 executes processing within the area indicated by the combined fragment opt1 (Option1). Specifically, the third registration means 2353 of the server device 2 registers user B in the friend list of user A in response to user B's acceptance (step st37). Together with this registration, the third registration means 2353 registers user A in the friend list of user B (step st38).

[0195] Next, the second game executing means permits user A and user B to control the second game on the condition that user B and user A are registered in the friend list of user A and user B, respectively (step st39).

[0196] Fig. 19 is a sequence diagram showing the flow of processing and interactions executed in the event part, particularly in the multi-part. In this example, the first user is assumed to be user A, and the second user is assumed to be user B. As shown in Fig. 19, first, the execution control means 236 of the server device 2 starts the event part (step st41).

[0197] When the execution control means 236 starts the event part, the processing of the multipart in the area indicated by the combined fragment Loop1 is repeatedly executed every day until the end condition (until the holding period of the event part ends) is satisfied. Specifically, first, the matching means 237 detects the specified start time of the multipart and starts the multipart (step st42).

[0198] Next, the matching means 237 matches and groups a plurality of users for performing the multi-part based on the progress of the solo part of the event part (step st43). In this example, a group a1 is created, and a user A and a user B are grouped into the group a1.

[0199] Next, in response to the start of the limited event, the second accepting means 2342 enables accepting requests from other group members to the partner list of the group member (step st44).

[0200] Next, the execution control means 236 generates an event in which one of the group members of group a1 encounters the raid boss in the solo part, and starts the multi-part (step st45). In this example, an example will be described in which the group members of group a1 other than user A and user B encounter the raid boss.

[0201] Next, the execution control means 236 notifies the game devices 5 of the group members other than the group member who encountered the raid boss that the raid boss has been encountered, to indicate that the multi-part has started (step st46).

[0202] Next, the game execution means 562 of the game device 5a receives a request to create a team a11 from the user A (step st47).

[0203] Next, upon receiving the request to create the team a11, the game execution means 562 of the game device 5a transmits the request to create the team a11 to the server device 2 (step st48).

[0204] Next, the fifth registration means 2354 of the server device 2 accepts the request for creating the team a11 and newly registers the team a11 (step st49).

[0205] Next, the game execution means 562 of the game device 5a receives a request from the user A to invite the user B to the team a11 (step st50).

[0206] Next, when the game execution means 562 of the game device 5a receives the invitation request from the user B to the team a11, the game execution means 562 transmits the invitation request to the server device 2 (step st51).

[0207] Next, the second accepting means 2342 of the server device 2 accepts the invitation request from user B to the team a11 as a request for registering user B in the partner list of user A (step st52).

[0208] Next, the second accepting means 2342 inquires of the game device 5b about acceptance of the invitation request from the user B (step st53).

[0209] Next, the game execution means 562 of the game device 5b receives a response to the invitation inquiry from the user B (step st54).

[0210] Next, when the game execution means 562 of the game device 5a receives a response to the invitation inquiry from the user B, the game execution means 562 transmits this response to the server device 2 (step st55).

[0211] Next, if the response from user B is "accepted", that is, if user B joins team a11, the server device 2 executes processing within the area indicated by the combined fragment opt2 (Option2). Specifically, the fifth registration means registers user B in the partner list of user A in response to the above-mentioned acceptance from user B (step st56). Together with this registration, the fifth registration means registers the partner list of user A in the partner list of user B (step st57).

[0212] Next, the execution control means 236 executes a battle event between the team a11, in which the user A and the user B are team members, and the raid boss (step st58).

[0213] Next, when the execution control means 236 detects the specified end time, it ends the battle event and ends the multi-part for that day (step st59).

[0214] To summarize the above, the control unit 23 (computer) of the server device 2 functions as a matching means 237 that matches multiple users to perform the second game part based on the progress of the first game part, and a registration means 235 that registers the user relationship between a first user and a second user included in the multiple users and updates the user relationship in the second game part, and when the third game part is started following the second game part, the matching means 237 matches multiple users to perform the third game part based on the progress of the first game part and the updated user relationship.

[0215] <Effects> According to this embodiment, users who have built a relationship in a matched multi-part can be matched in the next multi-part that is subsequently started. Also, according to this embodiment, users can be matched in a multi-part according to the progress of the game parts including the solo part. Therefore, according to this embodiment, it is possible to further deepen the user relationship through successive multi-parts (for example, aiming to conquer a limited event together, etc.), and it is also possible to encourage encounters with other users. Therefore, according to this embodiment, since the user relationship with the other matched users can be deepened, it is possible to improve the construction of the relationship with the other matched users.

[0216] [Variations] Although the present invention has been described based on the above embodiment, the present invention is not limited to the above embodiment. The following cases are also included in the present invention.

[0217] [First Modification] In the above embodiment, an example has been described in which a friend relationship is registered by registering a follow and the request for registration can be accepted, and registration is performed with the consent of the other party, but the friend relationship is not limited to this. For example, a friend relationship may be limited to a certain period of time, similar to a partner relationship, and a request for friend registration may be accepted on the condition that a limited event starts, and the friend registration may be cancelled when the limited event ends.

[0218] The first receiving means 2341 may be capable of receiving a request to register a second user in the friend list (third list) of the first user on condition that a limited-time event that is held for a limited period of time starts.

[0219] The third registration means 2353 may, upon the end of the limited event, cancel the registration of the second user from the friend list (third list) of the first user and may also cancel the registration of the first user from the friend list (fourth list) of the second user.

[0220] According to the above configuration, the third registration means 2353 can set the friend relationship to be valid only during the limited event. Therefore, according to the above configuration, the third registration means 2353 can register the friend relationship only during the limited event and exert its effect (for example, being able to play against the friend or being able to play cooperatively, etc.).

[0221] [Second modified example] Although not shown in the above embodiment, when a predetermined condition is satisfied based on preset information, a request for friend relationship registration may be automatically made. For example, when the first user and the second user are mutual followers, a request for the second user to be registered in the friend list of the first user may be automatically made (without the need for the first user's operation) based on information preset by the first user. Also, although not shown in the above embodiment, a request for friend relationship registration may be automatically accepted based on preset information. The user information may include, for example, information regarding the setting of an automatic request for friend relationship registration and information regarding the setting of automatic approval for friend relationship registration.

[0222] The control unit 56 of the game device 5 may function as a requesting means (not shown) by, for example, executing various programs. When a second user is registered in the friend list (first list) of the first user and the first user is registered in the friend list (second list) of the second user according to preset user information of the first user, the requesting means requests the first receiving means to register the second user in the friend list (third list) of the first user without requiring an operation by the first user.

[0223] According to the above configuration, when a friend relationship requirement is satisfied based on preset information, the request means can automatically request registration of the friend relationship without requiring user operation. Therefore, according to the above configuration, the request means can save the user the trouble of operating the user when requesting the registration, and can provide a means for building a user relationship that is easy to use.

[0224] The third registration means 2353 may, for example, register the second user as a friend of the first user in response to a request for registration of the second user in the friends (third list) of the first user based on preset user information of the second user, without requiring an operation by the second user to approve the registration. In addition, the third registration means 2353 may, for example, register the first user as a friend of the second user together with this registration.

[0225] According to the above configuration, the request means can automatically accept the request for registering a friend relationship based on preset information without the need for user operation. Therefore, according to the above configuration, the request means can save the user the trouble of operating the request for acceptance, and can provide a means for building a user relationship that is easy to use.

[0226] <Display control means> Now, with reference to FIG. 20, an example of processing by the display control means 564 regarding settings for automatic request and automatic approval in friend relationship registration will be described.

[0227] As shown in FIG. 20, the display control means 564 displays an automatic setting screen 690 on the display 61. The automatic setting screen 690 includes a setting area 691 and an OK button 692. The setting area includes an automatic request setting form for setting whether to automatically request friend registration on the condition of being followed back (in this example, a check box labeled "Automatically request a friend if followed back"), and an automatic approval setting form for setting whether to automatically approve friend registration. When the OK button 692 is pressed, the display control means 564 transmits the input contents of each form included in the setting area 691 to the server device 2 via the network interface 51. When the server device 2 receives the input contents, the third registration means 2353 reflects the input contents in the input user information.

[0228] [Third Modification] Although not shown in the above embodiment, the updated user relationships referred to when matching multiple users in the multipart may be the user relationships updated in the normal part.

[0229] The registration means 235 may update the user relationship, for example, in a normal part (fourth game part) that progresses independently of the solo part (first game part) and the multi-part (second game part).

[0230] For example, when the next multi-part (third game part) starts after the user relationships have been updated in the normal part (fourth game part), the matching means 237 may match multiple users to execute the next multi-part (third game part) based on the solo part (first game part) and the updated user relationships.

[0231] According to the above configuration, if the user updates the user relationship in the normal part, the user can enter the candidates (population of the lottery) to be matched in the multi-part. Therefore, according to the above configuration, the matching means 237 can increase the possibility of being matched.

[0232] The accepting means 234 accepts, for example, a request to update a user relationship from a first user.

[0233] The receiving means 234 (second receiving means 2342) may, for example, in the normal part (fourth game part), be able to receive a request to update the user relationship to a partner relationship (third relationship) with the permission condition being that the user relationship has been updated to a follow relationship (first relationship) or a friend relationship (second relationship). Furthermore, the receiving means 234 (second receiving means 2342) may relax the permission condition, for example, in the multi-part (second game part). For example, the receiving means 234 may be able to receive a request to update to a partner relationship (third relationship) if the other user making the request in the multi-part is a group member of the same group.

[0234] According to the above configuration, the reception means 234 can differentiate between the normal part and the event part (multi-part) in building a partner relationship. Therefore, according to the above configuration, the reception means 234 can create a sense of specialness in the multi-part in building a partner relationship (for example, a sense of specialness due to being friends of the same group or friends who have fought together as members of the same team), and can improve interest.

[0235] For example, in the normal part (fourth game part), when a request to update the user relationship is accepted, the registration means 235 updates and registers the user relationship to at least one of a follow relationship (first relationship) that does not require the consent of the second user, or a friend relationship (second relationship) or a partner relationship (third relationship) that requires the consent of the second user.

[0236] The game execution means 239 may, for example, permit the first user to control the game based on the game information of the second user in the normal part (fourth game part) in response to the user relationship being updated to a friend relationship (second relationship).

[0237] The matching means 237 may, for example, enable matching between the first user and the second user in the next multi-part (third game part), on the condition that the user relationship has been updated to a partner relationship (third relationship).

[0238] According to the above configuration, if the user updates the user relationship to a partner relationship in the normal part, the user can be matched in the multi-part. Therefore, according to the above configuration, the matching means 237 can perform the same group matching even when the user relationship is updated to a partner relationship in the normal part.

[0239] [Fourth Modification] In the above embodiment, an example has been described in which partner relationships are registered and managed in the partner lists (fifth list and sixth list) of the first user and the second user, respectively, but the present invention is not limited to this. For example, as another example of a method for registering and managing partner relationships, a list (hereinafter also referred to as a "team member list") may be provided for registering team members participating in each team organized in multipart. Partner relationships may also be registered in this team member list.

[0240] The team member list may include, for example, team identification information for identifying each team, leader user identification information for identifying a leader user of each team (a user who created each team), and one or more member user identification information for identifying one or more team member users of each team. In addition, in a team created by user A, when user A invites user B and user C to join and each is accepted, the fifth registration means 2354 registers user B and user C in the same team member list. The fifth registration means 2354 may update the user relationship between user B and user C registered in the same team member list to a partner relationship. In other words, the matching means 237 may match user B and user C to the same group on the condition that they participate in the same team (on the condition that they are registered in the same team member list), assuming that the user relationship between them is a partner relationship.

[0241] [Other embodiments] The various control means and processing procedures described in the above embodiment are merely examples, and are not intended to limit the scope of the present invention, its applications, or its uses. The various control means and processing procedures can be appropriately modified in design without departing from the spirit of the present invention.

[0242] In the above embodiment, the game device 5 is a smartphone. However, the game device 5 may be an amusement machine provided in a game center or the like.

[0243] The game may be an action game, a shooting game, a role-playing game, a simulation game, a board game, a puzzle game, etc., and can be applied to various types of games.

[0244] In the above embodiment, the object is a player character, but is not limited to this. For example, the object may be a card or an item (weapon, armor, or other equipment) used in the virtual game space.

[0245] In the above embodiment, the server device 2 and the multiple game devices 5 are integrated to function the game program, but the present invention is not limited to this. All the means of the game program, i.e., the reception means, the registration means, the execution control means, the matching means, the granting means, the game execution means, and the display control means, may be provided in the server device 2 alone, the game device 5 alone, a communication terminal other than the server device and the game device 5 alone, or two devices that are combined among them (for example, distributed processing in the server device 2 and the game device 5, etc.). In addition, when the server device, the game devices, and the communication terminals are integrated to function, it is also possible to appropriately change which means are to be operated in which device. For example, the control unit 56 of the game device 5 may execute various programs to function as the reception means, the registration means, the execution control means, the matching means, the granting means, and the game execution means of the server device 2 exemplified in the above embodiment.

[0246] Even when these other embodiments are adopted, the effects of the present embodiment are exhibited. In addition, the present embodiment can be appropriately combined with other embodiments, and other embodiments can be appropriately combined with each other. [Explanation of symbols]

[0247] 1. Game System 2. Server equipment 23 Control Unit 235 Registration Method 237 Matching Method

Claims

[Claim 1] Computer, a matching means for matching a plurality of users for executing a second game part based on the progress of the first game part; a registration means for registering a user relationship between a first user and a second user included in the plurality of users, the registration means functioning as a registration means for updating the user relationship in the second game part; the matching means, when a third game part is started following the second game part, matches a plurality of users for executing the third game part based on the progress of the first game part and the updated user relationships; Game program.

Images