JP2016140770A - Game control method, computer, and control program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a game control method, or the like capable of suitably maintaining game balance in a match game in which a plurality of players participate.SOLUTION: A game control method is a game control method of a computer (3) including a storage part (32), and executing a match game. The game control method includes: storing a setting value set to each player in the storage part for each of a plurality of players; starting a match between a game medium of a specific player and an opponent game medium according to a request from the specific player from among the plurality of players; notifying another player within the plurality of players of a request for participating in the match according to the request from the specific player; and receiving participation in the match by the other player within a range in that the total of the setting value set to each player participating in the match does not exceed the upper-limit value.SELECTED DRAWING: Figure 6

Description

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

  In recent years, servers that provide games to mobile terminals via communication networks have become widespread. As a game provided by such a server, a game in which a plurality of players can participate (so-called “social game”) is known. A game provided as a social game includes a so-called RAID battle in which a plurality of players participate and fight against a common enemy character.

  For example, Patent Document 1 describes a server system that executes an online game in which a plurality of players participate and a common event for defeating a common enemy character is triggered. In this server system, a player who has already obtained the right to participate in a common event requests another player to participate in the common event, and the other player who has received the participation request Even if you do not meet, you will get the right to participate in common events.

JP 2014-140557 A

  In the server system of Patent Literature 1, a common event in which a plurality of players participate is performed when a player who has obtained the right to participate in a common event requests another player to participate in the common event. However, various levels of players participate in the online game. Therefore, in a common event, only a strong player may participate and easily defeat the enemy character, and conversely, only a weak player may participate and be unable to defeat the enemy character, and the game balance may be lost. There is.

  The present invention has been made to solve such problems, and provides a game control method, a computer, and a control program capable of appropriately maintaining a game balance in a battle game in which a plurality of players participate. For the purpose.

A game control method according to the present invention is a game control method in a computer that includes a storage unit and executes a battle game, and stores a set value set for each player in the storage unit for each of a plurality of players. In response to a request from a specific player among the players, a battle between the game media of the specific player and the enemy game media is started, and in response to a request from the specific player, another player among the plurality of players is played. The participation request of other players in a range in which the total of the set values set for each player participating in the battle does not exceed a predetermined upper limit value.
Note that the computer is only required to be able to execute the above procedure, and is, for example, a mobile terminal, a stationary terminal, a server, or the like.

  In the game control method according to the present invention, the set value is preferably set to a smaller value as the strength of each player in the competitive game is higher.

  Further, in the game control method according to the present invention, the strength of each player includes the parameters of the game medium owned by each player, the items owned by each player, the number of times each player participated in the battle, and the past battle game It is preferable to be determined based on at least one of the results of each player.

  In the game control method according to the present invention, the predetermined upper limit value is preferably set according to at least one of the parameters of the enemy game medium and the game medium of the specific player.

  Moreover, in the game control method according to the present invention, it is preferable that the predetermined upper limit value is changed with the passage of time since the start of the battle.

  Further, in the game control method according to the present invention, the computer further includes a communication unit, and further, information relating to each battle in which the participation request is notified to the player is sent to the player terminal notified of the participation request. Display data for arranging and displaying in order based on at least one of the remaining physical strength of the enemy game media of each battle, the remaining time of each battle, and the reward obtained in each battle is transmitted via the communication unit. It is preferable.

  A computer according to the present invention is a computer that executes a battle game, and for each of a plurality of players, a storage unit that stores a set value set for each player, and a request from a specific player among the plurality of players In accordance with a match execution unit that starts a match between a game medium and an enemy game medium of a specific player, and participation that notifies other players of a plurality of players of a request to participate in a match according to a request from the specific player A request notifying unit, and a participation receiving unit that accepts participation of other players in the battle within a range in which a total of setting values set for each player participating in the battle does not exceed a predetermined upper limit value.

  A control program according to the present invention is a control program for a computer that includes a storage unit and executes a battle game, and stores a set value set for each player in the storage unit for each of a plurality of players. In response to a request from a specific player, a match between the game media of the specific player and the enemy game media is started, and in response to a request from the specific player, other players among the plurality of players participate in the battle. The request is notified, and the computer is caused to accept the participation of other players in the battle within a range where the total of the set values set for each player participating in the battle does not exceed a predetermined upper limit value.

  In the game control method, the computer, and the control program according to the present invention, since the total of the set values set for each player participating in the battle does not exceed the upper limit value, participation from each player in the battle is accepted. It is possible to appropriately maintain the game balance in the battle game in which the player participates.

It is a figure which shows an example of schematic structure of a game system. It is a figure which shows an example of schematic structure of a portable terminal. (A), (b) is a schematic diagram for demonstrating the game which a game system provides. (A)-(d) is a figure which shows an example of the screen displayed on a portable terminal. (A)-(c) is a figure which shows an example of the screen displayed on a portable terminal. It is a figure which shows an example of schematic structure of a server. (A)-(c) is a figure which shows an example of the data structure of each table. (A)-(c) is a figure which shows an example of the data structure of each table. It is a figure which shows an example of the operation | movement sequence which concerns on a game process. It is a figure which shows an example of the operation | movement sequence which concerns on a list screen display process. It is a figure which shows an example of the operation | movement sequence which concerns on a participation process. It is a figure which shows an example of the operation | movement flow of a battle | competition process. It is a figure which shows an example of the operation | movement flow of a participation request process. It is a figure which shows an example of the operation | movement flow of a 2nd participation request process. It is a figure which shows an example of the operation | movement flow of a participation reception process. It is a figure which shows an example of the operation | movement flow of a group classification | category process.

  Hereinafter, various embodiments of the present invention will be described with reference to the drawings. However, it should be noted that the technical scope of the present invention is not limited to these embodiments, and extends to the invention described in the claims and equivalents thereof.

1. Outline of Embodiment In the game system of this embodiment, a player executes a game provided by a server using a mobile terminal. The game provided by the server includes a quest that progresses according to a game scenario, a normal battle in which players fight each other, and a battle event that is executed as an event.

  A quest is generally called a search, a mission, or the like, and has a plurality of floors (stages) in each of a plurality of dungeons, and sequentially executes the processing of each floor. The processing of each floor includes a battle between a character and an enemy character possessed by the player, granting a privilege such as a specific item to the player, and the like. The normal battle is a battle executed between characters of each player. The battle event is a so-called RAID battle in which a plurality of players cooperate to fight an enemy character (a so-called non-player character), and is an example of a battle game.

  A character is an example of a game medium. A game medium is electronic data used in a game, and includes, for example, a card, an item, a character, an avatar, and the like. The game medium is electronic data that can be acquired, held, used, managed, exchanged, combined, strengthened, sold, discarded, and / or gifted, etc. by the player as the game progresses. The usage mode of the game media is not limited to those specified in this specification.

  The player character or enemy character used in the battle has a battle parameter. The battle parameters include, for example, attack power, defense power, physical strength (or HP (hit point)), attributes (eg, fire, water, thunder, etc.), rareness (eg, normal, rare, S (super) rare, SS (double super) rare, SSS (triple super) rare, legend, etc.), skill (special effect) activation rate, attack speed (number of attacks in one turn, number of turns until attack, etc.), number of defenses in one match Parameters and / or jobs (eg, occupation, military type, etc.).

  The server classifies a plurality of players into a plurality of groups in advance in order to execute a battle event. Then, in accordance with a participation request from a player participating in a battle event, the server first notifies each player belonging to the group to which the player belongs to a request for participation in the battle. Further, each time the notification time elapses, the server sequentially selects a group that has not yet been notified of the participation request, and notifies each player belonging to the selected group of the participation request for the battle. In this way, the server prevents the inundation of a large number of players in a battle event, and secures the number of participants even when each player notified of the participation request does not notice the participation request. It is intended to appropriately notify each player of a request to join.

  In addition, the server sets, for each player, a participation value used for determining whether or not to participate in each battle event according to the strength of each player in the battle event. Then, the server accepts participation in the battle from each player within a range in which the sum of the participation values set for each player participating in the battle does not exceed a predetermined upper limit value. In this way, in the battle event, the server suppresses that only strong players participate and easily defeat the enemy character, and conversely, only weak players participate and cannot defeat the enemy character. Aim to maintain game balance appropriately.

2. Configuration of Game System 1 FIG. 1 is a diagram illustrating an example of a schematic configuration of the game system 1.

  The game system 1 includes at least one mobile terminal 2 and a server 3. The portable terminal 2 and the server 3 are connected to each other via a communication network such as a base station 4, a mobile communication network 5, a gateway 6, and the Internet 7, for example. A program (for example, a browsing program) executed on the portable terminal 2 and a program (for example, a game program) executed on the server 3 are made using a communication protocol such as Hypertext Transfer Protocol (HTTP). Communicate.

  The mobile terminal 2 is assumed to be a multi-function mobile phone (so-called “smart phone”), but the present invention is not limited to this. The mobile terminal 2 only needs to be applicable to the present invention. For example, a mobile phone (so-called “feature phone”), a mobile information terminal (Personal Digital Assistant, PDA), a mobile game machine, a mobile music player, a tablet terminal, a tablet A PC, a notebook PC, or the like may be used.

