Game system and program

The game system enhances team cooperation and motivation by allowing character resurrection and strategic gameplay, addressing the issue of reduced contribution due to character death in team battle games.

JP7584174B2Active Publication Date: 2024-11-15KONAMI DIGITAL ENTERTAINMENT CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2023141975
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2023-09-01
Publication Date
2024-11-15
Estimated Expiration
2037-06-09

AI Technical Summary

Technical Problem

In team battle type action games, when a player's character dies, the user cannot contribute to the team for a certain period, leading to a decrease in motivation due to reduced cooperation opportunities.

Method used

A game system that includes a character control unit transitioning characters to a lower ability state under certain conditions, allowing resurrection by other team members, with a win/loss determination based on character actions, and incorporating a common field for team cooperation.

Benefits of technology

Enhances team cooperation by providing more opportunities for character revival and strategic gameplay, maintaining player motivation and ensuring fair competition.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007584174000001
    Figure 0007584174000001
  • Figure 0007584174000002
    Figure 0007584174000002
  • Figure 0007584174000003
    Figure 0007584174000003
Patent Text Reader

Abstract

To increase opportunity for cooperation within a team in a team match type action game.SOLUTION: A game system includes: a character control part for activating a related character for each user information within a common field within a team, based on operation for each user identified by user information that belongs to a team; a character state control part for shifting a character to a second state having a lower capacity than a first state on condition of satisfaction of the predetermined, first condition for the character in the first state, and for shifting the character to a third state having a limited activity of the character on condition of satisfaction of a predetermined, second condition for the character in the second state; a revival control part for reviving the character in the second state to the first state, based on another character that belongs to the same team as that of the character; and a victory / defeat determination part for determining victory or defeat of a team, based on a result of activity of a character by the character control part.SELECTED DRAWING: Figure 7
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a game system and a program. [Background technology]

[0002] There are action games in which characters operated by multiple users each fight against enemy characters while the game progresses (for example, Patent Document 1). For example, in team battles, cooperation among team members is an important factor for gaining an advantage in the battle. Generally, when a character operated by a user receives damage from an attack by an opponent and dies, the user and the team pay a heavy price, such as being unable to participate in battles for a certain period of time or until the next battle, or the opponent being awarded many points. For this reason, players cooperate within the team to play in order to prevent the death of the characters of the team members. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2010-207404 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, even if a team cooperates, it is not always possible to continue playing without any of the team members' characters dying. When a user's character dies, that user cannot contribute to the team for a certain period of time, which can cause a decrease in motivation.

[0005] One of the objectives of some aspects of the present invention is to provide a game system and program that provides more opportunities for cooperation within a team in a team-based action game.

[0006] Another aspect of the present invention has as an object to provide a game system and a program that enable the effects described in the embodiments described below to be achieved. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems, one aspect of the present invention is a game system comprising: a character control unit that causes a character associated with each user information belonging to a team to act within a common field within the team based on operations of each user identified by user information belonging to the team; a character state control unit that transitions the character in a first state to a second state in which abilities are reduced compared to the first state, provided that a predetermined first condition is satisfied for the character in the first state, and transitions the character in the second state to a third state in which the character's activity is restricted, provided that a predetermined second condition is satisfied for the character in the second state; a resurrection control unit that resurrects the character in the second state to the first state based on other characters belonging to the same team as the character; and a win / loss determination unit that determines a win / loss for the team based on the results of the character's activities performed by the character control unit.

[0008] Another aspect of the present invention is a program for causing a computer to function as the above-described game system. [Brief description of the drawings]

[0009] [Figure 1] FIG. 2 is a diagram showing an example of a field according to the first embodiment. [Diagram 2] FIG. 2 is a diagram showing an example of a play screen in a normal room according to the first embodiment. [Diagram 3] FIG. 2 is a diagram showing an example of a play screen in a boss room according to the first embodiment. [Figure 4] 1 is a block diagram showing an example of the configuration of a game system according to a first embodiment. [Diagram 5] FIG. 1 is a diagram showing an example of a hardware configuration of a game device according to a first embodiment. [Figure 6] FIG. 2 is a diagram showing an example of the hardware configuration of a game server according to the first embodiment. [Figure 7] FIG. 1 is a block diagram showing an example of the configuration of a game device and a game server according to a first embodiment. [Figure 8] 6 is a flowchart showing an example of an occupancy determination process according to the first embodiment. [Figure 9] 11 is a flowchart showing a first example of a winning / losing determination process according to the first embodiment. [Figure 10] 10 is a flowchart showing a second example of the winning / losing determination process according to the first embodiment. [Figure 11] FIG. 4 is a diagram showing an example of points given when a room is occupied according to the first embodiment. [Figure 12] FIG. 11 is a diagram showing an example of settings of the number of occupied rooms and a bonus coefficient according to the first embodiment. [Figure 13] FIG. 13 is a diagram showing an example of settings for the appearance method of a normal NPC according to the second embodiment. [Figure 14] 13A to 13C are diagrams showing the difference in processing between normal NPCs and boss NPCs according to the third embodiment. [Figure 15] 13 is a flowchart showing an example of a countdown process in a battle play according to the fourth embodiment. [Figure 16] FIG. 13 is a diagram showing an example of the appearance of a player character in each state according to the fifth embodiment. [Figure 17] FIG. 13 is a block diagram showing an example of a detailed configuration of a character control unit according to a fifth embodiment. [Figure 18] 13 is a flowchart showing an example of a state transition process according to the fifth embodiment. [Figure 19] FIG. 23 is a diagram showing a display example of a treasure chest item according to the sixth embodiment. [Figure 20] FIG. 23 is a diagram showing a display example of a normal item according to the sixth embodiment. [Figure 21] 23 is a flowchart showing an example of a reward granting process according to the sixth embodiment. [Figure 22] FIG. 23 is a view showing an example of the display of an effect on a play screen according to the seventh embodiment. [Diagram 23] FIG. 23 is a diagram showing an example of effect setting information according to the seventh embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] [First embodiment] Hereinafter, a first embodiment of the present invention will be described with reference to the drawings.

[0011] [Game Overview] First, an overview of an example of a game according to the present embodiment will be described. For example, the game according to the present embodiment is an action game in which characters (hereinafter also referred to as "player characters") operated by each of a plurality of users fight enemy characters while progressing through the game, and a team battle mode will be described as an example here. The number of teams may be two teams, or may be three or more teams, but here, a battle between two teams (i.e., a one-team battle) will be described as an example. Since there are player characters operated by each of a plurality of users for each team, it is a multi-player versus multi-player battle.

[0012] When a user starts playing a game, he or she decides on their own team and the opposing team before the match. After member matching is performed to decide which users will join their own team, member matching is performed on the opposing team. For example, one team consists of four people, and the match will be four against four. Note that the number of people on one team may be any other number. Matching of the own team may be a one-off random matching by the server device, or a matching of a team formed by users. The opposing team will be randomly matched by the server device. Note that to participate in a team match, it may be possible to consume specific items such as points or tickets set in the game.

[0013] A character is a person, animal, object (for example, a vehicle) that appears in a game. After team member matching is performed, a user selects a player character that the user will operate. For example, a player character is a warrior (person) that is the operation target of the user playing the game. The player character operated by a user may be one, or may be two or more in the form of a group (party). In the case of two or more, the user can play by switching between any one of the characters. In this embodiment, the description will be given assuming that each user operates one player character.

[0014] The player character is associated with parameters that affect the user's play, such as HP (Hit Point), MP (Magic Point), attack power, and defense power, as indicators of abilities. HP is a value indicating physical strength or vitality, and is a parameter that is a point for determining whether or not the game can be continued. This HP decreases due to attacks from enemies, and if it becomes equal to or lower than a predetermined value (for example, "0"), the game cannot be continued. MP is a value consumed when the player character uses an item such as a special ability or a special weapon. Attack power and defense power are values ​​indicating the player character's attack-related ability and defense-related ability, respectively. Attack power is a parameter indicating the magnitude of damage to an attack target, and is related to the amount of decrease in the HP of the attack target. Defense power is a parameter indicating resistance to damage when an attack is received, and is related to the reduction in the amount of decrease in HP. For example, attack power and defense power are set individually for each player character as the abilities of the player character. On the other hand, HP and MP are associated with the user who operates the player character. Note that HP and MP may be associated with the player character.

[0015] In addition, the specification may be such that a character to accompany the player character can be selected. The character supports the user's play by defeating enemy characters in place of or in cooperation with the player character, restoring the player character's HP, and so on. For example, the character to accompany is a character that acts autonomously by AI (artificial intelligence) without being operated by the user. There are several types of characters that can be selected as the character to accompany, and the effect differs depending on which character is to be brought along.

[0016] Furthermore, by equipping the player character with items, the player character's abilities can be improved. Items are classified into a number of categories. For example, items are classified into three categories: "weapons," "armor," and "special weapons." The abilities of a player character include parameters such as the player character's attack power and defense power, and the ability to perform special attacks by possessing a special weapon. The types of categories and the number of classifications can be determined arbitrarily.

[0017] Specifically, a "weapon" is an item that improves the attack power and other parameters of the player character. "Armor" is an equipment item that improves the defensive power and other parameters of the player character. A "special weapon" is an item that can perform an attack that causes a large amount of damage, such as an explosion, after a certain period of time has passed. For example, the user can obtain these items by winning a lottery or by clearing a certain event.

[0018] In addition, each of the player characters or items that can be equipped to the player characters has a characteristic that indicates the characteristics of each ability, and the type and power of the attack change depending on the combination of the characteristics. Therefore, it is necessary to consider a strategy depending on the player character or the items equipped to the player character. In addition, the opponent's character or the items equipped to the player character also have characteristics, and superiority or inferiority occurs depending on the compatibility of the opponent's character combination, so it is necessary to consider a strategy. Characteristics are, for example, abilities related to the character's actions (attack power, etc.) and abilities that affect actions (recovery skills, etc.). Specifically, for example, characteristics include "high attack power," "has recovery skills," "can attack high places with thrown weapons," "can deal large damage to characters with specific attributes," "has fast movement speed," "can attack enemies at a distance," "can deal damage over a wide area," etc.

[0019] Next, the field where the match takes place in the game space will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of a field according to this embodiment. In the illustrated field FLD, a match takes place between the blue team and the red team. The field FLD has four types of "rooms (areas)" as multiple areas common to both teams: a "start room", a "normal room", a "passage", and a "boss room".

[0020] Each team has its own start room. In the illustrated example, start room BS is the start room for the blue team, and start room RS is the start room for the red team. When the match begins, the player characters of each team start from their respective start rooms. When HP reaches 0 and a restart (respawn) is required, the game will also be restarted from this start room.

[0021] The normal rooms are rooms that each team is to occupy. In the illustrated example, rooms A, B, and C are rooms that the blue team occupies as an initial state at the start of the match play. Meanwhile, rooms D, E, and F are rooms that the red team occupies as an initial state at the start of the match play. In the normal rooms, NPCs (non-player characters) of the camp of the occupying side are present. NPCs are characters that do not require user operation and are controlled by game processing executed by a computer. Hereinafter, the NPCs present in the normal rooms are also referred to as "normal NPCs". The normal NPCs correspond to the team that is occupying either the blue team or the red team, and oppose attacks from player characters of the opponent team as characters of the camp of the occupying side. For example, when a normal NPC is defeated in a normal room, the team that defeated it will occupy the normal room. On the other hand, if a team fails to defeat a normal NPC in a normal room, the team that defeated the NPC will fail to occupy the room, and the team that originally occupied the room will continue to occupy the normal room.

[0022] The corridor is a room that cannot be occupied and is an area for moving to another room (in this case, a room that is initially occupied by the opposing team).

[0023] A boss room is a room where a boss character appears and is the room that can be occupied. The boss character is an NPC, but unlike normal NPCs, it is not a character of any camp. Therefore, in the initial state at the start of a battle, the boss room is not occupied by any team. In the following, the NPC that exists in this boss room is also called the "boss NPC". A boss NPC is a character that has higher attack and defense power than a normal NPC and can be attacked by either team. For example, when a boss NPC is defeated, the team that inflicted more damage on the boss NPC will occupy the boss room.

[0024] There are different types of fields where the battle is played, and the layout of the rooms differs for each field. Here, as an example, the rooms are arranged symmetrically from the viewpoint of equality for each of the competing teams. In the illustrated field FLD, the blue team's room is arranged on the left side, and the red team's room is arranged on the right side, so that the rooms are arranged symmetrically. A door DR is provided between each room and the adjacent room. Through this door DR, it is possible to move between the adjacent rooms. Specifically, the start room BS of the blue team is connected to room A, the room A is connected to room B, the room B is connected to room C and the boss room, and the room C is connected to the room F of the red team via a passageway, through the door DR. On the other hand, the start room RS of the red team is connected to room D, the room D is connected to room E, the room E is connected to room F and the boss room, and the room F is connected to the room C of the blue team via a passageway, through the door DR. The player characters of both teams can move between the field FLD without any restrictions, as it is a common area. It is also possible to prevent the player characters of the opponent team from entering only the start room.

[0025] Next, the basic rules of the game will be explained. The team that occupies the most rooms within the time limit (for example, 3 minutes) will be the winner. For example, each player character of each team moves within the field according to the operation of each user, and occupies rooms while fighting. The team that occupies the most rooms at the end of the time limit is determined to be the winner. The occupation of rooms will be explained in detail below.

[0026] In the normal room, the opposing teams (blue team and red team) compete to take the room by occupying it. In the normal room occupied by the blue team, there are normal NPCs from the blue team, who will attack any player characters from the red team that enter the room. These normal NPCs can be attacked by player characters from the red team. A hit detection is performed by each team's attacks, and depending on the degree of the hit (degree of accuracy, attack power, etc.), damage is inflicted on the attacked party and their HP is reduced. Conversely, in this normal room, player characters from the blue team cannot attack normal NPCs (there is no hit detection even if they attack), and normal NPCs do not attack player characters from the blue team.

[0027] In a normal room, if the normal NPC defeat status meets a predetermined occupancy condition that has been set in advance, the attacking team can occupy that normal room. The normal NPC defeat status is the number of normal NPCs appearing in that normal room. An example of a predetermined occupancy condition is that all normal NPCs in the room are defeated (HP becomes "0") (i.e., the number of normal NPCs becomes 0). When all normal NPCs in the room are defeated by the player character of the red team, the room becomes occupied by the red team.

[0028] When a normal room is occupied by the red team, normal NPCs from the red team will appear in the room. The normal NPCs from the red team that appear can be attacked by the blue team's player characters. In this state, the red team's player characters cannot attack the normal NPCs (there is no hit detection even if they attack), and the normal NPCs do not attack the red team's player characters. When all the normal NPCs in the room are defeated by the blue team's player characters, the room is once again occupied by the blue team. This process is repeated, with both teams taking turns occupying normal rooms. In this way, a normal room is occupied by one team, and normal NPCs from both teams are not mixed in at the same time.

[0029] The above-mentioned predetermined occupancy condition for a normal room is not limited to all normal NPCs in the room being defeated (HP becomes "0"), and may be other conditions. For example, the predetermined occupancy condition may be that the number of normal NPCs in the room is a predetermined number or less (e.g., 2 or less), or that the number of normal NPCs in the room that have been defeated is a predetermined number or more (e.g., 10 or more).

[0030] Also, when playing against other teams in a standard room, the bottom of the screen will change to the color of the team that is occupying the room. This makes it easier to see which team is occupying the room during a match. FIG. 2 is a diagram showing an example of a play screen in a normal room. The play screen G10 shown in the figure displays the inside of a normal room. The area FL at the bottom of the play screen G10 corresponds to the floor of the room. When this area FL is occupied by the blue team, it becomes blue (or a color similar to blue), and when it is occupied by the red team, it becomes red (or a color similar to red). Note that the area that is changed to the color of the occupying team may be another area in the play screen.

[0031] A map MA of the field is displayed at the top of the play screen G10. A position mark PS indicating the location of the room in the battle is displayed on the map MA. Symbols NP1 to NP3 indicate normal NPCs present in the room, and symbol P1 indicates the player character attempting to defeat the normal NPC. Note that, although there is only one player character in this figure, there may be multiple player characters on the same team or multiple player characters on the opponent's team.

[0032] Basically, there are no restrictions on the movement of the player characters, and they can move to any room. The rooms have a certain amount of space, and each player character can move freely within the room in response to the operations of each user.

[0033] In the boss room, a boss NPC appears. The boss NPC is not a member of either team. In other words, the boss NPC does not correspond to any one team, but attacks either team, and can be attacked by either team. When the boss NPC is defeated, the team that inflicts the most damage on the boss NPC will occupy the boss room. In the boss room, the boss NPC appears only once per battle. Therefore, once a boss room is occupied by one team, the other team cannot reoccupy it, and the occupying team (camp) will not change until the end of the battle. In other words, there is only one chance to occupy the boss room during a battle in one field. Note that there may be multiple boss rooms in a field, but the boss will only appear once during a battle in each boss room.

[0034] FIG. 3 is a diagram showing an example of a play screen in a boss room. The play screen G20 shown in the figure displays the state inside the boss room. Unlike the play screen G10 of a normal room, the boss room is not occupied during a battle, so no display indicating the occupancy status (display of team color) is performed. Also, the symbol BNP indicates the boss NPC present in this room, the symbols PB1 and PB2 indicate the player characters of the blue team who are trying to defeat the boss NPC, and the symbols PR1 and PR2 indicate the player characters of the red team who are also trying to defeat the boss NPC. The boss NPC has higher HP, attack power, defense power, etc. than the normal NPC, and more attacks are required to defeat it. Therefore, when the boss NPC appears in the boss room and the battle begins, the player characters of each team gather in the boss room to occupy the boss room, and each team cooperates to attack so that they can inflict more damage on the boss NPC. Since the boss room cannot be retaken, occupying the boss room ensures the occupation of at least one room, which works more favorably in the battle situation than occupying a normal room. By occupying a boss room, the parameters of the player character of the occupying side may be changed in an advantageous direction (for example, HP recovery, etc.). Also, the occupation of a boss room may be set to correspond to a predetermined multiple of the occupation of a normal room.

[0035] [System Configuration] Next, the system configuration of the game system 1 according to this embodiment will be described. FIG. 4 is a block diagram showing an example of the configuration of the game system 1 according to this embodiment. The game system 1 includes computer devices, namely, a game device 10-1, a game device 10-2, a game device 10-3, and the like, and a game server 30, and these computer devices are connected via a network NW. Since the game devices 10-1, 10-2, and 10-3 have the same configuration, when there is no particular need to distinguish them, the descriptions such as "-1" and "-2" will be omitted and they will be described as the game devices 10. Here, three game devices 10 are illustrated, but any number of game devices 10 may be connected to the game server 30.

[0036] The game server 30 is a server device that provides a game that can be played on the game device 10. For example, the game server 30 provides a control program (game control program) of a game that can be played on the game device 10 so that the game device 10 can download the program. The game server 30 also stores various setting information and history information necessary for the game played on the game device 10, and transmits the information to the game device 10 as necessary. The game server 30 also executes processing that needs to be executed on the server side among the processing of the game played on the game device 10. The game control program downloaded by the game device 10 may be stored not only in the game server 30, but also in another downloadable server device. The game control program may also be provided to the game device 10 by a storage medium such as a DVD-ROM, a CD-ROM, or a memory card.

[0037] The game device 10 executes a game control program provided by the game server 30. For example, the game device 10 is a computer device used by a user, and may be a home-use stationary game machine, a portable game machine, an arcade game machine installed in a game center or the like, a PC (Personal Computer), a tablet PC, a mobile phone such as a smartphone or a feature phone, a personal digital assistant (PDA), or the like. In this embodiment, the game device 10 will be described as being a portable game machine.

