Game program, game system, and management method

Abstract

Makes it easier for users in the same party to participate in the same quest together. [Solution] A game progression unit 100 progresses a game that includes quests, and a registration unit 101 registers users to a party. A management unit 102 manages users' participation in quests. The management unit manages user participation in quests so that when a first registered user U1, who is a user registered in a party, participates in a quest, a second registered user U2, who is a user registered in the party together with the first registered user U1, can participate in the quest in which the first registered user U1 is participating with priority over an unregistered user U5, who is a user not registered in the party.

Description

[Technical Field]

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

[0002] Patent Document 1 discloses that a plurality of players form a group. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2008-113782 Summary of the Invention [Problem to be solved by the invention]

[0004] When multiple users are registered in the same party to form a party, it is desirable to make it easier for users registered in the same party to participate in the same quest together, from the perspective of improving the sense of solidarity and friendship among the users in the party.

[0005] An object of the present invention is to make it easier for users registered in the same party to participate in the same quest together. [Means for solving the problem]

[0006] The first aspect is A computer system having one or more computers working together, a game progression section that progresses the game including quests; a registration unit for registering a user to a party; functioning as a management unit that manages the user's participation in the quest; The management unit manages the participation of the users in the quest so that, when a first registered user who is a user registered in the party participates in the quest, a second registered user who is a user who is registered in the party together with the first registered user can participate in the participation quest in which the first registered user will participate preferentially over an unregistered user who is a user not registered in the party. It is a game program.

[0007] In a first aspect, A participation condition for participating in the participation quest may be set in the participation quest, The management unit If the unregistered user satisfies the participation condition set for the participation quest, the unregistered user may be permitted to participate in the participation quest; The second registered user may be permitted to participate in the participation quest regardless of whether or not the second registered user satisfies the participation conditions set for the participation quest.

[0008] In a first aspect, The participation conditions may include at least one of a condition that a password set for the participation quest is entered, and a condition that participation in the participation quest is approved.

[0009] In a first aspect, The registration of the first registered user in the party may continue even after the participation quest ends.

[0010] In a first aspect, When the first registered user participates in the participation quest, the management unit sends a participation notification to the second registered user to notify them that the first registered user will be participating in the participation quest, but the participation notification does not have to be sent to the unregistered user.

[0011] In a first aspect, When a plurality of the first registered users participate in a plurality of the participation quests respectively, the management unit may send a plurality of the participation notifications corresponding to the plurality of participation quests to the second registered user.

[0012] In a first aspect, The participation notice includes an application instruction for applying to participate in the participation quest, The management unit may permit the second registered user to participate in the participation quest when the application instruction included in the participation notification sent to the second registered user is returned.

[0013] The second aspect is a game progression section that progresses the game including quests; a registration unit for registering a user to a party; a management unit that manages the user's participation in the quest; The management unit manages the participation of the users in the quest so that, when a first registered user who is a user registered in the party participates in the quest, a second registered user who is a user who is registered in the party together with the first registered user can participate in the participation quest in which the first registered user will participate preferentially over an unregistered user who is a user not registered in the party. It is a game system.

[0014] The third aspect is A management method for managing a user's participation in a quest included in a game, comprising: a registration step for registering a user with a party; and a management step of managing the participation of users in the quest so that, when a first registered user who is a user registered in the party participates in the quest, a second registered user who is a user who is registered in the party together with the first registered user can participate in the participation quest in which the first registered user will participate preferentially over an unregistered user who is a user not registered in the party. It is a management method. [Effects of the Invention]

[0015] According to the present invention, it is possible to make it easier for users registered in the same party to participate in the same quest together. [Brief explanation of the drawings]

[0016] [Figure 1] FIG. 1 is a block diagram illustrating a configuration of a game system according to an embodiment. [Figure 2] FIG. 1 is a block diagram illustrating a configuration of a game device. [Figure 3] FIG. 10 is a diagram illustrating an example of a link party menu image. [Figure 4] FIG. 10 is a diagram illustrating an example of a link party list image. [Figure 5] FIG. 10 is a diagram illustrating an example of a candidate member list image. [Figure 6] FIG. 1 is a schematic diagram showing a specific example 1 of a processing flow in a game system. [Figure 7] 10A and 10B are diagrams illustrating examples of game images displayed in Example 1. FIG. [Figure 8] FIG. 10 is a schematic diagram showing a specific example 2 of a processing flow in the game system. [Figure 9] 10A and 10B are diagrams illustrating examples of game images displayed in specific example 2. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0017] Hereinafter, the embodiments will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are designated by the same reference numerals and their description will not be repeated.

[0018] (Terminology explanation) First, the terms used in the following description will be explained. Terms such as game, game content, and object will be used below.

[0019] A "game" refers to a game (video game) that takes place in a virtual game space. The virtual space may be a three-dimensional space or a two-dimensional space. The virtual space is displayed as an image on a display device.

[0020] An example of such a game is an action game in which a character (player character) controlled by a user defeats enemy characters. In an action game, the player character recovers his / her stamina by equipping equipment items such as weapons and armor, and by using tool items such as recovery potions.

[0021] The above-mentioned games include quests. A quest is an in-game event with a set goal to be achieved. Quests include quests that are prepared in advance in the game and quests that are created in response to user operations. Quests also include quests for which participation conditions are set. Examples of participation conditions include a condition that a password set for the quest is entered, or a condition that participation in the quest is approved.

[0022] "Game media" refers to the virtual media used in the above-mentioned games. Examples of game media include items used in the game space (weapons, armor, tools, etc.), characters, vehicles ridden by characters (horses, cars, etc.), character skills, etc. Users can obtain the above-mentioned game media by directly purchasing them for a fee, completing quests, or by entering a lottery known as "gacha."

[0023] An "object" is a virtual medium placed in the game space. Examples of objects include a player character, an enemy character (such as a monster), a non-player character, and a vehicle.

[0024] In the above-described game, game contents obtained by a player character through user operation are granted to the player character. Specifically, information about the game contents granted to a player character in a game is associated with the player character and registered in a database. A user can create at least one player character, and information about at least one player character is associated with a user ID assigned to the user. Therefore, the database may also include the user ID of the user associated with the player character. In this embodiment, a game in which a player character is displayed in a third-person perspective in a game space is exemplified, but the present invention is also applicable to games in which a player character is displayed in a first-person perspective in which the player character is not displayed in a game space. In the first-person perspective, game contents can be granted to a user, and "granted (owned) by a user" is synonymous with "associated with a user."

[0025] For the sake of convenience, the following description will be given taking as an example a case where the game is an "action game in which the player character defeats monsters that are enemy characters."

[0026] (Game System) 1 illustrates the configuration of a game system 1 according to an embodiment. The game system 1 includes a server device 10 and a plurality of game devices 15. In the game system 1, the server device 10 and the game devices 15 are connected to each other so as to be able to communicate with each other via a communication network 5. Examples of the communication network 5 include the Internet and a LAN.