2.1. Configuration of Mobile Terminal 2 FIG. 2 is a diagram illustrating an example of a schematic configuration of the mobile terminal 2.

  The mobile terminal 2 includes a terminal communication unit 21, a terminal storage unit 22, an operation unit 23, a display unit 24, and a terminal processing unit 25. The portable terminal 2 requests the server 3 to advance the game in accordance with the operation of the operation unit 23 (button or the like) by the player. In addition, the mobile terminal 2 receives display data related to the progress of the game from the server 3 and displays it.

  The terminal communication unit 21 includes a communication interface circuit including an antenna whose sensitivity band is a predetermined frequency band, and connects the mobile terminal 2 to the wireless communication network. The terminal communication unit 21 establishes a radio signal line by a CDMA (Code Division Multiple Access) method or the like with the base station 4 through a channel assigned by the base station 4, and communicates with the base station 4. Do. Then, the terminal communication unit 21 transmits the data supplied from the terminal processing unit 25 to the server 3 or the like. Further, the terminal communication unit 21 supplies data received from the server 3 or the like to the terminal processing unit 25. Note that the terminal communication unit 21 may perform wireless communication with a wireless communication method of the IEEE 802.11 standard with a WiFi (Wireless Fidelity) access point (not shown).

  The terminal storage unit 22 includes, for example, a semiconductor memory device. The terminal storage unit 22 stores an operating system program, a driver program, an application program, data, and the like used for processing in the terminal processing unit 25. For example, the terminal storage unit 22 stores an input device driver program for controlling the operation unit 23, an output device driver program for controlling the display unit 24, and the like as driver programs. In addition, the terminal storage unit 22 stores, as an application program, a program that acquires and displays display data related to the progress of the game. The computer program is a terminal storage unit using a known setup program or the like from a computer-readable portable recording medium such as a CD-ROM (compact disk read only memory) or a DVD-ROM (digital versatile disk read only memory). 22 may be installed. Further, the terminal storage unit 22 stores, as data, a player ID that is identification information of the user of the mobile terminal 2, display data relating to the progress of the game, video data, image data, and the like. Further, the terminal storage unit 22 may temporarily store temporary data related to a predetermined process.

  The operation unit 23 may be any device as long as the operation of the mobile terminal 2 is possible, and is, for example, a touch panel, a key button, or the like. The player can input characters, numbers, symbols, and the like using the operation unit 23. When operated by the player, the operation unit 23 generates a signal corresponding to the operation. And the produced | generated signal is supplied to the terminal process part 25 as a player's instruction | indication.

  The display unit 24 may be any device as long as it can display images, images, and the like, and is, for example, a liquid crystal display or an organic EL (Electro-Luminescence) display. The display unit 24 displays a video corresponding to the video data supplied from the terminal processing unit 25, an image corresponding to the image data, and the like.

  The terminal processing unit 25 includes one or a plurality of processors and their peripheral circuits. The terminal processing unit 25 is a CPU (Central Processing Unit), for example, and comprehensively controls the overall operation of the mobile terminal 2. The terminal processing unit 25 includes a terminal communication unit 21, a display unit, and a display unit so that various processes of the mobile terminal 2 are executed in an appropriate procedure based on a program stored in the terminal storage unit 22, an operation of the operation unit 23, and the like The operation of 24 etc. is controlled. The terminal processing unit 25 executes processing based on programs (operating system program, driver program, application program, etc.) stored in the terminal storage unit 22. Further, the terminal processing unit 25 can execute a plurality of programs (such as application programs) in parallel.

2.1.1. Functions of Terminal Processing Unit 25 FIGS. 3A and 3B are schematic diagrams for explaining a battle event provided by the game system 1. As shown in FIGS. 3A and 3B, this battle event has the following two features.

  The first feature is that a request to participate in each battle event is notified for each group that classifies each player participating in the game.

  In the example shown in FIG. 3A, each player participating in the game is classified into a plurality of groups from group 1 to group N according to the timing at which each player accesses the game system 1. When a participation request is notified at time T from the portable terminal 2 of the player A who is fighting an enemy character in the battle event, first, the server 3 carries the mobile of each player belonging to the group K to which the player A belongs. The terminal 2 is notified of a request for participation in the battle. Next, at time T + 1 when the notification time has elapsed from time T, the server 3 is still continuing the battle event (has not won the enemy character) and the number of participants in the battle event has not reached the capacity. The participation request to the battle is notified to the portable terminal 2 of each player belonging to the group (K-1) and the group (K + 1) adjacent to the group K. After that, the server 3 is adjacent to the group that lastly notified the participation request every time the notification time elapses until the battle event ends (wins the enemy character) or the participants in the battle event reach the capacity. The participation request to the battle is notified to the portable terminal 2 of each player belonging to the group to be played.

  Since the request for participation in the battle event is notified for each group, it is possible to prevent a large number of players from rushing into the battle with the enemy character and the processing load on the server 3 from becoming too high. Furthermore, even if each player who has been notified of the participation request is not aware of the participation request, the participation request is notified to the players of other groups after the notification time has elapsed, so the number of players participating in the battle event is small. The number of players participating in the battle event is ensured. Therefore, the server 3 can appropriately notify each player of a participation request for a battle event.

  The second feature is that participation in a battle event from each player is accepted within a range in which the sum of participation values set for each player participating in the battle event does not exceed a predetermined upper limit value.

  As shown in FIG. 3B, each player participating in the game has a participation value used for determining whether or not to participate in the battle event according to the strength of each player in the battle event. Is set. In the example shown in FIG. 3B, a weaker player sets a larger participation value, and a stronger player sets a smaller participation value. The server 3 accepts participation of each player in the battle within a range in which the sum of the participation values set for each player participating in the battle event does not exceed the upper limit set in the battle event. That is, if a player B with a participation value of 10 points and a player C with a participation value of 5 points have already participated in a battle event with an enemy character with an upper limit value of 18 points, the participation value is 1 point. A strong player D can participate in the battle event, but a weak player E whose participation value is 10 points cannot participate in the battle event.

  Thereby, it is suppressed that only a weak player participates and cannot defeat an enemy character in a battle event. Conversely, by setting a larger participation value for a stronger player and setting a smaller participation value for a weaker player, it is possible to prevent an enemy character from being easily defeated by only strong players participating in a battle event. Is done. Therefore, the server 3 can appropriately maintain the game balance.

  FIG. 4A is a diagram illustrating an example of a home screen displayed on the display unit 24.

  A home screen 400 shown in FIG. 4A is displayed when the game is started. Each screen described below is displayed based on display data received from the server 3.

  On the home screen 400, a quest button 401, a battle button 402, an event button 403, and the like are displayed.

  When the quest button 401 is pressed, a screen (not shown) for executing the quest is displayed, and the player can execute the quest. In this embodiment, an enemy character in a battle event is also searched for in the quest. When an enemy character is found in the quest, a battle preparation screen described later is automatically displayed, and the player executes the battle event. Can do. When the battle button 402 is pressed, a screen (not shown) for executing the normal battle is displayed, and the player can execute the normal battle. When the event button 403 is pressed, a screen for executing a battle event is displayed, and the player can execute the battle event.

  FIG. 4B is a diagram illustrating an example of an event screen displayed on the display unit 24.

  The event screen 410 shown in FIG. 4B is displayed when the event button 403 is pressed on the home screen 400. The event screen 410 displays a plurality of battle execution buttons 411 and 412, a search button 413, a list button 414, a reward button 415, a result button 416, a home button 417, and the like for executing a battle event.

  The battle execution button 411 is a button for executing a battle event with an enemy character discovered by the player among battle events in which the player can participate. On the battle execution button 411, an image of the enemy character discovered by the player, the name, the level, the remaining time of the battle event, the name of the discovered player, and the like are displayed. The image of the enemy character includes a gauge that displays the maximum HP and the remaining HP of the enemy character in a band graph. The battle execution button 412 is a button for executing a battle event with an enemy character discovered by another player, that is, a battle event in which the player is notified of the participation request from among other battle events that the player can participate in. It is. On the battle execution button 412, the same information as the battle execution button 411 is displayed for the enemy character. The battle event executed by the battle execution button 412 is the most recommended battle event among the battle events in which the participation request is notified to the player. The most recommended battle event is a battle event with the highest or lowest HP of the enemy character, a battle event with the most or little remaining time, or a battle event with the highest or lowest reward when winning the enemy character.

  The battle execution button 411 is not displayed when the player has not found an enemy character. Note that the battle execution button 411 may function as a button for executing the second recommended battle event among the battle events for which a participation request is notified to the player when the player has not found an enemy character. Good.

  When the search button 413 is pressed, an enemy character search is executed, and when an enemy character is found, a battle preparation screen described later is displayed. On the other hand, when the enemy character is not found, the event screen is displayed again, and the fact that no enemy character was found is displayed on the event screen. When the search button 413 is pressed, a screen (not shown) for executing a quest may be displayed, and an enemy character may be searched for when the player executes the quest.

  When the list button 414 is pressed, a screen that displays a list of enemy characters that can currently battle against the battle event is displayed. When the reward button 415 is pressed, a screen (not shown) for displaying a list of rewards (points) awarded when winning the battle event is displayed for each enemy character and its level. When the result button 416 is pressed, a screen (not shown) representing the ranking of each player (for example, a list of player names from the first place to a predetermined order) calculated based on the game points given in the battle event. Is displayed. When the home button 417 is pressed, the home screen 400 is displayed again.

  4C and 4D are diagrams illustrating an example of a battle preparation screen displayed on the display unit 24. FIG.

  The battle preparation screen 420 shown in FIG. 4C is displayed when the battle execution buttons 411 and 412 are pressed on the event screen 410, when the search button 413 is pressed and an enemy character is found, or when an enemy character is included in the quest. This is displayed when is found. A battle preparation screen 440 shown in FIG. 4D is displayed when the battle preparation screen 420 is scrolled. On the battle preparation screen 420, the name of the player who found the enemy character 421, the name 422 of the enemy character, the level 423, the image 424, the HP 425, the remaining time 426 of the battle event, and the like are displayed. The battle preparation screen 420 displays an attack button 427, an item button 428, a participation request button 429, a recovery button 430, a setting button 431, a list button 432, a reward button 433, a result button 434, and the like. In addition, on the battle preparation screen 440, a reward 441, a participating player 442, an event button 443, a home button 444, and the like are displayed.

  As the HP 425, the maximum HP and the remaining HP of the enemy character are displayed as a belt-like graph (gauge) and a numerical value. When the attack button 427 is pressed, a battle event with the enemy character is executed, and a battle effect image representing a change in the HP of the player character and the enemy character is displayed by animation or the like, and a screen showing the result of the battle is displayed. Is displayed. When the item button 428 is pressed, a screen that displays a list of items owned by the player (not shown) that can activate special effects such as an effect of increasing attack power or defense power in a battle with an enemy character (not shown) ) Is displayed. The player can activate a special effect by selecting a specific item from the displayed screen.

  When the participation request button 429 is pressed, the server 3 is requested to participate in a battle event for another player, and the battle preparation screen is displayed again. In this embodiment, a player who has found an enemy character is a player who can request a participation request. Further, a player who participates in the battle event or a player who attacks the enemy character, or a player randomly selected from these players may be a player who can request a participation request. Note that the number of times each player can request a participation request may be limited to a predetermined number (for example, 3) or less. The participation request button 429 is displayed so that only a player who can request a participation request can be pressed. When a new player participates in the battle event, the participating player 442 is updated.

  When the recovery button 430 is pressed, a screen (not shown) that displays a list of recovery items that can recover the HP of the player character among the items owned by the player is displayed. The player can recover the HP by selecting a recovery item from the displayed screen. When the setting button 431 is pressed, a screen (not shown) for displaying a list of characters owned by the player is displayed. The player can select a character to be played against the enemy character from the displayed screen. The list button 432, the reward button 433, and the grade button 434 have the same functions as the list button 414, the reward button 415, and the grade button 416 on the event screen 410, respectively.

  The reward 441 is the total of game points that the player has acquired so far in the battle event. The participating player 442 is a list of players who are currently executing a battle event with an enemy character. When the event button 443 is pressed, the event screen 410 is displayed again. When the home button 444 is pressed, the home screen 400 is displayed again.

  When the attack button 427 is pressed on the battle preparation screen 420, the battle result screens 500 and 510 shown in FIGS. 5A and 5B are displayed after the effect image of the battle is displayed by animation or the like. The battle result screen 500 is displayed when the enemy character is defeated, and the battle result screen 510 is displayed when the enemy character is won.

  On the battle result screen 500, a player name 501 who has found an enemy character, an enemy character name 502, a level 503, an image 504, an HP 505, an image 506 of the player character, an HP 507, a result 508, a return button 509, and the like are displayed. .

  As the enemy character's HP 505 and the player's character HP 507, the maximum HP and the remaining HP are displayed as belt-like graphs (gauges) and numerical values in the same manner as the HP 425 displayed on the battle preparation screen 440. On the battle result screen 500, the enemy character's HP 505 is not yet 0, but the player's character HP 507 is 0, and as a result 508 is displayed that the player has lost. When the return button 509 is pressed, the battle preparation screen 440 is displayed again, and the player can play the enemy character again.

  On the battle result screen 510, a player name 501 who has found an enemy character, an enemy character name 502, a level 503, an image 504, an HP 515, an image 506 of the player character, an HP 517, a result 518, a return button 509, and the like are displayed. .

  In the match result screen 510, the HP 517 of the player character is not 0, but the HP 515 of the enemy character is 0, and as a result 518, the fact that the player has won and the reward given to the player are displayed. ing. When the return button 509 is pressed, the event screen 410 is displayed again.

  A list screen 520 shown in FIG. 5C is displayed when the list button 414 is pressed on the event screen 410 or when the list button 432 is pressed on the battle preparation screen 420. The list screen 520 displays information 521 and a selection button 522 related to each battle event for each battle event in which the player can participate, and also displays a rearrange button 523 and a return button 524. The battle event in which the player can participate is a battle event with an enemy character discovered by the player, or a battle event in which a player is notified of a participation request from another player.

  The information 521 related to each battle event includes the name of the player who found the enemy character, the image of the enemy character, the name, the level, the HP, the remaining time of the battle event, and the like. When the selection button 522 is pressed, battle preparation screens 420 and 440 for executing a battle event with the enemy character corresponding to the pressed selection button 522 are displayed. The rearrangement button 523 is a button for changing the order in which the information 521 and the selection button 522 related to each battle are arranged. The rearrangement buttons 523 include buttons for arranging the remaining HP (physical strength) of the enemy characters in each battle, the remaining time of each battle event, or the rewards obtained in each battle event in ascending or descending order. When the sort button 523 is pressed, the information 521 and the selection button 522 related to each battle event on the list screen 520 are rearranged and displayed again in the order corresponding to the pressed button. When the return button 524 is pressed, the event screen 410 or the battle preparation screen 420 is displayed again.

  As described above, the list screen 520 includes information 521 and a selection button 522 related to each battle event, and includes the remaining physical strength of the enemy character of each battle, the remaining time of each battle event, and the reward obtained in each battle event. Are arranged and displayed in the order based on at least one of them.

  Note that when the player discovers an enemy character, it is considered that the player has not yet participated in a battle event with the discovered enemy character. When the battle execution button 411 on the event screen 410, the selection button 522 on the list screen 520, or the attack button 427 on the battle preparation screen 420 is pressed with respect to the battle event, the player participates in a battle event with the found enemy character. It is regarded as having done.

