JP7620219B2 - GAME PROGRAM, GAME DEVICE AND GAME SYSTEM - Google Patents

Description

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

Conventionally, there are games in which a user builds relationships (following, following, etc.) with other users and provides advantageous effects to the user depending on the built relationships. For example, Patent Literature 1 discloses a game system in which a first user and a second user are associated in response to an association request from the second user, thereby enabling the second user to participate in a match between the first user and to watch the match. In addition, in this game system, if an association request is received without obtaining the consent of the first user, the second user is designated as the first related party, whereas if an association request including the consent of the first user is received, the second user is designated as the second related party, and the first user can select whether the second user who enables the first user to participate in a match is designated as the first related party or the second related party.

JP 2016-123756 A

In the above-mentioned conventional technology, relationships with other users can only be built in one of two ways: either the other user accepts the association request from the user or the other user does not accept it. However, building real human relationships is not this simple. For this reason, the conventional technology leaves room for improvement in the interest of building relationships with other users.

The present disclosure provides a game program, a game device, and a game system that can improve interest in building relationships with other users.

A first aspect includes a computer comprising:
a first registration means for registering a second user in a first list of a first user without the consent of the second user;
a second registration means for registering the first user in a second list of the second user without the consent of the first user;
a first game executing means for permitting the first user to control a first game, on condition that the second user is registered in the first list, regardless of whether the first user is registered in the second list;
an execution control means for executing a registration-related process for registering the second user in a third list of the first user, on condition that the second user is registered in the first list or the first user is registered in the second list;
a third registration means for registering the second user in the third list and registering the first user in a fourth list of the second user in response to the consent of the second user;
a second game execution means for permitting the first user to control a second game on condition that the second user is registered in the third list;
It is a game program.

In addition, in the first aspect, the first game control is not performed on the condition that the first user and the second user are connected to each other so as to be able to communicate with each other,
The second game control is performed on the condition that the first user and the second user are connected to each other so as to be able to communicate with each other.

In the first aspect, the computer includes:
As the registration-related process, the information processing device may further function as a first accepting unit that can accept a request to register the second user in the third list.

In addition, in the first aspect, the third registration means can execute, as the registration-related process, a process associated with the registration when the second user is registered in the third list.

In the first aspect, the computer includes:
As the registration-related process, the device may further function as a display control unit that changes a display mode of a screen for accepting a request to register the second user in the third list.

In addition, in the first aspect, the display control means can further change the display mode of the screen when the first user and the second user are both registered in the second list and the first list, and when either the first user or the second user is registered in the second list or the first list.

In the first aspect, the computer includes:
and further functioning as a first accepting unit that is capable of accepting a request for registering the second user in the third list on condition that a limited-time event is started.
The third registration means may cancel the registration of the second user from the third list and cancel the registration of the first user from the fourth list in response to the end of the limited event.

In the first aspect, the computer includes:
The device further functions as a second receiving means for receiving a request for registration of the second user to the first user's fifth list, on the condition that the first user and the second user are mutually registered in the second list and the first list, or the second user is registered in the third list.

In the first aspect, the computer includes:
The device further functions as a fifth registration means for registering the second user in the fifth list in response to the consent of the second user, and for registering the first user in a sixth list of the second user.

In addition, in the first aspect, the second reception means is capable of receiving a request for registering the second user to the fifth list on condition that a limited-time event is started,
The fifth registration means may cancel the registration of the second user from the fifth list and cancel the registration of the first user from the sixth list in response to the end of the limited event.

In the first aspect, the computer includes:
a first receiving means for receiving a request for registering the second user in the third list as the registration-related process;
When the second user is registered in the first list and the first user is registered in the second list according to pre-set user information of the first user, the device can further function as a requesting means for requesting the first receiving means to register the second user in the third list without requiring any operation by the first user.

In addition, in the first aspect, the third registration means can register the second user to the third list in response to a request for registration of the second user to the third list based on predefined user information of the second user, without requiring an operation by the second user to accept the registration.

The second aspect is
a first registration unit for registering a second user in a first list of a first user without consent of the second user;
a second registration unit that registers the first user in a second list of the second user without the consent of the first user;
a first game executing unit that permits the first user to control a first game, on condition that the second user is registered in the first list, regardless of whether the first user is registered in the second list;
an execution control unit that executes a registration-related process for registering the second user in a third list of the first user, on condition that the second user is registered in the first list or the first user is registered in the second list; and
a third registration unit that registers the second user in the third list in response to the consent of the second user, and registers the first user in a fourth list of the second user;
a second game executing unit that permits the first user to control a second game on condition that the second user is registered in the third list;
It is a server device.

