JP2021037312A - Information processing device - Google Patents

Abstract

To provide an information processing device capable of enhancing user's willingness to continuously receive benefits by paying a game charge every fixed period.SOLUTION: An information processing device includes a user information storage part 222 for storing user information including information for specifying whether to be a user who has paid a set game charge every fixed period, an event provision part 202 for providing a user who has paid the game charge for the preceding fixed period with an event game becoming playable by paying the game charge for the preceding fixed period within the preceding fixed period, and an event re-provision part 203 for re-providing a user who has paid the game charge for the preceding fixed period and has paid the game charge for a following fixed period of this time with an event game being the same as or related to the event game becoming playable by paying the game charge for the preceding fixed period within the fixed period of this time.SELECTED DRAWING: Figure 3

Description

The present invention relates to an information processing device and a program.

A system is known in which a game fee (for example, a monthly fee) is set for each fixed period, and a user who has paid the game fee for the fixed period is allowed to play the game within the fixed period (for example). , Patent Document 1).

Japanese Unexamined Patent Publication No. 2011-200692

In such a system, for example, when a user pays a game fee for a certain period of the previous time, he / she can benefit from paying the game fee only within the certain period of the previous time. Then, in order to receive the same benefits in the following fixed period, it is necessary to pay the game fee for this fixed period. However, since there was no mechanism to actively encourage users who paid the game fee for the previous fixed period to pay the game fee for the current fixed period, users who are trying to continue to benefit There was a risk of diminishing motivation.

The present invention has been made in view of such circumstances, and an object of the present invention is to motivate users to continuously benefit from payment of game fees at regular intervals. ..

The main invention of the present invention for solving the above problems is
A user information storage unit that stores user information that includes information for identifying whether or not the user has paid the game fee set at regular intervals, and
With the event providing department that provides the event game that can be played by paying the game fee for the previous fixed period to the user who paid the game fee for the previous fixed period within the previous fixed period. ,
It is possible to play by paying the game fee for the previous fixed period to the user who paid the game fee for the previous fixed period and also paid the game fee for the subsequent fixed period this time. The event re-provision unit that re-provides the same or related event game as the above-mentioned event game within a certain period of time this time.
It is an information processing device characterized by being equipped with.
According to such an information processing device, by paying the game fee for the previous fixed period and the game fee for the current fixed period, the event game that could be played within the previous fixed period can be played for the current fixed period. You will be able to continue playing within. Therefore, users who could not play the event game within the previous fixed period or users who played the event game within the previous fixed period but could not clear it will challenge the event game even within this fixed period. It becomes possible. As a result, it is possible to motivate the user who paid the game fee for the previous fixed period to pay the game fee for the current fixed period, so that the game fee can be continuously paid for the fixed period. It is possible to motivate users to benefit from.

In addition, when the user who paid the game fee for the previous fixed period logs in within the previous fixed period, the event providing department pays the logged-in user the game fee for the previous fixed period. By providing an event game that has become playable,
The event re-providing department does not log in if the user who paid the game fee for the previous fixed period and also paid the game fee for the current fixed period did not log in within the previous fixed period. It is desirable to provide the user with the same or related event game as the event game provided during the period during which he / she did not log in during the previous fixed period within the current fixed period. ..
As a result, even if you cannot log in to the event game within the previous fixed period, you can challenge the event game provided during the previous fixed period during which you did not log in within this fixed period. Is possible.

In addition, the event providing unit can play the event for a plurality of days for the logged-in user when the user who paid the game fee for the previous fixed period logs in within the previous fixed period. Offer the game,
The event re-providing department pays the game fee for the previous fixed period, and when the user who paid the game fee for the fixed period this time does not log in within a plurality of days, the event re-providing department does not log in. With the event game, the user who paid the game fee for the previous fixed period to the user who did not log in was able to play for multiple days for the number of days when he / she did not log in. It is desirable to provide the same or related event games again within a certain period of time this time.
As a result, even if you cannot log in to all the event games for multiple days within the previous fixed period, you can challenge for the number of days you did not log in during the multiple days within this fixed period. ..

In addition, when the user who paid the game fee for the previous fixed period logs in within the previous fixed period, the event providing department pays the logged-in user the game fee for the previous fixed period. The event game that became playable as a result of this is provided over multiple days spanning the previous fixed period and this fixed period.
The event re-providing department logs in on the day when the user who paid the game fee for the previous fixed period and also paid the game fee for the current fixed period is included in the previous fixed period among multiple days. If there is a day when the user did not log in, the user who paid the game fee for the previous fixed period logs in to the user who did not log in on the day included in the previous fixed period of multiple days. It is desirable to provide the same or related event game as the event game, which was playable for a plurality of days for the number of days that did not exist, again within a certain period of time.
As a result, when event games for multiple days spanning the previous fixed period and this fixed period are provided, even if multiple logins cannot be made on the days included in the previous fixed period of the multiple days. Only the number of days that you did not log in on the day included in the previous fixed period of the day can be challenged within this fixed period.

In addition, when the user who paid the game fee for the previous fixed period logs in within the previous fixed period, the event providing department pays the logged-in user the game fee for the previous fixed period. By providing an event game that has become playable,
The event re-providing department was provided during the period when the user who paid the game fee for the previous fixed period and also paid the game fee for the current fixed period logged in within the previous fixed period. If the event game cannot be cleared, it is desirable to provide the same or related event game as the event game that could not be cleared again within a certain period of time.
As a result, even if the event game is logged in within the previous fixed period but cannot be cleared, the event game that could not be cleared can be challenged again within the fixed period this time.

