JP7467102B2 - Game program, game processing method, and information processing device - Google Patents

Description

The present invention relates to a game program, a game processing method, and an information processing device.

There are known games in which a player can create another item by synthesizing multiple items based on a recipe (see, for example, Patent Document 1).

JP 2007-111319 A

For example, in so-called online games where multiple players play the game over a network, if each player were to explore new recipes through trial and error, this could lead to more revitalization of the game. However, in the above-mentioned conventional technology games, recipe information is presented when a request for analysis of item materials is received from a player, so the game system is not one that allows players to explore new recipes. For this reason, there was an issue that even if this technology was applied to online games, it would not lead to more revitalization of the game.

The present invention was made in consideration of these problems, and aims to provide a game program, a game processing method, and an information processing device that can revitalize online games by encouraging players to explore new recipes for using multiple game elements to generate other game elements.

To achieve the above object, the game program of the present invention causes an information processing device to function as a recipe success/failure determination processing unit that receives a recipe including a combination of multiple game elements and determines whether or not another game element can be generated using the recipe, a recipe identity determination processing unit that determines whether or not the received recipe is identical to any of the recipes registered in association with the rights holder player in the registration unit if the other game element can be generated, and a recipe registration processing unit that registers at least one of the received recipe or the rights holder player who transmitted the recipe in the registration unit if the received recipe is not identical to any of the registered recipes.

To achieve the above object, the game processing method of the present invention is a game processing method executed by an information processing device, and includes the steps of: accepting a recipe including a combination of multiple game elements, and determining whether or not another game element can be generated using the recipe; if the other game element can be generated, determining whether or not the accepted recipe is identical to any of the recipes registered in association with the rights holder player in a registration unit; and if the accepted recipe is not identical to any of the registered recipes, registering at least one of the accepted recipe or the rights holder player who transmitted the recipe in the registration unit.

To achieve the above object, the information processing device of the present invention has a recipe success/failure determination processing unit that receives a recipe including a combination of multiple game elements and determines whether or not another game element can be generated using the recipe, a recipe identity determination processing unit that determines whether or not the received recipe is identical to any of the recipes registered in association with the rights holder player in a registration unit when the other game element can be generated, and a recipe registration processing unit that registers at least one of the received recipe or the rights holder player who transmitted the recipe in the registration unit when the received recipe is not identical to any of the registered recipes.

The game program of the present invention can liven up online games by encouraging players to explore ways to use multiple game elements to generate other game elements.

1 is a system configuration diagram illustrating an example of the overall configuration of a game system according to an embodiment. FIG. 2 is a block diagram illustrating an example of a functional configuration of a server device. FIG. 13 is a diagram illustrating an example of a recipe creation screen. FIG. 13 is a diagram illustrating an example of an item list screen. FIG. 13 is a diagram illustrating an example of a status list screen. FIG. 13 is a diagram illustrating an example of an input operation screen. FIG. 13 is a diagram illustrating an example of a keyboard screen. FIG. 13 is a diagram illustrating an example of a recipe success screen. FIG. 13 is a diagram illustrating an example of a recipe failure screen. FIG. 13 is a diagram illustrating an example of a recipe registration screen. FIG. 13 is a diagram illustrating an example of a recipe rejection screen. FIG. 13 is a diagram illustrating an example of a registered recipe list screen. FIG. 13 is a diagram illustrating an example of a registered recipe viewing screen. FIG. 13 is a diagram illustrating an example of a screen for designating a prohibited target. 13 is a diagram illustrating an example of a registered recipe list screen when there is a viewing restriction. FIG. 13 is a diagram illustrating an example of a viewing prohibition screen. FIG. 13 is a diagram illustrating an example of a usage prohibition screen. FIG. 13 is a diagram illustrating an example of a reward acquisition screen. FIG. 13 is a diagram illustrating an example of a period lapse notification screen. 10 is a flowchart illustrating an example of a processing procedure executed by a CPU of the server device. FIG. 13 is a block diagram illustrating an example of a functional configuration of a server device in a modified example that accepts a request to register a recipe. FIG. 13 is a diagram showing an example of a recipe success screen in a modified example for accepting a request to register a recipe. 13 is a flowchart illustrating an example of a processing procedure executed by a CPU of the server device in a modified example for accepting a request for registering a recipe. FIG. 13 is a block diagram illustrating an example of the functional configuration of a server device in a modified example in which registered recipes can be viewed and used by a player who has purchased the recipes. FIG. 13 is a diagram illustrating an example of a sales screen for a registered recipe. FIG. 13 is a diagram illustrating an example of a purchase screen for a registered recipe. 13 is a flowchart illustrating an example of a processing procedure executed by a CPU of the server device in a modified example in which a registered recipe can be viewed and used by a player who has purchased the recipe. FIG. 13 is a block diagram illustrating an example of a functional configuration of a server device in a modified example in which the use of a registered recipe is permitted. FIG. 13 is a diagram illustrating an example of a license target designation screen. FIG. 13 is a diagram illustrating an example of a viewing prohibition screen. FIG. 13 is a diagram illustrating an example of a usage prohibition screen. FIG. 13 is a diagram illustrating an example of a period lapse notification screen. 13 is a flowchart illustrating an example of a processing procedure executed by a CPU of the server device in a modified example in which use of a registered recipe is permitted. FIG. 2 is a block diagram illustrating an example of a hardware configuration of an information processing device.

One embodiment of the present invention will be described below with reference to the drawings.

<1. Overall structure of the game system>
First, an example of the overall configuration of a game system 1 according to this embodiment will be described with reference to Fig. 1. As shown in Fig. 1, the game system 1 has a plurality of terminal devices 3 (three are illustrated in Fig. 1) operated by a plurality of players, and a server device 5. Each terminal device 3 and the server device 5 are communicatively connected via a network NW such as a LAN or the Internet. The network NW may be either wireless or wired. Although Fig. 1 illustrates a case in which the server device 5 is configured from a single computer, it may be configured from a plurality of computers.

The terminal device 3 is, for example, a smartphone, a tablet computer, a portable game machine, a mobile phone, etc. However, it is not limited to these, and may be, for example, a desktop computer, a notebook computer, a stationary game machine, etc. The terminal device 3 has a touch panel 7 on which various displays and various input operations by the player are performed. The player performs input operations by touching the touch panel 7 with a finger, a pen, etc. Note that the terminal device 3 may have input units such as buttons, switches, levers, joysticks, etc. in addition to the touch panel 7. It may also have an audio output unit such as a speaker.

The server device 5 (an example of an information processing device) is a so-called server computer. The server device 5 accepts access via the network NW from the terminal device 3 of each player who receives the game service, stores and manages the game information of each player in a recording device, and provides each player with an online game service via the network NW.

In one form of providing game services by the server device 5, a game program (also called application software) is implemented in the server device 5, and the game is not executed on the terminal device 3, but rather the server device 5 executes the game in response to the player's operation input on the terminal device 3, and transmits the execution results to the terminal device 3 of each player. For example, the server device 5 may provide a so-called browser game in which the game can be played using a web browser installed on the terminal device 3 of each player. The server device 5 may also provide a so-called cloud game in which game images resulting from the execution of the game on the server device 5 are transmitted to the terminal device 3 in, for example, a streaming format. Alternatively, the server device 5 may provide a so-called social game that is executed by application software created based on an operating environment such as an API (application programming interface) that operates on a web browser in an SNS (social networking service). Note that a part of the game program may be installed on the terminal device 3, and game processing may be partially executed not only on the server device 5 but also on the terminal device 3.

2. Functional configuration of the server device
Next, an example of the functional configuration of the server device 5 will be described with reference to FIG.

As shown in FIG. 2, the server device 5 has a recipe database 9, a recipe success/failure determination processing unit 11, a recipe identity determination processing unit 13, a recipe registration processing unit 15, a recipe publication processing unit 17, a first reward granting processing unit 19, a prohibition designation reception processing unit 21, and a use prohibition processing unit 23.

In the recipe database 9 (an example of a registration unit), recipes are registered in association with the rights holder player. A "recipe" is information that indicates a method for generating another game element using multiple game elements, and includes information such as the type and quantity of multiple game elements to be combined. It may also include other information such as the ratio and order of combinations, and if a specific process (such as processing) is required for the combination, the method of that process. In addition, a "rights holder player" is a player who first discovers and registers a recipe, and is the player who owns the registered recipe.