The third aspect is:
a first registration unit for registering a second user in a first list of a first user without consent of the second user;
a second registration unit that registers the first user in a second list of the second user without the consent of the first user;
a first game executing unit that permits the first user to control a first game, on condition that the second user is registered in the first list, regardless of whether the first user is registered in the second list;
an execution control unit that executes a registration-related process for registering the second user in a third list of the first user, on condition that the second user is registered in the first list or the first user is registered in the second list;
a third registration unit that registers the second user in the third list in response to the consent of the second user, and registers the first user in a fourth list of the second user;
a second game executing unit that permits the first user to control a second game on condition that the second user is registered in the third list;
It is a game system.

According to the present disclosure, a game program, a game device, and a game system are provided that can improve interest in building relationships with other users.

1 is a block diagram showing a configuration of a game system according to an embodiment of the present invention. 11A and 11B are schematic diagrams for explaining examples of relationship levels and their effects in the present embodiment. 10A and 10B are schematic diagrams for explaining examples of relationship levels and their conditions in the present embodiment. 4 is a schematic diagram for explaining an example of a game part in the present embodiment. FIG. 5 is a schematic diagram for explaining an example of the flow of a game part in the present embodiment. FIG. 11 is a schematic diagram for explaining an example of team composition in a game part in this embodiment. FIG. 13 is an example of a screen that is displayed on a display during a game. 13 is an example of a screen that is displayed on a display during a game. 13 is an example of a screen that is displayed on a display during a game. 13 is an example of a screen that is displayed on a display during a game. 13 is an example of a screen that is displayed on a display during a game. 13 is an example of a screen that is displayed on a display during a game. 13 is an example of a screen that is displayed on a display during a game. 13 is an example of a screen that is displayed on a display during a game. 13 is an example of a screen that is displayed on a display during a game. FIG. 2 is a flow chart showing a series of operations of the game system in the present embodiment. FIG. 2 is a flow chart showing a series of operations of the game system in the present embodiment. FIG. 2 is a sequence diagram showing a series of operations of the game system in this embodiment. FIG. 2 is a sequence diagram showing a series of operations of the game system in this embodiment. 13 is an example of a screen that is displayed on a display during a game.

The game system 1 according to an embodiment of the present disclosure will be described with reference to the drawings.

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

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, which are non-player characters.

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 these user relationships in a list. 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.

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 users whom the first user follows (hereinafter also referred to as "following users") are registered.
(2) Second user's follow list: This is one aspect of the second list of the second user, and 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 aspect of the sixth list of the second user, and is a list for registering partner users of the second user.

Now, with reference to Figures 2 and 3, an example of the relationship levels will be described. Figure 2 is a table showing an example of the relationship levels and their effects. As shown in Figure 2, an example in which the relationship levels are set to four levels, 1 to 4, will be described, but the relationship levels are not limited to these. In the "Relationship Level Description" 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 the "Effect" column of the table, an example of the in-game effect that occurs due to each relationship is described. For example, the effect of relationship level 1 is that it is possible to view information such as the progress of the person being followed and to rent the player character of the person being followed. In addition, this in-game effect may differ between the normal part and the event part.

"Following" refers to a relationship in which you can track information such as the progress of the other user's game. Furthermore, a following relationship can be registered without the consent of the other user. "One-sided following" 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. Furthermore, "mutual following" 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. A following relationship is one aspect of a first relationship.

"Friend" refers to 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.

"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, as registration requires the consent of the other user, and is always mutual. A partner relationship is one aspect of the third relationship.

A "normal part" is one of the game parts, and is a game part that the user normally progresses through in the game. A normal part may be, for example, a game part that is the main part of the game. An "event part" is one of the game parts, and is a game part that occurs as an event in the 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 the game.

A "game part" is content that a user can play within a game. Game parts include, for example, quests (game tasks or goals), mini-games, missions (game assignments), or events.

Figure 3 is a table showing an example of relationship levels and the conditions for each relationship level. As shown in Figure 3, each relationship level has its own requirement and registration conditions. For example, in the case of relationship level 3, in order for a user to request friend registration, the requirement is that the user relationship with the other user must be one-sided or mutual follow. Also, in the case of relationship level 3, even if this registration request can be made, in order for the friend registration to be carried out, the other user must consent to this registration request as a registration condition.

Now, with reference to Figure 4, we will explain examples of the normal part and the event part, which are game parts in this embodiment.

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

"Gacha" is a method in which the server device 2 selects any game medium from the lottery list 222 based on a predetermined selection ratio by lottery. The selected game medium is given to the user's game device 5. "Giving the game medium selected by gacha to the user/owning it" is synonymous with "associating/being associated with the game medium selected by the lottery process with identification information indicating the user."

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

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 specified field as part of solo play by consuming stamina that is specifically for the event part. In addition, in this search-type game, the user can obtain game media within the event part (for example, items that are exclusive to the event part, etc.).

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 below. In the solo part, the user can stock up to a specified number of parties of other users encountered for battles with floor bosses described below. These stocked parties of other users are hereinafter also referred to as "friend parties." In other words, by encountering other users in the solo part and stocking them as friend parties, it is possible to create advantageous effects from friends in the normal part (for example, working together with friends to take on quests).

