JP2013128582A - Game device, game system, game task data generation device, game task data generation method, game control method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a game device capable of generating game task data rich in variation.SOLUTION: The game device 10 executes a game wherein a user aims to clear a game task based on the game task data. A first keyword acquisition part 72 acquires one or more keywords selected by the user. A second keyword acquisition part 74 acquires one or more keywords selected by a game character inside the game. A game task data generation part 76 generates the game task data based on a combination between the one or more keywords acquired by the first keyword acquisition part 72 and the one or more keywords acquired by the second keyword acquisition part 74.

Description

  The present invention relates to a game device, a game system, a game task data generation device, a game task data generation method, a game control method, and a program.

  A game in which a user aims to clear a game task is known. For example, in a game in which a user operates a game character and adventures in a virtual world, a mission aimed at defeating a specific enemy character or a mission aimed at obtaining a specific item is a “game task. May be presented to the user.

  Patent Document 1 discloses a technique for automatically generating the game task (for example, a mission or the like) as described above. Specifically, a technique for generating a new game task by combining game tasks that have already been cleared by the user is disclosed.

JP 2010-214052 A

  However, in the technique described in Patent Document 1, a new game task is generated by combining game tasks that have already been cleared by the user. Therefore, a newly generated game task is a game task that has already been cleared by the user. In some cases, it was similar to, and lacked newness.

  The present invention has been made in view of the above problems, and its object is to provide a game device, a game system, a game task data generation device, and a game task data generation method capable of generating a variety of game task data. Another object is to provide a game control method and a program.

  In order to solve the above problems, a game device according to the present invention is a game device in which a user aims to clear a game task based on game task data, and one or more selected by the user. First acquisition means for acquiring a keyword, second acquisition means for acquiring one or more keywords selected by a game character in the game, and one or more acquired by the first acquisition means Generation means for generating the game task data based on a combination of a keyword and one or more keywords acquired by the second acquisition means.

  The game system according to the present invention includes a first acquisition unit that acquires one or a plurality of keywords selected by the user in a game system that executes a game in which the user aims to clear a game task; Second acquisition means for acquiring one or more keywords selected by a game character in the game, one or more keywords acquired by the first acquisition means, and acquired by the second acquisition means And generating means for generating game task data based on a combination of one or a plurality of keywords, and executing means for executing the game based on the game task data.

  In addition, the game task data generation device according to the present invention is a game task data generation device that generates game task data for executing a game that the user aims to clear the game task. First acquisition means for acquiring a plurality of keywords, second acquisition means for acquiring one or a plurality of keywords selected by the game character in the game, and 1 or acquired by the first acquisition means Generation means for generating the game task data based on a combination of a plurality of keywords and one or more keywords acquired by the second acquisition means.

  The game task data generation method according to the present invention includes a first acquisition step of acquiring one or a plurality of keywords selected by a user who plays a game that aims to clear a game task, and a game in the game A second acquisition step of acquiring one or more keywords selected by the character; game task data for executing the game; one or more keywords acquired in the first acquisition step; And a generation step of generating based on a combination of the one or a plurality of keywords acquired in the second acquisition step.

  The program according to the present invention is selected by a first acquisition means for acquiring one or a plurality of keywords selected by a user who plays a game that aims to clear a game task, and selected by a game character in the game Second acquisition means for acquiring one or more keywords, and game task data for executing the game, the one or more keywords acquired by the first acquisition means, and the second acquisition As a generating means to generate based on a combination of one or a plurality of keywords acquired by the means, for example, a home game machine (stationary game machine), a portable game machine, an arcade game machine, a mobile phone, portable information A program for causing a computer such as a terminal, personal computer, or server computer to function. .

  An information storage medium according to the present invention is a computer-readable information storage medium recording the above program.

  According to the present invention, it is possible to generate game task data rich in change.

  In one aspect of the present invention, the game task data may include information on at least one of the game task and a reward given to the user when the user clears the game task. The generating means refers to the correspondence data relating to the correspondence relation between the keyword and the information, thereby obtaining the information by one or more keywords acquired by the first acquisition means and the second acquisition means. It may be set based on a combination with one or a plurality of keywords acquired by.

  Also, in one aspect of the present invention, determination means for determining whether or not a game task related to the game task data has been cleared by the user and whether or not information regarding a degree of rarity of the game task data is presented to the user Determination means for determining whether or not based on the determination result of the determination means, and presentation means for presenting the information on the degree of rarity of the game task data to the user based on the determination result of the determination means; May be included.

  In the aspect of the invention, the first acquisition unit may acquire one or a plurality of keywords selected by the user from a plurality of keywords acquired by the user in the game.

  In the aspect of the invention, the second acquisition unit may acquire one or a plurality of keywords selected by the game character from the plurality of keywords acquired by the user in the game. Good.

  The game device according to the present invention is a game device that executes, based on game task data, a game in which the user aims to clear the game task, and whether or not the game task related to the game task data has been cleared by the user. A determination unit that determines whether to present information related to the degree of rarity of the game task data to the user based on a determination result of the determination unit, and a determination by the determination unit Presenting means for presenting the information related to the degree of rarity of the game task data to the user based on the result.

  In addition, the game system according to the present invention is a game system for executing a game in which a user aims to clear a game task, and an execution means for executing the game based on game task data, and a game related to the game task data Based on the determination result of the determination means, the determination means for determining whether or not the task has been cleared by the user and whether or not to present information regarding the degree of rarity of the game task data to the user are determined. And a presenting means for presenting the information on the degree of rarity of the game task data to the user based on a determination result of the determining means.

  In the game control method according to the present invention, in a game that is executed based on the game task data and the user aims to clear the game task, whether or not the game task related to the game task data has been cleared by the user. A determination step for determining whether to present information about the degree of rarity of the game task data to the user based on a determination result in the determination step, and a determination in the determination step A presentation step of presenting the information regarding the degree of rarity of the game task data to the user based on a result.

  In addition, the program according to the present invention is executed based on the game task data, and in a game in which the user aims to clear the game task, whether or not the game task related to the game task data has been cleared by the user. A determination means for determining, a determination means for determining whether or not to present information related to the degree of rarity of the game task data to the user based on a determination result of the determination means, and a determination result of the determination means A program for causing a computer to function as a presentation means for presenting the information related to the degree of rarity of the game task data to the user.

  An information storage medium according to the present invention is a computer-readable information storage medium recording the above program.

  According to the present invention, it is possible to assist the user so that the user can easily grasp the degree of rarity of the game task data while trying not to impair the interest of the game.