[0038] The network NW may be, for example, the Internet, a mobile phone network, a PHS (Personal Handy-phone System) network, a VPN (Virtual Private Network), a dedicated communication line network, a WAN (Wide Area Network), a LAN (Local Area Network), a PSTN (Public A communications network is a network that is composed of a public switched telephone network (PSTN), a switched telephone network (SPN), or a combination of these.

[0039] 5 is a diagram showing an example of a hardware configuration of a game device 10 according to this embodiment. The game device 10 includes, for example, a CPU (Central Processing Unit) 11, a communication unit 12, an input unit 13, a display unit 14, and a storage unit 15, and communicates with a game server 30 and other devices connected via a network NW via the communication unit 12. These components are connected to each other via a bus so that they can communicate with each other. The CPU 11 executes various programs stored in the storage unit 15 and controls each unit of the game device 10.

[0040] The communication unit 12 communicates with the game server 30 and other devices via the network NW based on the control of the CPU 11. The input unit 13 includes a plurality of operation buttons through which user operations are input, and outputs the input operation information to the CPU 11. Note that the input unit 13 may be another input device, such as a touch panel integrated with a display, a controller provided with a plurality of operation buttons, a keyboard, a mouse, a touch pad, or a microphone through which various instructions are input by voice. The display unit 14 is a display that displays information such as images and text, and is configured to include, for example, a liquid crystal display panel, an organic EL (ElectroLuminescence) display panel, etc. For example, the display unit 14 displays game play images.

[0041] The storage unit 15 includes, for example, a hard disk drive (HDD), a solid state drive (SSD), an electrically erasable programmable read-only memory (EEPROM), a read-only memory (ROM), a random access memory (RAM), and the like, and stores various information, images, programs (including game control programs), and the like that are processed by the game device 10. Note that the storage unit 15 is not limited to being built into the game device 10, and may be an external storage device connected via a digital input / output port such as a USB. Furthermore, the game device 10 may be configured to include hardware configurations such as a speaker, an audio output terminal, a camera, a gyro sensor, and a GPS (Global Positioning System) receiving module (not shown).

[0042] 6 is a diagram showing an example of a hardware configuration of the game server 30 according to this embodiment. The game server 30 includes, for example, a CPU 31, a communication unit 32, an input unit 33, and a storage unit 35, and communicates with a plurality of game devices 10 and other devices connected via a network NW via the communication unit 32. These components are connected to each other via a bus so that they can communicate with each other. The CPU 31 executes a game control program stored in the storage unit 35, and provides a game that can be played on the plurality of game devices 10.

[0043] Under the control of the CPU 31, the communication unit 32 communicates with a plurality of game devices 10 and other devices via the network NW. The input unit 33 is, for example, a keyboard, a mouse, a touch pad, a microphone for inputting various instructions by voice, or other input devices.

[0044] The storage unit 35 includes, for example, an HDD, an EEPROM, a RAM, and the like, and stores a game control program, an application program, various setting information and history information necessary for the game, and the like. The storage unit 35 is not limited to being built into the game server 30, and may be an external storage device connected via a digital input / output port such as a USB. The storage unit 35 may be an external storage device physically separated from the game server 30, or may be connected to the game server 30 via a network NW. The game server 30 may be configured to include hardware configurations such as a display unit, a speaker, and an audio output terminal (not shown).

[0045] [Functional configuration] Next, the functional configuration of the game device 10 and the game server 30 included in the game system 1 will be described with reference to Fig. 7. Fig. 7 is a block diagram showing an example of the configuration of the game device 10 and the game server 30 included in the game system 1 according to this embodiment.

[0046] [Functional configuration of game device 10] First, the configuration of the game device 10 will be described. The game device 10 includes a game control unit 110 as a functional configuration realized by the CPU 11 executing a game control program stored in the storage unit 15. The game control unit 110 controls the game play process. For example, the game control unit 110 includes a server control information acquisition unit 111, a character control unit 112, a normal NPC control unit 113, a battle control unit 114, and a display control unit 115.

[0047] The server control information acquisition unit 111 acquires data related to game processing from the game server 30 via the communication unit 12. For example, the server control information acquisition unit 111 acquires data related to a player character selectable by the user, data related to items possessed and equipable to the player character, etc. In addition, the server control information acquisition unit 111 acquires data based on the processing results of game processing executed by the game server 30 and data based on the processing results of game processing executed on other game devices 10 from the game server 30 via the communication unit 12.

[0048] The character control unit 112 controls the activities of the player character within the field FLD based on the user's operation on the input unit 13. Activity is a general term for movement and motion. Movement is the action (motion) associated with attack, defense, obtaining an item, and the like. Furthermore, the character control unit 112 changes the values ​​of HP and MP in response to attacking or being attacked in a battle play. Furthermore, the character control unit 112 transmits control information of the player character (such as information on position and motion, and values ​​of HP and MP) to the game server 30 via the communication unit 12.

[0049] The normal NPC control unit 113 controls the normal NPCs in each normal room. For example, the normal NPC control unit 113 controls the activities of the normal NPCs, such as making a normal NPC of the camp occupying the room (a normal NPC corresponding to the occupying team) appear in each normal room and attacking the player characters of the opponent team.

[0050] The match control unit 114 applies the match rules in match play, judges whether an attack hits the normal NPC, and determines the amount and type of damage based on the hit judgment result. For example, in a match between a normal NPC controlled by the normal NPC control unit 113 and a player character controlled by the character control unit 112, the match control unit 114 applies the match rules, judges whether an attack hits the normal NPC, and determines the amount and type of damage based on the hit judgment result. The match rules may be, for example, that an attack on a normal NPC is possible from a player character of a camp (team) different from that of the normal NPC, but not possible from a player character of the same camp (team). The match control unit 114 may restrict attacks on a normal NPC from player characters of the same camp (team), or may not restrict attacks themselves and may not perform hit judgment.

[0051] The match control unit 114 also transmits information indicating the hit judgment result of an attack from the player character to the normal NPC or the amount or type of damage to the game server 30 via the communication unit 12. For example, the game server 30 changes the HP value of the normal NPC based on the hit judgment result or the information indicating the amount or type of damage. Meanwhile, the match control unit 114 outputs the hit judgment result of an attack from the normal NPC to the player character or the information indicating the amount or type of damage to the character control unit 112. For example, the character control unit 112 changes the HP value of the player character based on the hit judgment result or the information indicating the amount or type of damage.

[0052] In addition, in a battle play in the boss room, the battle control unit 114 performs hit judgment by an attack, and determines the amount of damage and the type of damage based on the hit judgment result in a battle between the boss NPC controlled by the game server 30 and the player character controlled by the character control unit 112. In addition, the battle control unit 114 transmits the hit judgment result of the attack from the player character to the boss NPC or information indicating the amount of damage or the type of damage to the game server 30 via the communication unit 12. For example, the game server 30 changes the value of the HP of the boss NPC based on the hit judgment result or information indicating the amount of damage or the type of damage. On the other hand, the battle control unit 114 outputs the hit judgment result of the attack from the boss NPC to the player character or information indicating the amount of damage or the type of damage to the character control unit 112. For example, the character control unit 112 changes the value of the HP of the player character based on the hit judgment result or information indicating the amount of damage or the type of damage.

[0053] The display control unit 115 generates game images to be displayed as a game screen, and displays them on the display unit 14. For example, based on the control result by the character control unit 112, and data based on game processing executed by the game server 30 acquired by the server control information acquisition unit 111, or data based on game processing executed by another game device 10, the display control unit 115 generates display images such as the appearance of each room in the field, player characters of each team, normal NPCs, boss NPCs, and effects corresponding to attacks of each character, and displays them as a play screen on the display unit 14 (for example, see the play screens in FIGS. 2 and 3).

[0054] [Functional configuration of game server 30] Next, the configuration of the game server 30 will be described. The game server 30 includes a server control unit 310 as a functional configuration realized by the CPU 31 executing a program stored in the storage unit 35. For example, the server control unit 310 transmits data related to the game stored in the storage unit 35 (for example, data related to characters and items) to the game device 10 via the communication unit 32. The server control unit 310 also acquires control information of a player character controlled based on an operation of a user in each game device 10 from each game device 10 via the communication unit 32. The server control unit 310 then transmits the control information of each player character acquired from each game device 10 to game devices 10 other than the game device 10 from which the information was acquired. This makes it possible to display images of player characters operated by multiple users in a common field on the play screen of each game device 10. The server control unit 310 also executes processes required on the server device side, such as control of a boss NPC that performs processing in common for each game device 10, occupancy determination of a room, and victory determination of a team. The configuration of the game server 30 will be described in detail below.

[0055] First, a description will be given of the data stored in the storage unit 35 of the game server 30. For example, the storage unit 35 includes a user data storage unit 351, a team data storage unit 352, a character data storage unit 353, an item data storage unit 354, and a possession data storage unit 355.

[0056] The user data storage unit 351 stores user data related to a user (player) who plays the game. The user data is associated with a user ID, a user name, a level, HP, MP, player character data, equipment items, and the like. The user ID is identification information of the user. The user name is the name of the user displayed in the game. The level is a value that increases according to the degree of game progress by the user's play. The HP and MP store the values ​​of the HP and MP of the player character operated by the user. The player character data stores the character ID of the player character selected by the user and character parameters such as the attack power and defense power of the player character. The equipment items are associated with information (e.g., item ID) indicating the equipment items set by the user. These data are also stored in the storage unit 15 of the game device 10.

[0057] The team data storage unit 352 stores team data related to the team, such as user information (e.g., user ID) belonging to the team, room occupancy status by each team, and win / loss history. For example, the team data is associated with the team ID (team identification information), the user ID of the team, information indicating the occupied room (room identification information, room ID), win / loss history, and the like.

[0058] The character data storage unit 353 stores character data that the user can select as a player character, as well as character data related to normal NPCs and boss NPCs. The character data is associated with a character ID, a character name, attributes, characteristics, character parameters, and the like. The character ID is identification information of the character. The character name is the name of the character. The attributes include "fire", "water", "wood", "darkness", "holy", and the like, and one of the attributes is set for each character. "Fire", "water", and "wood" are in a relationship of superiority or inferiority to each other. For example, the attribute "water" is superior to the attribute "fire", the attribute "wood" is superior to the attribute "water", and the attribute "fire" is superior to the attribute "wood". Incidentally, "darkness" and "holy" are information indicating attack or defense having special abilities. As mentioned above, traits indicate the characteristics of each character's individual abilities, such as "high attack power," "has recovery skills," "can attack high places with thrown weapons," "can deal large damage to characters with specific attributes," "fast movement speed," "can attack enemies at a distance," and "can deal damage over a wide area." Character parameters include the character's attack power and defense power. Normal NPCs and boss NPCs have levels set that correspond to the abilities of each NPC (attack power, defense power, etc.).

[0059] The item data storage unit 354 stores item data related to items that can be equipped to the player character. The item data is associated with an item ID, an item name, a category, an attribute, and an item parameter. The item ID is identification information of the item. The item name is the name of the item. The category of each item (for example, one of "weapon", "armor", and "special weapon") is stored in the category. The attribute is stored in the attribute (one of "fire", "water", "wood", "darkness", and "holy") set to each item. The item parameters are set with values ​​of attack power, defense power, HP, MP, etc. of each item, and equipping an item enhances (increases) the attack power, defense power, HP, MP, etc. of the player character. Note that there may be an exclusive item that can be equipped only to a specific character, and information indicating the exclusive item may also be included in the item data.

[0060] The possession data storage unit 355 stores possession data of items possessed by the user. For example, the possession data stores data (e.g., item IDs) related to items acquired by the user through a lottery or by clearing a specific event, in association with the user ID. The user can select items to equip the player character from among the items stored in this possession data.

[0061] Next, a description will be given of the functional configuration of the server control unit 310. For example, as shown in Fig. 7, the server control unit 310 includes a terminal control information acquisition unit 311, a boss NPC control unit 312, a normal NPC state synchronization unit 313, a player character synchronization unit 314, an occupation determination unit 315, a win / lose determination unit 316, and a reward granting unit 317.

[0062] The terminal control information acquisition unit 311 acquires various information based on the game processing executed in each game device 10 from each game device 10 via the communication unit 32. For example, the terminal control information acquisition unit 311 acquires player character control information (information related to activities such as position, HP and MP values, etc.) from each game device 10. In addition, the terminal control information acquisition unit 311 acquires information indicating the hit judgment results of normal NPCs and boss NPCs in battle play, or the amount and type of damage from each game device 10.

[0063] The boss NPC control unit 312 controls the boss NPC in the boss room. For example, the boss NPC control unit 312 makes the boss NPC appear in the boss room, and controls the movement of the appeared boss NPC, attacks on each player character, and changes in the value of HP according to attacks from each player character. The boss NPC control unit 312 changes the value of HP of the boss NPC based on the hit judgment result of the attack from the player character to the boss NPC or information indicating the amount of damage or the type of damage acquired from each game device 10. When the value of HP of the boss NPC becomes "0", the boss NPC control unit 312 makes the boss NPC disappear (die). The boss NPC control unit 312 also transmits control information of the boss NPC (information on position and movement, HP value, etc.) to each game device 10 via the communication unit 32.

[0064] The normal NPC state synchronization unit 313 synchronizes the states of normal NPCs controlled by each game device 10 so that they are the same. For example, the normal NPC state synchronization unit 313 controls the number and timing of appearance of normal NPCs. Specifically, when making a normal NPC appear, the normal NPC state synchronization unit 313 transmits instruction information indicating this to each game device 10. Each game device 10 makes a normal NPC appear in response to the instruction information. As a result, the timing and number of normal NPCs appearing on each game device 10 become roughly the same, maintaining commonality.

[0065] Furthermore, the normal NPC state synchronization unit 313 changes the HP value of the normal NPC based on the hit determination result of the attack from the player character to the normal NPC or information indicating the amount or type of damage, which is acquired from each game device 10. Furthermore, the normal NPC control unit 113 causes the normal NPC whose HP value has become "0" to disappear (die). The normal NPC state synchronization unit 313 then transmits information indicating the HP value of the normal NPC to each game device 10 as needed, and when the normal NPC disappears (dies), transmits information indicating that to each game device 10. Each game device 10 controls the HP value and state of the normal NPC based on this information.

[0066] The player character synchronization unit 314 synchronizes the positions and states of the player characters controlled by each game device 10 so that they are the same. For example, the player character synchronization unit 314 controls each player character to be displayed at the same position on each game device 10 based on information indicating the position of the player character acquired from each game device 10. Specifically, the player character synchronization unit 314 transmits information indicating the position of the player character acquired from each game device 10 to each game device 10. Each game device 10 controls the position of the player character based on the information indicating the position of each player character in each game device 10. As a result, each player character of each game device 10 is displayed at the same position on each game device 10. Furthermore, the player character synchronization unit 314 controls each player character to be displayed at the same HP remaining amount based on information indicating the state of the player character acquired from each game device 10, and controls so that a player character that has disappeared (died) also disappears (died) on the other game devices 10. Specifically, the player character synchronization unit 314 transmits information indicating the state of the player character acquired from each game device 10 to each game device 10. Each game device 10 controls the state of the player character based on the information indicating the state of each player character in each game device 10.

[0067] The occupation determination unit 315 determines which team should occupy the normal room (i.e., which team should be associated with it) based on whether or not a predetermined occupation condition is met based on the user's operation result. For example, when the defeat status of a normal NPC in a normal room meets a predetermined occupation condition, the occupation determination unit 315 determines which team should occupy the normal room (i.e., which team should be associated with it).

[0068] For example, when a predetermined occupation condition is satisfied by the operation result (defeat status of a normal NPC) of a user of the red team in a normal room associated with the blue team, the occupation determination unit 315 determines that the normal room is occupied by the red team. In this case, the occupation determination unit 315 associates the normal room (room ID) with the red team (team ID of the red team) in the team data stored in the team data storage unit 352. Note that the occupation determination unit 315 may associate the normal room (room ID) with user information (user ID) belonging to the red team in the team data stored in the team data storage unit 352.

[0069] 8 is a flowchart showing an example of an occupation determination process for determining the occupation of a room according to the present embodiment. When a battle is started in a normal room, the occupation determination unit 315 determines whether a predetermined occupation condition (for example, all normal NPCs in the room are annihilated) is met based on the user's operation result (step S100). If it is determined that the predetermined occupation condition is not met (NO), the occupation determination unit 315 executes the process of step S100 again. On the other hand, if it is determined that the predetermined occupation condition is met (YES), the occupation determination unit 315 updates the team data stored in the team data storage unit 352 as an occupation by a team that meets the predetermined occupation condition (step S102).

[0070] The win / loss determination unit 316 determines the outcome of a match between multiple teams based on the determination result by the occupation determination unit 315. For example, the win / loss determination unit 316 determines the outcome of a match between the blue team and the red team based on the number of rooms each of the blue team and the red team occupies (i.e., the number of rooms associated with each of the blue team and the red team) based on the determination result by the occupation determination unit 315. For example, the win / loss determination unit 316 determines the team that occupies a larger number of rooms as the winner (win), and determines the team that occupies a smaller number of rooms as the loser (lose).

[0071] Also, the win / loss determination may include a draw. For example, the win / loss determination unit 316 may determine a draw when the teams occupy the same number of rooms. Also, when the teams occupy the same number of rooms, the win / loss determination unit 316 may determine one team as the winner and the other team as the loser, taking into consideration the types of rooms occupied. For example, the win / loss determination unit 316 may determine the team that occupies the boss room as the winner, or may make the occupancy of a boss room a higher contribution to victory than the occupancy of a normal room.

[0072] FIG. 9 is a flowchart showing an example of the winning / losing determination process according to this embodiment. When a match play starts, the winning / losing determination unit 316 starts timing (step S110). The timing may be counting up or down. Next, the winning / losing determination unit 316 determines whether the time limit has expired based on the time measured (step S112). If it is determined that the time limit has not expired (NO), the winning / losing determination unit 316 executes the process of step S110 again. On the other hand, if it is determined that the time limit has expired (YES), the winning / losing determination unit 316 determines the winning / losing result based on the number of rooms occupied by each team (step S114).

[0073] Note that the win / loss determination unit 316 may determine the outcome in consideration of the points given to each team or to the users identified by the user information belonging to the team by the reward giving unit 317, in addition to the determination result by the occupancy determination unit 315. For example, when each team occupies the same number of rooms, the win / loss determination unit 316 may determine the outcome based on the points given to each team.

[0074] FIG. 10 is a flow chart showing an example of a winning / losing determination process that considers not only the number of rooms occupied but also points. When a match play starts, the winning / losing determination unit 316 starts timing (step S120). The timing may be counting up or down. Next, the winning / losing determination unit 316 determines whether the time limit has expired based on the time measured (step S122). If it is determined that the time limit has not expired (NO), the winning / losing determination unit 316 executes the process of step S120 again. On the other hand, if it is determined that the time limit has expired (YES), the winning / losing determination unit 316 determines the winning / losing result based on the number of rooms occupied by each team and the points given to them (step S124).

[0075] In addition, the winner / loser determination unit 316 may determine the winner taking points into consideration only when the teams occupy the same number of rooms, or may determine the winner taking points into consideration even when the teams occupy a different number of rooms.

[0076] (Points Awarding) Next, the awarding of points will be described. The reward awarding unit 317 awards points to a team or a user of that team for "occupying a room," "defeating an NPC," "assisting," etc. Each will be described below in order.

[0077] - Points awarded for "room occupation" The reward granting unit 317 grants points to the team (or the user of that team) that has occupied the room. In other words, when all normal NPCs present in a normal room occupied by an opponent team are defeated and there are no normal NPCs in the room, the room is occupied by the team that defeated them, and points (e.g., 3000 points) are granted to the team. Specifically, the reward granting unit 317 associates points to be granted in accordance with the occupation of a room with a team (team ID) associated with the room (room ID) by the occupation determination unit 315 or with user information (user ID) belonging to that team, in the team data stored in the team data storage unit 352. For example, the points are added each time they are granted.

[0078] The points given may differ depending on the room. For example, the reward giving unit 317 may give points to a team that occupies a room according to the room. For example, a level (room level) is set for each room, and the reward giving unit 317 may give points to a team that occupies a room according to the room level of the room they occupy.

[0079] For example, the room level increases by one level each time the room is occupied. As the level increases, the level of the normal NPC that appears also increases, making it more difficult to occupy the room. Furthermore, as the room level increases, the normal NPC that appears may become a different type of normal NPC with a higher level. For example, the reward granting unit 317 may grant more points when the room is occupied the higher the room level. In other words, the reward granting unit 317 may increase the points granted each time a predetermined occupancy condition is satisfied in the same room. An initial value of points (for example, points granted when the room is occupied when the room level is level 1) is set for each room.

[0080] FIG. 11 is a diagram showing an example of points given when a room is occupied. This diagram shows the relationship between each room level and points given when a room is occupied for a normal room A (room A) and a normal room B (room B). In the example shown, the points given when a normal room A is occupied are set to 2000pt (points), 3000pt, 4500pt, 6000pt, and 7500pt for room levels of level 1 (Lv1), level 2 (Lv2), level 3 (Lv3), level 4 (Lv4), and level 5 (Lv5), respectively. The points given when a normal room B is occupied are set to 3000pt, 4500pt, 6000pt, 7500pt, and 9000pt for room levels of level 1 (Lv1), level 2 (Lv2), level 3 (Lv3), level 4 (Lv4), and level 5 (Lv5), respectively.

[0081] Furthermore, the reward granting unit 317 may grant more points to a team as the number of rooms the team occupies increases. For example, the reward granting unit 317 may grant bonus points according to the number of other rooms occupied by the team that has occupied a room at the time the room is occupied. For example, a bonus coefficient is set according to the number of occupied rooms, and bonus points according to the bonus coefficient are granted.

[0082] Fig. 12 is a diagram showing an example of the setting of the number of occupied rooms and the bonus coefficient. In the example shown, the bonus coefficients are set to 1.00, 1.05, 1.10, 1.15, 1.20, and 1.25 for the number of occupied rooms (number of occupied rooms) of 0, 1, 2, 3, 4, and 5, respectively. For example, points are awarded that are the points shown in Fig. 11 multiplied by the bonus coefficient according to the number of occupied rooms. In other words, the reward awarding unit 317 awards higher points the more rooms the same team has occupied at the time of occupancy.

[0083] By doing this, users on the same team can gain more points by attacking all at once during the same time period, which makes users think about strategies depending on the time period.

[0084] The points according to the room are not limited to points according to the room level (difficulty of occupying), but may be points according to the size (area) of the room, for example. For example, the reward granting unit 317 may grant more points the larger (wider) the occupied room is.

[0085] - Points awarded for "defeating NPCs" The reward granting unit 317 grants points according to the type of normal NPC of the opponent team that has been defeated (HP reduced to 0). When a defeat is based on the operations of multiple users, points are allocated in proportion to the damage inflicted during the defeat. For example, a level is set for normal NPCs, and points are set according to the level. Boss NPCs also have levels, and when a boss NPC is defeated, the next time it appears it will be replaced by a boss NPC with a higher level than the one that was defeated. The higher the level of the boss NPC, the more points are awarded when defeated. Since the points awarded for defeating a boss NPC are higher than those awarded for defeating a regular NPC, both teams will gather in the boss room while the boss is appearing to defeat it. Unlike regular NPCs, boss NPCs can be attacked by both teams, so if both teams deal damage to the boss, points are allocated to each team according to the amount of damage when the boss is defeated.

[0086] - Points awarded for "assists" The reward granting unit 317 grants a preset number of points (e.g., 50 points) by increasing (buffing) the attack power of a player character operated by a user on the same team, or decreasing (debuffing) the defense power of a normal NPC on the opposing team.

[0087] (Room occupancy bonus) When a room is occupied, the reward granting unit 317 may generate (for example, randomly generate) an advantageous effect as a bonus for the occupying team. For example, when the last normal NPC present in a normal room is defeated, the reward granting unit 317 generates the advantageous effect described above. The advantageous effect may be, for example, a powerful normal NPC companion appears in the occupied room, the number of normal NPC companions that appear in the occupied room increases, the attack power of all player characters on the team is increased (buffed), and the like. In this way, the reward granting unit 317 may generate an advantageous effect for the user of the team in the room occupied by the team in the progress of play based on the operation of the user.

[0088] [Summary of the first embodiment] As described above, the game system 1 according to the present embodiment includes the character control unit 112 (an example of a character moving unit), the occupation determination unit 315 (an example of an area determination unit), and the win / loss determination unit 316. The character control unit 112 moves a player character (an example of a character) associated with each piece of user information in a field having a plurality of rooms (an example of an area) common to a plurality of teams, based on an operation of each user identified by user information (for example, a user ID) belonging to each of the plurality of teams. The occupation determination unit 315 determines whether or not a room (an example of an area) is associated with a team (for example, which team is occupied) based on whether or not a result of the user's operation satisfies a predetermined occupation condition (an example of a predetermined condition). The win / loss determination unit 316 determines whether or not a match between a plurality of teams will be won or lost, based on the determination result by the occupation determination unit 315.

[0089] As a result, the game system 1 can provide a new enjoyment in which the winner is decided by occupying rooms (an example of a region) in a team-based action game in which each user moves a player character in a field by operating the game system. For example, in conventional team-based action games, the winner is often decided by which team defeats more opponent (enemy) characters or which team reaches the final destination first, so that it is sometimes difficult to know in real time which team is dominant during the game. However, in this embodiment, the winner is always known by the number of rooms occupied, so that the user can play without losing tension. In addition, compared to a game in which players compete for a region in a one-on-one battle, this embodiment is a team battle, so that a more strategic game can be provided by team cooperation play and the appearance of multiple player characters on both sides of the enemy.

[0090] For example, the game system 1 includes a normal NPC control unit 113 or a boss NPC control unit 312 (an example of an NPC control unit) that controls an NPC (a normal NPC or a boss NPC) in a room (an example of an area). An occupation determination unit 315 (an example of an area determination unit) determines whether or not to associate the room with a team when the defeat status of an NPC (a normal NPC or a boss NPC) in the room satisfies a predetermined occupation condition.

[0091] This allows the game system 1 to occupy each of the multiple rooms in the field by defeating the normal NPCs or boss NPCs that appear in each of the rooms, thereby putting each team's opponents on the same terms and maintaining fairness.

[0092] For example, the defeat status of normal NPCs is the number of normal NPCs appearing in a normal room (one example of an area). The predetermined occupancy condition is, for example, that all normal NPCs present in the room are defeated (HP becomes "0") (i.e., the number of normal NPCs becomes 0). Note that the above-mentioned predetermined occupancy condition in a normal room is not limited to that all normal NPCs present in the room are defeated (HP becomes "0"), and may be other conditions. For example, the predetermined occupancy condition may be that the number of normal NPCs present in the room is a predetermined number or less (e.g., 2 or less), or that the number of defeated normal NPCs present in the room is a predetermined number or more (e.g., 10 or more). In addition, in the case of a boss room, the above-mentioned predetermined occupancy condition is that the boss NPC is defeated (HP becomes "0").

[0093] This makes it easy to understand the occupation conditions because the game system 1 can occupy a normal room when the number of normal NPCs appearing in the normal room meets a predetermined occupation condition (for example, when the number of normal NPCs becomes 0). Also, since a room can be occupied quickly by cooperating with team members, the user can feel a sense of unity as they fight as a team.

[0094] For example, a normal NPC (an example of an NPC) in a normal room (an example of an area) corresponds to one of a plurality of teams. This allows the game system 1 to create a situation similar to fighting against an opponent's team, even though the opponent is an NPC, and allows the user to play while feeling that it is a team match.

[0095] Instead of fighting against NPCs, each room may be arranged so that a battle between team player characters takes place. For example, a room may be occupied by defeating a player character of the opponent team.

[0096] Furthermore, the winning / losing determination unit 316 determines the outcome of a match between multiple teams based on the number of rooms (an example of an area) associated with each of the multiple teams as determined by the occupation determination unit 315 (an example of an area determination unit). As a result, the game system 1 determines the outcome of a team based on the number of rooms occupied, making it easy for users to understand the situation during the match and the result when the match ends. Furthermore, since there are multiple rooms to occupy within the field in which the match is played, the game system 1 can widen the range of strategies, such as which rooms to occupy.

[0097] The game system 1 also includes a reward granting unit 317 that grants points to a team with which a room (an example of an area) is associated by the occupancy determination unit 315 (an example of an area determination unit) or to a user identified by user information belonging to the team. As a result, the game system 1 grants points to a team or a user of a team that occupies a room, and therefore can add fun beyond just the occupancy situation. For example, when the game system 1 grants points to each user, it can provide users with the fun of competing with users within a team in addition to playing against other teams.

[0098] For example, the reward granting unit 317 grants points according to the room level to a team with which a room (an example of an area) is associated by the occupancy determination unit 315 (an example of an area determination unit) or to a user identified by user information belonging to the team. For example, the reward granting unit 317 grants points according to the room level.

[0099] As a result, the game system 1 awards different points depending on the room occupied (e.g., room level), allowing teams to choose their strategy, for example, to try to occupy many low-difficulty rooms or to try to occupy as few high-difficulty rooms as possible, thereby providing a highly strategic game.

[0100] In addition, when a predetermined occupation condition is satisfied by an operation result of a user identified by user information belonging to another team in a room (an example of an area) associated with one of the multiple teams, the occupation determination unit 315 (an example of an area determination unit) associates the room with the other team or the user information belonging to the other team. Then, the reward granting unit 317 increases the points to be granted each time the predetermined occupation condition is satisfied in the same room. That is, the reward granting unit 317 increases the value of the reward to be granted each time the predetermined occupation condition is satisfied in the same room. The value of the reward is, for example, the amount of the reward (for example, the amount of points). Note that the value of the reward may be the degree of influence on the win / loss determination (for example, the level of points, the degree to which points affect the win / loss, etc.). In addition, the value of the reward may be the degree of advantage in the match, such as the amount by which the offensive power of the own team is increased or the amount by which the defensive power of the opponent team is decreased.

[0101] As a result, the game system 1 allows teams to occupy the same room, and thus higher points are awarded when the rooms are occupied, which increases the motivation of users on each team to play against each other repeatedly, and an exciting game can be expected.

[0102] The more rooms (an example of an area) associated with a team by the occupation determination unit 315 (an example of an area determination unit), the more points the reward granting unit 317 grants when an area is associated with the team. This allows the game system 1 to give the team an advantage in the game as more rooms are occupied.

[0103] The winning / losing determination unit 316 determines the outcome of a match between multiple teams based on the determination results for each of the multiple rooms (an example of an area) by the occupancy determination unit 315 (an example of an area determination unit) and the points granted to each team or to users identified by user information belonging to the team by the reward granting unit 317. As a result, the game system 1 can provide a highly strategic game since winning or losing depends on which area is occupied, since not only the occupation of rooms but also the acquisition of points affects the outcome.

[0104] The reward giving unit 317 is not limited to giving points, and may give items, virtual currency, or the like as rewards.

[0105] Furthermore, the reward granting unit 317 may generate advantageous effects for the progress of play based on the operation of a user identified by user information belonging to a team in a room (an example of an area) associated with the team by the occupation determination unit 315 (an example of an area determination unit). The advantageous effects include, for example, a powerful regular NPC companion appears in the occupied room, the number of regular NPC companions that appear in the occupied room increases, the attack power of all player characters on the team is increased (buffed), etc. In this way, the game system 1 can allow the player to advance the game with an advantage the more rooms they occupy.

[0106] Each of the player characters (one example of a character) is set with a characteristic that affects the progress of the game based on the user's operation. As a result, the game system 1 can provide a highly strategic game because the type and power of an attack change depending on the player character's characteristic, and superiority or inferiority also occurs depending on the compatibility of the player character and the opponent's characteristic.

[0107] [Second embodiment] Next, a second embodiment of the present invention will be described. The basic configuration of the game system 1 according to this embodiment is the same as that of the first embodiment, so a characteristic process of this embodiment will be described. In this embodiment, an example of a method of making a normal NPC appear in a normal room will be described. The type and initial number of normal NPCs present in a normal room are set for each room. Even if the player character defeats a normal NPC, it will be revived (appear) one by one every time a predetermined time (for example, 10 seconds) has elapsed. The normal NPCs are revived until the initial number is reached. In other words, the initial number set for each normal room becomes the upper limit number of normal NPCs present in that room. That is, the normal NPC control unit 113 makes a normal NPC appear in a normal room at a predetermined time interval. Also, the normal NPC control unit 113 makes a normal NPC appear in a normal room at a predetermined time interval until the number of normal NPCs appearing simultaneously in the normal room reaches a preset upper limit number.

[0108] In this way, normal NPCs will revive even if they are defeated, so it is more efficient to work together as a team and defeat them in one room at a time than to defeat normal NPCs alone. The time it takes for normal NPCs to revive is determined by each room and each room level, and the higher the room level, the shorter the time it takes to revive, making it more difficult to occupy.

[0109] 13 is a diagram showing an example of how to set a normal NPC's appearance method. In the example shown, the normal NPCs that appear (appearing NPCs), their initial number, and the time (time interval) they will appear when revived are set for each room level for normal room A (room A) and normal room B (room B). In normal room A, the normal NPC that appears is character A, and the higher the room level, the greater the initial number and the shorter the time (time interval) they will appear when revived, making it more difficult to occupy.

[0110] On the other hand, in normal room B, the normal NPC that appears from level 1 (Lv1) to level 3 (Lv3) is character B, but at level 4 (Lv4) and level 5 (Lv5), character C is added to the normal NPCs that appear. In this way, multiple types of normal NPCs may exist in one room. In that case, the initial number and the appearance time (time interval) when reviving may be set for each type of normal NPC. In this normal room B, the initial number and the appearance time (time interval) when reviving are set for each of character B and character C, and the higher the room level, the greater the initial number of each and the shorter the appearance time (time interval) when each is reviving. In this way, the higher the room level of normal room B, the greater the difficulty of occupying it.

[0111] [Summary of the second embodiment] As described above, in the game system 1 according to the present embodiment, the character control unit 112 (an example of a character moving unit) moves a character associated with each user information within a field (FLD) having a common area within the team based on the operation of each user identified by the user information belonging to the team. The normal NPC control unit 113 (an example of an NPC control unit) makes a normal NPC (an example of an NPC) appear in a normal room (an example of an area) at a predetermined time interval. In addition, the occupation determination unit 315 (an example of an area determination unit) determines whether or not to associate the normal room with the team when the defeat status of the normal NPC in the normal room satisfies a predetermined condition. The win / loss determination unit 316 determines the win / loss of the team based on the normal room associated with the team by the occupation determination unit 315.

[0112] In this way, even if a normal NPC is defeated, it revives at a predetermined time interval, so that a normal room cannot be easily occupied by a single person, and more cooperative play as a team is required. Therefore, the game system 1 can provide a game with a strong sense of team battles.

[0113] For example, the defeat status of normal NPCs is the number of normal NPCs appearing in a normal room (one example of an area). The predetermined occupancy condition is, for example, that all normal NPCs present in the room are defeated (HP becomes "0") (i.e., the number of normal NPCs becomes 0). Note that the above-mentioned predetermined occupancy condition in a normal room is not limited to that all normal NPCs present in the room are defeated (HP becomes "0"), and may be other conditions. For example, the predetermined occupancy condition may be that the number of normal NPCs present in the room is a predetermined number or less (e.g., 2 or less), or that the number of defeated normal NPCs present in the room is a predetermined number or more (e.g., 10 or more). In addition, in the case of a boss room, the above-mentioned predetermined occupancy condition is that the boss NPC is defeated (HP becomes "0").

[0114] This makes it easy to understand the occupation conditions because the game system 1 can occupy a normal room when the number of normal NPCs appearing in the normal room at a predetermined time interval meets a predetermined occupation condition (for example, when the number of normal NPCs becomes 0). Also, since the room can be occupied quickly by cooperating with team members, the user can feel a sense of unity as they fight as a team.

[0115] The normal NPC control unit 113 causes normal NPCs (an example of an NPC) appearing simultaneously in a normal room (an example of an area) at a predetermined time interval until the number of such NPCs (an example of an NPC) reaches a preset upper limit. The preset upper limit is, for example, the initial number of normal NPCs that initially exist (appear) in a normal room. In this way, the game system 1 makes it difficult for one person to occupy a normal room, since up to the initial number of normal NPCs that initially exist (appear) in a normal room, they will revive even if defeated, making it necessary to play cooperatively as a team. Thus, the game system 1 can provide a game that is highly conscious of team battles.

[0116] When there are multiple normal rooms (an example of an area) in the field, the normal NPC control unit 113 controls the time interval for making normal NPCs (an example of an NPC) appear or the upper limit number of normal NPCs appearing simultaneously for each of the multiple normal rooms. This allows the game system 1 to set the difficulty level of occupying each room.

[0117] The normal NPC control unit 113 decreases the time interval for making normal NPCs (an example of an NPC) appear in the normal room, or increases the upper limit of the number of normal NPCs that can appear at the same time, each time a predetermined occupancy condition (an example of a predetermined condition) is satisfied in the same normal room (an example of an area). As a result, in the game system 1, teams occupying the same room together make it more difficult to occupy the room, which requires more team cooperation, and an exciting game can be expected.

[0118] In this embodiment, an example has been described in which an initial number of normal NPCs are initially present in a normal room, and even if the normal NPCs are defeated, they can be revived up to the initial number at a specified time interval; however, it is also possible for normal NPCs not to initially be present in a normal room, and for them to appear or be revived up to a preset upper limit number at specified time intervals.

[0119] [Third embodiment] Next, a third embodiment of the present invention will be described. The basic configuration of the game system 1 according to this embodiment is the same as that of the first embodiment, so a characteristic process of this embodiment will be described. In this embodiment, a process for suppressing the influence of a time lag that may occur in an online game in which multiple game devices 10 play against each other in a multiplayer battle will be described. Conventionally, in real-time games such as online action games, management of player characters and NPCs (HP values, positions on a map, attack activation status, etc.) has generally been centrally managed by a server (or a host terminal having a function equivalent to a server). Operation information from each terminal is collected by the server, and the processing results are returned to each terminal, and each terminal performs processing such as drawing based on the results.

[0120] Here, if the same NPC is attacked at almost the same time from different devices with attack power sufficient to defeat it, it will appear as if the attack was made from both devices, but in the end, only one of the devices will have defeated the NPC. The user of the device that was unable to defeat the NPC may end up with a situation where they were unable to defeat the NPC despite having attacked. This is because of the time lag that occurs during communication between sending the attack information from the device, processing it on the server, and sending the processing results back to the device. This problem can be particularly noticeable in the case of devices that do not necessarily have a stable communication environment, such as mobile devices, or when the server is located overseas or in a physically distant location.

[0121] Therefore, as described in the first embodiment, in the game system 1, the normal NPC has a camp (team) setting, and can only be attacked by one of the teams. For example, the match-up control unit 114 of the game device 10 operated by the user of the blue team controls attacks from the blue team to normal NPCs in the red team camp based on the operation of the user of the blue team, and restricts attacks from the blue team to normal NPCs in the blue team camp. On the other hand, the match-up control unit 114 of the game device 10 operated by the user of the red team controls attacks from the red team to normal NPCs in the blue team camp based on the operation of the user of the red team, and restricts attacks from the red team to normal NPCs in the red team camp. Here, the restriction on attacks means, for example, that attacks cannot be made, or that there is no hit determination even if an attack is made.

[0122] This can mitigate the problem of being unable to defeat an enemy even though you attacked them. For example, since an NPC is not usually attacked by both the blue team and the red team, the above-mentioned problem does not occur between teams. However, the above-mentioned problem can occur between player characters in a team, but since this is a team-based game, it has less impact than if it occurs between opponents.

[0123] In addition, since the boss NPC can be attacked by both camps (for example, both the blue team and the red team), it is possible that a proto-language occurs in which the boss NPC was attacked but was not defeated. However, the boss NPC has higher HP, attack power, defense power, etc. than a normal NPC, and is defeated by a large number of attacks from both teams. Therefore, although a proto-language may occur in the attack at the time of defeat (final finishing blow), it is possible that the order of attacks from both teams up to that point may be reversed, but it cannot become a major proto-language. In addition, in conventional games, there are specifications in which bonus points are awarded for defeating the boss NPC (final finishing blow), but such bonus points are not awarded in this embodiment, so that the influence of the proto-language on the outcome of the game can be minimized.

[0124] In addition, the game system 1 also restricts attacks between opponent player characters. For example, the match control unit 114 restricts the damage inflicted by an attack from a player character on a player character of another team to be smaller than the damage inflicted by an attack from the player character on a normal NPC. In other words, the advantages of direct attacks or other battles between player characters are reduced, and factors that motivate player characters to battle each other are reduced. Specifically, attacks against opponent player characters are possible, but the damage in such a case is limited to a value smaller than the damage inflicted on a normal NPC, for example, a minimum value (for example, 1 point). Damage inflicted by an attack on an opponent player character may be "0" (no damage).

[0125] The match control unit 114 may limit the activity of the opponent player character by an attack from the player character to the opponent player character. Restricting the activity may, for example, prohibit a specific action (movement, attack, etc.), limit the speed of a specific action (for example, slowing down the movement speed), limit a specific attack (for example, reducing the attacking power), or limit the range of the activity (narrowing the movable range). For example, the match control unit 114 may stop the movement of the opponent player character for a certain period of time (for example, 2 seconds) in addition to or instead of inflicting damage (for example, a minimum value) on the opponent player character by an attack from the player character to the opponent player character. In this way, when attacking the opponent player character, the purpose is to stop the movement rather than inflict damage.

[0126] The differences in processing between normal NPCs and boss NPCs are summarized below. A normal NPC can only be attacked by a player character from one team, whereas a boss NPC can be attacked by a player character from either team. Therefore, the processing of both types differs in whether it is synchronous processing in which the positions, movements, states, etc. are controlled to be the same on each game device 10, or asynchronous processing in which they are controlled separately for each game device 10.

[0127] FIG. 14 is a diagram showing the difference between the processing of a normal NPC and a boss NPC. In the processing of a normal NPC, the processing of the position of the normal NPC in the field, the movement (motion) of the normal NPC, the display of effects due to attacks, and hit determination due to attacks are asynchronous (i.e., controlled for each game device 10), while the processing of the remaining HP amount that changes due to damage and abnormal status such as disappearance (death) are synchronous so that they are the same in each game device 10. On the other hand, in the processing of a boss NPC, the processing of the position of the boss NPC in the field, the movement (motion) of the boss NPC, the display of effects due to attacks, the remaining HP amount that changes due to damage, and abnormal status such as disappearance (death) are synchronous, and hit determination due to attacks is asynchronous. Note that the position of the player character is synchronous. The part that is synchronous processing is managed by the game server 30, and the part that is asynchronous processing is managed by the game device 10.

[0128] In other words, actions that require high real-time performance, such as the position and movement (motion) of normal NPCs in the field and the effects of attacks (techniques), are managed by each game device 10 (terminal side), and only information on defeat and damage amount is managed by the game server 30 (server side). Therefore, the position of a normal NPC in a room may differ for each game device 10. In contrast, the position of a boss NPC in the field, etc. is managed by the game server 30 (server side). Therefore, although there is a time lag between each game device 10, there is basically no difference in the position of the boss NPC.

[0129] For example, if the position of the boss NPC in the field were to be asynchronous, the positional relationship between the player characters of each team who are fighting against the same boss NPC would become more pronounced. For example, a player may attack the opponent's player character to stop him from moving and stop him from getting close to the boss NPC, but the boss NPC may be in a nearby position on the game device 10 of the opponent's player character, making it possible for the player character to attack. This would result in inconsistency in the strategies of each team. To prevent this, a synchronization process is performed on the position of the boss NPC in the field that can be attacked by either team.

[0130] [Summary of the third embodiment] As described above, in the game system 1 according to this embodiment, the normal NPC control unit 113 (an example of a first NPC control unit) controls normal NPCs (an example of a first NPC) in the field. The match-up control unit 114 controls attacks from the blue team to normal NPCs (e.g., an example of a first NPC) in the red team camp based on the operation of a user identified by user information belonging to the blue team (an example of a first team) among the multiple teams. On the other hand, the match-up control unit 114 restricts attacks from the red team (an example of a second team) among the multiple teams to normal NPCs in the red team camp.

[0131] This allows the game system 1 to prevent the occurrence of a situation that may occur in online games where an NPC cannot be defeated despite an attack being made, since an NPC can normally only be attacked by one of the teams (for example, an NPC cannot be attacked by both the blue team and the red team). In other words, the game system 1 can prevent the influence of a time lag that may occur in online games.

[0132] When controlling an attack on a player character (an example of a second character) acting based on the operation of each user identified by user information belonging to the red team (an example of a second team) based on the operation of a user identified by user information belonging to the blue team (an example of a first team), the match-up control unit 114 restricts the damage inflicted on the player character of the red team (an example of a second character) by an attack on the player character of the red team to be smaller than the damage (an example of an impact) inflicted on a normal NPC (e.g., an example of a first NPC) of the red team camp by an attack on the blue team (an example of a first team). Note that the match-up control unit 114 similarly restricts an attack from the red team to a player character of the blue team to have a smaller impact on the player character of the blue team.

[0133] As a result, in the game system 1, when player characters battle each other, there may occur an incident where an attack was made but the enemy was not defeated. However, by making the damage from attacks extremely small, the benefits of having player characters battle each other are reduced and the factors that motivate player characters to battle each other can be reduced, thereby suppressing the impact of the above-mentioned discrepancy.

[0134] Furthermore, the match control unit 114 may limit the activity of a player character of the red team (an example of a second character) by an attack from the blue team (an example of a first team) to the player character of the red team. Similarly, the match control unit 114 may limit the activity of a player character of the blue team by an attack from the red team to the player character of the blue team.

[0135] As a result, in a battle between player characters, the game system 1 makes it possible to prevent a situation in which an opponent's player character fails to be defeated despite having been attacked, since the objective is to stop the opponent's movement rather than to inflict damage on the opponent's player character.

[0136] The game system 1 also includes a plurality of game devices 10 (an example of a terminal device) each having a normal NPC control unit 113 (an example of a first NPC control unit), and a game server 30 (an example of a server device) communicatively connected to the plurality of game devices 10. The normal NPC control unit 113 controls the position of a normal NPC (an example of a first NPC) within the field for each of the plurality of game devices 10. That is, the normal NPC control unit 113 of each of the plurality of game devices 10 controls the normal NPC within the field for each of the plurality of game devices 10.

[0137] As a result, in the game system 1, actions that generally require real-time processing, such as the position and movement (motion) of an NPC within the field and the effects (effects) when an attack (skill) is activated, are managed by each game device 10 (terminal side), thereby making it possible to prevent the effects of time lags caused by communication from occurring.

[0138] Furthermore, the game server 30 (an example of a server device) includes a boss NPC control unit 312 (an example of a second NPC control unit) that controls a boss NPC (an example of a second NPC) in the field. The match-up control unit 114 controls an attack from the blue team to the boss NPC based on an operation of a user identified by user information belonging to the blue team (an example of a first team). Similarly, the match-up control unit 114 controls an attack from the red team to the boss NPC based on an operation of a user identified by user information belonging to the red team (an example of a second team). Then, the boss NPC control unit 312 controls the position of the boss NPC in the field so that it is in the same position on multiple game devices 10 (an example of a terminal device).

[0139] As a result, the game system 1 can synchronize the position of the target of attack of a boss NPC that is attacked by both sides (e.g., both the blue team and the red team) so that it is the same on each game device 10, thereby ensuring consistency in battles between multiple users against the same target.

[0140] To defeat a boss NPC (an example of a second NPC), more attacks are required than to defeat a normal NPC (an example of a first NPC). For example, a boss NPC is set to have a higher HP than a normal NPC. The boss NPC may also be set to have a higher defensive power than a normal NPC. Furthermore, the attack power of the player character when attacking a boss NPC may be lower than the attack power when attacking a normal NPC.

[0141] As a result, in the game system 1, although it is possible that an ancestor word may occur for the attack at the time of defeat (the final finishing blow) where an attack was made but the enemy was not defeated, even if the order of attacks from both teams up to that point was switched, this does not become a major ancestor word, so the impact of the above-mentioned discrepancy on the overall attacks leading up to the defeat can be reduced.

[0142] [Fourth embodiment] Next, a fourth embodiment of the present invention will be described. The basic configuration of the game system 1 according to this embodiment is the same as that of the first embodiment, so a characteristic process of this embodiment will be described. In the first embodiment, the basic rule of the game is that the team that occupies the most rooms within a time limit (for example, 3 minutes) wins. However, depending on the difference in ability between the opponent, the outcome of the battle may become clear before the time limit, and the outcome may be essentially decided. In such a case, if the user must continue playing until the time limit, the user may feel that the play time is a waste of time. Therefore, in this embodiment, an exceptional example will be described in which the outcome of a battle play is decided before the time limit.

[0143] In this embodiment, the win / loss determination unit 316 may determine the win / loss of the team even before the time limit is reached based on the room occupancy status of each team (i.e., the association status of multiple rooms (normal rooms, boss rooms, etc.) to the team). For example, when the room occupancy status of each team becomes a preset status, the win / loss determination unit 316 determines the win / loss of the team even before the time limit is reached on condition that the status is maintained for a predetermined time (e.g., 30 seconds). The preset room occupancy status is, for example, a situation in which one team occupies all of the rooms that can be occupied. In this case, when the status in which one team occupies all of the rooms is maintained for a predetermined time (e.g., 30 seconds), the win / loss determination unit 316 determines the win / loss of the team even before the time limit is reached. Specifically, the win / loss determination unit 316 determines the victory of the team that occupies all of the rooms. In other words, if there is a difference in ability between the teams based on the occupancy status of the rooms by each team and the outcome of the battle becomes clear before the time limit, the winner / loser determination unit 316 will determine the winner before the time limit and end the competitive play, like a so-called cold game.

[0144] Also, information indicating the above-mentioned predetermined time, which is a condition for determining the victory or defeat of a team, may be displayed on a play screen on which a play image of a match play is displayed. For example, when one team occupies all the rooms, the display control unit 115 starts a countdown display to the above-mentioned predetermined time (e.g., 30 seconds) as information indicating the time until the above-mentioned predetermined time is reached. Then, the display control unit 115 continues the countdown display while the situation in which one team occupies all the rooms is maintained, and ends the countdown display when the above-mentioned predetermined time has elapsed (when the countdown reaches 0 seconds) or when one or more rooms are reoccupied by the other team before the above-mentioned predetermined time has elapsed. Note that the information indicating the time until the above-mentioned predetermined time (e.g., 30 seconds) displayed on the play screen may be a countdown display (remaining time) or a count-up display (elapsed time).

[0145] Furthermore, when one team occupies all the rooms and then fails to maintain this state for a predetermined time (e.g., 30 seconds) and one or more rooms are returned to the other team, the victory / loss determination unit 316 may shorten (e.g., from 30 seconds to 15 seconds) the predetermined time, which is a condition for determining the victory or loss of the team, when the situation in which the one team occupies all the occupable rooms again occurs. In other words, when a situation in which all the rooms are occupied by any team occurs repeatedly, the victory / loss determination unit 316 may shorten the predetermined time, which is a condition for determining the victory or loss of the team, depending on the number of times all the rooms are occupied.

[0146] In this way, the more times all the rooms are occupied, the shorter the predetermined time becomes. The number of times all the rooms are occupied is counted for each team. In other words, if the same team repeatedly occupies all the rooms, the predetermined time is shortened each time. For example, if the blue team first occupies all the rooms and fails to maintain this occupation before the 30-second count ends, and the blue team occupies all the rooms again, the count will be 15 seconds, but if the red team, not the blue team, occupies all the rooms for the first time, the count will be 30 seconds instead of 15 seconds. The reason why this countdown gives the team that has had all the rooms occupied a chance to make a comeback is to eliminate the irrationality of the match ending without being able to show its true strength due to a sudden attack due to some factor.

[0147] If the time remaining until the time limit is reached (time remaining in the match) is less than the above-mentioned specified time, the countdown will not be displayed even if all rooms are occupied. This is because, for example, if one team occupies all rooms when there are 20 seconds left in the match, even if a 30-second countdown is started, the match will end before the countdown reaches "0" due to the time limit, so there is no point in displaying the countdown.

[0148] Next, the operation of the countdown process, which performs a countdown when all rooms are occupied by one of the teams in the above-mentioned battle play, will be described. FIG. 15 is a flowchart showing an example of the countdown process in battle play according to this embodiment.

[0149] When a match play starts, the occupancy determination unit 315 determines whether or not a room is occupied (step S200). If it is determined that the room is not occupied (NO), the occupancy determination unit 315 returns to the process of step S200 and determines whether or not a room is occupied. On the other hand, if it is determined that the room is occupied (YES), the occupancy determination unit 315 determines whether or not all rooms are occupied by any team (step S202).

[0150] If it is determined that none of the rooms are occupied by any team (NO), the occupancy determination unit 315 returns to the process of step S200 and determines whether or not the rooms are occupied. On the other hand, if it is determined that all of the rooms are occupied by any team (YES), the occupancy determination unit 315 determines the number of times that all of the rooms have been occupied by that team (step S204).

[0151] If it is determined that the team has occupied all the rooms for the first time (first time), the win / loss determination unit 316 determines whether or not the remaining time of the time limit (remaining time of the match) is 30 seconds or more (step S206). If it is determined that the remaining time is less than 30 seconds (NO), the win / loss determination unit 316 does not count down and returns to the process of step S200. This allows the match play to continue until the time limit is reached. On the other hand, if it is determined that the remaining time is 30 seconds or more (YES), the win / loss determination unit 316 starts a 30-second countdown (step S208).

[0152] Next, the occupancy determination unit 315 determines whether the room has been occupied (whether it has been reoccupied) (step S210). That is, the occupancy determination unit 315 determines whether the state in which all rooms are occupied is maintained. If it is determined that at least one room has been reoccupied (occupation of all rooms has not been maintained) before the countdown reaches "0" (YES), the victory / loss determination unit 316 ends the countdown midway and returns to the processing of step S200. This returns to normal battle play. On the other hand, if it is determined that the room is not occupied (occupation of all rooms is maintained) (NO), the victory / loss determination unit 316 determines whether the countdown has reached "0" (step S212). If it is determined that the countdown has not reached "0" (NO), the victory / loss determination unit 316 returns to the processing of step S210 and continues the countdown. On the other hand, if it is determined that the countdown has reached "0" (YES), the victory / loss determination unit 316 determines that the team that has occupied all the rooms has won (called game), and ends the match play at that point.

[0153] On the other hand, in step S210, if it is determined that the occupation of all the rooms was not maintained before 30 seconds have elapsed, the 30-second countdown ends midway and the game returns to normal battle play. In this state, if the team that occupied all the rooms last time again occupies all the rooms, in step S204, the number of times that the team occupied all the rooms is determined to be the second time. The second countdown will be 15 seconds, which is shorter than the first time. The win / loss determination unit 316 determines whether the remaining time of the time limit (remaining time of the battle) is 15 seconds or more (step S214). If it is determined that the remaining time is less than 15 seconds (NO), the win / loss determination unit 316 does not count down and returns to the process of step S200. As a result, the battle play continues until the time limit is reached. On the other hand, if it is determined that the remaining time is 15 seconds or more (YES), the win / loss determination unit 316 starts a 15-second countdown (step S216).

[0154] Next, the occupancy determination unit 315 determines whether the room has been occupied (whether it has been reoccupied) (step S218). That is, the occupancy determination unit 315 determines whether the state in which all rooms are occupied is maintained. If it is determined that at least one room has been reoccupied (occupation of all rooms has not been maintained) before the countdown reaches "0" (YES), the victory / loss determination unit 316 ends the countdown midway and returns to the process of step S200. This returns to normal battle play. On the other hand, if it is determined that the room is not occupied (occupation of all rooms is maintained) (NO), the victory / loss determination unit 316 determines whether the countdown has reached "0" (step S220). If it is determined that the countdown has not reached "0" (NO), the victory / loss determination unit 316 returns to the process of step S218 and continues the countdown. On the other hand, if it is determined that the countdown has reached "0" (YES), the victory / loss determination unit 316 determines that the team that has occupied all the rooms has won (called game), and ends the match play at that point.

[0155] On the other hand, if in step S218 it is determined that occupation of all the rooms has not been maintained before 15 seconds have elapsed, the 15-second countdown ends prematurely and normal competitive play is resumed, and then in this state the team that previously occupied all the rooms again occupies all the rooms, then in step S204 it is determined that this is the third time that all the rooms have been occupied by that team. If this is the third time that the same team has occupied all the rooms, the win / loss determination unit 316 does not count down, but determines that the team that occupied all the rooms at that point has won (called game), and ends the competitive play.

[0156] [Summary of the Fourth Embodiment] As described above, in the game system 1 according to this embodiment, the occupancy determination unit 315 (an example of an area determination unit) determines whether or not to associate each of the multiple rooms (an example of an area) in the field with a team (for example, which team should occupy it) based on whether or not the operation result of a user identified by user information belonging to a team satisfies a predetermined condition. The win / loss determination unit 316 determines whether or not the team will win based on the determination result by the occupancy determination unit 315 within a preset time limit, and determines whether or not the team will win based on the occupancy status of the rooms by each team (an example of the status of associating multiple areas with teams) even before the time limit is reached.

[0157] As a result, in an action game in which multiple users forming a team control their own characters to fight enemy characters, if the outcome of the battle becomes clear and the outcome is essentially decided before the time limit has expired, the game system 1 will determine the outcome at that point and end the game, thereby preventing users from wasting time playing.

[0158] Furthermore, when the room occupancy status (one example of the association status of a plurality of regions with a team) by each team reaches a preset status, the winning / losing determination unit 316 determines the winning / losing status of the team even before the time limit is reached, on condition that the status is maintained for a predetermined time. For example, the preset room occupancy status is a status in which one team occupies all of the occupyable rooms (all rooms occupied).

[0159] In this way, even if one team occupies all the rooms, the game system 1 can give the occupied team time to make a comeback. Therefore, the game system 1 can prevent irrationality from occurring, such as a sudden attack due to some factor, resulting in the match ending without the team being able to demonstrate their true abilities.

[0160] The preset room occupancy status may be a situation where the difference between the number of rooms occupied by one team and the number occupied by the other team is equal to or greater than a predetermined number, or a situation where one team occupies a predetermined percentage or number of rooms available for occupancy in the field. The preset room occupancy status may also be a situation based on the percentage or number of rooms occupied by one team that are reoccupied by the other team.

[0161] In addition, in this embodiment, an example has been described in which when the room occupancy situation by each team reaches a preset situation (e.g., all rooms are occupied), the team's victory or defeat is determined even before the time limit is reached, provided that this situation is maintained for a predetermined period of time.However, if the occupied team is not given a chance to make a comeback, the team's victory or defeat may also be determined even before the time limit is reached, provided only that the room occupancy situation by each team reaches a preset situation (e.g., all rooms are occupied).

[0162] Furthermore, the win / loss determination unit 316 shortens the above-mentioned predetermined time period depending on the number of times that the room occupancy status (one example of the status of association of a plurality of areas with teams) by each team reaches a preset status. In this way, when all rooms are repeatedly occupied, the game system 1 can more reliably consider that the team in question is in an advantageous position than when all rooms were occupied the first time, thereby shortening the time that the occupied team has a chance to make a comeback, and preventing the occurrence of wasted play time for the users of the team that occupied all the rooms.

[0163] For example, in the case of a match between multiple teams, the number of times is counted for each team. In this way, when one team occupies all the rooms and then the other team regains all the rooms, the game system 1 can provide each team with an equal chance of time to make a comeback, since it is considered that the outcome of the battle is not clear.

[0164] Furthermore, when the occupancy status of the rooms by each team (an example of an association status of a plurality of regions with teams) reaches a preset status, the display control unit 115 displays information indicating the time remaining until the above-mentioned predetermined time is reached. This allows the game system 1 to present the time remaining until victory or defeat is determined to the user playing a match, for example, by a countdown, thereby increasing the sense of tension. Furthermore, the game system 1 allows the user to easily grasp the remaining time until victory or defeat is determined, making it easier for the user to consider a strategy for what to do with the remaining time.

[0165] When the occupancy status of rooms by each team (an example of an association status of a plurality of regions with teams) reaches a preset status, the display control unit 115 determines whether or not to display information indicating the time until the predetermined time based on the remaining time until the time limit is reached and the predetermined time. For example, when the remaining time until the time limit is reached (remaining time of the match) is less than the predetermined time, the display control unit 115 does not display information indicating the time until the predetermined time is reached (countdown display) even if all rooms are occupied. This allows the game system 1 to avoid displaying a meaningless countdown when the remaining time of the match is shorter than the countdown time, because even if the countdown is started, the match will end due to the time limit before the countdown reaches "0".

[0166] Furthermore, the character control unit 112 (an example of a character moving unit) moves characters associated with each user information within a field having multiple areas common to the users, based on the operation of each user identified by the user information belonging to the team. In this way, when the outcome of the battle becomes clear and the outcome is essentially decided before the time limit, the game system 1 determines the outcome at that point and ends the game, thereby preventing users from wasting time moving characters within the field.

[0167] [Fifth embodiment] Next, a fifth embodiment of the present invention will be described. Since the basic configuration of the game system 1 according to this embodiment is the same as that of the first embodiment, only the characteristic processing of this embodiment will be described.

[0168] If a player character is attacked and dies, they will restart from the starting room. If they die, they will be unable to operate for a certain period of time until they can restart, and their activities will be restricted (a penalty related to winning and losing decisions). Therefore, one of the conditions for a team to win is to avoid death as much as possible. In this embodiment, it will be described that there is a state of suspended animation prior to the death of a player character, in which the player character can be revived by a team member.

[0169] When a player character receives damage from an attack by a normal NPC or a boss NPC and the HP becomes "0", the player character first enters a state of suspended animation. At this point, the player character is not dead. If the player character receives a predetermined amount of damage while in suspended animation, the player character enters a state of death. For example, when the player character enters a state of suspended animation, the HP value returns slightly (for example, "10"), and if the player character receives an attack and the HP becomes "0" again, the player character enters a state of death. A player character in suspended animation can be revived from the suspended animation state to a normal state based on a player character of the same team. In other words, even if the HP becomes "0", the player character does not enter a state of immediate death, but is given a chance to be revived. The normal state is a state in which the player character can move at least based on a user's operation from the time of appearance until the time of entering the suspended animation. For example, when a player character of the same team approaches a player character in suspended animation, a revival icon is displayed near the player character in suspended animation on the play screen as an operator that accepts an operation to revive the player character in suspended animation. When an operation is performed on this revival icon, the player character in suspended animation returns to a normal state and the HP value is also revived. In this way, by cooperating with other team members (comrades), a player character who is about to die within the team can be rescued before he or she is completely dead.

[0170] When the player character is in a state of suspended animation, the player character's abilities are significantly reduced compared to the normal state. For example, when the player character is in a state of suspended animation, parameters such as attack power, defense power, and HP are significantly reduced (the parameters are exclusive to the state of suspended animation). Furthermore, when the player character is in a state of suspended animation, the player character is unable to use skills set for the player character (such as attacks that cause great damage to the opponent and HP recovery). Furthermore, when the player character is in a state of suspended animation, the player character's movement speed and jumping power are reduced compared to the normal state. In other words, the state of suspended animation is not a state of death, but is a state in which the player character's abilities (parameters such as attack power, defense power, and HP) are reduced compared to the normal state, and as a result, the player character's activities are more restricted than in the normal state. For example, a player character in a state of suspended animation can move and fight a little, but is unable to cause much damage even when attacking.

[0171] On the other hand, the death state is a state in which the player character's activities are restricted (for example, a state in which the character cannot be operated at all) and cannot be revived to a normal state by other player characters on the same team. Note that the death state does not mean that the game is over upon death, but rather that the game continues to progress and the character cannot be operated for a certain period of time.

[0172] In addition, when the player character is in a suspended animation state, the appearance displayed on the play screen also changes. FIG. 16 is a diagram showing an example of the appearance of the player character in each state. As shown in the figure, in the normal state, the character is a warrior with a human appearance, but when the character is in a suspended animation state, the character becomes a skeleton. In addition, when the character is in a dead state, the character disappears. For example, when a player character acting based on a user's operation in the game device 10-1 is in a suspended animation state, the display control unit 115 of the game device 10-1 displays the player character in the suspended animation state in a display manner that is distinguishable from a player character in a normal state. In addition, when a player character acting based on a user's operation in the game device 10-1 is in a suspended animation state, the display control unit 115 of the game device 10-2 displays the player character in the suspended animation state in a display manner that is distinguishable from a player character in a normal state in the game device 10-2.

[0173] 16 shows an example in which the appearance of the player character is changed to that of a skeleton when the player character goes from a normal state to a suspended animation state, but the display content itself may be changed in this way, or the display content itself may not be changed. For example, when the player character goes from a normal state to a suspended animation state, the size of the player character displayed on the play screen may be changed, the display may be changed to a blinking display, or the color or transparency may be changed.

[0174] A player character in a state of suspended animation has reduced offensive power and other capabilities, making it almost impossible to achieve any military results, and also has low defensive power, making it easy for the character to die with even a small amount of damage. In other words, it is strategically necessary to escape from the state of suspended animation as quickly as possible. Therefore, by moving a player character from the same team close to the player character in a state of suspended animation, the player character in a state of suspended animation can be revived to a normal state. Thus, the game system 1 can provide a game that provides more opportunities for cooperation within a team.

[0175] 17 is a block diagram showing an example of a detailed configuration of the character control unit 112 according to this embodiment. The illustrated character control unit 112 includes a character state control unit 1121 and a revival control unit 1122. When the HP of a player character in a normal state becomes "0", the character state control unit 1121 transitions the player character to a suspended animation state. In addition, when the player character in a suspended animation state is further attacked and the HP value temporarily returns to "0" again, the character state control unit 1121 transitions the player character to a dead state.

[0176] The resurrection control unit 1122 resurrects a player character in a suspended animation state to a normal state based on other player characters belonging to the same team as the player character. For example, the resurrection control unit 1122 resurrects a player character in a suspended animation state to a normal state based on a positional relationship with a player character in a normal state belonging to the same team as the player character. Specifically, when a player character in a normal state belonging to the same team approaches a player character in a suspended animation state, the resurrection control unit 1122 instructs to display a resurrection icon that accepts an operation to resurrect the player character in the suspended animation state to a normal state on the play screen. Then, when an operation is performed on the resurrection icon, the resurrection control unit 1122 returns the player character in the suspended animation state to a normal state at that location, and also resurrects the value of HP (for example, to an initial value).

[0177] On the other hand, the resurrection control unit 1122 transitions a dead player character to a normal state when a predetermined time (e.g., 10 seconds) has passed since the dead state. For example, when the resurrection control unit 1122 transitions a dead player character to a normal state, the resurrection control unit 1122 places the player character in the start room. In other words, when the player character dies, it becomes impossible to operate the character for a certain period of time, and then the character is restarted from the start room.

[0178] Next, a description will be given of the operation of state transition processing in which the character control unit 112 controls the state transition of the player character. Fig. 18 is a flowchart showing an example of the state transition processing according to this embodiment.

[0179] When a battle play starts, the character control unit 112 places the player character in a normal state in the start room of the player character's team. At this time, the HP of the player character is an initial value (e.g., "1000") (step S300). Based on the user's operation, this player character moves within the field and fights with opponents (e.g., normal NPCs, boss NPCs, etc.) in each room.

[0180] The character control unit 112 determines whether the HP of the player character in the normal state has become "0" (step S302). If it is determined that the HP has not become "0" (NO), the character control unit 112 leaves the player character in the normal state and performs the process of step S302 again. On the other hand, if it is determined that the HP has become "0" (YES), the character control unit 112 transitions the player character in the normal state to a suspended animation state. In addition, the character control unit 112 returns the HP value of the player character slightly (for example, to "10") (step S304).

[0181] The character control unit 112 also determines whether the HP of the player character in the suspended animation state has become "0" (step S306). If it is determined that the HP has become "0" (YES), the character control unit 112 transitions the player character in the suspended animation state to the dead state (step S308). Then, the character control unit 112 returns to the process of step S300 after a predetermined time has elapsed since the transition to the dead state (step S310). Then, the player character that has been returned from the dead state to a normal state (for example, HP is an initial value (for example, "1000")) is placed in the start room (step S300). As a result, the dead player character is unable to be operated for a certain period of time, and then restarts from the start room.

[0182] On the other hand, if it is determined in step S306 that the HP is not "0" (NO), the character control unit 112 determines whether or not the display condition for the revival icon is satisfied (step S312). The display condition for the revival icon is that a character in a normal state of the same team approaches a player character in a suspended animation state. For example, when the character control unit 112 determines that a character in a normal state of the same team approaches within a predetermined distance of a player character in a suspended animation state (for example, when a character in a normal state of the same team is in a position where the player character in a suspended animation state is touching the player character in a suspended animation state, or when the characters are in a position where they overlap on the play screen), it determines that the display condition for the revival icon is satisfied.

[0183] If it is determined that the display condition for the revival icon is not satisfied (NO), the character control unit 112 returns to the process of step S306 and determines whether the HP of the player character in the suspended animation state has become "0." On the other hand, if it is determined that the display condition for the revival icon is satisfied (YES), the character control unit 112 instructs the display control unit 115 to display the revival icon. As a result, the display control unit 115 displays the revival icon near the player character in the suspended animation state on the play screen (step S314).

[0184] Next, the character control unit 112 judges whether or not an operation has been performed on the revival icon based on the user's operation on the input unit 13 (step S316). If it is judged that no operation has been performed on the revival icon (NO), the character control unit 112 returns the process to step S306. If the HP of the player character in a state of suspended animation becomes "0" before an operation is performed on the revival icon, the player character transitions to a dead state. In addition, before the HP of the player character in a state of suspended animation becomes "0", the revival icon that was once displayed after it was judged that the display condition of the revival icon was satisfied continues to be displayed.

[0185] On the other hand, if it is determined that an operation has been performed on the revival icon (YES), the character control unit 112 revives the player character in the suspended animation state to a normal state (for example, HP is an initial value (for example, "1000")) (step S318).

[0186] [Summary of the fifth embodiment] As described above, in the game system 1 according to the present embodiment, the character control unit 112 activates the characters associated with each user information in a field common to the team based on the operation of each user identified by the user information belonging to the team. For example, the character control unit 112 includes a character state control unit 1121 and a resurrection control unit 1122. The character state control unit 1121 transitions the player character in a normal state (an example of a first state) to a suspended animation state (an example of a second state) in which the ability is lower than that of the normal state, on the condition that the HP of the player character in the suspended animation state becomes "0" (an example of a predetermined first condition being satisfied). In addition, the character state control unit 1121 transitions the player character in the suspended animation state to a death state (an example of a third state) in which the activity of the player character is restricted, on the condition that the HP of the player character in the suspended animation state becomes "0" again (an example of a predetermined second condition being satisfied). The resurrection control unit 1122 resurrects the player character in the suspended animation state to a normal state based on other player characters belonging to the same team as the player character. The winning / losing determination unit 316 determines whether the team has won or lost based on the results of the activities of the player characters performed by the character control unit 112. For example, the winning / losing determination unit 316 determines whether the team has won or lost based on the occupancy status of the rooms of each team based on the results of the activities of the player characters (results of the battle).

[0187] As a result, even if a player character is attacked and his HP drops to "0," the game system 1 does not cause instant death, but gives the player a chance to revive with the cooperation of the same team. Thus, the game system 1 can increase the opportunities for cooperation within a team in a team-based action game.

[0188] The application of this embodiment is not limited to a battle play in which players occupy rooms. For example, in a battle play in which players defeat opponents, the winning / losing determination unit 316 may determine the winning / losing of a team based on the defeat status of each team based on the results of the player character's activities (results of the battle).

[0189] Furthermore, the resurrection control unit 1122 resurrects a player character in a suspended animation state (an example of a second state) to a normal state based on the positional relationship with a player character in a normal state (an example of a first state) belonging to the same team as the player character. For example, when the resurrection control unit 1122 determines that a character in a normal state of the same team approaches within a predetermined distance of a player character in a suspended animation state (for example, when a character in a normal state of the same team is in a positional relationship where the player character in a suspended animation state is touching the player character in a suspended animation state, or when the characters are in a positional relationship where they overlap on the play screen), the resurrection control unit 1122 resurrects the player character in a suspended animation state to a normal state.

[0190] In this way, in order to revive a player character in a state of suspended animation, the game system 1 requires other player characters on the same team to move to the location of the player character in the state of suspended animation, giving the player a sense of team members working together to rescue the player character.

[0191] The method of reviving a player character in a suspended animation state is not limited to a method based on a positional relationship between the player character in a suspended animation state and a player character in a normal state of the same team. For example, the method of reviving a player character in a suspended animation state may be a specific item used by a player character in a normal state of the same team. The specific item is, for example, a revival item that has an effect of reviving a player character in a suspended animation state. Also, the method of reviving a player character in a suspended animation state may be a player character in a normal state of the same team going to a specific location. The specific location is, for example, a prayer room for revival. For example, the player character in a suspended animation state may be revived by an operation of a user of the same team, in which the player character in a normal state of the user goes to a prayer room, or goes to the prayer room and performs an action of praying in the room.

[0192] The suspended animation state (an example of the second state) in which the ability is lower than the normal state (an example of the first state) includes a state in which the activity of the player character is restricted. In this way, when the game system 1 transitions the player character to the suspended animation state, the activity of the player character is restricted more than in the normal state, and therefore the fighting power of the team in a match-up is reduced, and therefore the team members can be motivated to revive the player character in the suspended animation state.

[0193] The suspended animation state (an example of the second state) in which the abilities are lower than in the normal state (an example of the first state) includes a state in which the values ​​of parameters associated with the player character are changed to values ​​that lower the abilities of the player character compared to the normal state. In this way, when the game system 1 transitions the player character to the suspended animation state, the values ​​of parameters such as the attack power, defense power, and HP of the player character are lower than in the normal state, and therefore the fighting power of the team in a match play is reduced, and therefore the team members can be motivated to revive the player character in the suspended animation state.

[0194] On the other hand, the death state (an example of the third state) includes a state in which the activity of the player character is restricted and the player character cannot be revived to the normal state (an example of the first state) based on other player characters belonging to the same team as the player character. In this way, the game system 1 can provide a motivation for team cooperation to somehow revive the player character while in a state of suspended animation, since the player character cannot be revived by cooperation within the team when the player character dies.

[0195] The dead state (an example of the third state) may be a state in which revival to the normal state (an example of the first state) is impossible. In this case, when the player character operated by the user dies, the user is unable to participate in the ongoing battle play thereafter (i.e., the game is over for the user), and can only watch the play screen, for example. In this way, when the player character dies, the game system 1 not only makes it impossible to revive the player character through cooperation within the team, but also makes it impossible to participate in the battle play thereafter, so that it is possible to provide an incentive for the players to cooperate within the team in order to somehow revive the player character while in a state of suspended animation.

[0196] The resurrection control unit 1122 transitions a player character in a dead state (an example of a third state) to a normal state (an example of a first state) when a predetermined time has passed since the player character entered the dead state. In this way, even if the player character dies, the game system 1 does not end the game, but continues playing, and restarts after a certain period of inoperability, allowing the player character to participate in competitive play again and contribute to the team. In addition, since the game system 1 makes it impossible to operate the player character for a certain period of time when the player character dies, it is possible to provide an incentive for the team members to cooperate in order to somehow revive the player character while in a state of suspended animation.

[0197] The resurrection control unit 1122 may transition a dead player character to a suspended animation state (an example of the second state) after a predetermined time has passed since the player character became dead. In this case, the game system 1 makes it impossible to operate the player character for a certain period of time when the player character dies, and furthermore, the player character needs to be rescued from the suspended animation state, so that the game specifications can be made more necessary for cooperation within a team.

[0198] Furthermore, when the resurrection control unit 1122 transitions a player character in a dead state (an example of a third state) to a normal state (an example of a first state) or a suspended animation state (an example of a second state), the resurrection control unit 1122 places the transitioned player character in a predetermined location in the field. For example, when the resurrection control unit 1122 transitions a player character in a dead state to a normal state, the resurrection control unit 1122 places the player character in the start room. In this way, the game system 1 can give a locational penalty in addition to a time penalty of being unable to operate the player character for a certain period of time by restarting the player character from the start room once the player character has died.

[0199] When the resurrection control unit 1122 transitions a dead player character to a suspended animation state (an example of the second state), the transitioned player character may be placed in the place in the field where the player character died, or in the start room of the player character. For example, when a player character revived from a dead state to a suspended animation state is placed in the place where the player character died, the player character will need further cooperation from team members to be revived to the normal state, but the penalty in terms of location will be waived. On the other hand, when a player character revived from a dead state to a suspended animation state is placed in the start room, the player character will need further cooperation from team members to be revived to the normal state, and a penalty in terms of location will also be imposed. In this way, the game system 1 can change the degree of the penalty when a player character dies.

[0200] The revival control unit 1122 may limit the number of times a player is revived from a suspended animation state (an example of the second state) to a normal state (an example of the first state). For example, the revival control unit 1122 may set a limit (e.g., three times) on the number of times a player can be revived from a suspended animation state in one match play. Revival may be prevented if this number of times is exceeded, or if this number of times is exceeded, revival may be prevented only by consuming a specific item. This allows the game system 1 to prevent the difficulty of play from becoming too low or the difference in ability between teams from being not reflected by allowing unlimited revivals.

[0201] Furthermore, when a player character acting based on a user's operation in game device 10-1 (an example of a first terminal device) is in a suspended animation state (an example of a second state), display control unit 115 displays the player character in game device 10-2 (an example of a second terminal device) in a display mode that is distinguishable from a player character in a normal state (an example of a first state). Note that display control unit 115 at this time is the processing of display control unit 115 of game device 10-2. This allows game system 1 to display the player character in a suspended animation state on the play screen so that the player character can be easily distinguished from a player character in a normal state.

[0202] In addition, if the player character dies, in addition to or instead of the time penalty of being unable to operate for a certain period of time and the location penalty of having to restart from the starting point, a certain number of points awarded to the reward awarding unit 317 may be deducted.

[0203] [Sixth embodiment] Next, a sixth embodiment of the present invention will be described. The basic configuration of the game system 1 according to this embodiment is the same as that of the first embodiment, so a characteristic process of this embodiment will be described. In this embodiment, items that can be obtained in the field will be described.

[0204] Items that can be acquired by the user operating the player character are placed in the field. There are two types of items placed: normal items and treasure chest items. The normal items are displayed in a display manner that allows the type of item to be identified. On the other hand, the treasure chest items are displayed in a display manner that makes it unclear what item can be acquired before acquiring them, and the acquired item becomes clear when acquired. Both items can be acquired by moving the player character to the location where they are placed. For example, the reward granting unit 317 grants the corresponding item as a reward based on the positional relationship between the player character and the treasure chest item or normal item. The acquired items include items that are consumed on the spot, such as items that recover parameters, and items that are confirmed to be acquired when the battle ends. In the case of an item that is confirmed to be acquired when the battle ends, it may be impossible to acquire it if the player loses the battle.

[0205] [Treasure Chest Item Specifications] The treasure chest items are arranged at a plurality of predetermined locations in the field. FIG. 19 is a diagram showing an example of display of the treasure chest items. As shown in the figure, the treasure chest items are displayed in a display mode showing an object representing a box, and the items in the contents that can be obtained are not known until they are obtained. That is, the display control unit 115 displays the treasure chest items arranged in the field in a display mode in which the type of item (reward contents) cannot be identified. The contents may be predetermined, or may be determined by lottery at the time of acquisition. When a certain user operates a player character to obtain a treasure chest item, the item is granted not only to that user but also to all users of the same team. For example, when an operation to obtain a treasure chest item arranged in the field is performed by any user, the reward granting unit 317 grants the item selected for each user as a reward to each user identified by user information belonging to the same team. Note that the item is not granted to users of the opponent team. Therefore, a strategy of acquiring more items than the opponent team by dividing the treasure chest items present in the field among users in the team and acquiring them may be possible.

[0206] Further, the placement information of the treasure chest item is associated with each team, but the placement position of the treasure chest item specified by this placement information is common. Therefore, the treasure chest item is placed in the same place in the field for each user. Furthermore, the information on whether each treasure chest item has been acquired or not is different for each team. In other words, a treasure chest item cannot be acquired by multiple users in a team in duplicate, and a treasure chest item once acquired by any user cannot be acquired by other users in the team. For example, the reward granting unit 317 excludes a treasure chest item that has been acquired by the operation of any user from the acquisition target for any user identified by the user information belonging to the same team. In other words, the reward granting unit 317 controls a team in which the "information on whether acquired or not acquired" included in the placement information of the treasure chest item associated with each team is "acquired", so that the team is excluded from the acquisition target for any user identified by the user information belonging to the team, so that other users in the team cannot acquire the item.

[0207] The placement information of the treasure chest items may be associated with each user information. When the placement information of the treasure chest items is associated with each user information, the placement positions of the treasure chest items specified by this placement information are common to all users. Furthermore, the information on whether each treasure chest item associated with each user information has been acquired or not is common to each team. In this way, the treasure chest items are placed in the same location in the field for every user, and the information on whether each treasure chest item has been acquired or not is managed for each team.

[0208] When a treasure chest item is acquired, the item is given to all users in the same team, but the contents given to each user are different even for the same treasure chest item. For example, since the contents are determined randomly, some users may be given a high-value item, while other users may be given a low-value item. For example, the display control unit 115 displays the type of item given to each user by the reward giving unit 317, which is identified by the user information belonging to the team. In other words, information showing the items given to users in the same team is displayed on the play screen, which serves as one opportunity for communication within the team.

[0209] It should be noted that items acquired from treasure chest items include items that are not included in normal items, such as items that can be equipped to the player character, and are often items that are relatively more valuable than normal items.

[0210] [Standard item specifications] Normal items are also arranged at multiple locations in the field that are set in advance. All types of normal items are arranged more than treasure chest items, and are encountered at a higher probability than treasure chest items. For example, the display control unit 115 displays normal items arranged in the field in a display mode that allows the type of item (reward content) to be identified. FIG. 20 is a diagram showing a display example of normal items. The normal item shown in the figure is a "meat" item that recovers HP, and is displayed in a display mode that shows an object representing meat. In this way, unlike treasure chest items, normal items can be identified before they are obtained. Note that many normal items, such as items that recover HP, are consumed on the spot. Therefore, when a user finds a normal item, the user may acquire it if necessary at the time, but if not necessary at the time, the user may not acquire it and may acquire it later when necessary.

[0211] The placement information of the normal item is set for each user, and does not affect other users. For example, a normal item acquired by a user can be acquired by other users regardless of the team. In other words, when an operation to acquire a normal item placed in the field is performed by any user, the reward granting unit 317 grants the normal item to the user, and when an operation to acquire the normal item is performed by another user, the reward granting unit 317 grants the normal item to the other user.

[0212] Furthermore, the placement information of normal items placed in the field is associated with each user information, but the placement positions of normal items specified by the placement information associated with each user information are common. The types of normal items (reward contents) specified by the placement information associated with each user information are also common. Therefore, the same type of normal item is placed in the same location in the field for each user. Meanwhile, information on whether each normal item has been acquired or not differs for each user. This allows each user to develop a strategy for when and where to acquire normal items (for example, whether to recover HP).

[0213] In the above description, the location information of normal items is associated with each user information, but it may be associated with each team. In this case, a strategy for using necessary items by necessary users within a team can be established on a team-by-team basis.

[0214] Next, the operation of the reward granting process for normal items and treasure chest items will be described. Fig. 21 is a flowchart showing an example of the reward granting process according to this embodiment.

[0215] When an item is acquired based on a user's operation on the input unit 13 (step S400), the reward granting unit 317 determines whether the acquired item is a normal item or a treasure chest item (step S402). If it is determined that the acquired item is a normal item, the reward granting unit 317 grants the normal item to the user (step S404).

[0216] On the other hand, if it is determined that the acquired item is a treasure chest item, the reward granting unit 317 randomly selects an item to be granted to each user from a plurality of items associated with the treasure chest item (step S406). Then, the reward granting unit 317 grants the selected item to each user based on the result of the selection (step S408). Furthermore, the reward granting unit 317 instructs the display control unit 115 to display information indicating the item granted to each user. As a result, the display control unit 115 displays information indicating the item granted to each user on the play screen (step S410).

[0217] [Summary of the sixth embodiment] As described above, in the game system 1 according to this embodiment, the character control unit 112 moves the characters associated with each user information within a field common to the team based on the operation of each user identified by the user information belonging to the team. When an operation to acquire a treasure chest item (an example of a first object) placed within the field is performed by any user, the reward granting unit 317 grants an item (an example of a reward) selected for each user to each user identified by the user information belonging to the same team.

[0218] This allows the game system 1 to divide the tasks of obtaining multiple treasure chest items present in the field among users on a team, thereby providing more opportunities for cooperation within a team in a team-based action game.

[0219] The display control unit 115 (an example of a first display control unit) displays the type of item (an example of the content of the reward) given to each user identified by the user information belonging to the team by the reward giving unit 317. This allows the game system 1 to know the type of item given to each user in the team, which can serve as a catalyst for communication within the team.

[0220] Furthermore, the display control unit 115 (an example of a first display control unit) displays treasure chest items (an example of a first object) placed in the field in a display mode in which the type of item (an example of the contents of the reward) cannot be identified. This allows the game system 1 to suggest that the type of item to be given will be known after the treasure chest item is obtained, i.e., the type of item to be given will not be known before obtaining the item, and by not knowing the type, the anticipation at the time of obtaining the item can be heightened.

[0221] Meanwhile, the display control unit 115 (an example of a second display control unit) displays normal items (an example of a second object) placed in the field in a display manner that allows the type of item (an example of the content of the reward) to be identified. This allows the game system 1 to enable the user to obtain a normal item after confirming in advance the type of item to be granted. For example, normal items are often items that are consumed on the spot, such as items that recover HP. Therefore, the user can determine whether or not to obtain a normal item as necessary after confirming in advance the type of item to be granted.

[0222] The reward granting unit 317 grants an item (an example of a reward) based on the positional relationship between the player character and a treasure chest item (an example of a first object). For example, the reward granting unit 317 grants an item by moving the player character to a location where the treasure chest item is located. In this way, the game system 1 allows users in a team to efficiently acquire items by having them share the task of moving the player character to each of a plurality of treasure chest items present in the field.

[0223] The reward granting unit 317 excludes a treasure chest item (an example of a first object) that has already been acquired by an operation of any user from the acquisition targets of any users identified by the user information belonging to the same team. This prevents multiple users in the same team from acquiring the same treasure chest item in duplicate, and therefore the game system 1 can prevent too many high-value items from being granted to users.

[0224] The reward granting unit 317 may exclude a treasure chest item (an example of a first object) that has already been acquired by the operation of any user from the acquisition targets for any user, regardless of the team. In this case, once one team has acquired the treasure chest item, the other team cannot acquire it, which makes the competition between the teams more intense.

[0225] Within the field, normal items (an example of a second object) different from treasure chest items (an example of a first object) are placed. When an operation to acquire a normal item placed within the field is performed by any user, the reward granting unit 317 grants a reward to the user, and when an operation to acquire the normal item is performed by another user, the reward granting unit 317 grants a reward to the other user.

[0226] In this way, the game system 1 can provide every user with an equal opportunity to acquire a normal item because a normal item acquired by a user can be acquired by other users regardless of team. Also, the game system 1 can allow each user to set a strategy for when and where to acquire a normal item (for example, to recover HP).

[0227] The placement information of the normal items (an example of the second object) placed in the field is associated with each user information, and the placement positions of the normal items specified by the placement information associated with each user information are common. This allows the game system 1 to place the normal items in the same places in the field for all users, so that all users can be given an equal opportunity to obtain the normal items.

[0228] The reward contents of the normal item (an example of the second object) specified by the placement information associated with each user information are the same. As a result, the game system 1 places the same type of normal item in the same place in the field for every user, so that every user can be given an equal opportunity to obtain the normal item.

[0229] [Seventh embodiment] Next, a seventh embodiment of the present invention will be described. The basic configuration of the game system 1 according to this embodiment is the same as that of the first embodiment, so a characteristic process of this embodiment will be described. In this embodiment, the process of the effect displayed on the play screen during a match play will be described.

[0230] The player characters used in a battle have various effects, such as being able to attack distant enemies or inflict damage over a wide area, depending on the characteristics based on the player character (player character characteristics or characteristics of equipment items equipped by the player character, etc.). When the player character attacks, an effect corresponding to the attack is displayed on the play screen. An effect is a display image (image) that visualizes an effect corresponding to the characteristics of the attack. FIG. 22 is a diagram showing an example of the display of effects on the play screen. The example shown in the figure shows an example of the display of an effect EF1 caused by an attack by the player character PR1 of the red team, and an example of the display of an effect EF2 caused by an attack by the player character PB1 of the blue team.

[0231] Generally, when such effects are displayed, the display mode is changed continuously in a short time, and a process of making the effects semi-transparent is frequently used, so that the processing load tends to be high. Therefore, in a scene where many player characters are displayed at the same time, it may be difficult to display the effects of all the player characters. For example, when the processing load becomes high (for example, the CPU usage rate exceeds 100%), delays in the drawing process and frame drops occur, which significantly impairs the operational feel. Even if the processing load is not a problem, when many effects are displayed, the effects may make it difficult to see the enemy's situation, making it difficult to grasp the progress of the game. Therefore, in this embodiment, a limit is set on the number of effects to be displayed, and the effects are displayed based on a priority (priority setting). For example, the display control unit 115 sets a limit on the display of effects based on a preset priority. Note that the priority setting may not be common, but may be set for each piece of user information.

[0232] For example, the priority is set so that the display of effects of a player character operated by a game device 10 (i.e., the player's own game device) on which the display control unit 115 executes the display process is prioritized over the display of effects of player characters operated by other game devices 10. In other words, the display control unit 115 restricts the display of effects of player characters operated by game devices 10 other than the game device 10 on which the display process is executed. This is to ensure a good operational feel for the user operating the game device 10, by giving a high priority to the effects of the player character operated by that user.

[0233] The priority may also be set so that the display of effects is restricted based on the characteristics of the player character or the characteristics of the equipment item. For example, the display of effects may be restricted based on the rarity of the player character or the rarity of the equipment item. Specifically, the display control unit 115 may prioritize the display of effects as the rarity of the player character or the equipment item increases.

[0234] The priority may be set so that the display of the effect is restricted based on the characteristics based on the time-limited effect set for the player character or the equipment item. The time-limited effect is a special effect that can be obtained only for a limited period of time. For example, attributes are set for the player character or the equipment item, and the ability of the player character or the equipment item with a specific attribute is increased as a time-limited effect depending on the day of the week, etc. Also, the ability of the character or the equipment item newly added to the game is set higher than usual for a certain period of time, such as 10 days after the addition, as a time-limited effect. For example, the display control unit 115 may prioritize the display of the effect of the player character or the equipment item to which the characteristics based on the time-limited effect are set, for that limited period of time.

[0235] Furthermore, the priority of displaying the effects of items possessed by the player character operated by the user himself / herself (or items that have been possessed in the past) among the equipment items of the player character operated by another user may be lowered. The priority of displaying the effects of items possessed by the player character operated by the user himself / herself (or items that have been possessed in the past) among the equipment items of the player character operated by another user may be lowered. In other words, the priority of the effects of items that the user already knows may be lowered since there is little need to inform the user of the effects. Information on items possessed by each user (items that can be equipped to the player character) and information on items that have been used as equipment items are stored in the user data storage unit 351 as an item possession history or item usage history.

[0236] In addition, when another user operates a character of the same type as a character owned by the user (or a character that the user has owned in the past) as a player character, the priority of displaying the effects of the player character operated by the other user may be lowered. In addition, when another user operates a character of the same type as a character operated by the user (or a character that the user has operated in the past) as a player character, the priority of displaying the effects of the player character operated by the other user may be lowered. In other words, the priority of the effects of a character that the user already knows may be lowered since there is little need to inform the user of the effects. Information on characters owned by each user (characters that can be operated as player characters) and information on characters that the user has operated as player characters is stored in the user data storage unit 351 as a character possession history or use history.

[0237] For example, the display control unit 115 may restrict the display of effects of a player character operated on a game device 10 other than the game device 10 executing the display process (i.e., the own game device 10 equipped with the display control unit 115), based on the possession history or usage history of a player character that can be controlled by a user on the game device 10, or the possession history or usage history of items that can be equipped to the player character.

[0238] Next, a specific example of a case where the display control unit 115 imposes a limit on the display of effects will be described. For example, the display control unit 115 imposes a limit on the display of effects in consideration of the above-mentioned priority based on the processing load of the game device 10 that itself executes the display process (i.e., the game device 10 that includes the display control unit 115). Specifically, the display control unit 115 may calculate the number of effects that can be displayed based on the current processing load (CPU usage rate) of the game device 10, and limit the number of effects to be displayed to less than or equal to this number. If the number of effects that need to be displayed simultaneously due to attacks by multiple users exceeds this calculated number of effects, the display control unit 115 may limit the display of effects in accordance with the above-mentioned priority.

[0239] Furthermore, in cases where the processing load differs significantly for each effect, the display control unit 115 may select and display a displayable effect based on the current processing load (CPU usage) of the game device 10 itself and the processing load for each effect. For example, setting information indicating the processing load for each effect may be stored in advance in the item data storage unit 354, and an effect to be preferentially displayed may be determined based on the setting information.

[0240] FIG. 23 is a diagram showing an example of setting information of an effect. The setting information of the effect shown in the figure shows an example of setting information related to the effect display of an equipment item, and an equipment item, a processing load, a rarity (degree of rarity), and a special effect period are associated with each other. The equipment item is the item ID of the equipment item. The processing load is the processing load of the CPU required to display the effect of the equipment item. The rarity is the rarity set to the equipment item. For example, the rarity is SS rarity, S rarity, and rarity in descending order, and one of them is set to each equipment item. In the case of an equipment item that can obtain a special effect for a limited time, the special effect period is set to the period during which the special effect can be obtained.

[0241] The display control unit 115 limits the display of effects as necessary so that the processing load is less than 100% when effects are displayed on the game device 10. For example, when limiting the display of effects, the display control unit 115 may prioritize equipment items with high rarity, or equipment items that are in a special effect period. The display control unit 115 may also limit the display of effects so that the processing load is less than 98% or less than 95%, for example.

[0242] When limiting the display of effects, the display control unit 115 may limit the content to be displayed instead of limiting the number of effects to be displayed. For example, an effect with a low priority may be changed to an effect with a low processing load (for example, a general-purpose effect that does not use special visuals).

[0243] [Summary of the Seventh Embodiment] As described above, the display control unit 115 of the game system 1 according to the present embodiment executes a display process for displaying effects based on characteristics associated with each of the player characters operated by each user in a game in which the player characters operated by each user identified by user information belonging to the team compete against the opponents of the player characters in a field common to the team. The display control unit 115 also places restrictions on the display of the effects based on a preset priority.

[0244] As a result, the game system 1 places restrictions on the display of effects based on the priority, and therefore can appropriately control the display of effects by multiple player characters.

[0245] For example, the display control unit 115 places a limit on the display of effects based on the processing load of the game device 10 that executes the display process. This allows the game system 1 to appropriately control the display of effects by multiple player characters in order to display high-priority effects while reducing the processing load so that the processing load of the game device 10 does not exceed (become overloaded).

[0246] Furthermore, the display control unit 115 restricts the display of effects of player characters operated on game devices 10 (i.e., other game devices 10) other than the game device 10 executing the above display process (i.e., the game device 10 equipped with the display control unit 115). This allows the game system 1 to preferentially display effects of a player character operated by the user on the game device 10 operated by the user, thereby ensuring a good operational feel for the user operating the game device 10.

[0247] Furthermore, the display control unit 115 restricts the display of effects of a player character operated on a game device 10 (i.e., another game device 10) other than the game device 10 that executes the display process (i.e., a game device 10 equipped with the display control unit 115) based on the possession or use history of a player character that can be operated by a user, or the possession or use history of an item that can be equipped to the player character. This allows the game system 1 to set the priority of effect display depending on whether the character or item is already known to the user, and therefore allows effects that need to be notified to the user (effects that the user has not seen yet) to be displayed preferentially over effects that need to be notified to the user less.

[0248] Furthermore, the display control unit 115 places restrictions on the display of effects based on a priority that is preset based on the characteristics associated with each player character operated by each user. This allows the game system 1 to set the priority of the effect display according to the characteristics of the player character, making it possible to highlight player characters with characteristics that are set to a high priority, and encouraging users to obtain characters with those characteristics.

[0249] For example, the characteristics associated with each player character for each user are characteristics based on the items associated with the respective player characters. This allows the game system 1 to set the priority of the effect display according to the characteristics of the equipment items, so that the equipment items with characteristics set to high priority can be made to stand out, and the user can be motivated to obtain the items with those characteristics.

[0250] The characteristics associated with each of the player characters for each user may be characteristics based on the rarity of each player character or an item associated with each player character. This allows the game system 1 to prioritize the display of effects of a player character with a higher rarity or an equipment item with a higher rarity. This allows, for example, weapons and characters that have never been seen before and seem to be highly valuable to be highlighted, and this can motivate the user to obtain those weapons and characters.

[0251] Furthermore, the characteristics associated with each of the player characters for each user may be characteristics based on a time-limited effect set for each of the player characters or an item associated with each of the player characters. This allows the game system 1 to prioritize the display of the special effect during a limited period in which the special effect can be obtained. This allows, for example, weapons and characters that are effective for a limited period to stand out, which can motivate the user to obtain those weapons and characters.

[0252] [Variations] Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configurations are not limited to the above-mentioned embodiments, and designs within the scope of the present invention are also included. For example, the configurations described in the first to seventh embodiments above can be combined in any manner.

[0253] In the above embodiment, an example of a one-on-one team match between the blue team and the red team has been described, but the present invention is not limited to this, and a match between three or more teams may be used. In the case of a match between three or more teams, a normal NPC in one's camp (team) can be attacked by player characters of all teams other than the one's camp (team). For example, the team that has defeated the most normal NPCs or the team that has inflicted the most damage on normal NPCs may become the team that occupies the normal room. In addition, a normal NPC to be attacked may be set for each camp (team) other than the one's camp (team).

[0254] In the above embodiment, an example of a team battle type has been described, but the present invention is not limited to this. The present invention may be applied to a game in which one team battles an enemy NPC and clears areas or stages in order each time the NPC is defeated. In this case, for example, the reward granting unit 317 may increase the points to be granted each time a predetermined condition is satisfied in the same area (e.g., a room) in the field. That is, the reward granting unit 317 may increase the value of the reward to be granted each time a predetermined occupation condition is satisfied in the same room. In addition, the normal NPC control unit 113 may decrease the time interval for making an NPC (e.g., a normal NPC) appear in the area, or increase the upper limit number of NPCs (e.g., a normal NPC) that can appear at the same time each time a predetermined condition is satisfied in the same area (e.g., a room) in the field.

[0255] In addition, a program for realizing the functions of the game control unit 110 or the server control unit 310 may be recorded in a computer-readable recording medium, and the program recorded in the recording medium may be read into a computer system and executed to perform part or all of the processing of the game control unit 110 or the server control unit 310. Here, "reading a program recorded in a recording medium into a computer system and executing it" includes installing the program into a computer system. The "computer system" here includes hardware such as an OS and peripheral devices. The "computer system" may also include a plurality of computer devices connected via a network including the Internet, a WAN, a LAN, a dedicated line, and other communication lines. The "computer-readable recording medium" refers to a portable medium such as a flexible disk, an optical magnetic disk, a ROM, a CD-ROM, and a storage device such as a hard disk built into a computer system. In this way, the recording medium storing the program may be a non-transient recording medium such as a CD-ROM. The recording medium also includes a recording medium provided inside or outside the distribution server that can be accessed from the distribution server in order to distribute the program. The code of the program stored in the recording medium of the distribution server may be different from the code of the program in a format executable by the terminal device. That is, the format in which the program is stored in the distribution server does not matter as long as the program can be downloaded from the distribution server and installed in a form executable by the terminal device. The program may be divided into multiple parts, each of which may be downloaded at a different time and then combined on the terminal device, or each of the divided programs may be distributed by a different distribution server. Furthermore, the term "computer-readable recording medium" includes a storage medium that holds a program for a certain period of time, such as a volatile memory (RAM) inside a computer system that is a server or client when a program is transmitted over a network. The program may also be one that realizes part of the above-mentioned functions.Furthermore, the above-mentioned functions may be realized in combination with a program already recorded in the computer system, that is, a so-called differential file (differential program).

[0256] Also, the above-mentioned game control unit 110 or the server control unit 310 may be partly or entirely realized as an integrated circuit such as an LSI (Large Scale Integration). Each of the above-mentioned functions may be individually implemented as a processor, or partly or entirely integrated into a processor. The integrated circuit implementation method is not limited to LSI, and may be implemented using a dedicated circuit or a general-purpose processor. Furthermore, if an integrated circuit implementation technology that can replace LSI appears due to advances in semiconductor technology, an integrated circuit based on that technology may be used.

[0257] Furthermore, a part of the configuration of the above-mentioned game control unit 110 may be included in the server control unit 310. For example, the game server 30 may be responsible for most of the game processing, and the game device 10 may be responsible for displaying game images based on the game processing executed by the game server 30 and inputting user operations.

[0258] [Note] From the above description, the present invention can be understood, for example, as follows: In order to facilitate understanding of the present invention, reference numerals in the accompanying drawings are conveniently written in parentheses, but the present invention is not limited to the illustrated embodiments.

[0259] (Appendix A1) A game system (1) according to one embodiment of the present invention includes a character movement unit (112) that moves a character (P1) associated with each user information within a field (FLD) having a plurality of areas (e.g., rooms) common to a plurality of teams based on operations of each user identified by user information belonging to each of the plurality of teams, an area determination unit (315, S100) that determines which team the area should be associated with (e.g., which team should occupy) based on whether or not the operation result of the user satisfies a predetermined condition (e.g., a predetermined occupation condition), and a win / loss determination unit (316, S114) that determines the outcome of a match between the plurality of teams based on the determination result by the area determination unit.

[0260] According to the configuration of appendix A1, the game system can provide a new enjoyment in a team-based action game in which players move player characters within a field by operating each user, in which the winner is decided by occupying territories (e.g., rooms). For example, this game system can allow users to play without losing tension, since it is always possible to know which team is dominant based on the number of territories occupied. Furthermore, compared to a one-on-one game in which players compete for territories, this game system is a team-based game, and therefore can provide a more strategic game due to the fact that multiple player characters appear on both sides, as well as cooperative play as a team.

[0261] (Appendix A2) Also, one aspect of the present invention is a game system as described in Appendix A1, comprising an NPC control unit (113, 312) that controls an NPC (non-player character) in the area, and the area determination unit determines whether or not to associate the area with a team when the defeat status of the NPC in the area satisfies the predetermined condition.

[0262] According to the configuration of Appendix A2, the game system allows players to occupy multiple areas (e.g., rooms) within the field by defeating NPCs (e.g., normal NPCs or boss NPCs) that appear in each of the areas, thereby placing each team's opponents on the same playing field and maintaining fairness.

[0263] (Additional Note A3) Furthermore, one aspect of the present invention is the game system according to Additional Note A2, in which the NPC in the area corresponds to any one of the multiple teams.

[0264] According to the configuration of Appendix A3, the game system can create a situation similar to fighting against an opponent's team, even though the opponent is an NPC, allowing the user to play while feeling like they are fighting a team battle.

[0265] (Appendix A4) Also, one aspect of the present invention is a game system described in any one of Appendices A1 to A3, wherein the win / loss determination unit determines the outcome of a match between the multiple teams based on the number of areas associated with each of the multiple teams based on the determination result by the area determination unit.

[0266] According to the configuration of Appendix A4, in the game system, the victory or defeat of a team is decided by the number of areas (for example, rooms) occupied, so that the user can easily understand the situation during the match and the result when the match ends.

[0267] (Appendix A5) Also, one aspect of the present invention is a game system as described in any one of Appendices A1 to A4, comprising a reward granting unit (317) that grants points to a team with which the area is associated by the area determination unit or to a user identified by user information belonging to the team.

[0268] According to the configuration of Appendix A5, the game system awards points to a team or a user of a team that occupies an area (e.g., a room), so that it is possible to add fun beyond the occupancy situation. For example, when the game system awards points to each user, it is possible to give users the fun of competing with other users in a team in addition to competing with other teams.

[0269] (Appendix A6) Also, one aspect of the present invention is the game system described in Appendix A5, wherein the reward granting unit grants points according to the area to a team with which the area is associated by the area determination unit or to a user identified by user information belonging to the team.

[0270] According to the configuration of Appendix A6, the game system awards different points depending on the area (e.g., room) occupied, so that a team can choose a strategy, for example, to try to occupy many areas with low difficulty or to try to occupy at least a few areas with high difficulty, thereby providing a highly strategic game.

[0271] (Appendix A7) Also, one aspect of the present invention is the game system described in Appendix A5 or Appendix A6, wherein, when the predetermined condition is satisfied in an area associated with one of the multiple teams by an operation result of a user identified by user information belonging to another team, the area determination unit associates the area with the other team or the user information belonging to the other team, and the reward granting unit increases the points to be awarded each time the predetermined condition is satisfied in the same area.

[0272] According to the configuration of Appendix A7, the game system allows teams to occupy the same area (e.g., a room) and thereby awards higher points when the area is occupied, thereby increasing the motivation of users on each team to play against each other repeatedly, and an exciting game can be expected.

[0273] (Appendix A8) Also, one aspect of the present invention is a game system as described in any one of Appendices A5 to A7, wherein the reward granting unit increases the points to be granted when an area is associated with a team, the more areas the area determination unit associates with the team.

[0274] According to the configuration of appended note A8, the game system can allow a player to advance the game with an advantage as the player occupies more areas (for example, rooms).

[0275] (Appendix A9) Also, one aspect of the present invention is a game system described in any one of Appendices A5 to A8, wherein the win / loss determination unit determines the outcome of a match between the multiple teams based on the determination results for each of the multiple areas by the area determination unit and points awarded by the reward awarding unit to each team or to a user identified by user information belonging to the team.

[0276] According to the configuration of Appendix A9, the game system can provide a highly strategic game since winning or losing depends not only on occupying an area (e.g., a room) but also on obtaining points, and therefore winning or losing depends on which area is occupied.

[0277] (Appendix A10) Also, one aspect of the present invention is a game system as described in any one of Appendices A5 to A9, wherein the reward granting unit generates an advantageous effect in the progress of play based on the operation of a user identified by user information belonging to a team in the area associated with the team by the area determination unit.

[0278] According to the configuration of appended note A10, the game system can allow a player to advance in the game with an advantage as the player occupies more areas (for example, rooms).

[0279] (Appendix A11) Also, one aspect of the present invention is a game system described in any one of Appendices A1 to A10, in which each of the characters is set with a characteristic that affects the progress of play based on the user's operation.

[0280] According to the configuration of appendix A11, the game system can provide a highly strategic game because the type and power of an attack vary depending on the characteristics of the character, and superiority or inferiority also depends on the compatibility of the characteristics of the opponent.

[0281] (Appendix A12) Another aspect of the present invention is a program for causing a computer to function as the game system according to any one of Appendices A1 to A11.

[0282] According to the configuration of Appendix A12, the program can provide a new level of entertainment in a team-based action game in which each user operates to move a player character within a field, in which the winner is decided by occupying an area (e.g., a room).

[0283] (Appendix B1) Furthermore, a game system (1) according to one embodiment of the present invention includes a character movement unit (112) that moves a character associated with each user information within a field (FLD) having a common area within a team based on an operation of each user identified by user information belonging to the team, an NPC control unit (113) that causes an NPC (non-player character) to appear in the area at a predetermined time interval, an area determination unit (315) that determines whether or not to associate the area with the team when the defeat status of the NPC in the area satisfies a predetermined condition, and a win / loss determination unit (316) that determines whether the team wins or loses based on the area associated with the team by the area determination unit.

[0284] According to the configuration of Appendix B1, the game system makes it difficult for a single person to occupy an area (for example, a normal room) because an NPC (for example, a normal NPC) revives at a predetermined time interval even if it is defeated, making it necessary to play in a team with more cooperation. Therefore, the game system can provide a game with a high level of team battle awareness.

[0285] (Appendix B2) Also, one aspect of the present invention is the game system described in Appendix B1, in which the NPC defeat status is the number of NPCs appearing in the area.

[0286] According to the configuration of Appendix B2, the game system can occupy an area (for example, a normal room) when the number of NPCs (for example, normal NPCs) appearing in the area at a predetermined time interval meets a predetermined condition (for example, the number of normal NPCs becomes 0), so the conditions for occupying the area are easy to understand. In addition, since the area can be occupied quickly by cooperating with team members, the user can feel a sense of unity as they fight as a team.

[0287] (Appendix B3) Also, one aspect of the present invention is a game system as described in Appendix B1 or Appendix B2, wherein the NPC control unit causes the NPCs to appear at predetermined time intervals in the area until the number of NPCs appearing simultaneously in the area reaches a preset upper limit number.

[0288] According to the configuration of Appendix B3, the game system makes it difficult for one person to occupy an area (for example, a normal room) easily, since the initial number of NPCs (for example, normal NPCs) that initially exist (appear) in the area (for example, a normal room) are revived even if they are defeated, making it necessary to play in cooperation with a team. Therefore, the game system 1 can provide a game with a high level of team battle awareness.

[0289] (Appendix B4) Also, one aspect of the present invention is a game system as described in any one of Appendices B1 to B3, wherein, when there are multiple areas within the field, the NPC control unit controls, for each of the multiple areas, the time interval at which the NPC appears or the upper limit number of the NPCs that may appear simultaneously.

[0290] According to the configuration of Appendix B4, the game system can set the difficulty level of occupancy for each area (for example, a normal room).

[0291] (Appendix B5) Also, one aspect of the present invention is a game system described in any one of Appendices B1 to B4, wherein the NPC control unit decreases the time interval for causing the NPC to appear in the same area, or increases the upper limit number of NPCs that can appear simultaneously, each time the specified condition is satisfied in the same area.

[0292] According to the configuration of Appendix B5, the game system has teams occupying the same area (e.g., a regular room), making it more difficult to occupy that area, which requires more cooperative team play and is expected to make for an exciting game.

[0293] (Appendix B6) Also, one aspect of the present invention is a game system described in any one of Appendices B1 to B5, comprising a reward granting unit (317) that grants a reward to a team with which the area is associated by the area determination unit.

[0294] According to the configuration of Appendix B6, the game system 1 awards points to a team or a user of a team that occupies an area (for example, a normal room), so that it is possible to add fun beyond the occupancy situation. For example, when the game system 1 awards points to each user, it is possible to give users the fun of competing with other users in a team in addition to playing against other teams.

[0295] (Additional Note B7) Another aspect of the present invention is the game system described in Additional Note B6, in which the reward granting unit increases the value of the reward to be granted each time the predetermined condition is satisfied in the same area.

[0296] According to the configuration of Appendix B7, the game system allows teams to occupy the same area (e.g., a regular room) and higher points are awarded when the area is occupied, thereby increasing the motivation of users on each team to play against each other repeatedly, and an exciting game can be expected.

[0297] (Supplementary Note B8) Another aspect of the present invention is a program for causing a computer to function as the game system according to any one of Supplementary Note B1 to Supplementary Note B7.

[0298] According to the configuration of Appendix B8, the program makes it difficult for a single person to occupy an area (for example, a normal room) because an NPC (for example, a normal NPC) revives at a predetermined time interval even if it is defeated, and requires more cooperative play in a team. Thus, the program can provide a game with a high level of teamwork awareness.

[0299] (Appendix C1) Furthermore, a game system (1) according to one embodiment of the present invention includes a character control unit (112) that activates a first character for each user within a field (FLD) common to the multiple teams based on an operation of each user identified by user information belonging to each of the multiple teams, a first NPC control unit (113) that controls a first NPC (non-player character) within the field, and a battle control unit (114) that controls attacks from the first team to the first NPC based on an operation of a user identified by user information belonging to a first team among the multiple teams, and restricts attacks from a second team other than the first team among the multiple teams to the first NPC.

[0300] According to the configuration of appendix C1, the game system can prevent a situation that may occur in an online game where an NPC (for example, a normal NPC) cannot be defeated even though it was attacked, because only one of the teams can attack the first NPC (for example, a normal NPC) (for example, both the blue team and the red team cannot attack), and thus the game system can prevent a situation that may occur in an online game where an NPC cannot be defeated even though it was attacked. In other words, the game system can prevent an effect of a time lag that may occur in an online game.

[0301] (Appendix C2) Also, one aspect of the present invention is the game system described in Appendix C1, wherein when the battle control unit controls an attack on a second character whose action is based on operations of a user identified by user information belonging to the second team based on operations of a user identified by user information belonging to the first team, the battle control unit limits the impact of an attack on the second character to be smaller than the impact of an attack on the first NPC.

[0302] According to the configuration of Appendix C2, in the game system, when characters controlled by users battle each other, there may occur an incident where an attack was attempted but the enemy was not defeated. However, by making the damage from an attack extremely small, the benefits of battling the characters against each other are reduced, and the factors that motivate the characters to battle each other are reduced, so that the impact of the above-mentioned discrepancy can be suppressed.

[0303] (Additional Note C3) Furthermore, one aspect of the present invention is the game system described in Additional Note C2, in which the match control unit limits the activity of the second character by an attack on the second character.

[0304] According to the configuration of Appendix C3, in a battle between characters controlled by users, the game system aims to stop the movements of the opponent's character rather than inflict damage on it, thereby preventing the occurrence of a situation where an attack is made but the opponent fails to defeat the character.

[0305] (Appendix C4) Also, one aspect of the present invention is a game system as described in any one of Appendices C1 to C3, comprising a plurality of terminal devices (10) equipped with the first NPC control unit, and a server device (30) communicatively connected to the terminal devices, wherein the first NPC control unit controls the position of the first NPC within the field for each of the plurality of terminal devices.

[0306] According to the configuration of Appendix C4, the game system basically manages actions that require real-time performance, such as the position and movement (motion) of the first NPC (e.g., a normal NPC) within the field, and the effects (effects) when an attack (skill) is activated, on each game device (terminal side), thereby preventing the effects of time lag caused by communication from occurring.

[0307] (Appendix C5) Also, one aspect of the present invention is a game system as described in Appendix C4, wherein the server device is provided with a second NPC control unit (312) that controls a second NPC different from the first NPC within the field, the battle control unit controls attacks from the first team to the second NPC based on operations of a user identified by user information belonging to the first team, and controls attacks from the second team to the second NPC based on operations of a user identified by user information belonging to the second team, and the second NPC control unit controls the position of the second NPC within the field so that it is in the same position on multiple terminal devices.

[0308] According to the configuration of Appendix C5, the game system can synchronize the position of the target of attack of a second NPC (e.g., a boss NPC) that is attacked by both sides (e.g., both the blue team and the red team) so that it is the same on each game device, thereby ensuring consistency in battles between multiple users against the same target.

[0309] (Additional Note C6) Furthermore, one aspect of the present invention is the game system described in Additional Note C5, in which defeating the second NPC requires more attacks than defeating the first NPC.

[0310] According to the configuration of Appendix C6, the game system can have a proto-word in which the attack at the time of defeat (the final finishing blow) is not defeated even though it was supposed to have been attacked, but it does not become a major proto-word in terms of the attacks from both teams up to that point, even if the order of the attacks is switched, so the impact of the above-mentioned discrepancy on the overall attacks up to the defeat can be reduced.

[0311] (Additional Note C7) Another aspect of the present invention is a program for causing a computer to function as the game system according to any one of Additional Note C1 to Additional Note C6.

[0312] According to the configuration of appendix C7, the program can prevent a situation that may occur in an online game where an attack was attempted but the NPC was not defeated, because the first NPC (for example, a normal NPC) can only be attacked by one of the teams (for example, the NPC cannot be attacked by both the blue team and the red team). In other words, the program can prevent the influence of a time lag that may occur in an online game.

[0313] (Appendix D1) Furthermore, a game system (1) according to one embodiment of the present invention includes an area determination unit (315, S100) that determines whether or not to associate each of a plurality of areas in a field (FLD) with a team (e.g., which team should occupy it) based on whether or not the operation result of a user identified by user information belonging to a team satisfies a predetermined condition, and a win / loss determination unit (316, S114) that determines whether or not the team has won based on the determination result by the area determination unit within a preset time limit, and the win / loss determination unit determines whether or not the team has won based on the association status of the plurality of areas with the team even before the time limit is reached (S204-S220).

[0314] According to the configuration of Appendix D1, in an action game in which multiple users forming a team control their own characters to fight enemy characters, if the outcome of the battle becomes clear and the outcome is essentially decided before the time limit has expired, the game system determines the outcome at that point and ends the game, thereby preventing users from wasting time playing.

[0315] (Appendix D2) Also, one aspect of the present invention is the game system described in Appendix D1, in which the win / lose determination unit determines the win / lose of the team when a preset status of association of the multiple areas with the team occurs (for example, when all rooms are occupied by one team), and the status is maintained for a predetermined time, even before the time limit is reached (S204 to S220).

[0316] According to the configuration of appendix D2, even if the association status of the multiple areas with the teams becomes a preset status (for example, all rooms are occupied by one team), the game system can give the occupied team time to have a chance to make a comeback. Therefore, the game system can prevent the occurrence of irrationality such as the match ending without being able to show its true ability due to a sudden attack due to some factor.

[0317] (Appendix D3) Also, one aspect of the present invention is the game system described in Appendix D2, wherein the win / lose determination unit shortens the specified time depending on the number of times the association status of the multiple areas with the team becomes a preset status (S204, S216).

[0318] According to the configuration of Appendix D3, for example, when all rooms are repeatedly occupied, the game system is more certain that the team in question will have the advantage than when all rooms were occupied the first time, thereby shortening the time that the occupied team has a chance to make a comeback and preventing users of the team that occupied all rooms from wasting playing time.

[0319] (Additional Note D4) Furthermore, one aspect of the present invention is the game system according to Additional Note D3, in which, in the case of a match between a plurality of teams, the number of times is counted for each team.

[0320] According to the configuration of Appendix D4, for example, when one team occupies all the rooms and then the other team regains control of all the rooms, the game system can provide each team with an equal amount of time to make a comeback, since it is considered that the outcome of the battle is not clear.

[0321] (Appendix D5) Also, one aspect of the present invention is a game system as described in any one of Appendices D2 to D4, comprising a display control unit (115) that displays information indicating the time until the specified time is reached when the association status of the multiple areas with the team reaches a preset status.

[0322] According to the configuration of appendix D5, the game system can increase the sense of tension by presenting the time remaining until the outcome of a match to the user during the match play by using a countdown or the like. In addition, the game system can make it easier for the user to grasp the remaining time until the outcome of the match is determined, making it easier for the user to consider a strategy for what to do with the remaining time.

[0323] (Appendix D6) Also, one aspect of the present invention is a game system described in any one of Appendices D2 to D5, wherein when the association status of the multiple areas to the team becomes a preset status, the display control unit determines whether or not to display information indicating the time remaining until the predetermined time is reached based on the remaining time until the time limit is reached and the predetermined time (S206, S214).

[0324] According to the configuration of Appendix D6, if the remaining time of the match is shorter than the countdown time, even if the countdown begins, the match will end due to the time limit before the countdown reaches "0", so the game system can avoid displaying a meaningless countdown.

[0325] (Appendix D7) Also, one aspect of the present invention is a game system as described in any one of Appendices D1 to D6, comprising a character movement unit (112) that moves a character associated with each user information within a field having multiple areas common to the users based on an operation of each user identified by user information belonging to the team.

[0326] According to the configuration of Appendix D7, when the outcome of the battle becomes clear and the outcome is essentially decided before the time limit, the game system will determine the outcome at that point and end the game, thereby preventing the user from wasting time moving the character around the field.

[0327] (Appendix D8) Another aspect of the present invention is a program for causing a computer to function as a game system according to any one of Appendices D1 to D7.

[0328] According to the configuration of Appendix D8, in an action game in which multiple users forming a team control their own characters to fight enemy characters, if the outcome of the battle becomes clear and the outcome is essentially decided before the time limit has expired, the program will determine the outcome at that point and end the game, thereby preventing users from wasting time playing.

[0329] (Appendix E1) Furthermore, a game system (1) according to one embodiment of the present invention includes a character control unit (112) that activates a character associated with each user information within a field (FLD) common to the team based on an operation of each user identified by user information belonging to the team; a character state control unit (1121, S304, S312) that transitions the character in a first state (e.g., normal state) to a second state (e.g., suspended animation) in which the ability is lower than that of the first state, on condition that a predetermined first condition is satisfied for the character in the first state, and transitions the character in the second state to a third state (e.g., death) in which the activity of the character is restricted, on condition that a predetermined second condition is satisfied for the character in the second state; a resurrection control unit (1122, S312) that resurrects the character in the second state to the first state based on other characters belonging to the same team as the character; and a win / loss determination unit (316, S114) that determines the win / loss of the team based on the result of the activity of the character by the character control unit.

[0330] According to the configuration of appendix E1, the game system can put a character in a first state (e.g., a normal state) into a second state (e.g., a suspended animation state) in which there is a chance for revival with the cooperation of the same team before the character is attacked and put into a third state (e.g., a death state). Thus, the game system can increase the opportunities for cooperation within a team in a team-based action game.

[0331] (Appendix E2) Also, one aspect of the present invention is a game system as described in Appendix E1, in which the resurrection control unit transitions the character in the third state (e.g., a dead state) to the first state (e.g., a normal state) or the second state (e.g., a suspended animation state) after a predetermined time has elapsed since the character entered the third state.

[0332] According to the configuration of appendix E2, even if the character enters the third state (e.g., death state), the game system does not end the game, but continues playing, and restarts after a certain period of inoperability, so that the player can participate in the match play again and contribute to the team. Also, since the game system makes it impossible to operate the character for a certain period of time when the character enters the third state (e.g., death state), it is possible to provide an incentive for the team to cooperate in order to somehow revive the character while in a state of suspended animation.

[0333] (Appendix E3) Also, one aspect of the present invention is the game system described in Appendix E2, wherein when the resurrection control unit transitions the character in the third state (e.g., a dead state) to the first state (e.g., a normal state) or the second state (e.g., a suspended animation state), the resurrection control unit places the transitioned character in a predetermined location within a field.

[0334] According to the configuration of Appendix E3, the game system can give a character that has entered the third state (e.g., a dead state) a locational penalty in addition to a time penalty of being unable to operate the character for a certain period of time by restarting the character from the starting room.

[0335] (Appendix E4) Also, one aspect of the present invention is a game system described in any one of Appendices E1 to E3, in which the resurrection control unit resurrects the character in the second state (e.g., a suspended animation state) to the first state based on a positional relationship with other characters in the first state (e.g., a normal state) that belong to the same team as the character.

[0336] According to the configuration of Appendix E4, in order to revive a character in suspended animation, the game system requires other characters on the same team to move to the location of the character in suspended animation, thereby giving the feeling that team members are working together to rescue the character.

[0337] (Appendix E5) Also, one aspect of the present invention is a game system described in any one of Appendices E1 to E4, wherein the third state (e.g., a death state) includes a state in which the activity of the character is restricted and in which the character cannot be revived to the first state (e.g., a normal state) based on another character belonging to the same team as the character.

[0338] According to the configuration of Appendix E5, the game system can provide an incentive for team members to cooperate to somehow revive a character while in the second state (e.g., suspended animation), since once the character reaches the third state (e.g., death), the character cannot be revived through cooperation within the team.

[0339] (Appendix E6) Also, one aspect of the present invention is the game system described in Appendix E5, wherein the second state (e.g., suspended animation) in which the character's abilities are lower than in the first state (e.g., normal state) includes a state in which the character's activities are restricted.

[0340] According to the configuration of Appendix E6, when the game system transitions a character to a second state (e.g., a suspended animation state), the character's activity is more restricted than in the first state (e.g., a normal state), thereby reducing the team's fighting power in competitive play, and therefore the team members can be motivated to revive the player character in the second state.

[0341] (Appendix E7) Also, one aspect of the present invention is a game system as described in any one of Appendices E1 to E5, wherein the second state (e.g., a state of suspended animation) in which the ability of the character is reduced compared to the first state (e.g., a normal state) includes a state in which the value of a parameter associated with the character is changed to a value that reduces the ability of the character compared to the first state (e.g., the normal state).

[0342] According to the configuration of Appendix E7, when the game system transitions a character to a second state (e.g., a state of suspended animation), the values ​​of the character's parameters such as attack power, defense power, and HP are lower than in the first state (e.g., a normal state), which reduces the team's fighting power in competitive play, and therefore can motivate team members to revive the character in the second state (e.g., a state of suspended animation).

[0343] (Appendix E8) Also, one aspect of the present invention is a game system described in any one of Appendices E1 to E7, in which the resurrection control unit limits the number of times that the character is resurrected from the second state (e.g., a suspended animation state) to the first state (e.g., a normal state).

[0344] According to the configuration of Appendix E8, the game system can prevent the difficulty of the game from becoming too low or the difference in skill between teams from being ignored due to the unlimited revivals.

[0345] (Appendix E9) Also, one aspect of the present invention is a game system as described in any one of Appendices E1 to E8, comprising a display control unit (115) that, when the character acting based on a user's operation on a first terminal device is in the second state (e.g., a suspended animation state), displays the character on a second terminal device in a display manner that is distinguishable from the character in the first state (e.g., a normal state).

[0346] According to the configuration of appended claim E9, the game system can display a character in the second state (eg, suspended animation state) on the play screen so that the character can be easily distinguished from a character in the first state (eg, normal state).

[0347] (Appendix E10) Another aspect of the present invention is a program for causing a computer to function as the game system according to any one of appendices E1 to E9.

[0348] According to the configuration of appendix E10, the program can cause a character in a first state (e.g., a normal state) to be attacked and put into a third state (e.g., a death state) before the character is put into a second state (e.g., a suspended animation state) in which there is a chance of revival with the cooperation of the same team. Thus, the program can increase the opportunities for cooperation within a team in a team-based action game.

[0349] (Appendix F1) Furthermore, a game system (1) according to one embodiment of the present invention includes a character moving unit (112) that moves a character associated with each user identified by user information belonging to the team within a field (FLD) common to the team based on an operation of each user identified by the user information of the team, and a reward granting unit (317, S408) that grants a reward (e.g., an item) selected for each user to each user identified by the user information belonging to the team when an operation to obtain a first object (e.g., a treasure chest item) placed within the field is performed by any of the users.

[0350] According to the configuration of Appendix F1, the game system enables users in a team to share the task of obtaining multiple first objects (e.g., treasure chest items) present in the field, thereby providing more opportunities for cooperation within a team in a team-based action game.

[0351] (Appendix F2) Also, one aspect of the present invention is a game system as described in Appendix F1, comprising a first display control unit (115, S410) that displays the content of the reward for each user (e.g., type of item) that the reward granting unit has granted to each user identified by user information belonging to the team.

[0352] According to the configuration of appendix F2, the game system can know the content of the reward given to each user in the team, which can serve as an opportunity for communication within the team.

[0353] (Appendix F3) Also, one aspect of the present invention is the game system described in Appendix F2, wherein the first display control unit displays the first object (e.g., a treasure chest item) placed in the field in a display manner in which the reward content (e.g., type of item) is not identifiable.

[0354] According to the configuration of Addendum F3, the game system indicates that the reward content will be known after the first object (e.g., a treasure chest item) is obtained, i.e., the reward content is not known before obtaining the first object, and the lack of knowledge can increase the sense of anticipation at the time of obtaining the object.

[0355] (Appendix F4) Another aspect of the present invention is a game system described in any one of Appendices F1 to F3, wherein the reward granting unit grants the reward (e.g., an item) based on the positional relationship between the character and a first object (e.g., a treasure chest item).

[0356] According to the configuration of Addendum F4, the game system allows users to efficiently obtain rewards (e.g., items) by having users in a team share the task of moving each of a number of first objects (e.g., treasure chest items) present in the field.

[0357] (Appendix F5) Also, one aspect of the present invention is a game system described in any one of Appendices F1 to F4, wherein the reward granting unit excludes the first object that has already been acquired by operation of any of the users from being available for acquisition by any of the users identified by user information belonging to the team.

[0358] According to the configuration of Addendum F5, the game system can prevent multiple users on the same team from acquiring the same first object (e.g., a treasure chest item) in duplicate, thereby preventing users from being given too many high-value rewards (e.g., items).

[0359] (Appendix F6) Also, one aspect of the present invention is a game system described in any one of Appendices F1 to F5, in which a second object (e.g., a normal item) different from the first object is placed in the field, and the reward granting unit grants a reward (e.g., an item) to one of the users when an operation to acquire the second object placed in the field is performed by one of the users, and grants a reward (e.g., an item) to the other user when an operation to acquire the second object (e.g., a normal item) is performed by another of the users (S404).

[0360] According to the configuration of appendix F6, the game system allows any user to have an equal opportunity to acquire the second object, since a second object (e.g., a normal item) acquired by a certain user can be acquired by other users regardless of team. Also, the game system 1 allows each user to set a strategy for when and where to acquire the second object (e.g., to recover HP).

[0361] (Appendix F7) Also, one aspect of the present invention is a game system described in any one of Appendices F6, in which placement information of the second object (e.g., a normal item) placed in the field is associated with each of the user information, and the placement position of the second object identified by the placement information associated with each of the user information is common.

[0362] According to the configuration of supplementary note F7, the game system places the second object (eg, a normal item) in the same location in the field for every user, and therefore, every user can be given an equal opportunity to obtain the second object.

[0363] (Additional Note F8) Another aspect of the present invention is a game system according to any one of Additional Note F7, in which the reward content of the second object specified by the placement information associated with each piece of user information is common.

[0364] According to the configuration of Appendix F8, the game system places the same type of second object (e.g., a normal item) in the same location in the field for each user, thereby giving each user an equal opportunity to obtain the second object.

[0365] (Appendix F9) Also, one aspect of the present invention is a game system as described in Appendix F6 or Appendix F7, comprising a second display control unit (115) that displays the second object (e.g., a normal item) placed in the field in a display manner in which the reward content (e.g., the type of item) is identifiable.

[0366] According to the configuration of appended note F9, the game system allows the user to obtain a second object (e.g., a normal item) after confirming the content of the reward to be given in advance. For example, the second object is often consumed on the spot, such as an item that recovers HP. Therefore, the user can determine whether or not to obtain the second object as necessary after confirming the content of the reward to be given in advance.

[0367] (Additional Note F10) Another aspect of the present invention is a program for causing a computer to function as the game system according to any one of Additional Notes F1 to F3.

[0368] According to the configuration of Appendix F10, the program enables users in a team to share the task of obtaining multiple first objects (e.g., treasure chest items) present in the field, thereby providing more opportunities for cooperation within a team in team-based action games.

[0369] (Appendix G1) Furthermore, a game system (1) according to one embodiment of the present invention includes a display control unit (115) that executes a display process to display effects based on characteristics associated with each of the characters operated by each user in a game in which characters operated by each user identified by user information belonging to a team compete against an opponent of the characters within a field (FLD) common to the team, and the display control unit places restrictions on the display of the effects based on a preset priority.

[0370] According to the configuration of supplementary note G1, the game system imposes restrictions on the display of effects based on the priority, and therefore, it is possible to appropriately control the display of effects by a plurality of characters.

[0371] (Appendix G2) Also, one aspect of the present invention is a game system as described in Appendix G1, comprising a terminal device (10) equipped with the display control unit, and a server device (30) communicatively connected to the terminal device, wherein the display control unit sets limitations on the display of the effect based on the processing load of the terminal device executing the display process.

[0372] According to the configuration of Appendix G2, the game system can appropriately control the display of effects by multiple characters, by reducing the processing load so that the processing load on the terminal device does not exceed (become overloaded), while displaying high priority effects.

[0373] (Appendix G3) Also, one aspect of the present invention is a game system as described in Appendix G1 or Appendix G2, comprising a plurality of the terminal devices, wherein the display control unit limits the display of the effects of a character operated on a terminal device other than the terminal device executing the display process.

[0374] According to the configuration of Appendix G3, the game system prioritizes displaying the effects of the character controlled by the user on the terminal device operated by the user, thereby ensuring a good operating feel for the user operating the terminal device.

[0375] (Appendix G4) Also, one aspect of the present invention is a game system as described in Appendix G3, wherein the display control unit restricts the display of the effects of a character operated on a terminal device other than the terminal device executing the display process, based on the possession history or usage history of a character controllable by the user, or the possession history or usage history of an item that can be equipped to the character.

[0376] According to the configuration of Appendix G4, the game system can set the priority of effect display depending on whether the character or item is already known to the user, and can therefore prioritize display of effects that are more important to inform the user of (effects that the user has not seen yet) over effects that are less important to inform the user of.

[0377] (Appendix G5) Also, one aspect of the present invention is a game system described in any one of Appendices G1 to G4, wherein the display control unit limits the display of the effects based on a priority that is preset based on characteristics associated with each of the characters operated by the user.

[0378] According to the configuration of Appendix G5, the game system can set the priority of displaying effects based on the characteristics of the player character, so that player characters with characteristics set to a high priority can be made to stand out, thereby motivating the user to obtain a character with those characteristics.

[0379] (Appendix G6) Also, one aspect of the present invention is a game system described in any one of Appendices G1 to G5, in which the characteristics associated with each of the characters for each user are based on items associated with each character.

[0380] According to the configuration of Appendix G6, the game system can set the priority of displaying effects based on the characteristics of the equipment item, so that equipment items with characteristics set to a high priority can be made to stand out, thereby motivating the user to obtain items with those characteristics.

[0381] (Appendix G7) Also, one aspect of the present invention is a game system described in any one of Appendices G1 to G5, wherein the characteristics associated with each of the characters for each user are based on the rarity of each character or an item associated with each character.

[0382] According to the configuration of appendix G7, the game system can prioritize the display of effects of characters or items with higher rarity. Therefore, for example, never-before-seen weapons or characters that seem to be highly rare can be made to stand out, and the user can be motivated to obtain those weapons or characters.

[0383] (Appendix G8) Also, one aspect of the present invention is a game system described in any one of Appendices G1 to G5, in which the characteristics associated with each of the characters for each user are based on time-limited effects set for each character or an item associated with each character.

[0384] According to the configuration of appendix G8, the game system can prioritize the display of special effects during a limited period when the special effects can be obtained. Therefore, for example, weapons or characters that are effective for a limited period can be highlighted, and the user can be motivated to obtain those weapons or characters.

[0385] (Appendix G9) Another aspect of the present invention is a program for causing a computer to function as a game system according to any one of appendices G1 to G8.

[0386] According to the configuration of appendix G9, the program limits the display of effects based on priority, so that the display of effects by multiple characters can be appropriately controlled. [Explanation of symbols]

[0387] 1 Game system, 10 Game device, 11 CPU, 12 Communication unit, 13 Input unit, 14 Display unit, 15 Memory unit, 30 Game server, 31 CPU, 32 Communication unit, 35 Memory unit, 110 Game control unit, 111 Server control information acquisition unit, 112 Character control unit, 113 Normal NPC control unit, 114 Battle control unit, 115 Display control unit, 310 Server control unit, 311 Terminal control information acquisition unit, 312 Boss NPC control unit, 313 Normal NPC state synchronization unit, 314 Player character synchronization unit, 315 Occupation determination unit, 316 Win / lose determination unit, 317 Reward grant unit, 351 User data storage unit, 352 Team data storage unit, 353 Character data storage unit, 354 Item data storage unit, 355 Possessive data storage unit

Claims

1. a character control unit that activates a character associated with each user information within a field common to the team based on an operation of each user identified by user information belonging to the team; a character state control unit that transitions the character in a first state to a second state in which the ability is lower than that of the first state, on condition that a predetermined first condition is satisfied for the character in the first state, and transitions the character in the second state to a third state in which operation of the character is disabled, on condition that a predetermined second condition is satisfied for the character in the second state; a resurrection control unit that resurrects the character in the second state to the first state based on another character that belongs to the same team as the character, and transitions the character in the third state to the first state on the condition that a predetermined third condition is satisfied after the character transitions to the third state; an NPC control unit that controls an NPC in the field; A battle control unit that controls attacks on the NPC based on an operation of each of the users; Equipped with The restoration control unit is When the character in the third state is to be transitioned to the first state, the transitioned character is placed at a predetermined location in a field; reviving the character in the second state to the first state at a location where the character in the second state is located based on at least a positional relationship with the character in the first state that belongs to the same team as the character; The second state is a state in which the character can move and fight, but has a lower attack power than the first state; The attack power is a first parameter indicating the magnitude of damage to an attack target, a second parameter that is decreased by an attack from the NPC is associated with the character; the first condition is satisfied when the second parameter of the character becomes a first predetermined value that is smaller than an initial value of the second parameter in the first state; the second condition is satisfied when the second parameter of the character becomes a second predetermined value that is smaller than an initial value of the second parameter in the second state; The character state control unit: When the character in the first state is transitioned to the second state, an initial value of the second parameter of the character is set to a value lower than the initial value of the second parameter in the first state and higher than the first predetermined value. Game system.

2. The game system according to claim 1 , wherein the third condition is satisfied when a predetermined time has elapsed.

3. moreover, The game system according to claim 1 , further comprising a win / loss determination unit that determines a win / loss of said team based on a result of an activity of said character caused by said character control unit.

Citation Information

Patent Citations

  • Game device, game programs

    JP2010207404A

  • Game control method, computer, and control program

    JP2015217266A

  • Game program

    JP2017064252A