[0027] [Server device] The server device 10 manages the game system. For example, the server device 10 is managed by an operator that provides the game. In this example, the server device 10 includes a network interface 11, a storage unit 12, and a control unit 13. The network interface 11 and the storage unit 12 are electrically connected to the control unit 13 via a bus 14.

[0028] The network interface 11 is communicably connected to other information processing devices (for example, the game device 15) via a communication network 5 in order to transmit and receive various information and data to and from the other information processing devices.

[0029] The storage unit 12 stores various types of information and data. The storage unit 12 is configured with an HDD, SSD, RAM, ROM, etc. In this example, the storage unit 12 stores a game program and game data for executing the game, account information (ID and password) of users playing the game, etc. The game data includes image data for generating various images, audio data for generating various sounds, control data (e.g., setting values ​​such as thresholds) used to control processing by the server device 10, information and data for managing the progress of the game and users (e.g., management information such as lists and tables, and data indicating the results of the progress of the game), etc.

[0030] The control unit 13 controls the operation of the server device 10. The control unit 13 transmits and receives various types of information and data, and processes the various types of information and data. The control unit 13 has a CPU (microcomputer) and memory. The memory stores programs for operating the CPU, etc.

[0031] [Game device] 2 illustrates the configuration of a game device 15. The game device 15 executes a game in response to operations by a user. The game progresses on the game device 15 based on the installed game program and game data. Game devices 15 can communicate data with each other using a communication network 5 or a short-range wireless communication device (not shown).

[0032] Examples of the game device 15 include a game console, smartphone, tablet, personal computer, etc., in which a display, speaker, and controller are externally connected or built-in. In the following, a case where the game device 15 is a "game console in which a display, speaker, and controller are externally connected or built-in" will be taken as an example. The game device 15 includes a game machine 20, a display 31, a speaker 32, and a controller 33.

[0033] The game machine 20 includes a network interface 21, a graphics processing unit 22, an audio processing unit 23, an operation processing unit 24, a storage unit 25, and a control unit 26. The network interface 21, the graphics processing unit 22, the audio processing unit 23, the operation processing unit 24, and the storage unit 25 are electrically connected to the control unit 26 via a bus 27.

[0034] The network interface 21 is communicably connected to other information processing devices via a communication network 5 in order to transmit and receive various information and data to and from other information processing devices (for example, the server device 10 and other game devices 15).

[0035] A display 31 is connected to the graphics processing unit 22. The graphics processing unit 22 displays various images (moving images drawn in a moving image format) on the display 31 in accordance with various image information output from the control unit 26. The display 31 is a display used by a user, and is an example of a display device that displays images to the user.

[0036] A speaker 32 is connected to the audio processing unit 23. The audio processing unit 23 outputs various sounds to the speaker 32 in accordance with various types of audio information output from the control unit 26. The speaker 32 is a speaker used by the user, and is an example of an acoustic device that outputs sounds to the user.

[0037] A controller 33 is connected to the operation processing unit 24. The operation processing unit 24 transmits and receives data related to operation inputs to the controller 33. The operation processing unit 24 then transmits operation information indicating operations input to the controller 33 to the control unit 26. The controller 33 is a controller used by a user and is an example of an operation unit operated by a user.

[0038] For example, a user operates the controller 33 to input an operation signal to the game device 15. That is, when the user operates the controller 33, the controller 33 transmits an operation signal corresponding to the user's operation to the operation processing unit 24. The operation processing unit 24 generates operation information based on the operation signal and transmits the operation information to the control unit 26.

[0039] The storage unit 25 stores various information and data. The storage unit 25 is configured with an HDD, an SSD, a RAM, a ROM, and the like. In this example, the storage unit 25 stores a game program and game data for executing a game, account information (ID and password) of a user who uses the game device 15, a database for managing game media assigned to the user, and the like. The game data includes image data for generating various images to be displayed on the display 31, audio data for generating various sounds to be output from the speaker 32, control data (e.g., setting values ​​such as thresholds) used to control processing by the game device 15, information and data for managing the progress of the game and users (e.g., management information such as lists and tables, and data indicating the results of the progress of the game), and the like.

[0040] The control unit 26 controls the operation of the game device 15. The control unit 26 transmits and receives various information and data, and processes various information and data. The control unit 26 has a CPU (microcomputer) and memory. The memory stores programs for operating the CPU. In this example, the control unit 26 controls the graphics processing unit 22 and the audio processing unit 23, thereby controlling the display 31 and the speaker 32.

[0041] [Functional configuration of the control unit in the server device] As shown in Figure 1, the control unit 13 of the server device 10 has a game progression unit 100, a registration unit 101, and a management unit 102. Specifically, the control unit 13 functions as the game progression unit 100, registration unit 101, and management unit 102 by having its CPU execute various programs. These programs are an example of a game program.

[0042] <Game Progression Department> The game progression unit 100 controls the game, including quests, and progresses through the game. In this example, the game progression unit 100 receives various types of information such as operation information, generates game data for running the game, and transmits the game data.

[0043] <Registration Department> The registration unit 101 performs various registrations. In this example, the registration unit 101 registers users in lists such as a link party list, which will be described later. The link party list is an example of a party list in which users who organize parties are registered.

[0044] Note that, while the following examples will be given in which "user names" are displayed as members of a linked party, the "player character names" associated with the data the user is currently playing may also be displayed as members of the linked party. In this case, too, this is synonymous with a "user" being registered in the linked party. For example, if multiple player characters are created and the user selects the player character to play before playing, the player character displayed as a member of the linked party will differ depending on which player character the user selects. In this case, even if the player character controlled by the user is not always the same, because the user controlling the character is the same person, it can be said that a "user" is registered in the linked party list.

[0045] <Management Department> The management unit 102 performs various management operations. In this example, the management unit 102 manages users' participation in quests, etc.

[0046] [Link Party Description] In the following description, a "link party" refers to a party (group) formed by users registered in the link party list. This type of party formation is provided to make it easier for users who form the same party to participate in the same quest together. Note that a link party allows users who form the same party to participate in different quests separately. In this way, a link party can provide a way for users to connect, whether they want to participate in different quests separately or the same quest together.

[0047] A leader (host) is also set for each link party. The user who is the leader of the link party has the authority to invite users to the link party, register users in the link party, and remove users from the link party.

[0048] In addition, users who are members of the link party have the authority to view the status (behavior logs) of other users who are members of the link party, and to leave the link party, etc. When a user who is the leader of the link party leaves the link party, one of the remaining members of the link party (for example, the user who has been with the link party for the longest period of time) is set as the new leader.

[0049] Additionally, you can join or leave a Link Party even while playing a quest. Note that even if you leave a Link Party, you can continue playing the quest.

[0050] Furthermore, when a user who is a member of a link party starts a quest, a notification is sent to other users who are members of the link party inviting them to participate in the quest. Note that the quest may be a quest prepared in advance in the game, or may be a quest created in response to user operation. The notification inviting participation in the quest is an example of a participation notification indicating that a user who is a member of the link party will participate in the quest.

