JP7312453B2 - Game program, game processing method, and game device - Google Patents

Description

Application of Article 30, Paragraph 2 of the Patent Law Publication date September 4, 2018 Place of publication (a) Application download service (App Store) operated by Apple Inc. URL: https://itunes. apple. com/jp/app/id940320341 (b) An application download service (Google Play) operated by Google. URL: https://play. google. com/store/apps/details? id=jp. konami. prospia (C) An application download service operated by Amazon. URL: https://www. amazon. co. jp/dp/B072LZSKQG

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

2. Description of the Related Art Conventionally, there are sports games such as baseball games in which player characters displayed on a screen are used to play against each other. Such games have a function of setting cheering songs for the player characters and the teams to which the player characters belong. For example, if a cheering song created by a user or a cheering song downloaded is set for a player character, the cheering song is played back when the player character participates in a match (see, for example, Patent Document 1).

Japanese Patent Application Laid-Open No. 2007-014701

In the game described above, when settings such as cheering songs are set for the player characters, the specifications are set for each player character. Therefore, when there are a plurality of types of player characters with the same player name but different rarities, even if one player character is set, other types of player characters with the same player name must be set separately, which is troublesome and inconvenient.

An object of some aspects of the present invention is to provide a game program, a game processing method, and a game device that improve the convenience of game settings.

Another object of the present invention is to provide a game program, a game processing method, and a game device that can achieve the effects described in the embodiments described later.

To solve the above-described problems, one aspect of the present invention is a game program for executing game processing using a plurality of player characters, wherein a computer refers to data in which first identification information for identifying each of a plurality of player characters including a plurality of types of player characters with the same player name and player characters with different player names are included, and second identification information, which is set as the same information for player characters with the same player name and different information for player characters with different player names as identification information for presentation for each player character, is associated. A game program for executing a step of associating, based on an operation, an effect that can be set for each player character with the second identification information associated with the player character, and a step of performing processing according to the effect associated with the second identification information associated with the player character satisfying the predetermined condition, in response to each of a plurality of player characters satisfying a predetermined condition based on the progress of the game.

Another aspect of the present invention is a game processing method executed by a computer that executes processing of a game using a plurality of player characters, wherein first identification information for identifying each of a plurality of player characters including a plurality of types of player characters with the same player name and player characters with different player names are included, and second identification information set as the same information for the player characters with the same player name and different information for the player characters with different player names as identification information for presentation of each player character are associated with each other. The game processing method includes a step of associating an effect that can be set for each player character with the second identification information associated with the player character, and a step of performing processing according to the effect associated with the second identification information associated with the player character satisfying the predetermined condition in response to each of the plurality of player characters satisfying a predetermined condition based on the progress of the game.

In one aspect of the present invention, there is provided a game device for executing game processing using a plurality of player characters, wherein first identification information for identifying each of a plurality of player characters including a plurality of types of player characters with the same player name and player characters with different player names are included, and second identification information, which is set as the same information for player characters with the same player name and different information for player characters with different player names as identification information for presentation of each player character, are associated with each other. The game device includes an associating part that associates a settable effect with the second identification information associated with the player character, and an effect processing part that performs processing according to the effect associated with the second identification information associated with the player character that satisfies the predetermined condition when each of the plurality of player characters satisfies a predetermined condition based on the progress of the game.

In one aspect of the present invention, a computer is caused to execute a step of acquiring a first object to be used in a game, a step of acquiring a second object that can be used in a game in association with the first object, and a step of associating the acquired second object with the first object. There is a game program.

Another aspect of the present invention is a game processing method executed by a computer, comprising the steps of obtaining a first object to be used in a game, obtaining a second object that is associated with the first object and usable in the game, and associating the obtained second object with the first object, wherein in the associating step, the obtained second object can be associated with the obtained first object, and can also be used with the unobtained first object after the first object is obtained. A game processing method that allows pre-association.

Further, one aspect of the present invention includes a first acquisition unit that acquires a first object to be used in a game, a second acquisition unit that acquires a second object that is associated with the first object and that can be used in the game, and an associating unit that associates the acquired second object with the first object, wherein the associating unit can associate the acquired second object with the acquired first object, and can also be used with the unacquired first object after the acquisition of the first object. It is a game device that is possible.

The figure which shows an example of the data regarding the player character which concerns on embodiment. The figure which shows an example of the setting data of the cheering song which concerns on embodiment. The figure which shows an example of the cheering song menu screen which concerns on embodiment. The figure which shows an example of the support music allocation screen which concerns on embodiment. The figure which shows an example of the cheering song manual setting screen which concerns on embodiment. FIG. 10 is a diagram showing an example of an assigned song selection screen according to the embodiment; FIG. The figure which shows an example of the assigned music determination screen which concerns on embodiment. The figure which shows an example of the cheering music manual setting screen after assigning the cheering music which concerns on embodiment. The block diagram which shows an example of a structure of the game system which concerns on embodiment. The figure which shows an example of the hardware constitutions of the terminal device which concerns on embodiment. The figure which shows an example of the functional structure of the terminal device which concerns on embodiment. The figure which shows an example of the character data which concerns on embodiment. The figure which shows an example of the possession character data which concerns on embodiment. The figure which shows an example of the cheering music setting data which concerns on embodiment. 4 is a flowchart showing an example of player character acquisition processing according to the embodiment; 4 is a flowchart showing an example of support song download processing according to the embodiment; 4 is a flowchart showing an example of support song creation processing according to the embodiment; 4 is a flowchart showing an example of support song setting processing according to the embodiment; 4 is a flowchart showing an example of support song reproduction processing according to the embodiment; FIG. 4 is a diagram showing data examples of character data before and after transfer according to the embodiment;

An embodiment of the present invention will be described below with reference to the drawings.
[Overview of game device]
First, an outline of an example of the game device according to the present embodiment will be described. The game device according to the present embodiment executes game processing that is played using a plurality of characters. A character is a person, an animal, an object (for example, a vehicle), etc. appearing in a game, and is displayed as an image (still image such as an illustration or photograph, moving image, etc.) on the game screen so that the user can recognize it. In this embodiment, a baseball game will be described as an example. A character in a baseball game is, for example, a player who forms a baseball team (a player who belongs to the team). A character representing a player is called a "player character". A team is composed of a collection (group) of a plurality of player characters.

In this embodiment, a baseball game will be described as an example, but the game is not limited to a baseball game, and may be a game based on other sports such as soccer, basketball, and rugby as long as it uses player characters. Each player character is associated with a game object representing the player character. Game objects are cards, medals, figures, etc., and are displayed as images on the game screen. For example, by obtaining and owning the player cards of each player character, the user can play a match with the opponent's team in the team including the player character of the player card selected from the player cards owned.

Also, the baseball game according to the present embodiment corresponds to, for example, a real baseball team and players belonging to the team. For example, team data of a team in a game using the team name of a team that actually exists is associated with player characters using the player names of the players that actually belong to the team. When the year changes and there is a change in the players belonging to the real team due to the transfer of players or the joining of new players, the team data of the team in the game will be updated according to the change. The team and player characters in the game are not limited to those corresponding to real teams and players, but may be those corresponding to fictitious teams and players, or those corresponding to real teams and players and fictitious teams and players may be mixed.