The game according to this embodiment is a game in which the player enjoys searching for new recipes through trial and error and ingenuity. The search for recipes may be executed as a standalone game, or may be executed in other types of games, such as role-playing games, simulation games, action games, etc. Each time a new recipe is discovered, the new recipe is associated with the identification information of the rights holder player who first discovered the recipe, and the associated information is registered and stored in the recipe database 9. Note that a certain number of recipes may be registered in advance as an initial setting.

The recipe success/failure determination processing unit 11 receives a recipe including a combination of multiple game elements from the terminal device 3, and determines whether or not another game element can be generated using the recipe. "Game elements" include tangible game elements such as items, as well as intangible game elements such as status, input operations, input information, virtual currency, location, time, attributes, etc.

Items include, for example, weapons, armor, equipment, decorations, accessories, tools, instruments, devices, medicines, food and drink, and other items with various effects. They also include living things such as harvested plants and captured animals. They also include special effects that can be given to these items (for example, enchantment effects, attribute effects, skills, etc. that have been turned into items), and characters (including character cards) that can be used to form parties or play cooperatively.

Status is information that represents the state of the player (including the character controlled by the player) performing the generation, and includes, for example, stamina, magic, intelligence, speed, attack power, defense power, experience points, prestige points, luck, and skills. Magic may include attribute elements such as fire, water, wind, ice, lightning, light, and darkness. When combining statuses, a specified amount is consumed.

The input operation includes, for example, operation information of directional keys and buttons displayed on the touch panel 7. The operation information may include, for example, not only the type of key or button to be operated, but also the timing of operation (operation simultaneously, operation in sequence, etc.). Note that the operation information may not be that of keys or buttons displayed on the touch panel 7, but that of actual keys and buttons. The input operation also includes, for example, handwritten input information of figures and characters by dragging on the touch panel 7.

The input information includes, for example, information such as letters, numbers, and symbols input using a keyboard displayed on the touch panel 7. Note that input may be made using an actual keyboard instead of a keyboard displayed on the touch panel 7.

Virtual currencies include those that are issued for a fee and those that are issued free of charge. Those that are issued for a fee are acquired by the player by purchasing them and paying a fee. Those that are issued free of charge are acquired by performing specific in-game actions, such as defeating enemy characters. They also include those that are distributed free of charge as part of campaigns, events, logging in, etc. Players can use (consume) virtual currency to purchase items within the game or platform, play lottery games (gacha), and perform various other game-related tasks. When combining virtual currencies, a specified amount is consumed.

The location includes information about the location within the game where the player (the character operated by the player) generates game elements. The location information includes information about the terrain, such as grasslands, deserts, rivers, mountains, oceans, forests, snow fields, etc. It may also include information related to the progress of the game, such as stages, levels, chapters, and chapters. It may also include information about the actual location of the player, obtained, for example, by GPS, rather than a virtual location within the game.

The time period includes time information within the game when the player (the character operated by the player) generates the game elements. The time information includes, for example, the time of day, the date, the season, etc. It may also include real time information rather than a virtual time within the game.

The attributes include in-game attribute information of the player (character operated by the player) who generates the game elements. Attribute information includes, for example, occupation, race, sex, age, place of residence, attribute elements (fire, water, wind, ice, lightning, light, darkness, etc.), etc. Also, it may include the player's real-life attribute information, rather than virtual attributes within the game.

In this embodiment, the player inputs the contents of the above-mentioned game elements, such as items, status, input operations, input information, and virtual currency, on the recipe creation screen (see FIG. 3). However, for example, the player only selects whether or not to include location, time, and attributes in the recipe, and the contents are automatically acquired by the terminal device 3. The player may also input the contents of location, time, and attributes.

The recipe success/failure determination processing unit 11 may determine the success/failure of a recipe by using a method other than the above. Specifically, the following methods may be considered. For example, the generation patterns of all game elements may be recorded in advance as a table, and if the generation patterns match, the game element may be determined as a success, and if they do not match, the game element may be determined as a failure. For example, all game elements may be assigned a numerical value (which may be within a predetermined numerical range), and if the numerical value calculated by a predetermined calculation (e.g., multiplication, etc.) based on the numerical value of the game element to be combined matches the numerical value of another game element, the game element may be determined as a success, and if they do not match, the game element may be determined as a failure. In this case, a numerical value or a numerical range corresponding to failure may be set. For example, the type of game element to be generated and the success or failure of generation may be determined by a determination process including random elements. In this case, when registering a recipe as a successful recipe in the recipe database 9, the random elements may be erased to confirm the recipe, thereby ensuring reproducibility.

When the recipe success/failure determination processing unit 11 determines that another game element has been generated, the recipe identity determination processing unit 13 determines whether the recipe received from the terminal device 3 is identical to any of the recipes registered in the recipe database 9 in association with the rights holder player. Here, they are determined to be identical when the types and number of the combined game elements are completely identical, and are determined not to be identical when, for example, even if the product is the same, the types and number of the combined game elements are even partially different. For ease of explanation, below, recipes registered in the recipe database 9 are also referred to as "registered recipes".

When a recipe received from the terminal device 3 is not identical to any of the recipes registered in the recipe database 9, the recipe registration processing unit 15 registers the received recipe in the recipe database 9 in association with the identification information of the rights holder player who sent the recipe. This causes new recipes that do not match the registered recipes to be sequentially accumulated in the recipe database 9. The identification information includes, for example, account information and the name of the avatar or character operated by the player.

As mentioned above, all game element generation patterns are prepared in advance as a table, and if the generation pattern table is, for example, common to the recipe database 9, recipes that have not been discovered by the player will be in a state where the rights holder player is not registered. In this case, the recipe identity determination processing unit 13 determines whether the recipe received from the terminal device 3 is identical to any of the recipes registered in the recipe database 9 together with the rights holder player, and if it is not identical to any of the recipes, the recipe registration processing unit 15 performs processing to register the rights holder player to the data of that recipe.

The recipe disclosure processing unit 17 discloses the contents of a recipe registered in the recipe database 9 so that it can be viewed by multiple players. When a player, etc. who is prohibited from using a registered recipe is designated by the prohibition designation reception processing unit 21 described below, the recipe disclosure processing unit 17 restricts the designated player, etc. from viewing the contents of the registered recipe. In other words, the recipe disclosure processing unit 17 discloses the contents of the registered recipe so that it can be viewed by players, etc. other than the designated player, etc.

The first reward granting processing unit 19 grants a reward to the rights holder player when a recipe registered in the recipe database 9 is used by a player other than the rights holder player. The reward may be granted in the form of virtual currency, for example, or an item other than virtual currency. The reward may be granted in the form of a fixed amount each time the recipe is used by another player, for example, or the number of times the recipe is used within a certain period of time (e.g., one day, one week, etc.) may be tallied and an amount according to the number of times may be granted.

The first reward granting processing unit 19 stops granting rewards to the rights holder player when a predetermined period of time has passed since the registered recipe was registered in the recipe database 9. The "predetermined period" may be, for example, a period of real time (e.g., one week, ten days, one month, six months, one year, etc.) or a period of virtual time within the game. Alternatively, instead of a period of time, it may be set as, for example, the period until the registered recipe is used a certain number of times.

The prohibition designation reception processing unit 21 receives designations of specific players or specific groups who are prohibited from using a registered recipe from the rights holder player who owns the registered recipe. A "group" includes, for example, a group of multiple players in an MMORPG (Massively Multiplayer Online Role-Playing Game) or an MMO simulation game, in which the group fights against another group. It may also include a gathering or facility (such as a guild) formed for multiple players to interact and exchange information.

The prohibition processing unit 23 prohibits a specific player or specific group (hereinafter referred to as "prohibited players, etc." as appropriate) accepted by the prohibition designation acceptance processing unit 21 from using a registered recipe. As mentioned above, the recipe disclosure processing unit 17 restricts the prohibited players, etc. from viewing the contents of a registered recipe. However, even if a player cannot view the contents of a recipe within the game, there is a possibility that the player may obtain the contents of the recipe from, for example, an information site on the Internet, SNS, or other information media. Therefore, the prohibition processing unit 23 determines the identification information of a prohibited player, etc. when the player, etc. attempts to generate a game element, and if the player, etc., corresponds to a prohibited player, etc., causes the generation to fail, thereby prohibiting the use of the registered recipe.