In addition, it is advantageous for the user that the user who paid the game fee for the previous fixed period performs the operation required for paying the game fee for the current fixed period earlier within the previous fixed period. It is desirable to have a privilege granting unit that grants the privilege.
As a result, it is possible to motivate the user who paid the game fee for the previous fixed period to pay the game fee for the current fixed period at an early stage. It will be possible to further increase the motivation of users to continuously benefit.

Also, the computer
A user information storage means that stores user information that includes information for identifying whether or not the user has paid the game fee set at regular intervals.
An event providing means that provides an event game that can be played by paying the game fee for the previous fixed period to the user who paid the game fee for the previous fixed period within the previous fixed period.
It is possible to play by paying the game fee for the previous fixed period to the user who paid the game fee for the previous fixed period and also paid the game fee for the subsequent fixed period this time. An event re-provision means that provides the same or related event game as the event game that has become, within a certain period of time this time.
It is a program to function as.
Such a program makes it possible to motivate users to continuously benefit from paying game fees at regular intervals.

It is a block diagram which shows an example of the information processing system which concerns on this embodiment. It is a hardware block diagram which shows an example of the computer which concerns on this embodiment. It is a functional block diagram which shows an example of the server apparatus which concerns on this embodiment. It is a functional block diagram which shows an example of the client terminal which concerns on this embodiment. It is a flowchart explaining the operation example of the information processing system 1 in this embodiment. It is a block diagram which shows an example of user information. It is a block diagram which shows an example of the log history information. It is a block diagram which shows an example of the monthly charge user information. It is a block diagram which shows an example of login bonus information. It is a block diagram which shows an example of event information. It is an image diagram which shows an example of a game screen. It is a figure explaining the specific example 1 when the same event game as last month's event game is provided again within this month. It is a figure explaining the specific example 2 when the same event game as last month's event game is provided again within this month. It is a figure explaining the specific example 3 when the same event game as last month's event game is provided again within this month.

Hereinafter, the information processing apparatus, program, and information processing system according to the embodiment of the present invention will be described in detail. The present invention can be widely applied to an information processing device, a program, an information processing system, or the like that employs a game that can be played by a user who has paid a game fee (for example, a monthly fee) at regular intervals.

[Embodiment]
<System configuration>
FIG. 1 is a configuration diagram showing an example of an information processing system 1 according to the present embodiment. As shown in FIG. 1, in the information processing system 1 according to the present embodiment, one or more client terminals 10 and a server device 20 are connected via a network N.

The client terminal 10 is a terminal device such as a PC, a smartphone, or a tablet operated by a user, or a terminal device such as a game-dedicated device for home or business use. The server device 20 manages and controls the game performed by the user on the client terminal 10, and performs in-game billing processing and the like. The network N is the Internet or the like, and includes a mobile radio base station or the like.

In addition to the client-server type information processing system 1 shown in FIG. 1, the present invention can be applied to a single game device by separately providing a mechanism for performing in-game billing processing. It goes without saying that the information processing system 1 of FIG. 1 is an example, and there are various system configuration examples depending on the application and purpose. For example, the server device 20 of FIG. 1 may be distributed and configured in a plurality of computers.

<Hardware configuration>
<< Client terminal and server device >>
FIG. 2 is a hardware configuration diagram showing an example of the computer 50 according to the present embodiment. The client terminal 10 and the server device 20 according to the present embodiment are realized by, for example, a computer 50 having a hardware configuration shown in FIG. The computer 50 is an example of an information processing device.

As shown in FIG. 2, the computer 50 includes a CPU 51, a RAM 52, a ROM 53, a communication interface 54, an input device 55, a display device 56, an external interface 57, an HDD 58, and the like, and each of them is connected to each other by a bus line B. Has been done. The input device 55 and the display device 56 may be connected and used when necessary.

The CPU 51 is an arithmetic unit that realizes control and functions of the entire computer by reading programs and data from storage devices such as ROM 53 and HDD 58 onto the RAM 52 and executing various processes based on the read programs and data.

The RAM 52 is an example of a volatile semiconductor memory (storage device) for temporarily holding a program or data, and is also used as a work area when the CPU 51 executes various processes.

The ROM 53 is an example of a non-volatile semiconductor memory (storage device) capable of holding programs and data even when the power is turned off. The ROM 53 stores programs and data such as BIOS, OS settings, and network settings that are executed when the computer 50 is started.

The communication interface 54 is an interface for connecting the computer 50 to the network N. As a result, the computer 50 can perform data communication via the communication interface 54.

The input device 55 is a device used by a user or an administrator to input various signals. The input device 55 in this embodiment is, for example, an operation device such as a touch panel, operation keys and buttons, a keyboard and a mouse.

The display device 56 is a device for displaying various information on the screen to the user or the administrator. The display device 56 in this embodiment is, for example, a display such as a liquid crystal or an organic EL.

The external interface 57 is an interface for connecting to an external device so as to be capable of data communication. As a result, the computer 50 can read and / or write to the recording medium via the external interface 57. The external device is, for example, a recording medium such as a flexible disk, a CD, a DVD, an SD memory card, or a USB memory.

