WO2013031310A1

WO2013031310A1 - Game management device, game system, game management method, program, and recording medium

Info

Publication number: WO2013031310A1
Application number: PCT/JP2012/063275
Authority: WO
Inventors: 正能鈴木; 暢也北村; 雄大堤; 浩之冨田; 加藤　禎人
Original assignee: 株式会社コナミデジタルエンタテインメント
Priority date: 2011-08-31
Filing date: 2012-05-24
Publication date: 2013-03-07
Also published as: JP5080673B1; JP2013051994A; KR101489610B1; KR20130087571A

Abstract

A game management device, comprising: a continuous access reward granting means that grants a continuous access achievement reward to a user who has achieved continuous access; and a friend support access determination means that determines, for a user having a missing unit period during which there was no access among continuous unit periods, whether or not a friend of the user has fulfilled prescribed support access conditions. If the friend support access determination means determines that the friend has fulfilled the support access conditions, the continuous access reward granting means grants the continuous access achievement reward to the user, even if said user has a missing unit period.

Description

GAME MANAGEMENT DEVICE, GAME SYSTEM, GAME MANAGEMENT METHOD, PROGRAM, AND RECORDING MEDIUM

This application claims priority on the basis of Japanese Patent Application No. 2011-190164 filed on August 31, 2011, the entire contents of which are incorporated herein by reference.

The present invention relates to a game management device, a game system, a game management method, a program, and a recording medium that accept access via a network from a terminal device of each user who receives a game service and manage game information of each user. is there.

2. Description of the Related Art Conventionally, a game system in which a user can receive various game services provided from a game server by connecting the user's terminal device (personal computer, mobile phone terminal, etc.) to a game server installed on the Internet. There is.

Conventionally, in the game system as described above, a game system has been proposed in which a privilege is given to the user according to the user's access level to the game server in order to encourage the user to continue using the game service (Patent Document 1). reference).

By the way, in recent years, the game system is incorporated into a social networking service (SNS) system, which is a community-type service that promotes and supports the connection between people, and is provided as one of the SNS services. Games are prevalent. In such a social game, each user can become a friend with other users who use the game service, or points can be acquired by communicating with fellow users. It has become. Thus, in the social game, the interest of the game is enhanced by promoting communication between users.

And when providing a user with a game service such as the social game that places importance on the connections and exchanges between users, how to activate the game community is important in building a game system. Become an element.

However, as in the conventional game system, simply giving a privilege to the user according to the user's access level to the game server can sufficiently promote communication between users receiving the game service. It is not possible to connect to the activation of the game community.

JP 2003-144759 A

The present invention has been made in view of the above problems, and a game management device, a game system, a game management method, and a game management device that can provide highly interesting game services by activating the game community than before. The object is to realize a program and a recording medium.

A game management device according to one aspect of the present invention receives access via a network from a terminal device of each user who receives a game service, manages game information of each user, and provides each user with the game via the network. A game management device that provides a service, storing the access information of each user in a storage device, managing the access for each user, and all of the unit periods of a continuous specified number of periods Continuous access privilege granting means for changing a user's game information and granting a continuous access achievement privilege so as to be advantageous to the game for the user who has achieved the continuous access that has performed the access, and each user as a center Friend management means for storing information on fellow users belonging to a group in a storage device and managing fellow users for each user; Friend support access determination means for determining whether or not a fellow user of the user satisfies a predetermined support access condition for a user having a missing unit period that has not been accessed among the unit periods of the continuous specified number of periods. And. And the said continuous access privilege provision means is said that even if it is a user with the said missing | missing unit period among the said unit periods of the continuous regulation period number, if the fellow user of the said user satisfy | fills the said support access conditions, When the fellow support access determination means determines, the user is provided with the continuous access achievement privilege.

A game system according to another aspect of the present invention includes a terminal device of each user who receives a game service, receives access via a network from the terminal device, manages game information of each user, and transmits the network to each user. And a game management device configured as described above for providing the game service via the network.

According to still another aspect of the present invention, there is provided a game management method that accepts access from a terminal device of each user who receives a game service, manages game information of each user, and sends each user through the network. A game management method in a game management apparatus that provides the game service, wherein the game management apparatus stores information on the access of each user in a storage device, and manages the access for each user; The game management device changes the game information of the user so that it is advantageous to the game for the user who has achieved the continuous access who has made the access for all the unit periods of the continuous specified number of periods, and the continuous access The continuous access privilege granting step for granting the achievement privilege and the game management device are provided for each user. A friend management step for storing the information of fellow users belonging to a central group in a storage device and managing the fellows for each user, and the game management device accesses the continuous period of the unit period. A friend support access determination step for determining whether or not the fellow user of the user satisfies a predetermined support access condition for a user who has a missing unit period. And even if it is a user where the missing unit period exists among the unit periods of the continuous specified number of periods, the continuous access privilege granting step is performed when the fellow user of the user satisfies the support access condition. When the fellow support access determination step determines, the user is provided with the continuous access achievement privilege.

According to still another aspect of the present invention, there is provided a program for receiving access via a network from a terminal device of each user who receives a game service, managing game information of each user, and providing each user with the network via the network. An access management means for operating as a game management apparatus for providing the game service, wherein the computer stores the access information of each user in a storage device and manages the access for each user A continuous access achievement privilege is provided by changing the game information of the user so as to be advantageous to the game for a user who has achieved continuous access for all the unit periods of the number of continuous specified periods. Access privilege granting means, friends who belong to a group centered on each user The friend management means for storing the information in the storage device and managing the friend for each user, and the user who has the missing unit period that has not been accessed among the unit periods of the continuous prescribed period, This is to allow the user to function as fellow support access determination means for determining whether or not a predetermined support access condition is satisfied. And the said continuous access privilege provision means is said that even if it is a user with the said missing | missing unit period among the said unit periods of the continuous regulation period number, if the fellow user of the said user satisfy | fills the said support access conditions, If the fellow support access determining means determines, the computer is caused to function as the user providing the continuous access achievement privilege.

According to the present invention, it is possible to give each user the motivation to communicate with friends, thereby activating the entire game community. As a result, each user strengthens the connection and interaction between friends in the game, and further increases the interest and interest in the game, and provides a highly entertaining game service with continuity that users will never get tired of it can.

The game management device and the game system of the present invention may be realized by a computer. In this case, a program for realizing the game device on a computer by causing the computer to operate as the above-described means, and the program. A recorded computer-readable recording medium also falls within the scope of the present invention.

The objects, features and advantages of the present invention will become more apparent from the following detailed description and the accompanying drawings.

It is explanatory drawing which shows the structural example of the game system which concerns on one embodiment of this invention. It is a block diagram which shows an example of the hardware constitutions of a game management apparatus. It is a block diagram which shows an example of the hardware constitutions of a terminal device. It is a functional block diagram which shows an example of a functional structure of a game management apparatus. It is a functional block diagram which shows an example of a functional structure of a game information management means. It is explanatory drawing which shows an example of the game information which a game information management means preserve | saves and manages in a database server. It is explanatory drawing which shows an example of the information regarding each user's associate which a fellow information storage control part memorize | stores. It is explanatory drawing which shows the other example of the information regarding the friend of each user which a fellow information storage control part memorize | stores. It is explanatory drawing which shows the other example of the information regarding the friend of each user which a fellow information storage control part memorize | stores. It is explanatory drawing which shows the other example of the information regarding the friend of each user which a fellow information storage control part memorize | stores. It is explanatory drawing which shows an example of the access information of each user which an access information storage control part memorize | stores. It is explanatory drawing which shows the other example of the access information of each user which an access information storage control part memorize | stores. It is explanatory drawing which shows the other example of the access information of each user which an access information storage control part memorize | stores. It is explanatory drawing which shows an example of the screen for alert | reporting generation | occurrence | production of a privilege. It is explanatory drawing which shows the other example of the screen for alert | reporting generation | occurrence | production of a privilege. It is explanatory drawing which shows an example of the screen for alert | reporting that continuous access is continuing. It is explanatory drawing which shows the other example of the screen for alert | reporting continuing continuous access. It is explanatory drawing which shows an example of the received message information which a message storage control part memorize | stores. It is explanatory drawing which shows an example of a buddy list screen. It is explanatory drawing which shows the other example of a buddy list screen. It is a flowchart which shows an example of operation | movement of a game system. It is a flowchart which shows an example of a process when a user loses access. It is a flowchart which shows an example of generation | occurrence | production processing of the continuous access achievement privilege. It is a flowchart which shows an example of a game progress process. It is a flowchart which shows the other example of a process when a user loses access. It is a functional block diagram which shows the other example of a functional structure of a game management apparatus. It is explanatory drawing explaining an example of the access performance to a game server. It is explanatory drawing explaining the other example of the access performance to a game server. It is explanatory drawing explaining the other example of the access performance to a game server. It is a flowchart which shows the other example of a process when a user loses access. It is a functional block diagram which shows the other example of a functional structure of a game management apparatus. It is explanatory drawing which shows an example of the scheduled date information which a scheduled date information storage control part memorize | stores. It is explanatory drawing which shows an example of an inaccessible schedule notification screen. It is explanatory drawing which shows an example of the screen which displays friend's information. It is a flowchart which shows the other example of a process when a user loses access. It is a functional block diagram which shows the other example of a functional structure of a game management apparatus. It is a flowchart which shows an example of generation | occurrence | production processing of a support access privilege. It is a flowchart which shows an example of generation | occurrence | production processing of a fellow access privilege. It is a functional block diagram which shows the other example of a functional structure of a game management apparatus. It is explanatory drawing which shows an example of a friend candidate list screen. It is explanatory drawing which shows the other example of a buddy list screen. It is a functional block diagram which shows the other example of a functional structure of a game management apparatus. It is explanatory drawing which shows the other example of the information regarding the friend of each user which a fellow information storage control part memorize | stores. It is explanatory drawing which shows the other example of the information regarding the friend of each user which a fellow information storage control part memorize | stores. It is a flowchart which shows the operation example of the game server containing the provision adjustment process of a privilege. It is a flowchart which shows the other operation example of a game server including the provision adjustment process of a privilege. It is a flowchart which shows the other operation example of a game server including the provision adjustment process of a privilege.

Hereinafter, a game management device, a game management method, a program, and a recording medium according to an embodiment of the present invention will be described with reference to the drawings.

[Outline of the game system]
FIG. 1 shows a configuration example of a game system in which a game management device according to an embodiment of the present invention is incorporated. As shown in the figure, this game system includes a game server 1 installed on a network 4 such as the Internet, a database server 2 connected to be communicable with the game server 1, and a game server via the network 4. 1 and the terminal device 3 of each user that can be communicably connected.

The network 4 according to the present embodiment is not limited to the Internet. For example, as long as the game server 1 and the terminal device 3 of each user can be connected to each other so as to communicate with each other, for example, a dedicated line, a public line, etc. It may be a line (telephone line, mobile communication line, etc.), a wired LAN (Local Area Network), a wireless LAN, or the like, or a combination of the Internet and these.

In this example of the game system, the game management device according to an embodiment of the present invention includes a game server 1 and a database server 2. The game server 1 receives access from the terminal device 3 of each user who receives the game service via the network 4 and stores and manages game information of each user in the database server 2 (storage device). A game service is provided via the network 4.

In the present embodiment, an example of providing a so-called browser game in which a game can be played by a web browser installed in each user terminal device 3 will be described as one form of game service provided by the game server 1. In the service form for providing the browser game, it is not necessary to download or install software dedicated to the game on the user's terminal device 3, and the user can easily connect to the game server anywhere as long as the terminal device 3 can be connected to the network 4. The game service provided from 1 can be enjoyed.

In this game system, a program (application software) for a browser game is installed in the game server 1, and the game server 1 performs arithmetic processing and data for progressing the game in accordance with input operations on the terminal device 3 of each user. Execute the process. Then, the game server 1 updates the game information of each user in the database server 2 based on the execution result of the arithmetic processing and the like, and web page information for displaying the execution result on the screen of the user terminal device 3 (Game screen data) is transmitted to the terminal device 3 of each user.

Each user's terminal device 3 is equipped with a web browser having a website browsing function as a user agent so that the web page information transmitted from the game server 1 can be displayed on the screen of the terminal device 3. It has become. Examples of the terminal device 3 include a mobile phone terminal, a PHS (Personal Handy-phone System) terminal, a personal digital assistant (PDA), and a smartphone that is a mobile terminal in which a mobile phone and a mobile information terminal are integrated. Various terminals that can be connected to the game server 1 via the network 4 and receive a game service, such as a personal computer or a tablet computer, can be applied.

In addition, the game provided in the present embodiment has a so-called social game element that allows the user to play while communicating with other users who are receiving game services. For example, by incorporating the game server 1 and the database server 2 of the present embodiment into a social networking service (SNS) system, a game system that provides a social game service as one of the SNS services can be obtained. In this way, a game service can be provided to the user by a game system operating on the SNS platform, but the game server 1 and the database server 2 can be constructed as independent game systems without being incorporated into the SNS system. Good.

In this game system, each user can build a special relationship of “friends” with one or more other users who are receiving game services. And the user who made the friend can enjoy the various merit mentioned later. As one form for a user to become a friend with another user, either one of the two users makes a friend application to the other user via the game server 1, and the user who has received the friend application The friend application made between both users and the operation of the approval of approving becoming a friend via the game server 1 are mentioned. And the game server 1 memorize | stores in the database server 2 the information of the associate user who belongs to the group called the "companion" centering on each user, and performs the associate management for every user. Details of this friend application, its approval, and friend management by the game server 1 will be described later.

In this game system, for example, a predetermined period (for example, one day) in the real world is defined as a unit period, and a user who has made at least one access to the game server 1 within the unit period is given access within the unit period. Assume that the user has achieved. Then, the game server 1 achieves continuous access by changing the game information of the user so as to be advantageous to the game with respect to the user who has achieved access within the unit period for all the unit periods of the continuous specified period. A privilege is given, thereby promoting the continuous use of each user's game service.

The unit period is not limited to one day (24 hours) in the real world, and may be, for example, half a day (12 hours) or two days in the real world, and an arbitrary period can be set. . Moreover, the number of continuous specified periods (the number of continuous unit periods) can be arbitrarily set. For example, when the unit period is one day in the real world and the number of continuous specified periods is 10, a continuous access achievement privilege is granted to a user who has achieved continuous access for 10 days. For example, when a half day is a unit period and the number of consecutive specified periods is 10, at least once in the morning (from 0:00 to 12:00) and in the afternoon (from 12:00 to 24:00) A continuous access achievement privilege is given to a user who has achieved access to the game server 1 for five consecutive days.

In the embodiment described below, an example will be described in which the unit period is one day in the real world, the number of consecutive specified periods is five, and a continuous access achievement privilege is given to a user who has achieved five days of continuous access. .

The game server 1 grants a privilege that should not be granted to a user unless the user has achieved continuous access for five days, to a user who has not been able to achieve continuous access for five days under certain conditions. That is, even if the user cannot achieve continuous access for 5 days due to the absence of access (missing unit period) within 5 consecutive days, When a friend satisfies a predetermined support access condition, it is assumed that there is no missing day (that is, the user has also accessed the game on the missing day), and a privilege for continuous access for 5 days is given. It has a typical configuration. As a specific example, even if the user cannot access the game server 1 for one day due to something, the friend of the user is in the support access condition (e.g. %) (If the game server 1 is accessed by the game server 1), it is assumed that there is no missing day for the day, and if 5 days of continuous access is achieved including the compensation for this missing day. For example, the user is given a privilege of continuous access. In addition, a user's fellow support access condition, the specific example of a privilege, etc. are mentioned later.

This characteristic configuration of the present embodiment has an advantage for the user himself / herself by maintaining a high access frequency such that the user's companion satisfies the support access condition, and conversely, the user himself / herself also maintains a high access frequency. If you do, you can indirectly support other friends. Thereby, each user is given the consciousness and motivation to increase the access frequency with each other. Each user is motivated to communicate with each other in an attempt to increase the frequency of access to the game of the entire group (access to the game server 1). It becomes possible to plan. The activation of the entire game community is an important element for realizing highly interesting social games, etc., and each user strengthens the connection and interaction between friends in the game, and thus interest and interest in the game. Result. Therefore, this game system can provide a game service having continuity that does not get tired for the user.

Hereinafter, the details of the configuration of the game management device according to the present embodiment, which can activate the entire game community as described above, will be described.

[Configuration of game management device]
As described above, in the present embodiment, the game management device includes the game server 1 and the database server 2. FIG. 2 shows an example of the hardware configuration of the game server 1. As shown in the figure, the game server 1 mainly includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12 and a RAM (Random Access Memory) 13 as a main storage device, and an auxiliary storage device 14. The communication control unit 15 and the input / output control unit 16 are connected to each other via a bus line 17 including an address bus, a data bus, a control bus, and the like. Note that an interface circuit is interposed between the bus line 17 and each component as necessary, but the illustration of the interface circuit is omitted here.

The CPU 11 interprets and executes instructions of application software such as system software and game programs, and controls the game server 1 as a whole. The ROM 12 stores a program and the like necessary for basic operation control of the game management device 1. The RAM 13 stores various programs and data, and secures a work area for the CPU 11.

The auxiliary storage device 14 is a storage device that stores application software such as a game program, various data, and the like. For example, a hard disk drive can be used as the auxiliary storage device 14. The program according to the present embodiment for causing the game server 1 (computer) to operate as a game management device is also stored in the auxiliary storage device 14, and the program is transferred from the auxiliary storage device 14 to the bus line when the game server 1 is started. 17 is loaded into the RAM 13 via the CPU 17 and executed by the CPU 11.

The communication control unit 15 includes a communication interface 15 a connected to the network 4, and controls communication with each user terminal device 3 via the network 4. The communication control unit 15 also controls communication with a server (not shown) connected to the network 4. For example, when it is set as the system configuration which incorporated the game server 1 in SNS, the communication control part 15 of the game server 1 controls communication with the SNS server which is not illustrated via the network 4. FIG.

The input / output control unit 16 is communicably connected to the database server 2 and is a database interface that performs input / output control when the CPU 11 executes reading / writing of data (records) with respect to the database server 2.

The database server 2 includes a large-capacity hard disk device having, for example, a RAID (Redundant Arrays of Inexpensive Disks) configuration as a storage device having an area for storing game information of each user managed by the game server 1. The database server 2 stores various game information (user name, level, in-game points, possessed items, etc.) of each user in association with identification information (user ID) for uniquely identifying each user, for example. It can be constructed as a database, an object database, an object relational database, or the like.

In the present embodiment, an example in which the game management device is configured by the game server 1 and the database server 2 is shown, but the present invention is not limited to this. For example, the game server 1 can have the function of the database server 2 and the game management device can be configured only by the game server 1. Further, the game server 1 can be configured as a plurality of servers by distributing the functions of the game server 1 to a plurality of servers. For example, when a user operates the terminal device 3 to access the game server 1, an authentication server having an authentication function for determining whether the user is a legitimate user is provided separately from the main server of the game server 1, The game server 1 may be composed of a main server and an authentication server. As another configuration example, a billing management server that performs billing management when a user purchases an item to be billed in a game is provided separately from the main server of the game server 1, and the main server, authentication server, and billing management The game server 1 may be configured by a server.

In addition, when the number of users who use this game service reaches several hundred thousand, millions, or more, it is required to construct a server system that can withstand huge access from the terminal device 3 of many users. Therefore, by providing a plurality of game servers 1 on the network 4 for redundancy (multiplexing), a load distribution type system configuration may be adopted. In this case, it is desirable to provide a load balancer for adjusting the load among the plurality of game servers 1.

Next, the configuration of the terminal device 3 of the user who accesses the game server 1 according to the present embodiment and receives a game service will be described.

[Configuration of terminal device]
As the terminal device 3 operated by the user, various terminals having a website browsing function such as a mobile phone terminal and a smartphone can be applied as described above, but in the present embodiment, a mobile phone terminal is exemplified. The configuration will be described. Note that the terminal device 3 other than the mobile phone terminal is also basically required for playing a game such as displaying a game screen using a website browsing function or performing an input operation for executing the game. The configuration is the same as that of the mobile phone terminal.

A mobile phone terminal having a website browsing function or the like is also called a feature phone or a smart phone, and FIG. 3 shows a configuration example thereof. As shown in the figure, the terminal device 3 mainly includes a CPU 31, a ROM 32 and a RAM 33 as main storage devices, an image processing unit 34, a display unit 35, a sound processing unit 36, and an audio input unit 37. , An audio output unit 38, an auxiliary storage device 39, an operation input unit 40, and a communication control unit 41. The components 31 to 34, 36 and 39 to 41 are connected to each other via a bus line 42. Has been. An interface circuit is interposed between the bus line 42 and each component as necessary, but the interface circuit is not shown here.

The CPU 31 interprets and executes commands of various programs including the web browser, and controls the terminal device 3 as a whole. The ROM 32 stores a program and the like necessary for basic operation control of the terminal device 3. The RAM 33 stores various programs and data loaded from the ROM 32 or the auxiliary storage device 39, and secures a work area for the CPU 31. A web browser that displays game screen data described in HTML or the like is stored in the ROM 32 or the auxiliary storage device 39, loaded into the RAM 33, and executed by the CPU 31. Various plug-in software for extending the browser function of the web browser may be stored in the ROM 32 or the auxiliary storage device 39 together with the web browser.

The image processing unit 34 drives the display unit 35 based on an image display command from the CPU 31 to display an image on the screen of the display unit 35. Various known display devices such as a liquid crystal display and an organic LE (Electro-Luminescence) display can be applied to the display unit 35.