[0051] Additionally, a "quest invitation" may be issued by a user who is a member of the link party. The invitation to participate in a quest can be issued by either the leader (host) or a member (guest) of the link party. The invitation to participate in a quest is an example of a participation notification indicating that a user who is a member of the link party will participate in a quest.

[0052] Furthermore, if a quest in which a user who is a member of a link party participates is a "quest with participation conditions set for participation," other users who are members of the link party can participate in the quest regardless of whether they meet the participation conditions. Examples of participation conditions include entering a password set for the quest, or being approved to participate in the quest, etc.

[0053] Furthermore, if a quest in which a user who is a member of a link party participates is a "quest with a limit on the number of participants set," the user may be permitted to participate in the quest even if the number of participants of the user who is a member of the link party (the number of people participating in the quest) exceeds the limit on the number of participants in the quest. In other words, the number of participants of the user may take priority over the limit on the number of participants in the quest. The above "limit on the number of participants in a quest" is an example of a participation condition set for a quest.

[0054] Note that the "maximum number of participants" is a number that is smaller than the maximum number of participants preset for the quest. If the number of users who are members of a link party (the number of people participating in the quest) exceeds the maximum number of participants for the quest, the user's participation in the quest may be denied. In other words, the number of users who can participate in the quest may be limited to less than the maximum number of participants for the quest. In this case, when the number of users participating in the quest reaches the maximum number of participants set for the quest, acceptance of user participation in the quest may be terminated.

[0055] Furthermore, if a quest in which a user who is a member of a link party participates is a "quest that only allows the accompaniment of non-player characters," other users who are members of the link party may be permitted to participate in the quest. The above-mentioned "restrictions on the types of characters permitted to participate in the quest" is an example of a participation condition set for a quest.

[0056] Furthermore, if a quest participated in by a user who is a member of a link party is a "quest that requires a specific type of platform (type of game console 20) on which the game is played," even if another user who is a member of the link party is "another user who plays the game on a platform type different from the type required in the quest," that other user may be permitted to participate in the above quest.

[0057] Specifically, the server device 10 is capable of performing a process (cross-play) in which a common game is simultaneously played among a plurality of game devices 15 of different platform types (types of game consoles 20). Quests also include quests for which cross-play is prohibited. A quest for which cross-play is prohibited is an example of the above-mentioned "quest that requires a specific type of platform on which the game is played." Furthermore, the above-mentioned "restriction on the type of platform permitted to participate in the quest" is an example of a participation condition set for a quest.

[0058] Furthermore, users who can organize a link party may be users who control player characters placed in a waiting area (lobby) set up within the game space, or users who control player characters placed in a location other than the above-mentioned waiting area (for example, a field).

[0059] Furthermore, in the waiting place (lobby) above, a display element (e.g., a predetermined icon) may be associated with a player character operated by a user who is a member of the link party, indicating that the user is a member of the link party. Furthermore, in the waiting place (lobby) above, the display priority of a player character operated by a user who is a member of the link party may be higher than the display priority of a player character operated by a user who is not a member of the link party.

[0060] In addition, a player character operated by a user who is a member of a link party may be associated with a display element (e.g., a specified icon) that indicates that the user is a member of the link party, even when not playing a quest.

[0061] The formation of a link party continues even after the quest ends. The user who formed the link party maintains the formation without disbanding the link party even after the quest ends. The link party may also be disbanded after logging out.

[0062] Additionally, it is prohibited for a single user to belong to different link parties at the same time.

[0063] The above-described organization of link parties is realized by processing (link party management processing) by management unit 102. The link party management processing will be explained in detail later.

[0064] [Explanation of environmental links] In the following description, the term "environment link" refers to a state in which the game play environment (game play conditions) for each of multiple users is set to a common environment. Users who participate in the environment link play the game in the common environment of the environment link. On the other hand, users who do not participate in the environment link play the game in individual environments according to the progress of the game. Examples of game play environments include the type of field, the type and level of enemy characters, etc.

[0065] In this example, participation in the environmental link is performed within the link party. A user who is a member of the link party can invite other users who are members of the link party to participate in the environmental link.

[0066] [Processing performed in the game system] In this example, the game system 1 performs login processing, game progress processing, image display processing, solicitation processing, solicitation confirmation processing, link party registration processing, link party withdrawal processing, leader delegation processing, link party exclusion processing, quest solicitation approval processing, environmental link solicitation approval processing, environmental link withdrawal processing, link party management processing, etc.

[0067] [Login process] The login process is performed to start a game. In the login process, the control unit 26 of the game device 15 responds to a user operation input to the controller 33 (an operation to start the login process) and transmits the user's account information to the server device 10. The control unit 13 (game progression unit 100) of the server device 10 performs user authentication based on the account information transmitted from the game device 15 and pre-registered account information. When access by the game device 15 is permitted as a result of the user authentication, the server device 10 and the game device 15 communicate with each other, and the game begins.

[0068] The game progression unit 100 can manage (confirm) which game device 15 the user is operating and which player character the user is controlling, based on the results of user authentication during the login process (which user is using the game device 15 that has been granted access).

[0069] [Game Progression Processing] The game progress process is a process for progressing the game, and is performed after the game device 15 is permitted to access (access to the server device 10) through the login process.

[0070] In the game progression processing, the control unit 13 (game progression unit 100) of the server device 10 transmits game data for executing the game to the game device 15. The control unit 26 of the game device 15 causes the display 31 and speaker 32 to output images and sounds related to the game, based on the game data transmitted from the server device 10. The user operates the controller 33 in accordance with the images and sounds output from the display 31 and speaker 32.

[0071] The control unit 26 of the game device 15 transmits operation information indicating operations input to the controller 33 to the server device 10. The control unit 13 (game progression unit 100) of the server device 10 generates game data that reflects the operation information transmitted from the game device 15, based on the operation information, and transmits the game data to the game device 15.

[0072] The game progresses by repeating the above process (the process of transmitting and receiving game data and operation information between the control unit 13 of the server device 10 and the control unit 26 of the game device 15).

[0073] For example, the game progression unit 100 progresses the game by causing player characters to move within the game space in response to operations by the user. The game progression unit 100 also causes non-player characters and predetermined objects (e.g., vehicles) to move within the game space. For example, the game progression unit 100 controls the actions of non-player characters and predetermined objects using AI (artificial intelligence), and progresses the game in response to the actions of the player characters and non-player characters.

[0074] In addition, the control unit 13 of the server device 10 is able to manage (confirm) the position and movement of the player character within the virtual space based on the game data generated by the game progression unit 100 and / or the operation information transmitted from the game device 15.

[0075] [Image display processing] The image display process is a process for displaying various images on the display 31. In the image display process, the control unit 26 of the game device 15 displays a desired image on the display 31 in response to a user operation (an operation for displaying a desired image) input to the controller 33. In this example, the images displayed by the image display process include an image showing a link party menu, an image showing a link party list, and the like.