The HDD 58 is an example of a non-volatile storage device that stores programs and data. The stored programs and data include an OS, which is basic software that controls the entire computer, and an application that provides various functions on the OS.

Instead of the HDD 58, a drive device (for example, a solid state drive: SSD) that uses a flash memory as a storage medium may be used.

The client terminal 10 and the server device 20 according to the present embodiment can realize various processes as described later by executing a program on the computer 50 having the hardware configuration described above.

<Software configuration>
《Server device》
FIG. 3 is a functional block diagram showing an example of the server device 20 according to the present embodiment. The server device 20 according to the present embodiment is realized by, for example, the functional block shown in FIG.

The server device 20 according to the present embodiment realizes the server control unit 200, the server storage unit 220, and the server communication unit 240 by executing the program.

The server control unit 200 has a function of executing processing related to various games. The server control unit 200 includes a game control unit 201, an event providing unit 202, an event re-providing unit 203, a privilege giving unit 204, a notification unit 205, and a display control unit 206.

The game control unit 201 controls the progress of various games such as a battle game and a lottery game, which will be described later, based on the game operation received from the user by the client terminal 10. The game control unit 201 in the present embodiment also functions as a battle game control unit and a lottery game control unit.

The event providing unit 202 provides an event game to the user. For example, when the user pays the game fee for the previous fixed period, the event providing unit 202 in the present embodiment can play the event game that can be played by paying the game fee for the previous fixed period. Provided within the previous fixed period. In addition, if the user continues to pay the game fee for the next fixed period, the game fee for the current fixed period will be paid to the user who paid the game fee for the fixed period. We will provide an event game that can be played by paying for this within a certain period of time.

The event reproving unit 203 again provides the user with an event game that has already been provided by the event providing unit 202. In the event reproving unit 203 of the present embodiment, for example, when the user pays the game fee for the previous fixed period and the user also pays the game fee for the following fixed period this time, the previous time. The same event game as the event game that became playable by paying the game fee for a certain period of time will be provided again within this certain period of time.

The privilege granting unit 204 grants a privilege to the user. For example, when the user pays the game fee for the previous fixed period, the privilege giving unit 204 in the present embodiment gives the user the privilege for the payment of the game fee for the previous fixed period within the previous fixed period. Is given to. In addition, if the user continues to pay the game fee for the next fixed period, the benefit for the payment of the game fee for the fixed period will be given to the user within the fixed period. And give. Then, the privilege granting unit 204 in the present embodiment, for example, performs an operation required for the user who paid the game fee for the previous fixed period to pay the game fee for the current fixed period for the previous fixed period. It is also possible to give a privilege that is advantageous to the user as soon as it is done within.

The notification unit 205 notifies the user of various information. The notification unit 205 in the present embodiment notifies the user within the current fixed period to prompt the user to pay the game fee for the next fixed period. The notification unit 205 can notify the user by screen display, e-mail transmission, push notification, or the like.

The display control unit 206 controls the screen display of the client terminal 10 by generating data of various game screens according to the progress of the battle game or the lottery game executed by the game control unit 201, for example.

The server storage unit 220 has a function of storing information about various games. The server storage unit 220 includes a character information storage unit 221, a user information storage unit 222, a login bonus information storage unit 223, and an event information storage unit 224.

The character information storage unit 221 is an example of the content information storage unit, and stores character information (content information) related to the character as an example of the content. In the character information stored in the character information storage unit 221, various characters used in the battle game and the lottery game, various characters used as a privilege, and the like are set.

The user information storage unit 222 stores user information about the user. The user information stored in the user information storage unit 222 includes information for identifying the user's rank, various characters possessed by the user, and whether or not the user has paid a game fee for a certain period (monthly charge user). Etc. are set.

The login bonus information storage unit 223 is an example of the privilege information storage unit, and stores login bonus information (privilege information) related to the login bonus as an example of the privilege. In the login bonus information stored in the login bonus information storage unit 223, the type and quantity of the login bonus given when the user logs in are set at regular intervals.

The event information storage unit 224 stores event information related to the event. In the event information stored in the event information storage unit 224, an event game provided to a user (monthly billing user) who has paid the game fee for each fixed period is set at regular intervals.

The server communication unit 240 has a function of communicating with the client terminal 10 via the network N.

《Client terminal》
FIG. 4 is a functional block diagram showing an example of the client terminal 10 according to the present embodiment. The client terminal 10 according to the present embodiment is realized by, for example, the functional block shown in FIG.

The client terminal 10 according to the present embodiment realizes a client control unit 100, a client storage unit 120, a client communication unit 140, an operation reception unit 150, and a screen display unit 160 by executing a program. The client control unit 100 includes a request transmission unit 101 and a response reception unit 102.

The operation reception unit 150 receives an operation from a user who operates the client terminal 10. In addition, the client control unit 100 performs processing related to the game on the client terminal 10. The request transmission unit 101 transmits a request to the server device 20 based on the content of the operation received from the user by the operation reception unit 150. The response receiving unit 102 receives a response such as a processing result for the request transmitted by the request transmitting unit 101 to the server device 20.

Further, the client storage unit 120 stores information required for the client terminal 10. The client communication unit 140 communicates with the server device 20. The screen display unit 160 displays the screen of the client terminal 10 according to the control from the server device 20.