The sound processing unit 36 converts an analog audio signal into a digital audio signal when audio is input from the audio input unit 37, generates an analog audio signal based on a sound generation instruction from the CPU 31, and outputs it to the audio output unit 38. Output. The voice input unit 37 includes a microphone built in the terminal device 3 and is used for telephone communication or recording. The voice output unit 38 is composed of a speaker that outputs a reception speaker at the time of telephone communication and a telephone ringtone or a sound effect at the time of game execution.

The auxiliary storage device 39 is a storage device that stores various programs and data. As the auxiliary storage device 39, for example, a flash memory drive or the like can be used as the internal memory of the mobile phone terminal, and a memory card reader / writer or the like can be used as the external memory of the mobile phone terminal.

The operation input unit 40 accepts a user's operation input and outputs an input signal corresponding to the operation input to the CPU 31 via the bus line 42. Examples of the operation input unit 40 include physical buttons such as a direction instruction button, a determination button, and an alphanumeric character input button provided on the main body of the terminal device 3. Further, in the case of the terminal device 3 in which the display unit 35 is configured as a so-called touch screen by mounting a touch panel (contact input type interface) on the screen of the display unit 35, the touch panel also becomes the operation input unit 40.

The communication control unit 41 includes a communication interface 41a, and has a communication control function for data communication when a game is operated, a communication control function for transmitting and receiving voice data as a mobile phone terminal, and the like. Here, for the communication control function for data communication, for example, a wireless LAN connection function, an Internet connection function via a wireless LAN or a cellular phone network, a predetermined frequency band (for example, a 2.4 GHz frequency band) is used. Includes short-range wireless communication functions. The communication control unit 41 transmits a connection signal for connecting the game apparatus 1 to a wireless LAN, the Internet, or the like based on a command from the CPU 31 and receives information transmitted from the communication partner side and supplies it to the CPU 31. To do.

In addition, the terminal device 3 may further include a GPS (Global Positioning System) signal receiving circuit, an imaging device (camera) such as a CCD (Charge Coupled Device) image sensor, a triaxial acceleration sensor, and the like. For example, GPS position information may be used in the game.

In the terminal device 3 configured as described above, a user who wants to receive a game service starts up a web browser and performs an operation of accessing a game site managed by the game server 1. When this access is authenticated by the game server 1, the communication control unit 41 of the terminal device 3 receives game screen data described in HTML or the like transmitted from the game server 1, and the CPU 31 executes the web browser. A game screen is displayed on the display unit 35. Here, the user selects and inputs selectable button objects and hyperlinks displayed on the game screen by operating the operation input unit 40. In response to this selection input, the game server 1 advances the game and transmits new game screen data to the terminal device 3. Then, this new game screen is displayed on the display unit 35 of the terminal device 3. Hereinafter, similarly, the user can select a button object or the like that can be selected on the game screen displayed on the display unit 35 by an operation. A game provided by the game server 1 can be played.

[Functional configuration of game management device]
Next, main functions of the game management device (game server 1 and database server 2) configured as described above will be described. FIG. 4 is a main functional block diagram of the game management device.

The game management device mainly includes game information management means 51, game progress means 52, fellow management means 53, authentication means 54, access management means 55, fellow support access determination means 56, continuous access privilege grant means 57, and notification means 58. And message transmission means 59. Each of these means 51 to 59 is realized by the CPU 11 of the game server 1 executing the program according to the present embodiment.

The game information management means 51 accumulates and manages the game information of each user in the database server 2. The items of game information managed by the game information management means 51 differ depending on the content of the game service that the game server 1 provides to the user.

Examples of games provided by the game server 1 include sports games based on various sports such as baseball, soccer, and golf, battle games based on battles, music simulation games, and other various role-playing games and training. Various games such as games and simulation games can be listed regardless of the game format and genre. As an example, in the present embodiment, the case where the game server 1 provides a baseball game as a game service will be described below.

In this embodiment, a baseball game in which a user owns a player character in the game and can play a game (match) with another user in the game using the player character is taken as an example. The player character owned by the user can be in a card format in which the form of the player character is visible on the screen of the terminal device 3. That is, the player character is managed by the game server 1 as a digital player card and displayed on the screen of the user terminal device 3. FIG. 10A illustrates a player card 71 displayed on the screen of the user's terminal device 3, and the form of the player character and the rareness of the card (the value of the scarce value is indicated by the number of ☆). Is displayed on the screen as a digital player card. The user can collect player cards while proceeding with the game, form his own original team, and compete with other users for ranking. In addition, the user can improve the ability of the player card (player character) by synthesizing the collected player cards (that is, nurture the player), and can enjoy the game with the aim of creating a stronger team. It can be done.

In such a baseball game, as shown in FIG. 5, the game information management means 51 for managing the game information of each user includes a user information storage control unit 51a, a level information storage control unit 51b, and an owned player card storage control unit 51c. , Owned point storage control unit 51d, owned coin storage control unit 51e, owned item storage control unit 51f, game result storage control unit 51g, ranking storage control unit 51h, privilege information storage control unit 51i, demerit information storage control unit 51j, etc. I have. FIG. 6 shows an example of game information of each user (in this example, one user ID = “000001”) that is stored and managed in the database server 2 by each storage control unit 51a to 51j of the game information management means 51. Game information).

The user information storage control unit 51a associates a user ID uniquely identifying each user with user information related to each user such as a login ID, password, user name (such as a nickname used in the game), team name, and the like. Each user ID is stored in a predetermined storage area of the database server 2. Here, the login ID and password are used for login authentication when each user operates the terminal device 3 to access the game server 1. The user name and team name are arbitrary information set by the user when the user registers as a member for receiving the game service or when the game is executed for the first time. The user name and team name are displayed on the game screen as necessary.

The level information storage control unit 51b stores level information such as the user level and the league level in a predetermined storage area of the database server 2 for each user ID in association with the user ID. In this baseball game, for example, experience values are accumulated as the user progresses the game, and the level of the user is increased when the experience value reaches a certain amount. Moreover, in this baseball game, for example, there are a plurality of different levels of leagues, and each user's team belongs to one of the leagues, and a game (league battle) is automatically played with another user's team in the league. To do. Moreover, according to the result of this league game, the replacement game between the teams of the users belonging to different leagues is automatically executed, and the league level to which the user's team belongs changes. The level information storage control unit 51b stores the user level and the league level in association with the user ID.

The owned player card storage control unit 51c stores information on player cards acquired and owned by the user in the game in a predetermined storage area of the database server 2 for each user ID in association with the user ID. Examples of the player card information include identification information (player card ID) for uniquely identifying the player card, an ability value indicating the height of the ability of the player, and a regular player flag.

FIG. 6 shows an example in which player ability values can be set for three ability items (abilities 1 to 3). As an example of the ability item, when the player card is a fielder, abilities 1 to 3 can be “blow”, “running power”, “defense”, etc., and when the player card is a pitcher, ability 1 ~ 3 can be set as "sphere", "control", "change", etc. The capability item is not limited to this example, and can be increased or decreased. A regular player flag is a regular player (player included in a team order) who participates in a match with another user's team among player cards owned by the user, or a non-regular player. This flag is “1”, indicating that it is registered as a player card for a regular player. By operating the terminal device 3, the user can select a regular player from an owned player card or set a team order.

Further, the database server 2 stores the player card image data, the player name, the position, the affiliation team, the ability value (initial value not strengthened by the synthesis) and the like in association with the player card ID. There is a database, and the game information management means 51 can acquire image data of a player card corresponding to the player card ID based on the player card ID stored in the owned player card storage control unit 51c. ing.

The owned point storage control unit 51d associates various points owned by the user in the game (including values corresponding to points) in a predetermined storage area of the database server 2 for each user ID in association with the user ID. Remember. In this game, there are various game modes, and various points can be acquired and the acquired points can be used according to the game mode.

As shown in FIG. 6, examples of the points include behavioral points, operating costs, reinforcement points, ale points, etc., in addition to the above experience values. The action power point is used in a “scout mode” in which the player card is searched and the player is scouted while consuming the action power point. The operation cost is used in the “match mode” in which an individual match is designated by specifying another user, and the individual match is performed at a cost (point) necessary for managing the match. It is consumed by. For example, behavioral power points and operating costs that are consumed and reduced during a game are recovered over time (for example, 1 point is recovered every 3 minutes), or the experience value is set to a certain amount. It can be recovered by reaching the user level.

Further, the strengthening points are used in the “strengthening mode” in which the ability of the player cards is improved by combining the player cards owned by the user, and is consumed by performing the combining. This strengthening point can be acquired, for example, by executing a scout mode or a match mode. In addition, the ale point is a point that can be acquired when a user sends a message or the like to another user to support (send an ale). This ale point can be used in, for example, “player lottery acquisition mode” in which a predetermined number (for example, one) of player cards can be acquired by lottery based on random numbers, etc., from all player cards managed by the game server 1 It is possible to receive one player card lottery for a predetermined ale point.

The owned coin storage control unit 51e associates the user ID with the coin owned by the user in the game (in-game currency different from the points) in a predetermined storage area of the database server 2 for each user ID. To remember. This coin is necessary, for example, when acquiring an item to be charged.

The owned item storage control unit 51f stores the item acquired by the user in the game in a predetermined storage area of the database server 2 for each user ID in association with the user ID. As shown in FIG. 6, examples of items include recovery items, puzzle card pieces, and fake cards. The recovery item is an item that recovers the above-described action power points and / or operation costs consumed and reduced during the game to the maximum value in an instant without waiting for the passage of time. For example, the recovery item can be acquired by consuming and purchasing the coin or satisfying a predetermined bonus condition in the game.

A puzzle card piece is an item that can be obtained a powerful (high ability) player card by collecting a predetermined number of pieces (for example, six pieces P1 to P6) and completing the puzzle card. . For example, a piece of a puzzle card can be obtained when a lottery based on a random number or the like is won at the time of executing the scout mode, and when the player wins by fighting with a piece owned by another user in the game mode In addition, it can be taken from the user of the opponent.

A fake card is an item that can be set only on a piece of the puzzle card so that even if it is defeated by another user in a match in the game mode, the targeted piece is not taken away only once. For example, a fake card can be obtained by consuming and purchasing the coin or satisfying a predetermined bonus condition in the game.

The game result storage control unit 51g associates a user ID with a game ID for uniquely identifying a game in which the user's team has played against another user's team, for each user ID. Store in the area. Here, the game uniquely specified by the game ID includes a game of an individual game performed by the user specifying an opponent and a game of a league game automatically performed by the game server 1.

Further, the database server 2 is associated with the game ID, the game date and time (real world game start or end time), the user ID of the winning team, the user ID of the defeated team, the battle score, the winning pitcher character, A game database is stored in which information about game results such as a loser pitcher character, a player character who has made a home run, and game critical information is stored. And the game information management means 51 can acquire the information regarding the game result corresponding to the said game ID from a game database based on the game ID which the game result memory | storage control part 51g has memorize | stored.

The ranking storage control unit 51h associates the user ID with ranking information such as the ranking in the affiliation league based on the number of wins and defeats of the user's team and the number of wins / defeats in the league match or replacement match, Each user ID is stored in a predetermined storage area of the database server 2. For example, a league game is automatically performed at a predetermined time on each day from Monday to Friday in the real world (for example, 12 games per day), and a replacement game is performed at a predetermined time on Saturday and Sunday in the real world. It is assumed that a predetermined number of games (for example, 12 games each day) are automatically played. In this case, as shown in FIG. 6, the ranking storage control unit 51h stores the ranking information for each day from Monday to Sunday in the real world, and updates the ranking information to the latest information every week.

The privilege information storage control unit 51i stores information related to the privilege granted to the user in a predetermined storage area of the database server 2 for each user ID in association with the user ID. The privilege in this Embodiment is provided with respect to the user who achieved the continuous access for 5 days as mentioned above. Giving a privilege here means making the game more advantageous (merit occurrence state) than before giving the privilege. In FIG. 6, bonus points (in this example, 200 points of strengthening points) are given. The example given to the user as a privilege is shown. Details of this privilege will be described later.

Next, the game progress means 52 shown in FIG. 4 will be described. The game progress means 52 executes a game in response to an operation on the terminal device 3 by the user, generates game screen data corresponding to the execution result, and transmits the game screen data to the terminal device 3. It has a function to advance the game by displaying a game screen according to the game. As shown in FIG. 4, the game progress means 52 includes a game execution means 52a, a game screen generation means 52b, and a game screen transmission means 52c.

When the game screen is displayed by the web browser of the terminal device 3 of the user, when the user performs an operation of selecting a selectable button object or hyperlink on the game screen, a request for the game screen corresponding to the operation is performed. Is transmitted to the game server 1 by the web browser of the terminal device 3. In the game server 1 that has received this request, the game execution means 52a reads the user's game information in response to the request and executes the game by performing calculations and data processing.

For example, in the case where the user performs an operation of playing against another user's team in the battle mode, the game execution means 52a is configured so that the player cards of both teams corresponding to the user IDs of the two users performing the battle. Information (player card information of regular players participating in the game) is read from the database server 2. And the game execution means 52a performs the calculation which determines a win / loss based on the ability value etc. of the player card of both teams. As an example of the calculation of this win / loss decision, the player with the highest total ability value of both teams may be the winning team, or the team with the higher total ability value will have a higher probability of winning. The winning team may be obtained by probability calculation. Moreover, the game execution means 52a performs the calculation which determines whether various effect productions which affect a win / loss are generated based on the combination of the player card which comprises a team before the calculation which determines a win / loss. May be.

The game screen generation means 52b generates game screen data composed of HTML data, for example, according to the execution result by the game execution means 52a. The HTML data may include image data such as a player card read from the database server 2. Moreover, the script (program) which operate | moves by the plug-in of the web browser of the terminal device 3 may be embedded in HTML data.

The game screen transmission unit 52c transmits the game screen data (HTML data or the like) generated by the game screen generation unit 52b to the user terminal device 3 as a response to the request for the game screen. In the terminal device 3 of the user who has received the game screen data, the game screen is displayed on the display unit 35 by the web browser.

Next, the fellow management means 53 will be described. The fellow management means 53 has a function of storing fellow user information belonging to a group called a fellow centered on each user in the database server 2 (storage device) and performing fellow management for each user. In addition, the group here shows the group of one's friend seen from the viewpoint of one user to the last, and each user who comprises these groups does not belong only to this group. Each user also has a group of “buddies” centered on him / herself. The fellow management means 53 includes a fellow information storage control unit 53a.

FIG. 7A shows an example of information related to each user's associate, which the associate information storage control unit 53a stores and manages in the database server 2. The buddy information storage control unit 53a receives the information on the limit number of buddy, the user ID of a buddy user who is already in a buddy relationship, the user ID of a buddy application user, and the buddy application in association with the user ID. However, the information regarding associates, such as user IDs of unapproved users, is stored in a predetermined storage area of the database server 2 for each user ID. In the example of FIG. 7A, information related to one user with the user ID = “000001” is shown, the number of associates is 20, the number of associate users of the user is 10, and the number of users who are applying for associates is one. The number of unapproved users who have received peer applications is zero.

In the baseball game of the present embodiment, by creating a friend, bonus points are awarded to both users who have become friends (for example, increasing the maximum value of the action power point and the operating cost by a predetermined point). Is possible). Moreover, it is the game specification which can advance a game advantageously by playing a game in cooperation with a fellow user or performing a present or support of a player card between friends. In this way, making a friend is promoted by giving the user the merit of making a friend in the game. However, for each user, a limit number of friends according to the degree of progress of the game (upper limit number of people who can make friends) is set, and the friend information storage control unit 53a associates the user ID with the friend limit. I remember the number. For example, the limit number of friends is set to increase as the level of the user increases. Thereby, in order to make more friends and make the game advantageous, the user is given a motivation to continuously advance the game and improve the level.

In this embodiment, in order for two users to become friends, either one of both users makes a friend application to the other user via the game server 1. As an operation example of this friend application, first, a user who wants to make a friend performs an operation of listing target candidates of friend candidates on the screen of the terminal device 3. In response to the operation by the user, the game server 1 transmits screen data listing the candidates for the fellow candidates, so that a plurality of fellow candidates are listed, for example, as shown in the screen example of FIG. A screen is displayed on the user terminal device 3. Here, the user confirms the user level, the league level, and the like of the target person listed on the screen, selects a user who wants to be a friend, and performs a friend application operation. Details of the fellow candidate list screen in FIG. 26 will be described later.

For example, consider a case where a user A with a user ID = “000001” performs a friend application operation on a user B with a user ID = “000002”. As shown in FIG. 7A, in response to this operation, the fellow information storage control unit 53a of the game server 1 associates with the user ID of the user A = “000001” as the game information of the user A who made the peer application. , The user ID of the user B who is an applicant = “000002” is stored as the “user ID under application”.

Furthermore, as shown to FIG. 8A, the associate information storage control part 53a matches the user ID of the said user B = "000002" as the game information of the user B who is an applicant, and made the associate application. A's user ID = “000001” is stored as “unapproved user ID”. Then, the game server 1 notifies the user A that there has been a friend application when the terminal device 3 of the user B logs into the game server 1.

And the user B who received the friend application checks the information such as the user level and the affiliation league level of the user A received from the game server 1 on the screen of the terminal device 3 and decides whether to approve or reject as a friend. Perform the operation to select. Here, when the user B performs an operation of approving as a friend, the friend management means 53 of the game server 1 establishes a friendship relationship between the user A and the user B in accordance with this operation, and both users A and B are established. Register as a friend. That is, as shown in FIG. 7B, as the game information of user A, the user ID of user B = “000002” is stored in association with the user ID of user A = “000001” as the “friend user ID”. The user ID of user B is deleted from “user ID under application”.

Further, as shown in FIG. 8B, the fellow information storage control unit 53a stores the user ID of the user A = “000001” as “a fellow user ID” in association with the user ID of the user B = “000002”. , The user ID of the user A is deleted from the “unapproved user ID”. Then, when the user A's terminal device 3 logs in to the game server 1, the game server 1 notifies the user B that the friend has been approved.

Next, the authentication unit 54 will be described. When a user who wants to receive a game service operates the terminal device 3 to access (log in) the game server 1, the authentication unit 54 determines whether the user has a game participation qualification and performs login authentication. . An example of this authentication is authentication based on a login ID and password associated with a user ID. For example, when the user uses the game service for the first time, a login ID (any alphanumeric character, email address, etc.) and password are registered in the game server 1 as member information. Then, when logging in to the game server 1 from the next time, the user operates the terminal device 3 to transmit the login ID and password to the game server 1. At this time, the authentication means 54 of the game server 1 determines whether or not the combination of the login ID and password received from the user terminal device 3 has been registered, and performs login authentication.

When the game system is incorporated into the SNS system, the SNS member registration information (login ID and password) may be used as registration information for receiving the game service of the game system. For example, when the user's terminal device 3 is logged in to the SNS server, when the game site managed by the game server 1 is first accessed, the user's login ID and password are automatically input from the SNS server to the game server 1. It may be transferred so that the user can register to use the game service without registering the login ID and password again.

In addition, an individual identification number of a mobile phone terminal that is the terminal device 3 (a mobile phone terminal different from the phone number is uniquely specified) so that the user can save the trouble of inputting a login ID and a password each time the user accesses the game server 1. Or a unique ID of the contractor (ID for uniquely identifying the contractor of the mobile phone terminal, which is not changed as long as the contractor is the same even if the model is changed) You may perform authentication using. That is, when the user registers the member by operating the mobile phone terminal, the game server 1 acquires the individual identification number or the contractor specific ID included in the data transmitted from the mobile phone terminal, and the login ID and password At the same time, the individual identification number or the contractor unique ID is also stored in the database server 2 in association with the user ID. Then, when receiving an access request from the mobile phone terminal, the authentication unit 54 performs login authentication by determining whether the individual identification number or the contractor unique ID has been registered. Thereby, when accessing the game server 1, the user can log in without inputting the login ID and password.

As another method that can save the user the trouble of inputting the login ID and password each time the game server 1 is accessed, there is a method of using HTTP cookie information (hereinafter referred to as cookie). That is, when the user operates the terminal device 3 to register as a member, the game server 1 issues individual identification information corresponding to the login ID and password and registers it in the database server 2, and the individual identification information is used as a cookie. It transmits to the terminal device 3. At this time, the browser of the terminal device 3 stores the received cookie in the terminal device 3. When accessing the game server 1 from the next time, the browser of the terminal device 3 transmits a Cookie to the game server 1 together with a page browsing request, so that the authentication unit 54 receives the access request from the mobile phone terminal. Can perform login authentication by determining whether or not the individual identification number of the cookie has been registered.

Next, the access management means 55 will be described. The access management means 55 stores access information of each user to the game server 1 in the database server 2 (storage device) and manages access for each user. Here, the access information is information such as the access history (access date and time) of each user, the number of accesses in the real world per day, the presence / absence of access in each day in the real world, and the like.

The access management means 55 has a function of managing the presence / absence of access to the game server 1 for each predetermined unit period for each user. The management information on the presence / absence of access for each predetermined unit period is a continuous access privilege granting unit 57 that grants a continuous access privilege to a user who has achieved continuous access who has accessed all of the unit periods of the specified number of consecutive periods. Used to determine whether continuous access has been achieved. In this embodiment, the access management means 55 manages the presence / absence of access for each predetermined unit period for each user. However, the access management means 55 stores only the date and time of access of each user. However, the continuous access privilege granting unit 57 may determine whether or not there is access for each predetermined unit period.

In the following description, the access management means 55 of the present embodiment uses one day in the real world as a unit period, and indicates whether or not the game server 1 is accessed each day (whether access has been made at least once a day). An example of managing whether or not) for each user will be described.