[0076] <Image of Link Party menu> FIG. 3 illustrates an image P11 showing a link party menu. In this example, the link party menu includes six items related to the link party. Hereinafter, the process of "inputting an operation to the controller 33 to select one item from the link party menu" will be simply described as "when one item is selected from the link party menu." Note that FIG. 3 illustrates an image P11 displayed on the display 31 of the game device 15 of the user who will be the leader (host) of the link parties.

[0077] When the item "Invite to Link Party" in the first row is selected, processing for inviting the user to the link party (link party invitation processing) begins. When the item "View Link Party Members" in the second row is selected, control unit 26 of game device 15 causes display 31 to display image P21 (see FIG. 4) showing a link party list.

[0078] When the item "View invitation notice list" on the third row is selected, the control unit 26 of the game device 15 causes the display 31 to display an image P12 showing a submenu related to invitation notices.

[0079] When the fourth option, "Return from environmental link," is selected, a process for removing the user from the environmental link (environmental link removal process) is initiated. When the fifth option, "Invite everyone to environmental link," is selected, a process for removing all users registered on the link party list from the environmental link (environmental link invitation process) is initiated. When the sixth option, "Remove from link party," is selected, a process for removing the user from the link party list (link party removal process) is initiated.

[0080] In the example of Fig. 3, the submenu list shown in image P12 includes three subitems related to solicitation notifications. Hereinafter, the process of "an operation to select one subitem from the submenu is input to controller 33" will be simply described as "when one subitem is selected from the submenu."

[0081] When the sub-item "Link Party Invitation Notification" in the first row is selected, processing to confirm the invitation to a link party (Link Party Invitation Confirmation Processing) begins. When the sub-item "Quest Invitation Notification" in the second row is selected, processing to confirm the invitation to a quest (Quest Invitation Confirmation Processing) begins. When the sub-item "Environment Link Invitation Notification" in the third row is selected, processing to confirm the invitation to an environment link (Environment Link Invitation Confirmation Processing) begins.

[0082] In addition, when the image P11 showing the link party menu is displayed on the display 31 of the game device 15 of a user other than the user who will be the leader (host) of the link party, the item "Invite to be a link party" on the first line is omitted.

[0083] <Link Party List Image> FIG. 4 illustrates an image P21 showing a link party list. The link party list shows a list of users who organize link parties. In the example of FIG. 4, four users are registered as users who organize link parties. In this example, the link party list created for each leader (host) of the link parties is stored in the memory unit 12 of the server device 10.

[0084] The Link Party List registers the name, user ID, rank, status, and other information of the user who organizes the Link Party as a single record. The "Status" displays the user's current status (action log). Examples of the above statuses include "On Quest," which indicates that the user is participating in a quest, "Quest Inviting," which indicates that the user is being invited to participate in a quest, "Environment Linking," which indicates that the user is participating in an Environment Link, and "Environment Link Inviting," which indicates that the user is being invited to participate in an Environment Link.

[0085] For example, the link party list is stored in the memory unit 12 of the server device 10. When an operation to display an image P21 of the link party list is input to the controller 33, the control unit 26 of the game device 15 transmits a transmission request to the server device 10 requesting transmission of the link party list. In response to the transmission request, the control unit 13 of the server device 10 transmits the link party list stored in the memory unit 12 to the game device 15. The control unit 26 of the game device 15 receives the link party list transmitted from the server device 10, and causes the display 31 to display an image P21 showing the link party list.

[0086] Furthermore, when an operation (for example, a predetermined button operation) is input to the controller 33 to select one of the users registered in the link party list, the control unit 26 causes the display 31 to display an image P22 showing a submenu related to the selected user. In the example of FIG. 4, the submenu includes three subitems. Note that FIG. 4 illustrates an example of image P22 displayed on the display 31 of the game device 15 of the user who will be the leader (host) of the link parties.

[0087] When the sub-item "Delegate link party leader" in the first row is selected, a process (leader delegation process) is initiated to change the user who will be the link party leader to another user. When the sub-item "Exclude from link party" in the second row is selected, a process (link party exclusion process) is initiated to exclude the user from the link party.

[0088] When the sub-item "View Profile" on the third row is selected, the control unit 26 of the game device 15 causes a profile image (not shown) showing the profile of the selected user (the user corresponding to the above sub-menu) to be displayed on the display 31. This profile image includes information about the player character currently being played by the user, such as the name of the player character, various images related to the player character, information about the equipped armor and weapons, and the user's total playing time.

[0089] In addition, when image P22 showing the above submenu is displayed on the display 31 of the game device 15 of another user who is not the user who will be the leader (host) of the link party, the sub-item "Delegate link party leader" in the first row and the sub-item "Exclude from link party" in the second row are omitted.

[0090] [Solicitation Processing] The solicitation process includes a link party solicitation process for soliciting a user to a link party, a quest solicitation process for soliciting a user to a quest, and an environment link solicitation process for soliciting a user to an environment link. Hereinafter, the soliciting user will be referred to as the "soliciting user," and the solicited user will be referred to as the "solicited user."

[0091] Link Party Solicitation Processing The link party invitation process is performed by a user who will be the leader (host) of the link parties. In this example, when an operation to select the item "Invite to link parties" in the first row shown in image P11 in Figure 3 is input to controller 33, the link party invitation process is started.

[0092] In the link party invitation process, the game device 15 of the inviting user displays on the display 31 an image showing a candidate member list that lists users who are candidates for invitation to become a link party. Examples of users who are candidates for invitation include users who have previously played quests with the inviting user, and users who have many commonalities or similarities with the inviting user in terms of their profile, such as rank. Candidate users for invitation can be identified based on past game progress results (history).

[0093] FIG. 5 illustrates an image P31 showing a candidate member list. In the example of FIG. 5, six users are registered as candidates for invitation to the link party. The member list registers the name, user ID, rank, status, etc. of each candidate user as a single record. The status is displayed as "Link party inviting" if the candidate soliciting user has already been invited to the link party, and as "Not yet invited" if the candidate soliciting user has not yet been invited to the link party. In this example, the candidate member list is stored in memory unit 25 of game device 15.

[0094] When an operation (for example, a predetermined button operation) is input to the controller 33 on the inviting user's game device 15 to select one of the "uninvited" users on the candidate member list, the control unit 26 transmits solicitation information indicating that the inviting user is inviting the selected user (invited user) to become a link party to the server device 10. The control unit 26 also changes the status of the invited user on the candidate member list from "unregistered" to "inviting to link party."

[0095] The control unit 13 of the server device 10 transfers the solicitation notification information to the game device 15 of the invited user indicated in the solicitation information. In the game device 15 of the invited user, the control unit 26 registers the soliciting user indicated in the solicitation notification information in a link party solicitation notification list (not shown). The link party solicitation notification list indicates a list of users who are being solicited by the link party (which users are being solicited by the link party). In this example, the link party solicitation notification list is stored in the memory unit 25 of the game device 15 and is used in the link party solicitation confirmation process described below.