As described above, in the information processing system 1 according to the present embodiment, the server device 20 controls the progress and display of the game, but the client terminal 10 may perform the game. Specifically, at least a part of the functional units of the server control unit 200 may not be provided in the server control unit 200 of the server device 20, while may be provided in the client control unit 100 of the client terminal 10. Good.

Further, the client control unit 100 of the client terminal 10 receives page data described in HTML (Hyper Text Markup Language) or the like, a script included in the page data, or the like from the server device 20, and performs processing related to the game. There is a type. Further, the client control unit 100 of the client terminal 10 has an application type that performs processing related to the game based on the installed application.

<Overview>
Here, the outline of the system in this embodiment will be described. In the system of the present embodiment, a battle game and a lottery game are provided to the user.

The battle game in the present embodiment is a game in which an enemy character appears in a party composed of a plurality of characters, and the appearing enemy character and each character constituting the party are played against each other.

In this battle game, multiple quests aimed at defeating enemy characters are set according to the difficulty level. The user can form a party using his / her own character, etc., select one of the quests, and challenge the battle with the enemy character. During the match, the user may be given a character set to be available for the selected quest.

In the lottery game of the present embodiment, when an operation of executing a character lottery is received from the user, one of the plurality of characters to be drawn is selected based on the lottery probability of each character, and the selected character is selected. Is a game that gives the user.

In this lottery game, the lower the lottery probability is set, the higher the rarity of the character is set. The user can compose his / her own party by using the characters obtained in the lottery game and play a competitive game.

Further, in the system of the present embodiment, by paying a game fee (monthly fee) every month (every fixed period), it is possible to become a monthly billing user. If you become a monthly paying user, for example, if you pay the game fee for this month, you will be provided with an event game that you can play by paying the game fee for this month during the month of this month, and for this month. You can receive benefits for paying the game fee.

In the present embodiment, as a privilege for paying the game fee for this month, a login bonus for logging in to the game can be received only once a day during this month. The login bonus received by monthly paying users is set to be more advantageous than the login bonus received by users who have not paid the game fee for this month (normal users).

Furthermore, if you become a monthly paying user, for example, if you paid the game fee for last month and then continue to pay the game fee for this month, you will play by paying the game fee for last month during the month of this month. The same event game as the one that became possible is being offered again.

Therefore, the user who paid the game fee for last month could not log in on any day of last month, and could play the event game for last month by paying the game fee for last month. Even if you cannot play, you can continue to pay the game fee for this month and challenge the event game for the previous month within the month of this month. Also, if the user who paid the game fee for last month logged in on any day of last month but could not clear the event game for that last month, he / she can continue to pay the game fee for this month. , It will be possible to re-challenge last month's event game that could not be cleared within the month of this month.

In this way, users who paid the game fee for the last month can be motivated to pay the game fee for this month, so that the monthly fee will continue to benefit from the payment of the monthly fee. It is possible to increase the motivation of paying users.

<Operation>
FIG. 5 is a flowchart illustrating an operation example of the information processing system 1 according to the present embodiment.

When the login screen of the battle game is displayed on the screen display unit 160 of the client terminal 10, the user performs a login operation on the client terminal 10 to log in to the battle game. When the user performs a login operation on the login screen, the operation reception unit 150 of the client terminal 10 accepts the operation content based on the user's login operation.

The request transmission unit 101 of the client terminal 10 requests the server device 20 to log in to the server device 20 for a battle game accompanied by login operation information including a user ID and password, etc., based on the operation content received from the user by the operation reception unit 150. Transmit (step S11).

Next, when the game control unit 201 of the server device 20 receives the login request for the battle game from the client terminal 10, the game control unit 201 executes the login process for the battle game according to the login operation information including the user ID and password (step). S12).

Specifically, the game control unit 201 of the server device 20 performs user authentication by referring to the user information stored in the user information storage unit 222 based on the user ID or the like accompanying the login request. When the game control unit 201 of the server device 20 normally authenticates the user, the log history information set in the user information is updated, and the login date and time of the battle game is added.

FIG. 6 is a configuration diagram showing an example of user information. The user information shown in FIG. 6 has user ID, number of items possessed, possessed character, party, log history information, monthly billing user information, event provision information, event clear information, and the like as items. The user ID is information for uniquely identifying the user. The number of items possessed is information indicating the number of items possessed by the user. The possessed character is information indicating one or a plurality of various characters possessed by the user at the present time. The party is information indicating each character that constitutes the user's party. The log history information is information indicating the log history of the user. Monthly billing user information is information about a monthly billing user. Event providing information is information about an event that can be provided to a user. Event clear information is information about an event cleared by the user.

FIG. 7 is a configuration diagram showing an example of log history information. The log history information shown in FIG. 7 has a log ID, a login date and time, a logout date and time, and the like as items. The log ID is information for uniquely identifying the log data. The login date and time is information indicating the date and time when the user logged in to the battle game. The logout date and time is information indicating the date and time when the user logged out.

Returning to FIG. 5, the game control unit 201 of the server device 20 then acquires the monthly charge user information from the user information stored in the user information storage unit 222 when the login process related to the battle game is completed in this way. With reference to the acquired monthly billing user information, it is determined whether or not the logged-in user is a monthly billing user who has paid the game fee for this month (step S13).

FIG. 8 is a configuration diagram showing an example of monthly billing user information. The monthly billing user information shown in FIG. 8 has items such as a payment target, a monthly billing user, and a payment date and time. The payment target is information indicating the month for which the monthly fee is to be paid. Here, it is assumed that this month is September, and it is shown that the user has paid the game fee for August, which is last month, and the game fee for September, which is this month. The monthly billing user is information indicating whether or not the user is a monthly billing user for the month to be paid. The payment date and time is information indicating the date and time when the game fee for the month was paid.

