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

Description

Application of Patent Act Article 30, Paragraph 2 Website address: http://tdig. gree-apps. net/ Publication date: July 16, 2013

Application of Patent Act Article 30, Paragraph 2 Website address: http://tdig. gree-apps. net/? mode=card&act=dungeon_top Posted date: July 16, 2013

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

In recent years, servers that provide games to mobile terminals via communication networks have become widespread. Games provided by such servers include those in which a plurality of players can participate (so-called "social games"). As such a social game, for example, a game (a so-called "card battle game") in which cards are used to battle against enemy characters is known (for example, Patent Document 1).

Also known as such a social game is, for example, a game in which a so-called quest is cleared according to a game scenario (a so-called “quest game”). In general, a quest game has a plurality of stages, and the stages are sequentially processed one by one each time the player instructs to proceed.

Japanese Patent Application Laid-Open No. 2008-113768

However, in the conventional quest game, the player needs to give an instruction each time the processing of each stage is executed, and it takes a lot of time and effort to execute the processing of a plurality of stages. Therefore, there is a possibility that the player's desire to continue the game may be lost during the progress of the quest game.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a game control method, a computer, and a control program that enable a player to maintain a desire to continue playing the game.

A control method according to the present invention is a game control method for a computer that executes a game that sequentially executes processing of a plurality of stages, and executes processing of one of the plurality of stages in accordance with a first instruction by a player. and continuously executing the processing of two or more predetermined stages among the plurality of stages in accordance with a second instruction by the player.
The computer may be a mobile terminal, a stationary terminal, a server, etc., as long as it can execute the above procedure.

Further, in the control method according to the present invention, when the processing of the predetermined number of stages is executed according to the second instruction, the execution result of each of the processing of the predetermined number of stages is displayed in the predetermined number of stages. is preferably displayed after all of the processing of .

Further, in the control method according to the present invention, when the processing of the predetermined number of stages is executed according to the second instruction, the item given in the predetermined number of stages is processed in the predetermined number of stages. is preferably given to the player after performing all of

Further, in the control method according to the present invention, when a predetermined number of stages are processed according to the second instruction, a predetermined number of points are obtained from the player's owned points for executing the stage processing. It is preferable to consume the points for the stage of .

Further, in the control method according to the present invention, if a specific event occurs in any stage of the predetermined number of stages executed according to the second instruction, the stage after the stage in which the specific event occurred It is preferable not to perform the processing of the stages consecutively.

Further, in the control method according to the present invention, it is preferable to change the privilege given to the player depending on whether the stage processing is executed according to the first instruction or the second instruction.

Further, in the control method according to the present invention, if the condition for clearing a specific stage out of the predetermined number of stages executed according to the second instruction is not satisfied, the stage after the specific stage is cleared. It is preferred that the treatments are not performed continuously.

Further, in the control method according to the present invention, when the condition for clearing a specific stage out of a predetermined number of stages scheduled to be executed according to the second instruction is not satisfied, the specific stage and the specific stage It is preferable not to run the later stages of processing in succession.

Further, in the control method according to the present invention, when other players related to the player are stored for each player, and processing of a predetermined number of stages is executed according to the second instruction, the other players related to the player It is preferable to give benefits to

Further, in the control method according to the present invention, it is preferable to advance the game field by a fixed distance in each of the plurality of stages.

A computer according to the present invention is a computer that executes a game that sequentially executes processes of a plurality of stages, and is a first execution unit that executes the process of one of a plurality of stages in accordance with a first instruction from a player. and a second execution unit that continuously executes processing of two or more predetermined stages among the plurality of stages in accordance with a second instruction from the player.

A program according to the present invention is a control program for a computer that executes a game that sequentially executes processing of a plurality of stages, and executes processing of one of the plurality of stages in accordance with a first instruction by a player, In accordance with a second instruction by the player, the computer is caused to continuously execute the processing of two or more predetermined stages among the plurality of stages.

The control method, computer, and control program according to the present invention execute the processing of one stage when a first instruction is given by the player, and continuously execute the processing of a plurality of stages when the second instruction is given by the player. Thus, it is possible to continuously execute a plurality of stages according to instructions from the player, and to keep the player's desire to continue playing the game.

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. It is a figure which shows an example of a schematic structure of a server. (a) is a diagram showing an example of the data structure of a player management table, (b) is a diagram showing an example of the data structure of a card management table, and (c) is a diagram showing an example of the data structure of a dungeon management table. It is a diagram. (a) to (d) are diagrams showing an example of a display screen of a mobile terminal. (a) to (d) are diagrams showing other examples of the display screen of the portable terminal. (a) to (d) are diagrams showing still another example of the display screen of the portable terminal. (a) to (c) are diagrams showing still another example of the display screen of the portable terminal. It is a figure which shows an example of the operation|movement sequence of a game system. It is a figure which shows an example of the operation|movement flow of the game progress process by a server. FIG. 10 is a diagram illustrating an example of an operation flow of normal execution processing by a server; FIG. 10 is a diagram illustrating an example of an operation flow of continuous execution processing by a server;

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

1. Overview of this Embodiment In the game system of this embodiment, a player uses a portable terminal to play a game provided by a server. The server executes quests that progress according to the game scenario as events in the provided game. A quest is generally called a search, a mission, or the like, and has a plurality of stages, and the processing of each stage is executed sequentially. Each stage includes a battle (competition) with an enemy character using game media owned by the player, granting special benefits such as specific game media to the player, a so-called RAID battle in which multiple players participate, and a battle with other players. Encounters and/or battles with other players are included. Players can grow their characters and obtain items by executing quests.

Note that game media are electronic data used in games, and include, for example, cards, items, characters, avatars, and the like. Game media are electronic data that can be acquired, possessed, used, managed, exchanged, combined, enhanced, sold, discarded, and/or gifted by players in the game as the game progresses. The mode of use of the game media is not limited to those specified in this specification. In this embodiment, a card registered in the game system in advance will be described as an example of the game content. Cards used in battles with enemy characters have attack power, defense power, physical strength (or HP (hit points)), attributes (e.g., fire, water, lightning, etc.), and rarity (e.g., normal, rare, S ( Super) Rare, SS (Double Super) Rare, SSS (Triple Super) Rare, Legend, etc.), activation rate of skills (special effects), number of attacks in one turn, number of defenses in one match, parameters and/or jobs ( For example, occupation, military type, etc.).

The quest executed in this embodiment explores the dungeon from the entrance to the position where the floor boss is, and each area obtained by dividing the dungeon by a certain distance is set as one stage. For example, if a 200m dungeon has 20 stages, the distance per stage is 10m. Note that the distance of each stage may be set to an arbitrary distance (for example, 1 m, 15 m, etc.) instead of dividing the dungeon into fixed distances. The distance of each stage is changed according to the ability of the character card used by the player so that the higher the ability of the character card used by the player, the longer the distance of each stage, and the lower the ability, the shorter the distance. You may Also, a dungeon may be divided into multiple units (for example, floors) and each unit may be divided into multiple stages. The player progresses a certain distance on the game field in each stage. In the game system of this embodiment, the player progresses the quest by giving a normal execution instruction for executing the processing of one stage or a continuous execution instruction for continuously executing the processing of a plurality of stages. To go. As a result, the player can continuously execute the processing of a plurality of stages with a single instruction, thereby reducing the time and effort required to clear the dungeon, thereby allowing the player to continue playing the game. It is possible to keep the desire.

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