It is a figure which shows an example of the hardware constitutions of the game device which concerns on embodiment of this invention. It is a figure which shows an example of a game screen. It is a figure which shows an example of a keyword table. It is a figure for demonstrating an example of the screen transition of a mission production | generation screen. It is a figure for demonstrating an example of the screen transition of a mission production | generation screen. It is a figure for demonstrating an example of the screen transition of a mission production | generation screen. It is a figure which shows an example of mission data. It is a figure which shows an example of a reward rank table. It is a figure which shows an example of a map table. It is a figure which shows an example of a boss character table. It is a figure for demonstrating an example of a mission screen. It is a figure which shows an example of a mission table. It is a figure which shows an example of a mission list screen. It is a functional block diagram of the game device concerning the embodiment of the present invention. It is a figure which shows an example of the data for producing | generating mission data. It is a figure which shows an example of the data for producing | generating mission data. It is a figure which shows an example of the data for producing | generating mission data. It is a figure which shows an example of the data for producing | generating mission data. It is a figure which shows an example of the data for producing | generating mission data. It is a figure which shows an example of the data for producing | generating mission data. It is a figure which shows an example of the data for producing | generating mission data. It is a flowchart which shows an example of the process for producing | generating mission data. It is a flowchart which shows an example of the process for producing | generating mission data. It is a flowchart which shows an example of the process for displaying a mission list screen.

  Hereinafter, examples of embodiments of the present invention will be described in detail with reference to the drawings. The game device according to the embodiment of the present invention includes, for example, a home game machine (stationary game machine), a portable game machine, an arcade game machine, a mobile phone (including a smartphone), and a portable information terminal (tablet computer). ) Or a personal computer or the like.

  FIG. 1 shows an example of a hardware configuration of a game device according to an embodiment of the present invention. As shown in FIG. 1, the game apparatus 10 includes a control unit 11, a storage unit 12, an optical disc drive unit 13, a communication unit 14, a display unit 15, an audio output unit 16, and an operation unit 17.

  The control unit 11 includes, for example, one or a plurality of microprocessors. The control unit 11 executes processing for controlling each unit of the game apparatus 10 or executes information processing based on an operating system or other program stored in the storage unit 12 or the optical disc.

  The storage unit 12 includes a main storage unit and an auxiliary storage unit. The main storage unit includes, for example, a RAM, and a program and data read from the auxiliary storage unit or the optical disc are written to the main storage unit. The main storage unit is also used as a working memory for the control unit 11. The auxiliary storage unit includes a nonvolatile storage medium such as a hard disk drive or a solid state drive, and programs and data are stored in the auxiliary storage unit.

  The optical disk drive unit 13 is for reading a program and data recorded on an optical disk (information storage medium). The program and data are supplied to the game apparatus 10 via the optical disc and stored in the storage unit 12. Note that the game apparatus 10 may include a memory card slot portion. The memory card slot section is for reading a program and data stored in a memory card (information storage medium). The program and data may be supplied to the game apparatus 10 via a memory card and stored in the storage unit 12.

  The communication unit 14 is for performing data communication via a communication network such as the Internet. For example, the program and data are supplied to the game apparatus 10 from a remote location via a communication network and stored in the storage unit 12.

  The display unit 15 is, for example, a liquid crystal display or an organic EL display. The display unit 15 displays a screen according to an instruction from the control unit 11. The audio output unit 16 is, for example, a speaker or a headphone terminal. The sound output unit 16 outputs sound (for example, music or sound effects) in accordance with instructions from the control unit 11.

  The operation unit 17 is used by the user for operation. The operation unit 17 includes one or more operation members for receiving user operations. For example, the operation unit 17 includes a button (key) and / or a stick (lever). For example, the operation unit 17 includes a pointing device such as a touch panel or a mouse.

  In the game apparatus 10 described above, a game in which the user aims to clear the game task is executed. For example, a game (for example, role playing game or action game) in which a game character (user character) operated by the user adventures in the virtual world is executed on the game device 10. Hereinafter, this game will be described.

  FIG. 2 shows an example of the game screen of the game. The virtual world viewed from the viewpoint set in the virtual world is displayed on the game screen. A user character 20 is displayed on the game screen shown in FIG. The user character 20 acts according to the user's operation. Note that the above viewpoint is set based on the position of the user character 20, and the user character 20 is always displayed on the game screen.

  In addition, a client character 22, a resident character 24, and a signboard 26 are displayed on the game screen shown in FIG. The resident character 24 is a game character indicating a resident in the virtual world. The client character 22 is a game character that makes a request to the user character 20. The client character 22 will be described later.

  In the above game, a main story (main game) and a sub story can be played. Here, the “sub story” is not indispensable for clearing the main story, and the user can clear the main story without clearing the sub story. However, by playing the sub story, the user can obtain game items (for example, weapons, armor, tools, or materials) useful for clearing the main story. “Clearing the main story or sub story” means achieving the final goal set in the main story or sub story.

  In the above-described game, upon receiving a request from the client character 22, the user character 20 challenges a mission of searching for and defeating a specific enemy character (boss character). Each mission corresponds to the “sub-story” described above. When the user character 20 defeats the boss character, the purpose of the mission is achieved (that is, the mission is cleared).

  In particular, the game has a function of generating mission data. Specifically, the game has a function of generating mission data based on a combination of a keyword selected by the user and a keyword selected by the client character 22. Hereinafter, the mission generation function will be described.

  Prior to using the mission generation function, the user needs to collect phrases (keywords) related to the mission by playing the main story (or sub-story). For example, when a keyword is output by the display unit 15 or the audio output unit 16, the keyword is obtained by the user.

  For example, the user obtains a keyword by causing the user character 20 to have a conversation with a game character (for example, the resident character 24) in the virtual world. That is, when the resident character 24 who speaks dialogue including a predetermined keyword and the user character 20 have a conversation, the keyword is obtained by the user.

  Further, for example, the user obtains the keyword by causing the user character 20 to check the signboard 26 in the virtual world. That is, when the user character 20 reads the signboard 26 including the predetermined keyword, the keyword is obtained by the user.

  Note that the method for obtaining the keyword is not limited to the above. For example, when the user character 20 reads a book that includes a predetermined keyword, the keyword may be obtained by the user.

  FIG. 3 shows an example of the keyword table. The keyword table shown in FIG. 3 is data indicating a list of keywords available to the user. That is, the keyword table is data indicating a list of phrases set as keywords by the game developer. The keyword table shown in FIG. 3 is also data indicating a list of keywords obtained by the user.

  The keyword table shown in FIG. 3 includes “category”, “keyword”, and “acquisition flag” fields. The “category” field indicates the category to which the keyword belongs. In the present embodiment, a plurality of keywords are grouped into three categories: a first category, a second category, and a third category. The first category is a category to which words such as those used in headline pillows belong. The second category is a category to which words related to places in the virtual world belong. The third category is a category to which words that imply the identity of the boss character belong.

  The “keyword” field indicates a phrase set as a keyword. Note that the keyword includes one having one character, one containing only numbers, one containing only symbols, and the like. The “acquisition flag” field indicates whether or not the user has already acquired the keyword. For example, a value of “0” or “1” is stored in the “acquisition flag” field. A value “0” indicates that the user has not acquired the keyword, and a value “1” indicates that the user has acquired the keyword.

  A user who desires to generate mission data causes the user character 20 to converse with the client character 22. When the user character 20 speaks to the client character 22, a mission generation screen for generating mission data is displayed on the display unit 15. 4-6 is a figure for demonstrating an example of the screen transition of a mission production | generation screen.

  When the user character 20 speaks to the client character 22, a screen as shown in FIG. 4 is displayed. The screen shown in FIG. 4 is a screen for the user to select one of the keywords belonging to the second category. The screen shown in FIG. 4 includes a keyword list field 30. The keyword list column 30 shows a list of keywords belonging to the second category among the keywords obtained by the user. The user selects one of the keywords displayed in the keyword list column 30 by performing a selection operation for selecting any one of the keywords.

  As described above, the second category is a category to which a keyword related to a place in the virtual world belongs. For this reason, selection of a keyword on the screen shown in FIG. 4 corresponds to selection of a place in the virtual world.

  If any keyword is selected on the screen shown in FIG. 4, then a screen as shown in FIG. 5 is displayed. The screen shown in FIG. 5 is a screen for the user to select any of the keywords belonging to the third category. The screen shown in FIG. 5 includes a keyword list field 32 and a selected keyword field 34. The selected keyword column 34 indicates a keyword selected by the user on the screen shown in FIG. On the other hand, the keyword list column 32 shows a list of keywords belonging to the third category among the keywords obtained by the user. The user selects one of the keywords displayed in the keyword list field 32 by performing a selection operation for selecting any one of the keywords.

  As described above, the third category is a category to which a keyword that implies the type of the boss character belongs. Therefore, the selection of the keyword on the screen shown in FIG. 5 corresponds to the selection of the boss character type and the like.

  When any keyword is selected on the screen shown in FIG. 5, a screen as shown in FIG. 6 is displayed. A client character 22 is displayed on the screen shown in FIG. In addition, a balloon 40 indicating the dialogue of the client character 22 is displayed on the screen shown in FIG. The client character 22 selects any one of the keywords belonging to the first category obtained by the user, and a speech about the keyword selected by the client character 22 is displayed in the balloon 40. . In the screen shown in FIG. 6, the dialogue including the keyword “amazing” is displayed in the balloon 40, and in the screen shown in FIG. 6, the keyword “amazing” belonging to the first category is selected by the client character 22. Is shown.