The use prohibition processing unit 23 lifts the prohibition on use by the prohibited player, etc., when a predetermined period of time has passed since the registered recipe was registered in the recipe database 9. The "predetermined period" may be, for example, a period of real time (e.g., one week, ten days, one month, six months, one year, etc.) or a period of virtual time within the game. Alternatively, instead of a period of time, it may be set as, for example, the period until the registered recipe is used a certain number of times.

Similarly, the recipe disclosure processing unit 17 lifts the viewing restrictions for prohibited players, etc. when a predetermined period of time has passed since the registered recipe was registered in the recipe database 9.

The processing in each processing unit described above is not limited to these examples of division of processing, and may be performed by a smaller number of processing units (e.g., one processing unit), or may be performed by a further subdivided processing unit. The functions of each processing unit described above are implemented by a game program executed by the CPU 501 (see FIG. 34), which will be described later, but some of them may be implemented by actual devices such as dedicated integrated circuits such as ASICs and FPGAs, or other electrical circuits. Furthermore, the processing units described above are not limited to being implemented in their entirety on the server device 5 side, and some or all of them may be implemented on the terminal device 3 side.

<3. Game screen>
Next, an example of a game screen according to this embodiment will be described with reference to FIG. 3 to FIG.

Figure 3 shows an example of a recipe creation screen. The recipe creation screen is a screen for creating a recipe by selecting game elements to be combined and for executing the created recipe. Note that "executing the created recipe" here refers to attempting to generate another game element using a combination of multiple input game elements. In the example shown in Figure 3, the recipe creation screen displays an element input section 25, and a "Yes" button 27 and a "No" button 29 for indicating whether or not to execute the recipe.

Check boxes 31 for selecting game elements to be combined are displayed for each game element in the element input section 25. By operating the check boxes 31, the player can select the desired game element from, for example, item, status, input operation, input information, virtual currency, location, time, and attribute. In the example shown in FIG. 3, item, status, and input operation are selected.

The element input section 25 also displays a button 33 for selecting an item from an item list. When the button 33 is operated, an item list (see FIG. 4) is displayed, and the contents of an item selected in the item list are displayed in the item contents display section 35. In the example shown in FIG. 3, it is possible to select up to two items, and for example, one item A is selected. Note that the maximum number of items is not limited to two, and may be, for example, one or three or more.

The element input section 25 also displays a button 37 for selecting a status from a status list. When the button 37 is operated, the status list (see FIG. 5) is displayed, and the content of the status selected in the status list is displayed in the status content display section 39. In the example shown in FIG. 3, it is possible to select one type of status, and it is displayed that five points of magic power will be consumed. Note that it may be possible to select multiple types of status.

In addition, the element input section 25 displays buttons 41 for performing input operations. When the buttons 41 are operated, an input operation screen (see FIG. 6) is displayed, and the contents of the input operation on the input operation screen are displayed in the input content display section 43. In the example shown in FIG. 3, it is displayed that four input operations have been performed in the order of the up arrow key, down arrow key, X button, and Y button. Note that the number of input operations may be other than four, and may also include simultaneous operation of multiple keys or buttons.

In addition, the element input section 25 displays buttons 45 for inputting information. When the button 45 is operated, a keyboard (see FIG. 7) is displayed, and information such as letters, numbers, and symbols input on the keyboard is displayed in the input content display section 47.

The element input section 25 also displays a display section 49 that displays the current amount of virtual currency held (1250G in this example), and an input section 51 for inputting the amount of virtual currency used (consumption). The input section 51 is configured, for example, as a pull-down menu, and allows the amount of use to be selected in preset units (for example, 50G, 100G, 150G, ...). However, other input methods (for example, display of a separate input window, a numeric input box using up-down buttons or the like, a slide bar, etc.) may also be used.

For the location, time, and attributes, only check boxes 31 are displayed, and as described above, the player selects whether or not to include them in the recipe. The details of the location, time, and attributes are automatically obtained by the terminal device 3.

If the player operates the "Yes" button 27, the recipe inputted via the element input unit 25 is executed. On the other hand, if the player operates the "No" button 29, the execution of the recipe is cancelled.

Figure 4 shows an example of an item list screen. The item list screen is displayed when button 33 is operated on the recipe creation screen shown in Figure 3. In the example shown in Figure 4, the item list screen displays an item list 53, and a "Yes" button 55 and a "No" button 57 for indicating whether or not to confirm the selection of an item.

The item list 53 displays a list of multiple items possessed by the player. For each item, the item list 53 displays an input section 59 for inputting the item name, number possessed, and number to be used, and a selection button 61 for selecting an item. The input section 59 is configured as, for example, a pull-down menu, but other input methods may be used. The player can select the type and number of items by operating the selection button 61 for the desired item and inputting the number to be used in the input section 59. Note that in this example, a maximum of two items can be selected as described above, but it may be possible to select three or more items. In the example shown in FIG. 4, one item A has been selected. Note that in FIG. 4, the operated selection button 61 is indicated by hatching.

If the player operates the "Yes" button 55, the selected item is confirmed and its contents are reflected in the item contents display section 35 of the recipe creation screen. On the other hand, if the player operates the "No" button 57, the item selection is canceled.

Figure 5 shows an example of a status list screen. The status list screen is displayed when button 37 is operated on the recipe creation screen shown in Figure 3. In the example shown in Figure 5, the status list screen displays a status list 63, and a "Yes" button 65 and a "No" button 67 for indicating whether or not to confirm the status selection.

The status list 63 displays a list of the status of the player (the character operated by the player). For each status item, the status list 63 displays an input section 69 for inputting the item name, current value, and consumption amount (e.g., consumed points), and a selection button 71 for selecting the status item. The input section 69 is configured as, for example, a pull-down menu, but other input methods may be used. The player can select the type of status and the points to be consumed by operating the selection button 71 for the desired item and inputting the points to be consumed in the input section 69. Note that in this example, as described above, one type of status can be selected, but multiple types of status can also be selected. In the example shown in FIG. 5, it is selected to consume five points of magic. Note that in FIG. 5, the operated selection button 71 is shown hatched.

If the player operates the "Yes" button 65, the selected status is confirmed and its contents are reflected in the status contents display section 39 of the recipe creation screen. On the other hand, if the player operates the "No" button 67, the status selection is canceled.

Figure 6 shows an example of an input operation screen. The input operation screen is displayed when button 41 is operated on the recipe creation screen shown in Figure 3. In the example shown in Figure 6, the input operation screen displays an input operation section 73, and a "Yes" button 75 and a "No" button 77 for indicating whether or not to confirm the input contents.

Check boxes 79 for selecting the input operation format are displayed for each input format in the input operation section 73. By operating the check boxes 79, the player can select whether to input using key operations or to hand-draw a figure using a drag operation. In the example shown in FIG. 6, key operations have been selected.

When inputting through key operations, the player operates multiple keys (including buttons) displayed on the key display section 81 by pressing them in any combination and in any order. In the example shown in FIG. 6, four directional keys 83, an up directional key, a down directional key, a left directional key, and a right directional key, and four buttons 85, an A button, a B button, an X button, and a Y button, are displayed.

When inputting a figure by handwriting, the player inputs the figure by dragging the handwriting input unit 87. Note that characters may also be input by handwriting instead of figures.

When the player operates the "Yes" button 75, the input contents are confirmed and reflected in the input contents display section 43 of the recipe creation screen. On the other hand, when the player operates the "No" button 77, the input operation is canceled.

Figure 7 shows an example of a keyboard screen. The keyboard screen is displayed when button 45 is operated on the recipe creation screen shown in Figure 3. In the example shown in Figure 7, the keyboard screen displays a keyboard 89, an input content display section 91, and a "Yes" button 93 and a "No" button 95 for indicating whether or not to confirm the input content.

The player can input any information, such as letters, numbers, symbols, etc., by operating the keyboard 89. The input information is displayed in the input content display section 91.

When the player operates the "Yes" button 93, the input contents are confirmed and reflected in the input contents display section 47 of the recipe creation screen. On the other hand, when the player operates the "No" button 95, the input contents are canceled.

Figure 8 shows an example of a recipe success screen when the creation is successful as a result of executing the recipe. The recipe success screen is displayed when the "Yes" button 27 is operated on the recipe creation screen shown in Figure 3 and the recipe success/failure determination processing unit 11 determines that another game element can be created. In the example shown in Figure 8, for example, "Skill Z" with a rarity of three stars has been created. Note that "Skill Z" is a specific skill (for example, an attacking skill) that has been made into an item, and the player can learn this skill by using Skill Z. The learned skill may be activated, for example, by performing an input operation included in the recipe.