Returning to FIG. 5, when it is determined that the user is a monthly billing user who has paid the game fee for this month as a result of the determination by the process of step S13 described above, the process proceeds to step S15 described later. On the other hand, if it is determined that the user is not the monthly paying user who paid the game fee for this month, the process proceeds to the next step S14.

Next, if it is determined that the privilege granting unit 204 of the server device 20 is not a monthly billing user who has paid the game fee for this month (step S13: NO), the normal user who has not paid the game fee for this month. Therefore, the login bonus of the normal user is given based on the login bonus information stored in the login bonus information storage unit 223 (step S14).

Specifically, the privilege granting unit 204 of the server device 20 is based on the login bonus information stored in the login bonus information storage unit 223, and only when the user first logs in on that day, the login bonus of the normal user set on that day is set. Is given. In other words, the login bonus will be given only once a day.

FIG. 9 is a configuration diagram showing an example of login bonus information. The login bonus information shown in FIG. 9 includes a privilege ID, a provision period, a privilege content of a normal user, a privilege content of a monthly billing user, and the like as items. The privilege ID is information for uniquely identifying the privilege. The provision period is information indicating the period during which the login bonus can be granted. The privilege content of the normal user is information indicating the content of the login bonus given when the normal user logs in during the provision period. Here, the item is usually set as a login bonus for the user, and as shown in parentheses in the figure, the number of items to be given is also set. The content of the privilege of the monthly charge user is information indicating the content of the login bonus given when the monthly charge user logs in during the provision period. Here, items and characters are set as login bonuses for monthly billing users, and as shown in parentheses in the figure, the number of items and characters to be granted is also set. In the present embodiment, the login bonus received by the monthly billing user is set to be more advantageous than the login bonus received by the normal user.

Returning to FIG. 5, next, when the privilege granting unit 204 of the server device 20 is determined to be a monthly billing user who has paid the game fee for this month (step S13: YES), the game fee for this month is charged. A login bonus is given as a privilege for paying (step S15).

Specifically, the privilege granting unit 204 of the server device 20 grants a login bonus of a monthly billing user different from the normal user set on that day based on the login bonus information stored in the login bonus information storage unit 223.

The privilege granting unit 204 of the server device 20 grants the login bonus of the monthly billing user set on that day only when the user first logs in on that day. In other words, the login bonus of the monthly billing user will be given only once a day.

Next, when the event providing unit 202 of the server device 20 grants the login bonus for this month by the privilege giving unit 204 in this way, the game charge for this month is given to the monthly billing user who paid the game charge for this month. Provide an event game for this month that can be played by paying (step S16).

Specifically, first, the event providing unit 202 of the server device 20 can provide this month to a monthly billing user who has paid the game fee for this month by referring to the event information stored in the event information storage unit 224. Get a minute event game.

FIG. 10 is a configuration diagram showing an example of event information. The event information shown in FIG. 10 has event ID, provision period, event content, privilege content, and the like as items. The event ID is information for uniquely identifying the event. The provision period is information indicating the period during which the event game can be provided. The event content is information indicating the content of the event game that can be provided. Here, a battle game (quest) or a lottery game whose offer period is limited is set as an event game. The privilege content is information indicating the privilege content that can be obtained in the event game. Here, items and characters are set as a privilege that can be acquired, and as shown in parentheses in the figure, the number of items and characters is also set.

Then, when the event providing unit 202 of the server device 20 acquires the event game for this month that can be provided to the monthly billing user who paid the game fee for this month, the event providing unit 202 sets the user information to be stored in the user information storage unit 222. The event provision information of the user is updated, and the setting registration of the acquired event game for this month that can be provided is performed.

Next, the event reproving unit 203 of the server device 20 acquires the monthly charge user information from the user information stored in the user information storage unit 222, and refers to the acquired monthly charge user information to charge the game for this month. It is determined whether or not the monthly billing user who paid the above is the user who also paid the game fee for the last month (step S17).

As a result of this judgment, if it is determined that the monthly fee user who paid the game fee for this month is the user who did not pay the game fee for last month (that is, the user who started paying the monthly fee from this month). , Proceed to the process of step S20 described later. On the other hand, if it is determined that the monthly paying user who paid the game fee for this month is the user who also paid the game fee for last month, the process proceeds to the next step S18.

Next, when the event reproving unit 203 of the server device 20 determines that the monthly billing user who paid the game fee for this month is the user who also paid the game fee for last month (step S17: YES). ), Determines if there is an event game for last month provided to other users who logged in during the period during which the user did not log in during the month of last month (step S18). ).

Specifically, the event reproving unit 203 of the server device 20 paid the game fee for the previous month and the game fee for this month with reference to the log history information shown in FIG. 7 and the event information shown in FIG. Identify last month's event games that were offered during the month that the monthly paying user did not log in during the month of last month. Then, if at least one or more event games can be identified, the corresponding event games for the last month will exist.

As a result of this judgment, if it is determined that there is no event game for last month provided to other users who logged in during the period during which the user did not log in during the month of last month. Proceeds to the process of step S20 described later. On the other hand, if it is determined that there is an event game for last month that was provided to other users who logged in during the period during which the user did not log in during the month of last month. , Proceed to the process of the next step S19.