[0096] Furthermore, when an operation (for example, a predetermined button operation) is input to the controller 33 on the inviting user's game device 15 to select one of the users in the "link party inviting" member list, the control unit 26 causes the display 31 to display an image P23 showing a submenu "Cancel link party invitation." When an operation to select the submenu is input to the controller 33, solicitation cancellation information indicating that the inviting user has canceled the invitation to the link party of the selected user (the invited user corresponding to the above submenu) is transmitted to the server device 10. Furthermore, the control unit 26 changes the status of the invited user in the candidate member list from "link party inviting" to "not invited."

[0097] Furthermore, the control unit 13 of the server device 10 transfers the solicitation cancellation information to the game device 15 of the invited user indicated in the solicitation cancellation information. In the game device 15 of the invited user, the control unit 26 deletes the soliciting user indicated in the solicitation cancellation information from the link party solicitation notification list (not shown).

[0098] <Quest invitation process> The quest invitation process is performed by any user. The flow of the quest invitation process is the same as the flow of the link party invitation process. In the quest invitation process, a candidate member list (not shown) that shows a list of users who are candidates for invitation to the quest is updated in the game device 15 of the inviting user, and a quest invitation notification list (not shown) that shows a list of users who are being invited to the quest is updated in the game device 15 of the invited user.

[0099] <Environmental link solicitation processing> The environmental link invitation process is performed by a user registered in the link party list. In this example, when an operation to select the item "Invite everyone to environmental link" in the fifth row shown in image P11 in Figure 3 is input to the controller 33, the environmental link invitation process is started.

[0100] The flow of the environment link solicitation process is the same as the flow of the link party solicitation process. In the environment link solicitation process, one of the users registered on the link party list becomes the soliciting user, and the remaining users registered on the link party list excluding the soliciting user become invited users. In the environment link solicitation process, a candidate member list (not shown) that lists users who are candidates for invitation to the environment link is updated on the game device 15 of the soliciting user, and an environment link solicitation notification list (not shown) that lists users who are being invited to the environment link is updated on the game device 15 of the invited user.

[0101] [Solicitation confirmation processing] The solicitation confirmation process includes a link party solicitation confirmation process, a quest solicitation confirmation process, and an environment link solicitation confirmation process. These processes are performed by any user (invited user).

[0102] <Link Party Solicitation Confirmation Processing> The link party solicitation confirmation process is performed in game device 15 used by the invited user. Control unit 26 causes display 31 to display an image (not shown) showing a link party solicitation notification list. The link party solicitation notification list shows a list of soliciting users who will solicit the invited user to become a link party. When an operation is input to controller 33 to select a "user who accepts the solicitation" from the link party solicitation notification list, the link party registration process is initiated.

[0103] <Quest invitation confirmation process> The flow of the quest invitation confirmation process is the same as the flow of the link party invitation confirmation process. In the quest invitation confirmation process, a quest invitation notification list (not shown) is displayed, which shows a list of inviting users who will invite the invited user to the quest. When an operation is input to the controller 33 to select a "user who will accept the invitation" from the quest invitation notification list, the quest invitation acceptance process begins.

[0104] <Environmental link solicitation confirmation process> The flow of the environmental link solicitation confirmation process is the same as the flow of the link party solicitation confirmation process. In the environmental link solicitation confirmation process, an environmental link solicitation notification list (not shown) is displayed, which shows a list of soliciting users who will solicit the invited user to the environmental link. When an operation is input to the controller 33 to select a "user who will accept the solicitation" from the environmental link solicitation notification list, the environmental link solicitation approval process is started.

[0105] [Link Party Registration Process] The link party registration process is performed by a user who has been invited by a link party. The link party registration process is an example of a registration step in the process by game system 1 (a management method for managing user participation in a quest).

[0106] In the link party registration process, control unit 26 in game device 15 of a user (invited user) invited by a link party transmits link party solicitation acceptance information indicating a user (inviting user) selected as a "user who accepts the solicitation" from a link party solicitation notification list (not shown) to server device 10. The link party solicitation acceptance information indicates the invited user who accepted the solicitation to the link party and the soliciting user who made the solicitation to the link party. Control unit 26 also deletes the soliciting user from the link party solicitation notification list.

[0107] The control unit 13 (registration unit 101) of the server device 10 detects from the storage unit 12 a link party list in which the soliciting user indicated in the link party solicitation approval information is registered, and registers the approved user indicated in the solicitation approval information in that link party list. In this example, a record including the approved user's "name," "user ID," "rank," and "status (action log)" is registered in the link party list. In this way, the registration unit 101 registers the user in the link party list.

[0108] Next, the control unit 13 (registration unit 101) of the server device 10 transmits registration completion information indicating that a new user (invited user) has been registered in the link party list in which the inviting user has been registered to the inviting user's game device 15. In the inviting user's game device 15, the control unit 26 deletes the record related to the invited user indicated in the registration completion information from the candidate member list (see FIG. 5).

[0109] [Link Party Withdrawal Processing] The link party withdrawal process is performed by a user registered in the link party list (see FIG. 4). In the link party withdrawal process, an operation to withdraw from the link party is input to controller 33 in game device 15, and control unit 26 transmits link party withdrawal information indicating the user withdrawing from the link party to server device 10. Control unit 13 of server device 10 detects from memory unit 12 the link party list in which the user indicated in the link party withdrawal information is registered, and deletes from that link party list the record related to the "user indicated in the link party withdrawal information."

[0110] In addition, if the user leaving the link party is the "leader of that link party," the control unit 13 (registration unit 101) sets another user (a user excluding the leader) who is registered in the link party list together with the leader of that link party as the "new leader of that link party."

[0111] [Leader delegation process] The leader delegation process is performed by a user who will become the leader of the link parties. In the leader delegation process, an operation is input to controller 33 on game device 15 of the user who will become the leader of the link parties to select a user who will become the "new leader of the link parties" from the link party list (see FIG. 4), and control unit 26 transmits leader change information indicating the user selected as the new leader to server device 10. The leader change information indicates the user who will be the leader before the change (old leader user) and the user who will be the leader after the change (new leader user).

[0112] The control unit 13 of the server device 10 detects from the storage unit 12 the link party list corresponding to the old leader user indicated in the leader change information, and changes the link party leader in that link party list from the "old leader user" to the "new leader user." In the example of Figure 4, if the user registered in the first row corresponds to the "link party leader" and the link party leader is changed from "User A" to "User B," the record related to "User A" registered in the first row is swapped with the record related to "User B" registered in the second row.

[0113] [Link Party Exclusion Processing] The link party exclusion process is performed by a user who will be the leader of the link parties. In the link party exclusion process, an operation to select a "user to be excluded from link parties" from the link party list (see FIG. 4) is input to controller 33 on game device 15 of the user who will be the leader of the link parties, and control unit 26 transmits link party exclusion information indicating the user selected as the excluded user to server device 10.

[0114] The control unit 13 of the server device 10 detects from the memory unit 12 a link party list in which the user indicated in the link party exclusion information is registered, and deletes from the link party list the record related to the "user indicated in the link party exclusion information."