Figure 9 shows an example of a recipe failure screen when generation fails as a result of executing a recipe. The recipe failure screen is displayed when the "Yes" button 27 is operated on the recipe creation screen shown in Figure 3 and the recipe success/failure determination processing unit 11 determines that another game element cannot be generated.

Figure 10 shows an example of a recipe registration screen when a successfully generated recipe is determined to be a newly discovered new recipe and is registered in the recipe database 9. The recipe registration screen is displayed when, after the recipe success screen shown in Figure 8 is displayed, the recipe identity determination processing unit 13 determines that the recipe is not identical to any of the recipes registered in the recipe database 9, and the recipe is registered in the recipe database 9 by the recipe registration processing unit 15. In the example shown in Figure 10, a recipe is registered as a "skill Z" recipe with a rarity of three stars, which contains a combination of one item A, the consumption of five points of magic power, and four input operations performed in the order of the up key, down key, X button, and Y button.

Figure 11 shows an example of a recipe rejection screen when it is determined that the successfully generated recipe is not a newly discovered new recipe (it is an existing recipe). The recipe rejection screen is displayed when the recipe identity determination processing unit 13 determines that the recipe is identical to a recipe registered in the recipe database 9 after the recipe success screen shown in Figure 8 is displayed.

Figure 12 shows an example of a registered recipe list screen. The registered recipe list screen is displayed when the recipe publication processing unit 17 publishes the contents of recipes registered in the recipe database 9 so that they can be viewed by multiple players. In the example shown in Figure 12, the registered recipe list screen displays a registered recipe list 97 and a reward display section 99.

The registered recipe list 97 displays a list of summaries of the registered recipes registered in the recipe database 9. For each registered recipe, the registered recipe list 97 displays, for example, the recipe name, rarity, the rights holder player, and a view button 101 for selecting a registered recipe to view its contents. The player can freely view the contents of a desired registered recipe by operating the view button 101 for that registered recipe.

The reward display section 99 displays the reward content that will be given to the rights holder player when the registered recipe is used. In the example shown in FIG. 12, the higher the rarity of the registered recipe, the higher the reward amount; for example, a registered recipe with one star rarity is set to 5 gold, a registered recipe with two stars rarity is set to 10 gold, a registered recipe with three stars rarity is set to 20 gold, a registered recipe with four stars rarity is set to 30 gold, and a registered recipe with five stars rarity is set to 50 gold. The reward content may be set to be the same regardless of rarity, or may be set to be different for each recipe using information other than rarity (e.g., status, etc.) as an indicator.

Figure 13 shows an example of a viewing screen showing the contents of a registered recipe. The registered recipe viewing screen is displayed when the view button 101 is operated on the registered recipe list screen shown in Figure 12. In the example shown in Figure 13, the registered recipe viewing screen displays a title display section 103, a status display section 105, and a recipe content display section 107. The title display section 103 displays, for example, the name, rarity, appearance, etc. of "Card C" generated by executing the registered recipe. The status display section 105 displays, for example, various status information of the character represented on "Card C", which is a character card.

For example, the recipe content display section 107 displays the recipe content for "Card C" as a combination of one Card A, one Card B, and the consumption of 50 experience points.

Figure 14 shows an example of a prohibited target designation screen. The prohibited target designation screen is displayed by the prohibition designation reception processing unit 21 when the rights holder player designates a specific player or specific group to be prohibited from using the registered recipe. In the example shown in Figure 14, the prohibited target designation screen displays a player designation section 109, a group designation section 111, and a "Yes" button 113 and a "No" button 115 for indicating whether or not to confirm the designation.

The player designation section 109 displays a button 117 for selecting an individual player from a player list. When button 117 is operated, a player list (not shown) is displayed, and the player selected in the player list is displayed in the designated player display section 119. The player designation section 109 also displays a button 121 for selecting all players at once. By operating button 121, a player can prohibit all players other than himself from using a registered recipe. In the example shown in FIG. 14, up to three players can be designated as prohibited players, and for example, one player P is designated. It is also possible to allow four or more prohibited players to be designated.

The group designation section 111 displays a button 123 for selecting an individual group from the group list. When button 123 is operated, a group list (not shown) is displayed, and a group selected from the group list is displayed in the designated group display section 125. The group designation section 111 also displays a button 127 for selecting all groups at once. By operating button 127, the player can prohibit all groups except the group to which the player belongs from using the registered recipe. In the example shown in FIG. 14, up to three prohibited groups can be specified, and one guild G is specified, for example. It is also possible to allow four or more prohibited groups to be specified.

If the player operates the "Yes" button 113, the specified content is confirmed, and the use prohibition processing unit 23 prohibits the specified player or group from using the registered recipe. On the other hand, if the player operates the "No" button 115, the specified content is canceled.

Figure 15 shows an example of a registered recipe list screen when viewing of registered recipes by a specified player or group is restricted. Note that the registered recipe list shown in Figure 15 has the same content as the registered recipe list shown in Figure 12.

In the example shown in FIG. 15, for registered recipes for which a player or group has been specified on the prohibited target specification screen shown in FIG. 14, the view button 101 indicates that there is a viewing restriction. For example, viewing of Skill Z, Ice Armor G, Flame Sword S, Magic F, and Character D by the specified player or group is restricted. Furthermore, there are no viewing restrictions for other registered recipes, and anyone can freely view the recipe contents.

If player P who is prohibited from using "Skill Z" or a player who belongs to guild G (see FIG. 14) operates the view button 101 for "Skill Z," the recipe disclosure processing unit 17 determines the identification information of the player, etc., and displays a view prohibition screen indicating that the recipe cannot be viewed because it is prohibited from being used, as shown in FIG. 16, for example. On the other hand, if a player other than player P or guild G operates the view button 101 for "Skill Z," a view screen showing the contents of the registered recipe is displayed.

Even if player P or a player belonging to guild G who is prohibited from using "skill Z" obtains the recipe contents of "skill Z" from, for example, an information site, SNS, or other information medium, and executes the recipe, the use prohibition processing unit 23 will determine the identification information of the player, etc., and the generation will fail. In this case, for example, as shown in FIG. 17, a use prohibition screen will be displayed indicating that the generation has failed because the use of the recipe is prohibited.

Figure 18 shows an example of a reward acquisition screen by a rights holder player. The reward acquisition screen is displayed when the first reward granting processing unit 19 grants a reward to a rights holder player when a registered recipe is used. In the example shown in Figure 18, a recipe for "skill Z" is used three times within a certain period (e.g., one day, one week, etc.), and rights holder player M has earned a reward of 60 gold (reward for a three-star rarity level of 20G x 3 = 60G).

Figure 19 shows an example of a time lapse notification screen that notifies the rights holder player that a predetermined period of time has passed since the registration of the registered recipe. The time lapse notification screen is displayed when a predetermined period of time has passed since the registration of the registered recipe, the first reward granting processing unit 19 stops granting rewards, the use prohibition processing unit 23 lifts the prohibition on use, and the recipe disclosure processing unit 17 lifts the viewing restrictions. In the example shown in Figure 19, for example, the predetermined period is set to one month, and one month has passed since the recipe for "skill Z" was registered, so the rights holder player is notified that the granting of rewards has been stopped and the prohibition on use and viewing restrictions for players or groups prohibited from using "skill Z" have been lifted.

4. Processing Procedure of Information Processing Device
Next, an example of a processing procedure executed by the CPU 501 of the server device 5 will be described with reference to FIG.

In step S5, the server device 5 uses the recipe success/failure determination processing unit 11 to determine whether or not a recipe including a combination of multiple game elements has been accepted from the terminal device 3. If a recipe has not been accepted (step S5: NO), the process proceeds to step S30, which will be described later. On the other hand, if a recipe has been accepted (step S5: YES), the process proceeds to step S10.

In step S10, the server device 5 uses the recipe success/failure determination processing unit 11 to determine whether or not the generation of another game element using the recipe accepted in step S5 above has been successful. If the generation has failed (step S10: NO), the process proceeds to step S30, which will be described later. On the other hand, if the generation has been successful (step S10: YES), the process proceeds to step S15.

In step S15, the server device 5 uses the recipe identity determination processing unit 13 to determine whether the recipe received in step S5 is identical to any of the recipes registered in the recipe database 9, i.e., whether it is a newly discovered new recipe. If it is not a new recipe (step S15: NO), the process proceeds to step S30, which will be described later. On the other hand, if it is a new recipe (step S15: YES), the process proceeds to step S20.