Next, the event re-providing unit 203 of the server device 20 is provided with the event game for the last month provided to other users who logged in during the period during which the user did not log in during the month of last month. If it is determined that exists (step S18: YES), it is the same as the event game for the last month that existed for the monthly billing user who paid the game fee for the last month and the game fee for this month. Event game is provided again (step S19).

Specifically, first, the event reproving unit 203 of the server device 20 updates the event providing information of the user set in the user information stored in the user information storage unit 222, and the event providing information of the user exists last month. Additional registration will be made as this month's event game that can provide the same event game as the minute event game.

In the present embodiment, the provision period of the additionally registered event game is set one month after the provision period of the event game for the last month in which it existed. Not limited to this, it is also possible to set the provision period of the additionally registered event game to one month during this month. In that case, the provision may be terminated when the user plays the event game. It is also possible to set a fixed date within this month.

Next, the notification unit 205 of the server device 20 sets a monthly event list in which the event games for this month that can be provided are listed based on the event provision information set in the user information stored in the user information storage unit 222. Notify the paying user (step S20).

That is, it is determined that the monthly paying user who paid the game fee for this month is the user who also paid the game fee for last month (step S17: YES), and the game fee for last month and the game fee for this month are set. If it is determined that there is an event game for last month that was offered to other users who logged in during the non-logged period of the month in which the paid monthly paying user did not log in (step). S18: YES), the notification unit 205 of the server device 20 displays a list of the event games for this month set in the event information stored in the event information storage unit 224 and the event games for the last month in which the event games existed. You will be notified of the event list.

On the other hand, if it is determined that the monthly paying user who paid the game fee for this month is a user who has not paid the game fee for last month (step S17: NO), or the game fee for last month and this month It is determined that there is no event game for last month that was offered to other users who logged in during the period when the monthly paying user who paid the game fee for the minute did not log in during the month of last month. In that case (step S18: NO), the notification unit 205 of the server device 20 notifies the event list in which only the event games for this month set in the event information stored in the event information storage unit 224 are displayed. It will be.

In the present embodiment, the notification is performed by the game screen as shown in FIG. Therefore, when the notification unit 205 of the server device 20 requests the execution of the screen display control, the display control unit 206 of the server device 20 controls the screen display unit 160 of the client terminal 10 to display the game screen.

FIG. 11 is an image diagram showing an example of a game screen. On the game screen 500, an event list 501 showing a list of event games for this month that can be provided to monthly billing users is displayed. Here, assuming that this month is September, the event game for September set in the event information stored in the event information storage unit 224, the game fee for August, and the game fee for September were paid. A list of the same event games as the August event games offered to other users who logged in during the month that the monthly paying user did not log in during the month of August are listed.

As described above, according to the information processing system 1 according to the present embodiment, the monthly billing user pays the game fee for this month following the game fee for last month, so that the same event game as the event game for last month can be played. It will be available later this month. This can motivate monthly paying users who paid the game fee for the last month to pay the game fee for this month. Therefore, it is possible to motivate monthly billing users to continuously benefit from the payment of monthly charges.

<< Specific example 1 >>
FIG. 12 is a diagram illustrating a specific example 1 when the same event game as last month's event game is provided again within this month. Here, it is assumed that last month is "August" and this month is "September", and it is assumed that the monthly paying user has paid the game fee for August and the game fee for September.

In this specific example 1, as shown in FIG. 12, a state in which "event A" and "event B" are set as event games for August is shown. Then, the monthly billing user logged in to the battle game at the time when "Event A" was provided and played "Event A", but could not log in to the battle game at the time when "Event B" was provided. The state in which "B" could not be played is shown.

If August is in such a state, in September of the following month, the event re-providing department 203 will provide it to other users who logged in during the period when they did not log in during the month of August. The "Event B" that has been done will be provided again within the month of September to the monthly billing user who did not log in.

As a result, even if you cannot log in to the battle game and play "Event B" during August, the August "Event B" that was provided to other users during the period when you did not log in It will be possible to challenge the same event game as in September. Therefore, users who have paid the game fee for August can be motivated to pay the game fee for September, and will continue to benefit from paying the game fee at regular intervals. It is possible to increase the motivation of the user.

<< Specific example 2 >>
FIG. 13 is a diagram illustrating a specific example 2 when the same event game as the event game for last month is provided again within this month. Here, as in the case of Specific Example 1 described above, it is assumed that last month is "August" and this month is "September", and the monthly paying user pays the game fee for August and the game fee for September. It is assumed that the payment has been completed.

In this specific example 2, as shown in FIG. 13, a state in which "event A" is set as an event game for August is shown. This "event A" is set as an event game for August that can be played over a plurality of days, unlike the above-mentioned specific example 1. Here, it is assumed that the player has been able to play for three days. Then, the monthly billing user logged in at the time when "Event A" was provided on the first day of the three days, but could not log in at the time when "Event A" was provided on the second and third days. The state is shown.

If August is in such a state, in September of the following month, the event re-providing department 203 will only log in for 2 days out of 3 days (2 on the 2nd and 3rd days). (Only for days), the same event game as "Event A" that was playable for the three days will be provided again within the month of September to the monthly paying user who did not log in.