A game system 1 includes at least one mobile terminal 2 and a server 3 . The mobile terminal 2 and the server 3 are interconnected via a communication network, for example, via a base station 4, a mobile communication network 5, a gateway 6, and the Internet 7. A program (for example, a browsing program) executed by the mobile terminal 2 and a program (for example, a game program) executed by the server 3 are communicated using a communication protocol such as Hypertext Transfer Protocol (HTTP). communicate.

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

The mobile terminal 2 connects to the server 3 via the base station 4 , the mobile communication network 5 , the gateway 6 and the Internet 7 and communicates with the server 3 . The mobile terminal 2 requests the server 3 to proceed with the game according to the player's operation of the operation unit 23 (such as buttons). The mobile terminal 2 also receives display data relating to the progress of the game from the server 3 and displays the data. For this purpose, the mobile terminal 2 includes a terminal communication section 21 , a terminal storage section 22 , an operation section 23 , a display section 24 and a terminal processing section 25 .

In this embodiment, a multifunctional mobile phone (so-called "smartphone") is assumed as the mobile terminal 2, but the present invention is not limited to this. The mobile terminal 2 may be used as long as the present invention can be applied. A PC, a notebook PC, or the like may be used.

The terminal communication unit 21 includes a communication interface circuit including an antenna whose sensitive band is a predetermined frequency band, and connects the mobile terminal 2 to a wireless communication network. The terminal communication unit 21 establishes a radio signal line using a CDMA (Code Division Multiple Access) method or the like with the base station 4 via a channel allocated by the base station 4, and communicates with the base station 4. conduct. Then, the terminal communication section 21 transmits the data supplied from the terminal processing section 25 to the server 3 or the like. Also, 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 Wi-Fi (Wireless Fidelity) access point (not shown) according to the wireless communication method of the IEEE802.11 standard.

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, etc. used for processing in the terminal processing unit 25 . For example, the terminal storage unit 22 stores, as driver programs, an input device driver program that controls the operation unit 23, an output device driver program that controls the display unit 24, and the like. The terminal storage unit 22 also stores, as application programs, a program for acquiring and displaying display data relating to the progress of the game. The computer program can be stored in 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) using a known setup program or the like. 22 may be installed. The terminal storage unit 22 also stores, as data, display data, video data, image data, etc. relating to the progress of the game. Furthermore, the terminal storage unit 22 may temporarily store temporary data related to predetermined processing.

The operation unit 23 may be any device as long as it can operate the mobile terminal 2, such as a touch panel and key buttons. The player can use the operation unit 23 to input letters, numbers, symbols, and the like. When operated by the player, the operation unit 23 generates a signal corresponding to the operation. The generated signal is supplied to the terminal processing section 25 as an instruction from the player.

The display unit 24 may also be any device as long as it can display video, images, and the like, such as a liquid crystal display and an organic EL (Electro-Luminescence) display. The display unit 24 displays an image corresponding to the image 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 more processors and their peripheral circuits. The terminal processing unit 25 controls overall operations of the mobile terminal 2, and is, for example, a CPU (Central Processing Unit). The terminal processing unit 25 controls the terminal communication unit 21, the display unit, and the like so that various processes of the mobile terminal 2 are executed in an appropriate procedure based on the programs stored in the terminal storage unit 22, the operation of the operation unit 23, and the like. 24 and the like. 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 . Also, the terminal processing unit 25 can execute a plurality of programs (application programs, etc.) in parallel.

2.1.1. 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 implemented by a program executed by a processor included in the terminal processing unit 25 . Alternatively, the browsing execution unit 251 may be implemented in the mobile terminal 2 as firmware.

The viewing execution unit 251 acquires and displays display data relating to the progress of the game. In other words, the viewing execution unit 251 transmits a request for acquiring display data relating to the progress of the game to the server 3 via the terminal communication unit 21 in accordance with an instruction from the player. In addition, the viewing 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 viewing execution unit 251 analyzes the received display data to specify control data and content data, lays out the specified content data based on the specified control data, and creates drawing data. The viewing execution unit 251 then outputs the created drawing data to the display unit 24 .

2.2. Configuration of Server 3 FIG. 3 is a diagram showing an example of a schematic configuration of the server 3 .

The server 3 advances the game in response to requests from the mobile terminal 2 . The server 3 also creates display data relating to the progress of the game and transmits the created display data to the mobile terminal 2 . For this purpose, the server 3 includes a server communication section 31 , a server storage section 32 and a server processing section 33 .

The server communication unit 31 has a communication interface circuit for connecting the server 3 to the Internet 7 and communicates with the Internet 7 . Then, the server communication unit 31 supplies the data received from the portable terminal 2 or the like to the server processing unit 33 . The server communication unit 31 also transmits data supplied from the server processing unit 33 to the mobile terminal 2 and the like.

The server storage unit 32 includes, for example, at least one of a magnetic tape device, a magnetic disk device, or an optical disk device. The server storage unit 32 stores an operating system program, a driver program, an application program, data, etc. used for processing in the server processing unit 33 . For example, the server storage unit 32 stores, as an application program, a game program for advancing a game and creating display data related to the result. The computer program may be installed in the terminal storage unit 22 from a computer-readable portable recording medium such as CD-ROM, DVD-ROM, etc. using a known setup program or the like. The server storage unit 32 also stores, as data, a player management table (FIG. 4A) for managing players, a card management table (FIG. 4B) for managing cards, and a dungeon management table (FIG. 4B) for managing dungeons. 4(c)), image data and the like relating to the player, cards and enemy characters are stored. Furthermore, the server storage unit 32 may temporarily store temporary data related to predetermined processing.

FIGS. 4A, 4B, and 4C are diagrams showing examples of data structures of various management tables.

FIG. 4(a) shows a player management table. In the player management table, for each player, the identification number (player ID) of the player, the password, the name, the file name of the image data, the identification number (card ID) of the character card (possession card) possessed by the player, the Parameter information about each parameter of the player, quest card information about the character card (quest card) used for the quest, stage information about the stage being executed, RAID boss battle information about the RAID boss battle, player IDs of other players related to the player, etc. is stored.

The parameter information includes the player's level, experience value, HP, stamina, and the like. The level is a parameter for determining the upper limit of HP, the number of other players related to the player, and the like. The experience value is a parameter to which a specific value is added when the battle is won. When the experience value exceeds a predetermined value, the level is incremented (1 increase). HP is a parameter from which a value corresponding to the amount of damage received when attacked by an enemy character in battle is subtracted. When the HP becomes 0, the player loses the battle. HP recovers by using specific items, but it does not recover over time. Stamina is a point for performing stage processing, and is consumed each time stage processing is performed. This stamina is an example of owned points owned by the player. It should be noted that stamina recovers after a certain amount of time has passed or by using a specific item.

The quest card is composed of a predetermined number (for example, three) of player cards set in advance from the possessed cards, and a predetermined number (for example, one) of guest cards arbitrarily designated by the server 3 from other than the possessed cards. be. Guest cards have levels, experience points, and HP. This guest card is given to the player when the quest is completed. The quest card information includes the card ID of each player card and the card ID, level, experience value and HP of the guest card.

The stage information includes the identification number of the dungeon (dungeon ID) being executed by the player in the quest, the identification number of the stage (stage ID), and the like.

The RAID boss battle information includes card IDs of character cards (deck cards) forming a deck used in the RAID boss battle. A deck card is composed of a predetermined number (for example, seven) of cards in possession.

Other players related to the player are other players who belong to the same group as the player, other players who are friends with the player, and rescued the player in past battles with enemy characters or quests. Other players, other players who have competed in the past, and/or other players belonging to a group which has competed in the past, and the like.

FIG. 4(b) shows a card management table. The card management table stores, for each card, the card ID, name, file name of image data, and parameters such as rarity, offensive power, and defensive power.