FIG. 9A shows an example of access information of each user that is stored and managed in the database server 2 by the access information storage control unit 55a. The access information storage control unit 55a is associated with the user ID, and in the real world today, 1 day ago, 2 days ago, 3 days ago, 4 days ago, ..., n days ago (in this embodiment, n is 5 or more Information indicating whether or not the game server 1 is accessed for each day (whether or not access within the unit period has been achieved) is stored in a predetermined storage area of the database server 2 for each user ID. When this information is “1”, it indicates that the game server 1 has been accessed at least once a day, while when this information is “0”, the game server 1 is accessed once a day. Indicates that there was no access. In the example of the present embodiment, a privilege is given by continuous access for 5 days, so it is only necessary to store information indicating the presence / absence of access for the most recent 5 days up to the previous day.

The access information stored in the access information storage control unit 55a is not limited to the example in FIG. 9A. For example, as shown in FIG. 9B, today, 1 day before, 2 days ago,. The number of accesses to the game server 1 for each day n days ago may be used. This access count information is used to manage whether or not access within a unit period (at least one access per day in this embodiment) is achieved depending on whether or not the information is “0”. Information.

Further, the access information storage control unit 55a stores information indicating whether or not the user's associate satisfies the support access condition in a predetermined storage area of the database server 2 for each user ID in association with the user ID. This information is information indicating the determination result by the fellow support access determination means 56 described later.

Further, the access information storage control unit 55a also stores in the predetermined storage area of the database server 2 for each user ID, in association with the user ID, the continuous access days that are the continuous days that the user has accessed the game server 1. The number of consecutive access days is the date when the user accesses the game server 1 and the date when the user is regarded as accessed (the same day as the missing date that the user did not access). The number of consecutive days) counted. This number of consecutive access days is initialized (reset) when continuous access by the user (including a case where access is considered to be interrupted) stops and when a privilege is given to the user by achieving continuous access for 5 days. .

For example, if the missing day that can be compensated is only one day among the five consecutive days, even if the continuous access continuation state is maintained by satisfying the support access condition for the missing day on the first day, two days thereafter When the missing date of the eyes is determined, the continuous access days are initialized. That is, assuming that the missing date that can be compensated is n days, when the missing date on the (n + 1) th day is determined, the continuous access is interrupted at that time, and the continuous access days are initialized.

∙ The number of missing days that can be compensated can be set arbitrarily. However, if too many missing days that can be compensated are allowed, even if the user himself / herself does not access the game server 1 in fact, there is a possibility that the missing days are compensated and a continuous access achievement privilege is obtained. Therefore, it is desirable to set an upper limit for missing dates that can be compensated. In this embodiment, first, an example in which a missing date that can be compensated is limited to one day will be described below, and a case where a plurality of missing dates that can be compensated are allowed will be described later.

Next, the fellow support access determination means 56 will be described. The fellow support access determination means 56 determines whether or not the fellow user of the user satisfies a predetermined support access condition for a user who has a missing date that has not accessed the game server 1 for five consecutive days. It has the function to do.

Here, various arbitrary conditions can be set as support access conditions. As an example of the support access condition, “the ratio of the fellow users who have accessed the game server 1 at least once on the same day as the missing date to the whole fellow users is equal to or more than a threshold value” can be set. When the number of fellow users including the user himself is x and the number of fellow users who have accessed the game server 1 at least once on the same day as the missing date is y and the threshold is z, “y / x ≧ z” is satisfied. It becomes support access condition. For example, when the threshold is set to 0.8 (80% as a percentage), if eight or more fellow users among the ten fellows including the user themselves are accessing the game server 1, this support access condition is satisfied. .

Here, as described above, a fellow user is a user who belongs to a group called a friend centered on each user, and basically, the user who forms the center of the group is also included in the fellow user. However, since the user himself / herself does not access the missing date, the user may be excluded from the fellow user, and the percentage of fellow users who accessed on the same day as the missing date may be calculated. That is, “y / (x−1) ≧ z” may be set as the support access condition.

When the number of friends is large, there is no significant difference between “y / x ≧ z” or “y / (x−1) ≧ z” as the support access condition, but the difference is as the number of friends decreases. Becomes prominent. For example, considering the case where there are four fellow users x including the user and the threshold value z = 0.8, the user himself / herself does not access when “y / x ≧ z” is satisfied. Even if all three fellow users have accessed, y / x = 3/4 = 0.75, which does not satisfy the condition. On the other hand, when “y / (x−1) ≧ z” is a condition, y / (x−1) = 3/3 = 1.00 satisfies the condition if three people except the user access. End up. That is, when “y / x ≧ z” is satisfied, if the number of fellow users x including the user is four or less, the condition is never satisfied, while “y / (x−1) ≧ z” is satisfied. When the condition is satisfied, even when x is 4 or less, the condition is easily satisfied by the access of a small number of fellow users. By satisfying the condition of “y / x ≧ z”, in order to satisfy the support access condition, first, the number of fellow users x must be five or more, and the user tries to make at least five fellows. You will be motivated. In addition, by setting “y / x ≧ z” as a condition, it is possible to avoid a state where the condition can be easily satisfied when the number of friends is small. Therefore, it can be said that it is more preferable to set “y / x ≧ z” as a support access condition than “y / (x−1) ≧ z”.

As another example of the support access condition, “the number of fellow users who accessed the game server 1 at least once on the same day as the missing date is equal to or greater than a threshold (for example, 10 people)”. In the case of this support access condition, if the total number of users of the user is less than the threshold, the condition is not satisfied. Therefore, the user is given the motivation to make at least a threshold (for example, 10 people) or more so as to satisfy the support access condition. In addition, since it becomes easier to satisfy the support access condition when making more friends, the user is motivated to make more friends in order to satisfy the support access condition more easily. Further examples of support access conditions will be described later.

The process for determining whether or not the support support condition is met by the fellow support access determination means 56 is after 12:00 pm (24:00) when the presence / absence of access by the user is confirmed, that is, at a predetermined time on the day after the user's missing date. Done. For example, the determination process by the fellow support access determination unit 56 is performed at 0:00 on the day after the missing day.

Further, as shown in FIG. 9A, the determination result by the fellow support access determination means 56 is stored in association with the user ID of the user as 1-bit information indicating whether or not the user's friend satisfies the support access condition. Is done. When this information is “1”, it indicates that the friend of the user satisfies the support access condition, while when this information is “0”, it indicates that the support access condition is not satisfied. In the present embodiment, since the missing date that can be compensated for in the continuous five days is only one day, only the missing date on the first day is determined by the fellow support

access determining means

56, and 2 The determination process is not performed for missing days. The information is “0” even when the determination process by the fellow support access determination unit 56 is not performed as in the case where the user accesses (the day that is not the missing date) or the missing date corresponds to the second day. It becomes.

As a result of the determination by the fellow cheering access judging means 56, when the user's fellows satisfy the cheering access conditions, it is considered that the continuous access to the game server 1 by the user is continued, and the “continuous access days shown in FIG. "Is incremented by one.

Next, the continuous access privilege giving means 57 will be described. The continuous access privilege giving means 57 has a function of changing the game information of the user to give a continuous access achievement privilege to the user who has achieved continuous access for 5 days so as to be advantageous to the game. Furthermore, the continuous access privilege granting means 57 is also connected to the fellow cheering access if the fellow user of the user satisfies the support access condition for the user who has the missing date that has not accessed the game server 1 within the continuous five days. When the determination means 56 determines, a continuous access achievement privilege is provided.

This continuous access privilege granting means 57 determines whether or not to grant a continuous access achievement privilege to the user based on the information on the continuous access days in FIG. 9A stored in the access information storage control unit 55a. It has. And the continuous access privilege provision means 57 is the game information (game information which the game information management means 51 memorize | stores and manages in the database server 2) of the user who determined that the privilege generation | occurrence | production determination part 57a produces | generates a continuous access achievement privilege. ) Is changed according to the contents of the privilege.

Here, the continuous access achievement privilege granted to the user by the continuous access privilege grant means 57 will be described. The continuous access achievement privilege only needs to be advantageous in terms of the game as compared to the case where the privilege is not given, and various privileges are conceivable depending on the type and content of the game.

As an example of the continuous access achievement privilege in the baseball game of the present embodiment, various points required for the user to advance the game, such as the above-mentioned action power points, operation costs, reinforcement points, ale points, etc., are given points. There is a privilege of granting the user as bonus points by the amount. When granting such bonus points as a privilege, the continuous access privilege granting means 57 uses the information related to the user's benefit stored in the privilege information storage control unit 51i of the game information management means 51 as the content of the bonus point. Change to match. The lower part of FIG. 6 shows an example in which “enhancement point = + 200” is stored as the privilege information of the user as a result of giving the privilege (bonus points) to the user with the user ID = “000001”. Further, the continuous access privilege giving means 57 changes the game information so as to increase the user's possession points stored in the possession point storage control unit 51d of the game information management means 51 by the bonus points.

As another example of the continuous access achievement privilege, there may be a privilege that a predetermined number (for example, three) of various items that are advantageously used in the game such as the recovery item and the fake card described above are given to the user. When granting an item used in a game as a privilege, the continuous access privilege granting unit 57 uses information related to the user's privilege stored in the privilege information storage control unit 51i of the game information management unit 51 as content of the privilege. The game information is changed so as to increase the number of items owned by the owned item storage control unit 51f by a predetermined number.

Examples of other benefits for achieving continuous access include the following. That is, points such as action power points consumed and reduced during the game are recovered by 1 point every 3 minutes, for example, but this point recovery time is shortened (for example, 2 minutes have elapsed) It is possible to recover 1 point each time. When this privilege is granted, information on the effective period in which the point recovery time is shortened is stored as the user privilege information stored in the privilege information storage control unit 51i. Thereby, the game information management means 51 of the game server 1 performs the process which shortens point recovery time rather than normal time in the period when a privilege is effective (for example, within 24 hours after a user receives notification of a privilege). It will be.

In addition, in the above-described player lottery acquisition mode, there is also a privilege that the probability that a rare card (a player card with a lower lottery probability than a normal player card and a rare value) will be drawn is increased by a predetermined number of times (for example, once). Conceivable. When this privilege is granted, the number of times that the lottery probability is increased is stored as the privilege information of the user stored in the privilege information storage control unit 51i. And the game progress means 52 of the game server 1 will perform the process which raises the lottery probability of a rare card temporarily at the time of the lottery execution of a privilege object.

Also, in the player lottery acquisition mode, points (such as the above-mentioned Yale points) are usually required to execute the player card lottery, but it is free for a predetermined number of times (for example, once) (ie, no points are consumed). A privilege that a player card can be drawn is also considered. When this privilege is given, the number of times that the player card can be drawn for free (no points) is stored as the privilege information of the user stored in the privilege information storage control unit 51i.

Also, a privilege that a predetermined number (for example, one) of player cards selected by the game server 1 by lottery using random numbers or the like is given to the user can be considered. When the player card selected by the game server 1 is given to the user as a privilege, the continuous access privilege granting unit 57 stores information related to the user's privilege stored in the privilege information storage control unit 51i of the game information management unit 51. While changing according to the content of a privilege, player card ID provided as a privilege is added to player card ID which the possession player card memory | storage control part 51c has memorize | stored.

In addition, in a battle mode in which a battle with another user's team is played, there is a privilege that the user is given a game advantage that is advantageous only for n battles (for example, 3 battles). As a method for making it advantageous to carry a game for n battles, a method for improving the strength of the user's team by n battles is conceivable.

Here, there are several ways to improve the user's team strength by means of special benefits. In the battle mode, a player card of a regular player who participates in the game is selected from the player cards owned by the user and battles are performed (for example, the user preliminarily selects from the player cards owned by the user). Select the card of the regular player who will participate in the match, and team up with the regular player's card to play against). Therefore, as a matter of course, normally, the strength of the own team cannot be other than the user's handheld player card.

However, in order to improve the team's strength by means of special benefits, one of the strongest player cards (the player card with the highest ability value) is automatically assigned to the regular player of the user. Try to replace one of the cards. In this case, the game progress means 52 of the game server 1 automatically performs the above-described player card replacement process at the time of execution of a privilege target battle. In addition, when the said user owns the strongest player card among all the user's friend's hand cards, the assistant player card (special which the game server 1 prepares) whose ability value is higher than the said strongest player card. One player card) may be automatically replaced with one of the regular player cards of the user.

As another method of improving the team strength of the user by the privilege, the ability value of a part or all of the player cards of the regular players participating in the game in the battle mode is improved by a predetermined ratio (or a predetermined value). There is also a method. In this case, the game progress means 52 of the game server 1 performs the process which improves the capability value of the player card of the user's team who received the privilege at the time of execution of the privilege target battle.

In addition, as another method for making game play advantageous for n battles, the probability that the user's team to which the privilege is given wins is improved by n battles (therefore, the probability that the opponent user's team wins) Is also possible. For example, if the ability of the teams of both users who are competing is the same, if no privilege is granted to any user, the victory probability of both teams is 50%, but the privilege is granted to one user In the battle being played, while the victory probability of the team of the user X to whom the privilege is given is increased by 10%, for example, to 60%, the victory probability of the team of the opponent user Y is reduced by 10% to 40%. %, The user X is more advantageous in terms of the probability of victory than the user Y.

As described above, when the privilege that the advantage of n battles is advantageous due to improvement in team strength or victory probability is given to the user, the privilege information storage control unit 51i of the game information management means 51 stores the user's The number of times that the battle is advantageous is stored as privilege information.

By the way, if the privilege is too large, there is a possibility that the balance with the improvement of the ability value of the player card that is originally realized by executing the game (that is, the development of the player) may be lost. It is preferable to set the level that gives a certain degree of profit to the user as a sub (sub) position to the last.

Next, the notification means 58 will be described. This notification means 58 has a function of notifying that a privilege has occurred to the user terminal device 3 to which the continuous access achievement privilege has been granted. In the present embodiment, there are roughly two timings at which the continuous access achievement privilege is generated, and the privilege notification processing by the notification means 58 is slightly different depending on the privilege generation timing as described below.

One of the timings when the continuous access achievement privilege is generated is when the user accesses the game server 1 on the last day (the fifth day in the present embodiment) when the continuous access is achieved, and the continuous access is achieved. It is. In this case, since the continuous access achievement privilege is generated in the login state in which the user terminal device 3 is connected to be able to communicate with the game server 1, the notification unit 58 indicates that the privilege has been generated immediately after the occurrence of the privilege. The terminal device 3 can be notified.

Another timing when the continuous access achievement privilege occurs is that the user did not access the game server 1 on the last day (the fifth day in the present embodiment) when the continuous access is achieved (that is, the last day is missing). Is when it is considered that continuous access has been achieved because the fellow user of the user satisfies the support access condition. In this case, since the continuous access achievement privilege is generated in a state where the user's terminal device 3 is not communicably connected to the game server 1, the notification unit 58 indicates that the privilege has been generated immediately after the occurrence of the privilege. Since the terminal device 3 cannot be notified, it is necessary to manage whether or not the user has been notified that the privilege has occurred. Therefore, in the present embodiment, this is managed by the privilege notification flag shown in the lower part of FIG.

That is, when it is considered that continuous access has been achieved by the fellow user satisfying the support access condition on the last day when continuous access is achieved, the notification means 58 notifies the user of the privilege. This is the time when the user's terminal device 3 first accesses the game server 1 after the granting process, and there is a certain time difference between the bonus granting process and the notification. Therefore, when the privilege is given to the user, the notification unit 58 of the game server 1 sets the privilege notification flag shown in FIG. 6 in association with the user ID of the user to “1”, thereby providing the user with the privilege. It manages the state that needs to be notified of the grant. Then, when there is an access to the game server 1 from the terminal device 3 of the user for which “1” is set as the privilege notification flag, the notification means 58 notifies the user that the privilege has been granted. In addition, the privilege notification flag is set to “0”.

An example of privilege notification by the notification means 58 is shown in FIGS. 10A and 10B. FIG. 10A shows an example of the main screen of the game displayed on the display unit 35 of the terminal device 3 of the user to whom the privilege is given. After the privilege granting process in the game server 1, screen data for displaying the main screen shown in FIG. 10A is transmitted from the notification unit 58 of the game server 1 to the user terminal device 3. On this main screen, the team name 70 of the user, the player card 71 selected as the leader among the player cards owned by the user, the game information 72 of the user, etc. are displayed, as well as privilege notification information 73. . Details of the main screen will be described later.

As shown in FIG. 10A, the privilege notification information 73 displayed on the main screen of the terminal device 3 is given a continuous access achievement privilege such as “Achieved continuous access for 5 days! Go to privilege confirmation screen”. It is understandable content. Further, a hyperlink is set in the privilege notification information 73 (or the privilege notification information 73 may be in the form of a button that allows selection of the whole or a part of the privilege notification information 73), and the user notifies the privilege notification on the screen. Information 73 can be selected.

Here, when the user operates the terminal device 3 and selects the privilege notification information 73, the privilege confirmation screen shown in FIG. 10B is displayed from the notification unit 58 of the game server 1 in response to the operation. The screen data is transmitted to the terminal device 3. On this privilege confirmation screen, for example, a specific benefit such as “enhancement point +200 points” is displayed together with a display of “continuous access achievement bonus”, and the user can confirm the content of the continuous access achievement bonus. . In addition, when a fellow user satisfies the support access conditions and is granted a continuous access achievement privilege, for example, “There was a day when the user did not access, but a friend's support access achieved continuous access for 5 days. A sentence such as “I was able to do it!” Is also displayed on the privilege confirmation screen. Thereby, the user can recognize clearly that the continuous access achievement privilege has been acquired by the friend's support access, and is strongly conscious of the existence of the friend.

Further, as shown in FIG. 10B, a “receive” button 74 is displayed on the privilege confirmation screen, and when the user selects the button 74, a present (bonus point) can be received in a pseudo manner. Also good. In this case, bonus points as benefits may be valid when the “receive” button 74 is selected. In this privilege confirmation screen, for example, when a “go to main screen” button 75 is selected, it is possible to return to the main screen.

As described above, in the present embodiment, by including the privilege notification information 73 in the main screen data of the game transmitted from the game server 1 to the user's terminal device 3, the occurrence of the privilege is notified to each user. It has become. The main screen is a basic screen that is always displayed at the start of the game. By displaying the privilege notification information 73 in the main screen, the occurrence of the privilege can be accurately notified to the user.

In addition, since the main screen includes many other objects and information, the details of the privilege can be confirmed by transitioning to the privilege confirmation screen shown in FIG. 10B. However, the present invention is not limited to this. Absent. For example, when the user terminal device 3 accesses the game server 1, the privilege confirmation screen shown in FIG. 10B is displayed on the display unit 35 of the user terminal device 3 before the main screen, and the confirmation screen is displayed. Then, after the user confirms the occurrence of the continuous access achievement privilege, the main screen may be changed by a predetermined operation by the user.

As described above, the notifying unit 58 displays the privilege occurrence information on the main screen or the like to notify the user, so that the notifying process cooperates with the game screen generating unit 52b and the game screen transmitting unit 52c. Is supposed to do.

Further, when the fellow support access determining means 56 determines that the fellow user of the user satisfies the support access condition after the day when the user has lost access (that is, after the missing date is confirmed), the notification means 58 is determined. In addition, the user has a function of notifying the user terminal device 3 that the continuous access is continued when the fellow user satisfies the support access condition. The notification unit 58 performs the notification process when the user's terminal device 3 first accesses the game server 1 after the fellow support access determination unit 56 determines that the support access condition is satisfied. There is a certain time difference between the determination by the support access determination unit 56 and the notification by the notification unit 58. Therefore, when the notification means 58 of the game server 1 determines that the fellow support access determination means 56 satisfies the support access conditions, the notification means 58 is associated with the user ID of the user, and the continuous access continuation notification flag ( In this figure, the continuation notification flag (abbreviated as “notified”) is set to “1”, thereby managing a state where it is necessary to notify the user that continuous access is continuing. When there is an access to the game server 1 from the terminal device 3 of the user for which “1” is set as the continuous access continuation notification flag during the day following the day when the access is lost, the notification means 58 In addition, the fact that the continuous access is continued when the fellow user satisfies the support access condition is notified, and the continuous access continuation notification flag is set to “0”.

In addition, although the continuous access once has been continued due to the support access of the fellow user, since the user did not access the game server 1 on the day after the day when the access was lost, the continuous access was eventually interrupted. In this case, the notification during continuous access by the notification unit 58 is not performed. Therefore, even when continuous access is interrupted, the continuous access continuation notification flag is set to “0”. However, even if continuous access is interrupted in this way, the notification means 58 of the game server 1 may notify the user's terminal device 3 of the fact that the fellow user satisfies the support access condition. .

11A and 11B show notification examples indicating that continuous access is being continued by the notification means 58. FIG. FIG. 11A shows an example in which the fact that continuous access is continuing is displayed on the main screen of the game to notify the user. When the user's terminal device 3 first accesses the game server 1 after the user's terminal device 3 first accesses the game server 1 after determining that the friend's support access determination means 56 satisfies the support access condition by the friend on the day after the day when the user has lost continuous access, Screen data for displaying the main screen shown in FIG. 11B is transmitted from the notification unit 58 of the server 1 to the terminal device 3 of the user. On the main screen, the team name 70, the player card 71, the game information 72, etc. of the user are displayed, and the continuous access continuation notification information 76 is also displayed. The continuous access continuation notification information 76 is, for example, that continuous access is performed when a fellow user satisfies the support access conditions such as “continuous access is being continued due to fellow support access! The content shows that it continues without interruption.

Thereby, the user can recognize the fact that the continuous access is continued by the support access of the fellow user on the next day when the game server 1 cannot be accessed. Therefore, the user is strongly conscious of the existence of his / her friend, and has a strong consciousness of continuously accessing the game server 1 and acquiring the continuous access achievement privilege. For this reason, continuous access to the game server 1 by the user can be effectively promoted.