As a result, even if you could not log in to the battle game during August and did not play a part of "Event A", the amount for August that was provided to other users for the number of days that you could not log in It will be possible to challenge the same event game as "Event A" in September. Therefore, users who have paid the game fee for August can be motivated to pay the game fee for September, and will continue to benefit from paying the game fee at regular intervals. It is possible to increase the motivation of the user.

<< Specific example 3 >>
FIG. 14 is a diagram illustrating a specific example 3 when the same event game as the event game for last month is provided again within this month. Here, as in the case of Specific Example 1 described above, it is assumed that last month is "August" and this month is "September", and the monthly paying user pays the game fee for August and the game fee for September. It is assumed that the payment has been completed.

In this specific example 3, as shown in FIG. 14, the first half of "event A" is set as the event game for August, and the second half of "event A" is set as the event game for September. It is shown. That is, unlike the above-mentioned Specific Example 1 and Specific Example 2, this "Event A" is set as an event game that can be played over a plurality of days spanning August and September. Here, it is assumed that the game can be played for 5 days straddling August and September, and the first 3 days (3 days from the 1st to the 3rd day) are set as the event game for August. , It is assumed that the latter two days (two days from the 4th day to the 5th day) are set as the event game for September. Then, it is shown that the monthly billing user could not log in during the provision period of "Event A" from the first day to the third day of the first half of the five days.

If August is in such a state, in September of the following month, the event re-providing department 203 will only log in for the first three days included in August of the five days. (Only for 3 days from the 1st to the 3rd day), the same event game as "Event A" that was playable for the 5 days was given to monthly paying users who did not log in in August. On the other hand, it will be provided again within the month of September. Here, the first three days are provided again in succession after the latter two days (two days from the fourth day to the fifth day) included in September of the plurality of days.

As a result, even if you did not log in for August of "Event A" that spans August and September, only the number of days you did not log in of August was provided to other users. It will be possible to challenge the same event game as "Event A" in September. Therefore, users who have paid the game fee for August can be motivated to pay the game fee for September, and will continue to benefit from paying the game fee at regular intervals. It is possible to increase the motivation of the user.

[Other Embodiments]
The above-described embodiment is for facilitating the understanding of the present invention, and is not for limiting the interpretation of the present invention. The present invention can be modified and improved without departing from the spirit thereof, and the present invention also includes an equivalent thereof. In particular, even the embodiments described below are included in the present invention.

<Event Re-Provision Department>
In the above-described embodiment, the event reproving unit 203 of the server device 20 plays the same event game as last month's event game provided to other users who logged in during the non-login period during the last month during this month. Although the case where the present invention is provided again is described as an example, the present invention is not limited thereto. Event games that are the same as or related to user-specific event games that were offered to the user during the non-login period during the last month and not to other users may be offered again later this month.

For example, the event reproving unit 203 of the server device 20 can play the event game for the last month that was provided during the period when the monthly paying user who paid the game fee for the last month and the game fee for the current month logged in last month. If the game cannot be cleared regardless of whether or not it is played, the same event game as last month's event game that could not be cleared may be provided again within this month.

In this case, in the process of step S18 of the flowchart shown in FIG. 5, it is determined whether or not there is an event game for the last month that could not be cleared among the event games for the last month provided during the login period in the last month. Will be done. That is, in the event reproving unit 203 of the server device 20, the monthly charge user who paid the game fee for last month and the game fee for this month based on the event clear information set in the user information shown in FIG. 6 is in the middle of last month. Identify the event games that could not be cleared from the last month's event games that were offered during the period you logged in to. Then, if at least one or more event games can be identified, the corresponding event games for the last month will exist.

Further, in the above-described embodiment, the case where the event reproving unit 203 of the server device 20 provides the same event game as the event game for the previous month again within this month has been described as an example, but the present invention has been described. It is not limited to this.

For example, the event re-provision unit 203 of the server device 20 can provide an event game related to the event game for last month by the end of this month. The event game related to the event game for last month may be any relationship between the event for last month and the event to be provided again within this month.

Specifically, if "Character X" can be obtained as a privilege by clearing "Quest X", which is the event game for last month, "Quest Y", which is different from "Quest X", will be provided within this month. It is also possible to be done. However, by clearing "Quest Y", the same "Character X" can be obtained as a privilege, and both sides are related.

In addition, if "Character N" can be obtained as a privilege by winning the event game "Lottery Game N" for last month, "Lottery Game M", which is different from "Lottery Game N", will be offered within this month. It is also possible to be done. However, by winning in the "lottery game M", the same "character N" can be obtained as a privilege, and both are related.

Also, if "Character X" can be obtained as a privilege by clearing "Quest X", which is the event game for last month, "Lottery Game Z", which has a different game type from "Quest X", will be offered within this month. It is also possible to do so. However, by winning in the "lottery game Z", the same "character X" can be obtained as a privilege, and both are related.

Further, in the above-described embodiment, the case where the event re-providing unit 203 of the server device 20 provides the same or related event game as the event game for the previous month again within this month has been described as an example. The present invention is not limited to this.

For example, the event reproving unit 203 of the server device 20 may provide an event game that is the same as or related to the event game several months ago, not limited to the last month's event, within this month.

<Bonus granting department>
In the above-described embodiment, the case where the login bonus as an example of the privilege is used has been described, but the present invention is not limited thereto. For example, the present invention can be applied even when a character or item is given as a privilege by clearing a quest in a battle game.