In the present embodiment, mission data is generated based on the combination of the keyword selected by the user on the screen shown in FIGS. 4 and 5 and the keyword selected by the client character 22. FIG. 7 shows an example of mission data. The mission data includes various information related to the mission. For example, the following information is included in the mission data.
(1) Mission name (2) Description (3) Reward rank (4) Number of battles (5) Map type (6) Map rarity (7) Difficulty (8) Boss type (9) Boss rarity

  “Mission name” and “Description” will be described. “Mission name” is the name of the mission, and “Description” is a summary description of the mission. The name of the mission and the outline description are determined based on the combination of keywords selected by the user and the client character 22. In the case of the present embodiment, data (not shown) indicating a correspondence relationship between a combination of keywords, a mission name, and an outline description is stored in the optical disc (or storage unit 12). Then, the mission name and outline description corresponding to the combination of keywords selected by the user and client character 22 are acquired from this data.

  The “reward rank” will be described. In the case of this embodiment, in order to challenge a mission, the user needs to pay a challenge fee in virtual currency (virtual world currency). Further, when the user clears the mission, a reward is given to the user. For example, a reward is given to the user in virtual currency, or a game item (reward item) is given to the user.

  “Reward rank” is information indicating the high challenge fee and good reward. FIG. 8 shows an example of the reward rank table. The reward rank table is data indicating a list of reward ranks. In the present embodiment, the reward rank is represented by “S”, “A”, “B”, “C”, and “D”. “S” indicates that the reward rank is the highest, and “D” indicates that the reward rank is the lowest. The higher the reward rank is, the higher the reward is, and the performance or / and rarity of the reward item is also increased. The higher the reward, the higher the challenge fee. Similarly, the higher the performance or / and rarity of the reward item, the higher the challenge fee.

  Explain the “number of battles”. In the case of the present embodiment, when the number of enemy characters (ordinary enemy characters: enemy characters other than boss characters) that have been exterminated by the user character 20 in the mission reaches a reference number, the boss character in the mission is placed in front of the user character 20. It has come to appear. “Number of battles” means the above-mentioned reference number. That is, the “number of battles” indicates the number of enemy characters that the user character 20 must defeat in order to fight the boss character. For example, when the number of battles is set to “30”, it is not possible to fight a boss character unless 30 normal enemy characters are defeated. On the other hand, when the number of battles is set to “one time”, it is possible to fight against a boss character by exterminating one normal enemy character.

  The “map type” will be described. “Map type” indicates the type of place (map) determined as the stage of the mission. In the case of the present embodiment, a plurality of map data of locations that can become mission stages are prepared in advance by the game developer. FIG. 9 shows an example of the map table. The map table is data indicating a list of a plurality of map data prepared in advance.

  The map table shown in FIG. 9 includes “ID”, “type”, and “map data” fields. The “ID” field indicates identification information for uniquely identifying map data. The “type” field indicates the type of map, and map data is stored in the “map data” field. In the case of the present embodiment, a plurality of map data is prepared for each type. The map data is data necessary for displaying on the game screen a place that can be the stage of the mission. The map data includes, for example, terrain data of a place that can be the stage of the mission, and objects (for example, Data, etc.).

  The “map rarity” will be described. In the case of this embodiment, weapons, armor, tools, etc. are placed in the place where the mission is set, or there are materials used to generate or improve weapons, armor, tools. Yes. Therefore, the user can obtain these game items (weapons, armor, tools, materials, etc.) by challenging the mission. The “map rarity” indicates the rarity of game items that can be obtained by the user character at the place where the mission is set. For example, the larger the numerical value indicating “map rarity”, the higher the rarity. The higher the “map rarity”, the higher the rarity game items can be obtained at the mission stage.

  The “difficulty level” will be described. “Difficulty” indicates the difficulty of the mission. The higher the “difficulty”, the stronger the strength of enemy characters and boss characters that appear in the mission, making it more difficult for the user to clear the mission.

  The “boss type” and “boss rarity” will be described. The “boss type” indicates the type of the boss character of the mission, and the “boss rarity” indicates the rarity of the boss character of the mission. In the case of this embodiment, a plurality of boss characters are prepared in advance by the game developer. FIG. 10 shows an example of a boss character table. The boss character table is data indicating a list of a plurality of boss characters prepared in advance.

  The boss character table shown in FIG. 10 includes “ID”, “kind”, “rareness”, “item”, and “boss character data” fields. The “ID” field indicates identification information for uniquely identifying the boss character. The “type” field indicates the type of the boss character. In the case of this embodiment, a plurality of boss characters are prepared for each type. The “rareness” field indicates the rarity of the boss character. The higher the value in the “rareness” field, the higher the rarity of the boss character. In the case of this embodiment, a plurality of boss characters having different rarity levels are prepared as the same type of boss character.

  The “item” field indicates a game item given to the user when the boss character is exterminated. The higher the rarity level of the boss character is, the higher the performance or / and the rarity game item is given to the user. Boss character data is stored in the “boss character data” field. The boss character data includes, for example, boss character appearance data and parameter data.

  In the case of the present embodiment, the mission data is generated by setting each piece of information included in the mission data based on a combination of keywords selected by the user and the client character 22.

  As described above, in the game apparatus 10, mission data is generated based on the combination of the keyword selected by the user and the keyword selected by the client character 22. For this reason, the game apparatus 10 generates mission data of a type corresponding to the number of keyword combinations. That is, mission data rich in change can be generated.

  When mission data is generated, for example, the screen shown in FIG. 11 is displayed. The screen shown in FIG. 11 is a screen showing an outline of the generated mission data. The screen shown in FIG. 11 includes a name column 50, a description column 52, and a difficulty level column 54 that indicate the name, description, and difficulty level of the mission, respectively. The user can know the outline of mission data by referring to this screen.

  When the user performs a predetermined start operation while the screen shown in FIG. 11 is displayed, a game based on newly generated mission data (that is, a mission) is started, and the user can challenge the mission.

  The generated mission data is stored in the storage unit 12, and the user can play the mission repeatedly. That is, the user can play again a mission that has been cleared in the past.

  FIG. 12 shows an example of a mission table. The mission table is data indicating a list of mission data generated in the past. The mission table shown in FIG. 12 includes “ID”, “name”, “mission data”, and “clear flag” fields.

  The “ID” field indicates identification information for uniquely identifying mission data. The “name” field indicates the mission name. Mission data is stored in the “mission data” field. The “clear flag” field indicates whether or not the user has cleared the mission. For example, a value of “0” or “1” is stored in the “clear flag” field. A value “0” indicates that the user has not cleared the mission, and a value “1” indicates that the user has cleared the mission.

  FIG. 13 shows an example of a mission list screen. The mission list screen is a screen showing a list of mission data stored in the storage unit 12, and is a screen for the user to select one of the mission data stored in the storage unit 12. The mission list screen includes a mission list field 60. The mission list column 60 shows a list of mission names of mission data stored in the storage unit 12. The user selects one of the mission data displayed in the mission list column 60 by performing a selection operation for selecting any one of the mission data.