In the solo part, an enemy character (hereafter also referred to as the "level boss") is set as the boss for each level, and when the user's party has progressed to a specified progress rate for each level (100% in this example), they will encounter this level boss, and a battle event will occur in which they will be able to defeat (hereafter also referred to as "subjugating") this level boss. In this battle event, the user can add a friend party that they have stocked to their own party to battle the level boss.

In a multi-part, a mission (such as a raid mission) is carried out in cooperation with other users. In a multi-part, the objective is to defeat a boss (hereinafter also referred to as a "raid boss") that is different from the level boss in cooperation with other users. At the start of a multi-part, a plurality of users who will execute the multi-part are matched, and the matched plurality of users are grouped. Next, a team is formed with the 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 the raid boss. The user relationship between these team members is registered as a partner relationship limited to the event part. In other words, during cooperative play with other users in the event part, 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.

The multi-part, in which team members battle the raid boss, ends a certain amount of time after it has started. When the multi-part ends, the group formed by matching (hereinafter 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 bonus (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, they will be matched into the same matching group in the next multi-part.

Returning to FIG. 1, the explanation will continue. The above-mentioned games are played using a gaming device 5, which is a home gaming console such as PlayStation (registered trademark), a portable gaming console such as Nintendo Switch (registered trademark), or an electronic device such as a personal computer, smartphone, or tablet. The following describes an example in which the gaming device 5 is a smartphone.

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

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

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.

After user authentication, the server device 2 and the game device 5 are able to communicate with each other. After logging in, the game device 5 receives data necessary for the game to proceed (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 speaker 62 based on the user's operations.

<Configuration of Game System 1>
The hardware configuration of the server device 2 and the game devices 5 will be described below with reference to Fig. 1. Note that each of the game devices 5 has the same configuration.

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

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

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

In the user DB221, for each identification number of a user playing the game, information about the player character operated by the user (status, etc.), 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."

"Consumable media" refers to currency, points, etc. that can be used within the virtual game space, and are consumed within the game to progress through the game. Consumable media are given to users as rewards for completing quests, or through charges in the real world.

The lottery list 222 is used when the lottery execution means 233 (described below) performs a lottery process generally known as 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 the selection rate in the lottery. Furthermore, when the game media is a player character, the parameters include, for example, fighting power, HP, attack power, defense power, intelligence, and speed.

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

The control unit 23 is composed of a microcomputer including a CPU and semiconductor memory, and controls the operation of the device 2.

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

-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 regarding the game media obtained by the gacha, etc.

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

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

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

-First reception method-
The first reception means 2341 enables a request for registration of the second user to the friend list (third list) of the first user as a registration-related process. When the first reception means 2341 becomes capable of receiving such a request, the first reception means 2341 receives a request for registration of the second user to the friend list of the first user from the first user. In addition, the first reception means 2341 enables a request for registration of the first user to the friend list (fourth list) of the second user as a registration-related process. When the first reception means 2341 becomes capable of receiving such a request, the first reception means 2341 receives a request for registration of the first user to the friend list of the second user from the second user. When the first reception means 2341 receives such a registration request, the first reception means 2341 inquires of the first user or the second user to whom the registration is to be made whether or not to accept such a registration request.

"Registration-related processing" refers to processing related to registering a second user or a first user to a friend list of a first user or a second user. Registration-related processing includes, for example, (a) processing to enable acceptance of a friend registration request, (b) processing to increase benefits granted based on user relationships, and (c) processing to update the display mode of the UI to request friend registration.

According to the above configuration, the first reception means 2341 can accept a request to register a friend on the condition that the second user is following the first user, or the second user is following the first user. Therefore, according to the above configuration, the first reception 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 reception means 2341 can build a user relationship in stages, from follow to friend.

The first reception means 2341, for example, receives a request from a first user to deregister a second user from the first user's friend list. The first reception means 2341 also receives a request from a second user to deregister the first user from the second user's friend list.

-Second reception method-
In the normal part, the second accepting means 2342 is capable of accepting 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 accepting means 2342 is thus capable of accepting, it accepts a request for registration in the partner list of the first user from the second user.

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, if the user relationship is mutually following or friends, the second reception means 2342 can make it possible to request the registration of a partner at a higher relationship level. Therefore, according to the above configuration, the second reception means 2342 can build a user relationship from mutual following to partners by skipping one level, or in stages from friends.

The second reception means 2342 may be capable of receiving a request to register the second user to the partner list (fifth list) of the first user, for example, on the condition that a limited event starts.

According to the above configuration, the second reception means 2342 can skip a step and build a user relationship to a partner only during the period when the limited event is held. According to the above configuration, the second reception means 2342 can 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, for example, thereby increasing interest.

The second reception means 2342, for example, receives a request from a first user to deregister a second user from the first user's partner list. The second reception means 2342 also receives a request from a second user to deregister a first user from the second user's partner list.

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

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. The registration means 235 also updates the user relationship between the solo part (first game part) and the multi-part (second game part).

-First registration means-
The first registration unit 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 unit 234 receives a request from the first user to register the second user in the follow list of the first user, the first registration unit 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 unit 2351 registers the relationship in which the first user follows the second user.

-Second registration means-
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.

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

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

According to the above configuration, the third registration means 2353 can encourage the user to register friends by executing processing associated with the registration, such as increasing the benefits granted to the user in response to the friend registration.

For example, in response to the first reception means 2341 receiving a request to deregister the second user from the partner list of the first user, the third registration means 2353 deregisters the second user from the partner list of the first user and deregisters the first user from the partner list of the second user. Conversely, for example, in response to the first reception means 2341 receiving a request to deregister the first user from the partner list of the second user, the third registration means 2353 deregisters the first user from the partner list of the second user and deregisters the second user from the partner list of the first user.

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

According to the above configuration, the fifth registration means 2354 can establish a partner relationship depending on the consent of the other user. Therefore, according to the above configuration, the fifth registration means 2354 can establish a partner relationship after obtaining the consent of the other user, in a case where the effect of the relationship is greater than that of a follow.

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 a multi-part event, instead of the second user's consent.

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

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 a friend relationship and create a sense of exclusivity in the partner relationship.

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

According to the above configuration, the execution control means 236 can execute the process related to friend registration on the condition that the follow registration has been made. Therefore, according to the above configuration, the execution control means 236 can encourage the building of a gradual user relationship from the follow to the friend status.

-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. The "users whose progress in the solo part is within a predetermined range" are, for example, users who are in the same hierarchical level in the solo part and whose progress rate is within a predetermined range.

When the next multi-part (third game part) is started following the multi-part (second game part), the matching means 237 matches multiple users to execute the next event part based on the progress of the solo part (first game part) and the user relationships 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 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 set a lottery frame for each of (A) to (C), such as X people in (A) and Y people in (B) or (C), and perform the lottery.

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 based on the progress of the game parts, including the solo parts. 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), and can also encourage encounters with other users. Therefore, according to the above configuration, the matching means 237 can improve the building of relationships with other matched users.

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 to the same group in the multipart.

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

According to the above configuration, the granting means 238 grants a reward 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 user relationships such as follow relationships.

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

According to the above configuration, the granting means 238 determines the value of the reward or the amount of the reward depending on 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.

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

-First game execution means-
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 (first list).

"First game control" refers to control over a game played by a first user, and is not, for example, conditional on the first user and 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, "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 (player character, items, etc.) of the second user (for example, so-called character rental, etc.).

The first game execution 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 benefit granted by the granting means 238 described below.

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

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

The "second game control" is a control for the game played by the 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 so as to be able to communicate with each other. "The first user and the second user are connected so as 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 so on, and is indirectly connected via the server device 2. 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's game progress is synchronized with each other, or may be asynchronous.

According to the above configuration, the second game execution 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 has been registered. Therefore, according to the above configuration, the second game execution means 2392 can differentiate between relationships that can be registered without the other party's consent (follow relationship) and relationships that require 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.

According to the above configuration, the second game execution 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 execution 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 that does not require the first user and the second user to be connected via a network, with the condition that the follow is registered.

<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 Figures 5 and 6. Figure 5 is a diagram showing an example of the flow of the event part. Figure 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.

(1) As shown in FIG. 5, when the specified start time (11:00) arrives 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.

(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, it starts the multi-part.

In the multipart mode, 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 inflicted on the raid boss by each team member. When the total of the accumulated damage reduces the raid boss's HP to 0, the execution control means 236 determines that the team has succeeded in defeating the raid boss.
- Even if there is no user relationship such as a follow relationship with a team member, it is possible to accept a request for a friend relationship or partner relationship.

(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 awarding means 238 calculates and awards 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 inflicted on the raid boss. The awarding means 238 awards rewards to each team member according to the ranking.
The awarding means 238 distributes rewards to team members according to their contribution to defeating the raid boss.
The awarding means 238 increases the reward awarded according to the number of people each team member follows/follows.

When a raid boss is defeated, the display control means 564 displays a notice screen or update screen (described below) encouraging team members to follow up.

(4) When the specified start time on the X+1th day during the limited event period arrives, similar to the previous day, the matching means 237 matches and groups multiple users for performing multi-parts based on the progress of the solo parts. 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.

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

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 they accept the request, i.e., whether they will join team A. The second reception means 2342 also accepts this invitation request as a request to register in user A's partner list. When the second reception means 2342 receives "accept" from user B in response to this 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 user A's partner list and registers user A in user B's partner list in response to user B's acceptance.

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 join 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, matching means 237 matches team members users A, B, and D to be on the same team.

<Configuration of Game Device 5>
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.

The network interface 51 is communicatively connected to the communication network 6 to transmit and receive various data between the game device 5 and the server device 2.

The graphics processing unit 52 renders game images including characters and various objects related to the virtual game space in a moving image format according to the game image information output from the control unit 56. The graphics processing unit 52 is connected to a display 61, which may be, 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.

The audio processing unit 53 is connected to the speaker 62, and plays and synthesizes game audio according to the instructions of the control unit 56, and outputs it from the speaker 62.

The operation unit 54 is connected to the touchpad 63, and transmits and receives data related to operation inputs to and from the touchpad 63. The user inputs operation signals to the game device 5 by touching the touchpad 63.

The storage unit 55 is composed of a HDD, SSD, RAM, ROM, etc. The storage unit 55 stores game data downloaded from the server device 2, various programs including parts of the game program, account information for the player's device 5, etc.

The storage unit 55 may store, for example, user information. The user information is at least a portion of the information in the user DB 221 stored in the storage unit 22 of the server device 2. The user DB 221 manages a master of the user information, and the storage unit 55 of the game device 5 stores at least a portion of the information in the master that is distributed from the server device 2.

The control unit 56 is composed of a microcomputer including a CPU and semiconductor memory, and controls the operation of the device 5.

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.

--Communication means 561--
The communication unit 561 is a function for communicating with the server device 2 via the network interface 51 .

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 touchpad 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, etc. to the server device 2. The communication means 561 also receives new game data sent from the server device 2 in response to download request information, information regarding the game media selected by lottery processing, etc. from the server device 2.

-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 touch pad 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.

The game execution means 562 then places a character on the game image in accordance with the 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 the user's operation via the touchpad 63 (hereinafter simply referred to as "user operation"). The game execution means 562 also causes the player character to use the game medium selected by the user in accordance with the user operation.

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.

-Voice control means-
The audio control means 563 controls audio output from the speaker 62 in response to operations by the user of the player's device 5 during game execution.

-Display control means-
When the game is executed, 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.

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 friends. 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 to enable" means, 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 unavailable (grayed out) to available.

According to the above configuration, the display control means 564 can change the display mode of the registration screen for registering friends, on the condition that a follow has been registered. Therefore, according to the above configuration, the display control means 564 can encourage the user relationship to be built in stages.

The display control means 564 may further change the display mode of the registration screen in 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 in a case where either the first user or the second user is registered in the second user's follow list or follows the first user (first list). For example, when both users are registered in each other's follow lists, i.e., in the case of mutual following, the display control means 564 may display an icon indicating mutual following (for example, the mutual follow icon described below) on the registration screen.

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 they are following each other or following 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 they are following each other, i.e., when they are in a mutual state.

The display control means 564 displays a screen (hereinafter also referred to as a "notification screen") notifying the granting of a benefit due to the user relationship between the first user and the second user being 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 benefit is granted.

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

<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 will be described with reference to Fig. 8, and an example of a screen after user B follows back user A will be described with reference to Fig. 9.

As shown in FIG. 7, the display control means 564 causes a profile screen 610 to be displayed 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 regarding 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.

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.

The relationship request button 612 is a button for requesting the registration of a user relationship (in this example, following) 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 accepts a request for registration of user B to the follow list of user A. The second registration means 2352 registers user B to the follow list of user A. In addition, when user B is registered to the follow list of user A, the reception means 234 is capable of accepting a request for registration of user B to the friend list of user A and a request for registration of user A to the friend list of user B as registration-related processing.

As shown in Figures 8 and 9, the display control means 564 causes the 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 in Figure 8 and a follower display area 620b in Figure 9. In the following/followers screen 620, the display content can be switched by specifying the tabs of the following display area 620a and the follower display area 620b.

As shown in FIG. 8, the follow display area 620a is an area that displays users that user A follows. The follow display area 620a includes a follow summary display area 620a1 and a follow list display area 620a2.

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 to request registration of a user relationship with a higher relationship level. For example, for the item of user B, the follow list display area 620a2 displays a friend request button 620a21 to request registration of a friend with a relationship level of follow or higher as the relationship request button.

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 accepts a request to register user B in the friend list of user A. When the first reception means 2341 accepts this friend registration request, it causes the display control means 564 to display the 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.

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

The follower summary display area 620b1 displays the number of followers of user A.

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

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

When the OK button 631 is pressed by user B, the display control means 564 transmits user B's response of consent to the above 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 user A's friend list and registers user A in user B's friend list in response to user B's consent.

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 consent inquiry 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.

When the profile display button 633 is pressed, the display control means 564 transitions to user A's profile screen (not shown).

As shown in FIG. 11, the display control means 564 causes the display 61 to display a solo part play screen 640. 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.

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

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

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.

As shown in FIG. 12, the display control means 564 displays a follow progress screen 650 on the display 61 during the event part. The follow progress screen 650 includes a follow progress list display area 651.

The follow progress list display area 651 displays the progress of each user being followed (hereinafter also referred to as "each following user") in the event part. In the follow progress list display area 651, each following user is displayed divided according to 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 exclusive to the event part.

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 partner registration request to the server device 2 via the network interface 51. When the server device 2 receives this partner registration request, the reception means 234 receives a request to register user I in the partner list of user A. When the reception means 234 receives this partner registration request, it causes the display control means 564 to display a partner request screen (not shown) on the display 61 of user I to inquire of user I whether or not he/she agrees to the partner registration request, similar to the case of friends. When user I responds to this request on the partner request screen by agreeing to the request, user I is registered in user A's partner list and user A is registered in user I's partner list in response to user I's agreement.

As shown in FIG. 13, the display control means 564 causes the display 61 to display a group member screen 660. 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.

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

The member list display area 662 displays, for each user of the group members displayed in the list, the user name, the relationship level with that user, and a relationship request button to request registration of a user relationship with a higher relationship level.

For example, in the member list display area 662, for User C's entry, a follow request button 6621 is displayed as a relationship request button for requesting to register a follow because there is currently no user relationship.

For example, in the member list display area 662 for User D, a one-sided follow icon 6622 is displayed to indicate the current one-sided follow relationship, and a friend request button 6623 is displayed to request the registration of a friend, which is a higher relationship level, and a partner request button 6624 is displayed to request the registration of a partner.

For example, in the member list display area 662 for User F, a mutual follow icon 6625 is displayed indicating the current mutual follow relationship, and a friend request button 6626 is displayed to request the registration of a friend, which is a higher relationship level, and a partner request button 6627 is displayed to request the registration of a partner.

For example, in the member list display area 662 for user G, a friend icon 6628 is displayed that indicates the current friend relationship, and a partner request button 6629 is displayed to request the registration of a partner, which is a higher relationship level.

As shown in FIG. 14, the display control means 564 causes a notice screen 670 to be displayed 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 a follow relationship in the event part. The notice screen 670 includes a notice display area 671 and an update promotion display area 672.

The preview display area 671 displays a message notifying the user that a bonus will be awarded and an image showing the bonus to be awarded.

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

As shown in FIG. 15, the display control means 564 causes the display 61 to display an update screen 680. The update screen 680 includes a group member list display area 681.

The group member list display area 681 displays, for each group member item displayed in the list, the relationship level between user A and that user, and a relationship request button for requesting registration of a higher relationship level. For example, the group member list display area 681 may 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, not shown, the group member list display area 681 may 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, not shown, the group member list display area 681 may display, for example, the contribution level, such as the amount of damage inflicted on a raid boss, for each group member item displayed in the list.

<Operational Flow of Game System 1>
16 to 19, examples of process flows and interactions executed by the game system 1 will be described.

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

Then, the first registration means 2351 registers the second user in the follow list of the first user without the second user's consent (step ST2).

Then, the first game execution 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).

Then, the execution control means 236 executes a registration-related process for registering the second user to the friend list (third list) of the first user, on the 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 the reception of a request to register the second user to the friend list of the first user.

Next, the first reception means 2341 receives a request to register the second user to the friend list of the first user (step ST5).

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

Then, the third registration means 2353 registers the second user in the friend list of the first user with the second user's consent (step st7).

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

Next, the second game execution means 2392 permits the first user to control the second game, on the condition that the second user is registered in the first user's friend list (step st9).

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

Next, the game execution means 239 starts the multi-part (step ST12).

Then, the registration means 235 updates the user relationship in the started multipart (step ST13).

Next, the game execution means 239 ends the multi-part (step ST14).

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

Figure 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 Figure 18, first, the game execution means 562 of user A's game device 5a accepts a request from user A to register user B in user A's follow list (step st21).

Next, when the game execution means 562 receives a request from user A to register user B to user A's follow list, it transmits this registration request to the server device 2 (step st22).

Next, the reception means 234 of the server device 2 receives the request to register user B to the follow list of user A sent above (step st23).

Then, in response to the received request to register user B in user A's follow list, the first registration means 2351 registers user B in user A's follow list without user B's consent (step st24).

Next, the first game execution 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).

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

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

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

Then, the game execution means 562 of the game device 5a accepts a request from user A to register user B on user A's friend list (step st31).

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

Next, the first reception means 2341 receives a request to register user B to user A's friend list (step ST33).

Next, the first reception means 2341 inquires of the game device 5b about consent to the request to register user B on user A's friend list (step st34).

Next, the game execution means 562 of the game device 5b accepts a response to the above-mentioned consent inquiry from user B (step ST35).

Next, when the game execution means 562 of the game device 5a receives a response from user B to the above-mentioned inquiry about consent, it transmits this response to the server device 2 (step st36).

Next, if the response from user B is "accepted," the server device 2 executes processing within the area indicated by the composite 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). In addition to this registration, the third registration means 2353 also registers user A in the friend list of user B (step st38).

Then, the second game execution means permits user A and user B to control the second game, on the condition that user B and user A are registered in user A's and user B's friend lists, respectively (step st39).

Figure 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 Figure 19, first, the execution control means 236 of the server device 2 starts the event part (step st41).

When the execution control means 236 starts an event part, the processing of the multipart within the area indicated by the combined fragment Loop1 is repeatedly executed every day until the end condition (until the period during which the event part is held ends) is met. Specifically, first, the matching means 237 detects the specified start time of the multipart and starts the multipart (step st42).

Next, the matching means 237 matches and groups multiple users to perform 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 user A and user B are grouped into group a1.

Then, the second reception means 2342, in response to the start of the limited event, enables the reception of requests from other group members to the group member's partner list) (step st44).

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). Note that in this example, an example will be described in which group members of group a1 other than user A and user B encounter the raid boss.

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, indicating that a multi-part has begun (step ST46).

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