Further, in the above-described embodiment, the privilege granting unit 204 performs the operation required for the monthly charge user who paid the game fee for the last month to pay the game fee for this month at an early stage in one month during the last month. The more it is done, the more it is possible to give benefits that are advantageous to the monthly billing user.

For example, the earlier a monthly billing user who paid the game fee for August performs the renewal procedure operation and the fee payment operation required to pay the game fee for September, the more rare the value is. It is also possible to give high characters and items as a login bonus for September. It is also possible to increase the number of characters and items and grant them. This can motivate users who paid last month's game fees to pay this month's game fees early, so they will continue to benefit from paying game fees at regular intervals. It is possible to further increase the motivation of users who want to do so.

<Notification section>
In the above-described embodiment, the notification unit 205 may give a notification prompting the payment or renewal procedure of the game fee for this month when the last day of last month is approached. Similarly, when approaching the last day of this month, the notification unit 205 may give a notification prompting payment or renewal procedure of the game fee for the next month. At that time, it may be notified that the earlier the payment or renewal procedure of the game fee is performed, the more advantageous benefits are given to the monthly paying user.

1 Information processing system 10 Client terminal 20 Server device 50 Computer 51 CPU
52 RAM
53 ROM
54 Communication interface 55 Input device 56 Display device 57 External interface 58 HDD
100 Client control unit 101 Request transmission unit 102 Response reception unit 120 Client storage unit 140 Client communication unit 150 Operation reception unit 160 Screen display unit 200 Server control unit 201 Game control unit 202 Event provision unit 203 Event provision unit 204 Bonus granting unit 205 Notification unit 206 Display control unit 220 Server storage unit 221 Character information storage unit 222 User information storage unit 223 Login bonus information storage unit 224 Event information storage unit 240 Server communication unit 500 Game screen 501 Event list B Bus line N network

Claims (7)

A user information storage unit that stores user information that includes information for identifying whether or not the user has paid the game fee set at regular intervals, and
With the event providing department that provides the event game that can be played by paying the game fee for the previous fixed period to the user who paid the game fee for the previous fixed period within the previous fixed period. ,
It is possible to play by paying the game fee for the previous fixed period to the user who paid the game fee for the previous fixed period and also paid the game fee for the subsequent fixed period this time. The event re-provision unit that re-provides the same or related event game as the above-mentioned event game within a certain period of time this time.
An information processing device characterized by being equipped with. The information processing device according to claim 1.
The event provider has paid the game fee for the previous fixed period to the logged-in user when the user who paid the game fee for the previous fixed period logged in within the previous fixed period. Offering event games made available by
The event re-providing department does not log in if the user who paid the game fee for the previous fixed period and also paid the game fee for the current fixed period did not log in within the previous fixed period. To the user, the same or related event game as the event game that was provided during the period during which the user did not log in during the previous fixed period is provided again within the current fixed period.
An information processing device characterized by this. The information processing device according to claim 2.
The event providing unit provides the event game that can be played for a plurality of days to the logged-in user when the user who paid the game fee for the previous fixed period logs in within the previous fixed period. Offer to,
The event re-providing department pays the game fee for the previous fixed period, and when the user who paid the game fee for the fixed period this time does not log in within a plurality of days, With the event game, the user who paid the game fee for the previous fixed period to the user who did not log in could play the event game for multiple days for the number of days when the user did not log in. The same or related event game will be offered again within this fixed period.
An information processing device characterized by this. The information processing device according to claim 2 or 3.
When the user who paid the game fee for the previous fixed period logged in within the previous fixed period, the event providing department paid the logged-in user the game fee for the previous fixed period. The event game that can be played by is provided over multiple days spanning the previous fixed period and this fixed period.
The event re-providing department logs in on the day when the user who paid the game fee for the previous fixed period and also paid the game fee for the current fixed period is included in the previous fixed period among multiple days. If there is a day when the user did not log in, the user who paid the game fee for the previous fixed period logs in to the user who did not log in on the day included in the previous fixed period of multiple days. An event game that is the same as or related to the event game that was playable for multiple days for the number of days that did not exist will be provided again within a certain period of time.
An information processing device characterized by this. The information processing apparatus according to any one of claims 1-4.
When the user who paid the game fee for the previous fixed period logged in within the previous fixed period, the event providing department paid the logged-in user the game fee for the previous fixed period. Offering event games made available by
The event re-providing department was provided during the period when the user who paid the game fee for the previous fixed period and also paid the game fee for the current fixed period logged in within the previous fixed period. If the event game cannot be cleared, the same or related event game as the event game that could not be cleared will be provided again within a certain period of time.
An information processing device characterized by this. The information processing apparatus according to any one of claims 1-5.
The benefit that the user who paid the game fee for the previous fixed period performs the operation required to pay the game fee for the current fixed period earlier within the previous fixed period is more advantageous to the user. And the privilege granting department that grants
An information processing device characterized by being equipped with. Computer,
A user information storage means that stores user information that includes information for identifying whether or not the user has paid the game fee set at regular intervals.
An event providing means that provides an event game that can be played by paying the game fee for the previous fixed period to the user who paid the game fee for the previous fixed period within the previous fixed period.
It is possible to play by paying the game fee for the previous fixed period to the user who paid the game fee for the previous fixed period and also paid the game fee for the subsequent fixed period this time. An event re-provision means that provides the same or related event game as the event game that has become, within a certain period of time this time.
A program to function as.

Images