FIG. 11B shows an example of notifying the user by displaying that continuous access is continuing on a screen other than the main screen of the game. When the user's terminal device 3 first accesses the game server 1 on the day after the day when the user has lost continuous access, the notification means 58 of the game server 1 shows, for example, before the main screen, as shown in FIG. 11B. The screen data is transmitted to the user terminal device 3. This screen displays that yesterday (the same day as the missing date) that the companion game access record and support access conditions have been satisfied. FIG. 11B shows a display example of a friend's access record such as “Yesterday, 8 out of 10 friends have accessed the game. Clear the support access condition (access 80% or more of friends)!”. Moreover, the continuous access continuation notification information 76 similar to FIG. 11A is displayed on this screen, and the user is informed that the continuous access is continued without interruption when the fellow user satisfies the support access condition. . In the screen of FIG. 11B, for example, when the “go to main screen” button 75 is selected by the user, the main screen data is transmitted from the game server 1 to the user terminal device 3, and the screen of the terminal device 3 transitions to the main screen. To do.

Next, the message transmission means 59 will be described. The message transmission unit 59 has a function of receiving a message addressed to another user transmitted from the terminal device 3 of each user and transmitting the message to the other user. The message transmission means 59 includes a message storage control unit 59a.

FIG. 12 shows an example of information related to a received message that is stored and managed in the database server 2 by the message storage control unit 59a. The message storage control unit 59a associates information about the message such as the user ID of the transmission source, the content of the message, and the transmission date with the user ID of the reception side user who received the message, for each user ID of the reception side user. Are stored in a predetermined storage area of the database server 2. The example of FIG. 12 shows information related to the received message for one receiving user with the user ID = “000002”, and the user has the user ID = “000001” to “access hard!” From the user with ID = “000038”, the message “Please support us because we cannot access tomorrow!” And the message “Thank you this week!” From the user with user ID = “000145”, respectively.

Here, an example of an operation in which a user sends a message to his / her fellow user will be described. FIG. 13A shows an example of a buddy list screen displayed on the user terminal device 3 based on the screen data transmitted from the game server 1. This buddy list screen is a screen that is displayed, for example, when the user operates the terminal device 3 and selects “buddy menu” in the main screen. On this buddy list screen, information of buddy users who are in a buddy relationship with the user is listed and displayed. In addition, about the information of the fellow user who cannot be displayed on a screen, the screen can be scrolled or the 2nd page or more of a fellow list can be requested to the game server 1, and can be displayed as another screen.

In this buddy list screen, an information display area for each buddy user listed is provided, and each information display area includes game information 81 of the buddy user (user name, team name, user level, buddy's The number of people, the league level, etc.), an avatar 82 that is the user's alternate character, the player card 83 of the leader owned by the user, and an object called an ale button 84 are also displayed. Then, when the user selects this ale button 84, it is possible to send ale (support) to his / her fellow users (display a support intention). The user can send only ale to fellow users, but can also send messages as described below.

When the ale button 84 is selected by the user's operation on the terminal device 3, the operation is transmitted from the terminal device 3 to the game server 1. Thereafter, from the game server 1, for example, data of a message input screen illustrated in FIG. 13B is transmitted to the terminal device 3, and the message input screen is displayed on the terminal device 3. On this message input screen, for example, text indicating that ale is sent to a fellow user (user B in the example of FIG. 13B) is displayed, and objects such as a message input area 85 and a send button 86 are also displayed. Is done. Then, the user operates the terminal device 3 to input an arbitrary message in the message input area 85 and selects the transmission button 86, whereby a message addressed to the fellow user is transmitted from the terminal device 3 to the game server 1. The FIG. 13B shows an example in which the user inputs a message “Let's do our best!”. In consideration of the storage capacity in the database server 2, there may be a restriction (for example, within 30 full-width characters) on characters that can be input in the message input area 85.

In addition, the hyperlink 87 for changing to the page of a fellow user (in this example, user B) is displayed on the message input screen, and the details of the game information of the fellow user are described by selecting this link. Displayed pages. In addition, a hyperlink 88 for transitioning to the buddy list and a hyperlink 89 for transitioning to the main screen are also displayed on the message input screen. By selecting these links, a buddy list or main screen is displayed. You can come back.

When a message is transmitted from the terminal device 3 by a user operation on this message input screen, the message storage control unit 59a of the message transmission means 59 in the game server 1 sends a message addressed to the fellow user received from the terminal device 3. Then, it is stored in the database server 2 in association with the user ID of the fellow user (see FIG. 12). When the fellow user's terminal device 3 accesses the game server 1, the message transmission means 59 of the game server 1 transmits screen data for displaying a message, a transmission source user name, a transmission time, and the like to the terminal device 3. To do. As a result, a message or the like is displayed on the terminal device 3 of the user who has received this screen data, and the message received from another friend can be confirmed on the screen.

As described above, in the game system according to the present embodiment, the communication tools illustrated in FIGS. 13A and 13B can be used to communicate with each other at any time.

In the example of FIGS. 13A and 13B, the example in which a message is sent to a user's associate has been described. However, it is possible to send an ale or a message to other users who are not in a friend relationship. For example, it is possible to send an ale or a message to other users who are not listed on the fellow candidate list screen (see FIG. 31), which will be described later, by the same operation as that of the fellow.

By the way, in the above description, the information about each user who is managed by the fellow management means 53, the access information of each user which is managed by the access management means 55, and the information about the message which is managed by the message transmission means 59 are as follows. For convenience, the information is described separately from the various information managed by the game information management means 51, but these pieces of information are all included in the game information managed by the game server 1.

[Game system operation]
In the above configuration, an example of the operation of the game system according to the embodiment of the present invention will be described below with reference to the flowchart of FIG. FIG. 14 shows a basic flow of processing of the terminal device 3 and the game server 1 when the user operates the terminal device 3 to access the game server 1 to receive a game service.

When the user receives the game service, first, the web browser is started by operating the operation input unit 40 of the terminal device 3 (S11). Thereafter, the user performs an operation of accessing a game site managed by the game server 1, and an access request is transmitted from the terminal device 3 to the game server 1 (S12). At this time, the game server 1 performs login authentication for access from the terminal device 3 (S21), and confirms that the access is from a user who is registered for use of the game service. Thereafter, the game server 1 transmits main screen data described in HTML or the like to the terminal device 3 (S22). In the terminal device 3 that has received the main screen data, the web browser interprets the data and displays the main screen on the display unit 35 (S13).

As illustrated in FIG. 10A, the main screen includes a user team name 70, an image of a player card 71 selected as a leader among player cards owned by the user, user game information 72 (user level, action Power points, operating costs, reinforcement points, ale points, number of player cards owned, number of friends, etc.) are displayed. In addition, the above-described privilege notification information 73 and the like are also displayed. Furthermore, on this main screen, by operating the direction keys of the terminal device 3 and scrolling the screen, a game mode selection button (not shown), various menu buttons, fellow movement information, messages from other users, etc. Various objects and information are displayed.

Here, when the user performs an operation of selecting an object such as a selectable button or a hyperlink displayed on the screen, a screen request corresponding to the operation is transmitted from the terminal device 3 to the game server 1 (S14). ). Receiving this request, the game server 1 performs arithmetic processing and data processing according to the user's operation to execute the game (S23), and transmits game screen data reflecting the execution result to the terminal device 3 (S24). ). And in the terminal device 3 which received screen data, a web browser interprets the said data and displays a game screen on the display part 35 (S15).

Thereafter, the above-described S14 and S15 are repeated in the user terminal device 3, and the above-described S23 and S24 are repeated in the game server 1, whereby the selectable button displayed on the screen of the terminal device 3 Etc., the game screen of the terminal device 3 is switched one after another, and the game can be advanced.

Thereafter, when the user operates the terminal device 3 to close the game screen (S16), the game server 1 performs logout processing (S25). For example, when the user closes the web browser, the game server 1 performs logout processing after a session timeout.

By the way, in this game system, even when the user logs out from the game server 1, the game server 1 side can read the game information of the user and advance the game. For example, another logged-in user may start a battle (individual battle) against the logged-out user's team, and the game progress means 52 of the game server 1 determines whether the user is logged in. Regardless of whether or not, the game information of each user is read from the database server 2 and the battle is executed, and the game information of each user is updated to reflect the execution result. Further, in the league game mode, the game progress means 52 of the game server 1 reads out the game information of each user from the database server 2 and automatically executes the league game without the user operating the terminal device 3. Thus, the result of the battle executed when the user is logged out from the game server 1 can be confirmed on the screen when the user accesses the game server 1 thereafter.

[Operation of game management device]
Next, a more detailed operation example of the game management device according to the embodiment of the present invention will be described with reference to the flowcharts of FIGS. FIG. 15 to FIG. 17 show the processing flow of the game server 1 for a single user, and the same processing is performed for each user managed by the game server 1.

The flowchart in FIG. 15 exemplifies a process that is executed every time one day (unit period) in the real world ends. For example, the process is started every day at midnight. If it is the start time of this process (YES in S31), it is determined whether or not the user has accessed the game server 1 at least once on the previous day (S32). This determination can be made based on the access information shown in FIG. 9A (information indicating the presence or absence of access one day ago).

If the user has not accessed the game server 1 on the previous day (NO in S32), whether or not the lack of access on the previous day corresponds to the first day of the missing access that occurred in the middle of five consecutive days. Determination is made (S33). In the present embodiment, since the missing date that can be compensated is only one day in the five consecutive days, if the lack of access on the previous day is the missing date on the second day (NO in S33), the user The continuous access to the game server 1 is interrupted, the process proceeds to S40, and the continuous access days shown in FIG. 9A are initialized to “0 days”.

When the previous day's lack of access is the first day of the missing access date that occurred in the middle of five consecutive days (YES in S33), a determination process as to whether or not the user's associates satisfy the support access condition (S34) And the process proceeds to S35). FIG. 15 shows an example in which the support access condition is “the proportion of the fellow users who have accessed the game server 1 at least once on the same day as the missing day is 0.8 or more in the whole fellow users”. . In S34, the ratio R of all the fellow users who have accessed the game server 1 at least once on the previous day (that is, the same day as the missing day) is calculated. Thereafter, in S35, it is determined whether or not the calculated ratio R satisfies the support access condition of 0.8 or more.

If the above-mentioned support access condition is not satisfied (NO in S35), the user's continuous access is interrupted, and the process proceeds to S40, where the continuous access days are initialized to “0 days”. On the other hand, when the above-mentioned support access conditions are satisfied (YES in S35), the game server 1 considers that the user has accessed the game server 1 on the previous day, and performs continuous access continuation processing (S36). As a specific processing example of the continuous access continuation processing, the user access information shown in FIG. 9A is set / changed as follows. That is, the game server 1 sets information indicating whether or not the support access condition is satisfied (information one day before) to “1”, increments the count of consecutive access days by one, and sets the continuous access continuation notification flag to “ Set to “1”.

Thereafter, it is determined whether or not continuous access for 5 days has been achieved (S37). When the previous day is the last day of 5 consecutive days, the user achieves continuous access when the user's friends satisfy the support access condition (YES in S37). In this case, the continuous access privilege grant means 57 changes the user's game information so as to be advantageous in terms of the game, and grants the continuous access achievement privilege (S38). For example, when a predetermined enhancement point is given to a user as a bonus point, game information (user privilege information and enhancement point information illustrated in FIG. 6) corresponding to the user ID of the user is changed. After the continuous access achievement privilege grant processing, the game server 1 sets the privilege notification flag shown in FIG. 6 to “1” (S39), and initializes the continuous access days shown in FIG. 9A to “0 days”. (S40).

On the other hand, if the previous day is not the last day of five consecutive days, the continuous access for five days has not been achieved yet at this point (NO in S37). The routine of 15 is finished.

As described above, in the present embodiment, even if there is a missing date when the user could not access the game server 1, the user's fellows satisfy the support access condition, so that the user's continuous access is continued.

Next, the operation of the game management device (game server 1) when the user accesses the game server 1 will be described with reference to the flowchart of FIG. When receiving the access request from the user terminal device 3 (YES in S51), the authentication means 54 of the game server 1 uses the login ID / password transmitted from the terminal device 3 or the individual identification number of the mobile phone terminal. Based on this, login authentication is performed to determine whether or not to permit access (S52). Here, when the authentication means 54 does not permit access (NO in S52), the game server 1 transmits screen data that prompts the terminal device 3 to use the game service (S53).

On the other hand, when the authentication unit 54 permits access (YES in S52), the access management unit 55 stores user access information (S54). For example, as shown in FIG. 9A, the access information storage control unit 53a of the access management means 55 updates the access information on the current day of the user in association with the user ID (that is, sets an information bit indicating the presence or absence of access to “ 1 ”). Furthermore, the access management means 55 of the game server 1 increases the count of the continuous access days shown in FIG. 9A by one (S55).

Thereafter, it is determined whether or not the number of consecutive access days has reached 5 (S56). Here, when the number of continuous access days of the user has reached 5 (YES in S56), the continuous access privilege granting means 57 changes the user's game information so that it is advantageous for the game, and the continuous access achievement privilege (S57). After the continuous access achievement privilege grant processing, the continuous access days shown in FIG. 9A are initialized to “0 days” (S58). And the alerting | reporting means 58 produces | generates the screen data for alerting | reporting to a user that the continuous access achievement privilege was provided (S59). For example, as shown in FIG. 10A, screen data including privilege notification information 73 in the main screen of the game is generated. Thereafter, the game server 1 transmits main screen data including the privilege notification information 73 to the user's terminal device 3 (S60). Thereby, since the main screen including the privilege notification information 73 illustrated in FIG. 10A is displayed on the user terminal device 3, the user can recognize that the continuous access achievement privilege has been acquired.

On the other hand, if the number of continuous access days of the user has not reached 5 (NO in S56), it is determined whether or not the privilege notification flag is set to “1” (S61). That is, in the present embodiment, as described above, the user who has not been able to access the game server 1 on the last day of five consecutive days satisfies the support access condition, so that the user achieves continuous access. In this case, the privilege notification flag is set to “1”. Therefore, when the privilege notification flag is set to “1” (YES in S61), the process proceeds to S59, and screen data for notifying the user that the continuous access achievement privilege has been granted is generated. (S59). When S59 is executed via S61, although not shown in the flowchart, the privilege notification flag is set to “0”. Thereafter, the game server 1 transmits main screen data including, for example, the privilege notification information 73 shown in FIG. 10A to the user terminal device 3 (S60). Thereby, since the main screen including the privilege notification information 73 is displayed on the user's terminal device 3, the user cannot access the game server 1 on the last day of five consecutive days, It is possible to recognize that a continuous access achievement privilege has been acquired through the support access of

If the privilege notification flag is not set to “1” in S61, it is determined whether or not the continuous access continuation notification flag is set to “1” (S62). That is, in the present embodiment, as described above, even if there is a missing date when the user could not access the game server 1, continuous access by the user is continued when the user's associates satisfy the support access condition. In this case, the continuous access continuation notification flag is set to “1”. Therefore, when the continuous access continuation notification flag is set to “1” (YES in S62), a screen for notifying that the continuous access is continued when the user's fellow user satisfies the support access condition Data is generated by the notification means 58 (S63). For example, as shown in FIG. 11A, screen data including continuous access continuation notification information 76 in the main screen of the game is generated. Thereafter, the game server 1 transmits main screen data including the continuous access continuation notification information 76 to the user terminal device 3 (S60). Thereby, since the main screen including the continuous access continuation notification information 76 is displayed on the terminal device 3 of the user, the user cannot access the game server 1 on the previous day, but the friend's support access It can be recognized that continuous access is continued.

On the other hand, when neither the privilege notification flag nor the continuous access continuation notification flag is “1” (NO in S61 and S62), the game server 1 transmits normal main screen data to the user terminal device 3 (S60). .

And the game server 1 performs a game progress process after transmission of main screen data (S64). The game progress process in the game server 1 will be described below with reference to the flowchart of FIG.

As shown in FIG. 17, when the game server 1 receives a screen request according to the user's game operation transmitted from the user's terminal device 3 (YES in S71), the game execution means 52a displays the screen request. The game is executed by performing arithmetic processing and data processing in accordance with (S72).

Thereafter, the game server 1 determines whether or not the user's game information needs to be updated by executing the game (S73). If the game server 1 needs to be updated (YES in S73), the game server 1 is stored in the database server 2. The game information of the existing user is updated (S74). For example, when the user's game operation is an operation for performing an individual battle with another user, as a result of the battle being executed, the game information of the user such as game result information, operation costs, reinforcement points, and items is updated. Will be. On the other hand, for example, when the game operation of the user is an operation for confirming the result of the league game, the game execution process corresponding to the operation is only a data process for reading out the result information of the league game from the database server 2, There is no change in the user's game information before and after the process, and therefore there is no need to update the user's game information (NO in S73).

Thereafter, the game screen generation means 52b generates game screen data reflecting the execution result of the game (S75), and the game screen transmission means 52c transmits the game screen data to the user terminal device 3 (S76). Thereafter, it is determined whether or not the user's terminal device 3 has logged out (S77), and the game proceeds by repeating the processes of S71 to S76 until the terminal device 3 logs out.

As described above, in the present embodiment, even if a user has a missing access date (missing unit period) within 5 consecutive days (unit period of the continuous specified number of periods), By satisfying a predetermined support access condition, a continuous access achievement privilege is given to the user. Therefore, even if the user is unable to access the game server 1 for something, he / she can acquire the continuous access achievement privilege by maintaining a high access frequency such that the user's companion satisfies the support access condition. Benefits arise. Moreover, if the user himself / herself also maintains a high access frequency, it can contribute to achievement of the support access condition when other associates lose access, and can indirectly support other associates. Thereby, each user is given the consciousness and motivation to increase the access frequency with each other. Therefore, each user is given the motivation to communicate with his / her fellow users in an attempt to increase the frequency of access to the game server 1 of all the friends. For example, each user sends a message such as “Let's do our best!” To his / her peers, and tries to excite the community with his / her fellow users.

Thus, in the present embodiment, not only providing the user with the fun of receiving a privilege, but also motivation to increase the access frequency with each other and to motivate to communicate with each other The user can be given a bonus, thereby activating the entire game community. As a result, each user strengthens the connections and exchanges between friends in the game, and further increases the interest and interest in the game, so that it is possible to realize a game having continuity that will not get tired for the user.

In this embodiment, fellow users who have made at least one access on the same day (within the same unit period) as the missing day of access (missing unit period) (a fellow user who has achieved access within the unit period) It is set as a support access condition that the ratio of the number of people or the total number of fellow users exceeds a threshold. In this case, in order to satisfy the support conditions for support by the fellow on the day of the missing date, the user informs other fellows in advance of a day that is likely to be a missing day (a day when access is unlikely). I can keep it. For example, the user can request a cheering access in advance by sending a message such as “Please give me cheering access because I cannot access tomorrow!” To my friends. In this way, by requesting support access in advance, the community between friends is excited. In addition, on the day that support access is requested in advance, the friend actually satisfies the support access condition, so the friendship is enhanced and the friendship is stronger, and the user is more interested and interested in the game. To do.

By the way, in the above description, an example is shown in which the missing date that can be compensated is only one day among the continuous five days, but the missing date that can be compensated can be two days or more. However, as described above, since the continuous access achievement privilege is originally acquired by the user himself / herself by continuously accessing the game server 1, it is better not to allow too many missing days that can be compensated. Therefore, it is desirable to set an upper limit for missing dates that can be compensated. For example, the maximum number of missing dates that can be compensated is 2 days, and 3 days or more cannot be compensated.

If the maximum number of missing days that can be compensated is 2, the support access conditions for making up the first day of the missing day and the support access conditions for making up the second day of the missing day should be the same condition. Is also possible. On the other hand, the second day of the missing date (second missing unit period) is more than the first day of the missing date (first missing unit period) to avoid making up for multiple missing days easily. However, it is desirable to set the conditions that do not satisfy the support access conditions. For example, the support access condition for making up for the first day of the missing date is “the ratio R of all the fellow users who accessed the game server 1 at least once on the same day as the missing date is 0. And the support access condition for making up for the second day of the missing date is “the ratio R is 0.9 or more (or access was lost on the same day as the missing date”). All friends other than the user have accessed the game server 1 at least once) ”, and the second day of the missing date is considerably stricter than the first day. The operation of the game server 1 when the second day of the missing date is set to a stricter support access condition than the first day will be described below with reference to the flowchart of FIG. In addition, about the process similar to the flowchart shown in FIG. 15, the same step number is attached | subjected and the description is abbreviate | omitted suitably.

If the processing start time is reached (YES in S31), it is determined whether or not the user has accessed the game server 1 at least once the previous day (S32), and if the user has not accessed the previous day (in S32). NO), it is determined whether or not the lack of access on the previous day corresponds to the third day of the missing access date that occurred in the middle of five consecutive days (S81). Here, if the lack of access on the previous day is the third day (YES in S81), the user's continuous access to the game server 1 has been interrupted, and the process proceeds to S40 where the number of consecutive access days is “ It is initialized to “Day 0”.

If the previous day's lack of access was not the third day of missing access that occurred in the middle of five consecutive days, that is, the missing day of the first or second day (NO in S81), the user's The process proceeds to determination processing (processing after S34) as to whether or not the friend satisfies the support access condition. In S34, the ratio R of all the fellow users who accessed the game server 1 at least once on the previous day (that is, the same day as the missing day) is calculated. Thereafter, in S82, a branching process for changing the support access condition is performed depending on whether or not the missing date is the first day. If the missing date is the first day (YES in S82), it is determined whether the calculated ratio R satisfies the support access condition of 0.8 or more (S35). On the other hand, if the missing date is the second day instead of the first day (NO in S82), whether or not the calculated ratio R is, for example, 0.9 or more so that the support access condition is stricter than the first day Is determined (S83). If the support access condition is satisfied (YES in S35 or S83), the game server 1 considers that the user has accessed the game server 1 on the previous day, and performs continuous access continuation processing (S36). On the other hand, when the support access condition is not satisfied (NO in S35 or S83), the user's continuous access is interrupted, and the process proceeds to S40, where the continuous access days are initialized to “0 days”. Note that S37 to S39 are basically the same processes as those described in the flowchart of FIG.