FIG. 4(c) shows the dungeon management table. The dungeon management table stores, for each dungeon, the dungeon ID, name, file name of image data, distance, number of stages, and stage ID of each stage included in the dungeon.

The server processing unit 33 includes one or more processors and their peripheral circuits. The server processing unit 33 controls overall operations of the server 3, and is, for example, a CPU. The server processing unit 33 controls operations of the server communication unit 31 and the like so that various processes of the server 3 are executed according to appropriate procedures based on programs and the like stored in the server storage unit 32 . The server processing unit 33 executes processing based on programs (operating system programs, driver programs, application programs, etc.) stored in the server storage unit 32 . Also, the server processing unit 33 can execute a plurality of programs (application programs, etc.) in parallel.

2.2.1. Functions of Server Processing Unit 33 FIGS. 5 to 8 are diagrams showing examples of display screens of the portable terminal 2 based on display data created by the server 3. FIG.

FIG. 5(a) shows a home screen 500 displayed when the game is started. The home screen 500 is displayed based on home screen display data received from the server 3 . A list of a plurality of buttons is displayed on the home screen 500 . By tapping the "go exploring" button 501, the server 3 is requested via the terminal communication unit 21 to start the quest game.

FIG. 5(b) shows a quest start screen 510 displayed when a quest game start is requested on the home screen 500 shown in FIG. 5(a). The quest start screen 510 is displayed based on the quest start screen display data received from the server 3 . The quest start screen 510 includes an image 511 of the dungeon currently in progress, the name of the dungeon, the current position in the dungeon and text 512 representing the distance from the current position to the position of the floor boss, and the current status of the entire dungeon. A gauge 513 is displayed that represents the position in the form of a histogram. The quest start screen 510 further displays a “sprint” button 514 , an “explore” button 515 , and an end button 516 . By tapping the “sprint” button 514, the server 3 is requested via the terminal communication unit 21 to continuously execute the processing of a plurality of stages. On the other hand, by tapping the “Explore” button 515, the server 3 is requested via the terminal communication unit 21 to normally execute the processing of one stage. Also, by tapping the end button 516 , the server 3 is requested to end the quest game via the terminal communication unit 21 .

FIG. 5(c) shows a normal battle screen 520 displayed when normal execution is requested on the quest start screen 510 shown in FIG. 5(b) and a normal battle is executed in that stage. The normal battle screen 520 is displayed based on the normal battle screen display data received from the server 3 . A normal battle is performed between the player card and guest card used in the quest game and the enemy character. On the normal battle screen 520, a text 521 indicating that a normal battle with an enemy character will be executed, an image 522 of the enemy character, and a "Fight" button 523 are displayed. By tapping the “fight” button 523, the server 3 is requested via the terminal communication unit 21 to execute a normal battle.

FIG. 5(d) shows a battle result screen 530 displayed when execution of a normal battle is requested on the normal battle screen 520 shown in FIG. 5(c). The battle result screen 530 is displayed based on the battle result screen display data received from the server 3 . The battle result screen 530 displays a text 531 similar to the text 512 in FIG. 5B, a gauge 532 similar to the gauge 513 in FIG. 5B, and a text and image 533 representing the battle result. be. The battle result screen 530 further displays a “sprint” button 514, an “explore” button 515, and an end button 516. FIG. It should be noted that the text 531 indicates from which position to which position the player has moved due to the execution of the processing of the stage, in addition to each piece of information indicated by the text 512 of FIG. 5B.

FIG. 6(a) shows an item grant screen 600 displayed when normal execution is requested on the quest progress screen 510 shown in FIG. 5(b) and an item is granted in that stage. The item grant screen 600 is displayed based on the item grant screen display data received from the server 3 . The item grant screen 600 includes a text 601 similar to the text 512 in FIG. 5B, a gauge 602 similar to the gauge 513 in FIG. Text and image 603 are displayed. The item grant screen 600 further displays a “sprint” button 514, an “explore” button 515, and an end button 516. FIG. Note that the text 601 indicates from which position to which position the player has moved by executing the processing of the stage, in addition to each piece of information indicated by the text 512 in FIG. 5B. Items given in each stage include enhancement items for enhancing the offensive power or defensive power of the character card, recovery items for recovering the player's stamina or HP, and the like. In addition, the items granted in each stage include map items to proceed to other dungeons, and not only when you clear the current dungeon, but also when you acquire the map item, you will be able to proceed to other dungeons. good too.

FIG. 6(b) shows a character card grant screen 610 displayed when normal execution is requested on the quest progress screen 510 shown in FIG. 5(b) and a character card is granted in that stage. The character card giving screen 610 is displayed based on the character card giving screen display data received from the server 3 . A character card grant screen 610 includes a text 611 similar to the text 512 in FIG. 5B, a gauge 612 similar to the gauge 513 in FIG. Text and an image 613 representing the card are displayed. The character card grant screen 610 further displays a "sprint" button 514, an "explore" button 515, and an end button 516. FIG. It should be noted that the text 611 indicates, in addition to each piece of information indicated by the text 512 in FIG. Note that the character card may be one type of items, and the character card may be given on the item giving screen of FIG. 6(a).

FIG. 6(c) shows a RAID boss battle screen 620 displayed when normal execution is requested on the quest progress screen 510 shown in FIG. 5(b) and a RAID boss battle is executed in that stage. The RAID boss battle screen 620 is displayed based on the RAID boss battle screen display data received from the server 3 . A RAID boss battle is a battle in which a plurality of players related to the player cooperate to fight against a RAID boss stronger than the enemy character in the normal battle. A RAID boss battle is performed using a deck made up of deck cards. The RAID boss battle screen 620 displays a text 621 indicating that a battle with the RAID boss will be executed, an image 622 of the RAID boss, and a “Fight” button 623 . By tapping the “Fight” button 623 , the server 3 is requested to execute a RAID boss battle via the terminal communication unit 21 . In this case, the RAID boss battle is executed by the server 3, and a battle result screen similar to the battle result screen 530 shown in FIG. 5(d) is displayed. The RAID boss battle may be started according to the player's selection as described above, or may be started automatically when the player reaches the position where the RAID boss is.

FIG. 6(d) shows a floor boss battle screen 630 displayed when normal execution is requested on the quest progress screen 510 shown in FIG. 5(b) and the position where the floor boss is present is reached. A floor boss battle is held between the player card and guest card used in the quest game and the floor boss. The floor boss battle screen 630 is displayed based on the floor boss battle screen display data received from the server 3 . A floor boss battle screen 630 displays a text 631 similar to the text 512 in FIG. 5B, a gauge 632 similar to the gauge 513 in FIG. Note that the text 631 indicates that the player has reached the position of the floor boss. Execution of a floor boss battle is requested to the server 3 via the terminal communication unit 21 by tapping the "challenge the boss" button 633 . In this case, the battle result screen 530 shown in FIG. 5(d) is displayed. A floor boss battle may be started according to the player's selection as described above, or may be started automatically as soon as the player reaches the location where the floor boss is.

7(a), (b) and (c) show continuous execution screens 700, 710 and 720 that are sequentially displayed when continuous execution is requested on the quest progress screen 510 shown in FIG. 5(b). each indicated. The continuous execution screens 700 , 710 and 720 are displayed based on the continuous execution screen display data received from the server 3 . On the continuous execution screen 700, player cards 701 to 703 and a guest card 704 advance to the right and encounter an enemy character 705 fighting in the first stage. On the continuous execution screen 710, the player cards 701 to 703 and the guest card 704 advance to the right and encounter the character card 706 given in the next stage. On the continuous execution screen 720, text 721 representing the result (success/failure) of continuous execution, player cards 701 to 703 and guest cards 704, enemy characters 705 who fought in each stage, character cards 706 provided, 707 is displayed. In this manner, the continuous execution screen sequentially displays the enemy characters that fight in each stage that is continuously executed, the character cards or items to be granted, and finally displays the results of the continuous execution.