Next, when the game execution means 562 of the game device 5a receives a request to create team a11, it transmits this creation request to the server device 2 (step ST48).

Next, the fifth registration means 2354 of the server device 2 accepts the request to create the team A11 and newly registers the team A11 (step ST49).

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

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

Next, the second reception means 2342 of the server device 2 receives a request from user B to invite team a11 as a request to register user B on user A's partner list (step st52).

Next, the second reception means 2342 inquires of the game device 5b whether to accept the invitation request from user B (step st53).

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

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

Next, if the response from user B is "accepted", i.e., if user B joins team a11, the server device 2 executes processing within the area indicated by the composite fragment opt2 (Option2). Specifically, the fifth registration means registers user B in the partner list of user A in response to user B's acceptance (step st56). In addition to this registration, the fifth registration means registers the partner list of user A in the partner list of user B (step st57).

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

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

In summary, the control unit 23 (computer) of the server device 2 functions as a first registration means 2351 for registering the second user in the first list of the first user without the consent of the second user, a second registration means 2352 for registering the first user in the second list of the second user without the consent of the first user, a first game execution means 2391 for permitting the first user to control the first game on condition that the second user is registered in the first list, regardless of whether the first user is registered in the second list, an execution control means 236 for executing a registration-related process related to the registration of the second user in the third list of the first user on condition that the second user is registered in the first list or the first user is registered in the second list, a third registration means 2353 for registering the second user in the third list in response to the consent of the second user and registering the first user in the fourth list of the second user, and a second game execution means 2392 for permitting the first user to control the second game on condition that the second user is registered in the third list.