On the mission list screen, an exclamation mark (!) Is added to the end of the mission name of mission data that satisfies the following two conditions (A) and (B).
(A) Mission data rarity is higher than standard rarity (B) Mission has been cleared in the past

  The “rareness of mission data” is, for example, the rarity of boss characters in the mission. That is, a mission with a high degree of rarity of a boss character is a mission with a high degree of rarity. Note that the reference rarity is set to, for example, the highest rarity “5”.

  On the mission list screen, an exclamation point is added to the mission name of mission data with a high degree of rarity, so that the user can grasp the mission data with a high degree of rarity at a glance. That is, it is possible to grasp at a glance mission data in which a boss character having a high degree of rarity appears.

  Even if mission data has a high degree of rarity, an exclamation mark will not be added to the mission name if the mission has not yet been cleared. If the user knows that the rarity of mission data is high (that is, the appearance of a boss character with a high rarity level) before the mission is cleared, there is a risk that the interest of the game will be impaired. In this regard, the present embodiment is configured as described above so that such inconvenience does not occur.

  When any mission data is selected on the mission list screen, a mission screen (FIG. 11) showing an overview of the mission data is displayed. When the user performs a predetermined start operation while the mission screen is displayed, a game based on the mission data (that is, a mission) is started.

  Next, a configuration for realizing the mission generation function described above will be described. FIG. 14 is a functional block diagram showing functional blocks realized by the game apparatus 10. As shown in FIG. 14, the game apparatus 10 includes a game data storage unit 70, a first keyword acquisition unit 72, a second keyword acquisition unit 74, a game task data generation unit 76, a game execution unit 78, a determination unit 80, A determination unit 82 and a rarity degree presentation unit 84 are included.

  For example, the game data storage unit 70 is realized by an optical disc or the storage unit 12, and other functional blocks are realized by the control unit 11. That is, functional blocks other than the game data storage unit 70 are realized by the control unit 11 executing a program stored in the optical disc or the storage unit 12.

  First, the game data storage unit 70 will be described. The game data storage unit 70 stores data necessary for executing the game. For example, data as shown in FIGS. 3, 7 to 10 and 12 is stored in the game data storage unit 70. In addition to these data, data for generating mission data is also stored in the game data storage unit 70. This point will be described later.

  The first keyword acquisition unit 72 will be described. The first keyword acquisition unit 72 acquires one or a plurality of keywords selected by the user. For example, the first keyword acquisition unit 72 acquires one or a plurality of keywords selected by the user from a plurality of keywords acquired by the user in the game.

  In the present embodiment, the first keyword acquisition unit 72 acquires the keyword selected by the user on the screen shown in FIG. 4 and the keyword selected by the user on the screen shown in FIG. That is, the first keyword acquisition unit 72 includes a keyword selected by the user from the second category keywords acquired by the user, and a keyword selected by the user from the third category keywords acquired by the user. To get.

  The second keyword acquisition unit 74 will be described. The second keyword acquisition unit 74 acquires one or a plurality of keywords selected by the game character in the game. For example, the second keyword acquisition unit 74 acquires one or more keywords selected by the game character from among a plurality of keywords acquired by the user in the game.

  In the present embodiment, the client character 22 corresponds to the “game character” described above. That is, the second keyword acquisition unit 74 acquires a keyword selected by the client character 22 from the first category keywords acquired by the user.

  The game task data generation unit 76 will be described. The game task data generation unit 76 generates game task data for executing a game that aims to clear the game task. For example, the game task data includes at least one of information regarding the content of the game task and information regarding a reward given to the user when the user clears the game task.

  In the case of the present embodiment, the mission data shown in FIG. 7 corresponds to “game task data”. In addition, the purpose of the mission, that is, to search for and kill a boss character corresponds to a “game task”. When the mission purpose is achieved, that is, when the boss character is exterminated, the game task is cleared.

  The game task data generation unit 76 is based on a combination of one or more keywords acquired by the first keyword acquisition unit 72 and one or more keywords acquired by the second keyword acquisition unit 74. Generate mission data.

  In the case of the present embodiment, data necessary for generating mission data is stored in the game data storage unit 70. Specifically, correspondence data regarding correspondence between keywords and information included in mission data is stored in the game data storage unit 70. 15 to 21 show examples of data for generating mission data. Hereinafter, these data will be described.

  FIG. 15 shows an example of data for setting the mission reward rank based on keywords. In the data shown in FIG. 15, the correspondence relationship between the keyword and the reward rank is defined. Specifically, the first category keyword and the reward rank probability information are associated with each other. The reward rank probability information is information indicating the probability that each reward rank is selected as the reward rank of the mission.

  For example, when the keyword “amazing” is selected, one of “S” to “D” is selected as the reward rank of the mission based on the probability information associated with the keyword “amazing”. For example, in the case of the data shown in FIG. 15, the probability of the reward rank “S” is set to “2%” in the probability information associated with the keyword “amazing”. This means that when the keyword “amazing” is selected, the reward rank of the mission is set to “S” with a probability of “2%”.

  Note that the reward rank probability information differs for each keyword. For example, in the probability information associated with the keyword “amazing”, the probability of the reward rank “S” is set to be relatively low, and the probability of the reward rank “D” is set to be relatively high. For this reason, when the keyword “amazing” is selected, it becomes difficult to select “S” as the mission reward rank, and “D” is easily selected. On the other hand, in the probability information associated with the keyword “quake”, the probability of the reward rank “S” is set to be relatively high, and the probability of the reward rank “D” is set to be relatively low. For this reason, when the keyword “quake” is selected, “S” is easily selected as the mission reward rank, and “D” is not easily selected.

  FIG. 16 shows an example of data for setting the number of battles in a mission based on keywords. In the data shown in FIG. 16, the correspondence between the keyword and the number of battles is defined. Specifically, the first category keyword is associated with the probability information of the number of battles. In the case of this embodiment, the number of battles in the mission is set to “1”, “5”, “10”, “20”, or “30”. This is information indicating the probability that the above number of times is selected as the number of battles of the mission.

  For example, when the keyword “amazing” is selected, one of “1”, “5”, “10”, “20”, or “30” is associated with the keyword “amazing” as the number of battles in the mission. Is selected based on the obtained probability information. For example, in the case of the data shown in FIG. 16, the probability of the battle count “1” is set to “8%” in the probability information associated with the keyword “amazing”. This means that when the keyword “amazing” is selected, “1” is selected as the number of battles of the mission with a probability of “8%”.

  Note that the probability information of the number of battles is different for each keyword. For example, in the probability information associated with the keyword “amazing”, the probability of the battle count “1” is set to be relatively low, and the probability of the battle count “30” is set to be relatively high. For this reason, when the keyword “amazing” is selected, it is difficult to select “1” as the number of battles of the mission, and “30” is easily selected. On the other hand, in the probability information associated with the keyword “quake”, the probability of the battle count “1” is set to be relatively high, and the probability of the battle count “30” is set to be relatively low. For this reason, when the keyword “quake” is selected, “1” is easily selected as the number of battles of the mission, and “30” is difficult to select.

  FIG. 17 shows an example of data for setting a mission map type based on keywords. In the data shown in FIG. 17, the correspondence between the keyword and the map type is defined. Specifically, the keyword of the second category is associated with the map type.

  FIG. 18 is an example of data for setting the map rarity of the mission. In the data shown in FIG. 18, the map rarity and the probability information are associated with each other. The probability information indicates the probability of being selected as the map rarity of the mission. In the case of the data shown in FIG. 18, the probability of the map rarity “1” is set to “49%”. This means that the mission map rarity is set to “1” with a probability of “49%”. Note that the higher the numerical value indicating the rarity level of the map, the higher the rarity level of the map. In the case of the data shown in FIG. 18, the higher the map rarity level, the lower the probability, and the mission map rarity level. As a degree, it is difficult to set a high degree of rarity.

  FIG. 19 shows an example of data for setting the difficulty level of a mission based on keywords. In the data shown in FIG. 19, a correspondence relationship between a keyword and a difficulty level is defined. Specifically, the front part (the part from the head to the second character) of the keyword in the third category is associated with the difficulty level.

  The data shown in FIG. 19 also defines the correspondence between the difficulty level and the enemy character level information. In the case of the data shown in FIG. 19, in the level information associated with the difficulty level “1”, the level information of enemy characters other than the boss character is set to “+3”. This indicates that the level of enemy characters other than the boss character is set to a level obtained by adding “3” to the level of the user character 20. In the level information associated with the difficulty level “1”, the level information of the boss character is set to “+5”. This indicates that the level of the boss character is set to a level obtained by adding “5” to the level of the user character 20. Note that the higher the level of the boss character or enemy character, the stronger the boss character or enemy character.

  FIG. 20 shows an example of data for setting the boss character rarity of the mission based on the keyword. In the data shown in FIG. 20, the correspondence between the keyword and the boss character rarity is defined. Specifically, the front part (the part from the top to the second character) of the keyword of the third category is associated with the probability information of the boss character rarity level. In the present embodiment, the boss character rarity level of the mission is set to any one of “1” to “5”, and the probability information of the boss character rarity level is the boss character rarity level. The probability of being selected as the character rarity is shown.

  For example, when a keyword whose front portion (portion from the first character to the second character) is “sleep” is selected, any one of “1” to “5” is set to “sleep” as the boss character rarity of the mission. Is selected based on the probability information associated with "." For example, in the case of the data shown in FIG. 20, in the probability information associated with “sleep”, the probability of the boss character rarity “1” is set to “80%”. This means that when a keyword whose front portion is “sleep” is selected, the boss rarity level of the mission is set to “1” with a probability of “80%”.

  The probability information of the boss character rarity differs for each keyword. For example, in the probability information associated with a keyword whose front portion is “sleep”, the probability of the boss rarity “1” is set to be relatively high, and the probability of the boss rarity “5” is set to be relatively low. Yes. For this reason, when a keyword whose front portion is “sleep” is selected, “1” is easily selected as the boss rarity level of the mission, and “5” is difficult to select.

  On the other hand, in the probability information associated with the keyword whose front portion is “hidden”, the probability of the boss rarity “5” is set higher than that of the keyword whose front portion is “sleep”. For this reason, when a keyword whose front part is “hidden” is selected, “5” is selected as the boss rarity level of the mission compared to the case where a keyword whose front part is “sleep” is selected. It becomes easy to be done.

  FIG. 21 shows an example of data for setting a mission boss type based on a keyword. The data shown in FIG. 21 is data for setting the mission boss type based on the third category keyword. That is, in the data shown in FIG. 21, the correspondence between the rear part of the keyword in the third category (the part from the third character to the end) and the boss type is defined.

  Specifically, in the data shown in FIG. 21, the correspondence between the rear part of the third category keyword, the boss rarity, the map type, and the boss type is defined. For this reason, in this embodiment, the boss type of the mission is determined by the combination of the rear part of the third category keyword, the boss rarity level, and the map type.

  The game task data generation unit 76 refers to the data described above, and converts the information included in the mission data into a combination of keywords acquired by the first keyword acquisition unit 72 and the second keyword acquisition unit 74. Determine based on. Details will be described later (see FIGS. 22 and 23 described later).

  The game execution unit 78 will be described. The game execution unit 78 executes the game based on the game task data generated by the game task data generation unit 76. In the case of this embodiment, the game execution part 78 performs a game based on mission data.

  The determination unit 80 will be described. The determination unit 80 determines whether or not the game task related to the game task data has been cleared by the user. In the present embodiment, the mission data corresponds to “game task data”, and the goal that the user should achieve in the mission (that is, to get rid of the boss character) corresponds to “game task”. For this reason, in this embodiment, when the mission goal is achieved (that is, when the boss character is exterminated), the determination unit 80 determines that the mission has been cleared by the user.

  The determination unit 82 will be described. The determination unit 82 determines whether or not to present information related to the degree of rarity of the game task data to the user based on the determination result of the determination unit 80.

  As described above, in the case of the present embodiment, the mission data corresponds to “game task data”, and the determination unit 82 determines whether or not to present the rarity of the mission data to the user. Determine based on. For example, if the user has cleared the mission data, the determination unit 82 determines to present the rarity of the mission data to the user. On the other hand, when the mission data is not cleared by the user, the determination unit 82 determines not to present the rarity of the mission data to the user.

  The rarity degree presentation unit 84 will be described. The rarity degree presentation unit 84 presents information regarding the degree of rarity of the game task data to the user based on the determination result of the determination unit 82.

  In this embodiment, when the rarity level of mission data is presented to the user, it is determined by the determining unit 82, and when the rarity level of mission data is equal to or higher than the standard rarity level, the rarity level is displayed on the mission list screen (FIG. 13) or the like. The presentation unit 84 displays a mission data display name with an exclamation mark added to the end of the mission name of the mission data.

  On the other hand, when the determination unit 82 determines that the rarity level of mission data is not presented to the user, the rarity level presenting unit 84 displays the mission data display name as it is in the mission list screen (FIG. 13) and the like. Display as. Even when the rarity level of the mission data is less than the reference rarity level, the rarity level presenting unit 84 displays the mission name of the mission data as it is as the display name of the mission data on the mission list screen (FIG. 13) or the like.

  The method of presenting the rarity of mission data to the user is not limited to the method described above. For example, the rarity presentation unit 84 may add a symbol or character other than the exclamation mark to the mission name, or may add a predetermined symbol or character to a position other than the end of the mission name. . In addition, for example, the rarity degree presentation unit 84 sets the mission data information (for example, mission name) whose rarity is equal to or higher than the reference rarity to a different aspect (for example, color) from the information of mission data whose rarity is not equal to or higher than the standard rarity level. You may make it display with. Further, for example, the rarity degree presentation unit 84 may display a predetermined symbol, an image, or the like in association with mission data whose rarity is equal to or higher than the reference rarity degree. Further, for example, the rarity degree presentation unit 84 may display a numerical value, symbol, or image indicating the rarity in association with the mission data. In this case, regardless of whether the rarity is equal to or higher than the reference rarity, the rarity presentation unit 84 may display a numerical value indicating the rarity in association with the mission data.

  Next, processing executed by the game apparatus 10 will be described. 22 and 23 are flowcharts showing an example of processing for generating mission data. The processing shown in FIGS. 22 and 23 is executed when, for example, the user character 20 speaks to the client character 22. The control unit 11 executes the processing shown in FIGS. 22 and 23 according to the program stored in the optical disc or the storage unit 12, so that the control unit 11 has the first keyword acquisition unit 72, the second keyword acquisition unit 74, And it comes to function as the game task data generation part 76.

  When generating mission data, first, the control unit 11 (second keyword acquisition unit 74) randomly selects one of the keywords of the first category obtained by the user (S101). The keyword selected in step S101 is the keyword selected by the client character 22.

  Thereafter, the control unit 11 (game assignment data generation unit 76) determines the reward rank of the mission based on the keyword selected in step S101 (S102). That is, the control unit 11 refers to the data shown in FIG. 15 and acquires probability information associated with the keyword selected in step S101. Then, the control unit 11 determines any one of “S” to “D” as the reward rank of the mission based on the probability information.

  Further, the control unit 11 (game task data generation unit 76) determines the number of battles of the mission based on the keyword selected in step S101 (S103). That is, the control unit 11 refers to the data shown in FIG. 16 and acquires probability information associated with the keyword selected in step S101. Based on the probability information, the control unit 11 determines any one of “1”, “5”, “10”, “20”, or “30” as the number of battles of the mission.

  Thereafter, the control unit 11 displays a screen (FIG. 4) for selecting any one of the second category keywords on the display unit 15 (S104). Then, the control unit 11 monitors whether the keyword selection is completed (S105). When the keyword selection is completed, the control unit 11 (first keyword acquisition unit 72) acquires the keyword selected by the user (S106).

  Then, the control unit 11 (game assignment data generation unit 76) determines the map type and map rarity of the mission based on the keyword acquired in step S106 (S107). That is, the control unit 11 refers to the data shown in FIG. 17 and determines the map type associated with the keyword acquired in step S106 as the map type of the mission. Further, the control unit 11 determines any one of “1” to “5” as the map rarity of the mission according to the probability based on the data shown in FIG.

  Thereafter, as shown in FIG. 23, the control unit 11 displays a screen (FIG. 5) for selecting any one of the third category keywords on the display unit 15 (S108). Then, the control unit 11 monitors whether the keyword selection is completed (S109). When the keyword selection is completed, the control unit 11 (first keyword acquisition unit 72) acquires the keyword selected by the user (S110).

  And the control part 11 (game task data generation part 76) determines the difficulty of a mission based on the keyword acquired by step S110 (S111). That is, the control unit 11 refers to the data shown in FIG. 19 and determines the difficulty level associated with the front part (the part from the top to the second character) of the keyword acquired in step S110 as the difficulty level of the mission. To do.

  Further, the control unit 11 (game assignment data generation unit 76) determines the boss rarity level of the mission based on the keyword acquired in step S110 (S112). That is, the control unit 11 refers to the data shown in FIG. 20, and acquires probability information associated with the front portion (portion from the top to the second character) of the keyword acquired in step S110. Then, the control unit 11 determines any one of “1” to “5” as the boss rarity level of the mission based on the probability information.

  Further, the control unit 11 (game assignment data generation unit 76) determines the mission boss type based on the keyword acquired in step S110 (S113). That is, the control unit 11 refers to the data shown in FIG. And the control part 11 is the back part (part from the 3rd character to the end) of the keyword acquired at step S110, the boss rarity determined at step S112, and the map type determined at step S107. The boss type associated with the combination is determined as the mission boss type.

  Thereafter, the control unit 11 stores the mission data in the storage unit 12 (S114). That is, mission data including each information determined in steps S102, S103, S107, S111 to S113 is registered in the mission table. Further, the control unit 11 displays a mission screen (FIG. 11) on the display unit 15 (S115). This is the end of the description of the processing of FIG. 22 and FIG.

  FIG. 24 is a flowchart showing an example of processing for displaying the mission list screen. The control unit 11 executes the processing shown in FIG. 24 according to the program stored in the optical disc or the storage unit 12 so that the control unit 11 functions as the determination unit 80, the determination unit 82, and the rarity degree presentation unit 84. Become.

  When displaying the mission list screen, the control unit 11 initializes the variable i to “1” (S201). Thereafter, the control unit 11 acquires the mission name of the i-th mission data from the mission table (FIG. 12) (S202).

  Further, the control unit 11 (determination unit 80) determines whether or not the i-th mission data has been cleared by the user (S203). When it is determined that the i-th mission data has been cleared by the user, the control unit 11 determines whether the rarity of the i-th mission data is greater than or equal to the reference rarity (S204). ). For example, the control unit 11 determines whether or not the boss rarity of the i-th mission data is “5” or more.

  If it is determined that the rarity of the i-th mission data is greater than or equal to the reference rarity, the control unit 11 (rareness presentation unit 84) adds an exclamation mark to the end of the mission name of the i-th mission data. This is set as the display name of the i-th mission data (S205).

  On the other hand, when it is determined that the rarity of the i-th mission data is less than the reference rarity, the control unit 11 (rareness presentation unit 84) directly uses the i-th mission data as the i-th mission data. Is set as the display name of the mission data (S206). Also, when it is determined in step S203 that the i-th mission data has not been cleared by the user, the control unit 11 (rareness presentation unit 84) uses the mission name of the i-th mission data as it is. It is set as the display name of the i-th mission data (S206).

  After the processing of step S205 or S206 is executed, the control unit 11 adds 1 to the value of the variable i (S207), and the value of the variable i is greater than the number (N) of mission data registered in the mission table. It is determined whether it is larger (S208). If the value of the variable i is not greater than N, the control unit 11 re-executes the process of step S202.

  On the other hand, when the value of the variable i is larger than N, the control unit 11 displays the mission list screen (FIG. 13) on the display unit 15 (S209). In this case, the display name of each mission set in step S205 or S206 is displayed in the mission list field 60 of the mission list screen. This is the end of the description of the processing illustrated in FIG.

  According to the game device 10 described above, mission data is generated based on the combination of the keyword selected by the user and the keyword selected by the game character (client character 22). According to the game apparatus 10, mission data of a type corresponding to the number of keyword combinations is generated. That is, according to the game apparatus 10, mission data rich in change can be generated.

  Further, in the game apparatus 10, mission data is generated not only based on the keyword selected by the user, but also based on the keyword selected by the game character (client character 22). According to the game device 10, even if the user repeatedly selects the same keyword, it is difficult to generate the same mission data.

  Further, in the game apparatus 10, the keywords that can be selected by the user and the game character (client character 22) are limited to the keywords obtained by the user in the game. According to the game device 10, it is possible to give the user the pleasure of collecting keywords.

  Further, in the game apparatus 10, an exclamation mark is added to the mission name of mission data with a high degree of rarity on the mission list screen. According to the game apparatus 10, it is possible to assist the user so that the user can grasp the mission data having a high rarity at a glance. In other words, it is possible to assist the user so that the user can grasp at a glance mission data such that a boss character having a high degree of rarity appears.

  Even if mission data has a high degree of rarity, no exclamation mark is added to the mission name if the mission has not yet been cleared. If the user knows that the rarity of mission data is high (that is, the appearance of a boss character with a high rarity level) before the mission is cleared, there is a risk that the interest of the game will be impaired. In this regard, the game apparatus 10 is designed to prevent such inconvenience.

  The present invention is not limited to the embodiment described above.

  (1) In the embodiment described above, the keywords that the user can select are limited to the keywords that the user has acquired in the game (main story or sub story), but the keywords that the user can select are You may make it not limit to the keyword acquired by the game. For example, on the screen shown in FIG. 4, keywords may be selected from all keywords belonging to the second category. In the screen shown in FIG. 5, keywords may be selected from all keywords belonging to the third category.

  In the embodiment described above, the keywords that can be selected by the client character 22 are limited to the keywords that the user has acquired in the game (main story or substory), but the client character 22 can be selected. The keyword may not be limited to the keyword acquired by the user in the game. For example, the client character 22 may select a keyword from all keywords belonging to the first category.

  (2) The first keyword acquisition unit 72, the second keyword acquisition unit 74, and the game task data generation unit 76 may be realized in a device different from the game device 10 that executes the game.

  For example, the present invention can also be applied to a game system including a game device 10 and a server device that can communicate with the game device 10. In this case, the first keyword acquisition unit 72, the second keyword acquisition unit 74, and the game task data generation unit 76 may be realized in a server device (game task data generation device). That is, the control unit of the server device executes the program so that the control unit of the server device functions as the first keyword acquisition unit 72, the second keyword acquisition unit 74, and the game task data generation unit 76. Also good.

  In this case, information indicating the keyword selected by the user on the screens shown in FIGS. 4 and 5 may be transmitted from the game apparatus 10 to the server apparatus. Data necessary for generating game task data may be stored in the storage unit of the server device or another server device accessible from the server device. Furthermore, the game task data generated in the server device may be transmitted from the server device to the game device 10.

  (3) The determination unit 80, the determination unit 82, and the rarity degree presentation unit 84 are not essential components, and these functional blocks may be omitted.

  (4) Even in the game device 10 that executes a game that does not have a function of generating game task data, the determination unit 80, the determination unit 82, and the rarity degree presentation unit 84 can be realized. That is, even when mission data generated in advance by the game developer is stored in the optical disc (or storage unit 12), the determination unit 80, the determination unit 82, and the rarity degree presentation unit 84 can be realized. Is possible. That is, it is possible to employ a configuration in which the first keyword acquisition unit 72, the second keyword acquisition unit 74, and the game task data generation unit 76 are omitted.

  (5) The present invention can be applied to a game other than a game in which a user character adventures in a virtual world. The present invention can be applied to a game in which a user aims to clear a game task.

  DESCRIPTION OF SYMBOLS 10 Game device, 11 Control part, 12 Storage part, 13 Optical disk drive part 13, 14 Communication part, 15 Display part, 16 Voice output part, 17 Operation part, 20 User character, 22 Client character, 24 Resident character, 26 Signboard , 30, 32 Keyword list field, 34 Selected keyword field, 40 Speech balloon, 50 Name field, 52 Description field, 54 Difficulty level field, 60 Mission list field, 70 Game data storage unit, 72 First keyword acquisition unit, 74 2nd keyword acquisition part, 76 game task data generation part, 78 game execution part, 80 determination part, 82 determination part, 84 rarity degree presentation part.