[0115] [Quest invitation approval process] The quest invitation acceptance process is performed by a user who has been invited to a quest (invited user). In the quest invitation acceptance process, the game device 15 of the invited user transmits quest invitation acceptance information indicating a user (inviting user) selected from a quest invitation notification list (not shown) as a "user who accepts the invitation" to the server device 10. The quest invitation acceptance information indicates the invited user who accepted the invitation to the quest and the inviting user who made the invitation to the quest. The control unit 26 also deletes the above-mentioned inviting user from the quest invitation notification list.

[0116] The control unit 13 (management unit 102) of the server device 10 permits the invited user indicated in the quest invitation acceptance information to participate in the "quest invited by the inviting user indicated in the quest invitation acceptance information." This allows the invited user to play the quest.

[0117] Next, the control unit 13 (management unit 102) of the server device 10 transmits quest participation information indicating that the invited user will participate in the "quest invited by the inviting user" to the inviting user's game device 15. In the inviting user's game device 15, the control unit 26 deletes the record related to the invited user indicated in the quest participation information from a candidate member list (not shown) that lists users who are candidates for invitation to the quest.

[0118] [Environmental Link Solicitation Approval Processing] The environment link invitation acceptance process is performed by a user (invited user) who has been invited to an environment link. In the environment link invitation acceptance process, the game device 15 of the invited user transmits to the server device 10 environment link invitation acceptance information indicating a user (inviting user) selected as a "user who accepts the invitation" from an environment link invitation notification list (not shown). The environment link invitation acceptance information indicates the invited user who accepted the invitation to the environment link and the inviting user who made the invitation to the environment link. The control unit 26 also deletes the above-mentioned inviting user from the environment link invitation notification list.

[0119] The control unit 13 (management unit 102) of the server device 10 initiates participation of the invited user indicated in the environment link invitation approval information in the "environment link invited by the inviting user indicated in the environment link invitation approval information." This allows the invited user to play the game under the common environment (game play conditions) of the environment link.

[0120] Next, the control unit 13 (management unit 102) of the server device 10 transmits environment link participation information indicating that the invited user will participate in the "environment link invited by the inviting user" to the inviting user's game device 15. In the inviting user's game device 15, the control unit 26 deletes the record related to the invited user indicated in the environment link participation information from a candidate member list (not shown) that lists users who are candidates for invitation to the environment link.

[0121] [Environmental link exit processing] The environmental link withdrawal process is performed by a user participating in the environmental link. In the environmental link withdrawal process, the control unit 26 of the game device 15 transmits environmental link withdrawal information indicating the user (user using this game device 15) who is withdrawing from the environmental link to the server device 10. The control unit 13 of the server device 10 cancels the participation of the user indicated in the environmental link withdrawal information in the environmental link. This allows the user who has withdrawn from the environmental link to play the game in an individual environment that corresponds to the progress of the game, rather than in the common environment of the above-mentioned environmental link.

[0122] [Link Party Management Processing] The link party management process is a management process related to users registered in the link party list (see FIG. 4). The link party management process is an example of a management step in the process by the game system 1 (a management method for managing user participation in a quest).

[0123] In the following explanation, one of the users registered on the link party list will be referred to as the "first registered user U1," a user registered on the link party list together with the first registered user U1 will be referred to as the "second registered user U2," and a user not registered on the link party list in which the first registered user U1 is registered will be referred to as the "unregistered user U5."

[0124] In the link party management process, the control unit 13 (management unit 102) of the server device 10 manages user participation in quests so that when a first registered user U1 participates in a participation quest, a second registered user U2 can participate in the participation quest with priority over an unregistered user U5.

[0125] The participation quest has a participation condition set for participating in the participation quest, which includes at least one of the following conditions: a condition that the password set for the participation quest is entered, and a condition that participation in the participation quest is approved.

[0126] In the link party management process, the management unit 102 allows the unregistered user U5 to participate in the participation quest if the unregistered user U5 meets the participation conditions set in the participation quest. In addition, the management unit 102 allows the second registered user U2 to participate in the participation quest regardless of whether the second registered user U2 meets the participation conditions set in the participation quest.

[0127] Also, in the link party management process, when a first registered user U1 participates in a participation quest, the management unit 102 sends a participation notification to a second registered user U2 to notify them that the first registered user U1 will be participating in the participation quest, but does not send a participation notification to an unregistered user U5.

[0128] Furthermore, in the link party management process, when multiple first registered users U1 participate in multiple participation quests, the management unit 102 sends multiple participation notifications corresponding to the multiple participation quests to the second registered user U2.

[0129] The participation notification includes an application instruction for applying to participate in the participation quest. When the management unit 102 receives a reply containing the application instruction included in the participation notification sent to the second registered user U2, the management unit 102 permits the second registered user U2 to participate in the participation quest.

[0130] The registration of the first registered user U1 in the link party list continues even after the participation quest ends. After the participation quest ends, the management unit 102 maintains the registration of the first registered user U1 in the link party list without deleting it. The same applies to the registration of the second registered user U2 in the link party list.

[0131] [Example 1 of link party management processing] Next, the flow of the link party management process will be explained with a specific example, with reference to Figures 6 and 7. In the example of Figure 6, four users, "User A" to "User D," are registered in the link party list indicating "Link Party A," while "User E" is not registered in the above link party list. Examples of User E include a user registered in a link party list other than "Link Party A," and a user not registered in any link party list.

[0132] (1) Participating in a Quest 6, when an operation for requesting participation in "Quest A" by "User A" is input to controller 33 in game device 15 of "User A," control unit 26 transmits a participation request indicating the request for participation in "Quest A" by "User A" to server device 10. In response to the participation request, control unit 13 (management unit 102) of server device 10 permits "User A" to participate in "Quest A." In this way, "User A" participates in "Quest A."

[0133] <(2) Participation notification> Next, in server device 10, management unit 102 refers to the link party list stored in storage unit 12 (the link party list in which "User A" is registered), and transmits a "Participation Notification A," which is a participation notification indicating that User A will participate in Quest A, to each of the game devices 15 of "User B," "User C," and "User D" registered in the link party list. Note that in this example, participation notification A includes an application instruction to apply to participate in "Quest A." Furthermore, management unit 102 does not transmit "Participation Notification A" to the game device 15 of "User E."

[0134] In the example of Figure 6, "User A" corresponds to the first registered user U1, and "User B," "User C," and "User D" correspond to the second registered user U2. "User E" corresponds to the unregistered user U5. "Quest A" corresponds to the participating quest.

[0135] 7 illustrates an example of a game image P10 displayed on the display 31 of the game device 15 of "User B." As shown in FIG. 7, along with the game image P10, a participation notification 50 including a notification message stating "User A of link party A has joined quest A" is displayed on the display 31 of "User B."

[0136] (3) Quest Participation: No participation restrictions Next, when an operation to request "User B" to participate in "Quest A" is input to the controller 33 on the game device 15 of "User B," the control unit 26 transmits to the server device 10 a participation request indicating "User B"'s request to participate in "Quest A."