FIG. 7(d) shows a continuous execution result screen 730 displayed subsequent to the continuous execution screens 700, 710 and 720. FIG. The continuous execution result screen 730 is displayed based on the continuous execution result screen display data received from the server 3 . A continuous execution result screen 730 displays a text 731 similar to the text 512 in FIG. 5B, a gauge 732 similar to the gauge 513 in FIG. A text 733 representing the character and an image 735 representing the character card and/or item acquired in each stage are displayed. As shown in the text 531 in FIG. 5(d), the text 601 in FIG. 6(a), the text 611 in FIG. 6(b), and the text 631 in FIG. It is displayed that the distance (10 m) has been progressed, but the text 731 displays that the distance (70 m) of a plurality of consecutively executed stages has been progressed. The text 733 displays the result of the battle in each stage and the character cards and/or items acquired in each stage. In addition, when the position where the floor boss is present is reached as a result of continuous execution, the continuous execution result screen 730 further displays a “challenge the boss” button 734 .

8A and 8B show a continuous execution screen 800 displayed when continuous execution is requested on the quest progress screen 510 shown in FIG. 5B and a RAID boss battle is executed in a specific stage. and 810 are shown. Note that if there is a battle with an enemy character, provision of a character card, and/or provision of an item before the RAID boss battle is executed, the continuous execution screens 800 and 810 are shown in FIGS. The continuous execution screens 700 and/or 710 are subsequently displayed. The continuous execution screen 800 displays player cards 701 to 703 and a guest card 704 advancing rightward and encountering a RAID boss 801 . If a RAID boss battle is executed during continuous execution, the continuous execution is interrupted and a continuous execution screen 810 is displayed. A continuous execution screen 810 displays a text 811 indicating that the player has encountered a RAID boss, the RAID boss 812, player cards 701 to 703, and a guest card 704 .

FIG. 8(c) shows a continuous execution result screen 820 displayed subsequent to the continuous execution screens 800 and 810. FIG. A continuous execution result screen 820 includes a text 821 similar to the text 512 in FIG. 5B, a gauge 822 similar to the gauge 513 in FIG. A text 826 representing the result of stage processing and an image 827 representing character cards and/or items obtained in each stage are displayed. In addition, the continuous execution result screen 820 further displays a RAID boss image 823 , a “select deck” button 824 , and a “fight” button 825 . As shown in FIGS. 8A to 8C, the image of the RAID boss and the appearance of the RAID boss are displayed on the screen so that the player can know that the continuous execution has been interrupted by the appearance of the RAID boss. You can smoothly transition to the RAID boss battle.

2.2.2. Configuration of Server Processing Unit 33 In order to implement the functions described above, the server processing unit 33 includes a control unit 331 , a game progression unit 332 , a normal execution unit 333 , and a continuous execution unit 334 . Each of these units is a functional module implemented by a program executed by a processor included in the server processing unit 33 . Alternatively, each of these units may be implemented in the server 3 as firmware.

Processing by the control unit 331 will be described below.

The control unit 331 controls the start and progress of the game, and appropriately instructs the game progression unit 332 and the like to execute processing.

When receiving a game start request from the portable terminal 2 via the server communication unit 31, the control unit 331 passes the received game start request to a player authentication unit (not shown) and instructs execution of authentication processing. The game start request includes the player ID and password. The control unit 331 creates home screen display data when the player authentication unit successfully authenticates the player. The control unit 331 creates home screen display data for displaying buttons and the like for receiving instructions such as game progress in a predetermined layout. Also, the control unit 331 transmits the created home screen display data to the mobile terminal 2 via the server communication unit 31 .

When receiving a game progress request from the portable terminal 2 via the server communication unit 31, the control unit 331 passes the received game progress request to the game progress unit 332 and instructs execution of game progress processing. The game progress request includes a player ID and a request type. The request type designates one of a quest start request, a normal execution request, a normal battle execution request, a RAID boss battle execution request, a floor boss battle execution request, a continuous execution request, an end request, and the like. Also, the control unit 331 transmits the display data of each screen received from the game progression unit 332 to the mobile terminal 2 via the server communication unit 31 .

Processing by the game progression unit 332 will be described below.

The game progression unit 332 controls the progress of the game and appropriately instructs the normal execution unit 333 or the continuous execution unit 334 to execute normal execution processing or continuous execution processing. Also, the game progression unit 332 passes the display data of each screen created by the game progression unit 332 , the normal execution unit 333 , or the continuous execution unit 334 to the control unit 331 .

The game progress unit 332 identifies the request of the mobile terminal 2 from the request type included in the game progress request received from the control unit 331 .

If the specified request is a quest start request, the game progress unit 332 reads the player management table, and specifies the dungeon ID and stage ID of the dungeon and stage being executed by the player with the player ID included in the game progress request. Then, the game progression unit 332 creates quest start screen display data for displaying a quest start screen for executing the process of the dungeon stage corresponding to the specified dungeon ID and stage ID. The game progression unit 332 reads the image, name, distance, stage information, etc. corresponding to the dungeon ID from the dungeon management table, identifies the position corresponding to the stage ID, and displays each information, buttons, etc. in a predetermined layout. Create quest start screen display data for.

If the specified request is a normal execution request, the game progress section 332 passes the player ID included in the game progress request to the normal execution section 333 and instructs execution of normal execution processing.

When the specified request is a normal battle execution request, the game progress unit 332 reads the player management table, and specifies the HP of the player with the player ID included in the game progress request, the player card, the guest card, and the HP of the guest card. . Furthermore, the game progression unit 332 reads out the card management table and specifies the offensive power and defensive power of the specified player card and guest card.

The game progression unit 332 determines the amount of damage to be given to the enemy character based on the attack power of the player card, the attack power of the guest card, and the defense power of the enemy character, and subtracts the determined amount of damage from the HP of the enemy character. . On the other hand, the game progression section 332 determines the amount of damage to be given to the player based on the offensive power of the enemy character and the defensive power of the player card, and subtracts the determined amount of damage from the HP of the player. Also, the game progression unit 332 determines the amount of damage to be given to the guest card based on the offensive power of the enemy character and the defensive power of the guest card, and subtracts the determined amount of damage from the HP of the guest card. If the HP of the enemy character becomes 0 first, the game progression unit 332 determines that the player has won, and if the HP of the player card or the HP of the guest card becomes 0 first, the player loses. It is determined that

The game progression unit 332 adds a specific value to the player's experience value in the player management table when the player wins, and increments the player's level (increase by 1) when the player's experience value exceeds a predetermined value. do. Similarly, the game progression unit 332 adds a specific value to the experience value of the guest card, and increments the level of the guest card (increase by 1) when the experience value of the guest card exceeds a predetermined value. Then, the game progression unit 332 creates battle execution screen display data for displaying battle effect images and battle result screen display data for displaying battle result details.

If the specified request is a RAID boss battle execution request, the game progress unit 332 reads the player management table and specifies other players related to the player with the player ID included in the game progress request. Also, the game progression unit 332 reads out the player management table and identifies the deck card of the player with the player ID included in the game progression request. Furthermore, the game progression unit 332 reads out the card management table, specifies the attack power and defense power of each specified deck card, and calculates the sum of the attack power and defense power of each deck card as the attack power and defense power of the deck, respectively. Calculate as