In step S20, the server device 5 registers the recipe received in step S5 in the recipe database 9 via the recipe registration processing unit 15.

In step S25, the server device 5 causes the recipe publication processing unit 17 to publish the contents of the recipe registered in the recipe database 9 in step S20 so that multiple players can view it.

In step S30, the server device 5 determines, via the first reward granting processing unit 19, whether or not a recipe registered in the recipe database 9 has been used by a player other than the rights holder player. If the registered recipe has not been used (step S30: NO), the process proceeds to step S40, which will be described later. On the other hand, if the registered recipe has been used (step S30: YES), the process proceeds to step S35.

In step S35, the server device 5 causes the first reward granting processing unit 19 to grant a reward to the rights holder player based on, for example, the number of times the registered recipe has been used.

In step S40, the server device 5 determines whether or not the prohibition designation reception processing unit 21 has received a designation from the rights holder player who owns the registered recipe of a specific player or specific group who is to be prohibited from using the registered recipe. If no designation has been received (step S40: NO), the process proceeds to step S50, which will be described later. On the other hand, if a designation has been received (step S40: YES), the process proceeds to the next step S45.

In step S45, the server device 5 prohibits the specific player or specific group accepted in step S40 from using the registered recipe by the use prohibition processing unit 23. In addition, the recipe disclosure processing unit 17 restricts the specific player or specific group accepted in step S40 from viewing the contents of the registered recipe.

In step S50, the server device 5 determines whether or not there are any registered recipes in the recipe database 9 for which a predetermined period of time has passed since they were registered. If the predetermined period of time has not passed for any of the registered recipes (step S50: NO), the process proceeds to step S60, which will be described later. On the other hand, if there are any registered recipes for which a predetermined period of time has passed (step S50: YES), the process proceeds to the next step S55.

In step S55, the server device 5 causes the first reward granting processing unit 19 to stop granting rewards to the rights holder player of the registered recipe for which a predetermined period of time has passed. In addition, if a prohibited player, etc. is specified for a registered recipe for which a predetermined period of time has passed, the use prohibition processing unit 23 lifts the prohibition on use for the prohibited players, etc., and the recipe disclosure processing unit 17 lifts the viewing restrictions for the prohibited players, etc.

In step S60, the server device 5 determines whether or not to end the game. For example, if the player performs a predetermined end operation, logs out, or the like (step S60: YES), the game ends. On the other hand, if the player has not performed an end operation, logs out, or the like (step S60: NO), the process returns to the previous step S5. This ends this flowchart.

The above-mentioned processing steps are merely examples, and at least some of the steps may be deleted or changed, or steps other than those described above may be added. Also, the order of at least some of the steps may be changed.

5. Effects of the embodiment
As described above, the game program of this embodiment causes the server device 5 to function as a recipe success/failure determination processing unit 11 that receives a recipe including a combination of multiple game elements and determines whether or not another game element can be generated using the recipe, a recipe identity determination processing unit 13 that determines whether or not the received recipe is identical to any of the recipes registered in the recipe database 9 in association with the rights holder player if the other game element can be generated, and a recipe registration processing unit 15 that registers at least one of the received recipe or the rights holder player who transmitted the recipe in the recipe database 9 if the received recipe is not identical to any of the registered recipes.

In this embodiment, when a player transmits a recipe combining multiple game elements from the terminal device 3 to the server device 5, it is determined whether or not the recipe can be used to generate another game element. This allows the player to explore recipes by trial and error until another game element is generated. If another game element is generated, it is determined whether the recipe is identical to any of the recipes already registered in the recipe database 9, and if it is not identical to any of the recipes, it is newly registered in the recipe database 9. The registered recipe can be made public so that other players can use it, as in the above-mentioned embodiment, and the right holder player can receive a reward depending on the number of times it is used, or, for example, as in the modified example described below, the registered recipe can be sold to allow players who have purchased it to use it and the right holder player can receive a reward depending on the number of times it is purchased. Various processes can be performed using the registered recipe.

In this way, if a player has come up with a new recipe through trial and error and creative ingenuity, it can be registered, and various processes that will be beneficial to the rights holder player who discovered the recipe can be executed. This can encourage many players to explore new recipes, leading to more excitement in the game.

In particular, in this embodiment, the game program also causes the server device 5 to function as a recipe publication processing unit 17 that publishes the contents of registered recipes so that they can be viewed by multiple players.

This allows recipes to be used by multiple players in the game.

In particular, in this embodiment, the game program causes the server device 5 to further function as a first reward granting processing unit 19 that grants a reward to the rights holder player associated with a recipe when a registered recipe is used by a player other than the rights holder player associated with the recipe.

This allows new recipes that players come up with through trial and error and creative ingenuity to have added value as a revenue source. This will encourage many players to explore new recipes, leading to more excitement in the game.

In particular, in this embodiment, the first reward granting processing unit 19 stops granting rewards to the rights holder player associated with the recipe when a predetermined period of time has passed since the accepted recipe was registered in the recipe database 9.

If the granting of rewards to rights holder players were to continue forever, players who have not registered recipes would be at a disadvantage, creating unfairness between players. In this embodiment, players who discover new recipes are encouraged to explore new recipes by granting rewards for a specified period of time, while the granting of rewards is stopped after the specified period has elapsed, preventing unfairness between players.

In particular, in this embodiment, the game program causes the server device 5 to further function as a prohibition designation reception processing unit 21 that receives, from the rights holder player associated with the recipe, the designation of a specific player or specific group that is to be prohibited from using the registered recipe, and a use prohibition processing unit 23 that prohibits the specified player or group from using the registered recipe.

In this embodiment, the player who registered the recipe can prohibit a specific player or a specific group from using the registered recipe. This makes it possible, for example, when a specific player (or specific group) is fighting another specific player (or specific group) in an MMORPG (Massively Multiplayer Online Role-Playing Game) or an MMO simulation game, to gain an advantage in the battle by prohibiting the opposing player or group from using the registered recipe.

In particular, in this embodiment, the recipe disclosure processing unit 17 discloses the contents of the registered recipe so that it can be viewed by players or groups other than the player or group designated as prohibited from use, and restricts viewing by the designated player or group.

This can increase the effectiveness of banning registered recipes from being used by specific players or groups.

In particular, in this embodiment, the use prohibition processing unit 23 lifts the prohibition on use of the player or group designated as the prohibited target when a predetermined period of time has passed since the accepted recipe was registered in the recipe database 9.

If a certain player or group were to be unable to use a registered recipe for an indefinite period of time, this would create unfairness among players and hinder the revitalization of the game. In this embodiment, the ban on use for a certain player or group is lifted after a certain period of time has passed. This allows a player who discovers a new recipe to be rewarded with the authority to exclude certain players from using the recipe for a certain period of time, while allowing all players to use the registered recipe equally after the certain period of time has passed. This encourages the exploration of recipes, prevents unfairness among players, and leads to the revitalization of the game.

6. Modifications
The present invention is not limited to the above-described embodiment, and various modifications are possible without departing from the spirit and technical concept of the present invention. Such modifications will be described below.

(6-1. When accepting a recipe registration request)
In the above embodiment, when a recipe is executed and generation is successful, the recipe is automatically compared with registered recipes in the recipe database 9 to determine whether it is new, and if it is new, it is registered in the recipe database 9, but this is not limited to the above. For example, when a recipe is executed and generation is successful, it may be determined whether the recipe is new only when a request for registration is received from the player.

Figure 21 shows an example of the functional configuration of a server device 5A according to this modified example. As shown in Figure 21, the server device 5A (an example of an information processing device) has a registration request determination processing unit 129 in addition to the functional configuration of the server device 5 shown in Figure 2 described above.

When the recipe success/failure determination processing unit 11 determines that another game element has been generated, the registration request determination processing unit 129 determines whether a request to register the recipe has been received from the terminal device 3. A "registration request" refers to an operational input made by the player to request that the successfully generated recipe be registered in the recipe database 9.

When the registration request determination processing unit 129 determines that a request to register a recipe has been received, the recipe identity determination processing unit 13 determines whether the recipe received from the terminal device 3 is identical to any of the recipes registered in the recipe database 9. In other words, in this modified example, it is only when a registration request is received from the player that it is determined whether the recipe is new, and if a registration request is not received, it is not determined whether the recipe is new.