As described above, by applying stricter support access conditions on the second day than on the first day of the missing day, it is possible to avoid making up for a plurality of missing days easily. In addition, to allow users who satisfy the severe support conditions on the second day to make up for multiple missing days, the consciousness to increase the access frequency with each other in order to achieve strict conditions And motivation can be given to the user.

In addition, when 3 days or more are allowed to make up for the missing date, the missing date (second missing unit period) that occurred later in time series is the missing date (first missing unit period) that occurred earlier than that. It is desirable to apply stricter support access conditions.

In addition, in the above description, an example in which a continuous access achievement privilege is granted if each user achieves continuous access for 5 days on any day has been described. However, continuous access is achieved in the following limited-time in-game event. A privilege may be given.

That is, in the game system of the present embodiment, the game server 1 manages the game information of the user and executes the game, so that the game execution program basically exists on the game server 1 side. Therefore, when the game service operator adds / changes the game execution program on the game server 1 side, all game service users (users) can receive the added / changed game service. For this reason, it is also possible to easily provide a variety of game services to the user by adding / changing the game execution program on the game server 1 side and appropriately holding in-game events for a limited time. Therefore, for example, the monthly event period is 5 days from the 1st to 5th of every month, or 7 days from Monday to Sunday of the first week of every month, or the 7th of the Christmas week is the Christmas event period. It is also possible to provide a game service that grants a privilege to those who have achieved continuous access. Especially when holding a limited-time event, it is often possible for users to acquire benefits that are larger than the continuous access achievement privilege that can be acquired during normal times, so support access conditions that can make up for missing days of access, It may be strict according to the size of the privilege.

[Another configuration example of the game management device]
Next, a configuration example of a game management apparatus to which a condition different from the above-described support access condition is applied will be described with reference to the functional block diagram of FIG. Note that the same components as those shown in the above-described drawings (FIGS. 1 to 18) are denoted by the same reference numerals, and description thereof will be omitted as appropriate. The support access condition described in the present embodiment is a threshold value that is an evaluation value of a group of users who have missing days (missing unit periods) in consecutive 5 days (unit period of consecutive specified periods). It is to exceed. The evaluation value of this group is calculated based on the access frequency, and in this embodiment, as an evaluation value of the group, an example of applying the fellow access average that is the average value of the fellow access frequency, This will be described below.

The game server 1 (game management apparatus) according to the present embodiment includes an access average calculation means 60 and fellow access average calculation means 61 (evaluation value calculation means) in addition to the means 51 to 55 and 57 to 59 shown in FIG. ). Moreover, this game server 1 is provided with the friend support access determination means 156 instead of the friend support access determination means 56 shown in FIG. The access average calculation means 60, the fellow access average calculation means 61, and the fellow support access determination means 156 are realized by the CPU 11 of the game server 1 executing the program according to the present embodiment.

The access average calculating means 60 calculates an “access average” that is an average value of the access frequency of each user to the game server 1 as a target of the frequency with which the user accesses the game server 1. Here, there are an infinite number of methods for calculating the access average. For example, a period for calculating the access average (hereinafter referred to as an access average calculation period) can be arbitrarily set.

However, the access average of each user calculated by the access average calculating means 60 is a value used as a base when the fellow access average calculating means 61 calculates the fellow access average, and thus affects the support access conditions. Since it is a value, it is desirable to determine the access average calculation period in consideration of this. Therefore, in this embodiment, a predetermined period (for example, seven days before the missing day) immediately before the missing date (missing unit period) that the user could not access is set as the access average calculation period. Then, the access average calculation means 60 calculates the access average during this access average calculation period for each of the user's fellow users, and the fellow access average calculation means 61 targets a group of friends centered on the user. The average of peer access is calculated.

There are several points to consider when setting the access average calculation period. First, as for the length of the period, since the change of users (users who stop receiving game services and new users) always occurs, the access average calculation period is a relatively long period of several months. In such a case, the number of user replacements that occur within the period is likely to increase. The user who started or stopped the game service in the middle of the access average calculation period does not satisfy the period condition for calculating the access average, so it is desirable to exclude it from the calculation target. By limiting the period to within 5 days, more preferably about 5 to 10 days, it is possible to reduce the exclusion of calculation objects that do not satisfy the period condition. In particular, for users who have started a game service, it is not possible to calculate access averages until a long access average calculation period of several months has passed (that is, they do not contribute to support access conditions at all) Never desirable. Therefore, the access average calculation period is preferably set to a period of one month or less, more preferably limited to about 5 to 10 days.

Further, if the access average calculation period (the parameter for calculating the access average) is limited to a period of less than one month, more preferably about 5 to 10 days, for example, the period is set to 3 months. In addition, it is possible to avoid a situation in which a change in the average value becomes scarce and a feeling of redundancy occurs.

Further, by setting the access average calculation period to a predetermined period of “immediately before the missing date” (for example, seven days before the missing date), the user's daily access to the game server 1 is reflected in the access average. Become. For example, even when the access average calculation period is the same 7 days, it is not 7 days from the previous day of the missing date (7 days from 7 days ago to 1 day before), for example, 7 days from 1st to 7th of the previous month In such a case, the access average calculation period ends a few weeks before the missing date, and access to the game server 1 after the end of the period is not reflected in the access average. On the other hand, if the access average calculation period is set to a predetermined period of “immediately before the missing date”, the daily access up to the previous day when the determination of whether or not the support access condition is achieved is reflected in the access average calculation result. Therefore, the user is always motivated to increase the access average.

Hereinafter, in the present embodiment, an example in which the access average calculation period is set to 7 days before the missing day will be described.

As shown in FIG. 9A, the access information storage control unit 55a (access frequency storage unit) of the access management unit 55 associates with the user ID to check whether or not the user has accessed each day up to n days before in the real world ( 1-bit information (present = “1”, absent = “0”) is stored for each user ID as information representing the access frequency. Alternatively, as shown in FIG. 9B, the access information storage control unit 55a of the access management means 55 associates the user ID with the number of accesses for each day up to n days before in the real world as information indicating the access frequency. Stored for each user ID.

Here, the number of times of access is the number of times of accessing and logging in to the game server 1 from a state where the user terminal device 3 is not connected to the game server 1 (a state where a session is not established). Therefore, in principle, access to the game server 1 for advancing the game after login is not included in the access count. After logging in, once the game is finished and logged off, when the user logs in again by accessing the game server 1, it is counted as the number of accesses.

If the login time is before midnight, which is the date change time, and the logout time has passed midnight, that is, if the game is played across dates, the date change time has passed. The subsequent access to the game server 1 may be regarded as an access on a different day from the day of login even if the access is being logged in, and the number of accesses may be counted.

In the game server 1, the date change time for game management may be set to a time different from midnight. For example, a game management day may start at 3 am until the next day until 3 am, and the game management date may be changed every day at 3 am.

Next, a specific calculation example of the access average by the access average calculation means 60 in the case where the access average calculation period is 7 days until the day before the missing date will be exemplified. Various methods can be considered as the access average calculation method. Here, calculation examples (1) to (3) will be described as typical calculation methods.

In calculation example (1), the total number of accesses for 7 days is simply divided by 7 days, and the number of accesses per day (number of times / day) is calculated as an access average. For example, as shown in FIG. 20A, the user A accessed 0 times, 1 time, 4 times, 1 time, 3 times, 5 times, and 0 times on each day 1 day to 7 days before the missing date. In this case, the access average of the user A is
(0 + 1 + 4 + 1 + 3 + 5 + 0) / 7 = 2 (times / day)
Can be calculated as

In the calculation example (2), if the game server 1 is accessed at least once a day, the count of the day is set to “1”, while the count is set to “0” when the access is never made. That is, if there is at least one access per day, the access is evaluated and the count is set to “1”. Then, the total of the seven days is divided by seven days, and the count per day (count / day) is calculated as the access average. In this case, if there is at least one access per day for all seven days, the access average = 1. In the example of the user A shown in FIG. 10A described above, the access average of the user A is
(0 + 1 + 1 + 1 + 1 + 1 + 0) /7=0.71 (count / day)
Can be calculated as In the case of this calculation example (2), as the access frequency information for 7 days, it is only necessary to know the presence / absence of access on each day, and the presence / absence of access can be stored as 1-bit information. The storage capacity can be reduced rather than storing.

The calculation example (3) is a modification of the above calculation example (2). When the access average is calculated on the day when the game server 1 is accessed only once per day and the day when the game server 1 is accessed a plurality of times per day. The weighted average is obtained by changing the weight of. For example, the count when accessed only once a day is set to “1”, and a weight is given so that the count when accessed multiple times per day is greater than 1, and the access average of each user is calculated. As an example of weighting, when the number of accesses on a given day is a, the weighted average weight w is
w = {1+ (a-1) × 0.1} (1)
It is possible to increase the weight as the number of accesses increases. In this weighted average calculation method, if there is at least one access per day, the access is highly evaluated and the count is set to “1”, and there are multiple accesses per day In addition, the number of accesses is additionally evaluated and the count is set to 1 or more. According to the weighting method of the above formula (1), when accessing twice or more per day, the count increases by 0.1 every time the access is increased once. In the example of the user A shown in FIG. 10A described above, the access average (weighted average) of the user A is
(0 + 1 + 1.3 + 1 + 1.2 + 1.4 + 0) /7=0.84 (count / day)
Can be calculated as

Note that the method of calculating the access average is not limited to the above calculation examples (1) to (3). For example, the weighting method for calculating the weighted average may be changed.

Here, calculation examples (1) to (3) will be considered based on the examples of the access results of the users A, B, and C to the game server 1 shown in FIGS. 20A to 20C.
User A in FIG. 20A accesses 5 times or more out of 7 days, and the number of accesses varies depending on the day. User B in FIG. 20B has the same total number of accesses as user A, 14 times, but only 3 days have been accessed more than once out of 7 days, and access is concentrated from Friday to Sunday. ing. The user C in FIG. 20C has a smaller total access count than the users A and B, but constantly accesses once a day for seven days. In this way, the access mode is tripartite, and the access average calculation result varies greatly depending on which of the calculation methods (1) to (3) is used.

For example, when the evaluation is focused on the number of accesses to the game server 1, the access average calculation method of the calculation example (1) is suitable. In the calculation method of calculation example (1), the access average of user C is lower than the access average of users A and B.

On the other hand, the calculation method of the average access in the calculation example (2) or (3) is suitable when the evaluation is focused on the constant access within the average calculation period rather than simply the number of accesses. In the calculation method of the calculation example (2) or (3), the access average of the user C is higher than the access average of the users A and B. For example, in the case of a game service that uses a so-called item billing system in which the basic game fee is free and only charges for the use of some items, etc., the amount of access is also important, but for game service users Since it is more demanded to continuously use the service, it can be said that the calculation example (2) or (3) in which evaluation is focused on constant access is more suitable. In particular, calculation example (3) employs a weighted average in which the number of accesses is also evaluated while placing emphasis on constant access, and is most suitable.

The access average calculating means 60 calculates the access average as described above for each of the fellow users who have lost access. Then, based on the calculated access average of each fellow user, the fellow access average calculating means 61 calculates a fellow access average that is an evaluation value of the group called the fellow.

Here, since the user (group) centering on each user includes the user who becomes the center, the access of the user (the user who has lost access) is also the center of the peer access average. You may calculate including an average, and may calculate a fellow access average based on the access average of fellows other than the user who becomes the said center.

For users who have not made any friends, since there is no group of friends centered on the user, the peer access average is not calculated, and therefore it is also determined whether or not the support access condition is satisfied. Absent.

Moreover, although the access average calculation means 60 demonstrated the example which calculates the associate access average for all the associates of a user fundamentally above, the non-active user shown below is excluded and an associate access average is calculated. It is good also as a structure. The inactive user here refers to a user who has registered to use the game service for the game server 1 but does not play the game at all, or indicates a user whose game play is less than the standard, It is defined as “a user whose access frequency to the game server 1 is less than a threshold”. For example, when the access frequency threshold is set to “once / month” (that is, access once in the most recent month), a user who has never accessed the game server 1 in the most recent month The inactive user does not satisfy the threshold condition.

Note that the threshold of access frequency is not limited to “once / month”, and for example, “twice / month” (two accesses in the most recent month), “once / three weeks”. (Access once in the last 3 weeks), “Once / 20 days” (Access once in the last 20 days), etc. Can be set to

The reason why the peer access average is calculated by excluding the inactive users in this way is that if the inactive users are included in the peer access average calculation target, the calculation data may not match the actual situation. For example, even if a user is enthusiastic about the game and makes a large number of friends (for example, about 30 friends), if about half of the friends happen to be inactive users, the average access rate of the users is large. It is because it will fall.

Therefore, the fellow access average calculation means 60 excludes inactive users whose access frequency to the game server 1 is less than the threshold from the user's peers, and calculates the peer access average for each user. Here, the determination as to whether or not the user is an inactive user is made based on the access frequency information of each user managed by the access management means 55.

In the present embodiment, as illustrated in FIG. 9A or FIG. 9B, the access information storage control unit 55a of the access management unit 55 uses the presence or absence of access up to n days ago as access information for managing the access frequency. The number of times is stored and managed in the database server 2 for each user ID. Based on this access information, the CPU 11 of the game server 1 determines, for example, whether or not the threshold of access frequency = “one time / month (30 days)” is satisfied. That is, it can be determined that the user corresponding to the user ID for which the information on the presence / absence of access or the number of accesses from 30 days ago is all “0” is an inactive user that does not satisfy the access frequency threshold condition. On the other hand, the user corresponding to the user ID having a value other than “0” in any one of the presence / absence of access and the information on the number of accesses from 30 days ago to at least once within the last 30 days It can be determined that the user has accessed the game server 1 and is not an inactive user.

For management of inactive users, as shown in FIG. 9C, as information stored and managed for each user ID by the access information storage control unit 55a of the access management means 55, the last access time of each user or active A flag may be included. Since the user's last access time indicates the length of the period during which the user has never accessed the game server 1 (the period from the last access time to the current time), the CPU 11 of the game server 1 determines the last access time. It is also possible to determine whether or not the user is an inactive user who does not satisfy the access frequency threshold.

The active flag is 1-bit information indicating whether the user is an active user or an inactive user. A user whose active flag is “1” is active, and the flag is “0”. The user is an inactive user. The access management means 55 sets an active flag based on the determination as to whether or not the user is an inactive user. And the fellow access average calculation means 60 extracts the fellow user of the object which calculates a fellow access average with reference to this active flag (namely, excludes an inactive user), and calculates the fellow access average of each user. be able to.

The fellow support access determination means 156 of the present embodiment compares the fellow access average calculated by the fellow access average calculation means 61 with a predetermined threshold, and the fellow access average exceeds a threshold (for example, 0.8). It is determined that the support access condition is satisfied.

The threshold value compared with the peer access average may be a fixed value, but may be a value that varies according to the overall access frequency as follows. That is, an overall access average that is an average value of access frequencies for all users who receive the game service is calculated, and a value obtained by adding a predetermined value (for example, 0.2) to the overall access average is set as a threshold value. For example, when the calculated overall access average is 0.6, the threshold value is 0.8 (= 0.6 + 0.2). Here, as the overall access average, the access average value of each user calculated by the access average calculating means 60 can be used. When calculating the overall access average, the access average calculation means 60 calculates the above-mentioned access average value of each user for all users. When calculating the overall access average, it is desirable to exclude users who started or stopped the game service in the middle of the access average calculation period from the calculation target because they do not satisfy the periodical condition for calculating the access average. . In addition, the above-mentioned inactive users may be excluded from the calculation target of the overall access average.

An example of processing of the game server 1 of the present embodiment is shown in the flowchart of FIG. In addition, about the process similar to the flowchart shown in FIG. 15 or FIG. 18, the same step number is attached | subjected and the description is abbreviate | omitted suitably.

S31, S32, and S81 are the same processing as in FIG. If the previous day's lack of access by the user is not the third day of missing access that occurred in the middle of five consecutive days, that is, the missing day of the first or second day (NO in S81), It shifts to the determination process (process after S91) whether the said user's associate is satisfying support access conditions. In S91, the access average calculation means 60 calculates the access average for 7 days until the day before the missing date for each of the fellow users who have lost access. Thereafter, the fellow access average calculating means 61 calculates the fellow access average AVA of the users who have lost access based on the access average of each fellow user calculated by the access average calculating means 60 (S92). Thereafter, in S82, a branching process for changing the support access condition is performed depending on whether or not the missing date is the first day.

If the missing date is the first day (YES in S82), it is determined whether or not the calculated fellow access average AVA satisfies the support access condition of, for example, 0.8 or more (S93). On the other hand, when the missing date is not the first day but the second day (NO in S82), the calculated peer access average AVA is 0.9 or more, for example, so as to be a stricter support access condition than the first day It is determined whether or not (S94). If the support access conditions are satisfied (YES in S93 or S94), the game server 1 considers that the user has accessed the game server 1 on the previous day, and performs continuous access continuation processing (S36). On the other hand, when the support access condition is not satisfied (NO in S93 or S94), the user's continuous access is interrupted, and the process proceeds to S40, where the continuous access days are initialized to “0 days”. Note that S37 to S39 are basically the same processes as those described in the flowchart of FIG.
In the flowchart of FIG. 21, an example is shown in which the maximum number of missing days that can be compensated is 2 days, but the missing date that can be compensated may be one day or three days or more.

In the above description, the example in which the peer access average is applied as the evaluation value of the group of the user friends who have missing days in five consecutive days has been described. However, the evaluation value of the group is not limited to this. For example, the evaluation value of the group may be the total value of the access frequencies of the fellow users, or may be the maximum value or the minimum value of the access frequencies among the fellow users. When the group evaluation value is set to the total value, the maximum value, or the minimum value as described above, for example, the access average of each fellow user calculated by the access average calculation unit 60 is used as a value indicating the access frequency. The total value, maximum value, or minimum value of the access averages of the fellow users can be obtained.

When the above maximum or minimum value is applied as the group evaluation value, the access frequency of one person in the group is the value representing the group, whereas the peer access average or total value is used as the group evaluation value. In this case, since the access frequency of all members in the group is reflected as the evaluation value, it can be said that it is preferable to use the peer access average or the total value as the evaluation value of the group. In other words, considering the case where the evaluation value of the group is the maximum value of the access frequency in the group, even if there are many users who are not frequently accessed in the group, even if there is only one fellow user who is frequently accessed in the group If it exists, the evaluation value of the group will be high. In this case, the user does not try to increase the access frequency of his / her entire group, but the group evaluation value is obtained by encouraging support access to only a few specific group users who have a relatively high access frequency than usual. There is a possibility to increase. On the other hand, the access frequency of many fellow users in the group is increased in order to increase the evaluation value by setting the evaluation value of the group to the average value (average access of peers) or the total value of the access frequencies in the group. As the need arises, the user can be motivated to communicate with many fellow users in the group.

In addition, when the above total value is applied as the evaluation value of the group, the total value tends to increase as the number of friends (number of groups) increases, so the access frequency of each fellow user in the group is so high. Even if the number of groups is large, the evaluation value of the group may increase as a result. On the other hand, by setting the group evaluation value to the average value of the access frequency within the group (friend access average), the high access frequency of all the members can be accurately determined regardless of the number of fellow users in the group. Since it is reflected as an evaluation value, it can be said that it is more preferable to use the peer access average as the evaluation value of the group.

In addition, when the above total value is applied as the evaluation value of the group, it is desirable to increase the reference value (threshold value) compared with the evaluation value as the number of fellow users belonging to the group increases. As a result, simply increasing the number of friends will not satisfy the support access conditions, and in order to increase the evaluation value, it will be necessary to increase the access frequency of the entire group, so users can communicate with many fellow users in the group. Can be motivated to try.

As described above, the game server 1 according to the present embodiment calculates the evaluation value of the group centered on the user based on the access frequency of the fellow user of the user who has the missing date (missing unit period). A value calculation means is provided, and the support access condition is that the evaluation value exceeds a threshold value. By setting such support support conditions, in order for the user's fellow users to satisfy the support access condition, it is necessary to increase the evaluation value of the group by increasing the access frequency of the fellow users. Therefore, each user is motivated to actively communicate with his / her fellow users in an attempt to increase the frequency of access of fellow users belonging to the group. Thereby, activation of the whole game community can be aimed at.

In addition, in order for a friend to satisfy the support access condition by setting the evaluation value (e.g., peer access average) of the group during the predetermined period immediately before the missing date (missing unit period) to exceed the threshold, the support access condition It is necessary to increase the access frequency of the companion during the predetermined period immediately before the missing date, not the access of the companion on the missing date. Therefore, in order to satisfy the support access condition, each user is given a consciousness and motivation to increase the access frequency with each other.

[Another configuration example of the game management device]
Next, another configuration example of the game management device will be described with reference to the functional block diagram of FIG. Note that the same components as those shown in the above-described drawings (FIGS. 1 to 21) are denoted by the same member numbers, and description thereof will be omitted as appropriate.

As described above, in this game system, even if there is a day (missing date) when the user cannot access the game server 1, the missing date is compensated for by the fellow user satisfying the support access condition, and continuous access is achieved. Benefits can be earned. Therefore, when it is known that the user cannot access the game server 1 in advance, the user notifies his / her friend of the scheduled date of inaccessibility and requests the friend in advance for cheering access so as to satisfy the cheering access condition. You can also. Since the game server 1 having the configuration illustrated in FIG. 4 or FIG. 19 includes the message transmission unit 59, the user cannot access his / her peers via the message transmission unit 59. You can send a message with However, if the number of friends is large, it takes time and effort to send a message describing the inaccessible scheduled date to each of the user's friends. Therefore, in the game system according to the present embodiment, if the user transmits information on the scheduled date of inaccessibility to the game server 1 only once, the game server 1 informs all of the user's allies information on the scheduled date of inaccessibility. A configuration for transmitting the signal will be described. This configuration can be applied to any of the game servers 1 illustrated in FIG. 4 or FIG. 19 described above, or to the game server 1 described later. Hereinafter, an example in which the configuration is applied to the game server 1 of FIG. Will be described.

As shown in FIG. 22, the game server 1 (game management apparatus) according to the present embodiment has a scheduled date transmission means 62 (inaccessible scheduled date transmission means) in addition to the means 51 to 59 shown in FIG. Is further provided. This scheduled date transmission means 62 receives the information on the scheduled date of inaccessibility transmitted from the terminal device 3 of the user whose schedule for which access is not possible is known in advance, and the information on the scheduled date of inaccessibility of the user. It has the function to transmit to all the associate users the terminal device 3, and to transmit the said inaccessible scheduled date to all the associate users. The scheduled date transmission means 62 is realized by the CPU 11 of the game server 1 executing the program according to the present embodiment.

The scheduled date transmission means 62 includes a scheduled date information storage control unit 62a. FIG. 23 shows an example of scheduled date information that is stored and managed in the database server 2 by the scheduled date information storage control unit 62a. The scheduled date information storage control unit 62a stores the transmission information and the reception information on the scheduled date of inaccessibility in a predetermined storage area of the database server 2 for each user ID in association with the user ID. The transmission information of the scheduled inaccessible date is information transmitted from the user's terminal device 3, and in the example of FIG. 23, in addition to the “scheduled inaccessible date” that the user notifies his fellow user, Information on “message contents” addressed to fellow users is included. Further, the user ID on the scheduled date transmission side is stored as the reception information on the scheduled date that cannot be accessed. If the user ID on the scheduled date transmitting side is stored in association with the user ID on the scheduled date receiving side, the scheduled date transmission information (“access not allowed” stored in association with the user ID on the scheduled date transmitting side is stored. Possible date ”and“ message content ”). Therefore, it is only necessary to store only the user ID on the scheduled date transmission side as the reception information of the scheduled access date.

In the example of FIG. 23, the scheduled date information for one user with the user ID = “000001” is shown, and the user sets the scheduled date of inaccessibility = “2011/1/15”, “Request for support access”. The message is sent to all of your fellow users. In addition, the user with the user ID = “000001” has received information on the scheduled date of inaccessibility from the two fellow users with the user ID = “000002” and the user ID = “000110”. Specific scheduled date information received from these two fellow users (“unscheduled scheduled access date” and “message content”) is stored in association with the user IDs of the two fellow users. It can be acquired by referring to the transmission information.

Here, an example of an operation in which a user notifies his / her fellow user of an inaccessible scheduled date will be described. FIG. 24 shows an example of a “not-accessible scheduled date notification screen” displayed on the user terminal device 3 based on the screen data transmitted from the game server 1. This screen is a screen that is displayed when, for example, the user operates the terminal device 3 to select the “not-accessible scheduled date notification menu” in the main screen. This inaccessible scheduled date notification screen is provided with an input area 201 that allows the user to easily enter the inaccessible scheduled date.

An example of this input area 201 is a pull-down menu (pull-down list). When the cursor is placed on the input area 201 and the enter button of the terminal device 3 is pressed, a list of selection items of “Tomorrow”, “2 days later”,... “5 days later” is displayed as illustrated in FIG. Make it appear hanging down. In this example, the inaccessible scheduled date from tomorrow to 5 days later can be selected and input. However, the present invention is not limited to this, and it can be selected and input until n days later (n is a positive integer). Also good. Further, instead of “Tomorrow” or the like, a specific “Date (Monday)” may be displayed as a selection item. As another example of the input area 201, a plurality of selection items from tomorrow to n days later may be displayed in a list together with radio buttons so that one of the selection items can be selected and input with the radio buttons. Alternatively, the user may be able to directly input the date of the inaccessible scheduled date into the input area 201 in text format.

In addition, objects such as a message input area 202 and a send button 203 are also displayed on this inaccessible scheduled date notification screen. Then, the user operates the terminal device 3 to input an arbitrary message in the message input area 203 and selects the send button 203, so that messages addressed to all the friends are not accessible from the terminal device 3. It is transmitted to the game server 1 together with the date information. FIG. 24 shows an example in which the user inputs the message “Please support us!”. In consideration of the storage capacity in the database server 2, there may be a restriction (for example, within 30 full-width characters) on the characters that can be input in the message input area 202. In addition, when the user inputs an inaccessible scheduled date in the input area 201 and presses the send button 203 without inputting a message in the message input area 202, only the inaccessible scheduled date is transmitted to all the friends. Will be. Moreover, you may display the hyperlink 204 for changing to a buddy list screen, the hyperlink 205 for changing to a main screen, etc. on the inaccessible scheduled date notification screen.

When information such as an inaccessible scheduled date is transmitted from the terminal device 3 by a user operation on the inaccessible scheduled date notification screen, the game server 1 in the game server 1 has a scheduled date information storage control unit 62a. However, the information received from the user terminal device 3 (“scheduled date of inaccessibility” and “message content”) is stored in the database server 2 in association with the user ID of the user (see FIG. 23). Further, the scheduled date information storage control unit 62a stores the user ID on the scheduled date transmission side in association with the user ID of each fellow user for all the fellow users of the users who have transmitted the scheduled date (FIG. 23). reference).

