JP7760185B2 - Program, game control method, game device and game system - Google Patents

Description

Application of Article 30, Paragraph 2 of the Patent Act: July 26, 2018: Konami Digital Entertainment Co., Ltd. has posted the application "Professional Baseball Spirits A v6.4.0," which implements functions related to "programs, game control methods, game devices, and game systems," on the websites ((A) https://itunes.apple.com (B) http://itunes.apple.com/jp/app/puro-ye-quiusupirittsua/id940320341?ls=1&mt=8 (C) https://play.google.com . com (D) https://play.google.com/store/apps/details?id=jp.konami.prospia (E) https://www.amazon.co.jp (F) https://www.amazon.co.jp/dp/B072LZSKQG

Application of Article 30, Paragraph 2 of the Patent Act. August 22, 2018: Konami Digital Entertainment Co., Ltd. has posted the application "Professional Baseball Spirits A v6.5.0," which implements functions related to "programs, game control methods, game devices, and game systems," on the following websites: (A) https://itunes.apple.com (B) http://itunes.apple.com/jp/app/puro-ye-quiusupirittsua/id940320341?ls=1&mt=8 (C) https://play.google.com . com (D) https://play.google.com/store/apps/details?id=jp.konami.prospia (E) https://www.amazon.co.jp (F) https://www.amazon.co.jp/dp/B072LZSKQG

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

Conventionally, baseball games have been offered in which players collect player characters using item charges, organize a team using the collected player characters, and play matches against opposing teams (see, for example, Patent Document 1).

JP 2019-80820 A

In a baseball game where a player plays a match, if the user were allowed to use their owned player characters at any time, there is a possibility that, for example, the same pitcher character would repeatedly play in consecutive matches (make consecutive appearances on the mound). However, in real-life professional baseball, pitchers tend to be more tired after each match than fielders, so pitchers are rarely made to play consecutive matches and are usually rested for several matches. If the same pitcher character were allowed to play consecutive matches in a baseball game, this could detract from the realism and reduce the game's appeal.

The present invention was made in consideration of the above-mentioned problems, and aims to improve the entertainment value of games.

The program of the present invention is a program for controlling a game that progresses using characters, and causes a computer to function as storage means for storing parameters associated with characters and that have an effect on the game depending on the values of the characters used in the game, and as modification means for modifying the values of the parameters stored in the storage means for the characters used in the game, and the game can be run in multiple modes, and the parameters are managed for each mode.

FIG. 10 is a diagram showing an example of a player information image of a baseball game. FIG. 10 is a diagram showing an example of a team setting image for a baseball game. FIG. 10 is a diagram showing an example of a team setting image for a baseball game. 1 is a diagram illustrating an example of the configuration of a game system according to an embodiment. 1 is a block diagram illustrating an example of a functional configuration of a game device according to an embodiment. FIG. 10 is a diagram showing an example of player character data. FIG. 10 is a diagram illustrating an example of order data. 10 is a flowchart showing an example of a processing procedure performed by the game device according to the embodiment. 10 is a flowchart showing an example of a processing procedure performed by the game device according to the embodiment. FIG. 10 is a diagram illustrating an ID assigned to a player character. FIG. 10 is a diagram for explaining the relationship between real-time battle modes, orders, and fatigue levels.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
[1. Game Description]
Below, an outline of a game to which the present invention is suitable will be described.
In this embodiment, a baseball game is described in which player characters are collected using item charges, etc., and a team (hereinafter also referred to as a user team) is formed using the collected player characters to play matches against opposing teams.

(Player character)
In the baseball game of this embodiment, player characters that imitate real baseball players are provided, and the names and images of the real baseball players are set. Note that, although the player characters imitate real baseball players in this embodiment, fictional characters may also be used as player characters.

1 is a diagram showing an example of a player information image showing information about a player character. The player information image is displayed on a display unit 106 of a game device 10, which will be described later. In FIG. 1, a player information image G100 of a pitcher character is shown.
Part P101 shows an image of a player character, and an image of a real baseball player is displayed.
Part P102 indicates the player name and series. In the example of FIG. 1, the player name is "x", but the name of an actual baseball player is displayed. Also, in the example of FIG. 1, the series of the player character is "2017 Series 1". Player characters with the same player name may be provided for each series, for example, "2017 Series 1 Player Name x", "2017 Series 2 Player Name x", etc. Therefore, there may be player characters with the same player name but from different series within the same team. With each update of the series, changes to the abilities, etc. are made based on the baseball player's performance.

Part P103 indicates the rarity of the player character. Rarity represents the rank of the player character, and the higher the rarity, the higher the upper limit of the level, abilities, and spirits. Rarity is ranked from highest to lowest as "S, A, B, C, D." Player characters with the same player name may have different rarities, and there may be player characters with the same player name but different rarities on the same team.
Part P104 indicates the spirits of the player characters. Spirits are a numerical value given to each player character, and are parameters that increase as the player character is strengthened. When a match or event confronts, a "spirits showdown" is held based on the spirits of the two opposing player characters, and the results of this will cause changes in abilities, etc.

The part P105 indicates the defensive information, cost information, training level information, and level/experience value information of the player character.
The defensive information indicates the appropriate position (defensive position) of the player character and the level of the player character's defensive ability. Defensive ability is rated "S, A, B, C, D, E, F, G" in descending order of defensive ability. In the example of Figure 1, "First S" indicates that the player character's appropriate position is "pitcher (starting pitcher)" and that the player character's defensive ability is "S."
The cost information indicates the cost of the player characters. A team must be formed so that the total cost of the player characters does not exceed an upper limit (team cost).
The training level information indicates the training level of the player character. The training level of the player character increases as the player undergoes training. As the training level increases, the player character's abilities and spirits also increase. Note that "Lv0/10" indicates that the upper limit of the player character's training level is "10" and that the current training level is "0."
The level and experience value information indicates the level and experience value of a player character. Player characters who participate in a match are granted experience values. When the experience value reaches a predetermined value, the level of the player character increases. When the level of a player character increases, the player character's abilities and spirits also increase. Note that "Lv50/60" indicates that the player character's upper limit level is "60" and the current level is "50".

Part P106 shows the pitching power parameter, control parameter, and stamina parameter that represent the pitcher's abilities. As the stamina parameter decreases, the control, power, and curveball speed decrease. A number and an alphabet are displayed for each parameter. The number indicates the parameter value, and the alphabet indicates the level of ability. Each parameter is ranked from highest to lowest as "S, A, B, C, D, E, F, G."
The part P107 indicates the fatigue level of the player character. The fatigue level will be described later.
The player information image G100 includes multiple pages, and the pages can be switched by operating the operation part P108.

Note that while Figure 1 shows a pitcher character, for fielder characters, the defensive information in part P105 displays the defensive position (catcher, first base, second base, etc.). Additionally, part P106 displays parameters representing the fielder's abilities (e.g., trajectory parameters, hitting parameters, power parameters, running ability parameters, etc.).

Now, with reference to Figure 10, we will explain the IDs assigned to player characters. IDs assigned to player characters include an "original ID," a "profile number ID," and a "player ID." An original ID is an ID assigned to each player name. A profile number ID is an ID assigned according to rarity. A player ID is an ID assigned to each player character owned by the user. As mentioned above, there may be player characters with the same player name but different series or rarities within the same team. There may also be player characters with the same player name and the same series or rarity within the same team. In this case, as shown in Figure 10, there will be multiple player characters assigned the same original ID, but the player IDs of these multiple player characters will be different from each other.

(Match format)
There are two types of match formats for playing against an opposing team: computer match and real-time match.
In computer matches, the match between the user's team and the opposing team (a computer team or the user team of another user on the network) progresses automatically. In computer matches, the progress of the match is automatically determined by the computer based on parameters related to the user's team and the opposing team, and the user watches the match progress as it progresses automatically. Note that even in computer matches, the user can still perform some operations (such as pitching and batting operations on the user's team's side).
In a real-time match, a game between a user team and an opposing team (a user team of another user on the network) progresses via a communication match in accordance with operations on each game device 10. If one user is on defense and the other user is on offense, a player character pitches or plays defense in response to the operation of one user (pitching operation or fielding operation), and a player character bats or runs the bases in response to the operation of the other user (batting operation or baserunning operation). In this way, the game situation is updated based on the user's operations on the player characters. Real-time matches are a match format that is also used in esports (e-sports).

(Real-time battle mode)
Real-time battles are available in ranked battle mode, room battle mode, and tournament mode.
Ranked Battle Mode is a mode in which you play in real time against other players of the same rank, selected through a matching process. In Ranked Battle Mode, your rank increases based on the points you earn from winning or losing matches. In this way, Ranked Battle Mode is a mode in which you can compete against players from all over the country.

Room battle mode is a mode in which you play in real time against other players who are participants in a group called a room. In room battle mode, points are not awarded for winning or losing a match. When you create a room, a room ID is issued, and by sharing the room ID with multiple players, room members can play matches against each other. When creating a room, you can set the match rules (for example, the number of innings in a match) as you like. In this way, room battle mode is a mode in which you can play against a limited number of players, such as friends.

Tournament mode is a mode in which players can participate in a tournament that is held for a limited time, for example, and compete in real-time against other players who are also participants in the tournament. Players are assigned a parameter called a "rating," and with each match, their current rating changes depending on their wins and losses and the "rating difference with their opponent." The highest rating recorded during the tournament period, known as the "best rating," is recorded as a ranking record.

(User team formation)
In order for a player character owned by the user to participate in a game, they must be registered in the order, which can be edited on the order screen. The order may consist of, for example, five starting pitchers, four relief pitchers (including two setup pitchers), one closer, nine fielders including a designated hitter, and five bench slots (pitchers and fielders), for a total of 24 player characters.

Figures 2 and 3 show examples of team setting images for organizing a user team. The team setting images constitute an order screen displayed on the display unit 106 of the game device 10, which will be described later. As shown in Figures 2 and 3, the team setting images G200 and G300 are images for selecting player characters to be registered as fielder or pitcher members of the team from among the player characters owned by the user. Parts P201 to P203 are parts for selecting either a pitcher, fielder, or reserve player.

2 shows a team setting image G200 for registering fielder members when part P201 is selected. In the team setting image G200, player characters registered as fielder members of the team are displayed in area A204. That is, a plurality of parts P205 corresponding to a plurality of player characters registered as fielder members of the team are displayed in area A204.
In the example of Fig. 2, the name of the player character is displayed within each part P205. Although not shown in Fig. 2, an image, rarity, etc. of the player character may be displayed within each part P205.

Area A204 includes area A2041 for starting members and area A2042 for bench members. Area A2041 displays parts P205 representing player characters registered as starting members. That is, one part P205 (one player character) is associated with each position. Meanwhile, area A2042 displays parts P205 representing player characters registered as bench members.
For example, by dragging and dropping part P205 onto another part P205, it is possible to change the positions of player characters or to switch player characters between starting members and bench members. In addition, by selecting one of the parts P205, the user can also switch the player character corresponding to that part P205 with a reserve player character (a player character owned by the user that is not registered as a member of the team).

Furthermore, part P206 indicates team spirits. Team spirits are calculated by executing a predetermined calculation process based on the spirits of each player character registered as a team member. For example, team spirits are the sum of the spirits of each player character registered as a team member. A "spirits showdown" with the team spirits of the opposing team occurs, and the superiority or inferiority of the two teams in the match is determined based on the results.
Part P207 indicates the team cost. The team cost indicates the total cost of the player characters registered as team members. "221/250" indicates that the team cost is "221" and the upper limit cost is "250." The user must set the team members so that the team cost does not exceed the upper limit cost.

Part P208 is a part for setting the batting order, etc. When part P208 is selected, an image for setting the batting order is displayed.
Part P209 is a part for saving team data. When part P209 is selected, the team data set by the user is saved.

3 shows a team setting image G300 for registering pitcher members when part P202 is selected. Elements similar to those in the team setting image G200 are given the same reference numerals, and their description will be omitted. In the team setting image G300, player characters registered as pitcher members of the team are displayed in area A204. In this case, a plurality of parts P205 corresponding to player characters registered as starting pitchers, relay pitchers, and closers are displayed in area A204.
Although not shown, when part P203 is selected, a reserve player character is displayed in area A204.

In this way, the user creates an order using the player characters that the user owns, organizes a user team made up of multiple player characters, and plays a match against an opposing team.
In the baseball game of this embodiment, as shown in Figure 11 (a), the orders are managed in common between the ranked battle mode and the room battle mode. On the other hand, in the tournament mode, the orders are managed separately from the orders in the ranked battle mode and the room battle mode. In other words, the orders for the tournament mode can be created independently of the orders for the ranked battle mode and the room battle mode.
In this way, the rank battle mode and the room battle mode share the same orders, and the team setting image is also the same. Figures 2 and 3 show the team setting image for creating orders for the rank battle mode and the room battle mode.

(fatigue level)
In the baseball game of this embodiment, a parameter called a "fatigue level" is associated with the pitcher character in a real-time match, introducing the concept that the pitcher character becomes fatigued when he takes the mound.
The fatigue level is set to level 0 when there is no fatigue, and increases by one level as fatigue increases, with level 4 being the highest level.

By having a pitcher character start the game, the pitcher character's fatigue level will increase by 4 levels.

In addition, by having a pitcher character come in to relieve a player, the relief pitcher character's fatigue level will increase according to predetermined rules. For example, the degree to which the fatigue level increases varies depending on the ratio of the relief pitcher character's remaining stamina at the end of the game to their maximum stamina (called the remaining stamina rate). For example, if the remaining stamina rate is 80% or higher, the relief pitcher character will increase by one level; if the remaining stamina rate is 50% or higher but less than 80%, the relief pitcher character will increase by two levels; if the remaining stamina rate is 20% or higher but less than 50%, the relief pitcher character will increase by three levels; and if the remaining stamina rate is less than 20%, the relief pitcher character will increase by four levels.

Also, by resting a pitcher character for one game, the fatigue level of the rested pitcher character will be reduced by one level. In other words, by not having the pitcher character take the mound and instead having another pitcher character take the mound in a game, the fatigue level of the rested pitcher character will be reduced by one level. The fatigue level of a pitcher character who is a reserve player will also be reduced by a similar level.

Depending on the level value of the fatigue level, an effect of suppressing a predetermined ability of the pitcher character is given.
The higher the fatigue level, the lower the spirits will be set, for example. To give a specific example, for the spirits set for a pitcher character, if the fatigue level is level 0, the spirits will not decrease, but will decrease by -10% at level 1, -20% at level 2, -30% at level 3, and -40% at level 4.
Furthermore, the higher the fatigue level, the lower the stamina will be set at the start of the game. For example, if the fatigue level is level 0, the stamina will not decrease compared to the stamina set for a pitcher character at the start of the game, but will decrease by -30% at level 1, -60% at level 2, -90% at level 3, and -100% at level 4.

In this way, a fatigue level is associated with a pitcher character, and the fatigue level value of a pitcher character who takes the mound in a match is changed. Depending on the fatigue level value, the pitcher character's specified abilities (spirits and stamina at the start of the match) are suppressed. This prevents situations where the same pitcher character takes the mound repeatedly, improving the game's appeal. Note that the fatigue level does not prohibit a pitcher character from taking the mound consecutively, and it is possible for a pitcher character to take the mound even if their spirits and stamina at the start of the match are low.

Also, by resting a pitcher character, the fatigue of that pitcher character will recover (their fatigue level will decrease). This adds to the fun of considering the rotation (the order in which starting pitchers are used) just like in real professional baseball, by having a pitcher character take the mound and then rest for a few games, further improving the game's appeal.

Here, fatigue levels are managed for each original ID. This is to prevent consecutive or frequent appearances by player characters with the same player name. For example, if the fatigue level of the player character "2017 Series 1 Player Name x" is assigned level 2, the fatigue level of the player character "2017 Series 2 Player Name x" will also be assigned level 2.

11A, the fatigue level is managed for each real-time battle mode, i.e., the fatigue level is managed for each of the ranked battle mode, room battle mode, and tournament mode.
If fatigue levels were managed only for each original ID, for example, when playing a match in Room Battle mode and then trying to play a match in Ranked Battle mode, the fatigue level from Room Battle mode would be applied. This would have the effect of suppressing a pitcher character's specific abilities due to the fatigue level from Room Battle mode, even though the pitcher character did not pitch in Ranked Battle mode. Furthermore, if a player wants to have a pitcher character pitch consecutively in Ranked Battle mode, where points can be earned, they could pitch in Ranked Battle mode and then play matches in Room Battle mode without having the pitcher character pitch, thereby lowering the pitcher character's fatigue level and allowing the pitcher character to pitch consecutively in Ranked Battle mode without being fatigued.
To avoid such a situation, the fatigue level is managed for each mode in addition to for each original ID, so that the fatigue level in one mode does not affect the other modes.

In the room battle mode, when a room is created, it may be possible to select for each room whether or not to introduce a fatigue level, that is, whether or not to associate a fatigue level with the pitcher character.
Furthermore, as a rule of the room battle mode, a user can only belong to one room at a time. In this case, if the fatigue level of the pitcher character is carried over when the user changes rooms, the pitcher character will start in a fatigued state in the new room, which would make it impossible to maintain fairness with other players. Therefore, when a user changes rooms, the fatigue levels of the pitcher characters owned by that user (pitcher characters available to that user) that are managed in the room battle mode are reset, so that the fatigue level in one room does not affect other rooms.
However, the fatigue level managed in the room battle mode will not be reset simply because the user has left the room. When re-entering the same room, the user can continue playing the game with their fatigue level maintained.

As shown in Figure 1, the player information image G100 may display a part P107 indicating the fatigue level. Furthermore, the spirits shown in part P104 may be displayed as a numerical value that decreases according to the fatigue level.

Also, as shown in FIG. 3, in the team setting image G300 for registering pitcher members, an icon 211 representing the fatigue level may be displayed on part P205 of a pitcher character that is not fatigue-free (a pitcher character whose fatigue level is level 1 or higher). In this case, as shown in FIG. 3, in the team setting image G300 for ranked battle mode and room battle mode, it is preferable to be able to switch between displaying the fatigue level managed in ranked battle mode and displaying the fatigue level managed in room battle mode by operating operation part P210.

2. Game System Configuration
Next, an outline of a game system for realizing the game described above will be described.
4 is a diagram showing an example of the configuration of a game system 1 according to this embodiment. In the game system 1 according to this embodiment, a server device 30 and a plurality of game devices 10 are connected wirelessly via a network 20. Note that the server device 30 and the plurality of game devices 10 may also be connected by wire.

The game device 10 is a device for operating the baseball game described above, and may be, for example, a portable communication device such as a smartphone, a dedicated portable game device, a tablet, or a stationary game device. The game device 10 has a CPU 101, ROM 102, RAM 103, a communication unit 104, an operation unit 105, a display unit 106, and a storage device 107. Note that while Figure 1 shows the hardware configuration of one game device 10, the hardware configurations of the other game devices 10 are similar and are therefore not shown.

The CPU 101 reads the control program stored in the ROM 102 into the RAM 103 and executes various processes. The ROM 102 stores the control program (such as the OS) required to operate the game device 10. Flash memory (NVRAM) may be used instead of the ROM 102. The RAM 103 is used as temporary storage space such as the CPU 101's main memory and work area. The communication unit 104 performs communication processing with the server device 30 and other external devices via the network 20. The operation unit 105 accepts various operations by the user. Note that if the display unit 106 is an LCD display panel equipped with a touch panel, the touch panel serves as the operation unit 105. The display unit 106 displays various information such as the game screen described above. The storage device 107 mainly stores game programs and various game-related data.

The functions and processing of the game device 10 are realized by the CPU 101 reading and executing a program stored in the ROM 102 or storage device 107. As another example, the CPU 101 may read a program stored on a removable storage medium such as an SD card, rather than reading a program stored in the ROM 102 or the like. The means for supplying the program to the computer may also be a computer-readable storage medium such as a CD-ROM containing the program, or a transmission medium such as the Internet for transmitting the program. Hereinafter, the game device 10 will be described as a smartphone having a liquid crystal display panel equipped with a touch panel.

The server device 30 has a CPU 301, a ROM 302, a RAM 303, a communication unit 304, and a storage device 305.

The CPU 301 reads out the control program stored in the ROM 302 and executes various processes. The RAM 303 is used as temporary storage area such as the CPU 301's main memory and work area. The communication unit 304 performs communication processing with the game device 10 and other external devices via the network 20. The storage device 305 stores game-related programs, identification information such as the ID of the user operating the game device 10, and various other user-specific information required for the game. Note that some of this information may be stored in a database (not shown) or the like.

FIG. 5 is a block diagram showing an example of a functional configuration for storing, changing, and managing fatigue levels in the game device 10. As shown in FIG.
The storage device 107 of the game device 10 stores a game program for executing the game, and further includes a data storage unit 1071 that stores various data necessary for game processing. The data storage unit 1071 stores player character data DT1, order data DT2, etc.

6 is a diagram showing an example of the player character data DT1. The player character data DT1 is data indicating a list of player characters owned by a user, and exists for each user.
The player character data DT includes fields for "serial number,""originalID,""playerID,""name,""series,""rarity,""cost,""position,""experiencevalue,""level," and "spirits." For pitcher characters, it also includes a "fatigue level" field. Although not shown in FIG. 6, it may also include upper limit level, training level, ability parameters, etc.

The "serial number" field indicates a serial number for uniquely identifying a player character owned by the user. If a user owns multiple player characters with the same player name, these player characters will have the same original ID but different serial numbers.
"Original ID" indicates the original ID of a player character owned by the user.
"Player ID" indicates the player ID of a player character owned by the user.
The "Name", "Rarity", "Cost", "Position", "Level", and "Spirits" fields indicate the player character's player name, rarity, cost, appropriate position, level, and spirits, respectively.
The "series" field indicates which series the player character belongs to.
The "experience value" field indicates the cumulative total of experience values given to the player character.
The "Fatigue Level" field shows the fatigue level in Ranked Battle Mode, Room Battle Mode, and Tournament Mode.
The player character's experience points, level, spirits, etc. are changed by having the player character participate in a match or undergo special training. In addition, the player character's fatigue level is changed by having the player character participate in a match or resting.

In this way, the storage device 107 stores, in the player character data DT1, a fatigue level, which is a parameter associated with a pitcher character and exerts an influence on the pitcher character taking the mound in a game according to its value. Specifically, the fatigue level has an effect of suppressing a predetermined ability of the pitcher character according to the level value of the fatigue level. The fatigue level is stored and managed for each real-time battle mode. That is, the fatigue level is managed separately for the ranked battle mode, the room battle mode, and the tournament mode. For example, when a match is played in ranked battle mode, the fatigue level of the pitcher character taking the mound in this match has an effect of suppressing a predetermined ability of the pitcher character according to the level value of the fatigue level managed in ranked battle mode. The same applies to the room battle mode and the tournament mode.
In this embodiment, the storage device 107 corresponds to the storage means of the present invention.

In the server device 30, provided player character data indicating player characters currently provided by the game system 1 and player characters provided in the past is stored in the storage device 305. The provided player character data manages fixed information such as "original ID,""name,""rarity,""cost," and "position," as well as initial values such as "experience points,""level," and "spirits."
In Figure 6, the player character data DT1 is shown to include fixed information such as "original ID,""name,""rarity,""cost," and "position," but this information may refer to the provided player character data, and the player character data DT1 may include only changeable information such as "experience points,""level,""spirits," and "fatigue level."

FIG. 7 is a diagram showing an example of order data DT2. Order data DT2 is data indicating an order created by a user, and exists for each user. Furthermore, even for the same user, multiple pieces of order data DT2 exist, such as orders for ranked battle mode, room battle mode, and tournament mode. FIG. 7 shows order data for ranked battle mode and room battle mode.
The order data DT2 includes member data 701 and team spirits data 702.
The member data 701 indicates the serial numbers of the player characters registered in the lineup (five starting pitchers, four relief pitchers, one closer, nine fielders including a designated hitter, and five bench players). The member data 701 also indicates the batting order set by the user.
The team spirits data 702 indicates the numerical value of the team spirits.

The game device 10 also includes a game control unit 120, the functions of which are realized by the CPU 101 executing a game program stored in the storage device 107. The game control unit 120 performs the controls necessary for the user to play the game on the game device 10. The game control unit 120 includes a fatigue level change unit 1201 and a reset unit 1202.

The fatigue level change unit 1201 changes the fatigue level value of a pitcher character who has pitched in a match, among the fatigue levels stored in the player character data DT1 in the storage device 107. As described above, by having a pitcher character pitch as a starter, the fatigue level of this pitcher character is increased by four levels. Also, by having a pitcher character pitch as a relief pitcher, the fatigue level of this relief pitcher character is increased in accordance with the remaining stamina. For example, when a match is played in ranked match mode, the fatigue level value managed in ranked match mode is changed among the fatigue levels of pitcher characters who have participated in this match. The same applies to room match mode and tournament mode.
The fatigue level change unit 1201 also changes the fatigue level value of a pitcher character who did not pitch in a match. As described above, by resting a pitcher character for one match, the fatigue level of the rested pitcher character is reduced by one level. For example, when a match is played in ranked match mode, the fatigue level value managed in ranked match mode of the pitcher character who did not pitch in the match is changed. The same applies to room match mode and tournament mode.
In this embodiment, the fatigue level changing unit 1201 corresponds to the changing means of the present invention.

When a user moves to a different room, the reset unit 1202 resets the fatigue levels of pitcher characters owned by the user (pitcher characters available to the user) that are managed in the room battle mode.
In this embodiment, the reset unit 1202 corresponds to the reset means of the present invention.

[3. Processing in the Game System]
The processing in the game system according to this embodiment will be described below.
In a real-time match, a match between a user team and an opponent team (a user team of another user on the network) progresses via a communication match in accordance with operations on each game device 10. Operations of the user and the other users are exchanged between the game devices 10 via the server device 30, thereby realizing the communication match and updating the match status. Note that known screen displays, operations, etc., may be used in a real-time match, and therefore a description thereof will be omitted.

For example, when a match is played in ranked match mode, the fatigue level of the pitcher character taking the mound in that match is affected to suppress certain abilities of that pitcher character according to the fatigue level value managed in ranked match mode. Also, when a match is played in room match mode, the fatigue level of the pitcher character taking the mound in that match is affected to suppress certain abilities of that pitcher character according to the fatigue level value managed in room match mode. Also, when a match is played in tournament mode, the fatigue level of the pitcher character taking the mound in that match is affected to suppress certain abilities of that pitcher character according to the fatigue level value managed in tournament mode.

Next, the process executed when a real-time match ends will be described.
8 is a flowchart showing an example of a processing procedure by the game device 10 according to this embodiment. The processing described below is realized by the CPU 101 reading a game program stored in the storage device 107 into the RAM 103 and executing this game program.
The flowchart in Fig. 8 is executed when a real-time battle match ends. That is, the flowchart in Fig. 8 is executed when a match in the ranked battle mode ends, when a match in the room battle mode ends, and when a match in the tournament mode ends.

In S101, the fatigue level change unit 1201 increases the fatigue level of the starting pitcher character of the finished game by four levels.
The fatigue level change unit 1201 changes the level value in the "fatigue level" field of the starting pitcher character in the player character data DT1 depending on the mode of the completed game. That is, if a match in ranked match mode has ended, the fatigue level value managed in ranked match mode is changed. Also, if a match in room match mode has ended, the fatigue level value managed in room match mode is changed. Also, if a match in tournament match mode has ended, the fatigue level value managed in tournament match mode is changed. Note that the maximum value for the fatigue level is level 4, so if the fatigue level is already at level 1 or higher, it will be set to level 4.
In addition, the fatigue level change unit 1201 changes the level value of the "fatigue level" field of a pitcher character who is given the same original ID as the starting pitcher character in the player character data DT1 so that it is the same as the level value of the "fatigue level" field of the starting pitcher character.

In S102, the fatigue level change unit 1201 determines whether a relief pitcher took the mound in the finished game. If a relief pitcher took the mound, the process proceeds to S103, and if a relief pitcher did not take the mound, the process proceeds to S104.
In S103, the fatigue level change unit 1201 increases the fatigue level of the relief pitcher character in accordance with the remaining stamina rate.
In addition, in the player character data DT1, the level value of the "fatigue level" field of the relief pitcher character is changed depending on the mode of the completed game, and the "fatigue level" fields of pitcher characters assigned the same original ID are changed to have the same level value, just as in the case of starting pitchers.

In S104, the fatigue level change unit 1201 reduces the fatigue level of a pitcher character who did not pitch in the finished game by one level.
In addition, in the player character data DT1, the level value of the "fatigue level" field of an unpitched pitcher character is changed depending on the mode of the completed game, and the "fatigue level" field of pitcher characters given the same original ID is changed to have the same level value, just like in the case of starting pitchers and relief pitchers.

Next, the process executed when a user moves to a room will be described.
9 is a flowchart showing an example of a processing procedure by the game device 10 according to this embodiment. The processing described below is realized by the CPU 101 reading the game program stored in the storage device 107 into the RAM 103 and executing this game program.
The flowchart of FIG. 9 is executed when a user moves to a room.
In S201, the reset unit 1202 resets the fatigue levels managed in the room battle mode among the fatigue levels of pitcher characters owned by the user (pitcher characters available to the user). That is, the reset unit 1202 changes the fatigue levels in the room battle mode in the "fatigue level" fields of all pitcher characters in the player character data DT1 to level 0.

In this embodiment, the fatigue level managed in room battle mode is reset when the user moves to a room, but this is not limited to this. For example, fatigue levels may be managed for each room in room battle mode. This allows the user to maintain their previous fatigue level when they move from one room to another and then return to the same room. Rooms disappear when certain conditions are met (for example, everyone has left the room), so when a room disappears, management of fatigue levels in that room can be stopped.

As described above, a fatigue level is associated with a pitcher character, and the fatigue level value of a pitcher character who has pitched in a game is changed. The fatigue level value has an effect of suppressing certain abilities of the pitcher character (spirits and stamina at the start of the game). This prevents situations where the same pitcher character pitches repeatedly, improving the entertainment value of the game. Note that the fatigue level does not prohibit a pitcher character from pitching consecutively, and it is possible for the pitcher character to pitch even if his spirits and stamina at the start of the game are low.
Furthermore, fatigue levels are managed for each real-time battle mode (ranked battle mode, room battle mode, tournament mode), so fatigue levels in one mode do not affect other modes.
Furthermore, by resting a pitcher character, the fatigue of the rested pitcher character will be restored (the fatigue level will decrease). This increases the fun of considering the rotation (the order of starting pitchers to be used) just like in real professional baseball, such as resting a pitcher character for several games after pitching, and further improves the enjoyment of the game.

4. Modifications
Although the embodiments of the present invention have been described in detail with reference to the drawings, the specific configuration is not limited to the above-described embodiments and can be modified as appropriate within the scope of the present invention.

In the above-described embodiment, an example was described in which a fatigue level was associated with a pitcher character, but a fatigue level may also be associated with a fielder character. If there is a player who can play both pitcher and fielder, the fatigue levels can be managed separately for a "pitcher version" and a "fielder version."

Also, while an example has been described in which the fatigue level of a starting pitcher is uniformly increased by four levels, the degree to which the fatigue level is increased may be varied depending on the number of innings pitched, etc. The fatigue level may be increased not only at the end of the game, but also during the game.

In addition, an example has been explained in which a state of no fatigue is level 0, and the level increases by 1 as fatigue increases, with the highest level being level 4, but the range of level values for fatigue levels is not limited, and they may be expressed in finer, multiple levels.

Also, while an example has been described in which the method of changing fatigue levels is the same in each real-time battle mode (ranked battle mode, room battle mode, tournament mode), the method of changing fatigue levels may be different for each mode. For example, in room battle mode or tournament mode, which are short-term battles, the amount of increase in the starting pitcher's fatigue level may be smaller than the amount of increase in ranked battle mode, making it easier to have consecutive pitchers pitch.

Although the fatigue level is introduced in the real-time ranked battle mode, room battle mode, and tournament mode in the above example, the present invention is not limited to this. For example, the fatigue level may not be introduced in the room battle mode.
In this case, as shown in FIG. 11(b), fatigue levels are managed separately for the ranked battle mode and the tournament mode.
11(b), the orders for the ranked battle mode and the room battle mode are managed as separate orders from the orders for the tournament mode. Therefore, if fatigue levels are not introduced in the room battle mode, fatigue levels may be managed for each order. This is one way of managing fatigue levels for each mode.

Also, while an example of introducing a fatigue level in real-time battles has been described, a fatigue level may also be introduced in computer battles. As long as a game using characters can be played in multiple modes, there are no limitations on the battle method used when applying this invention.

In the above-described embodiment, the processing in Figures 8 and 9 was described as being performed by the game device 10, but all or part of the processing may be performed by the server device 30. Also, while the player character data DT1 and order data DT2 were described as being stored in the storage device 107 of the game device 10, they may also be stored in the storage device 305 of the server device 30.

Furthermore, while the above-described embodiment uses a baseball game as an example, the present invention is not limited to this. The present invention can be applied to any game in which characters are used to progress, such as sports games other than baseball (such as soccer games), fighting games, combat games, racing games, etc.

[5. Notes]
The following games are envisioned as games to which the present invention is applied.
This is a baseball game in which a match is played between teams consisting of a plurality of player characters, and has a function of restricting the ability of the player character in the match according to the fatigue level of the player character participating in the match, and a function of increasing the fatigue level of the player character participating in the match.
One mode can be selected from a first mode and a second mode in which a match can be played.
The fatigue level of the player character is configured to include a first fatigue level for the first mode and a second fatigue level for the second mode.
When a match is executed in the first mode, the ability of the player character in the match is restricted according to the first fatigue level associated with the player character participating in the match, and the first fatigue level of the player character participating in the match is increased.
When a match is executed in the second mode, the ability of the player character in the match is restricted according to the second fatigue level associated with the player character participating in the match, and the second fatigue level of the player character participating in the match is increased.

The game is played between teams consisting of multiple characters, and is equipped with a means for influencing the abilities of a character in the game according to a parameter representing the degree to which the character used in the game influences the abilities of the character, and a means for changing the parameter of the character used in the game.
The game system includes a means for selecting one of a first mode and a second mode in which the game can be executed, and the parameters of the character include a first parameter and a second parameter.
When the game is executed in the first mode, the ability of the character used in the game is affected in accordance with a first parameter associated with the character used in the game, and the first parameter of the character used in the game is changed;
When the game is executed in the second mode, the ability of the character in the game is affected according to the second parameter associated with the character used in the game, and the second parameter of the character used in the game is changed.

The present invention can be understood, for example, as follows.
(1)
A program according to one aspect of the present invention is a program for controlling a game that progresses using characters, and causes a computer to function as a memory means (107) that stores parameters that are associated with characters and that have an effect on the game depending on the values of the characters used in the game, and a modification means (1201) that modifies the values of the parameters of the characters used in the game from among the parameters stored in the memory means (107), and the game can be executed in multiple modes, and the parameters are managed for each of the modes.

(7)
A game control method according to one aspect of the present invention is a game control method for controlling a game that progresses using characters, which stores parameters associated with characters and that have an effect on the character used in the game depending on their values in a storage means (107), and controls to change the values of the parameters of the character used in the game from among the parameters stored in the storage means (107), and is characterized in that the game can be executed in multiple modes, and the parameters are managed for each of the modes.

(8)
A game device according to one aspect of the present invention is a game device that executes a game that progresses using characters, and is equipped with a memory means (107) that stores parameters that are associated with characters and that have an influence on the character used in the game depending on the value of the parameters, and a change means (1201) that changes the value of the parameter of the character used in the game from among the parameters stored in the memory means (107), and is characterized in that the game can be executed in multiple modes, and the parameters are managed for each of the modes.

(9)
A game system according to one aspect of the present invention is a game system for executing a game that progresses using characters, and is equipped with a memory means (107) for storing parameters that are associated with characters and that have an effect on the game depending on the values of the characters used in the game, and a modification means (1201) for modifying the values of the parameters of the characters used in the game from among the parameters stored in the memory means (107), and the game can be executed in multiple modes, and the parameters are managed for each of the modes.

The inventions pertaining to (1), (7), (8), or (9) above can prevent situations where the same character is used repeatedly, improving the game's appeal and preventing fatigue levels in one mode from affecting other modes.

(2)
In one aspect of the present invention, in the aspect (1) above, the multiple modes include a first mode and a second mode, the parameters include a first parameter managed in the first mode and a second parameter managed in the second mode, and when the game is executed in the first mode, an influence in the game is given to a character used in the game depending on the value of the first parameter of the character, and the change means (1201) changes the value of the first parameter of the character used in the game, and when the game is executed in the second mode, an influence in the game is given to a character used in the game depending on the value of the second parameter of the character used in the game, and the change means (1201) changes the value of the second parameter of the character used in the game.

(3)
In one aspect of the present invention, in the above aspect (1) or (2), the parameter is an effect on the game that suppresses a predetermined ability of the character.

(4)
In one aspect of the present invention, in any one of the above aspects (1) to (3), the game is a game in which teams made up of multiple characters compete against each other. According to the above aspect (4), it is necessary to consider how to combine the characters that make up the team, and the entertainment value of the game can be further improved.

(5)
In one aspect of the present invention, in any one of the aspects (1) to (3) above, the game is a battle game, the multiple modes include a group battle mode in which a battle is played against participants in a group, and in the group battle mode, a user can only belong to one group at a time, and when a user moves to a different group, the computer is made to function as a reset means (1202) that resets the parameters of characters available to the user that are managed in the group battle mode.
(6)
In one aspect of the present invention, in the above aspect (5), it is possible to select whether or not to introduce the parameter for each group.
According to the above aspects (5) and (6), the game can be played in a mode in which the game can be played against a limited number of players, such as friends. When a user switches groups, the fatigue level in one room can be prevented from affecting the other rooms.

1: Game system, 10: Game device, 20: Network, 30: Server device, 101, 301: CPU, 102, 302: ROM, 103, 303: RAM, 104, 304: Communication unit, 105: Operation unit, 106: Display unit, 107, 305: Storage device, 1071: Data storage unit, 120: Game control unit, 1201: Fatigue level change unit, 1202: Reset unit

Claims (7)

A program for controlling a game in which players compete against each other using characters,
a storage means for storing parameters associated with the character that affect abilities used in a battle;
a management means for managing suppression parameters associated with the characters, the suppression parameters being used to change the parameters so as to suppress the abilities of the characters, based on the usage status of the characters in a battle;
causing the computer to function as a change means for changing the parameters when the character is to be used in the next battle, based on the suppression parameters managed by the management means;
Battles can be played in multiple modes,
The management means manages the suppression parameters for each of the modes. The program described in claim 1, characterized in that the parameter is the value of the ability. 3. The program according to claim 1, wherein the management means sets the suppression parameter according to different rules when the character is used from the beginning of a battle and when the character is used partway through a battle. 4. The program according to claim 1, wherein the management means sets the suppression parameter based on a value of a predetermined parameter after a match. A game control method for controlling a game in which characters are used to play against each other, comprising:
The computer
storing parameters associated with the character and affecting abilities used in a battle in a storage means;
managing a suppression parameter for changing the parameter so as to suppress the ability of the character based on the usage status of the character in a battle, in association with the character;
changing the parameters when the character is next used in a battle based on the suppression parameters that are managed ;
Battles can be played in multiple modes,
A game control method characterized in that the suppression parameter is managed for each of the modes. A game device for executing a game in which characters are used to battle each other,
a storage means for storing parameters associated with the character that affect abilities used in a battle;
a management means for managing suppression parameters associated with the characters, the suppression parameters being used to change the parameters so as to suppress the abilities of the characters, based on the usage status of the characters in a battle;
a change means for changing the parameter when the character is to be used in the next battle based on the suppression parameter managed by the management means;
Battles can be played in multiple modes,
The game device is characterized in that the management means manages the suppression parameters for each of the modes. A game system for executing a game in which characters are used to battle each other,
a storage means for storing parameters associated with the character that affect abilities used in a battle;
a management means for managing suppression parameters associated with the characters, the suppression parameters being used to change the parameters so as to suppress the abilities of the characters, based on the usage status of the characters in a battle;
a change means for changing the parameter when the character is to be used in the next battle based on the suppression parameter managed by the management means,
Battles can be played in multiple modes,
The game system is characterized in that the management means manages the suppression parameters for each of the modes.