The game progression unit 332 determines the amount of damage to be given to the RAID boss based on the attack power of the deck and the defense power of the RAID boss, and subtracts the determined amount of damage from the HP of the RAID boss. On the other hand, the game progression unit 332 determines the amount of damage to be given to the player based on the attack power of the RAID boss and the defense power of the deck, and subtracts the determined amount of damage from the HP of the player. Then, the game progression unit 332 determines that the player has won when the HP of the enemy character becomes 0. On the other hand, when the player's HP becomes 0, the game progression unit 332 continues to battle the RAID boss using character cards of other players related to the player. Then, the game progression unit 332 determines that the player has won when the HP of the enemy character becomes 0, and determines that the player has been defeated when the HP of all other players related to the player becomes 0. judge.

The game progression unit 332 adds a specific value to the player's experience value in the player management table when the player wins, and increments the player's level (increase by 1) when the player's experience value exceeds a predetermined value. do. Similarly, the game progression unit 332 adds a specific value to the experience value of all other players related to the player, and if the experience value of each player exceeds a predetermined value, increments the player's level ( 1). Then, the game progression unit 332 creates battle execution screen display data for displaying battle effect images and battle result screen display data for displaying battle result details.

When the specified request is a floor boss battle execution request, the game progression unit 332 executes a battle between the player cards and guest cards and the floor boss in the same manner as when the specified request is a normal battle execution request. Then, the game progression section 332 creates battle execution screen display data and battle result screen display data for displaying battle effect images and result content.

If the specified request is a continuous execution request, the game progress section 332 passes the player ID included in the game progress request to the continuous execution section 334 and instructs execution of continuous execution processing.

When the identified request is a termination request, the game progression unit 332 ends the quest game and instructs the control unit 331 to create home screen display data. In this case, the control unit 331 creates home screen display data and passes the created home screen display data to the game progression unit 332 .

Processing by the normal execution unit 333 will be described below.

The normal execution unit 333 performs normal execution processing of executing the processing of one stage among a plurality of stages of the quest game according to one instruction by the player (tapping of the “explore” button). Also, the normal execution unit 333 passes the display data of each screen created in the normal execution process to the game progression unit 332 .

The normal execution unit 333 reads out the player management table, and identifies the stamina of the player with the player ID included in the game progress request, the dungeon ID of the dungeon being executed, and the stage ID of the stage. The normal execution unit 333 consumes (subtracts) the consumption points from the stamina on the condition that the specified stamina is equal to or more than the consumption points required for executing the processing of one stage, and the stage is set to 1. advance one. The normal execution unit 333 advances the stage by updating the stage ID in the player management table.

When the progressed stage is the final stage of the dungeon, the normal execution unit 333 determines that the event in that stage is the floor boss battle. In this case, the normal execution unit 333 creates floor boss battle screen display data for displaying, in a predetermined layout, a message indicating that the position where the floor boss is located, a "challenge the boss" button, and the like.

On the other hand, if the progressed stage is not the last stage of the dungeon, the normal execution unit 333 performs the following based on a predetermined standard (for example, with a predetermined probability using a pseudo-random number generated using the current time as a seed). , the event in the stage is determined to be one of normal battle, item grant, character card grant, and RAID boss battle.

When the event in the stage is determined to be a normal battle, the normal execution unit 333 determines an enemy character based on a predetermined standard, and performs a normal battle for displaying the enemy character, the "fight" button, etc. in a predetermined layout. Create screen display data.

On the other hand, when the event in the stage is determined to be an item grant, the normal execution unit 333 determines an item to be granted based on a predetermined criterion, and grants the determined item to the user. Then, the normal execution unit 333 creates item grant screen display data for displaying the granted items and the like in a predetermined layout.

On the other hand, when the event in the stage is decided to give a character card, the normal execution part 333 decides the character card to be given based on a predetermined criterion, and gives the decided character card to the user. Then, the normal execution unit 333 creates character card provision screen display data for displaying the provided character cards and the like in a predetermined layout.

On the other hand, when the event in the stage is determined to be a RAID boss battle, the normal execution unit 333 creates RAID boss battle screen display data for displaying the RAID boss, the "Fight" button, etc. in a predetermined layout.

Processing by the continuous execution unit 334 will be described below.

The continuous execution unit 334 processes two or more predetermined stages (e.g., 10) out of a plurality of stages included in the quest game, according to one instruction by the player (tapping the "sprint" button). Execute continuous execution processing. Also, the continuous execution unit 334 passes the display data of each screen created in the continuous execution process to the game progression unit 332 .

Similarly to the normal execution unit 333, the continuous execution unit 334 identifies the stamina of the player, the dungeon ID of the dungeon and stage being executed, and the stage ID. Consume consumption points from to advance the stage one by one. Note that the continuous execution unit 334 does not consume consumption points from the stamina each time a stage is progressed, but collects the consumption points for the continuously executed stages at the end of the continuous execution processing. may be consumed from

If the progressed stage is the final stage of the dungeon, the continuation unit 334 determines the event in that stage to be the floor boss battle. In this case, the continuous execution unit 334 terminates the continuous execution processing and does not continuously execute the processing of the stage after that stage.

On the other hand, if the progressed stage is not the final stage of the dungeon, the continuous execution unit 334 selects the event in the stage from normal battle, item award, character card award, and RAID boss battle based on a predetermined standard. decide whether

When the event in the stage is determined to be a normal battle, the continuous execution unit 334 determines enemy characters based on a predetermined criterion. Then, the continuous execution section 334 executes a normal battle in the same manner as the normal battle by the game progression section 332 .

When the player's HP or the HP of the guest card becomes 0 as a result of the normal battle and the player loses, the continuous execution unit 334 ends the continuous execution processing and continuously executes the processing of the stage after that stage. do not do. In this way, if the condition for clearing a stage is not satisfied, the continuous execution unit 334 does not continuously execute the processing of the stage after that stage. As a result, it is possible to prevent erroneous progress to a stage that should not be progressed.

Further, even when the player's level or the guest card's level increases as a result of the normal battle, the continuous execution section 334 ends the continuous execution processing and does not continuously execute the processing of the stage after that stage. As a result, the player can know in real time that the level has been raised, and after the level has been raised, can proceed to the next stage after changing various settings.

Further, if the player's HP or the HP of the guest card is equal to or less than a predetermined value before the normal battle, the continuous execution unit 334 ends the continuous execution processing, and continuously executes the processing of the stage after that stage. You can choose not to. The predetermined value is set, for example, to a value predicted to be required to win the next battle. In this way, when the conditions for clearing a stage to be executed are not satisfied, the continuous execution unit 334 does not continuously execute the processing of that stage and the stages after that stage. As a result, the player can recover his HP before starting the normal battle, and the continuous execution process can prevent the player from being unexpectedly defeated by the enemy character due to the normal battle being continuously performed. can. For example, if an item that recovers HP that has become 0 is a special item that is different from an item that recovers HP that is not 0, the player is prevented from consuming the special item that causes HP to become 0. can do.

On the other hand, when it is determined that the event in the stage is to give an item, the continuous execution unit 334 decides the item to give based on a predetermined criterion.

On the other hand, when it is decided to give the character card as the event in the stage, the continuous execution part 334 decides the character card to be given based on a predetermined criterion.

On the other hand, when the event in that stage is determined to be the RAID boss battle, the continuous execution unit 334 ends the continuous execution processing and does not continuously execute the processing of stages subsequent to that stage.