2.1.2. Configuration of Terminal Processing Unit 25 The terminal processing unit 25 includes at least a browsing execution unit 251. The browsing execution unit 251 is a functional module realized by a program executed by a processor included in the terminal processing unit 25. Or the browsing execution part 251 may be mounted in the portable terminal 2 as firmware.

  The browsing execution unit 251 acquires and displays display data relating to the progress of the game. That is, the browsing execution unit 251 transmits a display data acquisition request related to the progress of the game to the server 3 via the terminal communication unit 21 in accordance with an instruction from the player. Further, the browsing execution unit 251 receives corresponding display data from the server 3 via the terminal communication unit 21. The browsing execution unit 251 creates drawing data based on the received display data. That is, the browsing execution unit 251 analyzes the received display data to identify control data and content data, lays out the content data that has been identified based on the identified control data, and creates drawing data. Then, the browsing execution unit 251 outputs the created drawing data to the display unit 24. Further, the browsing execution unit 251 stores each piece of information included in the display data in the terminal storage unit 22 while the communication connection with the server 3 is established.

2.2. Configuration of Server 3 FIG. 6 is a diagram illustrating an example of a schematic configuration of the server 3. FIGS. 7A to 7C and FIGS. 8A to 8C are diagrams illustrating examples of data structures of various tables stored in the server storage unit 32.

  The server 3 includes a server communication unit 31, a server storage unit 32, and a server processing unit 33. The server 3 advances the game in response to a request from the mobile terminal 2. Further, the server 3 creates display data relating to the progress of the game and transmits it to the mobile terminal 2.

  The server communication unit 31 is an example of an output unit, includes a communication interface circuit for connecting the server 3 to the Internet 7, and performs communication with the Internet 7. And the server communication part 31 supplies the data received from the portable terminal 2 grade | etc., To the server process part 33. FIG. In addition, the server communication unit 31 transmits the data supplied from the server processing unit 33 to the mobile terminal 2 or the like.

  The server storage unit 32 includes, for example, at least one of a magnetic tape device, a magnetic disk device, and an optical disk device. The server storage unit 32 stores an operating system program, a driver program, an application program, data, and the like used for processing in the server processing unit 33. For example, the server storage unit 32 stores, as an application program, a game program that progresses a game and creates display data related to the result. The computer program may be installed in the terminal storage unit 22 using a known setup program or the like from a computer-readable portable recording medium such as a CD-ROM or DVD-ROM.

  Further, the server storage unit 32 includes, as data, a player table shown in FIG. 7A, a battle information table shown in FIG. 7B, a battle table shown in FIG. 7C, and a group shown in FIG. A table, a character table shown in FIG. 8B, an item table shown in FIG. 8C, image data of each player, various image data relating to the progress of the game, and the like are stored. Further, the server storage unit 32 may temporarily store temporary data related to a predetermined process.

  FIG. 7A shows a player table for managing players. In the player table, for each player, an identification number (player ID) of the player, a password, a name, a file name of image data, owned character information, usage ID, owned item information, a player level, a player ID of a related player, etc. Information is stored in association.

  In the owned character information, for each character owned by the player, an identification number (owned ID) for managing the owned character, an identification number (character ID) of the character, and the like are stored in association with each other. The usage ID is an identification number of a used character used for the battle, and is a possession ID of the character used for the battle among the characters included in the owned character information. In the owned item information, for each item owned by the player, an identification number (owned ID) for managing the owned item, an identification number (item ID) of the item, and the like are stored in association with each other. The item is, for example, a medicine capable of invoking a special effect such as an effect of increasing an attack power or a defense power in a battle against an enemy character, a medicine for recovering a battle point, and the like.

  The player level is the level of the player in the quest or the normal battle, and is determined according to the points given to the player in the quest or the normal battle. The related player is another player related to the player. The related player is, for example, another player who belongs to the same group as the player, another player who has a friendship with the player, another player who has rescued the player in a battle against a previous enemy character, Other players who belong to a group that has played against the past and / or a group that has played in the past, other players who have transmitted or received messages in the past, and the like.

  FIG. 7B shows a battle information table for managing information related to battle events for each player. In the battle information table, information such as player ID, battle point, participation value, result information, discovery battle ID, participation battle ID, participation request battle ID, past results, and the like of the player is stored in association with each player.

  The battle point is a point for executing a battle event with the enemy character, and is consumed each time the battle event is executed. In addition, a battle | competition point recovers by progress of fixed time, use of a specific item, etc. The participation value is a value used for determining whether or not to participate when the player participates in the battle event, and is an example of a setting value set for the player. The participation value is set according to the strength of each player in the battle event. For example, the participation value is set to a smaller value as the strength of each player is higher. Alternatively, the participation value may be set to a smaller value as the strength of each player is lower.

  The result information includes game points, the number of wins, the number of participations, and the like. The game point is a cumulative value of points given to each player when the enemy character is damaged in the battle event or when the enemy character is won. The number of wins is the number of battle events in which the player has won the enemy character. The number of participation is the number of battle events in which the player has participated. The discovery battle ID is an identification number of a battle event in which the player has found an enemy character. The participating battle ID is an identification number of the battle event in which the player is participating. The participation request battle ID is an identification number of a battle event for which the player has received a participation request. The past results are stored in association with an identification number (event ID) for managing the event, the ranking of the player in the event, and the like for each event in a predetermined event period in which a battle event has been held in the past. . The ranking is determined by the game points acquired by the player at the event.

  FIG. 7C shows a battle table for managing each battle event. In the battle table, for each battle event, an identification number (match game ID), enemy character name, level, HP, total participation value, discovery time, end flag, discovery player ID, participation player ID for managing the battle event. The participation request player ID, reward points, participation request start time, and the like are stored.

  The enemy character name is the name of the enemy character that fights in the battle event. The level is the level of the enemy character that battles in the battle event. As the HP, the remaining HP and the maximum HP of the enemy character are stored. The total participation value indicates the sum of participation values of players participating in the event. The discovery time is the time when the enemy character was discovered, that is, the time when the battle event started. The end flag indicates whether or not the battle event has ended, and is set to OFF at the start of the battle event, and is turned ON after a certain time (for example, 30 minutes) has elapsed from the discovery time or when the player wins the enemy character. Is set.

  The found player ID is the player ID of the player who found the enemy character. The participating player ID is a player ID of a player participating in the battle event. The participation request player ID is the player ID of the player who has been notified of the participation request for the battle event. The reward point is a point given to the player when the enemy character is won. The participation request start time is the time when the participation request request from the player is first notified. If the participation request request has not been notified yet, a blank is stored as the participation request start time.

  FIG. 8A shows a group table for managing each group into which each player is classified. In the group table, for each group, the player IDs of players belonging to the group are stored in association with each other.

  FIG. 8B shows a character table for managing characters. In the character table, for each character, the character ID of the character, the name, the file name and rareness of the image data, parameters such as attack power, defense power, attribute, consumption value, and the like are stored in association with each other. The consumption value indicates a value consumed from the player's battle point when the character is used in the battle event.

  FIG. 8C shows an item table for managing items. In the item table, for each item, the item ID, name, file name, type, and the like of the item are stored in association with each other.