＜Effects＞
According to this embodiment, it is possible to permit a game control (second game control) different from the first game control permitted by the registration of a follow, on the condition that a friend is registered. Therefore, according to this embodiment, by changing the permitted game control, it is possible to differentiate between a relationship in which registration can be made without the consent of the other party (a follow relationship) and a relationship in which consent is required (a friend relationship). Therefore, according to this embodiment, by making such a distinction, a gradual user relationship (a friend relationship is more effective than a follow relationship) can be built, and the interest in building relationships with other users can be improved.

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

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

The first reception means 2341 may be capable of receiving a request to register a second user to a friend list (third list) of a first user, on condition that a limited-time event is to start, for example.

The third registration means 2353 may 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 in response to the end of the limited event.

According to the above configuration, the third registration means 2353 can register the friend relationship 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).

[Second Modification]
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 based on information preset by the first user, 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 to perform an operation). 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.

The control unit 56 of the game device 5 may function as a request means (not shown), for example, by 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 request means requests the first reception means to register the second user in the friend list (third list) of the first user without requiring any operation by the first user.

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

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 pre-set user information of the second user, without requiring an operation by the second user to accept 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.

According to the above configuration, the request means can automatically accept the request for friend relationship registration 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 the acceptance, and can provide a means for building user relationships that is easy to use.