The continuous execution unit 334 terminates the continuous execution process when the number of advanced stages reaches a predetermined number, that is, when all the processes of the predetermined number of stages are executed.

When terminating the continuous execution process, the continuous execution section 334 grants to the player all the items and character cards determined to be granted to the player during the continuous execution.

In addition, when ending the continuous execution process, the continuous execution unit 334 provides a continuous display showing how the enemy characters who fought in each of all the continuously executed stages, the granted items, and/or the character cards are sequentially displayed. Create execution screen display data. If the event in the last stage of continuous execution is a RAID boss battle, the continuous execution unit 334 creates continuous execution screen display data in which the RAID boss is displayed following the enemy character, item and/or character card.

In addition, the continuous execution unit 334 creates continuous execution result screen display data for displaying the execution results and the like of the processes of all stages that have been continuously executed in a predetermined layout. Note that, if the last stage of the continuous execution is the last stage of the dungeon, the continuous execution unit 334 creates continuous execution result screen display data for further displaying a "challenge the boss" button or the like. Further, if the last stage of the continuous execution is a normal battle, and the player's HP or the HP of the guest card becomes 0 and the player is defeated, the continuous execution unit 334 further informs that the HP has become 0. Create the continuous execution result screen display data to be displayed. Further, when the last stage of the continuous execution is the normal battle and the level of the player or the guest card has increased, the continuous execution section 334 creates continuous execution result screen display data for further displaying the fact that the level has increased. do. Further, when the last stage of the continuous execution is the RAID boss battle, the continuous execution unit 334 creates continuous execution result screen display data for further displaying the RAID boss, the "Fight" button, and the like. Further, when the stamina is less than the consumption point, the continuous execution unit 334 creates continuous execution result screen display data for further displaying a message such as that the processing of the stage cannot be executed due to lack of stamina.

Note that the server processing unit 33 may change the privilege given to the player between the normal execution process and the continuous execution process. For example, the continuous execution unit 334 counts the number of times of continuous execution, and when the number of times of continuous execution reaches or exceeds a predetermined number, the player may be given benefits such as granting of items or leveling up. good.

In addition, for example, when performing continuous execution processing, the server processing unit 33 determines the level, attack power, defense power, HP, rarity, skill activation rate, number of attacks per turn, and , an item with a high parameter such as the number of defenses in one battle, or a large number of items may be given. Conversely, when performing the continuous execution process, the server processing unit 33 may give an item with a lower parameter than the item given in the normal execution process or a small number of items.

Similarly, the server processing unit 33 may change consumption points between the normal execution process and the continuous execution process. In that case, the server processing unit 33 may set the consumption points for the continuous execution process to be smaller than the consumption points for the normal execution process. Conversely, the server processing unit 33 may increase the consumption points when performing the continuous execution process more than the consumption points when performing the normal execution process.

Similarly, the server processing unit 33 may change parameters such as attack power, defense power and/or HP in the normal battle between the normal execution process and the continuous execution process. In that case, the server processing unit 33 may set the parameter for continuous execution processing higher than the parameter for normal execution processing. Conversely, the server processing unit 33 may set the parameter for continuous execution processing lower than the parameter for normal execution processing.

Similarly, the server processing unit 33 may change the experience value given when winning the normal battle between the normal execution process and the continuous execution process. In that case, the server processing unit 33 may set the experience value given when performing the continuous execution process higher than the experience value given when performing the normal execution process. Conversely, the server processing unit 33 may set the experience value to be given when performing the continuous execution process to be lower than the experience value to be given when performing the normal execution process.

By making the privilege given when performing continuous execution processing larger than the privilege given when performing normal execution processing, performing continuous execution processing becomes attractive to the player, and the use of continuous execution processing rate can be improved. Therefore, the player can clear the dungeon in a shorter period of time, and the game provider can have the player complete more dungeons. On the other hand, if the benefit given when performing the continuous execution process is made smaller than the benefit given when performing the normal execution process, the player will receive a larger benefit when clearing the dungeon over a long period of time. can be obtained. Therefore, the player strategically selects whether to perform the continuous execution process or the normal execution process, which makes it possible to improve the interest of the game.

Moreover, each of the above-mentioned benefits given to the player when the continuous execution process is performed may be given to other players related to the player in the same way. For example, when the player who has performed the continuous execution process has other players accompany him to the dungeon, the server processing unit 33 also gives the above benefits to the other players who accompany him. Alternatively, the server processing unit 33 may give each of the above benefits to other players who have participated in the RAID boss battle.

FIG. 9 is a diagram showing an example of an operation sequence of the game system 1. As shown in FIG. Note that the operation sequence described below is based on programs stored in advance in the terminal storage unit 22 and the server storage unit 32, mainly by the terminal processing unit 25 and the server processing unit 33. Executed in cooperation with each element.

The player uses the operation unit 23 of the mobile terminal 2 to give an instruction to start the game. The viewing execution unit 251 receives a player ID and password from the player using the operation unit 23, and transmits a game start request including the received player ID and password to the server 3 via the terminal communication unit 21 (step S101). .

When receiving a game start request from the mobile terminal 2 via the server communication unit 31, the control unit 331 of the server 3 passes the player ID and password included in the received game start request to the player authentication unit, and performs authentication processing. Execution is instructed (step S102).

When the authentication by the player authentication unit is successful, the control unit 331 creates home screen display data (step S103).

The control unit 331 transmits the created home screen display data to the mobile terminal 2 via the server communication unit 31 (step S104).

When receiving the home screen display data from the server 3 via the terminal communication section 21, the browsing execution section 251 of the mobile terminal 2 creates drawing data based on the received home screen display data. Also, the viewing execution unit 251 outputs the created drawing data to the display unit 24 to display the home screen 500 (step S105).

Next, in response to an instruction from the player using the operation unit 23, the browsing execution unit 251 sends a game progress request including the request type corresponding to the instruction and the player ID of the player via the terminal communication unit 21. to the server 3 (step S106).

It should be noted that when the "go exploring" button 501 on the home screen 500 of FIG. 5(a) is tapped, the request type is a quest start request. Also, the quest start screen 510 in FIG. 5(b), the battle result screen 530 in FIG. 5(d), the item grant screen 600 in FIG. 6(a), the character card grant screen 610 in FIG. When button 515 is tapped, the request type is a normal execution request. Also, when the "Fight" button 523 on the normal battle screen 520 in FIG. 5C is tapped, the request type is a normal battle execution request. Also, when the "Fight" button 623 on the RAID boss battle screen 620 in FIG. 6C is tapped, the request type becomes a RAID boss battle execution request. Further, when the "challenge the boss" button 633 on the floor boss battle screen 630 in FIG. 6(d), the "challenge the boss" button 734 on the continuous execution result screen 730 in FIG. The type is a floor boss battle execution request. In addition, the quest start screen 510 in FIG. 5(b), the battle result screen 530 in FIG. 5(d), the item grant screen 600 in FIG. 6(a), the character card grant screen 610 in FIG. When the "sprint" button 514 is tapped, the request type becomes a continuous execution request. 5(b), the battle result screen 530 of FIG. 5(d), the item grant screen 600 of FIG. 6(a), the character card grant screen 610 of FIG. 6(b), etc. When 516 is tapped, the request type becomes a termination request.

When receiving a game progress request from the mobile terminal 2 via the server communication unit 31, the control unit 331 passes the received game progress request to the game progress unit 332 and instructs execution of game progress processing. The game progression section 332 executes the game progression process when instructed to execute the game progression process by the control section 331 (step S107). In the game progress process, each part of the server processing unit 33 creates display data corresponding to the received game progress request, and the game progress unit 332 passes the created display data to the control unit 331 . Details of the game progress processing will be described later.