2.2.1. Configuration of Server Processing Unit 33 The server processing unit 33 includes a progress control unit 331, a main game execution unit 332, a battle execution unit 333, a participation request notification unit 334, a participation reception unit 335, and a classification unit 336. Each of these units is a functional module realized by a program executed by a processor included in the server processing unit 33. Alternatively, each of these units may be mounted on the server 3 as firmware.

  The progress control unit 331 controls the start and progress of the game, and appropriately instructs the main game execution unit 332, the battle execution unit 333, the participation request notification unit 334, and the participation reception unit 335 to execute the process. The progress control unit 331 exchanges necessary data with the mobile terminal 2 via the server communication unit 31.

  When the request for each screen described with reference to FIGS. 4A to 5C is received from the portable terminal 2, the progress control unit 331 receives a button for receiving an instruction from the player, and character information notified to the player. The display data for displaying an image or the like in a layout corresponding to the screen is created or instructed to each unit, and the data is transmitted to the portable terminal 2. When any button is pressed on the screen displayed on the mobile terminal 2 and a request for the next screen corresponding to the button is received from the mobile terminal 2, the progress control unit 331 similarly displays the next screen. The creation of data is executed or each unit is instructed, and the data is transmitted to the portable terminal 2.

  In particular, when an operation for starting a game using the mobile terminal 2 or an operation for transitioning to the home screen is performed by the player and a corresponding home screen request is received from the mobile terminal 2, the progress control unit 331 Display data for displaying the screen 400 is created. Then, the progress control unit 331 transmits the created display data to the mobile terminal 2.

  When the quest button 401 or the battle button 402 is pressed on the home screen 400 displayed on the mobile terminal 2 and a corresponding quest request or normal battle request is received from the mobile terminal 2, the progress control unit 331 displays the main game. The execution unit 332 is instructed to execute a quest or a normal battle. Then, the progress control unit 331 transmits the display data created by the main game execution unit 332 for executing the quest or the normal battle to the mobile terminal 2.

  When the event button 403 is pressed on the home screen 400 displayed on the mobile terminal 2 and a corresponding event screen request is received from the mobile terminal 2, the progress control unit 331 displays the event screen 410 on the battle execution unit 333. Instructs the creation of display data for display. Then, the progress control unit 331 transmits the display data created by the battle execution unit 333 to the mobile terminal 2.

  When the search button 413 is pressed on the event screen 410 displayed on the mobile terminal 2 and a corresponding search request is received from the mobile terminal 2, the progress control unit 331 causes the battle execution unit 333 to execute search processing. Instruct. Then, the progress control unit 331 transmits display data for displaying the event screen 410 or the battle preparation screens 420 and 440 created by the battle execution unit 333 according to the result of the search process to the mobile terminal 2.

  When the attack button 427 is pressed on the battle preparation screen 420 displayed on the mobile terminal 2 and a corresponding battle request is received from the mobile terminal 2, the progress control unit 331 causes the battle execution unit 333 to execute the battle. Instruct. Then, the progress control unit 331 carries display data for displaying the battle effect image created by the battle execution unit 333 according to the battle execution result and display data for displaying the battle result screens 500 and 510. Transmit to terminal 2.

  Further, when the participation request button 429 is pressed on the battle preparation screen 420 displayed on the mobile terminal 2 and a corresponding participation request request is received from the mobile terminal 2, the progress control unit 331 participates in the participation request notification unit 334. Instructs execution of request processing. Further, the progress control unit 331 instructs the battle execution unit 333 to create display data for the battle preparation screens 420 and 440, and transmits the display data created by the battle execution unit 333 to the mobile terminal 2.

  When the list button 414 of the event screen 410 displayed on the mobile terminal 2 or the list button 432 of the battle preparation screen 420 is pressed and a corresponding list screen request is received from the mobile terminal 2, the progress control unit 331 The battle execution unit 333 is instructed to create display data for displaying the list screen 520. Then, the progress control unit 331 transmits the display data created by the battle execution unit 333 to the mobile terminal 2.

  When the battle execution buttons 411 and 412 on the event screen 410 displayed on the mobile terminal 2 or the selection button 522 on the list screen 520 is pressed and a corresponding participation response is received from the mobile terminal 2, the progress control unit 331 Instruct the participation reception unit 335 to execute the participation reception process. When participation is received by the participation reception unit 335, the progress control unit 331 instructs the battle execution unit 333 to create display data of the battle preparation screens 420 and 440 corresponding to the battle event for which participation has been received. The display data created by the execution unit 333 is transmitted to the mobile terminal 2. On the other hand, when participation is not received by the participation receiving unit 335, the progress control unit 331 instructs the battle execution unit 333 to create display data for the event screen 410, and displays the display data created by the battle execution unit 333 as a portable terminal. 2 to send.

  When the execution control unit 331 instructs execution of the quest or the normal battle, the main game execution unit 332 specifies the player ID included in the quest request or the normal battle request, and corresponds to the specified player ID in the player table. Each piece of information such as possessed character information is extracted. Furthermore, the main game execution unit 332 extracts information related to the character corresponding to the extracted owned character information from the character table. The main game execution unit 332 creates display data for executing a quest or a normal battle based on each extracted information, and passes the created display data to the progress control unit 331. Thereafter, a quest or a normal battle is executed using the created display data.

  When the progress control unit 331 instructs the creation of display data for the event screen 410, the battle execution unit 333 identifies the player ID included in the event screen request, and participates in association with the identified player ID in the battle information table. It is determined whether or not the battle ID is stored.

  When the participation battle ID is stored in association with the identified player ID, that is, when the player has already participated in the battle event, the battle execution unit 333 reads each piece of information corresponding to the participation battle ID from the battle table. Then, display data of the battle preparation screen 420 representing each read information is created. Then, the battle execution unit 333 passes the created display data to the progress control unit 331.

  On the other hand, when the participating battle ID is not stored in association with the identified player ID, that is, when the player has not yet participated in the battle event, the battle execution unit 333 creates display data of the event screen 410. In this case, the battle execution unit 333 extracts, from the battle information table, a battle event in which the player has found an enemy character and a battle event in which the player is notified of a participation request and in which the player can participate.

  Note that the battle execution unit 333 extracts a battle event corresponding to the found battle ID stored in association with the identified player ID as a battle event notified of the participation request to the player in the battle information table. In addition, the battle execution unit 333 extracts a battle event corresponding to the participation request battle ID stored in association with the identified player ID as a battle event notified of the participation request to the player in the battle information table. Further, the battle execution unit 333 is a value obtained by adding the participation value of the player to the total value of the participation values, with the end flag set to OFF in the battle table, the number of participating player IDs not reaching the upper limit of the number of players. Is extracted as a battle event that the player can participate in.

  The battle execution unit 333 determines a battle event that is most recommended among the extracted battle events based on each piece of information stored in the battle table. The battle execution unit 333 reads, from the battle table, information on the battle event in which the player has found the enemy character and information on each determined battle event, and an event screen 410 representing the battle execution buttons 411 and 412 corresponding to each battle event. Create display data for. Then, the battle execution unit 333 passes the created display data to the progress control unit 331.

  When the execution control unit 331 instructs execution of the search process, the battle execution unit 333 uses, for example, a pseudo-random number generated using the current clock counter value of the server 3 as a seed, and the player selects an enemy character. A lottery is performed to select whether or not a discovery has been made. When winning the lottery, the battle execution unit 333 further determines an enemy character and its level using a pseudo-random number generated using the current clock counter value of the server 3 as a seed. Note that the battle execution unit 333 may determine the enemy character as an enemy character that is one level higher than the enemy character that the player has just found.

  In the battle table, the battle execution unit 333 newly registers each piece of information related to the battle event with the determined enemy character with the player ID of the player as the discovery player ID and the current time as the discovery time. Also, the battle execution unit 333 stores the battle ID of the newly registered battle event in the battle information table in association with the player as a discovery battle ID. And the battle | competition execution part 333 produces the display data of the battle preparation screens 420 and 440 showing each information corresponding to the battle | competition event. On the other hand, the battle execution unit 333 recreates the display data of the event screen 410 when the lottery is not won. Then, the battle execution unit 333 passes the created display data to the progress control unit 331.

  In addition, when the execution of the battle is instructed from the progress control unit 331, the battle execution unit 333 identifies the player ID and the battle ID included in the battle request, and the use ID associated with the identified player ID from the player table. And a battle point associated with the specified player ID is extracted from the battle information table. Furthermore, the battle execution unit 333 extracts the consumption value of the character associated with the extracted use ID from the character table. Next, the battle execution unit 333 determines whether or not the extracted consumption value is equal to or less than the battle point. When the consumption value is larger than the battle point, the battle execution unit 333 does not execute the battle event and creates display data of a battle preparation screen indicating that the battle point is insufficient.

  On the other hand, when the consumption value is equal to or lower than the battle point, the battle execution unit 333 subtracts the consumption value from the battle point in the battle information table. Next, the battle execution unit 333 determines whether the player participates in the battle event based on whether or not the participation battle ID associated with the identified player ID is the same as the battle ID included in the battle request in the battle information table. It is determined whether or not. When the player is not a participating player of the battle event, the battle execution unit 333 determines whether or not the found battle ID associated with the identified player ID is the same as the battle ID included in the battle request in the battle information table. It is determined whether or not the player is a player who has found the battle event. If the player is not a player who has found the battle event, the battle execution unit 333 does not execute the battle event, and creates display data of a battle preparation screen indicating that the player has not participated in the battle event.

  On the other hand, when the player is a player who has found the battle event, the battle execution unit 333 stores the identified battle ID as the participating battle ID in the battle information table in association with the identified player ID, and further in the battle table. The specified player ID is stored as a participating player ID in association with the specified battle ID. Thereby, the battle execution unit 333 causes the player to participate in the battle event.

  When the player is a participating player of the battle event, the battle execution unit 333 executes the battle event. The battle execution unit 333 determines a damage amount to be given to the enemy character based on the attack power of the player character and the defense strength of the enemy character, and subtracts the determined damage amount from the enemy character's HP in the battle table. On the other hand, the battle execution unit 333 determines the amount of damage given to the player's character based on the enemy character's attack power and the player's character defense, and subtracts the determined damage amount from the player character's HP. The battle execution unit 333 determines that the player has won when the HP of the enemy character first becomes 0, and determines that the player has lost when the HP of the character of the player has previously become 0.

  When the player wins, the battle execution unit 333 sets an end flag corresponding to the battle event to ON in the battle table, and finds the battle ID, participation battle ID, and participation of each player who participated in the battle event in the battle information table. The battle ID of the battle event is deleted from the requested battle ID. Note that the battle execution unit 333 similarly sets the end flag corresponding to the battle event in the battle table to ON in the battle table even when a certain time has elapsed from the discovery time, and each player who has participated in the battle event in the battle information table. The battle ID of the battle event is deleted from the found battle ID, participation battle ID, and participation request battle ID.

  Further, the battle execution unit 333 reads the reward points from the battle table, adds the read reward points to the game points of each player who participated in the battle event in the battle information table, and increments (+1) the number of wins. Furthermore, the battle execution unit 333 determines an item to be given to each player by lottery and adds it to the owned item information of each player in the player table. Also, the battle execution unit 333 creates display data for displaying a battle effect image and display data for displaying the battle result screens 500 and 510 according to the result of the battle event. Thus, the battle execution unit 333 starts and executes a battle between the character of the specific player and the enemy character in accordance with a request from the specific player.

  In addition, when the progress control unit 331 instructs the creation of display data for the list screen 520, the battle execution unit 333 specifies the player ID included in the list screen request and the order specified by the sorting button 523. The battle execution unit 333 is notified of a battle event in which the identified player has found an enemy character from the battle information table, as well as the case where the display data of the event screen 410 is created, and the player is notified of the participation request. Extract all battle events that can participate. The battle execution unit 333 reads information related to each battle event extracted from the battle table, creates display data of the list screen 520 in which information related to each battle event is arranged in the specified order, and creates the created display data. It is passed to the progress control unit 331.

  When the execution request process is instructed from the progress control unit 331, the participation request notification unit 334 specifies the player ID and the battle ID included in the participation request request. Next, the participation request notifying unit 334 can request the player depending on whether or not the found player ID or the participating player ID associated with the identified battle ID is the same as the identified player ID in the battle table. It is determined whether or not the player is a player. When the player is not a requestable player, the participation request notification unit 334 does not notify other players of a participation request for a battle event.

  On the other hand, if the player is a requestable player, the participation request notifying unit 334 specifies a group including the specified player ID in the group table, and each player other than the requesting player belongs to the specified group. Are extracted. Next, the participation request notification unit 334 reads the total participation value associated with the identified battle ID from the battle table and also reads the participation value associated with each extracted player ID from the battle information table. The participation request notification unit 334 determines whether or not a value obtained by adding the player's participation value to the total participation value is equal to or less than a predetermined upper limit value. Notify participation request.

  The participation request notification unit 334 stores the player ID of the player who notified the participation request in the battle table as the participation request player ID in association with the identified battle ID, and the identified battle ID in the battle information table. An ID is stored in association with the player ID. Thereby, when the player next displays the event screen 410 or the list screen 520 on the portable terminal 2, the battle event corresponding to the identified battle ID is displayed on each screen so that the player can select the event. A request for participation is notified. Further, the participation request notification unit 334 may directly notify the player of the participation request for the battle event by transmitting an e-mail or the like to the player's portable terminal 2 via the server communication unit 31. In this way, the participation request notifying unit 334 notifies the participation request for the battle event to the players included in the group including the requesting player according to the request from the requesting player.

  Next, the participation request notification unit 334 stores the current time as the participation request start time in the battle table in association with the identified battle ID. Next, the participation request notification unit 334 recreates the display data of the battle preparation screens 420 and 440 and passes the created display data to the progress control unit 331.

  Thereafter, the participation request notification unit 334 periodically determines whether or not a battle event is being executed based on whether or not an end flag associated with the identified battle ID is OFF in the battle table. When a battle event is being executed, the participation request notification unit 334 notifies the participation request every time the notification time elapses from the participation request start time, that is, when the notification time has elapsed since the previous participation request was notified. Other groups that have not been selected are sequentially selected, and player IDs included in the selected group are extracted. Next, the participation request notification unit 334 reads the total participation value associated with the identified battle ID from the battle table and also reads the participation value associated with each extracted player ID from the battle information table. The participation request notifying unit 334 determines whether or not a value obtained by adding the player's participation value to the total participation value exceeds a predetermined upper limit value, and only when the upper limit value is not exceeded, the player participates in the battle event. Notify the request. In this way, each time the notification time elapses, the participation request notification unit 334 sequentially selects a group other than the group including the requesting player, and requests the players included in the selected group to participate in the battle event. Notice.

  The participation request notification unit 334 selects each group adjacent to the group that has notified the participation request immediately before as a group that notifies the participation request next. As will be described later, each group is classified so that the latest time when the player to which the player belongs accesses the battle event is evenly distributed, so that the player who notifies the participation request is only the player who has recently accessed, or It is suppressed that it becomes only the player who is not accessing.

  Moreover, the notification time which prescribes | regulates the space | interval which notifies a participation request can be made into predetermined fixed time (for example, 1 minute). The notification time includes the number of players who participated in the battle event in response to the participation request, the number of players executing the battle event, the number of characters of the requesting player who have won the enemy character in the battle event, It may be changed based on at least one of the number of the player characters participating in the battle event, the level of the requesting player, and the number of messages transmitted by the requesting player to other players.

  For example, the participation request notification unit 334 increases the notification time as the number of players participating in the battle event in response to the participation request increases, and decreases the notification time as the number of players participating in the battle event in response to the participation request. shorten. Thereby, when many players have already participated in the battle event, the participation of further players is restricted, and the player is prevented from rushing into one battle event. On the other hand, if there are still few players participating in the battle event, more players can be made to participate as soon as possible, and it is prevented that it takes a long time to win the enemy character.

  In addition, for example, the participation request notification unit 334 increases the notification time as the number of players currently executing the battle event increases, and decreases the notification time as the number of players currently executing the battle event decreases. . As a result, it is possible to prevent more players who want to participate during lunch breaks and commuting hours when there are a large number of players performing a battle event, and to allow more players to participate at midnight when the number of players is small. And the number of participants in each battle event can be made uniform.

  In addition, for example, the participation request notification unit 334 shortens the notification time as the number of wins or the number of participations of the requesting player in the battle event increases. Accordingly, the player frequently participates in the battle event so that the players can gather the participants in the battle event in a shorter time and defeat the enemy character, so that the battle event can be activated.

  Further, for example, the participation request notification unit 334 shortens the notification time as the player level of the requesting player in the battle event is higher. As a result, the player executes the quest or the normal battle more frequently so that the players can gather the participants in the battle event in a shorter time and defeat the enemy character, so the quest or the normal battle can be activated. It becomes.

  In addition, for example, the participation request notification unit 334 shortens the notification time as the number of messages transmitted by the player to the related player or the number of messages solicited to the main game transmitted from the player to other players increases. Accordingly, the player transmits messages more frequently so as to gather the participants in the battle event in a shorter time and defeat the enemy character, so that communication between the players can be activated.

  In addition, the participation request notification unit 334 sets the group that first notifies the participation request when the execution control unit 331 is instructed to execute the participation request process, to another group instead of the group including the requesting player. May be. For example, at least one of a related player related to the requesting player, a player participating in the battle, and a related player related to the player participating in the battle is first notified of the participation request. The group may be included.

  The participation reception unit 335 specifies the player ID and the battle ID included in the participation response when the execution control unit 331 instructs execution of the participation reception process. The participation reception unit 335 reads each piece of information associated with the identified battle ID from the battle table.

  The participation reception unit 335 determines whether or not the player has determined that the match event or the participation request player ID associated with the specified match ID is the same as the player ID included in the participation response in the match table. It is determined whether the player is a discovered player or a player notified of a participation request. In addition, the participation reception unit 335 determines whether or not the battle event is being executed based on whether or not the end flag is set to OFF in the battle table. Furthermore, the participation reception part 335 specifies the number of participating players participating in the battle event from the participating player IDs stored in the battle table. Furthermore, the participation reception unit 335 reads the total participation value associated with the identified battle ID from the battle table, and reads the participation value associated with the identified player ID from the battle information table.

  The participation reception unit 335 is a player who has found the battle event or a player who has been notified of the participation request, the battle event is being executed, the number of participating players has not reached the upper limit of the number of players, and the total participation Only when the value obtained by adding the player's participation value to the value does not exceed the upper limit value, the player's participation in the battle event is accepted.

  When the participation reception unit 335 receives a player's participation in a battle event, the participation reception unit 335 stores the specified battle ID as the participation battle ID in the battle information table in association with the specified player ID, and participates in association with the player. Increment (+1) the number of times. Further, the participation reception unit 335 stores the specified player ID as a participating player ID in association with the specified battle ID in the battle table, and adds the participation value of the newly added player to the total participation value.

  In this way, the participation receiving unit 335 receives the participation of each player in the battle as long as the total of the participation values set for each player participating in the battle event does not exceed the upper limit value. This participation value is set to a smaller value as the strength of each player in the battle event is higher, and is set to a larger value as the strength of each player is lower. Therefore, it is suppressed that only weak players participate in a specific battle event and reach the upper limit of the number of players, and strong players cannot participate in the battle event, and as a result, it is not possible to defeat the enemy character. Alternatively, the participation value may be set to a larger value as the strength of each player in the battle event is higher, and may be set to a smaller value as the strength of each player is lower. In this case, it is possible to prevent only the strong player from participating in the specific battle event and easily defeat the enemy character, and to maintain the game balance appropriately.

  Alternatively, whether the participation value is set to a smaller value or a larger value as the strength of each player in the battle event is higher depends on an average time until the player wins the enemy character in the battle event. May be changed automatically. In that case, for example, when the average time until the player wins the enemy character is a predetermined time or more, the participation value is high for each player in the battle event so that more strong players can participate in the battle event. The smaller the value is set. Conversely, when the average time until the player wins the enemy character is less than a predetermined time, the participation value increases as the strength of each player in the battle event increases so that only strong players do not participate in the battle event. Set to a value.

  The strength of each player includes the parameters of the characters owned by each player, the items owned by each player, the number of times each player participated in the battle event or the number of times won in the battle event, and each of the past battle events. It is determined based on at least one of the player's results.

  For example, among the characters owned by each player, the player's strength is set to a higher value as the sum of the parameters of a predetermined number of characters increases in the descending order of parameters such as attack power, defense power, and HP. Further, for example, the player's strength is set to a higher value as the number of items owned by each player that can activate special effects or items that recover the battle points is larger. In addition, for example, the player's strength is set to a higher value as the number of participation or victory of each player in the battle event is larger. In addition, for example, the strength of the player is set to a higher value as the performance of each player in the past battle event is higher. Accordingly, it is possible to distribute the players who are highly likely to give great damage to the enemy character in a balanced manner.

  Also, when the participation value is set to a smaller value as the strength of each player in the battle event is higher, the upper limit value of the total participation value is not divisible by the participation value set for the weak player, and the remainder is strong. It is set to a value that is equal to or greater than the participation value set for the player. For example, when the upper limit of the total participation value is set to 18, the participation value of the weak player is set to a value that is not divisible by 18 as 10 and the participation value of the strong player is 18 to 10 as 1. The remainder is set to a value less than the remainder (8). This ensures that strong players can participate without only weak players participating in the battle event. Conversely, when the participation value is set to a smaller value as the strength of each player in the battle event is lower, the upper limit value of the total participation value is set to a value that cannot be divided by the participation value set for the strong player. This makes it possible for players who are weak in the battle event to participate.

  Note that the upper limit value of the total participation value may be set according to at least one of a predetermined battle situation, an enemy character parameter, and a requester player character parameter. The predetermined battle situation includes a situation in at least one battle among a battle with a predetermined enemy character, a battle in which a predetermined player participates, and a battle related to a combination of the predetermined enemy character and the player. For example, the upper limit value is an upper limit value in another battle in at least one battle among a battle with a predetermined enemy character, a battle in which a predetermined player participates, and a battle related to a combination of the predetermined enemy character and the player. Is set to a higher value. Alternatively, the upper limit value is an upper limit value in another battle in at least one battle among a battle with a predetermined enemy character, a battle in which a predetermined player participates, and a battle related to a combination of the predetermined enemy character and the player. A lower value may be set. Thereby, it becomes possible to improve the game property in a battle event.

  Further, for example, the upper limit value is set to a lower value as the parameters such as the attack power, defense power, and HP of the enemy character are higher. Thereby, since only a stronger player participates in the battle event that battles against a strong enemy character, the possibility of winning against the enemy character can be increased. Further, for example, the upper limit value is set to a higher value as the parameters such as the attack power, defense power, and HP of the character of the requesting player are higher, and set to a lower value as the parameter is lower. As a result, when the requesting player is strong, the weak player participates in the battle event, and when the requesting player is weak, the strong player participates in the battle event, so the strength of all players participating in the battle event is uniform. It becomes possible to.

  Further, the upper limit value of the total participation value may be changed with the passage of time since the battle event was started. For example, the participation reception unit 335 changes the upper limit value to a larger value every time the notification time elapses after starting the battle event. This makes it possible to add a player who participates in the battle event when the enemy character is not won within a certain period of time, thereby increasing the possibility of winning the enemy character.

  The classification unit 336 classifies each player into a plurality of groups based on the order in which each player accesses the battle event. The classification unit 336 assigns each player to each group according to the order in which the actions are executed when each player executes a specific action for the battle event. For example, the classification unit 336 allocates the player of the mobile terminal 2 that first transmitted the event screen request to the group 1, and then allocates the player of the mobile terminal 2 that transmitted the event screen request to the group 2. Thereafter, the classification unit 336 allocates the player of the mobile terminal 2 that has transmitted the event screen request to the group next to the group to which the player has been allocated immediately before. The classification unit 336 assigns each player to each group by adding the player ID of each player as the belonging player ID of each group in the group table.

  Further, the classification unit 336, when the player of the portable terminal 2 that transmitted the event screen request already belongs to a specific group, that is, when the portable terminal 2 of the player transmits the second or subsequent event screen request, The player is deleted from the group to which the player belongs, and is assigned to the group next to the group to which the player was assigned immediately before. Thereby, each group is classified so that the latest time when the player to which the player belongs accesses the battle event is evenly distributed.

  The classifying unit 336 may classify each player in the order in which the access time to the battle event of each player is close to the current time. In that case, a predetermined number of players whose access times are closest to the current time are classified into group 1, a predetermined number of players whose access times are closest to the current time are classified into group 2, and group N is classified as group N. A predetermined number of players whose access times are farthest from the current time are classified. In addition, the participation request notification unit 334 notifies participation requests for the battle event in order from the players included in the group 1, that is, from the player whose access time is close to the current time. Thereby, since a participation request can be preferentially notified to a player who is highly likely to participate in a battle event, the number of players participating in the battle event can be secured early.

  Further, the classification unit 336 may classify each player based on the order in which each player logs into the game. In that case, the classification unit 336 classifies each player so that the login times to the games of the players included in each group are evenly distributed. The game duration of a player who has been short after logging in is likely to be long, and the participation rate in a battle event is likely to be high. Therefore, it is possible to prevent the participation rate in the battle event of the player who is notified of the participation request from being extremely biased and to maintain the game balance.

  Or the classification | category part 336 may classify | categorize each player into each group in order with the login time to the game of the player contained in each group close to the present time. In this case, the participation request notification unit 334 notifies participation requests for the battle event in order from the players included in the group 1, that is, in order from the player whose login time is close to the current time. Thereby, a participation request is preferentially notified to a player who is highly likely to participate in a battle event, and the number of players participating in the battle event can be secured early.

  Further, the classification unit 336 may classify each player based on the strength of each player in the battle event. In that case, the classification unit 336 classifies each player so that the strengths of the players included in each group are evenly distributed. This prevents the strength of players participating in the battle event from being extremely biased and prevents the game balance from being lost.

  Further, the classification unit 336 may classify each player based on the participation rate of each player in the battle event. In that case, the classification unit 336 classifies each player so that the participation rate of the players included in each group in the battle event is evenly distributed. Thereby, it is possible to prevent the participation rate in the battle event of the player who is notified of the participation request from being extremely biased, and to maintain the game balance.

  Or the classification | category part 336 may classify | categorize each player into each group in order with a high participation rate in the battle | competition event of the player contained in each group. In that case, the participation request notifying unit 334 notifies the participation request to the battle event in order from the players included in the group 1, that is, in order from the player having the higher participation rate in the battle event. Thereby, since a participation request is preferentially notified to a player who is highly likely to participate in a battle event, the number of players participating in the battle event can be secured early. Alternatively, the participation request notification unit 334 may notify the participation request to the battle event in order from the players included in the group N, that is, from the player with the lowest participation rate in the battle event. Thereby, a participation request is preferentially notified to a player who is unlikely to participate in a battle event, and the battle event can be activated.

  Further, in this embodiment, the player who has already participated in a specific battle event is restricted so that it cannot participate in other battle events. Therefore, when the portable terminal 2 of the player participating in the battle event transmits an event screen request, the classification unit 336 does not reclassify the player but reclassifies the battle event when it ends. That is, when the battle event ends, the classification unit 336 reclassifies at least a part of the players in the game including the players who participated in the battle event. This prevents the player from changing to another group while participating in the battle event, and prevents the player who cannot participate in the new battle event from being assigned as the latest player.

  FIG. 9 is a diagram illustrating an example of an operation sequence related to the game processing of the game system 1. This operation sequence cooperates with each element of the portable terminal 2 and the server 3 mainly by the terminal processing unit 25 and the server processing unit 33 based on the programs stored in the terminal storage unit 22 and the server storage unit 32 in advance. And executed.

  First, when the player presses the event button 403 using the operation unit 23 while the home screen 400 is displayed on the display unit 24 of the mobile terminal 2, the browsing execution unit 251 of the mobile terminal 2 sends an event screen request to the terminal. It transmits to the server 3 via the communication part 21 (step S101). When the progress control unit 331 of the server 3 receives an event screen request from the mobile terminal 2, the battle execution unit 333 creates display data for the event screen 410 (step S102). Next, the battle execution unit 333 transmits the created display data to the mobile terminal 2 (step S103). When the display data is received from the server 3 via the terminal communication unit 21, the browsing execution unit 251 of the mobile terminal 2 creates drawing data based on the received display data and causes the display unit 24 to display the event screen 410. (Step S104).

  Next, when the player presses the search button 413 using the operation unit 23 in a state where the event screen 410 is displayed on the display unit 24 of the mobile terminal 2, the browsing execution unit 251 of the mobile terminal 2 sends a search request to the terminal. It transmits to the server 3 via the communication part 21 (step S105). When the progress control unit 331 of the server 3 receives a search request from the mobile terminal 2, the battle execution unit 333 executes a lottery to determine whether the player has found an enemy character, and the detected enemy character and its level. (Step S106). Next, the battle execution unit 333 creates display data of the battle preparation screens 420 and 440 or the event screen 410 depending on whether or not the player has found an enemy character (step S107). Next, the battle execution unit 333 transmits the created display data to the mobile terminal 2 (step S108). When the display data is received from the server 3 via the terminal communication unit 21, the browsing execution unit 251 of the mobile terminal 2 creates drawing data based on the received display data, and displays the battle preparation screens 420 and 440 on the display unit 24. Alternatively, the event screen 410 is displayed (step S109).

  Next, when the player presses the attack button 427 using the operation unit 23 in a state where the battle preparation screens 420 and 440 are displayed on the display unit 24 of the mobile terminal 2, the browsing execution unit 251 of the mobile terminal 2 The request is transmitted to the server 3 via the terminal communication unit 21 (step S110). When the progress control unit 331 of the server 3 receives a battle request from the mobile terminal 2, the battle execution unit 333 executes a battle process (step S111). Details of the battle process will be described later. Next, the battle execution unit 333 creates display data of a battle effect image and display data of the battle result screen 500 or 510 according to the result of the battle event (step S112). Next, the battle execution unit 333 transmits the created display data to the mobile terminal 2 (step S113). When display data is received from the server 3 via the terminal communication unit 21, the browsing execution unit 251 of the mobile terminal 2 creates drawing data based on the received display data, and displays a battle effect image and a battle on the display unit 24. The result screen 500 or 510 is displayed (step S114).

  Thereafter, when the player presses the participation request button 429 using the operation unit 23 in a state where the battle preparation screens 420 and 440 are displayed again on the display unit 24 of the mobile terminal 2, the browsing execution unit 251 of the mobile terminal 2 A participation request is transmitted to the server 3 via the terminal communication unit 21 (step S115). When the progress control unit 331 of the server 3 receives the participation request request from the portable terminal 2, the participation request notification unit 334 executes a participation request process (step S116). Details of the participation request process will be described later. Next, the participation request notification unit 334 recreates the display data of the battle preparation screens 420 and 440 (step S117). Next, the battle execution unit 333 transmits the created display data to the mobile terminal 2 (step S118). When the display data is received from the server 3 via the terminal communication unit 21, the browsing execution unit 251 of the mobile terminal 2 creates drawing data based on the received display data, and displays the battle preparation screens 420 and 440 on the display unit 24. Is displayed (step S119). Thus, the operation sequence related to the game process is completed.

  FIG. 10 is a diagram illustrating an example of an operation sequence related to the list screen display process of the game system 1. This operation sequence cooperates with each element of the portable terminal 2 and the server 3 mainly by the terminal processing unit 25 and the server processing unit 33 based on the programs stored in the terminal storage unit 22 and the server storage unit 32 in advance. And executed.

  First, in a state where the event screen 410 is displayed on the display unit 24 of the portable terminal 2, when the player presses the list button 414 using the operation unit 23, the browsing execution unit 251 of the portable terminal 2 sends a list screen request to the terminal. It transmits to the server 3 via the communication part 21 (step S201). When the progress control unit 331 of the server 3 receives a list screen request from the mobile terminal 2, the battle execution unit 333 creates display data for the list screen 520 (step S202). Next, the battle execution unit 333 transmits the created display data to the mobile terminal 2 (step S203). When display data is received from the server 3 via the terminal communication unit 21, the browsing execution unit 251 of the mobile terminal 2 creates drawing data based on the received display data and causes the display unit 24 to display the list screen 520. (Step S204). Thus, the operation sequence related to the list screen display is completed.

  FIG. 11 is a diagram illustrating an example of an operation sequence related to the participation process of the game system 1. This operation sequence cooperates with each element of the portable terminal 2 and the server 3 mainly by the terminal processing unit 25 and the server processing unit 33 based on the programs stored in the terminal storage unit 22 and the server storage unit 32 in advance. And executed.

  First, in a state where the event screen 410 or the list screen 520 is displayed on the display unit 24 of the mobile terminal 2, when the player presses the battle execution buttons 411, 412 or the selection button 522 using the operation unit 23, The browsing execution unit 251 transmits a participation response to the server 3 via the terminal communication unit 21 (step S301). When the progress control unit 331 of the server 3 receives a participation response from the mobile terminal 2, the participation reception unit 335 executes a participation reception process (step S302). Details of the participation acceptance process will be described later. Next, the battle execution unit 333 creates display data of the event screen 410 or the battle preparation screens 420 and 440 according to the result of the participation reception process (step S303). Next, the battle execution unit 333 transmits the created display data to the mobile terminal 2 (step S304). When the display data is received from the server 3 via the terminal communication unit 21, the browsing execution unit 251 of the mobile terminal 2 creates drawing data based on the received display data, and displays the event screen 410 or the battle preparation on the display unit 24. The screens 420 and 440 are displayed (step S405). This completes the operation sequence related to the participation process.

  FIG. 12 shows an operation flow of battle processing by the battle execution unit 333. The battle process shown in FIG. 12 is executed in step S111 of FIG.

  The battle execution unit 333 first extracts each piece of information associated with the player ID included in the battle request from the player table, the battle information table, and the character table (step S401). Next, the battle execution unit 333 determines whether or not the extracted consumption value is equal to or less than the battle point (step S402). When the consumption value is larger than the battle point (No at Step S402), the battle execution unit 333 does not execute the battle event (Step S403) and ends a series of steps. In this case, the battle execution unit 333 is not the display data of the battle effect image and the display data of the battle result screen 500 or 510 in step S112 of FIG. 9, but the battle preparation screen indicating that the battle points are insufficient. Create display data.

  On the other hand, when the consumption value is equal to or less than the battle point (step S402—Yes), the battle execution unit 333 subtracts the consumption value from the battle point in the battle information table. Next, the battle execution unit 333 determines whether or not the player is a participating player in the battle event (step S404). When the player is a participating player of the battle event (step S404-Yes), the battle execution unit 333 shifts the process to step S407. On the other hand, when the player is not a participating player of the battle event (step S404-No), the battle execution unit 333 determines whether or not the player is a player who has found the battle event (step S405). When the player is not a player who has found the battle event (step S405 No), the battle execution unit 333 does not execute the battle event (step S403) and ends a series of steps. In this case, the battle execution unit 333 creates display data of a battle preparation screen indicating that the player has not participated in the battle event in step S112 of FIG.

  On the other hand, when the player is a player who has found the battle event (step S405—Yes), the battle execution unit 333 causes the player to participate in the battle event (step S406). Next, the battle execution unit 333 executes a battle event (step S407). When the player loses in the battle event (step S408-No), the battle execution unit 333 ends the series of steps. In this case, the battle execution unit 333 creates display data of a battle effect image indicating that the player has lost, and display data of the battle result screen 500 in step S112 of FIG.

  On the other hand, when the player wins the battle event (step S408-Yes), the battle execution unit 333 sets the end flag corresponding to the battle event to ON in the battle table, and ends the battle event (step S406). Next, the battle execution unit 333 updates the game points and the number of wins of each player who participated in the battle event in the battle information table, and gives a privilege to the player (step S407), and ends a series of steps. In this case, the battle execution unit 333 creates display data of a battle effect image indicating that the player has won and display data of the battle result screen 510 in step S112 of FIG.

  FIG. 13 shows an operational flow of participation request processing by the participation request notification unit 334. The participation request process shown in FIG. 10 is executed in step S116 of FIG.

  The participation request notification unit 334 first determines whether or not the player is a player that can be requested (step S501). If the player is not a requestable player, the participation request notifying unit 334 does not notify the other player of the participation request for the battle event, and ends the series of steps.

  On the other hand, if the player is a player that can be requested, the participation request notifying unit 334 specifies a group to which the player belongs in the group table (step S502). Next, the participation request notification unit 334 extracts players other than the requesting player who belong to the specified group (step S503). Next, the participation request notifying unit 334 determines whether or not a value obtained by adding the extracted participation value of the player to the total participation value of the battle events notifying the participation request exceeds a predetermined upper limit value (step S504). . If the added value is equal to or less than the upper limit value (step S504—Yes), the participation request notification unit 334 notifies the player of a participation request for a battle event (step S505). On the other hand, if the added value exceeds the upper limit value (No in step S504), the participation request notification unit 334 does not notify the player of a participation request for a battle event.

  Next, the participation request notification unit 334 determines whether all players other than the requesting player belonging to the identified group have been extracted (step S506). If the participation request notifying unit 334 has not yet extracted all the players (No at Step S506), the process returns to Step S503 and repeats the processes at Steps S503 to S506. On the other hand, when all the players have been extracted (step S506-Yes), the participation request notification unit 334 stores the current time as the participation request start time of the identified battle in the battle table (step S507), and the series of steps is performed. finish.

  FIG. 14 shows an operation flow of the second participation request process by the participation request notification unit 334. The second participation request process shown in FIG. 14 is periodically executed after the participation request process shown in FIG.

  First, the participation request notification unit 334 determines whether or not the target battle event is being executed (step S601). If the target battle event is not being executed (step S601-No), the participation request notification unit 334 ends a series of steps. On the other hand, when the target battle event is being executed (step S601-Yes), the participation request notification unit 334 determines whether the notification time has elapsed since the previous participation request was notified (step S602). . If the notification time has not elapsed (step S602—No), the participation request notification unit 334 returns the process to step S601 and repeats the processes of steps S601 to S602. On the other hand, when the notification time has elapsed (step S602—Yes), the participation request notification unit 334 selects a group that has not yet notified the participation request (step S603).

  Next, the participation request notification unit 334 extracts players belonging to the selected group (step S604). Next, the participation request notification unit 334 determines whether or not a value obtained by adding the extracted participation value of the player to the total participation value of the target battle event exceeds a predetermined upper limit value (step S605). When the added value is equal to or less than the upper limit value (step S605-Yes), the participation request notification unit 334 notifies the player of a participation request for a battle event (step S606). On the other hand, if the added value exceeds the upper limit value (step S605-No), the participation request notification unit 334 does not notify the player of a participation request for a battle event.

  Next, the participation request notification unit 334 determines whether all players belonging to the selected group have been extracted (step S607). If all the players have not yet been extracted (step S607-No), the participation request notification unit 334 returns the process to step S502 and repeats the processes of steps S604 to S607. On the other hand, when the participation request notifying unit 334 has extracted all the players (step S607—Yes), the series of steps ends.

  FIG. 15 shows an operation flow of participation acceptance processing by the participation acceptance unit 335. The participation acceptance process shown in FIG. 15 is executed in step S302 in FIG.

  First, the participation reception unit 335 determines whether or not the player is a player who has found the battle event or a player who has been notified of the participation request (step S701). When the player is a player who has found the battle event or a player whose participation request has been notified (step S701-Yes), the participation reception unit 335 determines whether the battle event is being executed (step S702). When the battle event is being executed (step S702-Yes), the participation reception unit 335 determines whether the number of participating players participating in the battle event is less than the upper limit of the number of players (step S703). When the number of participating players is less than the upper limit of the number of players (step S703-Yes), the participation receiving unit 335 adds a value obtained by adding the extracted participation value of the player to the total participation value of the target battle event. It is determined whether or not the value is exceeded (step S704). When the added value is equal to or less than the upper limit value (step S704-Yes), the participation reception unit 335 receives the player's participation in the battle event (step S705), and ends the series of steps.

  On the other hand, if the player is not a player who has found the battle event or a player whose participation request has been notified (step S701-No), or if the battle event is not being executed (step S702-No), the number of participating players exceeds the upper limit of the player number. When exceeding (step S703-No) or when the added value exceeds the upper limit value (step S704-No), the participation receiving unit 335 performs a series of steps without notifying the player of the participation request for the battle event. Exit.

  FIG. 16 shows an operation flow of group classification processing by the classification unit 336. The group classification process shown in FIG. 16 is executed when each player executes a specific action for the battle event.

  The classification unit 336 first determines whether or not a player who has performed a specific action for a battle event participates in the battle event (step S801). When the player is participating in the battle event (step S801—Yes), the classification unit 336 does not perform any particular processing and ends the series of steps. On the other hand, when the player has not participated in the battle event (step S801-No), the classification unit 336 determines whether the player already belongs to a specific group (step S802). When the player already belongs to a specific group (step S802-Yes), the classification unit 336 deletes the player from the group to which the player belongs (step S803). Next, the classification unit 336 allocates the player to a group next to the group to which the player has been allocated immediately before (Step S804), and ends a series of steps.

  As described above, the server 3 classifies a plurality of players into a plurality of groups, selects a group sequentially each time the notification time elapses, and requests players included in the selected group to participate in a battle event. To be notified. As a result, it is possible to prevent a large number of players from rushing to the battle event, and furthermore, the number of participants is ensured even if each player notified of the participation request is not aware of the participation request. Can be appropriately notified to each player.

  Further, the server 3 accepts participation in the battle event from each player within a range in which the sum of the participation values set for each player participating in the battle event does not exceed the upper limit value. This prevents only strong players from participating in a battle event and easily defeating enemy characters, and conversely, only weak players from participating in an enemy character are prevented from being defeated. Can be maintained.

  In addition, not only players who belong to the same group as the requesting player, limited players such as the requesting player and the friend's player, but also all players are notified of the request for participation in the battle. It becomes possible to expand communication between players.

  Note that the present invention is not limited to this embodiment. For example, the game executed on the mobile terminal 2 may be a hybrid game in which each of the server 3 and the mobile terminal 2 takes part of the processing. In that case, for example, each screen related to the progress of the game is a web display displayed on the mobile terminal 2 based on display data generated by the server 3, and other menu screens and the like are installed in the mobile terminal 2. The native display is displayed by.

  It should be understood by those skilled in the art that various changes, substitutions, and modifications can be made thereto without departing from the spirit and scope of the present invention.