[0137] In server device 10, management unit 102 determines whether the user indicated in the participation request (the user applying to participate in the participation quest) is registered in the link party list indicating "Link Party A." Since "User B" is registered in the above link party list, management unit 102 permits "User B" to participate in "Quest A" regardless of whether "User B" meets the participation conditions set for "Quest A." In this way, "User B" participates in "Quest A."

[0138] In this example, as shown in FIG. 7, the participation notification 50 displayed on the display 31 of "user B" includes a shortcut display element 51 and a time display element 52.

[0139] The shortcut display element 51 is a display element for instructing a reply (a reply to the management unit 102) of an application instruction for applying to participate in the "participation quest." In the example of FIG. 7, the shortcut display element 51 is a start button labeled "START," and can be selected by operating the controller 33.

[0140] When an operation to select shortcut display element 51 is input to controller 33 in game device 15 of "User B," control unit 26 detects an application instruction to apply for participation in the "participation quest" from participation notification A and automatically transmits the application instruction to server device 10. In server device 10, management unit 102 accepts the application instruction returned from game device 15 of "User B." In this way, management unit 102 accepts the application from "User B" to participate in "Quest A."

[0141] In this example, the operation by "User B" to apply to participate in "Quest A" is an operation (shortcut operation) to select the shortcut display element 51. The participation application indicating the application by "User B" to participate in "Quest A" is a participation instruction to apply to participate in the "Participation Quest" returned from the game device 15 of "User B."

[0142] In order to request "User B" to participate in "Quest A" without using a shortcut operation, an operation to display a menu screen image (not shown), an operation to select "Quest Application" from the menu screen image, and an operation to select "Quest A" as the target for "User B" to request participation are required. On the other hand, if a shortcut operation is used, "User B" can request to participate in "Quest A" using only the shortcut operation.

[0143] The time display element 52 is a time element that indicates the display time (remaining time until the display ends) of the join notification 50. In the example of Fig. 7, the time display element 52 is a playback bar, which is a bar-shaped display element that extends in the left-right direction of the game image P10. The length of the time display element 52 changes depending on the remaining display time of the join notification 50 (remaining time until the display ends).

[0144] (4) Quest Participation: Participation restrictions apply Furthermore, when an operation to request "User E" to participate in "Quest A" is input to the controller 33 on the game device 15 of "User E," the control unit 26 transmits to the server device 10 a participation request indicating "User E"'s request to participate in "Quest A."

[0145] In the server device 10, the management unit 102 determines whether the user indicated in the participation request (the user applying to participate in the participation quest) is registered in the link party list indicating "Link Party A." Since "User E" is not registered in the above link party list, the management unit 102 determines whether "User E" meets the participation conditions set for "Quest A." If "User E" meets the participation conditions set for "Quest A," the management unit 102 then permits "User E" to participate in "Quest A." In this way, "User E" participates in "Quest A."

[0146] [Specific example 2 of link party management processing] Next, a specific example of the flow of the link party management process will be explained with reference to Figures 8 and 9. As in the example of Figure 6, in the example of Figure 8, four users, "User A" to "User D", are registered in the link party list indicating "Link Party A", and "User E" is not registered in the above link party list.

[0147] As shown in Figure 8, when "User A" participates in "Quest A," "User B" participates in "Quest B," and "User C" participates in "Quest C," the management unit 102 sends to the game device 15 of "User D" a "Participation Notification A" which is a participation notification indicating that User A will participate in Quest A, a "Participation Notification B" which is a participation notification indicating that User B will participate in Quest B, and a "Participation Notification C" which is a participation notification indicating that User C will participate in Quest C.

[0148] In the example of Figure 8, "User A," "User B," and "User C" correspond to the first registered user U1. "User D" corresponds to the second registered user U2. "Quest A," "Quest B," and "Quest C" correspond to participation quests.

[0149] Note that the participation notification A may be sent not only to the game device 15 of "User D," but also to each of the game devices 15 of "User B" and "User C." In this case, "User B" and "User C" correspond to second registered users U2 who are registered in the link party list indicating "Link Party A" together with "User A," who is the first registered user U1. Similarly, the participation notification B may be sent to each of the game devices 15 of "User A" and "User C," and the participation notification C may be sent to each of the game devices 15 of "User A" and "User B."

[0150] 9 illustrates an example of a game image P10 displayed on the display 31 of the game device 15 of "User D." As shown in FIG. 9, along with the game image P10, the display 31 of "User D" displays a first participation notification 50a including a notification statement that "User A of link party A has participated in quest A," a second participation notification 50b including a notification statement that "User B of link party A has participated in quest B," and a third participation notification 50c including a notification statement that "User C of link party A has participated in quest C."

[0151] Similar to the join notification 50 shown in Fig. 7, each of the three join notifications 50 (first join notification 50a, second join notification 50b, and third join notification 50c) shown in Fig. 9 includes a shortcut display element 51 and a time display element 52. In the example of Fig. 9, the three join notifications 50 are arranged vertically on the game image P10.

[0152] [Summary of the embodiment] To summarize the above, the game program of the embodiment causes a computer system having one or multiple cooperating computers (control unit 13) to function as a game progression unit 100 that progresses a game that includes quests, a registration unit 101 that registers users in a party (link party list), and a management unit 103 that manages users' participation in quests. When a first registered user U1, who is a user registered in a party, participates in a quest, the management unit 103 manages users' participation in quests so that a second registered user U2, who is a user registered in the party together with the first registered user U1, can participate in the participation quest in which the first registered user U1 is participating with priority over an unregistered user U5, who is a user not registered in the party.

[0153] The game system of the embodiment comprises the game progression unit 100, the registration unit 101, and the management unit 102.

[0154] The management method of the embodiment is a management method for managing user participation in quests included in a game, and includes a registration step (link party registration processing) and a management step (link party management processing). In the registration step, users are registered in a party (link party list). In the management step, user participation in quests is managed so that, when a first registered user U1, who is a user registered in the party, participates in a quest, a second registered user U2, who is a user registered in the party together with the first registered user U1, can participate in the participation quest, which is the quest in which the first registered user U1 will participate, with priority over an unregistered user U5, who is a user not registered in the party.

[0155] [Effects of the embodiment] As described above, in the embodiment, by managing user participation in quests so that the second registered user U2 can participate in participation quests with priority over the unregistered user U5, it is possible to make it easier for the second registered user U2 to participate in participation quests than the unregistered user U5. This makes it easier for users registered in the same party to participate in the same quest together.

[0156] In the embodiment, participation conditions for participating in the participation quest are set in the participation quest. The management unit 102 permits the unregistered user U5 to participate in the participation quest if the unregistered user U5 meets the participation conditions set in the participation quest. The management unit 102 also permits the second registered user U2 to participate in the participation quest regardless of whether the second registered user U2 meets the participation conditions set in the participation quest.