Next, the control section 331 transmits each display data received from the game progression section 332 to the portable terminal 2 via the server communication section 31 (step S108).

When each display data or the like is received from the server 3 via the terminal communication unit 21, the browsing execution unit 251 creates drawing data based on the received display data. Also, the browsing execution unit 251 outputs the created drawing data to the display unit 24 and displays the corresponding screen (step S109). After that, the processing of steps S106 to S109 is repeated.

FIG. 10 is a diagram showing an example of an operation flow of game progress processing by the game progress section 332. As shown in FIG. The game progress process shown in FIG. 10 is executed in step S107 of FIG.

First, the game progression unit 332 identifies the request of the mobile terminal 2 from the request type included in the game progression request received from the control unit 331 (step S201).

If the specified request is a quest start request (step S202-Yes), the game progression unit 332 creates quest start screen display data (step S203). Next, the game progression unit 332 passes the created quest start screen display data to the control unit 331 (step S215), and ends the series of steps.

On the other hand, if the specified request is a normal execution request (step S202-No, step S204-Yes), the game progression unit 332 instructs the normal execution unit 333 to execute normal execution processing, and the normal execution unit 333 performs normal execution. Processing is executed (step S205). In the normal execution process, the normal execution unit 333 executes the process of one stage of the quest game, creates display data for each screen according to the result, and passes it to the game progression unit 332 . Details of the normal execution process will be described later. Next, the game progression section 332 passes the display data received from the game progression section 332 to the control section 331 (step S215), and ends the series of steps.

On the other hand, if the identified request is a normal battle execution request (step S204-No, step S206-Yes), the game progression unit 332 executes a normal battle and creates battle execution screen display data and battle result screen display data. (step S207). Next, the game progression unit 332 passes the created battle execution screen display data and battle result screen display data to the control unit 331 (step S215), and ends the series of steps.

On the other hand, if the identified request is a RAID boss battle execution request (step S206-No, step S208-Yes), the game progression unit 332 executes the RAID boss battle and creates battle execution screen display data and battle result screen display data. (step S209). Next, the game progression unit 332 passes the created battle execution screen display data and battle result screen display data to the control unit 331 (step S215), and ends the series of steps.

On the other hand, if the identified request is a floor boss battle execution request (step S208-No, step S210-Yes), the game progression unit 332 executes the floor boss battle and creates battle execution screen display data and battle result screen display data. (step S211). Next, the game progression unit 332 passes the created battle execution screen display data and battle result screen display data to the control unit 331 (step S215), and ends the series of steps.

On the other hand, if the specified request is a continuous execution request (step S210-No, step S212-Yes), the game progression unit 332 instructs the continuous execution unit 334 to execute continuous execution processing, and the continuous execution unit 334 executes continuous execution. Processing is executed (step S213). In the continuous execution process, the continuous execution section 334 continuously executes the processing of a plurality of stages of the quest game, creates continuous execution screen display data and continuous execution result screen display data according to the results, and executes the game progression section. Hand over to 332. Details of the continuous execution process will be described later. Next, the game progression unit 332 passes the consecutive execution screen display data and the consecutive execution result screen display data received from the game progression unit 332 to the control unit 331 (step S215), and ends the series of steps.

On the other hand, if the specified request is neither of the above, that is, if it is a termination request (step S212-No), the game progression unit 332 terminates the quest game and instructs the control unit 331 to create home screen display data. do. The control unit 331 creates home screen display data and passes it to the game progression unit 332 (step S214). Next, the game progression unit 332 passes the consecutive execution screen display data and the consecutive execution result screen display data received from the game progression unit 332 to the control unit 331 (step S215), and ends the series of steps.

FIG. 11 shows an example of an operational flow of normal execution processing by the normal execution unit 333 . The normal execution process shown in FIG. 11 is executed in step S205 of FIG.

First, the normal execution unit 333 determines whether or not the stamina in the player management table is equal to or greater than consumption points (step S301).

If the stamina is less than the consumption points (step S301-No), the normal execution unit 333 creates display data for displaying that the stage processing cannot be executed due to lack of stamina (step S302). . Next, the normal execution unit 333 passes the created display data to the game progression unit 332 (step S315), and ends the series of steps.

On the other hand, if the stamina is equal to or more than the consumption points (step S301-No), the normal execution unit 333 subtracts the consumption points from the stamina (step S303), and advances the stage by one (step S304).

Next, the normal execution unit 333 determines whether or not the progressed stage is the final stage of the dungeon (step S305).

If the advanced stage is the last stage of the dungeon (step S305-Yes), the normal execution unit 333 determines that the event in that stage is the floor boss battle, and creates floor boss battle screen display data (step S306). . Next, the normal execution unit 333 passes the created floor boss battle screen display data to the game progression unit 332 (step S315), and ends the series of steps.

On the other hand, if the progressed stage is not the last stage of the dungeon (step S305-No), the normal execution unit 333 performs the normal battle, item grant, character card grant, and RAID event on the stage based on a predetermined standard. One of the boss battles is determined (step S307).

When the normal execution unit 333 determines that the event in the stage is a normal battle (step S308-Yes), the normal execution unit 333 determines an enemy character based on a predetermined criterion, and creates normal battle screen display data (step S309). Next, the normal execution unit 333 passes the generated normal battle screen display data to the game progression unit 332 (step S315), and ends the series of steps.

On the other hand, when the normal execution unit 333 determines that the event in the stage is to give an item (step S308-No, step S310-Yes), the normal execution unit 333 decides an item to be given based on a predetermined criterion, and gives the item to the user. At the same time, item grant screen display data is created (step S311). Next, the normal execution unit 333 passes the created item grant screen display data to the game progression unit 332 (step S315), and ends the series of steps.

On the other hand, when the normal execution unit 333 determines that the event in the stage is to give a character card (step S310-No, step S312-Yes), the character card to be given is determined based on a predetermined standard, and the character card is given. While giving to the user, character card giving screen display data is created (step S313). Next, the normal execution unit 333 passes the created character card giving screen display data to the game progression unit 332 (step S315), and ends the series of steps.

On the other hand, when the normal execution unit 333 determines that the event in the stage is other than normal battle item grant and character card grant, that is, when the RAID boss battle is determined (step S310-No), the normal execution unit 333 creates RAID boss battle screen display data ( step S312). Next, the normal execution unit 333 passes the created RAID boss battle screen display data to the game progression unit 332 (step S315), and ends the series of steps.

FIG. 12 shows an example of an operational flow of continuous execution processing by the continuous execution unit 334 . The continuous execution process shown in FIG. 12 is executed in step S213 of FIG.

First, the continuous execution unit 334 determines whether or not the stamina in the player management table is equal to or greater than the consumption points (step S401).

If the stamina is less than the consumption points (step S401-No), the continuous execution unit 334 proceeds to step S416.

On the other hand, if the stamina is equal to or greater than the consumption points (step S401-Yes), the continuous execution unit 334 subtracts the consumption points from the stamina (step S402) and advances the stage by one (step S403).

Next, the continuous execution unit 334 determines whether or not the progressed stage is the last stage of the dungeon (step S404).

If the progressed stage is the last stage of the dungeon (step S404-Yes), the continuous execution unit 334 determines that the event in that stage is the floor boss battle, and the process proceeds to step S416.

On the other hand, if the progressed stage is not the last stage of the dungeon (step S404-No), the continuous execution unit 334 sets the events in the stage to normal battle, item grant, character card grant, and RAID based on predetermined criteria. One of the boss battles is determined (step S405).