Figure 22 shows an example of a recipe success screen in this modified example. In the example shown in Figure 22, for example, skill Z with a rarity of three stars has been generated. The recipe success screen also displays a "Yes" button 131 and a "No" button 133 for indicating whether or not to request the registration of the recipe.

When the player operates the "Yes" button 131, the registration request determination processing unit 129 determines that a request to register a recipe has been accepted, and determines whether or not the recipe is identical to the registered recipe. If it is not identical to the registered recipe, it is registered in the recipe database 9, and if it is identical to the registered recipe, the registration is rejected. On the other hand, if the player operates the "No" button 133, the registration request is canceled. In this case, no determination is made as to whether or not the recipe is identical to the registered recipe, and registration is not performed.

Figure 23 shows an example of a processing procedure executed by the CPU 501 of the server device 5A according to this modified example.

Steps S5 and S10 are similar to those in FIG. 20 above, so the explanation is omitted.

In step S13, the server device 5A uses the registration request determination processing unit 129 to determine whether or not a request to register the recipe received in step S5 has been received from the terminal device 3. If a registration request has not been received (step S13: NO), the process proceeds to step S30, which will be described later. On the other hand, if a registration request has been received (step S13: YES), the process proceeds to step S15.

Steps S15 to S60 are the same as those in FIG. 20 above, so the explanation is omitted.

According to the modified example described above, the player can choose whether or not to request the registration of a recipe as necessary. For example, by not requesting registration, it is possible to keep a discovered recipe for personal use only (turn it into know-how) without making it public.

In the above, it is determined whether or not a registration request has been received from the player when a recipe is executed and successfully generated. However, it may also be determined whether or not a registration request has been received from the player when, for example, a recipe is executed and successfully generated, and it is determined whether the recipe is new and it is determined that it is new. Also, for example, the player may be allowed to select "only publish," which requests publication by registering a recipe, but does not request the granting of rewards or the specification of prohibited use.

(6-2. When the player who purchased the registered recipe can view and use it)
In the above embodiment, the contents of the registered recipes are made public, and players other than the right holder player can freely use the registered recipes in principle, but this is not limited to this. For example, the registered recipes may be sold or transferred, and only the player who purchased the registered recipes may view and use the contents of the registered recipes.

Figure 24 shows an example of the functional configuration of the server device 5B according to this modified example. As shown in Figure 21, the server device 5B (an example of an information processing device) has a recipe sales processing unit 135, a recipe disclosure processing unit 137, and a second reward granting processing unit 139 in addition to the recipe success/failure determination processing unit 11, the recipe identity determination processing unit 13, and the recipe registration processing unit 15 shown in Figure 2 described above.

The recipe sales processing unit 135 sells or transfers recipes registered in the recipe database 9. For example, the recipe sales processing unit 135 sells or transfers the contents of a registered recipe as a recipe item. "Transfer" includes, for example, transfer or exchange without compensation.

The recipe disclosure processing unit 137 discloses the contents of a registered recipe to a player who purchases (or receives in the case of transfer; the same applies below) the registered recipe. This allows the player who purchased the registered recipe to use it.

The second reward granting processing unit 139 grants a reward to the rights holder player associated with the purchased registered recipe. The reward may be granted in the form of virtual currency, for example, or in the form of an item other than virtual currency. The reward may be a fixed amount each time a registered recipe is purchased, for example, or the number of times it is purchased within a certain period (for example, one day, one week, etc.) may be tallied and an amount according to the number of times may be granted. The reward may be the price of the registered item itself, or, for example, an amount calculated by multiplying the price by a certain percentage.

Figure 25 shows an example of a sales screen for registered recipes. The sales screen for registered recipes is displayed by the recipe sales processing unit 135 so that multiple players can view it. In the example shown in Figure 25, a registered recipe list 141 and a price display section 143 are displayed on the sales screen for registered recipes.

The registered recipe list 141 displays a list of summaries of registered recipes registered in the recipe database 9. For each registered recipe, the registered recipe list 141 displays the recipe name, rarity, the rights owner player, and a purchase button 145 for purchasing the registered recipe. By operating the purchase button 145 for the desired registered recipe, the player can purchase that registered recipe by consuming the virtual currency they possess for the price. Note that while the player can view the contents of registered recipes that they have purchased, for registered recipes that they have not purchased, they can only view the summary displayed in the registered recipe list 141.

The price display section 143 displays the price of the registered recipe. In the example shown in FIG. 25, the price is set to be higher as the rarity of the registered recipe increases. The price may be set to be the same regardless of rarity, or the price may be set to be different for each recipe using information other than rarity (e.g., status, etc.) as an indicator.

Figure 26 shows an example of a purchase screen showing the contents of a purchased registered recipe. The purchase screen for a registered recipe is displayed when the purchase button 145 is operated on the sales screen for a registered recipe shown in Figure 25. In the example shown in Figure 26, the purchase screen for a registered recipe displays a title display section 147, a status display section 149, and a recipe content display section 151. The title display section 147 displays, for example, the name, rarity, and appearance of the "Ice Armor" that is generated by executing the registered recipe. The status display section 149 displays various status information for the resulting product, "Ice Armor."

For example, the recipe content display section 151 displays the recipe content for "Ice Armor" as a combination of one item A, one item B, a snowy field location, and winter season.

Figure 27 shows an example of a processing procedure executed by the CPU 501 of the server device 5B according to this modified example.

Steps S5 to S20 are the same as those in FIG. 20 above, so the explanation is omitted.

In step S23, the server device 5B sells the recipes registered in the recipe database 9 via the recipe sales processing unit 135.

In step S27, the server device 5B determines whether the registered recipe being sold has been purchased by a player other than the right holder player. If the registered recipe has not been purchased (step S27: NO), the process proceeds to step S60, which will be described later. On the other hand, if the registered recipe has been purchased (step S27: YES), the process proceeds to step S33.

In step S33, the server device 5B causes the recipe disclosure processing unit 137 to disclose the contents of the registered recipe to the player who purchased the recipe.

In step S37, the server device 5B causes the second reward granting processing unit 139 to grant a reward to the rights holder player of the purchased registered recipe.

Step S60 is the same as that in Figure 20 described above, so the explanation will be omitted.

According to the modified example described above, only the player who purchased the registered recipe can view the contents of that registered recipe. This makes it possible to make the registered recipe available only to the player who purchased it, while keeping the contents of the registered recipe private.

In addition, in this variation, when another player purchases a recipe, the rights holder player who registered the recipe can receive a reward. This allows new recipes that players have come up with through trial and error and ingenuity to have added value as a source of revenue. As a result, this can encourage many players to explore new recipes, leading to more excitement in the game.

In this modified example, if a certain period of time has passed since a registered recipe was registered in the recipe database 9, the sale of the registered recipe may be stopped so that other players may freely view and use the recipe.

(6-3. When permission to use registered recipes is granted)
In the above embodiment, other players than the right holder player are allowed to freely use the registered recipes in principle, and the right holder player is allowed to designate players etc. who are prohibited from using the registered recipes, but this is not limited to this. For example, the right holder player may be allowed to designate players etc. who are permitted to use the registered recipes, and only the permitted players may be allowed to use the registered recipes.

Figure 28 shows an example of the functional configuration of a server device 5C according to this modified example. As shown in Figure 28, the server device 5C (an example of an information processing device) has a permission designation acceptance processing unit 153 and a usage permission processing unit 155 in addition to the recipe success/failure determination processing unit 11, recipe identity determination processing unit 13, recipe registration processing unit 15, recipe disclosure processing unit 17, and first reward granting processing unit 19 shown in Figure 2 described above.

The permission designation reception processing unit 153 receives designation of a specific player or specific group that is authorized to use the registered recipe from the rights holder player associated with the registered recipe.

The license processing unit 155 permits a specific player or specific group (hereinafter referred to as "licensed players, etc." as appropriate) accepted by the license designation acceptance processing unit 153 to use the registered recipe. Note that players or groups who have not received a license are prohibited from using the registered recipe. Furthermore, if a predetermined period of time has passed since the registered recipe was registered in the recipe database 9, the license processing unit 155 permits players, etc. who have not received a license to use the registered recipe. In other words, it opens the use of the registered recipe to all players.

The first reward granting processing unit 19 grants a reward to the rights holder player associated with the registered recipe when the registered recipe is used by a licensed player or the like. In addition, the first reward granting processing unit 19 stops granting rewards to the rights holder player when a predetermined period of time has passed since the registered recipe was registered in the recipe database 9.