<Display Control Means>
Here, 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.

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

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

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

For example, when the next multi-part (third game part) is started 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.

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

The reception means 234 receives, for example, a request to update a user relationship from a first user.

The reception means 234 (second reception 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 relationship has been updated to a follow relationship (first relationship) or a friend relationship (second relationship). Furthermore, the reception means 234 (second reception means 2342) may, for example, relax the permission condition in the multi-part (second game part). For example, the reception 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.

According to the above configuration, the reception means 234 can differentiate between normal parts and event parts (multiple parts) when building partner relationships. Therefore, according to the above configuration, the reception means 234 can create a sense of exclusivity in the multiple parts when building partner relationships (for example, a sense of exclusivity due to being fellow members of the same group or being fellow members of the same team who have fought together), thereby increasing interest.

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 partner relationship (third relationship) that requires the consent of the second user.

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

The matching means 237 may, for example, enable matching between a first user and a 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).

According to the above configuration, if a 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.

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

The team member list may include, for example, team identification information for identifying each team, leader user identification information for identifying the leader user of each team (the 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 users B and C to join and each is accepted, the fifth registration means 2354 registers users B and C in the same team member list. The fifth registration means 2354 may update the user relationship between users B and C registered in the same team member list to a partner relationship. In other words, the matching means 237 may match users B and 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.

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

In the above embodiment, the game device 5 is a smartphone, but the game device 5 may be an amusement device provided at a game center, etc.

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.

In the above embodiment, the object is a player character, but this is not limiting. For example, the object can be a card or an item (weapon, armor, and other equipment) used in the virtual game space.

In the above embodiment, the server device 2 and the multiple game devices 5 are integrated to function as a game program, but the present invention is not limited to this. All of the means of the game program, i.e., the reception means, registration means, execution control means, matching means, granting means, game execution means, and display control means, may be provided in the server device 2 alone, the game device 5 alone, a communication terminal separate from the server device and the game device 5, or two devices that are combined among these (e.g., 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 by which device. For example, the control unit 56 of the game device 5 may execute various programs to function as the reception means, registration means, execution control means, matching means, granting means, and game execution means of the server device 2 exemplified in the above embodiment.

Even when these other embodiments are adopted, the effects of this embodiment are achieved. In addition, this embodiment can be combined with other embodiments, and other embodiments can be combined with each other as appropriate.

1 Game system 2 Server device 23 Control unit 235 Registration means 2351 First registration means 2352 Second registration means 2353 Third registration means 236 Execution control means 239 Game execution means 2391 First game execution means 2392 Second game execution means

Claims (13)

Computer,
a first registration means for registering a second user in a first list of a first user without the consent of the second user;
a second registration means for registering the first user in a second list of the second user without the consent of the first user;
an execution control means for executing a registration-related process for registering the second user in a third list of the first user, on condition that the second user is registered in the first list or the first user is registered in the second list ;
a third registration means for registering the second user in the third list and registering the first user in a fourth list of the second user in response to the consent of the second user;
functioning as a first reception means capable of receiving a request for registering the second user in the third list on condition that a limited-time event is started;
Game program. The computer,
and further functioning as a first reception unit that is capable of receiving a request for registration of the second user in the third list as the registration-related process.
The game program according to claim 1 . the third registration means executes, as the registration-related process, a process associated with the registration when the second user is registered in the third list;
The game program according to claim 1 . The computer,
and causing the display control unit to further function as a display control unit that changes a display mode of a screen for accepting a request for registering the second user in the third list as the registration-related process.
The game program according to claim 1 . The display control means further changes a display mode of the screen in a case where the first user and the second user are both registered in the second list and the first list, and in a case where either the first user or the second user is registered in the second list or the first list.
The game program according to claim 4 . Computer,
execution control means for executing a registration-related process for registering the second user in the third list of the first user;
a third registration means for registering the second user in the third list and registering the first user in a fourth list of the second user in response to the consent of the second user;
functioning as a first reception means for receiving a request for registering the second user in the third list on condition that a limited-time event is to start;
the third registration means, in response to an end of the limited event, cancels the registration of the second user from the third list and cancels the registration of the first user from the fourth list.
Game program. The computer,
and further functioning as a second accepting unit that is capable of accepting a request for registering the second user in the fifth list of the first user, on condition that the first user and the second user are mutually registered in the second list and the first list, or the second user is registered in the third list.
The game program according to claim 1 . The computer,
and further functioning as a fifth registration means for registering the second user in the fifth list and registering the first user in a sixth list of the second user in response to consent of the second user.
The game program according to claim 7 . the second reception means is operable to receive a request for registering the second user to the fifth list on condition that a limited-time event is started;
The game program according to claim 8 . The computer,
a first receiving means for receiving a request for registering the second user in the third list as the registration-related process;
when the second user is registered in the first list and the first user is registered in the second list according to preset user information of the first user, the device further functions as a requesting device that requests the first accepting device to register the second user in the third list without requiring an operation by the first user.
The game program according to claim 1 . the third registration means, in response to a request for registration of the second user in the third list based on preset user information of the second user, registers the second user in the third list without requiring an operation by the second user to approve the registration;
The game program according to claim 1 . A storage unit that stores the game program according to any one of claims 1 to 11;
A control unit that executes the game program;
A server device comprising: A storage unit that stores the game program according to any one of claims 1 to 11;
A control unit that executes the game program;
A game system comprising:

Images