Information processing system, information processing program, information processing device, and information processing method
The system ensures rewards are granted for early-terminated events by extending them over multiple periods, addressing user disappointment and maintaining motivation.
Patent Information
- Application Number
- JP2020147680
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-09-02
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2040-09-02
AI Technical Summary
Existing games do not account for early termination of events, leading to lost opportunities for participation rewards and potentially damaging user expectations and motivation.
An information processing system that allows game events to be held over multiple unit periods, providing rewards for participation during each period, and ensuring that unawarded rewards are granted if the event ends early, maintaining user expectations and fairness.
Prevents user disappointment and maintains motivation by ensuring rewards are granted even if events end early, thus aligning with user expectations and promoting continued participation.
Smart Images

Figure 0007586409000001 
Figure 0007586409000002 
Figure 0007586409000003
Abstract
Description
[Technical field]
[0001] The present invention relates to information processing for providing users with game events that may be held over a number of unit periods, and more particularly to processing for granting users rewards for game events. [Background technology]
[0002] Conventionally, games in which time-limited in-game events are held are known. In addition, among such games, there are also known games in which an event participation reward is given to a user once a day (for example, Non-Patent Document 1). [Prior art documents] [Non-patent literature]
[0003] [Non-Patent Document 1] Nintendo Co., Ltd., "Learn with Sharon! FE Heroes 018 Fight in the Sky Castle", [online], [Retrieved August 21, 2020], Internet (URL: https: / / guide.fire-emblem-heroes.com / eve003 / ) Summary of the Invention [Problem to be solved by the invention]
[0004] In the above-mentioned games, the duration of the event is generally determined in advance, and the user is given the opportunity to participate in the event until the scheduled end date of the duration. Therefore, in such games, no consideration has been given to the case where the event ends early.
[0005] Here, if the event ends early, the user may lose the opportunity to receive part of the participation reward that was scheduled to be given to the user, which may result in a result contrary to the user's expectations. In particular, for a user who intends to participate in the event every day, the user would have originally expected to receive all of the participation reward, but losing the opportunity to participate in the event due to the early end means that the user loses the opportunity to obtain part of the participation reward, which results in a result contrary to the user's expectations. There is room for improvement in terms of not damaging such user expectations.
[0006] Therefore, an object of the present invention is to provide an information processing system, an information processing program, an information processing device, and an information processing method that prevent a user's expectations regarding rewards that were scheduled to be awarded from being damaged even if an event ends early. [Means for solving the problem]
[0007] In order to achieve the above object, for example, the following configuration example can be given.
[0008] An example of the configuration is an information processing system for providing a user with a game event that may be held over a plurality of unit periods, and includes an update means, a presentation means, a first granting means, a termination means, and a second granting means. The update means updates the progress of the game event based on the participation of the user or another user different from the user in the game event. The presentation means presents to the user information on a plurality of participation rewards, which are rewards granted for participating in the game event during each unit period within the period in which the game event is held, and in which the reward contents for at least two or more unit periods determined in advance are preset regardless of the progress. The first granting means grants to the user a participation reward associated with the unit period to which the timing of the participation belongs in response to the user's participation in the game event. The termination means terminates the progress of the game event when the progress of the game event satisfies a termination condition. The second granting means grants to the user at least a portion of the ungranted reward, which is the participation reward that has not been granted to the user, if the number of occurrences of a unit period from the start of a game event to the progress of the game event satisfying an end condition is less than the above-mentioned specified number of times.
[0009] According to the above configuration example, when an event ends in a period shorter than the originally scheduled period and in a number of days shorter than the upper limit number of times for which the reward is to be given, at least a portion of the presented rewards that have not been given can be given to the user. This can prevent the user's expectations that are created by the advance presentation of the reward from being lost, and can also prevent the user's motivation to participate in the event from being lost. Therefore, even in an event that may end early, the user's motivation to participate in the event can be maintained.
[0010] As another configuration example, the second granting means grants the ungranted reward to the user for the number of times the unit period occurs until the progress state satisfies the end condition, which is less than the predetermined number of times.
[0011] According to the above configuration example, when an event ends early, the rewards that have not been granted to the user are granted to the user for the number of times that the number of occurrences in a unit period is less than the upper limit number of times for granting the rewards. This makes it possible to prevent the expectation of the user who was expecting the reward to be granted from being damaged.
[0012] As another configuration example, the second granting means may grant to the user only the participation reward from the ungranted rewards that would not be granted to the user even if the user had participated in each of the unit periods until the end of the game event.
[0013] According to the above configuration example, when an event ends early, the reward that was lost for all users can be granted to the user. This makes it possible to maintain a sense of fairness among users. That is, in a unit period during which a reward can be granted, all users are given an equal opportunity to be granted the reward, and whether or not to participate is left to the discretion of each user, so the difference in the presence or absence of a reward during such a period cannot be said to be unfair. On the other hand, if the event ends before the number of times the unit period arrives is less than the upper limit number of times for which a reward can be granted, the reward for the number of times that is short of the upper limit number will not be granted even if the user participates every day until the end of the event. Therefore, by granting only the reward that was lost for all users, it is possible to prevent a sense of fairness among users from being impaired.
[0014] As another configuration example, the second granting means may grant at least a portion of the ungranted reward to a user who is using an application in which a game event may be held, but who has never participated in the game event during the period in which the game event is held.
[0015] According to the above configuration example, even if a user is not participating at the time of the early end of the event, if the event had not ended early, it could be said that they could have participated later. Therefore, by granting a part of the ungranted reward to such users who were not participating at the time of the early end, it is possible to maintain the users' expectations and a sense of fairness among users.
[0016] As another configuration example, when a user participates in the game event, the user may be given a participation reward that corresponds to a unit period determined based on the number of unit periods in which the user has previously participated in the game event.
[0017] According to the above configuration example, the number of days of participation can be counted based on the user's criteria to determine the participation reward. This allows the user to receive a participation reward according to the number of times the user actually participates in the event. This provides motivation for continued participation in the event.
[0018] Another configuration example is an information processing system for providing a user with a game event that may be held over a plurality of unit periods, comprising a presenting means, a first granting means, an updating means, a terminating means, and a second granting means. The presenting means presents to the user information on a plurality of participation rewards, which are rewards granted for participating in the game event during each unit period within the period in which the game event is held, and in which an upper limit number of unit periods, which is at least two or more unit periods in which the rewards may be granted throughout the entire period in which the game event is held, is set, and the reward content is preset regardless of the progress status. The first granting means grants to the user a participation reward associated with the unit period to which the timing of the participation belongs in response to the user's participation in the game event. The updating means updates the progress status of the game event based on the participation of the user or another user different from the user in the game event. The terminating means terminates the progress of the game event when the progress status of the game event satisfies a termination condition. The second granting means grants to the user at least a portion of the ungranted reward, which is the participation reward that has not been granted to the user, if the number of unit periods that occur from the start of the game event to the progress of the game event satisfying the end condition is less than the upper limit number of unit periods.
[0019] According to the above configuration example, when the event ends in a period shorter than the originally scheduled period and in a number of days shorter than the upper limit number of times the reward is to be given, at least a portion of the presented rewards that have not been given can be given to the user. This makes it possible to prevent the user's expectations that are created by the advance presentation of the reward from being lost, and also to prevent the user's motivation to participate in the event from being lost. Effect of the Invention
[0020] According to this embodiment, it is possible to prevent the sense of anticipation given to the user by the presentation of the participation reward from being ruined by the early end of the event, and it is also possible to prevent the motivation to participate in the event from being diminished. [Brief description of the drawings]
[0021] [Figure 1] FIG. 1 is a schematic diagram showing an overall image of an information processing system according to an embodiment of the present invention; [Diagram 2] Block diagram showing the hardware configuration of the server 101 [Diagram 3] A block diagram showing the hardware configuration of the information processing terminal 102. [Figure 4] An example of a game screen [Diagram 5] An example of a game screen [Figure 6] A diagram for explaining the granting of participation rewards [Figure 7] A diagram for explaining the granting of participation rewards [Figure 8] A memory map showing an example of various data stored in the memory 112 of the server 101. [Figure 9] An example of the data configuration of the user data 403 [Figure 10] An example of the data configuration of the event data 404 [Figure 11] An example of the data configuration of the participation reward information 424 [Figure 12] A memory map showing an example of various data stored in the memory 122 of the information processing terminal 102. [Figure 13] A flowchart showing details of the event processing executed by the server 101 (server-side event processing). [Figure 14] Flowchart showing details of the in-progress process (server side) [Figure 15] Flowchart showing details of the in-progress process (server side) [Figure 16] Flowchart showing details of post-termination processing (server side) [Figure 17] FIG. 4 is a diagram showing the relationship between the value of the event progress counter 406 and the number of remaining days. [Figure 18] 1 is a flowchart showing details of event processing executed by the information processing terminal 102. [Figure 19]Flowchart showing details of in-session processing (terminal side) [Figure 20] Flowchart showing details of post-termination processing (terminal side) DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0022] An embodiment of the present invention will be described below. FIG. 1 is a schematic diagram showing an overall image of an information processing system according to this embodiment. The information processing system 100 of this embodiment includes a server 101 and a plurality of information processing terminals 102. The server 101 and the information processing terminals 102 are configured to be able to communicate with each other via the Internet 103. In this embodiment, information processing is executed with such a configuration, and in the following, game processing will be described as an example of the information processing. Specifically, a game application is installed on the information processing terminal 102, and game processing is executed while communicating with the server 101 as necessary.
[0023] [Server hardware configuration] Next, a hardware configuration of the server 101 will be described. Fig. 2 is a block diagram showing the hardware configuration of the server 101. The server 101 includes at least a processor 111, a memory 112, and a communication unit 113. The processor 111 executes various programs for controlling the server 101. The memory 112 stores various programs executed by the processor 111 and various data used. The communication unit 113 is connected to a network by wired or wireless communication, and transmits and receives predetermined data to and from the information processing terminal 102 or other servers (not shown).
[0024] [Hardware configuration of information processing terminal] FIG. 3 is a block diagram showing a hardware configuration of an information processing terminal 102 in which game processing according to this embodiment is executed. Here, in this embodiment, the information processing terminal 102 is assumed to be, for example, a smart device such as a smartphone or a tablet, a stationary game device, a portable game device, a personal computer, or the like. In the explanation of this embodiment, an information processing terminal (for example, a smartphone) having a display screen and a touch panel in an integrated form will be explained as an example. Therefore, input operations are mainly input to the touch panel. However, in other embodiments, the input operation may be performed using a physical controller connected wirelessly or by wire to the information processing terminal 102, or may be performed using an input device configured to be integrated with the information processing terminal 102, for example.
[0025] In FIG. 3, the information processing terminal 102 includes a processor 121, a memory 122, an operation unit 123, a display unit 124, and a communication unit 125. The processor 121 controls the operation of the information processing terminal 102 by executing a game process described later and a system program (not shown) for controlling the overall operation of the information processing terminal 102. The processor 121 may be equipped with a single processor or may be equipped with multiple processors. The memory 122 stores various programs executed by the processor 121 and various data used in the programs. The memory 122 is, for example, a flash EEPROM or a hard disk device. The operation unit 123 is an input device for receiving operations from a user, and in this embodiment, a touch panel is mainly assumed. In other embodiments, the operation unit 123 may be various pointing devices, various push-down buttons, an analog stick, or the like. The display unit 124 is typically a liquid crystal display device. The communication unit 125 is connected to a network via wired or wireless communication, and transmits and receives predetermined data to and from the server 101 .
[0026] [Outline of game processing in this embodiment] Next, an overview of the game processing executed in this embodiment will be described. The game processing assumed in this embodiment is processing related to an in-game event held in a predetermined game application, and more specifically, processing related to the awarding of a reward for the event.
[0027] The game application assumed in this embodiment may be any game in which an in-game event as described below can be held. For example, the game application may be of any genre, such as a role-playing game, a simulation game, an action game, or a puzzle game. In this embodiment, an SRPG (simulation role-playing game) is taken as an example. Each user can obtain multiple "characters" in the course of playing the SRPG. The obtained characters can be used in the in-game events as described below.
[0028] Next, an outline of an in-game event (hereinafter simply referred to as an event) assumed in this embodiment will be described. This event is assumed to be a cooperative event in which multiple users participate and cooperate. In addition, the event is an event in which a predetermined holding period is set in multiple unit periods, for example, with "one day" being taken as a "unit period," and is held over multiple unit periods. Hereinafter, these "multiple unit periods" will be referred to as an event holding period. In this embodiment, one day consisting of a period from 0:00:00 to 23:59:59 will be described as an example of the unit period. In addition, in this embodiment, a case in which the event holding period is 10 days will be taken as an example.
[0029] In this embodiment, an event in which a boss character called an "event boss" appears and is common to all participants will be described as an example. The purpose of the event (event end condition) is to reduce the HP (hit points) of the event boss to 0 during the event period. Each user who participates in the event has their own character attack the boss character. This can damage the event boss and reduce the HP of the event boss. In this way, the event is a situation in which each user who is an event participant attacks the event boss individually to reduce the HP of the event boss, which is common to all participants. If the HP becomes 0 during the event period, the goal of the event is achieved and the event ends at that point. The event also ends if the event period of 10 days has passed without the HP becoming 0.
[0030] Note that the condition for ending the event is merely an example, and in other embodiments, other conditions may be set as the event ending condition. For example, the ending condition may be defeating a predetermined number of predetermined boss characters.
[0031] Next, the event progress of this embodiment will be illustrated with specific screen examples and operation examples. In this embodiment, first, the user can participate in an event by performing a predetermined "event participation operation." Also, in this embodiment, multiple event participations are possible within the unit period. Note that, in other embodiments, a limit may be placed on the number of times that an event can be participated in. For example, an event can be participated in only once a day.
[0032] As an example of the event participation operation, in this embodiment, an example of performing a predetermined operation on a game screen related to the event will be given. Fig. 4 shows an example of a game screen related to an event of this embodiment (hereinafter referred to as an event screen). The event screen of Fig. 4 is displayed in response to a user selecting an icon indicating "event" from, for example, a home screen of a game application. In the example screen shown in Fig. 4, an event information display area 201, a participation reward presentation area 202, a participation button 203, and a back button 204 are displayed.
[0033] Various information related to the event may be displayed in the event information display area 201. For example, an image of the event boss, an image of a character owned by the player that will be used in the event, that is, an image of a character that will attack the event boss, etc. may be displayed.
[0034] An image showing the contents of the participation reward is displayed in the participation reward display area 202. The participation reward will be described later.
[0035] The participation button 203 is a button for participating in the event. Specifically, a tap operation on the participation button 203 corresponds to the event participation operation. In the present embodiment, the event participation operation also serves as an operation for attacking the event boss. That is, the event participation operation includes an attack operation on the event boss. One event participation operation corresponds to one attack. By performing the event participation operation multiple times in one day, multiple attacks on the event boss are possible. By performing the event participation operation, a state in which a character set in advance by the user as an attacking member against the event boss attacks the event boss and a performance showing the damage value of the attack are displayed. Note that, although the present embodiment has given an example in which the event participation operation also serves as an attack operation against the event boss, in other embodiments, it is not necessary for the event participation operation to also serve as such an attack operation. For example, in response to the event participation operation, a transition may be made to a game screen for attacking the event boss that is separately prepared. For example, a game screen in which the event boss and the user's owned character are displayed in a predetermined game field may be displayed. Then, the user may operate the owned character on this screen, select a desired attack method, and perform an attack on the event boss.
[0036] Next, a back button 204 is a button for closing the event screen.
[0037] Next, the participation reward shown in the participation reward presentation area 202 will be described. In this event, a plurality of rewards called "participation rewards" are prepared for the purpose of encouraging the user to participate in the event. This participation reward is available in the game application in which the event is held. In this example, in order to explain an SRPG as an example, for example, equipment such as weapons and armor that can be used in the game, consumable items such as recovery items, and in-game currency are prepared as the participation reward. In addition, various characters may be used as the participation reward. Furthermore, magic, skills, special moves, and other things that can be acquired by the player character to advance the game advantageously may be used as the participation reward. In addition, any thing that can be used in the game application in which the event is held may be used as the participation reward.
[0038] Here, in this event, the participation reward is set for each unit period. More specifically, the participation reward is awarded only once per day. In other words, in this embodiment, an upper limit is set on the number of times the participation reward is awarded within a unit period. In this embodiment, an example is given of once per day, but this is not limiting, and in other embodiments, for example, the participation reward may be awarded up to three times per day.
[0039] In addition, with regard to the timing of granting the participation reward, in this embodiment, the participation reward is granted at the timing of the first participation in a certain unit period. The participation reward is not granted for the second or subsequent participation in that unit period. Therefore, in FIG. 4, when the first event participation operation is performed within the unit period, a pop-up display 207 as shown in FIG. 5 is displayed prior to the display of the attack effects and the like as described above. The pop-up display 207 indicates that the participation reward has been received for the event participation operation. Then, when the pop-up display 207 is closed by a predetermined operation, the display of the attack effects and the like as described above begins.
[0040] In this embodiment, an example is given in which the participation reward is granted at (almost simultaneously with) the event participation operation, but the timing of granting the participation reward is not limited to this. The participation reward may be granted at a predetermined timing after a predetermined time has elapsed since the event participation operation was performed. For example, the participation reward may be granted half a day after the event participation operation has elapsed, or one day after the event participation operation has elapsed. Alternatively, a configuration may be adopted in which the participation reward is sent to a so-called "present box" and the user receives it at a timing of their choice.
[0041] In addition, in this embodiment, there is an upper limit to the number of unit periods for which a participation reward is given. In other words, an upper limit is set on the number of unit periods for which a participation reward can be given during the entire event period (hereinafter, the upper limit number of unit periods). In addition, the upper limit number of unit periods is assumed to be two or more unit periods. In this embodiment, the upper limit number of unit periods is described as 5. That is, it is assumed that participation rewards for five unit periods (five days in total) are set in advance. Therefore, it is not possible to obtain all of the prepared participation rewards in only one unit period (one day in this example). In other words, in order for a user to obtain all of the participation rewards, participation in the event is required for at least the upper limit number of unit periods. In this way, it is possible to provide a motivation for the user to play the event continuously over a plurality of unit periods.
[0042] In addition, because there is such an upper limit on the number of unit periods, if a user is given five participation rewards, no more participation rewards will be given to the user even if the user participates in the event in the subsequent unit periods. In the following description, the participation reward for the first participation will be called "participation reward A", the second participation reward will be called "participation reward B", the third participation reward will be called "participation reward C", the fourth participation reward will be called "participation reward D", and the fifth participation reward will be called "participation reward E". The contents of these participation rewards may all be the same or different. In this embodiment, the case where the contents of the participation rewards for the five times are all set to be different will be taken as an example. In addition, the number of participation reward contents for each unit period may be any number. For example, the participation reward A may be "three items A", the participation reward B may be "five items B", and the participation reward C may be "one weapon C".
[0043] In this embodiment, the content of the participation reward as described above is presented so that the user can confirm it in advance. In the example of FIG. 4, the participation reward corresponding to the above-mentioned five unit periods is presented in the participation reward presentation area 202. In FIG. 4, the participation reward images 206A to 206E corresponding to the above-mentioned participation rewards A to E are aligned horizontally starting from the left end. Note that the participation reward image 206A is grayed out and has a check mark displayed, indicating that the participation reward A has already been awarded.
[0044] As described above, each user participating in the event can attack the event boss by performing an event participation operation from the event screen, and reduce the HP of the event boss, which is common to all participating users. Here, as described above, the event ends when the HP of the event boss becomes 0, even before the last day of the event period has passed. Therefore, for example, if the HP of the event boss becomes 0 on the third day from the start of the event and the event ends, the opportunity to obtain the fourth and fifth participation rewards D and E of the above five participation rewards will be lost. In other words, the participation rewards D and E are rewards that will not be given to the user even if the user participates in the event every day from the start to the end of the event. As described above, since the contents of the participation reward are presented to the user on the event screen, for example, a user who intends to participate in the event every day may have expectations of obtaining all five participation rewards. However, if the event ends early as described above, it will be contrary to the user's expectations, and may lead to the user losing interest in the game or event. Therefore, in this embodiment, if the number of unit periods until the end of the event (i.e., the number of days from the start to the end of the event) is smaller than the upper limit number of unit periods, a process is performed to grant the participation rewards D and E for which the opportunity to receive them was lost to the user. This makes it possible to achieve results that meet the user's expectations. Also, in this embodiment, the participation rewards for which the opportunity to receive them was lost are granted to all users of the game application, including users who did not participate in the event (hereinafter, non-participating users). Note that the "user of the game application" here is assumed to be, for example, a user who has registered as a user of the game application and whose user data is recorded in server 101.
[0045] In this embodiment, some examples of the participation reward granting patterns as described above will be given. Here, as described above, the event period is a maximum of 10 days, and the period from August 1st to August 10th will be described as a specific example. Also, as described above, a case where the participation reward is set five times will be taken as an example. Also, a case where the HP of the event boss becomes 0 in fewer days (1 to 4 in this example) than the upper limit unit period number (5 in this example) is called "early defeat". Also, the participation reward that is to be granted separately to the user when the above-mentioned grant opportunity is lost is called "compensation target reward" in the following description. FIG. 6 shows in table form the relationship between the number of days from the start of the event, the unit period, the remaining days of the event, and the compensation target reward when an early defeat occurs, assuming that a certain user participates in the event every day. In the example of FIG. 6, if an early defeat occurs, for example, at 15:00 on the first day of the event (August 1st), the participation rewards B to E, that is, the participation rewards for the second to fifth times, will be the compensation target reward. Also, if an early defeat occurs at 15:00 on the third day of the event (August 3rd), only participation rewards D to E, that is, the participation rewards for the fourth and fifth times, will be compensated. Also, defeats of the event boss from the fifth day onwards will not be treated as "early defeats". Therefore, no compensation rewards will be generated from this point onwards.
[0046] Next, FIG. 7 shows in table form the relationship between multiple users with different participation statuses during the event period and the rewards given depending on whether or not there was an early defeat. In this figure, four users, User A to User D, are illustrated on the vertical axis. Each user's event participation status is different, and User A is an example of a case where User A participates only on the first day after the event starts. User B is an example of a case where User B participates only on the first and third days after the event starts. User C is an example of a case where User C participates every day until the event ends after the event starts. User D is an example of a case where User D does not participate in the event. The horizontal axis shows the participation rewards that are obtained as a result of an early defeat and the participation rewards that are obtained as a result of an early defeat. In addition, here, an example is shown of an early defeat occurring on the third day from the start of the event. In addition, an example is shown of an early defeat not occurring when the HP of the event boss becomes 0 on the seventh day from the start of the event.
[0047] In FIG. 7, first, for user A who participated only on the first day, if an early defeat occurs, participation reward A is given for participation on the first day (first time in total). In addition, participation rewards D and E corresponding to the fourth and fifth participations are given as compensation rewards. Here, the reason why the second and third participations are not compensation rewards is because user A was given the opportunity to participate on the second and third days after the start of the event. In other words, the compensation is the participation reward that was lost for all users. In this case, all users are equal in the fourth and fifth participation rewards, and the opportunity to participate in the event is lost, so no user is given this participation reward. However, the second and third participation rewards can be given if user A participates in the event, and there are also users who are given the second and third participation rewards, such as users B and C described later. If a participation reward corresponding to the day's participation is given to a user who did not participate despite having the opportunity to participate in the event, it may cause a sense of unfairness among users, such as user C who participates every day. Therefore, in this embodiment, only the participation reward that the opportunity to be awarded to all users was lost is given to all users as the compensation reward.
[0048] On the other hand, if the event is not defeated early, User A will be awarded Participation Reward A for participating on the first day. In other words, User A only participated once on the first day, even though he was given seven opportunities (for seven days) to participate during the event period.
[0049] Next, looking at user B who only participated on the first and third days, in the case of early defeat, participation reward A for participation on the first day will be awarded. Also, participation reward B for participation on the third day (second participation overall) will be awarded. In addition to this, for the same reasons as above, participation rewards D and E corresponding to the fourth and fifth participation will be awarded as compensation. On the other hand, if there is no early defeat, since the user only participated twice in the seven days until the end of the event, only participation rewards A and B will be awarded.
[0050] Next, in the case of user C who participated in the event every day until the boss's HP reached 0, in the case of early defeat, participation rewards A to C will be awarded for the 1st to 3rd participations, and participation rewards D and E will be awarded as compensation rewards. On the other hand, if the boss is not defeated early, participation rewards A to E will be awarded for the 1st to 5th participations. In other words, participation rewards D and E in this case are not compensation rewards.
[0051] Next, for user D who did not participate in the event, if an early defeat occurs, participation rewards D and E will be awarded as compensation rewards. On the other hand, if there is no early defeat, there will be no compensation reward, and therefore no participation reward will be awarded.
[0052] [Details of the game processing in this embodiment] Next, the process related to the above-mentioned event in this embodiment will be described in more detail with reference to Figures 8 to 21. Note that here, the process related to the above-mentioned event and the granting of the participation reward will be mainly described, and the description of other game processes will be omitted.
[0053] [About data usage] First, various data used in the processing of this embodiment will be described. First, data used in the server 101 will be described. Fig. 8 is a memory map showing an example of various data stored in the memory 112 of the server 101. The memory 112 of the server 101 stores a server-side program 401, a user database 402, event data 404, item master data 405, an event progress counter 406, and the like.
[0054] The server-side program 401 is a program for executing the game application in this embodiment. This program also includes code for executing the event processing according to this embodiment. In addition, the program also includes code for executing a user login process, a process for transmitting or receiving predetermined user data 403 included in a user database 402 to the information processing terminal 102, and the like.
[0055] The user database 402 is a database that is a collection of data related to each user who plays the game application according to this embodiment. In this embodiment, the user database 402 is a database configured with user data 403 as shown in Fig. 9 as one record. After a login process is performed in the information processing terminal 102, a process of acquiring the user data 403 corresponding to the user from the server 101 is performed as necessary.
[0056] The data configuration of the user data 403 will be described with reference to FIG. 9. The user data 403 shown in FIG. 9 includes a user ID 411, attack operation history information 412, participation reward grant history information 413, compensation target reward grant information 414, possessed item data 415, possessed character data 416, and the like. The user ID 411 is an ID for uniquely identifying each user. The attack operation history information 412 is a history of the date and time when the user performed an attack operation on an event boss for a certain event, recorded so as to be distinguishable for each event. The participation reward grant history information 413 is information indicating the history of granting of the participation reward to the user. That is, it is information indicating how many times the participation reward has been granted. This information is also recorded so as to be distinguishable for each event. The compensation target reward grant information 414 is information recording whether or not the compensation target reward has been granted for each event, and the contents thereof. The possessed item data 415 is information indicating the in-game items owned by the user. The owned character data 416 is information indicating the above-mentioned characters owned by the user. In addition, although not shown in the figure, the user data 403 also includes data indicating the progress of the game (so-called save data) and information about each user, such as the user's handle name.
[0057] Returning to Fig. 8, event data 404 is data defining the in-game event. Fig. 10 shows an example of the data configuration of the event data 404. The event data 404 is data in a table format, with items such as an event ID 421, an event status 422, event schedule information 423, participation reward information 424, initial HP 425, and current HP 426 being one record. Each record of the event data 404 can be added, changed, or deleted by an administrator of the game application, etc., as necessary.
[0058] The event ID 421 is an ID for uniquely identifying the in-game event. The event status 422 is information indicating whether the event is "not yet started", "ongoing", or "finished". The event schedule information 423 is information defining the start date and end date of the event. Note that if an early defeat occurs as described above, the event may end earlier than the end date defined here.
[0059] The participation reward information 424 is data that defines the content of the participation reward in the event. In the example of this embodiment, participation rewards for up to five times and their contents are defined. FIG. 11 shows an example of the data configuration of the participation reward information 424 in this embodiment. As shown in FIG. 11, the participation reward information 424 is data in a table format that is composed of a number of times awarded 431 and reward contents 432. In the example of FIG. 11, information on in-game items that are the reward contents and the number of items to be awarded are defined for each of the first to fifth times. Needless to say, the reward is not limited to in-game items, and in-game currency may be defined.
[0060] Returning to FIG. 10, initial HP 425 is data that defines the initial HP of the event boss. Current HP 426 is data that indicates the current HP of the boss of the event. The value of initial HP 425 is subtracted in response to attacks from participating users. When the value of current HP 426 finally reaches 0, the event boss is deemed to have been defeated, and processing for ending the event is carried out.
[0061] In addition, although not shown in the figure, the event data 404 also includes data defining the image and attack method of the event boss, information defining the conditions for ending the event, and various other data used in holding the event.
[0062] 8, the item master data 405 is data that defines all in-game items in the game application of this embodiment. A predetermined in-game item selected from the data can be defined as the participation reward.
[0063] The event progress counter 406 is data used to manage the progress of an in-game event in the process according to this embodiment. Specifically, the initial value is 1, and the counter is counted up by 1 each time a predetermined period has passed since the start of the event. In this embodiment, it is assumed that the period for the count-up is defined as "one day", which is the same as the unit period. That is, the event progress counter 406 is counted up by 1 each time 24 hours have passed since the start of the event. In another example, the period for the count-up may be 6 hours, and the counter may be configured to count up by 4 per day. In this embodiment, this counter can be used to manage the event period divided into terms of several hours, and to grasp the remaining number of days of the event, etc.
[0064] Additionally, the memory 112 of the server 101 stores various data necessary for holding events and processing games.
[0065] Next, a description will be given of various data stored in memory 122 of information processing terminal 102. Fig. 12 is a memory map showing an example of various data stored in memory 122 of information processing terminal 102. Memory 122 of information processing terminal 102 stores a terminal-side game program 501, image data 502, login data 503, operation data 504, working data 505, etc.
[0066] The terminal-side game program 501 is a program for executing the game application according to this embodiment, and includes code for executing the processes related to the above-mentioned events.
[0067] Image data 502 is data of various images displayed in the game application including the above events.
[0068] Login data 503 is various data necessary for logging in to the game application of this embodiment.
[0069] The operation data 504 is data indicating various operation contents performed on the operation unit 15. In this embodiment, the operation data 504 includes data indicating the presence or absence of input to a touch panel serving as the operation unit 15, the touch coordinates, and the like, and data indicating the pressed state of various buttons (not shown), and the like.
[0070] The working data 505 is various data that is temporarily used in the processing related to the above-mentioned events, and can be generated and stored as necessary during the execution of the game processing.
[0071] [Server 101 processing details] Next, details of the event processing according to this embodiment will be described. First, details of the event processing executed by the server 101 will be described. Here, an example will be described in which an event is currently being held, that is, the event start date has passed. More specifically, an event related to a record with the event ID 421 of "0002" in FIG. 10 will be described as an example. Regarding the change of the event status 422 from "before starting" to "in progress", the processor 111 may determine whether or not the event start date has arrived based on the current date and time and the event schedule information 423. Then, if the event start date has arrived, a process may be appropriately performed to change the event status 422 from "before starting" to "in progress".
[0072] Fig. 13 is a flowchart showing details of the event processing (server-side event processing) executed by server 101. First, in step S11 of Fig. 13, processor 111 refers to event status 422 and determines whether the event is being held or has ended. If the event is being held (YES in step S11), processor 111 executes during-event processing (server side) in step S12. On the other hand, if the event has ended (NO in step S11), processor 111 executes after-end processing (server side) in step S13.
[0073] [Server-side processing during an event] 14 and 15 are flow charts showing details of the in-event process (server side) in step S12. The process loop of steps S21 to S28 in this process is repeated at a predetermined processing cycle. When performing the processes shown in Figs. 14 and 15, a notification that an event is being held may be sent to the information processing terminal 102 as necessary. In Fig. 14, first, in step S21, the processor 111 determines whether or not participation instruction data transmitted from the information processing terminal 102 has been received. The participation instruction data is data sent to the server 101 in response to the operation of the participation button 203 in the information processing terminal 102. If the result of this determination is that the participation instruction data has not been received (NO in step S21), the process is repeated until the participation instruction data is received. On the other hand, if the participation instruction data has been received (NO in step S22), the process is repeated until the participation instruction data is received (NO in step S23). 1 If the answer is YES in step S22, processor 111 identifies the user who transmitted the participation instruction data.
[0074] Next, in step S23, processor 111 determines whether or not it is possible to grant a participation reward for the unit period for which the participation instruction data was transmitted. Specifically, processor 111 refers to participation reward grant history information 413 for the user, and determines whether or not a participation reward has already been granted to the user in the current unit period. If the result of the determination is that the participation reward for the current unit period has not yet been granted (YES in step S23), it is possible to grant a participation reward. In this case, in step S24, processor 111 determines the content of the participation reward to be granted based on participation reward information 424. Then, processor 111 grants the determined participation reward to the user. Specifically, processor 111 adds the participation reward to possessed item data 415 of the user. Thereafter, the process proceeds to step S25, and transitions to execution of game processing. On the other hand, if the result of the above determination is that the participation reward for the current unit period has already been granted (NO in step S23), the process of step S24 is skipped and the process proceeds to the next process.
[0075] 15, processor 111 transmits data relating to the current event boss to information processing terminal 102 which transmitted the participation instruction data. Specifically, processor 111 transmits the data including the value of current HP 426 to information processing terminal 102. Information processing terminal 102 executes game processing based on the data transmitted here (described later), and transmits data indicating the result to server 101.
[0076] Next, in step S26, processor 111 determines whether or not result data of the game processing has been received from information processing terminal 102. As a result, if the result data has not yet been received (NO in step S26), the process of receiving the result data is repeated, and the result data is awaited. On the other hand, if the result data has been received (YES in step S26), then in step S27, processor 111 updates the value of current HP 426 based on the result data. That is, a process is executed to subtract HP of the event boss in accordance with the result of the user's attack on the event boss.
[0077] Next, in step S28, it is determined whether or not current HP 426 of the event boss has become 0. As a result, if it is not 0 (NO in step S28), the process returns to step S21 and is repeated. On the other hand, if it has become 0 (YES in step S28), in order to end the holding of the event, in step S29, processor 111 sets a value indicating "event ended" to holding status 422. Then, the in-open process (server side) is ended.
[0078] [Server 101 processing after the event ends] Next, the process of the post-termination process (server side) in step S13 of FIG. 13 will be described. FIG. 16 is a flow chart showing the details of the post-termination process (server side). First, in step S41, processor 111 identifies the number of days in which the HP of the event boss became 0, and judges whether or not an early defeat as described above has occurred. Any method of judgment may be used, but in this embodiment, the judgment is made as follows. First, processor 111 acquires the value of event progress counter 406. Then, the number of remaining days of the event is calculated assuming that the event is held until the last day. As described above, in this embodiment, the case where event progress counter 406 is counted up by 1 every time 24 hours have passed since the start of the event is taken as an example. In this case, the number of remaining days is calculated assuming that the event is held until the last day of the event period by subtracting the progress counter value from the maximum number of days for which the event is held (10 in this example). For reference, FIG. 17 shows the relationship between the value of event progress counter 406 and the number of remaining days in a table format. In the example of FIG. 17, for example, on the third day after the start of the event, the event progress counter 406 is 3, and the number of remaining days if the event is held until the final day is 7 days.
[0079] If the remaining number of days for the event can be calculated as described above, it is determined whether or not the remaining number of days is greater than the upper limit number of unit periods (5 in this example). That is, the processor 111 determines whether or not the remaining number of days > the upper limit number of unit periods. If this condition is met, it is determined that early defeat has occurred, and if not, it is determined that early defeat has not occurred.
[0080] 16, if it is determined in step S41 that an early defeat has occurred (YES in step S41), then in step S42, processor 111 determines whether the compensation target reward has already been awarded. If the compensation target reward has already been awarded (YES in step S42), the process proceeds to step S45 described later.
[0081] On the other hand, if the compensation target reward has not yet been given (in other words, if the post-event process is executed for the first time after the event ends), in step S43, the processor 111 specifies the participation reward to be the compensation target reward described above. Any method may be used for this specification, but for example, assume that an early defeat occurs on the fourth day from the start of the event (August 4 in this example). In this case, assuming that the event participation reward has been distributed up to the fourth time, the fifth event participation reward is specified as the compensation target reward. For example, the maximum number of days held - the remaining number of days is calculated as the number of times that is assumed to have been given. If an early defeat occurs on August 4, 10-6=4 is calculated. In this case, assuming that the opportunity to give up to the fourth time has been given to the user, only the fifth time is specified as the compensation target reward. In other words, the opportunity to participate in the event up to the fourth day has been given to all users, but the opportunity to give the fifth participation reward has also been lost because the opportunity to participate in the event has been lost for all users. Therefore, the fifth participation reward is determined as the compensation target reward. Similarly, if an early defeat occurs on the third day after the start of the event (August 3rd in this example), the participation rewards for the fourth and fifth times will be determined as the compensation rewards.
[0082] Next, in step S44, processor 111 executes a process of granting the determined compensation target reward to all users of the game application. That is, processor 111 executes a process of adding the compensation target reward to each user's owned item data 415, regardless of whether the user participated in the event. Furthermore, processor 111 records information indicating the date and time of the addition and the reward content in compensation target reward grant information 414.
[0083] On the other hand, if the result of the determination in step S41 above is that an early defeat has not occurred (NO in step S41), the processes in steps S42 to S44 above are skipped and the process proceeds to the next step.
[0084] Next, in step S45, processor 111 determines whether or not an inquiry as to whether the event is being held has been received from any of information processing terminals 102. If the inquiry has been received (YES in step S45), in step S46 processor 111 transmits information that the event has ended to information processing terminal 102 that made the inquiry. On the other hand, if the inquiry has not been received (NO in step S45), the end-of-event process (server side) ends. Therefore, once the compensation target remuneration has been awarded, the process of server 101 after the event ends is essentially a process of simply returning an indication that the event has ended in response to an inquiry from an information processing terminal about holding the event.
[0085] [Processing of information processing terminal 102] Next, details of the event processing executed by the information processing terminal 102 will be described. FIG. 18 is a flowchart showing details of the event processing executed by the information processing terminal 102. The processing is started when a predetermined operation for transitioning to an event screen is performed, such as a user tapping an "event" icon arranged on the home screen of a game application. In step S51 of FIG. 18, the processor 121 first determines whether the event is being held or has ended. Any method of determination may be used, but for example, a process of inquiring the server 101 as to whether the event is being held or not may be performed, and based on the response result, a determination as to whether the event is being held or not may be performed. Alternatively, a method of obtaining calendar data in which an event is scheduled to be held from the server 101 and comparing it with the current date and time to make a determination may be used. In this case, if the current date and time are included in the event schedule, the server may be further inquired as to whether the HP of the event boss still remains. If the HP of the event boss still remains, it is determined that the event is being held, and if it is 0, it is determined that the event has ended. As a result of the determination, if the event is being held (YES in step S51), processor 121 executes in-event processing (terminal side) in step S52. On the other hand, if the event has ended (NO in step S51), processor 121 executes post-event processing (terminal side) in step S53.
[0086] [Processing on the terminal during the event] Fig. 19 is a flowchart showing details of the in-event process (terminal side) in step S52. In Fig. 19, first, in step S61, processor 121 generates an event screen as shown in Fig. 4 above. Specifically, processor 121 generates an image to be displayed in participation reward presentation area 202 based on participation reward information 424 acquired from server 101. Furthermore, processor 121 appropriately generates an image to be displayed in event information display area 201, and combines these to generate an event screen as shown in Fig. 4 above. Then, the event screen is output to display unit 124.
[0087] Next, in step S62, processor 121 acquires operation data 504 and determines whether or not an event participation operation (tap operation of participation button 203) has been performed. If the result of this determination is that an event participation operation has been performed (YES in step S62), then in step S63, processor 121 generates the above-mentioned participation instruction data for indicating that an event participation operation has been performed, and transmits it to server 101. The participation instruction data includes information that an event participation operation has been performed, various information (network address, etc.) for identifying the sender (i.e., the user's own terminal), information indicating the operation date and time, and the like. Note that, as described above, server 101 receives this data and determines whether or not a participation reward needs to be provided and provides the reward as appropriate.
[0088] Next, in step S64, processor 121 determines whether or not a participation reward has been given for the event participation operation performed this time. That is, it determines whether or not this is the first event participation operation within the current unit period. Any method of determination may be used for this determination, but in this embodiment, participation reward giving history information 413 at this time point is obtained from server 101, and based on this, it is determined whether or not a participation reward has already been given in the current unit period. Note that in other embodiments, a configuration may be adopted in which server 101 notifies information processing terminal 102 that a participation reward has been given for the event participation operation, and whether or not a participation reward has been given is determined by determining whether or not the notification has been received.
[0089] If it is determined in step S64 that a participation reward has been granted for the current event participation operation (YES in step S64), then in step S65, processor 121 generates pop-up display 207 as shown in Fig. 5 above, and displays it on display unit 124. On the other hand, if a participation reward has not been granted for the current event participation reward (that is, the participation reward has already been granted) (NO in step S64), the process of step S65 is skipped, and the process proceeds to the next step.
[0090] Next, in step S66, processor 121 receives data on the event boss at that time from server 101, and executes game processing based on the data. Specifically, processor 121 calculates a damage value given to the event boss. Note that in another embodiment, the game processing may be a game processing in which a predetermined game screen is displayed and the user operates a player character. In this case, too, a process of calculating a damage value given to the event boss is performed based on the user's operation. In addition, in this embodiment, an example is given in which the damage value is calculated on information processing terminal 102 side, but in another embodiment, the calculation of the damage value may be performed on server 101 side. In this case, the calculation result may be transmitted to information processing terminal 102, and the game processing on the information processing terminal side may be a process of displaying an attack effect based on the result.
[0091] Next, in step S67, processor 121 generates game processing result data including the damage dealt value. Then, processor 121 transmits the game processing result data to server 101.
[0092] Next, in step S68, processor 121 generates a message or the like indicating that the attack on the event boss has ended, and displays it on display unit 124. Thereafter, if a prescribed operation is performed to instruct the end of the display of the message, the process returns to step S61 and the processing is repeated.
[0093] Next, a case will be described where, as a result of the determination in step S62, the operation to participate in the event has not been performed (NO in step S62). In this case, in step S69, processor 121 determines whether or not an operation to close the event screen has been performed. If, as a result of the determination, the operation to close has not been performed (NO in step S69), the process returns to step S61 and is repeated. On the other hand, if the operation to close has been performed (YES in step S69), the in-event process (terminal side) ends.
[0094] [Processing of the information processing terminal 102 after the event ends] Next, the post-termination process (terminal side) in step S53 of FIG. 18 will be described. FIG. 20 is a flowchart showing the details of the post-termination process (terminal side). First, in step S81, processor 121 determines whether or not the compensation target reward has been granted for the currently ended event. This can be determined by obtaining compensation target reward grant information 414 from server 101 and referring to this. If the result of the determination is that the compensation target reward has been granted (YES in step S81), in step S82, processor 121 appropriately generates a message indicating that the compensation target reward has been received and displays it on display unit 124. On the other hand, if the compensation target reward has not been granted (NO in step S81), the process of step S82 is skipped.
[0095] Next, in step S83, processor 121 generates a message or the like to the effect that the event has ended, and displays it on display unit 124. Thereafter, a predetermined operation for closing the screen is performed, and the post-event processing ends.
[0096] In this embodiment, a participation reward is provided for an event in which participants cooperate to defeat a boss having a common HP among the participants. The participation reward is a reward given for participating in the game event during each unit period during the period in which the game event is held. In addition, the participation reward is set with an upper limit of the number of unit periods that can be given throughout the period in which the game event is held. Furthermore, the content of the reward is presented to the user in advance. If the number of times the unit periods arrive from the start to the end of the game event is less than the upper limit of the number of unit periods, at least a part of the ungiven reward, which is the participation reward that has not been given to the user, is given to the user. In other words, the reward that was expected by the user to be given due to the presentation is given to the user, but the opportunity to give the reward is lost because the event goal is achieved and the event ends in fewer days than the upper limit of the number of unit periods that can be given. This prevents the user's expectation of the participation reward from being damaged.
[0097] [Variations] In the above embodiment, as an example of an event, an example of decrementing the HP of an event boss common to the participants is shown. In other embodiments, a predetermined parameter of the event boss may be incremented by a predetermined operation corresponding to the attack operation. Then, when the value of the parameter exceeds a predetermined value set as the event termination condition, it may be determined that the event termination condition is satisfied. In addition, the method of progressing the event is not limited to the appearance of an attack on the event boss as described above. As long as a predetermined parameter common to the participants is changed by a process based on the operation of each participant, and when this parameter satisfies a predetermined condition, the event ends even if the scheduled end date has not yet arrived, any method of progressing the event may be used.
[0098] In addition, in the above example, the content of the participation reward is determined according to the number of days that the user participated in the event. In other embodiments, the participation reward may be determined according to the date, not based on the number of days of participation. For example, the participation reward A may be predefined as the participation reward for "August 1st" and the participation reward B may be predefined as the participation reward for "August 2nd". In this case, for example, if user A first participates in the event on August 1st and user B first participates in the event on August 2nd, both will participate in the event on the first day in total, but the reward content that they receive will be different. That is, user A will be given the participation reward A and user B will be given the participation reward B for participating in the event on the first day in total. In addition, in this case, the compensation target reward when early defeat occurs will be the participation reward defined corresponding to the date after the day after the early defeat occurs.
[0099] In the above embodiment, the compensation target reward is an example of all the participation rewards that were lost for all users due to early defeat. In other embodiments, only a part of the participation rewards may be compensated. In the example of the above embodiment, even if an early defeat occurs on the third day after the start of the event, only the participation reward E for the fifth time in total may be compensated.
[0100] In the above embodiment, an example was given in which the participation reward corresponding to the date of occurrence of the early defeat is not compensated. In another embodiment, the participation reward corresponding to the date of occurrence of the early defeat may also be included in the compensation to be compensated. In this case, the participation reward corresponding to the date of occurrence of the early defeat is only given to users who have not been given the participation reward, and users who have already been given the reward should not be given the reward twice.
[0101] Furthermore, the compensation target reward may include not only the participation reward that has been lost for all users, but also the unassigned reward that has not been assigned to each user. For example, assume that user A has participated three times in total and has been assigned participation rewards A to C, while user B has participated only once in total and has been assigned only participation reward A. In this case, according to the above embodiment, the participation rewards D and E for the fourth and fifth times are compensated, but this is not limited to this, and in other embodiments, the participation rewards B and C that have not been assigned to user B may also be included in the compensation target. Furthermore, in this case, instead of assigning all of the unassigned rewards, only a portion of them may be assigned.
[0102] In the above embodiment, the compensation target reward is given to users who do not participate in the event, but in other embodiments, non-participating users who have never participated in the event may be excluded from the compensation target. In other words, the compensation target reward may be given only to users who have participated in the event at least once.
[0103] The subject that executes the above-mentioned processing is not limited to the above-mentioned configuration. For example, in the above-mentioned information processing system, the server-side system may be composed of a plurality of information processing devices, and the processing to be executed on the server side may be shared and executed by the plurality of information processing devices. For example, data other than the above-mentioned terminal-side game program 501 and operation data 505 may also be stored in the server 101, and the information processing terminal 102 may access the server 101 and refer to the data as necessary. In this case, for example, the information processing terminal 102 may send operation data 505 indicating a user's operation to the server 101, execute various game processes in the server, receive the execution results, and generate and display a game screen that reflects the execution results. [Explanation of symbols]
[0104] 101 Server 102 Information processing terminal 111 Processor 112 Memory 113 Communications Department 121 processors 122 Memory 123 Operation section 124 Display section 125 Communications Department
Claims
1. An information processing system for providing a user with a game event that can be held over a plurality of unit periods, comprising: an update means for updating a progress status of the game event based on participation of the user or another user different from the user in the game event; a presentation means for presenting to the user information regarding a plurality of participation rewards, the participation rewards being given for participating in the game event during each of the unit periods during a period during which the game event is held, the reward contents being preset for at least two or more unit periods determined in advance for a predetermined number of times, regardless of the progress of the game event; a first granting means for granting to the user the participation reward, the participation reward being associated with the unit period to which the timing of the participation belongs, in response to the user's participation in the game event; a termination means for terminating the progress of the game event when the progress of the game event satisfies a termination condition; and a second granting means for granting to the user at least a portion of the participation reward, which is the participation reward that has not been granted to the user, if the number of occurrences of the unit period from the start of the game event to the progress of the game event satisfying the end condition is less than the specified number of times.
2. The information processing system according to claim 1 , wherein the second granting means grants the ungranted reward to the user for an amount of time that the number of occurrences of the unit period until the progress status satisfies the end condition is less than the predetermined number of times.
3. The information processing system according to claim 1 or 2, wherein the second granting means grants to the user only participation rewards from the ungranted rewards that would not be granted to the user even if the user had participated in each of the unit periods until the end of the game event.
4. The information processing system of any one of claims 1 to 3, wherein the second granting means grants at least a portion of the ungranted reward even to a user who is using an application in which the game event can be held and who has never participated in the game event during the period in which the game event is held.
5. The information processing system of any one of claims 1 to 4, wherein when the user participates in the game event, the first granting means grants the user a participation reward corresponding to the unit period determined based on the number of unit periods in which the user participates in the game event during the period in which the game event is held.
6. An information processing program executed by a computer of an information processing device for providing a user with a game event that can be held over a plurality of unit periods, comprising: The computer, an update means for updating a progress status of the game event based on participation of the user or another user different from the user in the game event; a presentation means for presenting to the user information regarding a plurality of participation rewards, the participation rewards being given for participating in the game event during each of the unit periods during a period during which the game event is held, the reward contents being preset for at least two or more unit periods determined in advance for a predetermined number of times, regardless of the progress of the game event; a first granting means for granting to the user the participation reward, the participation reward being associated with the unit period to which the timing of the participation belongs, in response to the user's participation in the game event; a termination means for terminating the progress of the game event when the progress of the game event satisfies a termination condition; An information processing program that functions as a second granting means for granting to the user at least a portion of the ungranted reward, which is the participation reward that has not been granted to the user, if the number of times the unit period occurs from the start of the game event to the progress of the game event satisfying the end condition is less than the specified number of times.
7. An information processing device for providing a user with a game event that can be held over a plurality of unit periods, an update means for updating a progress status of the game event based on participation of the user or another user different from the user in the game event; a presentation means for presenting to the user information regarding a plurality of participation rewards, the participation rewards being given for participating in the game event during each of the unit periods during a period during which the game event is held, the reward contents being preset for at least two or more unit periods determined in advance for a predetermined number of times, regardless of the progress of the game event; a first granting means for granting to the user the participation reward, the participation reward being associated with the unit period to which the timing of the participation belongs, in response to the user's participation in the game event; a termination means for terminating the progress of the game event when the progress of the game event satisfies a termination condition; an information processing device comprising: a second granting means for granting to the user at least a portion of an ungranted reward, which is the participation reward that has not been granted to the user, when the number of occurrences of the unit period from the start of the game event to the progress of the game event satisfying the end condition is less than the specified number of times.
8. An information processing method executed by a computer that controls an information processing system for providing a user with a game event that can be held over a plurality of unit periods, comprising: The computer includes: updating a progress status of the game event based on participation of the user or another user different from the user in the game event; presenting to the user information regarding a plurality of participation rewards, the participation rewards being given for participating in the game event during each of the unit periods during which the game event is held, the reward contents being preset for at least two or more unit periods determined in advance for a predetermined number of times, regardless of the progress of the game event; granting the user, in response to the user's participation in the game event, the participation reward associated with the unit period to which the timing of the participation belongs; If the progress of the game event satisfies a termination condition, the progress of the game event is terminated; An information processing method in which, if the number of occurrences of the unit period from the start of the game event to the progress of the game event satisfying the end condition is less than the specified number of times, at least a portion of the participation reward that has not been granted to the user is granted to the user.
9. An information processing system for providing a user with a game event that can be held over a plurality of unit periods, comprising: a presentation means for presenting to the user information regarding a plurality of participation rewards, the participation rewards being awarded for participating in the game event during each of the unit periods within a period during which the game event is held, the participation rewards being set with an upper limit number of unit periods being at least two or more unit periods during which the participation rewards may be awarded throughout the entire period during which the game event is held, and the content of the participation rewards being preset regardless of the progress of the game event; a first granting means for granting to the user the participation reward, the participation reward being associated with the unit period to which the timing of the participation belongs, in response to the user's participation in the game event; an update means for updating a progress status of the game event based on participation of the user or another user different from the user in the game event; a termination means for terminating the progress of the game event when the progress of the game event satisfies a termination condition; and a second granting means for granting to the user at least a portion of the participation reward, which is the participation reward that has not been granted to the user, if the number of occurrences of the unit period from the start of the game event to the progress of the game event satisfying the end condition is less than the upper limit number of unit periods.
Citation Information
Patent Citations
Systems and methods for compensating participants of virtual environments
US20090098939A1