The recipe disclosure processing unit 17 makes the contents of the registered recipe available for viewing by licensed players, etc., while restricting viewing by players, etc. who are not licensed. In addition, when a predetermined period of time has passed since the registered recipe was registered in the recipe database 9, the recipe disclosure processing unit 17 lifts the restriction on viewing by players, etc. who are not licensed, and makes the contents of the registered recipe available.

Figure 29 shows an example of a license target designation screen. The license target designation screen is displayed by the license designation reception processing unit 153 when the rights holder player designates a specific player or a specific group to whom the license holder player is to grant use of the registered recipe. In the example shown in Figure 29, the license target designation screen displays a player designation section 157, a group designation section 159, and a "Yes" button 161 and a "No" button 163 for indicating whether or not to confirm the designation.

The player designation section 157 displays a button 165 for selecting an individual player from a player list. When the button 165 is operated, a player list (not shown) is displayed, and the player selected in the player list is displayed in the designated player display section 167. The player designation section 157 also displays a button 169 for selecting all players at once. By operating the button 169, the player can grant permission for all players to use the registered recipe. In the example shown in FIG. 29, up to three licensed players can be designated, and for example, one player P is designated. It is also possible to allow four or more licensed players to be designated.

The group designation section 159 displays a button 171 for selecting an individual group from the group list. When button 171 is operated, a group list (not shown) is displayed, and a group selected from the group list is displayed in the designated group display section 173. The group designation section 159 also displays a button 175 for selecting all groups at once. By operating button 175, the player can grant permission for all groups to use the registered recipe. In the example shown in FIG. 29, up to three licensed groups can be designated, and one guild G is designated, for example. It is also possible to allow four or more licensed groups to be designated.

When the player operates the "Yes" button 161, the specified content is confirmed, and the license processing unit 155 grants permission for the specified player or group to use the registered recipe. On the other hand, when the player operates the "No" button 163, the specified content is cancelled.

In this modified example, the registered recipe list is made public to all players, but viewing of the contents of the registered recipes is restricted to players other than those authorized to use the recipes. For example, on the registered recipe list screen shown in FIG. 12 above, if player P who is authorized to use "skill Z" or a player belonging to guild G (see FIG. 29) operates the view button 101 for "skill Z," a view screen showing the contents of the registered recipes is displayed. On the other hand, if a player other than player P or guild G operates the view button 101 for "skill Z," the recipe disclosure processing unit 17 determines the identification information of the player, etc., and a view prohibition screen is displayed, for example as shown in FIG. 30, indicating that the recipe cannot be viewed because the player is not authorized to use the recipe.

Even if a player other than player P or guild G who is not authorized to use "skill Z" obtains the recipe contents of "skill Z" from, for example, an information site, SNS, or other information medium, and executes the recipe, the usage permission processing unit 155 will determine the identification information of the player, etc., and the generation will fail. In this case, for example, as shown in FIG. 31, a usage prohibition screen will be displayed indicating that the generation has failed because the use of the recipe is not authorized.

Figure 32 shows an example of a time lapse notification screen that notifies the rights holder player that a predetermined period of time has passed since the registration of a registered recipe. The time lapse notification screen is displayed when a predetermined period of time has passed since the registration of a registered recipe, the first reward granting processing unit 19 stops granting rewards, and the license processing unit 155 and recipe disclosure processing unit 17 release the registered recipe (release of use, removal of viewing restrictions). In the example shown in Figure 32, for example, the predetermined period is set to one month, and one month has passed since the recipe for "skill Z" was registered, so the granting of rewards to the rights holder player M is stopped and the player is notified that "skill Z" has been released.

Figure 33 shows an example of a processing procedure executed by the CPU 501 of the server device 5C according to this modified example.

Steps S5 to S20 are the same as those in FIG. 20 above, so the explanation is omitted.

In step S24, the server device 5C determines whether or not the permission designation reception processing unit 153 has received, from the rights holder player, a designation of a specific player or specific group that is authorized to use the registered recipe. If a designation of permission to use has not been received (step S24: NO), the process proceeds to step S44, which will be described later. On the other hand, if a designation of permission to use has been received (step S24: YES), the process proceeds to step S28.

In step S28, the server device 5C, through the license processing unit 155, permits the licensed players, etc. accepted in step S24 above to use the registered recipe, and prohibits players, etc. who are not licensed from using the registered recipe. In addition, the recipe disclosure processing unit 17 discloses the contents of the registered recipe so that the licensed players, etc. can view it, and restricts players, etc. who are not licensed from viewing it.

In step S34, the server device 5C determines, via the first reward granting processing unit 19, whether or not the registered recipe has been used by a licensed player, etc. If it has not been used by a licensed player, etc. (step S34: NO), the process proceeds to step S44, which will be described later. On the other hand, if it has been used by a licensed player, etc. (step S34: YES), the process proceeds to step S38.

In step S38, the server device 5C, via the first reward granting processing unit 19, grants a reward to the rights holder player based on, for example, the number of times the registered recipe has been used.

In step S44, the server device 5C determines whether there are any registered recipes in the recipe database 9 for which a predetermined period of time has passed since they were registered. If the predetermined period of time has not passed for any of the registered recipes (step S44: NO), the process proceeds to step S60, which will be described later. On the other hand, if there are any registered recipes for which a predetermined period of time has passed (step S44: YES), the process proceeds to the next step S55.

In step S48, the server device 5C causes the first reward granting processing unit 19 to stop granting rewards to the rights holder player of the registered recipe for which a predetermined period of time has passed. In addition, if a licensed player or the like is specified for a registered recipe for which a predetermined period of time has passed, the license processing unit 155 releases the use of the registered recipe, and the recipe disclosure processing unit 17 discloses the contents of the registered recipe.

Step 60 is the same as that described above in Figure 20, so the explanation will be omitted.

According to the modified example described above, the rights holder player can grant permission for a specific player or a specific group (e.g., a guild, etc.) to use a registered recipe. This makes it possible, for example, when a specific player (or specific group) is fighting another specific player (or specific group) in an MMORPG or MMO simulation game, to gain an advantage in the battle by granting permission for the friendly player or group to use the registered recipe.

In addition, only specific players or specific groups who have been granted permission to use the registered recipe can view the contents of the registered recipe, which increases the effectiveness of the permission to use.

If the state in which only certain players or groups could use the registered recipes were to continue forever, this would create unfairness among players and hinder the revitalization of the game. In this modified example, players or groups other than the licensed players are permitted to use the registered recipes after a specified period of time has passed. In this way, a player who discovers a new recipe is given the right to use it exclusively for a specified period of time by the rights holder player and the licensed players, and after the specified period has passed, all players are allowed to use the registered recipes equally. This encourages the exploration of recipes, prevents unfairness among players, and leads to the revitalization of the game.

In addition to what has already been described above, the methods according to the above embodiments and each modified example may be used in appropriate combination. Although not illustrated individually, the above embodiments and each modified example may be implemented with various modifications within the scope of their purpose.

7. Hardware configuration of server device
Next, an example of a hardware configuration of the server device 5 (including the server devices 5A, 5B, and 5C) that realizes each processing unit implemented by the program executed by the CPU 501 described above will be described with reference to Fig. 34. The terminal device 3 may have a similar hardware configuration.

As shown in FIG. 34, the server device 5 has, for example, a CPU 501, a ROM 503, a RAM 505, a GPU 506, a dedicated integrated circuit 507 constructed for a specific application, such as an ASIC or FPGA, an input device 513, an output device 515, a recording device 517, a drive 519, a connection port 521, and a communication device 523. These components are connected to each other via a bus 509, an input/output interface 511, etc., so that signals can be transmitted between them.

The game program can be recorded, for example, in ROM 503, RAM 505, or a recording device 517 such as a hard disk.

The game program may also be temporarily or permanently (non-temporarily) recorded on a removable recording medium 525, such as a magnetic disk such as a flexible disk, various types of CDs, MO disks, optical disks such as DVDs, or semiconductor memories. Such recording media 525 may also be provided as so-called packaged software. In this case, the game program recorded on these recording media 525 may be read by the drive 519 and recorded on the recording device 517 via the input/output interface 511, bus 509, etc.

The game program may also be recorded, for example, on a download site, another computer, or another recording device (not shown). In this case, the game program is transferred via a network NW such as a LAN or the Internet, and the communication device 523 receives this program. The program received by the communication device 523 may then be recorded in the recording device 517 via the input/output interface 511, bus 509, etc.