In addition, effects in the game can be set for the player characters. The production in the game is, for example, cheering songs. The cheering song is a song or music (song + poem) for cheering on a player, and is set for each player. For example, the cheering song may be a cheering song peculiar to each player (for example, a cheering song whose lyrics include the player's name), or a cheering song that does not specify the player. If a cheering song created by the user or a cheering song downloaded is set for a player character, the set cheering song is played back when the player character participates in a match. Here, an example of the effect of setting a cheering song to the player character will be described, but instead of or in addition to the cheering song, effects such as banners, cheering, sound effects, player introduction announcements, and changes in the display mode of the player character can also be set to the player character in the same way as the cheering song.

Here, the player characters include not only player characters of a plurality of different players (different player names), but also player characters of a plurality of types of the same player (same player name). For example, player characters that are the same player (same player name) but have different rarities are distinguished as different types of player characters. The rarity is an index indicating the rarity of the player card of each player character, and is one of the associated information preset for the player character. For example, one of N, R, and SR is set as rarity for player characters, and the rarity increases in the order of N, R, and SR, and the higher the rarity, the more difficult it is to obtain. A player character with a high rarity has higher abilities than a player character with a low rarity, and a player character with a high rarity is more likely to win the match.

In this way, when there are a plurality of types of player characters of the same player (same player name), it is inconvenient to set a cheering tune for each of the plurality of types of player characters when it is desired to set a cheering tune for one player. For example, it is assumed that after setting a cheering song for a player character owned by the user whose rarity is N, the player character of the same player (same player name) whose rarity is higher than N is obtained. In this case, it is inconvenient that the same cheering music set to the player character of rarity N must be set to the player character of rarity S again in order to reproduce the cheering song when the obtained player character of rarity S participates.

Therefore, in this embodiment, if a cheering song is set for one player character, the selected cheering song is applied not only to the player character but also to other types of player characters of the same player (same player name) as the player character. Specifically, as the data related to the player characters, in addition to identification information for identifying each player character (hereinafter referred to as "character ID"), identification information for performance such as cheering songs (hereinafter referred to as "description ID") is used. The performance ID is set as the same information for player characters with the same player name and as different information for player characters with different player names.

FIG. 1 is a diagram showing an example of data regarding player characters according to the present embodiment. As illustrated, the data about the player character is associated with at least a character ID, a player name, a rarity, and an effect ID. Here, data examples of three types of player characters whose player name is Player A and differ in rarity (N, S, SR) and two types of player characters whose player name is Player B and differ in rarity (N, SN) are shown. Since the character ID is identification information for identifying each player character, it is different information (CA1, CA2, CA3, CA4, CA5) for each player character. Player characters with character IDs CA1, CA2, and CA3 have the same player name (player A) but different rarities. Player characters with character IDs CA4 and CA5 have the same player name (player B) but different rarities. Since player characters with character IDs CA1, CA2 and CA3 and player characters with character IDs CA4 and CA5 have different player names (because they are not the same player), the IDs for presentation (EF1) of the player characters with character IDs CA1, CA2 and CA3 and the IDs (EF2) for player characters with character IDs CA4 and CA5 are different identification information. The game device sets a cheering song for the player character by associating the cheering song with the production ID.

FIG. 2 is a diagram showing an example of setting data for cheering songs according to the present embodiment. As shown in the figure, the support song setting data is associated with the performance ID and the support song. For example, when the user owns only the player character with the character ID of CA1 among the player characters with the character IDs of CA1, CA2, and CA3, the user sets cheering song A to the player character. In this case, the performance ID (EF1) associated with the character ID (CA1) of the player character shown in FIG. 1 is associated with the cheering song A desired by the user (see FIG. 2). As a result, cheering song A is reproduced when the player character whose character ID is CA1 participates in the game. Further, after that, when player characters having character IDs CA2 and CA3 are to be owned and made to participate in the game, cheering song A is already associated with the performance ID (EF1) associated with the character IDs (CA2 and CA3) of the player characters. Therefore, even if the cheering song A is not newly set for the player characters with the character IDs CA2 and CA3, the cheering song A is reproduced when the player characters with the character IDs CA2 and CA3 participate in the game.

In this way, in this embodiment, if a cheering song is set for one player character, the cheering song is set even if it is not separately set for other types of player characters having the same player name, so that the setting can be made with less effort and convenience can be improved.

Next, with reference to the game screen examples shown in FIGS. 3 to 8, the flow of operations when the user sets cheering songs for player characters will be described.
FIG. 3 is a diagram showing an example of a cheering song menu screen according to this embodiment. The illustrated cheering song menu screen G10 is an example of a game screen on which options for selecting various functions related to cheering songs are displayed. In a screen area GS11 of the cheering song menu screen G10, a ``notice'' button B11, a ``download cheering song'' button B12, a ``generating cheering song'' button B13, a ``assign cheering song'' button B14, and a ``shop'' button B15 are displayed as operation buttons for selecting various functions related to the cheering song.

When the "notification" button B11 is operated to select, the screen transitions to a notification screen that displays a notification to the user regarding the cheering song (for example, precautions regarding the use of the cheering song). When an operation to select the "download cheering song" button B12 is performed, a transition is made to a download screen for downloading each player's cheering song and each team's cheering song provided by the management side of the game. When an operation to select the "create cheering song" button B13 is performed, the screen transitions to a cheering song creating screen on which the user can create a cheering song or edit the created cheering song. When an operation to select the "assign cheering song" button B14 is performed, a transition is made to a cheering song assignment screen on which a cheering song can be set for the player character and conditions for reproducing the cheering song can be set. When the "shop" button B15 is operated to select, the screen transitions to a shop screen where usage rights for using the downloaded cheering songs can be purchased.

In addition, in the screen area GS12 of the cheering song menu screen G10, a "my page" button B1, a "game" button B2, an "order" button B3, a "player" button B4, a "home" button B5, and a "return" button B6 for transitioning to game screens related to functions other than various functions related to the cheering song are displayed. The "My Page" button B1 is an operation button for transitioning to a My Page screen on which user information of the user and information such as scores and points obtained by the user playing this baseball game are displayed. The "Match" button B2 is an operation button for executing a match process in which a team set by the user and another team compete in a match and transitioning to a match screen. The "order" button B3 is an operation button for transitioning to an order setting screen for the user to set the starting members and bench members of his/her own team. The "Player" button B4 is an operation button for transitioning to a player list screen on which a list of a plurality of player characters prepared in the game, a list of player characters owned by the user, and the like are displayed. The "home" button B5 is an operation button for transitioning to the home screen of this baseball game. The home screen is the main game screen that serves as the center (topmost) of operations for transitioning to various game screens in this baseball game, and displays an operation button for transitioning to this cheering song menu screen G10, an operation button for executing a lottery process for the user to obtain a player character, and furthermore, the above-described "My Page" button B1, "Game" button B2, "Order" button B3, "Player" button B4, and the like. Also, the "return" button B6 is an operation button for returning to the game screen before transition to the currently displayed game screen.

For example, on the cheering song menu screen G10, when an operation to select the "assisting song assignment" button B14 is performed, the screen transitions to the cheering song assignment screen G20 shown in FIG.
FIG. 4 is a diagram showing an example of a cheering song assignment screen according to this embodiment. In the screen area GS21 of the cheering song assignment screen G20 shown, an "assign to each batter" button B21, an "automatic assignment" button B22, and a "condition setting" button B23 are displayed. The "assign to each batter" button B21 is an operation button for transitioning to the cheering song manual setting screen G30 (see FIG. 5) where the cheering song can be manually selected and set for each player (each batter). The "automatic assignment" button B22 is an operation button for automatically setting cheering songs for each player (batter). The "condition setting" button B23 is an operation button for transitioning to a reproduction condition setting screen on which conditions for reproducing the set cheering song can be set. As the conditions for reproducing cheering songs, for example, one or more of home games, visitor games, innings, various chances, scores, and victories can be selected. For example, when a player character appears during a game and satisfies the scrutinized condition, the cheering song set for the player character is played.

In addition, in the screen area GS22 of the cheering song assignment screen G20, similarly to the cheering song menu screen G10 shown in FIG.

FIG. 5 is a diagram showing an example of a cheering song manual setting screen according to the present embodiment. When the "assign to each batter" button B21 is operated on the cheering song menu screen G10, the screen transitions to the illustrated cheering song manual setting screen G30. On the cheering song manual setting screen G30, the user can manually select and set a cheering song for each player (each batter). In the screen area GS31 of the cheering song manual setting screen G30, the team name (here, team α) and the team mark (primary mark, symbol mark, logo mark, etc.) are displayed as information indicating the team whose cheering song is set on the current screen. In the screen area GS32, the team marks of each team are arranged side by side and have a function as a selectable operation button so that the teams for which cheering songs are set can be switched. In the illustrated example, the team mark of team α (the team mark indicated by symbol B31) is selected in the screen area GS32. For example, in the screen area GS32, when an operation is performed to select the team mark of the team β (the team mark indicated by the symbol B32), the information indicating the team in the screen area GS31 becomes the information indicating the team β, making it possible to select and set cheering songs for players belonging to the team β.

In the illustrated example, since team α is selected, it is possible to select and set cheering songs for players belonging to team α. In the screen area GS33, the player names of the players belonging to the team α and the setting status of cheering songs for each player are displayed in association with each other. Here, since the cheering song has not yet been set for any player, "unset" is displayed as the setting status of the cheering song for each player. If all the players belonging to the team α cannot be displayed in the screen area GS33 at once, only some of the players are displayed, and all the players can be displayed in order by scrolling. Further, the display switching button B33 alternately switches between "filter OFF" and "filter ON" each time it is operated. In the "filter OFF", the player names of all the players belonging to the team α and the setting status of cheering songs are displayed in the screen area GS33. On the other hand, in the "filter ON", the names of only the players belonging to the team α whose player characters are owned by the user and the settings of cheering songs are displayed in the screen area GS33.

Here, it is possible to allocate and set cheering songs for athletes for whom the user owns athlete characters (at least one kind of athlete character) and athletes for whom the user does not own any athlete characters (does not own any kind of athlete character). In other words, it is possible to set a cheering song in advance even for a player whose player character does not own any kind of player character. When the player character of the player is obtained, the previously set cheering music is applied to the player character of any type (rarity) without setting the cheering music again. It should be noted that the configuration may be such that the user can set cheering songs only for players who own player characters (at least one type of player character).

In addition, each player name of each player displayed in the screen area GS33 functions as a selectable operation button for each icon itself displayed. For example, when player A (player name indicated by symbol B34) is selected, the screen transitions to an assigned song selection screen G40 (see FIG. 6) on which a cheering song to be assigned to player A can be selected.

In the screen area GS34 of the cheering song manual setting screen G30, similarly to the cheering song menu screen G10 shown in FIG. 3 and the cheering song assignment screen G20 shown in FIG.

FIG. 6 is a diagram showing an example of an assigned song selection screen according to this embodiment. The illustrated assigned song selection screen G40 is a screen that transitions when an operation is performed to select player A (player name indicated by reference symbol B34) on the cheering song manual setting screen G30, and the screen area GS41 is displayed superimposed on the cheering song manual setting screen G30 shown in FIG. A list of cheering songs that can be assigned to player A is displayed in the screen area GS41. When the tab TB41 is selected, a list of cheering songs created by the user is displayed, and when the tab TB42 is selected, a list of downloaded cheering songs is displayed. In the illustrated example, the tab TB41 is selected, and cheering song A, cheering song B, cheering song C, and cheering song D are displayed as a list of cheering songs created by the user. Each of the cheering song A, the cheering song B, the cheering song C, and the cheering song D functions as an operation button that can be selected by each icon itself on which each is displayed. For example, when an operation is performed to select cheering song A (supporting song indicated by symbol B41), cheering song A is selected as a cheering song to be assigned to player A, and the assigned song determination screen G50 shown in FIG. 7 is displayed. The "Cancel" button B42 is an operation button for canceling the selection of player A and returning to the cheering song manual setting screen G30.

FIG. 7 is a diagram showing an example of an assigned song determination screen according to this embodiment. The assigned song determination screen G50 shown in the figure is a screen for receiving an operation to decide the cheering song to be assigned to the player, and the screen area GS51 is superimposed on the cheering song manual setting screen G30 shown in FIG. The screen area GS51 displays the selected player (player A) and the selected cheering song (supporting song A). When an operation to select the "play" button B51 is performed, the cheering song A is played. This allows the user to preview the currently selected cheering song before determining the cheering song to be assigned. When an operation to select the "OK" button B52 is performed, cheering song A is determined as the cheering song to be assigned to player A. According to this operation, the performance ID (EF1) associated with the player character of player A is associated with cheering song A (see FIG. 2). On the other hand, when the "Cancel" button B53 is operated to select, the selection of Supporting Song A is cancelled, and the screen returns to the assigned song selection screen G40.

Also, when an operation to select the "OK" button B52 is performed on the assigned song determination screen G50, the cheering song to be assigned to player A is determined as cheering song A, and then the screen returns to the cheering song manual setting screen. FIG. 8 is a diagram showing an example of a cheering song manual setting screen after assigning cheering song A to player A. FIG. The cheering song manual setting screen G60 shown in FIG. 5 has the same basic display items as the cheering song manual setting screen G30 shown in FIG.

In this way, the user can set cheering songs for any player of any team.

[Configuration of game system]
Next, the configuration of the game system according to this embodiment will be described.
FIG. 9 is a block diagram showing an example of the configuration of the game system 1 according to this embodiment. The game system 1 comprises a plurality of terminal devices 10-1, 10-2, . Since the terminal devices 10-1, 10-2, .

The terminal device 10 functions as a game device by executing a game control program. For example, the terminal device 10 is a computer device used by a user, and can be a game machine, a PC (Personal Computer), a tablet PC, a mobile phone such as a smart phone or a feature phone, or the like.

The server device 30 manages game data and a game control program necessary for executing the game control program on the terminal device 10 . For example, the server device 30 is a computer device managed by a game operating company, and can be regarded as a system composed of a plurality of server machines, storages, network switches, routers/firewalls, and the like. The game data managed by the server device 30 is used when the terminal device 10 executes the game control program, or is transmitted to the terminal device 10 in advance and used. The game data also includes advertisement data (information on other games) displayed during the game. For example, an image displayed on the screen (game screen) of the terminal device 10 includes part of the game data. The game control program managed by the server device 30 includes a part of the game control program. The game control program includes not only those downloaded to the terminal device 10 before starting the game, but also those downloaded to the terminal device 10 after starting the game. Note that the game control program downloaded to the terminal device 10 before starting the game may be managed by a server device that distributes programs that operate on the terminal device 10 instead of the server device 30 .

[Hardware Configuration of Game Device]
Next, the hardware configuration of the terminal device 10 as a game device according to this embodiment will be described.
FIG. 10 is a diagram showing an example of the hardware configuration of the terminal device 10 according to this embodiment. The terminal device 10 includes, for example, a communication section 11 , an input section 12 , a display section 13 , an audio output section 14 , a storage section 15 and a CPU (Central Processing Unit) 16 .

The communication unit 11 is a device that performs communication conforming to the communication standard of the communication network NW such as wireless LAN, wired LAN, mobile communication (LTE), etc., with which the terminal device 10 and the server device 30 can communicate.

The input unit 12 is an input device capable of receiving operation information based on a user's operation on the terminal device 10 . For example, the input unit 12 is configured integrally with a display as a touch panel. The input unit 12 receives operation information based on user's operation on the touch panel, and outputs an operation signal based on the operation information to the CPU 16 . In place of or in addition to the touch panel, the input unit 12 may include other input devices such as physical input devices such as buttons, keyboards, and levers, pointing devices such as mice and touch pads, and voice and gesture recognition devices (microphones, cameras).

The display unit 13 is a display that displays information such as images and texts, and includes, for example, a liquid crystal display panel, an organic EL (Electro Luminescence) display panel, and the like. Note that the display unit 13 may be configured separately from the terminal device 10, and may be, for example, a television, an external monitor, or a head-mounted display (HMD).

The audio output unit 14 includes, for example, a speaker, an audio output terminal for outputting audio to headphones or the like, and the like.

The storage unit 15 includes, for example, a HDD (Hard Disk Drive), an SSD (Solid State Drive), an EEPROM (Electrically Erasable Programmable Read-Only Memory), a ROM (Read-Only Memory), a RAM (Random Acc ESS Memory), etc., and stores various information, images, programs, etc. used for processing by the terminal device 10 . Note that the storage unit 15 is not limited to being built in the terminal device 10, and may be an external storage device connected via a digital input/output port such as a USB.

The CPU 16 executes various programs stored in the storage section 15 and controls each section of the terminal device 10 . Note that the CPU 16 is an example of a processor that executes processing in the terminal device 10 .

The terminal device 10 may include a camera, a gyro sensor, and a GPS (Global Positioning System) chip (not shown).

[Functional Configuration of Game Device]
FIG. 11 is a diagram showing an example of the functional configuration of the terminal device 10 according to this embodiment. In this diagram, a data storage unit 150 and a game control unit 160 are shown as the functional configuration of the terminal device 10 . The data storage unit 150 has a functional configuration corresponding to the storage unit 15 shown in FIG. 10 . The game control unit 160 is a functional configuration realized by the CPU 16 executing the game control program stored in the storage unit 15 .

The data storage unit 150 includes, for example, a character data storage unit 151, a user data storage unit 152, an owned character data storage unit 153, a cheering song data storage unit 154, and a cheering song setting data storage unit 155.

The character data storage unit 151 stores character data of a plurality of player characters prepared for the game. FIG. 12 is a diagram showing an example of character data stored in the character data storage unit 151. As shown in FIG. Note that this character data is a specific example corresponding to the data relating to the player character shown in FIG. Character ID, player name, team ID, rarity, performance ID, character image, ability, etc. of the player character are associated with the illustrated character data D151. The team ID is identification information for identifying the team to which the player character belongs. Specifically, different character IDs such as CA1, CA2, CA3, CA4, and CA5 are set for each of the types of player characters as different types of player characters having at least one of different player names or rarities. Player characters with character IDs CA1, CA2, and CA3 have different rarities but have the same player name (player A), so the same effect ID (EFA1) is associated with the character IDs CA1, CA2, and CA3. Also, player characters with character IDs CA4 and CA5 have different rarities but have the same player name (player B), so the same effect ID (EFA2) is associated with the character IDs CA4 and CA5. In the example shown in FIG. 1, the effect IDs were EF1, EF2, . . . , but here, EFA1, EFA2, . If the team to which the player belongs changes due to a transfer or the like, the character ID and the production ID also change (details will be described later).

A character image is an image related to a player character, and includes a player image of the player character (for example, a picture or illustration of the player), an image for displaying information (such as rarity) for each player character, and the like. The ability is a parameter indicating ability such as offensive power and defensive power of each player character. The character data that is the basis of the character data D151 is managed by the server device 30, and is acquired from the server device 30 and stored when the game is first started on the terminal device 10. FIG. Further, when the character data managed by the server device 30 is changed (for example, when the player belonging to the team is changed due to the player's transfer or joining the team), the terminal device 10 acquires the updated character data from the server device 30 and updates the character data D151.

User data of a user who uses the terminal device 10 is stored in the user data storage unit 152 . The user data is associated with a user ID, which is identification information for identifying the user, a user name indicating the name of the user in the game, and the like. User data is also associated with data such as coins, medals, points, tickets, or items acquired by the user in the game. Note that this user data may be transmitted to the server device 30 and the user data of a plurality of users may be managed by the server device 30 .

The owned character data storage unit 153 stores character data of owned characters obtained by the user through a lottery or the like among a plurality of player characters prepared in the game. For example, the lottery process is performed by the server device 30, and the character data of the owned character is added by acquiring the lottery result (data of the player character selected by lottery) from the server device 30. FIG. FIG. 13 is a diagram showing an example of possessed character data stored in possessed character data storage unit 153. As shown in FIG. The illustrated possessed character data D153 is associated with the user ID of the user, the serial number and character ID of the player character owned by the user, the ability of the player character, and the like. The serial number is a number uniquely assigned to each owned player character, and is information that can identify each player character in the game. Even if the player characters have the same character ID, if a plurality of player characters are owned, they are assigned different serial numbers and associated with each other. Also, the ability stores the ability value of the character data D151 of the player character when the player character is given to the user (for example, when the player character is given to the user by lottery). The ability values of the possessed character data D153 are updated at any time as the game progresses. Note that the player name, team ID, rarity, character image, performance ID, and the like may also be associated with the user ID, serial number, character ID, and the like in the possessed character data D153. The owned character data D153 may be transmitted from the terminal device 10 to the server device 30, and the owned character data of a plurality of users may be managed by the server device 30 in association with each user (each user ID).

The cheering song data storage unit 154 stores data of cheering songs downloaded by the user and data of cheering songs created by the user. For example, cheering song data is data in a file format predetermined in the game, and can be uniquely identified by the file name of each data. The data of the downloaded cheering song and the data of the cheering song created by the user are stored so as to be distinguished from each other by flag information or the like.

The cheering song setting data storage unit 155 stores cheering song setting data indicating the setting status of cheering songs for players (player characters). FIG. 14 is a diagram showing an example of cheering song setting data stored in the cheering song setting data storage unit 155. As shown in FIG. This cheering song setting data is a specific example corresponding to the cheering song setting data shown in FIG. The cheering song setting data D155 shown in the figure is associated with an effect ID and a cheering song. The effect ID corresponds to the effect ID associated with each character ID in the character data D151 shown in FIG. The file name of the cheering song stored in the cheering song data storage unit 154 is stored in the cheering song. For example, when cheering music A is assigned to player A according to the operation flow for setting cheering music for a player (player character) described with reference to FIGS. Also, in the drawing, "null" is described as the cheering song for the performance ID "EFA3", which indicates that no cheering song is set for the performance ID "EFA3". It should be noted that an effect ID for which no cheering song is set may not be included in the cheering song setting data D155, and may be stored at the time of setting.

Returning to FIG. 11, the game control unit 160 includes an operation reception unit 161, a display control unit 162, a character acquisition unit 163 (an example of a first acquisition unit), a cheering song creation processing unit 164, a cheering song data acquisition unit 165 (an example of a second acquisition unit), a cheering song setting unit 166 (an example of an association unit), a match processing unit 167, and an effect processing unit 168.

The operation reception unit 161 acquires an operation signal based on the operation on the input unit 12 . For example, the operation reception unit 161 acquires operation signals from the input unit 12 based on user operations on various game screens (see FIGS. 3 to 8) described above.

The display control unit 162 controls display on the display unit 13 . For example, the display control unit 162 generates images to be displayed on the various game screens (see FIGS. 3 to 8) described above by referring to data stored in the data storage unit 150, and displays them on the display unit 13. The display control unit 162 controls the generated images to be displayed on various game screens based on the operation signal acquired by the operation reception unit 161, and controls to transition to various game screens based on the user's operation.

The character acquisition unit 163 acquires character data of a plurality of player characters prepared for the game from the server device 30 and stores them in the character data storage unit 151 so that the terminal device 10 can use them. When the character data is updated by the server device 30 , the update data is acquired according to the instruction from the server device 30 and the data in the character data storage unit 151 is updated. The update data may be only some character data (data to be updated) of the plurality of player characters prepared in the game, or may be all character data.

In addition, the character acquisition unit 163 acquires the player character discharged through the character lottery process. This character lottery process is a process of drawing lots for a player character to be given to the user from among a plurality of player characters prepared in the game. Hereinafter, the character lottery process is simply referred to as "lottery process". This lottery process is performed by the server device 30 . Character acquisition unit 163 transmits a lottery request signal for requesting lottery processing to server device 30 based on a user's operation (an operation for executing a lottery). When the server device 30 acquires the lottery request signal, it executes lottery processing and transmits the lottery result (information including the character ID of the discharged player character) to the terminal device 10 that has transmitted the lottery request signal. When the character acquisition unit 163 acquires the lottery result from the server device 30, the character ID of the player character discharged in the lottery and the user ID are associated with each other, and are additionally stored in the possessed character data D153 (see FIG. 13) stored in the possessed character data storage unit 153. Thereby, the terminal device 10 manages the player character discharged by lottery as an owned character.

The cheering song creation processing unit 164 generates cheering song data based on the user's operation. For example, on the cheering song creation screen to which the user selects the "create cheering song" button B13 on the cheering song menu screen G10 shown in FIG. 3, the user performs an operation for creating a cheering song or editing the created cheering song. The cheering song that can be created by the cheering song creation processing unit 164 may be, for example, a cheering song that does not contain any poems.

The cheering song data acquisition unit 165 acquires the data of the cheering song generated by the cheering song creation processing unit 164 and stores it in the cheering song data storage unit 154 . Also, the cheering song data acquisition unit 165 downloads and acquires the data of the cheering song, and stores it in the cheering song data storage unit 154 . For example, on the download screen to which the user selects and downloads a cheering song from a list of downloadable cheering songs on the download screen to which the user selects the "download cheering song" button B12 of the cheering song menu screen G10 shown in FIG. The download source may be the server device 30, or may be a server device other than the server device 30 (that is, a server device different from the server device that provides the game data and the game control program). In addition, the cheering song data acquisition part 165 associates each data with different flag information or the like so as to distinguish the cheering song data generated by the cheering song creation processing part 164 from the downloaded cheering song data, and stores them in the cheering song data storage part 154.例文帳に追加

The cheering song setting unit 166 sets cheering songs for athletes (athlete characters). Specifically, the cheering song setting unit 166 refers to the character data D151 (see FIG. 12) in which the character ID for identifying each player character and the effect ID for each player character are associated, and based on the user's operation, associates the cheering song that can be set for each of the plurality of player characters with the effect ID associated with the character ID for each player character. For example, when an operation is performed to assign cheering song A to player A according to the flow of operations for setting cheering songs for athletes (player characters) described with reference to FIGS.

Note that the cheering song setting unit 166 can associate the performance ID associated with the character ID of each player character with the cheering song based on the user's operation, regardless of whether the player character has a character ID associated with the user ID (that is, the player character that has been acquired by the user) or the player character that does not have a character ID associated with the user ID (that is, the player character that has not been acquired by the user) among the plurality of player characters prepared in the game.

The match processing unit 167 executes the process of a match using player characters owned by the user (owned characters). For example, the match processing unit 167 executes processing of a match between a team including a player character selected by the user from owned characters and an opponent team. The order of the user's team (starting members, bench members, batting order, etc.) can be set by the user by performing an operation of selecting the "order" button B3. Specifically, the game processing unit 167 advances the game in the same order as the flow of an actual baseball game, in which the players (starting members) are introduced, the top of the first inning, the bottom of the first inning, and so on. The game processing unit 167 causes each player character to appear at bat according to a preset order in each attack. Also, the game processing unit 167 ends the game when the game is won or lost based on the progress of the game, and generates a game result. The match processing unit 167 generates an image corresponding to the progress of the match as the match progresses, and causes the display unit 13 to display the image as a game screen image during the match through the display control unit 162 .

When each of the plurality of player characters has satisfied a predetermined condition based on the progress of the game, the effect processing unit 168 reproduces cheering music set for the player character who has satisfied the predetermined condition. For example, the production processing unit 168 refers to the character data D151 (see FIG. 12) and the cheering song setting data D155 (see FIG. 14), and reproduces the cheering song associated with the production ID associated with the character ID of the player character who satisfies the predetermined condition. Here, the predetermined condition is a condition set in advance as a condition for reproducing the support music of the player character, for example, when the player character appears, when the player character is introduced (before the start of the game, etc.), when the batting turn comes around, when the batting turn comes around in a specific offensive inning (for example, the 7th inning), when a hit or home run is hit, when a score is scored, and the like.

[Operation of game processing]
Next, the operation of game processing executed by the CPU 16 of the terminal device 10 based on the game control program will be described.
First, with reference to FIG. 15, the operation of player character acquisition processing for acquiring a player character discharged by lottery by the CPU 16 will be described. FIG. 15 is a flowchart showing an example of player character acquisition processing according to the present embodiment.

The CPU 16 acquires player characters to be used in the game. Specifically, the CPU 16 transmits a lottery request signal requesting the lottery process to the server device 30 based on the user's operation (operation for executing the lottery) (step S100). By transmitting a lottery request signal to the server device 30, the CPU 16 acquires from the server device 30 the lottery result of the lottery processing executed by the server device 30 (information including the character ID of the discharged player character) (step S102).

When the CPU 16 acquires the result of the lottery from the server device 30, the CPU 16 associates the character ID of the player character discharged by lottery with the user ID, and adds and stores them to the possessed character data D153 (see FIG. 13) stored in the possessed character data storage unit 153 (step S104). Thereby, the CPU 16 can use the player character discharged by lottery as an owned character in the game.

Next, referring to FIG. 16, the operation of the cheering song download process in which the CPU 16 acquires cheering songs by downloading will be described. FIG. 16 is a flowchart showing an example of support song download processing according to the present embodiment. Here, it is assumed that the server apparatus 30 is the download source of the cheering songs.

The CPU 16 acquires cheering music that can be used in the game in association with the player character. For example, the CPU 16 transmits a download request signal requesting download of the cheering song to the server device 30 based on the user's operation (the operation of downloading the cheering song) (step S110). The operation of downloading a cheering song is, for example, an operation of selecting the "download cheering song" button B12 shown in FIG. On a download screen transitioned by an operation of selecting a ``download cheering song'' button B12, a user selects and downloads a cheering song from a list of downloadable cheering songs, and in response to the operation, a CPU 16 downloads and acquires data of the selected cheering song (step S112).

When the CPU 16 downloads and acquires the cheering song data from the server device 30, the CPU 16 stores the downloaded cheering song data in the cheering song data storage unit 154 in association with flag information indicating the downloaded cheering song (step S114).

Next, with reference to FIG. 17, the operation of the cheering song creation process in which the CPU 16 acquires the cheering song created by the user will be described. FIG. 17 is a flow chart showing an example of support song creation processing according to the present embodiment.

The CPU 16 acquires cheering music that can be used in the game in association with the player character. For example, the CPU 16 generates cheering song data based on a user's operation (an operation for creating a cheering song) (step S120). For example, when the user performs an operation of creating a cheering song or editing the created cheering song on the cheering song creation screen to which the user selects the "create cheering song" button B13 on the cheering song menu screen G10 shown in FIG. Then, the CPU 16 acquires the data of the generated cheering song (step S122).

When acquiring the generated cheering song data, the CPU 16 stores the acquired cheering song data in the cheering song data storage unit 154 in association with the flag information indicating the created cheering song (step S124).

Next, referring to FIG. 18, the CPU 16 will explain the operation of the cheering song setting process for setting the cheering song to the player (player character). FIG. 18 is a flowchart showing an example of support song setting processing according to the present embodiment.

The CPU 16 selects a player (player character) for which cheering songs are set (assigned) (step S150). For example, in the cheering song manual setting screen G30 shown in FIG. 5, when an operation is performed to select player A (player name indicated by symbol B34), the CPU 16 selects player A as a player to set (assign) a cheering song. Then, the CPU 16 causes the screen to transition to an assigned song selection screen G40 (see FIG. 6) on which a cheering song to be assigned to player A can be selected.

The CPU 16 selects a cheering song to be assigned to the selected player (for example, player A) (step S152). For example, when an operation to select cheering song A (player name indicated by symbol B34) is performed on the assignment song selection screen G40 shown in FIG.

Then, the CPU 16 associates and stores the effect ID of the player (for example, player A) selected in step S150 and the cheering song (for example, cheering song A) selected in step S152 (step S154). For example, referring to the character data D151 (see FIG. 12) stored in the character data storage unit 151, the performance ID (e.g., EFA1) associated with the character ID (e.g., CA1) of the player (e.g., player A) selected in step S150 is associated with the cheering song (e.g., cheering song A) selected in step S152, and stored in cheering song setting data D155 stored in the cheering song setting data storage unit 155.

Next, with reference to FIG. 19, the operation of cheering song reproduction processing (effect execution processing) for playing cheering music set for a player (player character) by the CPU 16 will be described. FIG. 19 is a flow chart showing an example of support song reproduction processing according to the present embodiment.

The CPU 16 determines whether or not the game process has started (step S200). When the CPU 16 determines that the game process has not started (NO), the process of step S200 is performed again. On the other hand, when the CPU 16 determines that the game process has started (YES), it determines whether each of the plurality of player characters has satisfied a predetermined condition based on the progress of the game (step S202). A predetermined condition is, for example, the appearance of a player character in a match.

When the CPU 16 determines that the predetermined condition is satisfied (YES), the CPU 16 refers to the character data D151 (see FIG. 12) and the cheering song setting data D155 (see FIG. 14), and reproduces the cheering song associated with the production ID associated with the character ID of the player character who satisfies the predetermined condition (step S204). Then, the process proceeds to step S206. On the other hand, when the CPU 16 determines that the predetermined condition is not satisfied (NO), it proceeds to the process of step S206 without performing the process of step S204.

In step S206, the CPU 16 determines whether or not the game process has ended. When the CPU 16 determines that the game process has not ended (NO), it returns to the process of step S202 and determines whether or not the predetermined condition is satisfied. On the other hand, when the CPU 16 determines that the match processing has not ended (NO), it ends the cheering song reproduction processing.

[Data update at the time of team transfer of player character]
Also, in the character data D151 shown in FIG. 12, each of the character IDs of a plurality of players is associated with the team ID of the team to which each player belongs. When a player transfers teams (for example, when a player transfers to a team that actually exists and character data is updated in accordance with the game), the character ID of the transferred player character and the performance ID associated with the character ID are each changed to new identification information different from that before the transfer, and associated with the team ID of the transfer destination team.

FIG. 20 is a diagram showing data examples of character data before and after transfer. Character data D151-1 indicates an example of character data of player characters of player A and player B belonging to team α before the transfer. On the other hand, character data D151-2 shows an example of character data after player A transfers from team α to team β.

In the illustrated example, there are three types of player characters for player A, each having a different rarity. As shown in character data D151-1, the character IDs of the three types of player characters of player A before transfer are "CA1", "CA2", and "CA3", respectively. Each character ID of "CA1", "CA2", and "CA3" is associated with the team ID of team α. Also, since the player characters of these three types of player A have the same player name (player A), the same performance ID "EFA1" is associated with each of the character IDs of "CA1", "CA2" and "CA3".

On the other hand, as shown in the character data D151-2, after the player A transfers from the team α to the team β, the character IDs of the three types of player characters of the player A become 'CB1', 'CB2' and 'CB3', respectively, and are updated to identification information different from that before the transfer. Each of "CB1", "CB2", and "CB3" is associated with the team ID of team β. In addition, the character IDs of "CB1", "CB2", and "CB3" are associated with the same effect ID "EFB1", which is updated to a different effect ID than before the transfer.

In this way, even if the player character is the same before the transfer and after the transfer, it is necessary to distinguish it as a player of a different team (for example, the uniform of the team is different), so different character IDs are set. Also, if the team changes, the performance contents such as cheering songs will also be different. Therefore, even for the same player character, different performance IDs are set before and after the transfer.

[Summary of embodiment]
As described above, the terminal device 10 (an example of a game device) according to the present embodiment executes game processing using a plurality of player characters. The terminal device 10 refers to data associated with a character ID (an example of first identification information) for identifying each of a plurality of player characters including a plurality of types of player characters with the same player name and player characters with different player names, and a cheering song ID (an example of second identification information), which is set as identification information for a cheering song (an example of performance) for each player character, the same information for player characters with the same player name and different information for player characters with different player names. A cheering song that can be set for each character is associated with a cheering song ID associated with the character ID of each player character. Then, when each of the plurality of player characters satisfies a predetermined condition based on the progress of the game, the terminal device 10 performs processing (for example, reproduction of the cheering song) according to the cheering song associated with the cheering song ID associated with the character ID of the player character satisfying the predetermined condition.

As a result, the terminal device 10 can set cheering music as a performance of a player character satisfying a predetermined condition with one operation for all the player characters of the same player (same player name) of a plurality of kinds, so that the convenience of game setting can be improved.

In addition, the terminal device 10 processes a match using a player character (that is, a player character owned by the user) whose character ID (an example of first identification information) is associated with a user ID (an example of third identification information) for identifying the user among the plurality of player characters. Then, the terminal device 10 can associate the cheering song ID (an example of the second identification information) associated with the character ID of each player character with the cheering song (an example of rendering) based on the user's operation for both player characters whose user IDs are associated with character IDs and player characters whose user IDs are not associated with character IDs.

As a result, the terminal device 10 can set cheering songs in advance even for player characters that the user has not yet owned (for example, the user's favorite player character), so that it is possible to further increase the desire to obtain player characters that have not been acquired and to increase the motivation to play the game. In addition, by setting the cheering music in advance, even if the cheering music is not set again when acquiring and using an unacquired player character, the cheering music is reproduced according to the satisfaction of a predetermined condition, so that the convenience of setting the game can be improved.

In addition, each character ID (an example of first identification information) for identifying player characters of a plurality of players is associated with a team ID (an example of fourth identification information) for identifying the team to which each player belongs. Then, in the terminal device 10, when a player transfers teams, the character ID for identifying the player character of the player and the performance ID (an example of the second identification information) associated with the character ID are each changed to new identification information different from that before the transfer, and associated with the team ID of the transfer destination team.

As a result, the terminal device 10 can prevent the cheering song set before the transfer from being reproduced at the transfer destination when the player transfers teams.

Moreover, according to the above-described embodiment, the following configuration can also be considered. For example, the terminal device 10 acquires a player character (an example of a first object) to be used in a game, and also acquires cheering music (an example of a second object) that can be used in the game in association with the player character. In addition, the terminal device 10 associates the acquired cheering song with the player character. Then, the terminal device 10 can associate the acquired cheering music with the acquired player character, and can also associate with the unacquired player character in advance so that it can be used after the player character is acquired.

As a result, the terminal device 10 can set cheering music in advance even for a player character that has not yet been acquired, so that when acquiring and using an unacquired player character, the cheering music associated with the player character can be used without setting the cheering music again. Therefore, the convenience of setting the game can be improved.

Note that the second object may be a production (banner, cheering, sound effect, player introduction announcement, change in player character display mode, etc.) other than cheering music.

[Modification]
Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to the above-described embodiments, and includes design and the like within the scope of the gist of the present invention. For example, the configurations described in the above embodiments can be combined arbitrarily.

Further, in the above embodiment, an example has been described in which player characters of the same player (same player name) but of different rarities are distinguished as different types of player characters, but the rarity is not limited. Player characters that are the same player (same player name) but have at least part of the associated information preset for the player character different may be distinguished as different types of player characters. For example, the incidental information is information that is set in advance in association with the player character, and is fixed information that does not change as the game progresses. The incidental information may include, in addition to the rarity, basic properties, attributes such as personality, special skills, and the like.

Also, in the above-described embodiment, the example of the game using player characters has been described by taking the baseball game as an example, but the present invention is not limited to this. For example, it can also be applied to games using other types of characters, such as battle games and RPG games. For example, characters used in the game are not limited to player characters, and may be characters such as warriors, explorers, and adventurers. Also, a character may be associated with an effect, or may be associated with an item or the like in addition to the effect. For example, the terminal device 10 may acquire a character (an example of a first object) used in a game, acquire an item (an example of a second object) that can be used in the game in association with the character, and associate the acquired item with the character. The terminal device 10 may be able to associate an acquired item with an acquired character, and may also be able to associate an unacquired character in advance so that the item can be used after the character is acquired. Here, the items may be weapons, armor, etc. that can be equipped by warriors, explorers, adventurers, and the like. A character used in a game may be an object (for example, a vehicle), or may be a car used in a game themed on car racing, for example. In this case, the terminal device 10 acquires a car (an example of a first object) used in the game, acquires an item (an example of a second object) that can be used in the game in association with the car, and associates the acquired item with the car. The terminal device 10 may be able to associate the acquired item with an already acquired car, and may also be able to pre-associate with an unacquired car so that the item can be used after the car is acquired. Here, the items may be various parts (parts that affect performance) such as tires, suspensions, and steering wheels that can be installed on the vehicle.

Alternatively, a program for realizing the functions of the game control unit 160 described above may be recorded in a computer-readable recording medium, and the program recorded in the recording medium may be read by a computer system and executed by the game control unit 160. Processing as the game control unit 160 may be performed. Here, "loading and executing the program recorded on the recording medium into the computer system" includes installing the program in the computer system. The "computer system" here includes hardware such as an OS and peripheral devices. A "computer system" may also include a plurality of computer devices connected via a network including communication lines such as the Internet, WAN, LAN, and dedicated lines. The term "computer-readable recording medium" refers to portable media such as flexible discs, magneto-optical discs, ROMs and CD-ROMs, and storage devices such as hard discs incorporated in computer systems. Thus, the recording medium storing the program may be a non-transitory recording medium such as a CD-ROM. Recording media also include internal or external recording media accessible from the distribution server for distributing the program. The program code stored in the recording medium of the distribution server may be different from the program code in a format executable by the terminal device. That is, as long as it can be downloaded from the distribution server and installed in a form that can be executed on the terminal device, the form stored in the distribution server does not matter. It should be noted that the program may be divided into a plurality of parts, and the divided programs may be downloaded at different timings and then merged in the terminal device, or the distribution servers that distribute the divided programs may be different. Furthermore, "computer-readable recording medium" includes those that hold the program for a certain period of time, such as the volatile memory (RAM) inside the computer system that acts as a server or client when the program is transmitted via a network. Further, the program may be for realizing part of the functions described above. Further, it may be a so-called difference file (difference program) that can realize the above functions by combining with a program already recorded in the computer system.

Also, some or all of the functions of the game control unit 160 described above may be implemented as an integrated circuit such as an LSI (Large Scale Integration). Each of the functions described above may be individually processorized, or part or all of them may be integrated and processorized. Also, the method of circuit integration is not limited to LSI, but may be realized by a dedicated circuit or a general-purpose processor. In addition, when an integration circuit technology that replaces LSI appears due to advances in semiconductor technology, an integrated circuit based on this technology may be used.

Moreover, the server device 30 may include at least a part of the data storage unit 150 and the game control unit 160 included in the terminal device 10 . For example, the terminal device 10 acquires a game image based on the game processing executed by the server device 30 and displays it on the display unit 13, and receives a user's operation regarding the game processing and transmits it to the server device 30, whereby the server device 30 may execute processing based on the user's operation. That is, the game that can be played on the terminal device 10 may be a so-called browser game.

In the above-described embodiment, a configuration example of the game system 1 in which the terminal device 10 communicates with the server device 30 has been described, but the server device 30 is not essential, and the terminal device 10 alone may be used.

[Appendix]
From the above description, the present invention can be grasped, for example, as follows. In order to facilitate understanding of the present invention, reference numerals in the accompanying drawings are added in parentheses for convenience, but the present invention is not limited to the illustrated embodiments.

(Supplementary Note 1) A game program according to an aspect of the present invention is a game program for executing game processing using a plurality of player characters, wherein the computer includes first identification information (e.g., character ID) for identifying each of a plurality of player characters including a plurality of types of player characters with the same player name and player characters with different player names, and second identification information (e.g., cheering song) that is set as the same information for player characters with the same player name and different information for player characters with different player names as identification information for performance for each player character. A step (S154) of referring to data associated with a player character and referring to data associated with a player character (for example, a cheering song) based on a user's operation to associate an effect (for example, cheering song) that can be set for each player character with the second identification information associated with the player character (S154); and let it run.

According to the configuration of Supplementary Note 1, the game program can set, with a single operation, the performance of the player character that satisfies the predetermined condition for all of the player characters of the same player (same player name) of a plurality of types, so that the convenience of setting the game can be improved.

(Supplementary Note 2) An aspect of the present invention is the game program according to Supplementary Note 1, which causes the computer to execute a step of processing a match using a player character associated with third identification information (for example, a user ID) for identifying a user among a plurality of player characters, and in the associating step, both the player character associated with the third identification information and the player character not associated with the third identification information are associated with the respective player characters based on the user's operation. It is possible to associate identification information (for example, cheering song ID) with the production (for example, cheering song).

According to the configuration of Supplementary Note 2, the game program can set effects in advance even for a player character that the user has not yet owned (for example, the user's favorite player character). Further, by setting the performance in advance, when acquiring and using an unobtained player character, the performance can be performed according to the satisfaction of a predetermined condition without setting the performance again, so that the convenience of setting the game can be improved.

(Supplementary Note 3) Also, one aspect of the present invention is the game program according to Supplementary Note 1 or Supplementary Note 2, wherein each of the plurality of player characters is associated with fourth identification information (e.g., team ID) for identifying the team to which each player belongs.

According to the configuration of Supplementary Note 3, the game program can prevent the performance set before the transfer from being performed at the transfer destination when the player transfers teams.

(Additional Note 4) A game processing method according to an aspect of the present invention is a game processing method executed by a computer that executes processing of a game using a plurality of player characters, wherein first identification information (e.g., character ID) for identifying each of a plurality of player characters including a plurality of types of player characters with the same player name and player characters with different player names, and second identification information (e.g., character ID) that is set as the same information for player characters with the same player name and different information for player characters with different player names as identification information for performance for each player character ( For example, referring to data associated with a cheering song ID), a step of associating an effect (for example, a cheering song) that can be set for each of the player characters based on the user's operation with the second identification information associated with the player character (S154); 204), and

According to the configuration of Supplementary Note 4, the game processing method can set the performance of a player character that satisfies a predetermined condition for all of a plurality of types of player characters of the same player (same player name) with a single operation, thereby improving the convenience of setting the game.

(Appendix 5) A game device (10) according to an aspect of the present invention is a game device that executes a game process using a plurality of player characters, and includes first identification information (e.g., character ID) for identifying each of a plurality of player characters including a plurality of types of player characters with the same player name and player characters with different player names, and second identification information (e.g., character ID) that is set as the same information for player characters with the same player name and different information for player characters with different player names as identification information for presentation for each player character. an association unit (166) that refers to data associated with a cheering song ID) and associates an effect (for example, cheering song) that can be set for each player character based on a user's operation with the second identification information associated with the player character; Prepare.

According to the configuration of Supplementary Note 5, the game device can set the performance of a player character that satisfies a predetermined condition for all of a plurality of types of player characters of the same player (same player name) with a single operation, thereby improving the convenience of setting the game.

(Supplementary Note 6) The game program according to one aspect of the present invention causes a computer to acquire a first object (for example, a character such as a player, a warrior, or a car) to be used in a game (S102), acquire a second object (for example, a performance such as cheering song, items, parts, etc.) that can be used in the game in association with the first object (S112, S122), and associate the acquired second object with the first object (S154). and in the associating step, the obtained second object can be associated with the already obtained first object, and can also be previously associated with the not yet obtained first object so that it can be used after the first object is obtained.

(Supplementary Note 7) A game processing method according to an aspect of the present invention is a game processing method executed by a computer, and includes a step of acquiring a first object (e.g., a character such as a player, a warrior, a car, etc.) to be used in a game (S102), a step of acquiring a second object (e.g., an effect such as cheering song, items, parts, etc.) that can be used in the game in association with the first object (S112, S122), and a step of associating the acquired second object with the first object (S1). 54), wherein in the associating step, the obtained second object can be associated with the obtained first object, and can also be associated with the unacquired first object in advance so that it can be used after the first object is obtained.

(Supplementary Note 8) A game device (10) according to an aspect of the present invention includes a first acquisition unit (163) that acquires a first object (for example, a character such as a player, a warrior, or a car) used in a game, a second acquisition unit (165) that acquires a second object that can be used in the game in association with the first object (for example, a production such as cheering music, items, parts, etc.), and an association unit (166) that associates the acquired second object with the first object, The association unit can associate the acquired second object with the acquired first object, and can also associate with the unacquired first object in advance so that it can be used after the first object is acquired.

According to the configurations of appendices 6, 7, and 8, it is possible to set a second object in advance even for an unacquired first object, so that when acquiring and using an unacquired first object, the second object associated with the first object can be used without setting the second object again. Therefore, the convenience of setting the game can be improved.

Reference Signs List 1 game system 10 terminal device 11 communication unit 12 input unit 13 display unit 14 audio output unit 15 storage unit 16 CPU 151 character data storage unit 152 user data storage unit 153 owned character data storage unit 154 cheering song data storage unit 155 cheering song setting data storage unit 161 operation reception unit 162 display control unit 163 character acquisition unit 164 Supporting music creation processing unit 165 Supporting music data acquisition unit 166 Supporting music setting unit 167 Game processing unit 168 Effect processing unit 30 Server device

Claims (3)

A game program for executing game processing using a plurality of player characters,
to the computer,
a step of associating the selected effect with all player characters with the same player name, based on a user's operation of selecting a effect to be set for one player character among a plurality of player characters including a plurality of types of player characters with the same player name and player characters with different player names ;
a step of, in response to each of a plurality of player characters having satisfied a predetermined condition based on the progress of the game, performing a process according to an effect associated with the player character satisfying the predetermined condition;
A game program for executing A game processing method executed by a computer that executes processing of a game using a plurality of player characters,
to the computer,
a step of associating the selected effect with all player characters with the same player name, based on a user's operation of selecting a effect to be set for one player character among a plurality of player characters including a plurality of types of player characters with the same player name and player characters with different player names;
a step of, in response to each of a plurality of player characters having satisfied a predetermined condition based on the progress of the game, performing a process according to an effect associated with the player character satisfying the predetermined condition;
game processing methods, including; A game device for executing game processing using a plurality of player characters,
an association unit that associates the selected effect with all player characters with the same player name, based on a user's operation of selecting a effect to be set for one player character among a plurality of player characters including a plurality of types of player characters with the same player name and player characters with different player names;
an effect processing unit that, in response to each of a plurality of player characters satisfying a predetermined condition based on the progress of the game, performs a process according to an effect associated with the player character satisfying the predetermined condition;
game device.

Images