Then, when the terminal device 3 of the fellow user who has received the notification of the scheduled date accesses the game server 1, the scheduled date transmission means 62 of the game server 1 is stored in association with the user ID on the scheduled date transmission side. Screen data for displaying “scheduled inaccessible date”, “message content”, and the like is transmitted to the terminal device 3 of the fellow user. Thereby, for example, the fellow information screen shown in FIG. 25 is displayed on the terminal device 3 of the user who has received this screen data, so that the user can check the scheduled access date of other fellows on the screen. It has become. This fellow information screen is a screen displayed on the display unit 35 of the terminal device 3 as a part of the main screen of the game or as another screen linked to the main screen. In the screen example of FIG. 25, the avatar 206 of the user who has transmitted the inaccessible scheduled date, the user name 207, the inaccessible scheduled date 208, and a message 209 are displayed as support access request information from a friend. Note that information about friends who cannot be displayed on the screen can be displayed by scrolling the screen. Moreover, this friend's support access request information can be confirmed on the screen of the terminal device 3 of the friend user who received the support access request until the inaccessible scheduled date elapses.

As described above, in the game system of the present embodiment, the communication tool as illustrated in FIG. 24 is used so that the user can notify the friend of the inaccessible scheduled date by a simple operation. In the present embodiment, the user can transmit the inaccessible scheduled date and the original message to all of his / her friends only by performing an operation of transmitting the inaccessible scheduled date to the game server 1 only once. This is possible, and the operation on the user side is facilitated. In particular, the configuration of the present embodiment is suitable for a game service such as a social game that requires strong user operation.

By the way, it is determined whether or not the support access condition is satisfied, every time a lack of access occurs for a user who has never accessed the game server 1 once a day (access within the unit period has not been achieved). It is a process performed. As the number of registered game service users managed by the game server 1 increases, the number of users who cause access loss increases, so the processing load on the game server 1 increases. For example, even if about 10% of 1 million game service use registrants have lost access, the process of determining whether or not the support access condition is satisfied for about 100,000 users is executed. Will be. The determination process of whether or not the support access condition is satisfied is not a process performed by the user requesting the game server 1 to execute the game, but a negative fact that the user has not accessed the game server 1. Therefore, it is also a process to be executed with the processing load of the game server 1 reduced as much as possible.

Therefore, the fellow support access determining means 56 shown in FIG. 22 accesses the same date as the scheduled date of inaccessibility after the user has transmitted the scheduled date of inaccessibility to the fellow user in advance by the scheduled date transmitting means 62. Only when there is not, you may make it determine whether the fellow user of the said user satisfy | fills support access conditions. In other words, the advance notification of the inaccessible scheduled date for the fellow user is made an indispensable condition for receiving a determination as to whether or not the support access condition is satisfied. A case where this is applied to the processing of the flowchart of FIG. 15 is illustrated in the flowchart of FIG.

That is, if it is the start time of the process after the end of one day (unit period) in the real world (YES in S31), first, is the previous day an inaccessible scheduled date notified in advance from the user to the fellow user? It is determined whether or not (S101). If the previous day is an inaccessible scheduled date (YES in S101), the routine proceeds to a routine of S32 to S40 including a determination process (S34 and S35) as to whether or not the support access condition is satisfied. On the other hand, when the previous day is not an inaccessible scheduled date (NO in S101), the process of the flowchart of FIG. 26 is terminated without shifting to a routine including a process for determining whether or not the support access condition is satisfied.

As described above, the game server 1 makes the advance notification on the scheduled inaccessible date a condition for executing the process for determining whether or not the support access condition is satisfied. Since the determination process of whether or not the support access condition is satisfied and the subsequent process when the condition is satisfied are performed, the processing load on the game server 1 can be greatly reduced.

In addition, for the user, if the game server 1 is not accessed on the day when the scheduled date of inaccessibility to the fellow user is not notified in advance, it is not possible to receive a determination as to whether or not the support access condition is satisfied. Therefore, the missing date will not be compensated. Therefore, when a day that is unlikely to be accessible is scheduled, each user will make an advance request for support access by actively notifying the fellows of the scheduled date of inaccessibility, thereby Activation of communication.

[Another configuration example of the game management device]
Next, another configuration example of the game management device will be described with reference to the functional block diagram of FIG. Note that the same components as those shown in the above-described drawings (FIGS. 1 to 26) are denoted by the same member numbers, and description thereof will be omitted as appropriate.

In the present embodiment, a configuration will be described in which when a continuous access achievement privilege is given to a user by a friend's support access, some advantage is also given to the friend who has contributed to the support access. This configuration can be applied to any of the game servers 1 illustrated in FIG. 4, FIG. 19, or FIG. 22, or to the game server 1 described later. An applied example will be described.

As shown in FIG. 27, the game server 1 (game management apparatus) according to the present embodiment further includes support access privilege granting means 63 in addition to the means 51 to 59 shown in FIG. This support access privilege granting means 63 is a friend user of a user who has been granted a continuous access achievement privilege when a fellow user of a user who has a missing date (missing unit period) satisfies the support access condition. It has the function to give the support access privilege by changing the game information of the said fellow user so that it may become advantageous on a game with respect to the fellow user who performed the access which satisfy | fills conditions. This support access privilege provision means 63 is implement | achieved when CPU11 of the game server 1 runs the program which concerns on this Embodiment.

Here, the support access privilege given to the fellow user who has contributed to the support access only needs to be advantageous in terms of the game as compared to the case where the privilege is not given, and is similar to the continuous access achievement privilege. Various benefits can be applied according to the type and content of the game. However, with regard to the size of the privilege (degree of merit), the support access privilege given to fellow users who helped to achieve continuous access rather than the continuous access achievement privilege given to users who achieved continuous access It is desirable to have a small benefit. For example, if the continuous access achievement privilege is an enhancement point for 200 points, the support access privilege is an enhancement point for 50 to 100 points. Further, for example, the type of privilege may be changed between the continuous access achievement privilege and the support access privilege such that the continuous access achievement privilege is set to three recovery items and the support access privilege is set to one fake card.

Next, the operation of the game management device (game server 1) of the present embodiment will be described with reference to the flowchart of FIG. FIG. 28 shows a flow of processing executed for a group called a friend centered on one user, and the same applies to a group centered on each user managed by the game server 1. Is performed.

If a certain user is granted a continuous access achievement privilege (S111), whether the user has achieved continuous access without making up for missing days, or missing due to peer support even though there was a missing day of access It is determined whether continuous access has been achieved by making up for the day (S112). This determination can be made based on the access information illustrated in FIG. 9A that is stored in association with the user ID (information indicating the presence or absence of daily access and support access condition achievement).

Here, if the user has achieved continuous access without making up for missing days (NO in S112), the routine shown in FIG. 28 is terminated without performing the process of giving the support access privilege to the fellow user of the user. . On the other hand, when the user has achieved continuous access by making up for the missing date (YES in S112), the support access privilege granting means 63 of the game server 1 contributes to make up for the missing date, ie, support. A fellow user who has made access satisfying the access conditions is extracted (S113).

The extraction process of the fellow users in S113 is when the support access condition is “the number of fellow users who accessed the game server 1 on the same day as the missing date or the ratio of the whole fellow users exceeds the threshold”. It can be realized as follows. That is, the access information illustrated in FIG. 9A in which the fellow users who have accessed the game server 1 are stored in association with the user ID on the same day as the missing date when the support access condition is satisfied (the presence or absence of daily access) Information).

In addition, when the support access condition is “the evaluation value of the group of users who have missing days exceeds the threshold value”, the extraction process of S113 can be realized as follows. For example, when the evaluation value of the group is a fellow access average and the threshold is 0.8, a fellow user having an access average of 0.8 or more is extracted.

Moreover, when the evaluation value of the group is the total value of the access frequency of the fellow users, since the fellow users whose access frequency is not 0 contributed to satisfy the support access condition, all the fellow users whose access frequency is not 0 are all included. It may be extracted. However, since the degree of contribution varies greatly depending on the frequency of access, a friend user with a higher access frequency may have a higher support access privilege. Moreover, you may exclude from the extraction object of S113 about the fellow user whose access frequency whose degree of contribution is very low is below a predetermined value.

In addition, when the evaluation value of the group is “the maximum value of access frequency in the group”, only the fellow users having the maximum value are extracted. In this case, since there is only one fellow user to be extracted and the degree of contribution is large, the support access privilege may be increased as compared to other support access conditions. In addition, when the evaluation value of the group is “the minimum value of the access frequency within the group”, all the fellow users have contributed to satisfy the support access condition, so all the fellow users may be extracted. .

After S113, the support access privilege granting means 63 changes the extracted game information of the fellow users and gives the support access privilege so as to be advantageous in the game (S114). For example, when a predetermined strengthening point is given to a fellow user as a support access privilege, game information corresponding to the user ID of the fellow user (information on the strengthening point of the user illustrated in FIG. 6) is changed.

Screen data for notifying the user that the privilege is granted to the user when the terminal device 3 of the user first accesses the game server 1 after the privilege is granted. Is transmitted to the terminal device 3 of the user. Thereby, the user can recognize that the fellow has acquired the continuous access achievement privilege by his support access, and that the support access privilege has been given to himself.

As described above, when a fellow user of a user with a missing date is granted a continuous access achievement privilege by satisfying the support access condition, the support access privilege is also given to the fellow user who has contributed to the support access. Thus, each user is provided with awareness and motivation to actively support his / her friends.

Next, when there are more than a predetermined number or more than a predetermined percentage of fellow users who have acquired a continuous access achievement privilege in a group of friends centered on the user, a configuration that allows the user to be further merited explain. This configuration can be applied to any of the game servers 1 illustrated in FIG. 4, FIG. 19, or FIG. 22, or to the game server 1 described later. An applied example will be described.

As shown in FIG. 27, the game server 1 (game management apparatus) according to the present embodiment further includes fellow privilege granting means 64 in addition to the means 51 to 59 shown in FIG. This fellow privilege granting means 64 is advantageous in terms of the game with respect to the user who has a certain number of fellow users or more than a predetermined ratio to which the continuous access achievement privilege is given in a group of fellows centered on the user. It has a function to change the game information of the user so as to give a fellow privilege. This fellow privilege grant means 64 is implement | achieved when CPU11 of the game server 1 runs the program which concerns on this Embodiment.

Here, in determining the number or ratio of fellow users who have been granted the continuous access achievement privilege within the group centered on each user, the central user may be included, or the central user is excluded. May be. In addition, about the user who does not make any associate, since the group itself called the associate centering on the said user does not exist, the associate privilege is not provided.

Here, the fellow benefits only need to be advantageous in terms of the game as compared to the case where the benefits are not given, and various benefits depending on the type and content of the game, as with the continuous access achievement privilege. Can be applied. Since this fellow privilege is a privilege that has a high degree of difficulty in which it is necessary to have a certain number of fellow users who have acquired the continuous access achievement privilege in their fellow group or more than a predetermined ratio, the size of the privilege ( About the degree of merit), it is also possible to make the benefit the same or larger than the continuous access achievement privilege given to the continuous access achievement user. For example, when the continuous access achievement privilege is an enhancement point for 200 points, the fellow privilege is an enhancement point for 200 to 300 points. In addition, for example, while the continuous access achievement privilege is set as an enhancement point for 200 points, the type of privilege may be changed between the continuous access achievement privilege and the fellow privilege, such as three recovery items.

As an example of applying this companion benefit, it can be applied to the above-mentioned limited-time in-game event. That is, a continuous access achievement privilege is given to those who have achieved continuous access during the event period, and the number of fellow users who have acquired the continuous access achievement privilege within the group during the event period is equal to or greater than a predetermined number or a predetermined ratio A fellow privilege is granted to the above users.

In addition, even during normal times when no in-game event is held for a limited period of time, a fellow user who has determined a predetermined period (for example, every Monday to Sunday) and has acquired a continuous access achievement privilege within the group during the period. You may give a fellow privilege to a user who has more than a predetermined number or a predetermined ratio.

Next, the operation of the game management device (game server 1) of the present embodiment will be described with reference to the flowchart of FIG. FIG. 29 shows the flow of processing executed for one user, and the same processing is performed for each user managed by the game server 1.

When a predetermined period for determining whether or not to give a friend privilege is over (S121), the game server 1 determines whether or not a friend exists in the user (S122). Here, when the user has not made any buddies (NO in S122), the game server 1 ends the process without determining whether or not to give the buddies benefits to the user. On the other hand, when the user has a friend (YES in S122), the friend privilege granting means 64 of the game server 1 achieves continuous access by the friend information of the user managed by the fellow management means 53 and the continuous access privilege giving means 57. Based on the information (privilege information illustrated in FIG. 6) that gives the privilege to the user, the number or ratio of fellow users who have been granted the continuous access achievement privilege within the group centered on the user is determined (S123). In addition, in FIG. 29, the example which calculates | requires the number N of fellow users is shown.

Thereafter, the fellow privilege granting means 64 determines whether or not the number N of people obtained in S123 is equal to or greater than a predetermined threshold value (an example in which the threshold value is 10 is shown in FIG. 29). Here, if the number N is smaller than the threshold (NO in S124), the process ends without giving the fellow benefits to the user. On the other hand, when the number N is equal to or greater than the threshold (YES in S124), the fellow privilege granting means 64 changes the game information of the user so as to be advantageous in terms of the game, and grants the fellow privilege (S125). For example, when a predetermined strengthening point is given to a user as a fellow benefit, game information corresponding to the user ID of the user (information on the strengthening point of the user illustrated in FIG. 6) is changed.

When the user's terminal device 3 accesses the game server 1 for the first time after granting the privilege, screen data for notifying that the privilege has been granted from the game server 1 is given to the user who has been granted the fellow privilege. To the terminal device 3 of the user. Thereby, the user can recognize that the fellow privilege was provided because the fellow user who acquired the continuous access achievement privilege was more than the threshold in his / her fellow group.

As described above, in the present embodiment, when there are more than a predetermined number of users or a predetermined percentage of fellow users who have acquired a continuous access achievement privilege in a group of friends centered on the user, the user is given a fellow privilege. Is provided. Combined with the configuration that this companion makes it easy for friends to acquire continuous access achievement benefits by making up for missing days due to support access, each user can acquire continuous access achievement benefits for each user. In this way, awareness and motivation to increase the access frequency are given. In other words, there is a chance to acquire not only continuous access achievement benefits but also fellow benefits, so that many fellow users can acquire continuous access achievement benefits as well as to obtain continuous access achievement benefits. In addition, the user is motivated to increase the frequency of access to the game server 1. In addition, even for users who have lost continuous access halfway and can no longer obtain the continuous access achievement privilege, there is a chance that many of their own fellow users will acquire the continuous access achievement privilege. Therefore, in order that many fellow users can acquire a continuous access achievement privilege by support access, the user is motivated to increase the access frequency to the game server 1.

[Another configuration example of the game management device]
Next, another configuration example of the game management device will be described with reference to the functional block diagram of FIG. Note that the same components as those shown in the previous drawings (FIGS. 1 to 29) are denoted by the same reference numerals, and the description thereof is omitted as appropriate. The configuration of the present embodiment can be applied to any of the game servers 1 illustrated in FIG. 4, FIG. 19, FIG. 22, or FIG. 27, or the game server 1 described later. An example in which this configuration is applied to the game server 1 will be described.

As shown in FIG. 30, the game server 1 (game management apparatus) of the present embodiment further includes an access frequency display control means 100 (display control means) in addition to the means 51 to 59 shown in FIG. ing. The access frequency display control unit 100 transmits screen data (display control information) including information on the access frequency of another user to the terminal device 3 of the user who has received the access, whereby the screen of the user terminal device 3 is displayed. And a function for displaying the access frequency of other users. This access frequency display control means 100 is realized by the CPU 11 of the game server 1 executing the program according to the present embodiment.

In this game system, when a lack of access occurs, it is determined whether or not the missing date will be compensated depending on the support access by the user's peers. The information on the access frequency of the user is important. Therefore, the access frequency display control unit 100 of the present embodiment displays information on the access frequency of other users on the screen of the user terminal device 3 as information for the convenience of each user. Yes.