Claims (13)

In a game device that executes a game that a user aims to clear a game task based on game task data,
First acquisition means for acquiring one or more keywords selected by the user;
Second acquisition means for acquiring one or more keywords selected by the game character in the game;
Generating means for generating the game task data based on a combination of one or more keywords acquired by the first acquiring means and one or more keywords acquired by the second acquiring means; ,
A game apparatus comprising: The game device according to claim 1,
The game task data includes information on at least one of the game task and a reward given to the user when the user clears the game task,
The generating means refers to the correspondence data relating to the correspondence relation between the keyword and the information, thereby obtaining the information by one or more keywords acquired by the first acquisition means and the second acquisition means. Set based on the combination of one or more keywords acquired by
A game device characterized by that. The game device according to claim 1 or 2,
Determining means for determining whether or not a game task related to the game task data has been cleared by the user;
Determining means for determining whether or not to present information regarding the degree of rarity of the game task data to the user based on a determination result of the determining means;
Presenting means for presenting the information on the degree of rarity of the game task data to the user based on a determination result of the determining means;
A game apparatus comprising: The game device according to any one of claims 1 to 3,
The game device, wherein the first acquisition means acquires one or a plurality of keywords selected by the user from a plurality of keywords acquired by the user in the game. The game device according to claim 4,
The game apparatus, wherein the second acquisition means acquires one or a plurality of keywords selected by the game character from the plurality of keywords acquired by the user in the game. In a game system that executes a game in which a user aims to clear a game task,
First acquisition means for acquiring one or more keywords selected by the user;
Second acquisition means for acquiring one or more keywords selected by the game character in the game;
Generating means for generating game task data based on a combination of one or more keywords acquired by the first acquiring means and one or more keywords acquired by the second acquiring means;
Execution means for executing the game based on the game task data;
A game system comprising: In a game task data generation device for generating game task data for executing a game in which a user aims to clear a game task,
First acquisition means for acquiring one or more keywords selected by the user;
Second acquisition means for acquiring one or more keywords selected by the game character in the game;
Generating means for generating the game task data based on a combination of one or more keywords acquired by the first acquiring means and one or more keywords acquired by the second acquiring means; ,
A game task data generation device comprising: A first acquisition step of acquiring one or more keywords selected by a user playing a game that aims to clear a game task;
A second acquisition step of acquiring one or more keywords selected by the game character in the game;
The game task data for executing the game is based on a combination of one or more keywords acquired in the first acquisition step and one or more keywords acquired in the second acquisition step. Generating step to generate,
A game task data generation method comprising: First acquisition means for acquiring one or more keywords selected by a user who plays a game that aims to clear a game task;
Second acquisition means for acquiring one or more keywords selected by the game character in the game; and
The game task data for executing the game is based on a combination of one or more keywords acquired by the first acquisition unit and one or more keywords acquired by the second acquisition unit. Generating means for generating
As a program to make the computer function as. In a game device that executes a game that a user aims to clear a game task based on game task data,
Determining means for determining whether or not a game task related to the game task data has been cleared by the user;
Determining means for determining whether or not to present to the user information regarding the degree of rarity of the game task data based on a determination result of the determining means;
Presenting means for presenting the information on the degree of rarity of the game task data to the user based on a determination result of the determining means;
A game apparatus comprising: In a game system that executes a game in which a user aims to clear a game task,
Execution means for executing the game based on game task data;
Determining means for determining whether or not a game task related to the game task data has been cleared by the user;
Determining means for determining whether or not to present to the user information regarding the degree of rarity of the game task data based on a determination result of the determining means;
Presenting means for presenting the information on the degree of rarity of the game task data to the user based on a determination result of the determining means;
A game system comprising: A determination step for determining whether or not the game task related to the game task data is cleared by the user in a game that is executed based on the game task data and the user aims to clear the game task;
A determination step of determining whether or not to present information regarding the degree of rarity of the game task data to the user based on a determination result in the determination step;
A presenting step of presenting the information related to the degree of rarity of the game task data to the user based on a determination result in the determining step;
A game control method comprising: A determination unit configured to determine whether or not the game task related to the game task data is cleared by the user in a game that is executed based on the game task data and the user aims to clear the game task;
Determining means for determining whether or not to present to the user information regarding the degree of rarity of the game task data based on a determination result of the determining means; and
Presenting means for presenting the information on the degree of rarity of the game task data to the user based on the determination result of the determining means;
As a program to make the computer function as.

Images