The game program may also be recorded, for example, in an appropriate external connection device 527. In this case, the game program may be transferred via an appropriate connection port 521 and recorded in the recording device 517 via the input/output interface 511, bus 509, etc.

Then, the CPU 501 executes various processes according to the programs recorded in the recording device 517, thereby realizing processes by the recipe success/failure determination processing unit 11, recipe identity determination processing unit 13, recipe registration processing unit 15, etc. described above. At this time, the CPU 501 may, for example, read the programs directly from the recording device 517 and execute them, or may load them once into the RAM 505 and then execute them. Furthermore, when the CPU 501 receives a program via the communication device 523, drive 519, or connection port 521, for example, it may execute the received program directly without recording it in the recording device 517.

The CPU 501 may also perform various processes based on signals and information input from an input device 513, such as a mouse, keyboard, or microphone, as necessary, in addition to signals input from each terminal device 3 via the network NW.

The GPU 506 performs image display processing, such as rendering processing, in response to instructions from the CPU 501.

The CPU 501 and GPU 506 then output the results of the above processing to each terminal device 3 via the network NW, and, if necessary, output the results from an output device 515 including an audio output unit (not shown) such as a speaker or headphones. Furthermore, the CPU 501 and GPU 506 may transmit the processing results via the communication device 523 or the connection port 521, if necessary, or may record the results in the recording device 517 or the recording medium 525.

3 Terminal device 5 Server device (information processing device)
5A Server device (information processing device)
5B Server device (information processing device)
5C Server device (information processing device)
9 Recipe database (registration section)
REFERENCE SIGNS LIST 11 Recipe success/failure determination processing unit 13 Recipe identity determination processing unit 15 Recipe registration processing unit 17 Recipe publication processing unit 19 First reward granting processing unit 21 Prohibition designation reception processing unit 23 Use prohibition processing unit 129 Registration request determination processing unit 135 Recipe sales processing unit 137 Recipe disclosure processing unit 139 Second reward granting processing unit 153 Permission designation reception processing unit 155 Use permission processing unit

Claims (15)

An information processing device,
a recipe success/failure determination processing unit that receives a recipe including a combination of a plurality of game elements and determines whether or not another game element can be generated using the recipe;
a recipe identity determination processing unit that, when the different game element is generated, determines whether or not the received recipe is identical to any of the recipes registered in the registration unit in association with the right holder player;
a recipe registration processing unit which, when the received recipe is not identical to any of the recipes registered in association with the right holder player, associates the received recipe with a player who transmitted the recipe and registers the recipe in the registration unit, or , when the received recipe is not identical to any of the recipes registered in association with the right holder player, associates the player who transmitted the recipe with a recipe identical to the received recipe among recipes that have been registered in advance in the registration unit while the right holder player is not registered, and registers the recipe in the registration unit;
Function as a
The recipe is:
a first game element into which the player inputs content;
a second game element selected by the player as to whether or not to include the second game element in the recipe, and the content of the second game element is acquired by the information processing device when the player selects to include the second game element in the recipe;
Including,
The first game element is
The input information includes a combination of types of input operations performed by the player, or a timing of the input operations, or a letter, a number, a symbol, or a figure input by the player,
The second game element is
The information includes location information in the game where the player creates the recipe or real-world location information of the player, or time information in the game or real-world time information where the player creates the recipe,
Game program. The information processing device,
a recipe publishing processing unit that publishes the contents of the registered recipe so that a plurality of players can view the contents;
Further functioning as
The game program according to claim 1 . The information processing device,
a first reward granting processing unit that grants a reward to the right holder player associated with the recipe when the registered recipe is used by a player other than the right holder player associated with the recipe;
Further functioning as
The game program according to claim 2. The first reward granting processing unit,
when a predetermined period of time has elapsed since the accepted recipe was registered in the registration unit, stopping the provision of a reward to the right holder player associated with the recipe;
Further functioning as
The game program according to claim 3. The information processing device,
a prohibition designation reception processing unit that receives, from the right holder player associated with the recipe, designation of a specific player or a specific group that is prohibited from using the registered recipe;
a use prohibition processing unit that prohibits a designated player or group from using the registered recipe;
Further functioning as
5. The game program according to claim 3 or 4. The recipe disclosure processing unit:
publishing the content of the registered recipe so that it can be viewed by other players or groups other than the designated player or group, and restricting the designated player or group from viewing the content;
The game program according to claim 5. The use prohibition processing unit is
When a predetermined period of time has elapsed since the accepted recipe was registered in the registration unit, the prohibition on use of the recipe by the designated player or group is lifted.
7. A game program according to claim 5 or 6. The information processing device,
a registration request determination processing unit that determines whether or not a request for registration of the accepted recipe has been accepted when the other game element has been generated;
It also functions as
The recipe identity determination processing unit includes:
when the request for registration is received, it is determined whether or not the received recipe is identical to any of the recipes registered in association with the right holder player;
The game program according to any one of claims 1 to 7. The information processing device,
a recipe sales processing unit that sells or transfers the registered recipes;
a recipe disclosure processing unit that discloses the content of the registered recipe to a player who has purchased the recipe;
Further functioning as
The game program according to claim 1 . The information processing device,
a second reward granting processing unit that grants a reward to the right holder player associated with the purchased recipe;
Further functioning as
The game program according to claim 9. The information processing device,
a permission designation reception processing unit that receives, from the right holder player associated with the recipe, designation of a specific player or a specific group that is authorized to use the registered recipe;
a license processing unit that grants permission for the designated player or group to use the registered recipe;
It also functions as
The first reward granting processing unit,
When the registered recipe is used by a designated player or group, a reward is given to the right holder player associated with the recipe.
5. The game program according to claim 3 or 4. The recipe disclosure processing unit:
publishing the contents of the registered recipe so that the designated player or group can view the contents, and restricting viewing by players or groups other than the designated player or group;
The game program according to claim 11. The license processing unit,
permitting a player or group other than the designated player or group to use the registered recipe when a predetermined period of time has elapsed since the accepted recipe was registered in the registration unit;
13. A game program according to claim 11 or 12. A game processing method executed by an information processing device, comprising:
receiving a recipe including a combination of a plurality of game elements and determining whether the recipe can be used to generate another game element;
a step of determining whether or not the received recipe is identical to any of the recipes registered in a registration unit in association with the right holder player when the different game element is generated;
a step of associating the received recipe with a player who transmitted the recipe and registering the received recipe in the registration unit when the received recipe is not identical to any of the recipes registered in association with the right holder player, or associating the player who transmitted the recipe with a recipe identical to the received recipe among recipes that have been registered in advance in the registration unit while the right holder player is not registered, and registering the recipe in the registration unit when the received recipe is not identical to any of the recipes registered in association with the right holder player;
having
The recipe is:
a first game element into which the player inputs content;
a second game element selected by the player as to whether or not to include the second game element in the recipe, and the content of the second game element is acquired by the information processing device when the player selects to include the second game element in the recipe;
Including,
The first game element is
The input information includes a combination of types of input operations performed by the player, or a timing of the input operations, or a letter, a number, a symbol, or a figure input by the player,
The second game element is
The information includes location information in the game where the player creates the recipe or real-world location information of the player, or time information in the game or real-world time information where the player creates the recipe,
Game processing method. a recipe success/failure determination processing unit that receives a recipe including a combination of a plurality of game elements and determines whether or not another game element can be generated using the recipe;
a recipe identity determination processing unit that, when the different game element is generated, determines whether the received recipe is identical to any of the recipes registered in a registration unit in association with the right holder player;
a recipe registration processing unit which, when the received recipe is not identical to any of the recipes registered in association with the right holder player, associates the received recipe with a player who transmitted the recipe and registers the recipe in the registration unit, or , when the received recipe is not identical to any of the recipes registered in association with the right holder player, associates the player who transmitted the recipe with a recipe identical to the received recipe among recipes that have been registered in advance in the registration unit while the right holder player is not registered, and registers the recipe in the registration unit;
having
The recipe is:
a first game element into which the player inputs content;
a second game element selected by the player as to whether or not to include the second game element in the recipe, and the content of the second game element is acquired by an information processing device when the player selects to include the second game element in the recipe;
Including,
The first game element is
The input information includes a combination of types of input operations performed by the player, or a timing of the input operations, or a letter, a number, a symbol, or a figure input by the player,
The second game element is
The information includes location information in the game where the player creates the recipe or real-world location information of the player, or time information in the game or real-world time information where the player creates the recipe,
Information processing device.

Images