Here, as an example of a screen on which the access frequency of other users is displayed, there is a fellow candidate list screen as shown in FIG. This friend candidate list screen is one of the game screens transmitted from the game server 1 when a user who wants to make a friend performs a game operation to search for a friend candidate with his / her terminal device 3. On this friend candidate list screen, a plurality of users extracted by the game server 1 and not yet in a friend relationship with the user are listed and displayed as friend candidates. In addition, about the information of the fellow candidate user who cannot be displayed on the screen, the screen can be displayed by scrolling, or the second and subsequent pages of the fellow candidate list can be requested from the game server 1 and displayed as a separate screen. . In the friend candidate list screen, an information display area for each user of the listed friend candidates is provided. In each information display area, game information 111 (user name, team name, user's name of the friend candidate user) is provided. Level, number of friends, league level, etc.), the avatar 112 which is a separate character of the fellow candidate user, the player card 113 of the leader owned by the fellow candidate user, and the access frequency 114 of the fellow candidate user are displayed. The

The user confirms information of other users listed on this friend candidate list screen, and finds a user who wants to apply for a friend. Moreover, if operation which selects the hyperlink 111a of a user name is made on this friend candidate list screen, for example, the game server 1 will respond to the said operation, and the more detailed game information (for example, about the user of the said user name) Screen data for displaying the ability value of the player card 113 of the leader) is transmitted to the terminal device 3. This screen data includes a friend application button and an ale button (or their hyperlinks), and the user can operate the terminal device 3 to send a friend application and a message.

Here, the information of the access frequency 114 displayed on the screen can be, for example, the value of the user's access average (for example, the access average for the most recent 7 days) during a predetermined period. In this embodiment, as illustrated in FIG. 9A or FIG. 9B, the access information storage control unit 55a of the access management means 55 stores information on the presence / absence of access up to Bn days ago for each user ID. Therefore, the access average for the last n days can be calculated from this information, and the calculated access average can be used as the information of the access frequency 114 displayed on the screen.

The information on the access frequency 114 displayed on the screen is not limited to the access average for the last n days, for example, the access average for the last week, the access average for the last month, the total access count for the last n days, and the total access for the last week. Any information may be used as long as it indicates the past access frequency of the user, such as the number of times and the total number of accesses last month. Alternatively, the information of the access frequency 114 may be displayed in a multi-level display, for example, in three levels A to C (A: many accesses, B: normal access, C: few accesses).

Thus, in this Embodiment, when the user tries to make a friend, the past access frequency of each user to be listed is displayed on the friend candidate list screen displayed on the display unit 35 of the terminal device 3. . Thereby, the user can see another user's access frequency on a screen, and can use it as one standard at the time of making a friend. In other words, in the present embodiment, in order to satisfy the support access condition by the fellow when lack of access occurs, it is desirable that the access frequency of the fellow is high, so one guideline when the access frequency creates the fellow It becomes.

In addition to the information on the access frequency, information indicating the level and ability of each user (user level, league level, etc.) is also displayed on the fellow candidate list screen. According to the above configuration, When a user decides whether or not to make another user a friend, he considers not only the level and ability of the user, but also the access frequency, and comprehensively judges these, Users can be selected.

In addition, even for a user who has received a friend application, an access frequency is displayed on the screen (not shown) of the terminal device 3 of the user as one piece of information of the user who has applied for the friend. Can also be used as a guide for determining whether to approve a fellow application.

Another example of the screen displaying the access frequency of other users is a friend list screen as shown in FIG. As described above, information of fellow users who are in a fellow relationship with the user is listed and displayed on the fellow list screen. On this buddy list screen, game information 81 of the buddy user (user name, team name, user level, number of buddy, level of affiliation, etc.), avatar 82, player card 83 of the owned leader, ale button 84, etc. At the same time, the access frequency 114 of the fellow user is displayed. As described above, the access frequency 114 may be any information that indicates the user's past access frequency. For example, the access frequency 114 may be an average of access over the last n days of the user.

Thus, by displaying the access frequency 114 of the fellow user on the fellow list screen, the following usage is also possible. That is, it is desirable to increase the access frequency of all the fellow users who belong to their own group so that the fellows can satisfy the support access condition when access is lost. Therefore, it is efficient by grasping a fellow user with a low access frequency based on the access frequency 114 displayed on the fellow list screen and sending a support message to the fellow user to increase the access frequency. The access frequency of the entire group can be increased.

Here, in order to further facilitate understanding of the access frequency 114 of each fellow user, a display order change button (in order to rearrange the display order on the fellow user's screen in order from the one with the lowest access frequency (or one with the highest access frequency)) ( Other selectable objects) may be displayed on the terminal device 3 of the user. When an operation for selecting the display order change button is performed on the terminal device 3 of the user, the screen data in which the game server 1 rearranges the fellow users in order from the one with the lower access frequency (or the higher one) according to the operation. Is transmitted to the terminal device 3. Since the user 3 arranged in order of access frequency is displayed on the terminal device 3 that has received this screen data, the user can quickly grasp the user whose access frequency is low, and promptly support the user in question. Messages can be sent.

[Another configuration example of the game management device]
Next, still another configuration example of the game management device will be described with reference to the functional block diagram of FIG. In addition, the same member number is attached | subjected about the structure similar to the structure shown in previous drawing (FIGS. 1-32), and the description is abbreviate | omitted suitably.

In the present embodiment, a game system is described in which part or all of the friend registration of a user can be canceled based on the user's intention. In order to increase the possibility of making up for the missing date when the user loses access (to increase the possibility that the fellow user satisfies the support access condition), the access frequency of the fellow user in his / her group is high. However, when the user can freely cancel the friend registration, the following situation is also conceivable. That is, instead of trying to increase access frequency by sending a support message to fellow users with low access frequency, try to increase the possibility of missing days by canceling the friend registration of fellow users with low access frequency Therefore, there is a possibility that a user who tries to adopt a method far from the original purpose appears. Therefore, as a countermeasure, in the present embodiment, as described below, when the user cancels the friend registration, the continuous access achievement privilege is hardly given by tightening the support access condition for a certain period from the cancellation. Or a configuration that reduces the continuous access achievement privilege originally obtained. This configuration can be applied to any of the game servers 1 illustrated in FIG. 4, FIG. 19, FIG. 22, FIG. 27, or FIG. 30, but an example in which this configuration is applied to the game server 1 of FIG. Will be described.

As shown in FIG. 33, the game server 1 (game management apparatus) of the present embodiment further includes a privilege grant adjusting means 121 in addition to the means 51 to 59 shown in FIG. Moreover, the friend management means 53 of this Embodiment is further provided with the friend registration cancellation | release means 122. FIG. The privilege grant adjustment means 121 and the friend registration cancellation means 122 are realized by the CPU 11 of the game server 1 executing the program according to the present embodiment.
The fellow registration cancellation unit 122 has a function of accepting cancellation of fellow registration from each user. An example of the operation of the friend registration cancellation means 122 is shown below.

For example, when the user A (user ID = “000001”) operates the terminal device 3 and performs an operation to cancel the registration of the fellow user B (user ID = “000002”), the communication data ( Request) is transmitted to the game server 1. In the game server 1 that has received the communication data, the fellow registration cancellation unit 122 cancels the fellow registration between the user A and the user B.

That is, the fellow registration release means 122 is stored in association with the user ID of user A = “000001” for the fellow information for each user illustrated in FIG. 34A stored in the fellow information storage control unit 53a. The user ID of user B = “000002” is deleted from the information field of the fellow user ID (in the figure, this is indicated by a double strikethrough for convenience). Furthermore, the fellow registration cancellation unit 122 records the fellow registration cancellation information in association with the user ID of the user A = “000001”. The friend registration cancellation information recorded here includes the user ID of the user B who is the cancellation partner = “000002”, information on the cancellation date and the cancellation person flag, and the like. The canceler flag is information for distinguishing between the side where the friend registration is canceled as “1” and the canceled side as “0”, for example. In the example of FIG. 34A, since the user A is the side on which the friend registration is canceled, the canceler flag = 1 is set.

Further, as shown in FIG. 34B, the fellow registration cancellation unit 122 also reads the user ID of the user A = “from the information storage column of the fellow user ID stored in association with the user ID of the user B =“ 000002 ”. “000001” is deleted (in the figure, this is indicated by a double strikethrough for convenience). Furthermore, the fellow registration cancellation unit 122 records the fellow registration cancellation information in association with the user ID of the user B = “000002”. The friend registration cancellation information recorded in this case is information such as the user ID of the user A who is the cancellation partner = “000001”, the cancellation date and the canceler flag = 0.

The game server 1 notifies the user A that the friend registration has been canceled when the terminal device 3 of the user B whose friend registration has been canceled accesses the game server 1 after the friend registration cancellation process. In addition, the game server 1 imposes a penalty such as reducing the number of owned points, for example, on the user A on the side of canceling the friend registration so that the user does not easily cancel the friend registration. May be.

Next, the privilege grant adjusting means 121 will be described. This privilege granting adjustment means 121 achieves continuous access with stricter support access conditions for a user who has canceled friend registration than when there is no cancellation of the friend registration for a predetermined period from the cancellation of the friend registration. It has a function of adjusting the provision of a privilege by making it difficult for a privilege to be granted, or by reducing the continuous access achievement privilege obtained by satisfying support access conditions. The processing example of the game server 1 provided with this privilege provision adjustment means 121 is shown in the flowchart of FIG.

35, S31 to S34 are basically the same processes as those described in the flowchart of FIG. After S34, it is determined whether or not the user has canceled the friend registration within a predetermined period, for example, within the last four weeks (S130). For example, as shown in FIG. 34A, the determination in S130 can be made based on the friend registration cancellation information (release date and releaser flag) of each user managed by the friend management unit 53. That is, a user who has canceled friend registration within 4 weeks has information on release date and releaser flag = 1 within 4 weeks as friend registration cancellation information associated with the user ID of the user. It is a user.

If the user has not canceled the friend registration within 4 weeks (NO in S130), it is determined whether or not the ratio R calculated in S34 satisfies the support access condition of, for example, 0.8 or more (S35). ). On the other hand, when the user cancels the friend registration within 4 weeks (YES in S130), the ratio R calculated in S34 is, for example, 0.9 or more so that the support access condition is stricter than S35. It is determined whether or not (S131). That is, the privilege grant adjustment means 121 sets the friend registration by setting the threshold value of the support access condition when the user cancels the friend registration within four weeks higher than when the user does not cancel the friend registration. It increases the difficulty of making up for missing days for users who cancel. The subsequent processing (S36 to S40) is basically the same processing as that described in the flowchart of FIG.

35. By the process illustrated in FIG. 35, the user who cancels the friend registration has more severe support access conditions than the case where the friend registration is not canceled for four weeks after the friend registration is canceled. As a result, even if you try to increase the possibility of making up for missing days by canceling fellow registration of fellow users with low access frequency, by canceling fellow registration, for a certain period (4 weeks in this example) As a result, it becomes difficult to obtain a continuous access achievement privilege when access is lost. Therefore, it is possible to effectively suppress the user from taking an action that is far from the original purpose, such as canceling the friend registration in order to increase the possibility of making up for the missing date.

Further, another processing example of the game server 1 provided with the privilege grant adjusting means 121 will be described below with reference to the flowchart of FIG.

36, S51 to S57 are basically the same processes as those described in the flowchart of FIG. When the number of continuous access days of the user has reached 5 days (YES in S56), the continuous access privilege giving means 57 changes the game information of the user so as to be advantageous in terms of the game and gives the continuous access achievement privilege. (S57). For example, 200 points of enhancement points are given to the user as bonus points.

After that, whether the user achieved continuous access without making up for missing days, or whether the user achieved continuous access by making up for missing days by peer support even though there was a missing day of access Determination is made (S141). Here, when the user has achieved continuous access by making up for the missing date (YES in S141), the privilege grant adjustment means 121 allows the user to register a friend within a predetermined period, for example, within the last four weeks. It is determined whether or not the release is performed (S142). Here, when the user cancels the friend registration within 4 weeks (YES in S142), the privilege grant adjustment means 121 gives the privilege for granting continuous access given to the user to the privilege granted in S57 ( For example, it is adjusted to 100 strengthening points (S143). The subsequent processing (S58 to S64) is basically the same processing as the processing described in the flowchart of FIG. 16, and the description thereof is omitted.

With the process shown in FIG. 36, the user who canceled the friend registration achieved the continuous access obtained by making up for the missing date for four weeks after canceling the friend registration, compared to the case where the friend registration was not canceled. Benefits are reduced. As a result, even if an attempt is made to increase the possibility of making up for missing days by canceling the friend registration of a friend user with low access frequency, by canceling the friend registration, a certain period of time (4 weeks in this example) is originally obtained. Only a privilege smaller than the continuous access achievement privilege that should be obtained can be obtained. Therefore, it is possible to effectively suppress the user from taking an action that is far from the original purpose, such as canceling the friend registration in order to increase the possibility of making up for the missing date.

In the above example shown in FIG. 35 and FIG. 36, it is difficult to give the continuous access achievement privilege itself, or the original continuous access is achieved, with 4 weeks from the cancellation of the friend registration as the penalty period for canceling the friend registration. The grant is adjusted by granting a privilege that is smaller than the privilege. However, the present invention is not limited to this. For example, the period may be shortened to about one to three weeks, and conversely It may be set longer than 4 weeks, and an arbitrary period can be set.

Further, in the above example, the example in which the grant adjustment of the continuous access achievement privilege by the privilege grant adjustment unit 121 is performed if even one person cancels the friend registration within the predetermined period is described, but the present invention is not limited thereto. Instead, for example, privilege adjustment adjustment may be performed only when n or more fellow registrations (for example, two or more within one week) are canceled within a predetermined period.

By the way, even if a user sends a cheer message to a fellow user with low access frequency and makes efforts to increase the access of the fellow member, the access frequency of the fellow user remains low, so the friend registration may be canceled unavoidably possible. Therefore, even when the user cancels the friend registration, if the user who has sent the message a predetermined number of times and removes the friend user who remains low in access frequency from the friend, the friend registration is canceled without sending such a message. In some cases, it is desirable to have different effects.

Therefore, the privilege grant adjusting means 121 of the game server 1 according to the present embodiment allows the user who canceled the friend registration during a predetermined period (for example, within two weeks before the cancellation) before canceling the friend registration. When a message is transmitted a predetermined number of times or more (e.g., twice or more) to a friend user to be canceled, the above-described privilege grant adjustment is not performed. A processing example of the game server 1 provided with the classic grant adjusting means 121 configured as described above is shown in the flowchart of FIG.

37, S31 to S34 are basically the same processes as those described in the flowchart of FIG. After S34, it is determined whether or not the user has canceled the friend registration within a predetermined period, for example, within the last four weeks (S150). The process of S150 is basically the same as S130 of FIG. Here, if the user has not canceled the friend registration within 4 weeks (NO in S150), it is determined whether or not the ratio R calculated in S34 satisfies the support access condition of 0.8 or more, for example. (S35).

On the other hand, when the user cancels the friend registration within 4 weeks (YES in S150), the privilege granting adjustment means 121 indicates that the user who canceled the friend registration is, for example, twice within two weeks before the cancellation. As mentioned above, it is judged whether the message is transmitted to the friend user of cancellation | release object (S151).

For the determination in S151, the fellow information storage control unit 53a of the fellow management means 53 stores, for example, each member's fellow registration cancellation information (stored in association with the user ID of each user shown in FIG. 34A). , Cancellation partner user ID, cancellation date and cancellation person flag), and the message storage control unit 59a of the message transmission means 59, for example, information relating to the message shown in FIG. 12 (corresponding to the user ID of the receiving user) The stored information such as the user ID of the transmission source and the transmission date / time is used. That is, the “cancellation target fellow user” for which the user has canceled the fellow registration can be specified as the “releasing partner user ID” in the fellow registration cancellation information shown in FIG. 34A. Further, the “period within two weeks before cancellation” can be specified based on the “release date” in the above-mentioned friend registration cancellation information. In addition, regarding “whether or not the user who canceled the friend registration has sent a message to the friend user to be released”, the “reception-side user ID” shown in FIG. It can be determined by checking whether or not the user ID of the user who canceled the friend registration is included as the “transmission source user ID”. In addition, since the information of “transmission date and time” is also stored together with the above “transmission source user ID”, a message from the user who canceled the friend registration to the friend user to be canceled is within two weeks before the cancellation. It is possible to determine whether or not the message has been transmitted to.

In S151, when the user who canceled the friend registration has not sent a message to the friend user to be canceled more than once within two weeks before the cancellation (NO in S151), the support is more severe than the S35. Whether or not the ratio R calculated in S34 is, for example, 0.9 or more so as to satisfy the access condition is determined (S131). That is, the privilege grant adjustment means 121 is a user who canceled the fellow registration by setting the threshold value of the support access condition to a value (0.9) higher than the threshold value (0.8) in S35. For users who have not sent a message to a friend user to be canceled more than once within two weeks before the cancellation, the support access condition is made strict and it is difficult to generate a continuous access achievement privilege.

On the other hand, when the user who canceled the friend registration has sent a message to the friend user to be canceled at least twice within two weeks before the cancellation (YES in S151), the process does not proceed to S131. The process proceeds to S35. That is, 0.8 is used as the threshold value for the support access condition, and the privilege grant adjustment is not performed. The subsequent processing (S36 to S40) is basically the same processing as that described in the flowchart of FIG.

With the process shown in FIG. 37, the user who canceled the friend registration, in principle, has a continuous access achievement privilege because the support access conditions become stricter than when the friend registration is not released for four weeks after the friend registration is released. However, if the message is transmitted to the friend user to be canceled twice or more within two weeks before canceling the friend registration as an exception, the support access condition does not become severe. As a result, for users who have canceled their friend registration, users who have made an effort to increase their friend's access by sending a support message before canceling it will make it difficult to give bonuses (continuous access achievement bonuses) Can be avoided. Therefore, it is intended only for users who cancel the registration of fellow users with low access frequency in order to increase the possibility of missing days without sending support messages to friends and trying to increase the access of friends. Effective measures can be taken, and it is possible to more effectively suppress the user from taking an action that is far from the original purpose.

In the example shown in FIG. 37, the privilege grant adjustment that the user who canceled the friend registration has transmitted a message to the friend user to be canceled at least twice within two weeks before the cancellation. However, the present invention is not limited to this. For example, the message transmission conditions before canceling friend registration (conditions for not granting benefits) are set to at least once within one week before cancellation, or three times within one month before cancellation It may be set as described above, and the period before canceling the friend registration and the condition of the number of message transmissions during the period can be arbitrarily set.

[Other Embodiments]
In the above-described embodiment, the game execution program is installed on the game server 1 side, and the game server 1 executes arithmetic processing and data processing for the game progress according to the input operation on the terminal device 3 of each user. And although the application example to the game system which a game progresses by transmitting the screen data reflecting the execution result to the terminal device 3 was demonstrated, it is not limited to this. For example, the game server 1 manages game information such as user access information, friend information, message information, and privilege information, and provides the user with game services such as message exchange and privilege provision between users within the game. On the other hand, the game execution process for advancing the game can be basically applied to a game system performed on the user terminal device side.

That is, the present invention can also be applied to a game system in which a part or all of the game execution program is downloaded or installed on the user terminal device side and the game execution processing is also performed on the terminal device. Therefore, as a user terminal device, various devices that can be connected to a game server (game management device) via a network and receive a game service can be applied. The above-described mobile phone terminal, PHS terminal, mobile information In addition to a terminal (PDA), a smartphone, a personal computer, and a tablet computer, a home video game device having a network connection function (a game configured by connecting a home video game machine to a home television) Device), a portable game-dedicated device, and the like are also applicable.

The computer-readable program according to the present embodiment is recorded on various computer-readable recording media such as a hard disk, an optical disk (CD-ROM, DVD-ROM, etc.), a flexible disk, a semiconductor memory, and the like. Is executed by the CPU 11 of the game server 1. The means for providing the program to the game server 1 is not limited to the recording medium described above, and can be performed via a communication network such as the Internet.

[Outline of Embodiment]
(1) As described above, the game management device according to one aspect of the present invention receives the access from the terminal device of each user who receives the game service via the network and manages the game information of each user. A game management device for providing the game service via the network, wherein (a) access management means for storing the access information of each user in a storage device and managing the access for each user; (B) Granting a continuous access achievement privilege by changing the game information of the user so as to be advantageous to the game for the user who has achieved the continuous access for all the unit periods of the specified number of continuous periods. And (c) information of fellow users belonging to a group centered on each user is stored in a storage device and stored. For a user who has fellow management means for performing peer management for each of the users and (d) a missing unit period that is not accessed among the unit periods of the prescribed number of consecutive periods, the fellow user of the user has a predetermined support access Fellow support access determining means for determining whether or not the condition is satisfied. And the said continuous access privilege provision means is said that even if it is a user with the said missing | missing unit period among the said unit periods of the continuous regulation period number, if the fellow user of the said user satisfy | fills the said support access conditions, When the fellow support access determination means determines, the user is provided with the continuous access achievement privilege.

According to this configuration, the game management device provides game services to each user via the network while receiving access from the terminal device of each user via the network and managing the game information of each user. For example, it is configured by an information processing apparatus that can be connected to a network such as a server. As a game service provided to each user by the game management device, there is a service such as a social game that can be played while the users cooperate or communicate with each other.

The game management device includes access management means for storing the access information of each user in a storage device and managing the access for each user. And this game management apparatus changes the game information of the said user so that it may become advantageous to a game with respect to the user of continuous access achievement who accessed all the unit periods of the continuous regulation period number, and performs continuous access. A continuous access privilege granting means for granting an achievement privilege is provided. For example, when one day in the real world is a unit period and the number of consecutive specified periods is 5, a continuous access achievement privilege is given to a user who accesses the game management device for 5 consecutive days.

The unit period is not limited to one day in the real world, and may be, for example, a half day (12 hours) or two days, and an arbitrary period can be set as the unit period. Further, the number of continuous specified periods is not limited to 5, and an arbitrary number of periods can be set. The access is access to the game management device from the terminal device of each user via the network, and (A) a top page (game main screen page) of a game service provided by the game management device, (B) Access to any page of (A) to (C), which is a specific page for executing an actual game, or (C) any page among all pages. For example, it may be judged that access has been made by proceeding to a specific page where an actual game is executed, and the access condition is made slightly strict, such as a case where it is terminated only by looking at the top page is not considered access. May be.