[0157] In the above configuration, a participation restriction can be set for the unregistered user U5 (a restriction that the user must meet the participation conditions to participate in the participation quest), and the participation restriction can be exempted for the second registered user U2. This makes it easier for the second registered user U2 to participate in the participation quest than the unregistered user U5.

[0158] In the embodiment, the participation conditions include at least one of the conditions that a password set for the participation quest is entered and that participation in the participation quest is approved.

[0159] In the above configuration, by requiring the unregistered user U5 to enter at least one of a password and participation approval in order to participate in the participation quest, it is possible to set a participation restriction on the unregistered user U5.

[0160] In addition, in the embodiment, the registration of the first registered user U1 in the party continues even after the participation quest ends.

[0161] Unlike typical party formations where a party disbands after a quest ends, the above configuration allows the first registered user U1 and the second registered user U2 to continue forming the same party even after the quest they participated in ends. This maintains the effect of making it easier for users registered in the same party to participate in the same quest together.

[0162] Also, in an embodiment, when a first registered user U1 participates in a participation quest, the management unit 102 sends a participation notification to a second registered user U2 to notify them that the first registered user U1 will be participating in the participation quest, but does not send a participation notification to an unregistered user U5.

[0163] In the above configuration, by sending a participation notification to the second registered user U2 while not sending a participation notification to the unregistered user U5, it is easier for the second registered user U2 to participate in a participation quest than the unregistered user U5.

[0164] In addition, in the embodiment, when multiple first registered users U1 participate in multiple participation quests, the management unit 102 sends multiple participation notifications corresponding to the multiple participation quests to the second registered user U2.

[0165] In the above configuration, the second registered user U2 can be made aware that multiple first registered users U1 are participating in multiple participation quests, respectively, and can thereby be made to select which of the multiple participation quests to participate in.

[0166] In the embodiment, the participation notification includes an application instruction for applying to participate in the participation quest. When the management unit 102 receives a reply to the application instruction included in the participation notification sent to the second registered user U2, the management unit 102 permits the second registered user U2 to participate in the participation quest.

[0167] With the above configuration, the process by which the second registered user U2 is permitted to participate in a participation quest can be simplified.

[0168] (Other embodiments) In the above description, the following configuration or processing may be performed.

[0169] Although the above example shows a case where participation conditions are set for a participation quest, the present invention is not limited to this. For example, participation conditions may not be set for a participation quest.

[0170] Although the case where the join instruction is included in the join notification has been described as an example, the present invention is not limited to this. For example, the join instruction does not have to be included in the join notification. The join notification 50 displayed on the display 31 does not have to include the shortcut display element 51 or the time display element 52.

[0171] Although the above example shows a case where user registration is performed by registering in a list of link parties, the present invention is not limited to this. Registration and management of link parties may be performed by means other than a list format.

[0172] The game program may be implemented so as to be executed by multiple computers working together. For example, the processing performed by the control unit 13 may be shared among multiple computers provided in one server device 10, or may be shared among multiple computers included in multiple server devices 10 connected via the communication network 5.

[0173] For example, in the above embodiment, a database for managing game media, various data and lists related to link parties such as a link party solicitation notification list, etc. are stored in the memory unit 25 of the game device 15, but these may also be stored in the memory unit 12 of the server device 10.

[0174] The effects of the present invention can be achieved even when these other embodiments are adopted. Furthermore, this embodiment can be combined with other embodiments, and other embodiments can be combined with each other as appropriate. The above-described embodiments are essentially preferred examples and are not intended to limit the scope of the present invention, its applications, or its uses. [Explanation of symbols]

[0175] 1. Game System 10 Server device 11 Network Interface 12 Storage section 13 Control Unit 15 Gaming Devices 20 gaming consoles 21 Network Interface 22 Graphics Processing Unit 23 Audio Processing Unit 24 Operation processing section 25 Memory section 26 Control Unit 31 Display 32 speakers 33 Controller 100 Game Progression Section 101 Registration Department 102 Management Department U1 First registered user U2 Second Registered User U5 Unregistered User

Claims

1. A computer system having one or more computers working together, a game progression section that progresses the game including quests; a registration unit for registering a user to a party; functioning as a management unit that manages the user's participation in the quest; the management unit manages the participation of the users in the quest so that, when a first registered user who is a user registered in the party participates in the quest, a second registered user who is a user who is registered in the party together with the first registered user can participate in the participation quest, which is the quest in which the first registered user will participate, preferentially over an unregistered user who is a user not registered in the party; The participation quest has a participation condition set for participating in the participation quest, The management unit permitting the unregistered user to participate in the participation quest if the unregistered user satisfies the participation conditions set for the participation quest; Allowing the second registered user to participate in the participation quest regardless of whether the second registered user satisfies the participation conditions set for the participation quest Game program.

2. In the game program of claim 1, The participation conditions include at least one of a condition that a password set for the participation quest is entered and a condition that participation in the participation quest is approved. Game program.

3. The game program of claim 1, The registration of the first registered user in the party continues even after the participation quest ends. Game program.

4. The game program of claim 1, When the first registered user participates in the participation quest, the management unit sends a participation notification to the second registered user to notify the second registered user that the first registered user will participate in the participation quest, but does not send the participation notification to the unregistered user. Game program.

5. In the game program of claim 4, When the first registered users each participate in a plurality of the participation quests, the management unit sends the second registered user a plurality of participation notifications corresponding to the plurality of participation quests. Game program.

6. In the game program of claim 4, The participation notice includes an application instruction for applying to participate in the participation quest, The management unit, when the application instruction included in the participation notification sent to the second registered user is returned, permits the second registered user to participate in the participation quest. Game program.

7. a game progression section that progresses the game including quests; a registration unit for registering a user to a party; a management unit that manages the user's participation in the quest; the management unit manages the participation of the users in the quest so that, when a first registered user who is a user registered in the party participates in the quest, a second registered user who is a user who is registered in the party together with the first registered user can participate in the participation quest, which is the quest in which the first registered user will participate, preferentially over an unregistered user who is a user not registered in the party; The participation quest has a participation condition set for participating in the participation quest, The management unit permitting the unregistered user to participate in the participation quest if the unregistered user satisfies the participation conditions set for the participation quest; Allowing the second registered user to participate in the participation quest regardless of whether the second registered user satisfies the participation conditions set for the participation quest Game system.

8. A management method for managing a user's participation in a quest included in a game, comprising: a registration step for registering a user with a party; a management step of managing the participation of users in the quest so that, when a first registered user who is a user registered in the party participates in the quest, a second registered user who is a user who is registered in the party together with the first registered user can participate in the participation quest, which is the quest in which the first registered user will participate, with priority over an unregistered user who is a user not registered in the party; The participation quest has a participation condition set for participating in the participation quest, In the management step, permitting the unregistered user to participate in the participation quest if the unregistered user satisfies the participation conditions set for the participation quest; Allowing the second registered user to participate in the participation quest regardless of whether the second registered user satisfies the participation conditions set for the participation quest Management method.

Images