When the event in the stage is determined to be a normal battle (step S406-Yes), the continuous execution unit 334 determines an enemy character based on a predetermined criterion and executes a normal battle (step S407).

Next, the continuous execution unit 334 determines whether or not the player's HP or the HP of the guest card becomes 0 as a result of the normal battle and the player is defeated (step S408). If the player loses (step S408-Yes), the continuous execution unit 334 proceeds to step S416.

On the other hand, when the player wins (step S408-No), the continuous execution unit 334 determines whether the level of the player or the guest card has increased (step S409). If the player's level has increased (step S409-Yes), the continuous execution unit 334 shifts the process to step S416, and if the player's level has not increased (step S409-No), shifts the process to step S415. do.

On the other hand, when the continuous execution unit 334 determines that the event in the stage is to give an item (step S406-No, step S410-Yes), the consecutive execution unit 334 decides an item to be given to the player based on a predetermined criterion (step S411), The process proceeds to step S415.

On the other hand, if the continuous execution unit 334 decides to give the character card for the event in that stage (step S410-No, step S412-Yes), it decides the character card to be given to the player based on a predetermined criterion (step S413). ), and the process proceeds to step S415.

On the other hand, if the event in the stage is determined to be other than normal battle item grant and character card grant, ie, a RAID boss battle (step S412-No), the continuous execution unit 334 starts the RAID boss battle (step S414), and proceeds to step S416. Migrate processing.

In step S415, the continuous execution unit 334 determines whether or not the number of advanced stages has reached a predetermined number (step S415). If the number of advanced stages has not reached the predetermined number (step S415—No), the continuous execution unit 334 returns the process to step S401, and repeats the processes after step S401.

On the other hand, when the number of advanced stages reaches a predetermined number (step S415-Yes), the continuous execution unit 334 gives the player all the items and character cards determined in step S411 (step S416).

Next, the continuous execution unit 334 generates continuous execution screen display data showing how the enemy characters who fought in each of the continuously executed stages, the granted items, the granted character cards, or the RAID bosses are sequentially displayed. to create In addition, the continuous execution unit 334 creates continuous execution result screen display data for displaying the results of the successively executed stages in a predetermined layout (step S417).

Next, the normal execution unit 333 passes the created continuous execution screen display data and continuous execution result screen display data to the game progression unit 332 (step S418), and ends the series of steps.

As described above, the server 3 executes the processing of one stage according to the normal execution instruction from the player, and continuously executes the processing of a plurality of stages according to the continuous execution instruction from the player. As a result, the player can continuously execute the processing of a plurality of stages with a single instruction, thereby reducing the time and effort required to clear the dungeon, thereby allowing the player to continue playing the game. It is possible to keep the desire.

For example, if the distance of one stage is 10m and one stage takes 3 seconds, in order to clear a 200m dungeon, the user would have to give instructions 20 times before clearing the dungeon in normal execution. , which takes 60 seconds. On the other hand, in continuous execution, the user can clear the dungeon in 6 seconds with two operations.

In addition, in the continuous execution process of the present embodiment, the stage progresses by a predetermined number of stages instead of progressing to the goal of the dungeon at once, so the player can control the progress of the quest within a certain range. You can get the feeling of being there.

In addition, the present invention is not limited to this embodiment. For example, in the present embodiment, the server 3 executes the game, but the server 3 may be omitted and the mobile terminal 2 may execute the game. The terminal storage unit 22 stores information about the player of the mobile terminal 2, a card management table, a dungeon management table, and the like in the player management table. 3 has the same function as each part of the server processing part 33 of No. 3. The terminal processing unit 25 transmits and receives each information within the terminal processing unit 25 instead of transmitting and receiving each information via the terminal communication unit 21 and the server communication unit 31 .

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.

1 game system 2 mobile terminal 3 server 31 server communication unit 32 server storage unit 33 server processing unit 331 control unit 332 game progression unit 333 normal execution unit 334 continuous execution unit

Claims (12)

A computer game control method comprising a storage unit and a processing unit,
the storage unit stores information about a plurality of events and information about parameter values associated with a player;
The processing unit is
progressing one of the plurality of events when a first request by the player is obtained, and changing the parameter value associated with the player according to the player's victory in the one event; death,
If a second request by the player is obtained, the plurality of events are run in succession, and the parameter value associated with the player is changed in response to the player's victory in each of the plurality of events. including
The amount of change in the parameter value according to the player's victory in the one event progressed according to the first request is determined by the player in the one event out of the plurality of events progressed according to the second request. Different from the amount of change in the parameter value according to the victory of
A control method characterized by: 2. The control method according to claim 1, wherein said processing unit further comprises displaying progress results of each of said plurality of events after all of said plurality of events have progressed continuously. When the plurality of events includes an event of giving a predetermined game content, the processing unit provides the predetermined game content to the player after all of the plurality of events have progressed continuously. 3. A control method according to claim 1 or 2, further comprising: 4. The method according to any one of claims 1 to 3, wherein, when a specific event occurs while the plurality of events are continuously progressing, the processing unit terminates progress of an event after the specific event among the plurality of events. The control method according to any one of the items. If a condition for clearing the one event is not satisfied while the plurality of events are continuously progressing, the processing unit may reduce the progression of the event after the one event among the plurality of events. The control method according to any one of claims 1 to 4, which terminates. The storage unit stores information about other players related to the player,
The processing unit according to any one of claims 1 to 5, further comprising giving a privilege to said other player related to said player after all of said plurality of events have progressed continuously. control method. The storage unit stores information about the plurality of player game media associated with the player, the plurality of player game media competing against a first game content appearing in a specific battle event among the plurality of events. is stored and
When the specific battle event occurs, the processing unit determines the result of the battle between the first game medium and the plurality of player game mediums based on information regarding the plurality of player game mediums associated with the player. The control method according to any one of claims 1 to 6, wherein The storage unit stores information about other players related to the player,
When the parameter value associated with the player reaches a predetermined value in the specific battle event, the processing unit controls the first game medium and the plurality of game media associated with the other player associated with the player. 8. The control method according to claim 7, wherein the result of a battle with other player game media is determined. 9. The control method according to claim 8, wherein said processing unit determines that said player has been defeated when said parameter value associated with said other player reaches said predetermined value in said specific battle event. 10. The processing unit according to claim 8, wherein the processing unit determines that the player has won when the parameter value associated with the first game content reaches the predetermined value in the specific battle event. control method. a storage unit that stores information about a plurality of events and information about parameter values associated with players;
progressing one of the plurality of events when a first request by the player is obtained, and changing the parameter value associated with the player according to the player's victory in the one event; death,
If a second request by the player is obtained, the plurality of events are run in succession, and the parameter value associated with the player is changed in response to the player's victory in each of the plurality of events. , a processing unit, and
with
The amount of change in the parameter value according to the player's victory in the one event progressed according to the first request is determined by the player in the one event out of the plurality of events progressed according to the second request. Different from the amount of change in the parameter value according to the victory of
A computer characterized by: A computer control program comprising a storage unit and a processing unit,
the storage unit stores information about a plurality of events and information about parameter values associated with a player;
in the processing unit,
progressing one of the plurality of events when a first request by the player is obtained, and changing the parameter value associated with the player according to the player's victory in the one event; death,
If a second request by the player is obtained, the plurality of events are run in succession, and the parameter value associated with the player is changed in response to the player's victory in each of the plurality of events. ,
causing the computer to perform
The amount of change in the parameter value according to the player's victory in the one event progressed according to the first request is determined by the player in the one event out of the plurality of events progressed according to the second request. Different from the amount of change in the parameter value according to the victory of
A control program characterized by:

Images