Moreover, the above-mentioned continuous access achievement privilege may be any advantage as long as it is advantageous in terms of the game as compared to the case where the privilege is not granted, and various privileges can be applied depending on the type and content of the game. If an example is given, if it is a game in which a point and an item are used, the continuous access achievement privilege of giving a user the point and item which can advance a game advantageously can be considered. In addition, in a battle-type game such as a baseball game or a soccer game where users can play against each other, there is a continuous access achievement privilege that the fighting power is improved by n battles (for example, three battles) and the battle is advantageous. Conceivable. In addition, if the game system is configured so that items can be obtained by lottery, the probability that a rare item (item with a lower lottery probability than a normal item and a rare value) can be obtained by lottery A continuous access achievement privilege of increasing a predetermined number of times (for example, once) is also conceivable.

Moreover, this game management apparatus is provided with the friend management means which performs the friend management for every user, and memorize | stores in the memory | storage device and manages the information of the fellow user who belongs to the group "friend" centering on each user. Yes. In addition, the group here shows the group of one's friend seen from the viewpoint of one user to the last, and each user who comprises these groups does not belong only to this group. Each user also has a group of “buddies” centered on him / herself.

Further, the game management device determines whether or not the fellow user of the user satisfies a predetermined support access condition for a user who has a missing unit period that has not been accessed in a unit period of a continuous specified number of periods. Companion support access judging means for judging is provided. Here, support access conditions should just be conditions regarding the access of a fellow user, and arbitrary conditions can be set. As an example of the support access condition, as will be described later, the number or ratio of fellow users who have accessed within the same unit period as the missing unit period exceeds the threshold. And even if it is a user who has a missing unit period in which access is missing in a unit period of a continuous specified number of periods, the fellow cheering access determining means determines that the fellow user of the user satisfies the cheering access condition In such a case, a continuous access achievement privilege is given to the user. For example, even if the user is unable to access the game management device for one day for some reason, if the user's companion satisfies the support access conditions, there is no missing unit period for the day. If a predetermined number of continuous accesses have been achieved, including compensation for missing unit periods, the user is granted a continuous access achievement privilege.

Thereby, even if the user cannot access the game management device for something, the user can maintain the continuous access achievement privilege by maintaining a high access frequency such that the user's companion satisfies the support access condition. The advantage is that it can be acquired. Moreover, if the user himself / herself also maintains a high access frequency, it can contribute to achievement of the support access condition when other associates lose access, and can indirectly support other associates. Thereby, each user is given the consciousness and motivation to increase the access frequency with each other. Therefore, each user is given the motivation to communicate with his / her fellow users in an attempt to increase the access frequency of the whole fellows. For example, each user sends a message such as “Let's do our best!” To his / her peers, and tries to excite the community with his / her fellow users.

In this way, in this configuration, not only providing the user with the fun of receiving benefits, but also motivation to increase the access frequency with each other and to motivate to communicate with each other. It gives to a user, and can thereby aim at activation of the whole game community. As a result, each user strengthens the connections and exchanges between friends in the game, and further increases the interest and interest in the game, so that it is possible to realize a game having continuity that will not get tired for the user.

(2) In the above configuration, the support access condition is such that the number of the fellow users who have performed the access within the same unit period as the missing unit period or a ratio of the whole fellow users exceeds a threshold. Preferably there is.

According to this configuration, it is determined whether the support access condition is satisfied for the same unit period as the missing unit period that the user could not access. For example, if the missing unit period is one day in the real world, the number or percentage of fellow users who accessed the game management device on the same day as the day the user missed access (ratio to the whole fellow users) exceeds the threshold. The support access condition is.

By setting the support access condition as described above, the user can access something for the same unit period as the missing unit period (for example, the same day as the missing date) so that the support access condition by the fellow is satisfied. The schedule of the unit period that is likely to be lost can be communicated to other friends in advance. For example, the user sends a message such as “I cannot access tomorrow so please give me cheering access!” For cheering access (as a concrete action of my friend, simply access the game) Can be requested in advance. In this way, the community of friends is excited by requesting support access in advance. In addition, on the day (unit period) when advance request for support access is made, if the friend actually satisfies the support access condition, the friendship will become stronger and the connection between the friend will become stronger, and the user will be interested and interested in the game. To make it even stronger.

(3) In said structure, a game management apparatus calculates the evaluation value which calculates the evaluation value of the group centering on the said user based on the said access frequency of the said fellow user in the user in which the said missing unit period exists It is preferable that the support access condition is that the evaluation value calculated by the evaluation value calculation means exceeds a threshold value. That is, it is an example of support access conditions different from the configuration of (2) above.

According to this structure, based on the access frequency of the fellow user of the user who has the missing unit period, the evaluation value of the group centering on the user is calculated, and the evaluation value exceeds the threshold as the support access condition Yes. Here, the evaluation value of the group indicates an average value or total value of access frequencies of fellow users who belong to the group centered on the user, a maximum value or a minimum value of the fellow users (within the group called the fellow), and the like.

In order for the user's fellow users to satisfy the support access condition by using such support access conditions, it is necessary to increase the evaluation value of the group by increasing the access frequency of the friend users. Therefore, each user is motivated to actively communicate with his / her fellow users in an attempt to increase the frequency of access of fellow users belonging to the group. Thereby, activation of the whole game community can be aimed at.

(4) In any one of the configurations described above, the unit period is one day in the real world, and the inaccessible scheduled date information transmitted from the terminal device of the user whose schedule for the inaccessibility is known in advance The information processing apparatus further includes an inaccessible scheduled date transmission means for transmitting the information on the scheduled date of inaccessibility to the terminal devices of all the fellow users of the user and transmitting the scheduled date of inaccessibility to all of the fellow users. It is preferable.

As described above, even if there is a missing unit period in which the user cannot access the game management device, the missing unit period is compensated for by the companion satisfying the support access condition, and a continuous access achievement privilege can be obtained. ing. Therefore, when it is known that the user cannot access the game management device in advance, the user may notify the friend of the scheduled date of inaccessibility so that the friend satisfies the support access condition. Here, according to said structure, the user can notify all the fellows of an inaccessible scheduled date by simple operation.

That is, normally, when a user transmits a message or the like to his / her friend, a transmission operation for each member is required. However, when the number of friends is large, it takes a lot of time and labor to send a message describing the inaccessible scheduled date to each of the user's friends. On the other hand, in this configuration, the user only needs to send the scheduled date of inaccessibility to the game management device only once. , To the terminal devices of all the fellow users of the user. Therefore, the user can notify all of his / her colleagues of the scheduled date of inaccessibility with a single operation, and the operation on the user side can be facilitated. In particular, this configuration is suitable for game services such as social games that require strong user operation.

(5) In the configuration of the above (4), the fellow support access determination means is inaccessible after the user has transmitted in advance the inaccessible scheduled date to the fellow user by the inaccessible scheduled date transmitting means. Only when the access is not performed on the same day as the scheduled date, it is preferable to determine whether the fellow user of the user satisfies the support access condition.

According to this configuration, as shown below, the processing load on the game management apparatus can be greatly reduced. That is, the determination as to whether or not the support access condition is satisfied is a process that is performed whenever a lack of access occurs in principle for a user who has not accessed within the unit period. Therefore, as the number of users managed by the game management device (users receiving the game service) increases, the number of users who have lost access increases, so the processing load on the game management device increases. For example, even if only about 10% of 1 million game service users have lost access, the process of determining whether or not the support access condition is satisfied for about 100,000 users is executed. It will be. The determination process of whether or not the support access condition is satisfied is not a process performed by the user actively requesting the game management device to execute the game service, but the user has not accessed the game management device. Since this process is also performed in response to a negative fact, it is also a process that should be executed with the processing load of the game management device reduced as much as possible.

Therefore, in this configuration, the prior notification by the user to the fellow inaccessible scheduled date is used as a condition for executing the determination process whether or not the support access condition is satisfied, Only when the user does not access on the same day, it is determined whether or not the support access condition is satisfied. Thereby, the game management device is limited to the user who has previously notified the inaccessible scheduled date, the determination process whether the support access condition is satisfied, and the subsequent process when the condition is satisfied Therefore, the processing load can be greatly reduced.

In addition, for users, if they do not access the game management device on the day when the scheduled date of inaccessibility to the fellow users is not notified in advance, the user cannot receive a determination as to whether or not the support access condition is satisfied. Therefore, the missing unit period is not compensated. Therefore, when a day that is unlikely to be accessible is scheduled, each user will make an advance request for support access by actively notifying the fellows of the scheduled date of inaccessibility, thereby Revitalization of communication.

(6) In any one of the configurations described above, the fellow support access determination means includes a first missing unit period and a period after the first missing unit period as the missing unit period in the unit period of a continuous specified number of periods. When the generated second missing unit period exists, it is preferable that the second missing unit period is set to a condition that does not satisfy the support access condition more easily than the first missing unit period.

According to this configuration, the missing unit period (second missing unit period) that occurred later in time series has stricter support access conditions than the missing unit period (first missing unit period) that occurred earlier. Apply. For example, if one day in the real world is set as the unit period, the stricter support access conditions are on the second day from the first day of the missing access day or on the third day from the second day of the missing day Apply. As an example, the support access condition for making up for the first day (the first missing unit period) of the missing date is “80% or more fellow users who have accessed the same day as the missing date”, The support access condition for making up for the second day (second missing unit period) of the missing date is “90% or more fellow users who have accessed on the same day as the missing date”.

As described above, the missing unit period (second missing unit period) that occurs later in time series applies the stricter support access condition than the missing unit period (first missing unit period) that occurs before that. Thus, it is possible to avoid making up for a plurality of missing unit periods easily. In addition, while allowing for support for multiple missing days while tightening the support access conditions for the second missing unit period that occurred later in time series, it is possible to increase the access frequency to each other in order to achieve strict conditions Users can be given awareness and motivation for further improvement.

(7) In any one of the configurations described above, the game management device is a user terminal that is determined by the friend support access determination unit when the friend user satisfies the support access condition after the elapse of the missing unit period. It is preferable that the apparatus further includes notification means for notifying that the continuous access is continued when the fellow user of the user satisfies the support access condition.

According to this configuration, even if a missing unit period occurs because the user did not access the game management device, continuous access of the user is not interrupted by the fellow user performing access that satisfies the support access condition. When it is in a continuous state, after the elapse of the missing unit period, the notification means notifies the user that “continuous access is continuing because the fellow user satisfies the support access condition”. Thereby, the user can recognize clearly the fact that continuous access is continuing by fellow support access after progress of a missing unit period. Therefore, the user is strongly conscious of the existence of his / her friend, and has a strong consciousness of continuously accessing the game management device and acquiring the continuous access achievement privilege. For this reason, continuous access to the game management device by the user can be effectively promoted.

(8) In any one of the above configurations, the game management device is a fellow user of a user who has been granted the continuous access achievement privilege when a fellow user of the user who has the missing unit period satisfies the support access condition. Further, a support access privilege granting means for giving a support access privilege by changing the game information of the friend user so as to be advantageous to the game for the friend user who performs the access satisfying the support access condition. It is preferable to provide.

According to this configuration, when a fellow user of a user who has a missing unit period that did not access satisfies the support access condition, the user achieves continuous access and acquires a continuous access achievement privilege. A support access privilege is also given to a fellow user who has contributed to the achievement of this continuous access (a fellow user who has performed access that satisfies the support access condition). Here, the support access privilege is only required to be advantageous in terms of the game as compared to the case where the privilege is not given, and according to the type and content of the game, similar to the above-described continuous access achievement privilege. Various benefits can be applied.

In this way, each user is given awareness and motivation to actively support his / her friends by providing support access benefits to the user's fellow users who have contributed to the continuous access of the user. Will be.

(9) In any one of the configurations described above, the game management device may be provided to a user who has at least a predetermined number or a predetermined ratio of fellow users who are granted the continuous access achievement privilege in a group centered on the user. On the other hand, it is preferable to further include fellow privilege granting means for changing the game information of the user so as to be advantageous in terms of the game and granting the fellow privilege.

According to this configuration, when the number of fellow users who have acquired the continuous access achievement privilege is greater than or equal to a predetermined number or a predetermined ratio in the group of friends centering on the user, the fellow privilege is given to the user. That is, by having many fellow users who have acquired the continuous access achievement privilege in their own group, the user can acquire a privilege different from the continuous access achievement privilege called the fellow privilege. Here, the companion benefits only need to be advantageous in terms of the game as compared to the case where the benefits are not granted, and, like the above-mentioned continuous access achievement benefits, various benefits depending on the type and content of the game. Special benefits can be applied.

And this configuration is combined with the above-mentioned configuration that “a friend can easily acquire a continuous access achievement privilege by making up for the missing unit period by support access”, and each user has many of his / her friends continuously. Awareness and motivation to increase the access frequency so that the access achievement privilege can be acquired will be given. In other words, each user also has a chance to acquire fellow benefits in addition to the continuous access achievement privilege, so that many fellow users can obtain the continuous access achievement privilege as well as to obtain the consecutive access achievement privilege. In order to do so, the user is motivated to increase the frequency of access to the game management device. In addition, even for users who have lost continuous access and are unable to acquire the continuous access achievement privilege, there is a chance that many of their own fellow users can acquire the fellow privilege if they acquire the continuous access achievement privilege. Therefore, in order to allow many fellow users to obtain a continuous access achievement privilege through support access, the user is motivated to increase the access frequency to the game management device.

(10) A game system according to another aspect of the present invention receives a terminal device of each user who receives a game service, receives access from the terminal device via a network, manages game information of each user, And a game management device having any one of the above-described configurations for providing the game service via the network.

(11) In a game management method according to still another aspect of the present invention, the game information of each user is managed by receiving an access made by a user from a terminal device of each user who receives a game service and managing the game information of each user. A game management method in a game management device that provides the game service via a network, wherein the game management device stores information on the access of each user in a storage device, and manages the access for each user An access management step, and the game management device changes the game information of the user so that it is advantageous to the game for a user who has achieved continuous access for all the unit periods of the specified number of continuous periods. A continuous access privilege granting step for granting a continuous access achievement privilege, and the game management device , A fellow management step for storing fellow user information belonging to a group centered on each user in a storage device to perform peer management for each user, and the game management device includes a continuous prescribed period number of the unit periods. A fellow support access determination step for determining whether or not a fellow user of the user satisfies a predetermined support access condition for a user who has a missing unit period that has not been accessed is included. And even if it is a user where the missing unit period exists among the unit periods of the continuous specified number of periods, the continuous access privilege granting step is performed when the fellow user of the user satisfies the support access condition. When the fellow support access determination step determines, the user is provided with the continuous access achievement privilege.
(12) A program according to still another aspect of the present invention receives a computer access from a terminal device of each user who receives a game service and manages game information of each user, A program for operating as a game management apparatus that provides the game service via a network, wherein the computer stores the access information of each user in a storage device, and manages the access for each user Access management means, for a user who has achieved continuous access for all of the unit periods of the continuous specified number of periods, the game information of the user is changed so as to be advantageous to the game, and a continuous access achievement privilege is provided. Continuous access privilege granting means to be assigned, belonging to a group centered on each user Associate management means for storing inter-user information in a storage device and managing associates for each user, and for users who have missing unit periods that have not been accessed among the unit periods of the continuous specified number of periods, It functions as a fellow support access determination means for determining whether or not a fellow user satisfies a predetermined support access condition, and the continuous access privilege granting means includes the missing unit period in the unit period of the continuous specified number of periods. If the fellow cheering access determination means determines that the fellow user of the user satisfies the cheering access condition, the computer is assumed to give the user the continuous access achievement privilege. It is for making the function.
(13) A recording medium according to still another aspect of the present invention is a computer-readable recording medium recording the program according to (12) above.

It should be noted that the specific embodiments or examples made in the mode for carrying out the invention are merely to clarify the technical contents of the present invention, and are limited to such specific examples in a narrow sense. The present invention should not be interpreted, and various modifications can be made within the scope of the technical idea of the present invention and the claims.

The present invention particularly relates to a game management device, a game management method, a program, and a recording medium for a so-called social game that a user can play while communicating with other users who are receiving game services. Since it can be applied suitably and a highly entertaining game service can be provided, it can be used industrially.

Claims

A game management device that accepts access from a terminal device of each user who receives a game service, manages game information of each user, and provides each user with the game service via the network,
Storing access information of each user in a storage device and managing the access for each user;
Continuous access that gives a continuous access achievement privilege by changing the game information of the user so as to be advantageous to the game for a user who has achieved the continuous access for all the unit periods of the specified number of continuous periods. Privilege granting means;
Associate management means for managing associates for each user by storing information of associate users belonging to a group centered on each user in a storage device;
Friend support access determination means for determining whether or not a fellow user of the user satisfies a predetermined support access condition for a user having a missing unit period that has not been accessed among the unit periods of the continuous specified number of periods. And comprising
The continuous access privilege granting means may support the fellow supporter if the fellow user of the user satisfies the support access condition even if the missing unit period is present among the unit periods of the continuous prescribed number of periods. A game management device that grants the continuous access achievement privilege to the user when the access determination means determines.
2. The game according to claim 1, wherein the support access condition is that a number of the fellow users who have made the access within the same unit period as the missing unit period or a ratio of the whole of the fellow users exceeds a threshold value. Management device.
Based on the access frequency of the fellow user in the user in which the missing unit period exists, further comprising an evaluation value calculating means for calculating an evaluation value of a group centered on the user,
The game management device according to claim 1, wherein the support access condition is that the evaluation value calculated by the evaluation value calculating unit exceeds a threshold value.
The unit period is one day in the real world,
The information on the scheduled date of inaccessibility transmitted from the terminal device of the user whose schedule for which access is not possible is known in advance is received, and the information on the scheduled date of inaccessibility is sent to the terminal devices of all the fellow users of the user The game management device according to claim 1, further comprising: an inaccessible scheduled date transmission means for transmitting and transmitting the inaccessible scheduled date to all of the fellow users.
The fellow support access determination means did not perform the access on the same day as the scheduled date of inaccessibility after the user transmitted the scheduled date of inaccessibility to the fellow user by the inaccessible scheduled date transmission means in advance. 5. The game management device according to claim 4, wherein only in a case, it is determined whether or not a fellow user of the user satisfies the support access condition.
The fellow support access determination means includes a first missing unit period and a second missing unit period generated after the first missing unit period as the missing unit period in the unit period of a continuous specified period number. In this case, the game management device according to claim 1, wherein the second missing unit period is set to be more difficult to satisfy the support access condition than the first missing unit period.
After the elapse of the missing unit period, the fellow user of the user determines the support access condition for the user terminal device determined by the fellow support access determination means that the fellow user satisfies the support access condition. The game management device according to claim 1, further comprising notification means for notifying that continuous access is continued by satisfying the condition.
A fellow user who has been granted the continuous access achievement privilege when the fellow user of the user with the missing unit period satisfies the support access condition, and the friend user who has performed the access satisfying the support access condition On the other hand, the game management apparatus according to claim 1, further comprising support access privilege granting means for changing the game information of the fellow user to give a support access privilege so as to be advantageous in terms of the game.
The game information of the user is given to the user who is more than a predetermined number or a predetermined ratio of fellow users to whom the continuous access achievement privilege is given in a group centered on the user so that it is advantageous in terms of the game. The game management device according to any one of claims 1 to 8, further comprising fellow privilege granting means for changing and granting the fellow privilege.
A terminal device of each user receiving the game service;
A game management device according to claim 1, wherein the game management device according to claim 1, which receives access from the terminal device via a network, manages game information of each user, and provides the user with the game service via the network. system.
A game management method in a game management apparatus that receives access from a terminal device of each user who receives a game service, manages game information of each user, and provides each user with the game service via the network There,
The game management device stores the access information of each user in a storage device, and manages the access for each user;
The game management device achieves continuous access by changing the game information of the user so that it is advantageous to the game for a user who has achieved continuous access for all the unit periods of the specified number of continuous periods. A continuous access privilege granting step for granting a privilege;
A friend management step in which the game management device stores the information of fellow users belonging to a group centered on each user in a storage device and performs fellow management for each user;
The game management device determines whether or not a fellow user of the user satisfies a predetermined support access condition for a user who has a missing unit period that is not accessed among the unit periods of a predetermined number of continuous periods. A friend support access determination step,
In the continuous access privilege granting step, even if the missing unit period exists in the unit period of the continuous prescribed number of periods, the fellow supporter if the fellow user of the user satisfies the support access condition A game management method for providing the user with the continuous access achievement privilege when the access determination step determines.
The computer operates as a game management apparatus that accepts access from the terminal device of each user who receives the game service via the network, manages game information of each user, and provides the game service to each user via the network A program for
The computer,
Access management means for storing the access information of each user in a storage device and managing the access for each user;
Continuous access that gives a continuous access achievement privilege by changing the game information of the user so as to be advantageous to the game for a user who has achieved the continuous access for all the unit periods of the specified number of continuous periods. Privilege granting means,
Friend management means for storing information on fellow users belonging to a group centered on each user in a storage device and managing fellow users for each user,
Friend support access determination means for determining whether or not a fellow user of the user satisfies a predetermined support access condition for a user having a missing unit period that has not been accessed out of the unit periods of the specified number of continuous periods. Function as,
The continuous access privilege granting means may support the fellow supporter if the fellow user of the user satisfies the support access condition even if the missing unit period is present among the unit periods of the continuous prescribed number of periods. A program for causing a computer to function as providing the user with the continuous access achievement privilege when the access determination means determines.
A computer-readable recording medium on which the program according to claim 12 is recorded.