DESCRIPTION OF SYMBOLS 1 Game system 3 Server 31 Server communication part 32 Server memory | storage part 33 Server processing part 331 Progress control part 332 Main game execution part 333 Battle execution part 334 Participation request notification part 335 Participation reception part 336 Classification part

Claims (8)

A game control method in a computer comprising a storage unit and executing a battle game,
For each of a plurality of players, a setting value set according to the strength of each player in the battle game is stored in the storage unit.
In accordance with a request from a specific player among the plurality of players, a battle between the game media of the specific player and the enemy game media is started,
In response to a request from the specific player designated on the screen displayed according to the result of the battle after the result of the battle is determined, the other players of the plurality of players enter the battle. Notification of your participation request,
Receiving the participation of the other player in the battle in a range in which the total of the set values set for each player participating in the battle does not exceed a predetermined upper limit value,
The predetermined upper limit value is a state in which the player who has been set with the first set value receives a maximum number of participations in the battle, and has the second set value that is smaller than the first set value. Set to accept participation in the match,
A game control method characterized by the above.   The game control method according to claim 1, wherein the set value is set to a smaller value as the strength of each player in the competitive game is higher.   The strength of each player is at least one of the parameters of the game media owned by each player, the items owned by each player, the number of times each player has participated in the battle, and the results of each player in the past battle game. The game control method according to claim 2, wherein the game control method is determined based on the two.   The predetermined upper limit value is set according to at least one of a predetermined battle situation, a parameter of the enemy game medium, and a parameter of the game medium of the specific player. The game control method according to claim 1.   The game control method according to any one of claims 1 to 4, wherein the predetermined upper limit value is changed according to a lapse of time after the battle is started. The computer further includes a communication unit,
Further, the player's terminal notified of the participation request is provided with information on each battle for which the player is notified of the participation request, the remaining physical strength of the enemy game medium of each battle, the remaining time of each battle, and The game control method according to any one of claims 1 to 5, wherein display data for arranging and displaying in order based on at least one of rewards obtained in each battle is transmitted via the communication unit. A computer that executes a battle game,
A storage unit that stores, for each of a plurality of players, a setting value set in accordance with the strength of each player in the battle game;
A battle execution unit that starts a battle between the game media of the specific player and the enemy game media in accordance with a request from a specific player among the plurality of players;
In response to a request from the specific player designated on the screen displayed according to the result of the battle after the result of the battle is determined, the other players of the plurality of players enter the battle. A participation request notification section for notifying the participation request,
A participation accepting unit that accepts participation of the other player in the battle within a range in which the total of the set values set for each player participating in the battle does not exceed a predetermined upper limit;
The predetermined upper limit value is a state in which the player who has been set with the first set value receives a maximum number of participations in the battle, and has the second set value that is smaller than the first set value. Set to accept participation in the match,
A computer characterized by that. A computer control program comprising a storage unit and executing a battle game,
For each of a plurality of players, a setting value set according to the strength of each player in the battle game is stored in the storage unit.
In accordance with a request from a specific player among the plurality of players, a battle between the game media of the specific player and the enemy game media is started,
In response to a request from the specific player designated on the screen displayed according to the result of the battle after the result of the battle is determined, the other players of the plurality of players enter the battle. Notification of your participation request,
Allowing the computer to accept participation of the other player in the battle within a range in which the total of the set values set for each player participating in the battle does not exceed a predetermined upper limit;
The predetermined upper limit value is a state in which the player who has been set with the first set value receives a maximum number of participations in the battle, and has the second set value that is smaller than the first set value. Set to accept participation in the match,
A control program characterized by that.

Images