JP7140486B2 - game system, game program - Google Patents

Description

The present invention relates to a game system and a game program that can be played using play rights.

Conventionally, there has been a game device that consumes play rights such as stamina to play (for example, Patent Document 1).
However, conventional game devices do not have any special features regarding the use of the right to play.

JP 2016-185350 A

SUMMARY OF THE INVENTION An object of the present invention is to provide a game system and a game program that can develop and use play rights.

The present invention solves the problems by means of the following solutions. In order to facilitate understanding, reference numerals corresponding to the embodiments of the present invention are used for explanation, but the present invention is not limited to these. Also, the configurations described with reference numerals may be improved as appropriate, and at least a part of them may be replaced with other components.

・The first form is a game system that can be played by using the play right that increases according to the increase condition, and the right information storage that stores the increased play right as the owned play right owned by the player up to the possession upper limit value. (16, 26), and a rights management unit (18b, 28b) for managing the right to play, wherein the right management unit lends the lending right, which is the right to play, to the player in response to a request from the player. The game system is characterized by storing in the right information storage unit.
The second mode is characterized in that, in the game system of the first mode, the game has a player level, and the upper limit of the lending right increases according to the player's level. It is a game system that
A third mode is the game system according to the first or second mode, wherein the right management section (18b, 28b), when a lending right exists in the right information storage section (16, 26), The game system is characterized in that the play right that increases according to the increase condition is not increased as the owned play right, but is used to return the lending right.
- A fourth form is the game system of any one of the first to third forms, comprising a play control section (18a) for controlling the play of the game of this game system, and the play control section controls the lending right. This game system is characterized in that, when playing using the owned play right, a privilege more advantageous to the player is given than when playing using the owned play right.
- A fifth form is a game characterized in that, in the game system according to any one of the first to fourteenth forms, the right management unit (18b, 28b) grants the right to play according to the elapsed time. system.
- A sixth form is a game characterized in that, in the game system of the fifth form, the rights management unit (18b, 28b) controls to return more playing rights than the lending rights. system.
A seventh mode is the game system according to any one of the first to sixth modes, wherein the right management section (18b, 28b) stores the right information storage section in response to lending the lending right to the player. This game system is characterized by lowering the holding upper limit of (16, 26).
・The eighth form is a computer (10, 20) provided in a game system that can be played by using the play right that increases according to the increase condition, and the increased play right is held by the player as the possessed play right. and a right management means (18b, 28b) for managing the right to play. is lent to the player and stored in the right information storage means.

- In the first and eighth forms, even if the player lacks the right to play, the player can still play by lending the right to lend.
- In the second mode, more lending rights can be lent to the player as the player's level increases.
In the third mode, the play right, which increases according to the increase condition, is given priority over the granting of the owned play right to return the lending right, so the lending right can be recovered reliably.
- In the fourth mode, it is possible to encourage play using the lending right. As a result, since the player uses the lending right in addition to the normal right to play, it is possible to encourage the player to play for a long time.
- The fifth form can be applied to a system in which the right to play is recovered according to the elapsed time.
- The sixth and seventh forms can ensure fairness between a player who frequently uses the lending right and a player who does not frequently use the lending right.

BRIEF DESCRIPTION OF THE DRAWINGS It is a figure explaining the structure of the game system 1 of 1st Embodiment. 4 is a table for explaining information stored in a player information storage unit 25c of the server 20 of the first embodiment; 7 is a graph for explaining changes in normal rights and excess rights in the first embodiment; 7 is a graph for explaining changes in normal rights and excess rights in the first embodiment; It is a figure which shows the login screen 40 of 1st Embodiment, and the selection screen 41. FIG. It is a figure explaining the screen transition of the touch panel 11 of 1st Embodiment. It is a figure which shows the transition of the screen at the time of the play process of 1st Embodiment. It is a figure which shows the display screen at the time of the item management process of 1st Embodiment. 9 is a flowchart of item conversion reservation processing after receiving an item conversion reservation in the first embodiment; 7 is a graph for explaining an increase/decrease in normal rights after accepting an item conversion reservation in the first embodiment; FIG. 10 is a diagram showing an excess rights management screen 49 of the first embodiment; FIG. 7 is a graph for explaining changes in normal rights and excess rights in the first embodiment; It is a figure which shows the transition of the screen in the lending right process of 1st Embodiment. It is a figure explaining change of the normal right of 1st Embodiment, and a rental right. FIG. 10 is a diagram illustrating transition of screens displayed during recovery speed management processing according to the first embodiment; FIG. 11 is a graph for explaining fluctuations in normal rights after the recovery speed of normal rights is set according to the first embodiment; FIG. It is a figure explaining the structure of the game system 201 of 2nd Embodiment. FIG. 11 is a diagram for explaining information stored in a player information storage unit 25c and sharing right storage units 216d and 226d according to the second embodiment; FIG. 10 is a diagram for explaining character-stage information included in the game program of the second embodiment; FIG. 9 is a graph for explaining changes in normal rights and shared rights in the second embodiment; FIG. 11 is a diagram illustrating transition of screens when using shared rights according to the second embodiment; FIG. 11 is a graph for explaining changes in shared rights of a game system 201 of another embodiment of the second embodiment, and a diagram showing a shared right attribute selection screen 244 of a game terminal 210A of the second embodiment; It is a figure explaining the structure of the game system 301 of 3rd Embodiment. It is a graph which shows the change of the normal right of 3rd Embodiment, and a rental right. FIG. 14 is a diagram showing a display screen of the touch panel 11 during lending processing according to the third embodiment; FIG. 14 is a diagram showing a display screen of the touch panel 11 during lending processing according to the third embodiment; FIG. 11 is a flowchart of intra-group lending right return processing according to the third embodiment; FIG. FIG. 12 is a diagram showing a display screen of the touch panel 11 during item exchange processing within a group according to the third embodiment;

(embodiment)
BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described with reference to the drawings.
(First embodiment)
FIG. 1 is a diagram illustrating the configuration of a game system 1 according to the first embodiment.
FIG. 2 is a table for explaining information stored in the player information storage unit 25c of the server 20 of the first embodiment.
In the embodiment, when indicating a specific player P, the player name is appropriately used, and the player ID, which is the player identification information, is added in parentheses. That is, a specific player P is described as, for example, player (P011), Ichiro (P011), and the like.
A game system 1 allows a player to play a game on a game terminal 10 (game machine) owned by the player. The game terminal 10 is, for example, a mobile phone, a multi-function mobile phone (also called a smart phone), a personal computer, a tablet computer, a dedicated game terminal, or the like. In the embodiment, an example in which the game terminal 10 is a multifunctional mobile phone will be described. A game program to be executed on the game terminal 10 is downloaded from the server 20 to the game terminal 10 . Game programs may also be downloaded from content servers of content service operators that distribute digital content (applications, movies, music).

The game of the embodiment is, for example, a role-playing game (RPG) in which a player forms a party of four characters C, operates the characters C in order to fight the enemy E, and damages the enemy E ( See FIG. 7(C)).
The player owns a plurality of characters C, and selects three of the four characters C to be used in each play. A fourth character C can use a character C owned by another player.

[Configuration of game system 1]
As shown in FIG. 1, the game system 1 includes a game terminal 10 and a server 20. FIG. Although one game terminal 10 is illustrated in FIG. 1, the game system 1 actually includes the game terminals 10 owned by the players.
The game terminal 10 and the server 20 are connected by a communication network 2 using the Internet or the like, and can communicate information as necessary.

The game terminal 10 and the server 20 are computers.
In the embodiments, a computer refers to an information processing device including a storage device, a control device, and the like. The game terminal 10 and the server 20 are information processing apparatuses having storage units 15 and 25, control units 18 and 28, etc., and are included in the concept of a computer.
The storage units 15 and 25 are storage devices for storing information, programs, and the like necessary for the operation of the game terminal 10 and the server 20 . The storage units 15 and 25 include semiconductor memory elements and the like.
The control units 18 and 28 are devices for performing arithmetic processing required for the operations of the game terminal 10 and the server 20 and for controlling them in an integrated manner. The control units 18 and 28 are composed of, for example, a CPU (Central Processing Unit). The control units 18 and 28 realize various functions of the embodiment by appropriately reading and executing various programs stored in the storage units 15 and 25 .

(Game terminal 10)
The game terminal 10 includes a touch panel 11 , a storage section 15 and a control section 18 .
Note that the touch panel 11 is a device that serves both as a display unit that displays information to the player and as an operation unit that receives operations from the player. For the touch panel 11, for example, a capacitive touch panel can be used.
The touch panel 11 displays a play screen, each setting screen, etc., and can accept operations during play and operations during each setting.

The storage unit 15 includes a game program storage unit 15 a and a rights information storage unit 16 .
The game program storage unit 15a is a storage area that stores a game program for the game terminal 10. FIG. As described above, the game program can be downloaded from the server 20, content server, or the like.
The rights information storage unit 16 includes a normal rights storage unit 16a, an excess rights storage unit 16b, and a lending rights storage unit 16c.
The normal right storage unit 16a, the excessive right storage unit 16b, and the lending right storage unit 16c store information on the normal right, the excess right, and the lending right as play rights, respectively.
As will be described later, the server 20 also has a rights information storage unit 26 . The storage contents of the two right information storage units 16 and 26 are the same by synchronizing them (for reference, the reference numerals of the storage units 16, 16a, 16b and 16c are given in parentheses in FIG. 2). However, the game terminal 10 stores the above information in a temporary memory device after logging in to the game (that is, an operation for putting the game terminal 10 into a state in which operations related to the game can be performed), during activation of the game program, etc. etc. is stored. This is because the above information is always stored in the server 20 .
Details of each right information will be described later.

Although detailed description is omitted, after login, the storage unit 15 includes a storage area for acquiring and storing information about the game from the server 20 in addition to the right information storage unit 16 .
That is, the game executed on the game terminal 10 is executed based on the game program of the game terminal 10, but after logging into the game, the game terminal 10 communicates with the server 20, Necessary information about the game (character C, information about items, etc.) is acquired from and stored. Then, the game terminal 10 performs game-related processing while matching the information stored in the game terminal 10 and the information stored in the server 20 as necessary.

The control unit 18 includes a play control unit 18a, a rights management unit 18b, and an item conversion unit 18c.
The play control unit 18a performs processing related to the progress of the play on the game terminal 10, and the like.
The right management unit 18b performs processing related to management of each right information of the player.
The item conversion unit 18c performs processing related to conversion between normal rights and the like and items that can be used in the game.
Details of the processing of the control unit 18 will be described later.

(Server 20)
The server 20 is a computer that controls the game system 1 .
The server 20 is installed at a facility or the like of the operator of the game system 1 .
The server 20 has a storage unit 25 and a control unit 28 .
Although illustration is omitted, the server 20 displays an operation unit (input devices such as a keyboard and a mouse) for the administrator of the game system 1 to operate the server 20, and displays a management screen and the like during maintenance. A display unit (liquid crystal display device, etc.) and the like are provided.

The storage unit 25 includes a game program storage unit 25a, a management program 25b, and a player information storage unit 25c.
The game program storage unit 25 a stores game programs to be downloaded to the game terminal 10 .
The management program 25b is a program for various processing and control of the server 20. FIG. The management program 25b relates to, for example, management of rights information, processing related to items, and the like. The management program 25b is not directly involved in play control on the game terminal 10, but is included in a type of game program because it performs processing related to the game.

The player information storage unit 25c stores information that associates a player ID with play-related information that is information about the game of the player. The player information storage unit 25c is provided corresponding to each player.
The player information storage section 25c includes a player ID storage section 25d, a player name storage section 25e, an LV storage section 25f, a character storage section 25g, an item storage section 25h, a group information storage section 25i, and a right information storage section .
The player ID is stored in the player ID storage unit 25d, and the play-related information is stored in the player name storage unit 25e, LV storage unit 25f, character storage unit 25g, item storage unit 25h, group information storage unit 25i, and right information storage unit 26. stored in
A player ID is identification information that identifies a player. The player ID is not limited to unique information provided for the game system 1, and may be, for example, an e-mail address, terminal identification information individually assigned to the game terminal 10, or the like.
Also, although illustration is omitted, the player information storage unit 25c stores a player ID and a login password for starting processing related to the game in association with each other.

As shown in FIG. 2, the player name storage unit 25e stores player names of players. The player name is a nickname or the like used when the player plays, and does not need to be a real name. The player name can be registered from the game terminal 10 or the like.
The LV storage unit 25f stores the play level of the player (the play level is also called "LV"). LV is information indicating the level in the game. The play control unit 18a determines the LV based on, for example, the score of the game, the level of the stage cleared, the experience value, and the like. For this reason, a player with a higher LV tends to have a higher game skill, a longer playing experience, or the like.
The character storage unit 25g stores information about the character C owned by the player.
The representative character shown in FIG. 2 is, for example, character C that can be selected when selecting a friend (see FIG. 7B).
The item storage unit 25h stores information on items owned by the player. The types of items include those equipped by the character C (sword, shield, etc.) as well as types of rights described later.

The group information storage unit 25i stores information about the group to which the player belongs. Although detailed description is omitted in this embodiment, the game system 1 allows a plurality of players to form a group and cooperate in the game. In the embodiment, other players in the group to which each player belongs are also called friends.

Like the right information storage unit 16 of the game terminal 10, the right information storage unit 26 stores right information related to the player's play.
That is, the rights information storage unit 26 includes a normal rights storage unit 26a, an excess rights storage unit 26b, and a lending rights storage unit 26c. The normal right storage unit 26a, the excessive right storage unit 26b, and the lending right storage unit 26c store information on the normal right, the excess right, and the lending right as play rights, respectively.
Details of each right information will be described later.

The control unit 28 performs processing such as managing information stored in the storage unit 25 .
The control unit 28 includes a rights management unit 28b and an item conversion unit 28c.
The rights management unit 28b and the item conversion unit 28c perform the same processing as the rights management unit 18b and the item conversion unit 18c of the game terminal 10, respectively.
The right management units 18b and 28b execute synchronized processing. Similarly, the item converters 18c and 28c perform synchronized processing. As a result, the information stored in the game terminal 10 and the information stored in the server 20 are matched.
Details of the processing of the control unit 28 will be described later.

[Overview of rights information]
An overview of rights information that can be used in the game system 1 will be described.
3 and 4 are graphs for explaining changes in normal rights and excess rights in the first embodiment.
FIG. 3 shows how normal rights and excess rights change when they are not used in play or the like.
The degree of each right possessed by the player is represented by the number of points (parameter).

(Normal right)
Normal rights have attributes that can be used for play in each stage and item conversion.
A normal right is granted to the player by increasing with time. In the embodiment, an increase in normal rights is also referred to as "restoration".
In addition to the increase in normal rights due to the lapse of time, there are, for example, the following conditions.
- On the condition that the player's LV is raised (that is, the LV is raised), the normal right increases. In this case, the normal rights are granted up to the upper limit according to the LV increase, regardless of the amount held before the LV increase.
・The number of normal rights increases by using the seeds of rights, which are items. As will be described later, the player can obtain the seed of right by item conversion. Although detailed explanation is omitted, the player can also purchase the seed of the right online from the system operator via the content service operator.

The normal right storage units 16a and 26a store rights to be restored up to an upper limit value (holding upper limit value). The upper limit value increases in accordance with the player's LV (see the upper limit values of the normal right storage units 16a and 26a shown in FIG. 2).
In the embodiment, the upper limit is the same numerical value as the LV. For example, if the player is LV100, the upper limit is 100 points.

As shown in FIG. 3, in the embodiment, normal right recovery speed (play right increase speed, which is the degree of right increase per unit time) is 1 point in 6 minutes (1 point/6m) in normal time, That is, it is set to 10 points in one hour (10 points/h). Also, as will be described later, the player can set the recovery speed of normal rights to a recovery speed different from the normal recovery speed.

(Excess rights)
As will be described later, excess rights have attributes that can be used for play on the stage corresponding to the time period to which they are granted.
As shown in FIG. 3, after the normal entitlement reaches the upper limit, the excess entitlement increases at the same recovery speed as the normal entitlement while the normal entitlement remains at the upper limit. In other words, the right management units 18b and 28b grant normal rights up to the upper limit as rights that can be recovered over time. After the owned rights reach the upper limit value, the rights management units 18b and 28b store the rights to be recovered by exceeding the upper limit value with the lapse of time as the excess rights instead of the normal rights. , 26b.
As a result, the player can hold rights granted in excess of the upper limit of normal rights as excess rights.

As shown in FIG. 4, when the normal right falls from the upper limit value to less than the upper limit value due to the player's playing, the right management units 18b and 28b do not increase the excess right while the player is below the upper limit value. Stop. Then, after the normal entitlement reaches the upper limit again, the increase of the excess entitlement is resumed.

Excess rights decrease over time after 24 hours from grant. Decay speed is the same as recovery speed, decreasing by 10 points per hour. Therefore, if the excess rights are not used, the points given 24 hours ago will gradually disappear, while new points will be given (see FIG. 3).
Therefore, in the embodiment, no upper limit value is set for the excess right, but the present invention is not limited to this, and an upper limit value or the like of the same numerical value corresponding to the LV may be set as in the case of the normal right.

(Lending rights)
The lending right is lent to the player from the game system 1 in response to the player's request when the right is normally insufficient. The lending right storage units 16c and 26c store the lending right lent to the player.
The details of the graph (see FIG. 14) showing the increase/decrease in rental rights will be described later.
Lending rights, like normal rights, have attributes that can be used for play in each stage. Therefore, the player can play by using the lending right when the normal right is insufficient.
As with normal rights, the upper limit of the same numerical value as the LV is set for the lending right, and it increases according to the player's LV. For example, if the player is LV 100, the upper limit of the excess right is 100 points. (Refer to the upper limit values of the lending right storage units 16c and 26c shown in FIG. 2).
Therefore, the higher the level of the player, the more lending rights the player can request from the game system 1 .

[Operation of game system 1]
FIG. 5 is a diagram showing a login screen 40 and a selection screen 41 according to the first embodiment.
FIG. 6 is a diagram for explaining screen transition of the touch panel 11 of the first embodiment.
As shown in FIG. 5A, the control unit 18 of the game terminal 10 first displays the login screen 40 on the touch panel 11 when starting processing related to the game. In order to log in to the game, the player may operate the log-in execution button 40a after entering the player ID and password while the log-in screen 40 is displayed. Note that the player ID and password may be accepted by a software keyboard method using the touch panel 11, for example.
The control unit 18 of the game terminal 10 transmits login information including player ID and password information to the server 20 . Upon receiving this, the control section 28 of the server 20 refers to the player information storage section 25c to determine whether or not the player ID and password included in the login information are appropriate.

When the control unit 28 of the server 20 determines that these are appropriate, it reads out the information necessary for the processing related to the game from the storage unit 25 and transmits it to the game terminal 10 . When receiving this, the control unit 18 of the game terminal 10 displays the selection screen 41 (see FIG. 5B) on the touch panel 11 .
On the other hand, when the control unit 28 of the server 20 determines that these are inappropriate, it transmits information to that effect to the game terminal 10 . When receiving this, the control unit 18 of the game terminal 10 displays on the touch panel 11 a display indicating that the login information is inappropriate and a display (not shown) prompting re-input.

The selection screen 41 in FIG. 5B will be described.
The selection screen 41 displays selection buttons corresponding to processes to be shifted to next.
That is, the selection screen 41 includes buttons corresponding to play start processing, item management processing, excess rights management processing, play right recovery setting processing, and group management processing. A button 41e, a recovery speed setting button 41c, and a group management button 41d are displayed.
Descriptions of the group management screen 360, the normal rights change screen 361, the intra-group lending setting screen 362, and the intra-group item conversion screen 370 shown in FIG. 6 are omitted in this embodiment.
As shown in FIG. 6, when each button is selected, the control unit 18 of the game terminal 10 displays a processing screen corresponding to each button and starts processing corresponding to each button.
The screen of the touch panel 11 and its screen transition shown in FIG. 6 correspond to the processing of the game system 1 and the transition of the processing. For example, when the display of the touch panel 11 transitions from the selection screen 41 to the play start processing screen 42, the processing of the game system 1 transitions from selection processing (processing for accepting selection of subsequent processing) to play start processing. corresponds to

The rights management unit 18b of the game terminal 10 transmits information about rights after the change to the server 20 when rights change after login. Upon receiving this, the server 20 updates the information on each right in the player information storage unit 25c. As a result, the information about each right of the game terminal 10 and the information about each right of the server 20 match, that is, match.

After logging out, the rights management unit 28b of the server 20 performs processes related to changes in rights information over time (that is, recovery of normal rights, provision of excess rights, extinguishment, return of lent rights, etc.). may not be performed. In other words, the rights management unit 28b maintains the rights information unchanged after logout, and at the next login, the rights management unit 28b reflects changes in rights corresponding to the time from the time of logout to the time of login to the rights information. may Further, the process of reflecting the change in rights information may be performed by the rights management unit 18b of the game terminal 10 instead of the server 20, and the reflected rights information may be transmitted to the server 20. FIG.
As a result, the server 20 does not need to process changes in rights information from the time the player logs out until the player logs in, so the load can be reduced.

It should be noted that, in the embodiment, the concept of rights changing over time includes reflecting the amount of recovery corresponding to the elapsed time from logout to log-in in the right information at the time of login. described as a thing.
Further, the control unit 18 of the game terminal 10 and the control unit 28 of the server 20 control changes in various information in the game terminal 10 (for example, changes in the use of rights in the game terminal 10) in addition to changes in rights according to the elapsed time. and item information due to use of the item), the information in the storage units 15 and 25 of both are synchronized to match.

(play processing)
FIG. 7 is a diagram showing transition of screens during play processing according to the first embodiment.
It should be noted that in the drawings for explaining the display of the screen of the touch panel 11 in FIG. 7 and subsequent figures, the illustration of the outer shape of the game terminal 10 is omitted as appropriate.
As shown in FIG. 7A, the control unit 18 of the game terminal 10 displays a play start processing screen 42 on the touch panel 11 in the game start processing.
The play start processing screen 42 displays a right information display portion 42a and a stage selection portion 42b.
The right information display section 42a indicates each right owned by the player with a belt-shaped graph and a point value. The shaded portion of the graph corresponds to the number of rights held. In the example of FIG. 7A, the normal right is 50 points, the excess right is 50 points, and the lending right is 0 points.

The stage selection section 42b is a button that accepts the selection of the stage that the player wishes to play. The play start processing screen 42 of FIG. 7A displays selection buttons 42c and 42d for normal stages St10 and St20, a selection button 42e for limited-time stage L1, and a selection button 42f for event stage E20.
The player may select a button corresponding to a desired stage from the normal stages St10 and St20, the limited-time stage L1, and the event stage E20.

(Overview of normal stage, limited-time stage, and event stage)
I will explain the outline of the normal stage, the limited time stage, and the event stage.
As "normal rights 10" and "normal rights 20" are displayed inside the selection buttons 42c and 42d of the normal stages St10 and St20, in order to play in the normal stages St10 and St20, the normal rights are 10, respectively. , requires 20 points. In this way, normal stages can be played using normal rights. As will be described later, the normal stage can be played by replacing some or all of the normal rights with lending rights.

In normal stages, the higher the player's LV, the higher the level of difficulty that is opened. Further, the higher the normal stage, the more points are required. In other words, a player with a higher LV can play in a higher normal stage, but requires more right points for that play. Therefore, the higher the LV of the player, the higher the upper limit of the normal points that can be held. It should be noted that such a setting in which the higher the stage, the more necessary rights are not limited to the normal stage. The number of necessary rights may be increased.
FIG. 7(A) shows only the selection buttons 42c and 42d for the two normal stages St10 and St20, but by scrolling the screen, the selection buttons for the higher normal stages are displayed. You can select the normal stage of

The limited-time stage L1 is open only during a limited time period of the day. The limited time stage may be open every day or only on weekdays. By defeating the enemy E in the play in the limited-time stage L1, for example, advantageous items (for example, equipment for the character C, synthetic items, etc.) are given to the player.
The playable time zone of the limited-time stage L1 is different for each player. 00 to 14:00” or the like.

As "Normal right 1" is displayed inside the selection button 42e of the limited time stage L1, one normal right point is required to play in the limited time stage L1. Also, the limited-time stage L1 can be played using normal rights in the same manner as the normal stage, and can be played by replacing part or all of the normal rights with rental rights.
In this way, the limited-time stage L1 is a special special stage for the player, because it is possible to play with a small right such as 1 point, in addition to being a chance to acquire advantageous items as described above. can be positioned as
Although FIG. 7A shows an example in which only one selection button 42e is shown and only one limited-time stage L1 is prepared, the present invention is not limited to this, and a plurality of limited-time stages are provided. may

The event stage E20 is a special stage that is opened during an event held by the system operator. By winning each special stage or a plurality of special stages, the player is granted special benefits (for example, equipment of character C, right items to be described later, etc.). The event period is, for example, several days to several weeks, and the play control unit 18a accepts play in the event stage E20 during this period regardless of the time zone. Therefore, the event stage E20 can also be positioned as a special special stage for the player.
Since the event stage E20 is opened only during the event period, it may be included in the limited-time stage.

For the player, such an event stage is also a chance to acquire benefits, like the limited-time stage. However, the event stage cannot be played with a small number of rights points like the limited-time stage. As shown inside the selection button 42f of the event stage E20, in order to play in the event stage, the same points as in the normal stage (for example, 10 points or more) are required.
Since the game program during the event period can execute the event stage, it differs from the game program during normal times. The system operator should store the game program for the event period in the server 20, the content server, etc., so that the game terminal 10 can download the game program during the event period and before and after the event period. .

When each selection button is selected, the play control section 18a starts playing the stage corresponding to the button.
Here, an example in which the selection button 42c of the normal stage St10 is selected will be described.
As shown in FIG. 7B, the play control unit 18a of the game terminal 10 displays the character selection screen 43 on the touch panel 11 when the selection button 42c is selected.
The character selection screen 43 is a screen for selecting and determining four characters C that form a party to be played on the stage. Note that the play control unit 18a acquires information necessary for displaying the character selection screen 43 (information on each character C, etc.) from the server 20 as appropriate.
The character selection screen 43 displays a character selection portion 43a and a friend selection portion 43b.
The character selection section 43a displays selection buttons for selecting the character C owned by the player (Ichiro (P011) in the example of FIG. 7). The player can select three characters C by selecting three selection buttons.
The friend selection section 43b has a selection button for adding a friend's representative character to the composition of the party. The player can select one character C by operating one selection button.
The player can select four characters C by the above operation.
The right management units 18b and 28b of the game terminal 10 and the server 20 determine the use of the normal right according to the selection of four characters on the character selection screen 43. FIG. Also, the play control unit 18a of the game terminal 10 starts playing.

In the example of FIG. 7C, the play control unit 18a of the game terminal 10 displays the play screen 44 in response to receiving the selection of the four characters C, and starts playing the normal stage St10.
The play control unit 18a of the game terminal 10 processes the progress of the play in which the four characters C fight the enemy E in order according to the player's operation. The play control unit 18a of the game terminal 10 determines that the player wins when the HP of the enemy E (a parameter indicating physical strength) becomes 0, while the HP of all the four characters C becomes 0. If so, it is determined that the player has lost. The play control unit 18a of the game terminal 10 transmits the play result to the server 20, and the control unit 28 of the server 20 receives the play result and updates information such as the play history in the player information storage unit 25c. In addition, the control units 18 and 28 provide the player with points, experience points, items, and the like according to the play results.
After that, the control unit 18 of the game terminal 10 ends the play processing of the normal stage St10, and displays the play start processing screen 42 again.

(Item management process)
Item management processing will be described.
FIG. 8 is a diagram showing a display screen during item management processing according to the first embodiment.
As shown in FIG. 8A , the control unit 18 of the game terminal 10 displays the item management screen 45 on the touch panel 11 .
The item management screen 45 displays an item conversion button 45a, an item conversion reservation button 45b, and an item use button 45c. The control unit 18 of the game terminal 10 shifts to item conversion processing, item conversion reservation processing, and item use processing in accordance with the operation of each button. The player may operate a button corresponding to desired processing.

(Item conversion process)
As shown in FIG. 8B, the item conversion unit 18c displays an item conversion screen 46 and starts item conversion processing in response to the operation of the item conversion button 45a.
The item conversion screen 46 displays an item conversion execution button 46a.
In addition, the item conversion screen 46 displays information 46b and the like regarding the possessed ordinary rights.
The item conversion execution button 46a is a button for receiving an execution instruction for item conversion. If the player desires item conversion, the player can operate the item conversion execution button 46a.

The item conversion unit 18c converts 30 points, which are part of the normal rights owned by the player, into a right seed, which is an item, in response to the operation of the item conversion execution button 46a.
As described above, the item conversion unit 18c of the game terminal 10 ends the item conversion process and displays the item management screen 45 again. The normal rights in the normal right storage units 16a and 26a are updated to 10 points by subtracting 30 points from 40 points before item conversion.

The seeds of rights after item conversion can be used for playing in each stage, that is, related to play rights.
Therefore, the player can hold the play right as an item by converting the normal right to a right seed.

Also, according to the item conversion, the normal rights owned are subtracted, so the point difference between the normal rights owned at the moment and the upper limit (= upper limit - normal rights owned at the moment) is ,growing. That is, the point difference, which was 60 before item conversion, increases to 90 after item conversion.
As a result, the game system 1 can prevent the recovery time from being wasted even if the normal right is not used after logout and the idle state continues for a long time.

In other words, if the item is not converted, the difference in points is 60 points, and the time until the normal right reaches the upper limit is 6 hours from the current time, since the recovery speed is 10 (points/h). is. Ordinary rights do not recover beyond the cap. Therefore, if the idle state exceeds 6 hours from the present time, the player cannot obtain the normal right that could have been obtained if the upper limit value had not been reached during the exceeding time.

On the other hand, when the item is converted, the point difference is increased to 90 points compared to when the item is not converted, so the upper limit reaching time is extended by 3 hours to 9 hours. Therefore, even if the idle state continues for 9 hours, the normal right is recovered during this period, so the player can acquire the normal right. As a result, if the player plays again within 9 hours from the current time, the normal right can be acquired even after 9 hours before reaching the upper limit value. Also, even if the player does not play again within 9 hours from the current time, the player can acquire the normal right for the extended upper limit reaching time of 3 hours. Therefore, for example, when the player has a plan to not play for a long time or wants to go to bed early due to fatigue, even if the normal rights have reached the upper limit or near the upper limit, the player can change the item, A normal right to reinstate can be effectively obtained. Therefore, the game system 1 can increase the degree of freedom in selecting the time period for the player to play.

In a form different from the present embodiment, the normal points cannot be converted into items, so the player cannot obtain the normal rights that should have been obtained as described above. This may cause player dissatisfaction. Also, in this form, it is necessary to play in each stage in order to reduce the normal right and increase the point difference. However, for example, playing before going to bed may be painful for the player. Such dissatisfaction, pain, etc., of the player is, for example, one of the major factors that hinder continuous play (for example, play on consecutive days), and is also a factor in leaving the game (stopping the game).
On the other hand, the game system 1 of the present embodiment, as described above, allows the player to have more freedom in selecting the time period for playing. can be strongly urged.

In addition, although the above description shows an example in which only normal rights are converted into items, the present invention is not limited to this. For example, if the normal rights necessary for item conversion are insufficient, the shortage of rights may be compensated by the lending rights described later. In this case, in the item conversion process, the item conversion unit 18c displays on the touch panel 11 a screen similar to that shown in FIGS. 13A to 13C, which will be described later. should be confirmed with the player.

(Item conversion reservation process)
As shown in FIG. 8C, the item conversion unit 18c of the game terminal 10 displays the item conversion reservation screen 47 and starts the item conversion reservation process in response to the operation of the item conversion reservation button 45b.
In the item conversion reservation process, in response to the acceptance of the player's reservation operation, that is, in accordance with the acceptance of the item conversion from the possessed normal rights in advance, at the scheduled recovery date and time (scheduled time) later than the current time, This is the process of item conversion.

The item conversion reservation screen 47 displays a scheduled recovery date and time display section 47a and a reservation button 47b.
Also, the item conversion reservation screen 47 displays the number of points of the normal right possessed by the player, the current date and time, and the like.
The scheduled recovery date and time display section 47a displays the scheduled recovery date and time. The scheduled recovery date and time is the date and time when the normal right will reach the upper limit when a period of time has passed since the current time without using the normal right. In addition, the scheduled recovery date and time display section 47a also displays the time required until the upper limit value is reached.

In the example of FIG. 8C, the current date and time is 01:00 on January 10, and the possessed ordinary rights are 40 points. The item conversion unit 18c calculates the required time "6 hours" by dividing the 60 points up to the upper limit by the recovery speed 10 (points/h). is calculated.
The reservation button 47b is a button for accepting a reservation for item conversion. If the player wishes to make a reservation for item conversion, the player can operate the reservation button 47b.
The player can make a reservation for item conversion when, for example, the player does not play for a long time after playing.

Processing after accepting the operation of the reservation button 47b will be described.
FIG. 9 is a flowchart of item conversion reservation processing after receiving an item conversion reservation in the first embodiment.
FIG. 10 is a graph for explaining an increase/decrease in normal rights after accepting an item conversion reservation according to the first embodiment.
In step S2, the item conversion unit 18c determines whether or not the normal right has been used after receiving the item conversion reservation (S2) and before the scheduled recovery date and time elapses. If the item conversion unit 18c determines that the normal right has reached the upper limit (S2: YES), it proceeds to S5. move on.

Here, with reference to FIG. 10, the mode of restoration of the normal rights when the normal rights are not used and the mode of restoration of the normal rights when the normal rights are used before the scheduled restoration date and time have passed. and explain.
The example of FIG. 10A is a case where the normal right is not used until the scheduled recovery date and time has passed. In this case, the normal right reaches the upper limit at the scheduled recovery date and time of "07:00 on January 10" as planned. In such an example, for example, it is assumed that the normal right is restored to the upper limit while the player is sleeping, and the item is converted.

On the other hand, in the example of FIG. 10B, between "06:00 on January 10" and "07:30 on January 10", which is before "07:00 on January 10", which is the scheduled recovery date and time, This is when the player plays. Such an example is, for example, a scene in which the player wakes up earlier than planned and plays the game on the assumption that the normal right will be restored to the upper limit value and the item will be converted while sleeping.
If the normal right is used before the scheduled recovery date and time has passed, the play right will decrease before the scheduled recovery date and time. does not reach the upper limit even if

In S3, the item conversion unit 18c of the game terminal 10 determines whether or not the scheduled recovery date and time has passed. When the item conversion unit 18c determines that the scheduled recovery date and time has passed (S3: YES), the process proceeds to S4. repeat.

In the process up to this point, in the example of FIG. 10A, the normal right reaches the upper limit as scheduled at the scheduled recovery date and time, so the item conversion unit 18c proceeds to S5 (S2: YES→S5). On the other hand, in the example of FIG. 10(B), the normal right does not reach the upper limit value as scheduled at the scheduled recovery date and time, so the process proceeds to S4 (S2: NO→S3: NO→S4).

In S4, the item conversion unit 18c determines whether or not the normal rights required for item conversion are sufficient. If the item conversion unit 18c determines that the normal rights required for item conversion are sufficient (S4: YES), it proceeds to S5. The processing of S4 is repeated.
Here, when S4: NO is determined, it is when the normal right is frequently used in the play before the scheduled recovery date and time, or when there are many required rights for one stage. In such a case, the item conversion unit 18c repeats the process of S4 and waits until the normal right recovers to the number of points required for item conversion.

In S5, the item conversion unit 18c executes item conversion from normal rights to right seeds. As a result, the normal rights possessed by the player are subtracted, and the seeds of rights, which are items, are granted. The item conversion unit 18c transmits to the server 20 the normal rights and item information after the item conversion. The item conversion section 28c of the server 20 updates the information in the storage section 25 in response to receiving these information.

Through the above processing, the game system 1 has the following actions and effects.
(1) When the normal right reaches the upper limit at the scheduled recovery date and time and the item is converted (S2: YES→S5), the normal right is subtracted from the upper limit. For this reason, the same effects as those of the item conversion without reservation described above (suppression of waste of right recovery time, etc.) can be achieved.
In addition, the effect can be further improved by playing after the item is converted and before the normal right reaches the upper limit. That is, the player can extend the time until the normal right reaches the upper limit value again by playing after the item is converted until the normal right is fully recovered. In the example of FIG. 10(A), by playing from 07:00 after the item conversion to 10:00 when the normal rights are fully recovered, the time until the normal rights reach the upper limit again , extended beyond 10:00.
Thus, by controlling the time until the normal right reaches the upper limit, the player can control the time during which the normal right reaches the upper limit as short as possible.

(2) Even if the normal rights do not reach the upper limit at the scheduled recovery date and time (S2: NO) by playing the game between the time when the item conversion reservation is made and the scheduled recovery date and time, if the scheduled recovery date and time passes ( S3: YES), item conversion is executed. Therefore, even if the game is played before the scheduled recovery date and time after the item conversion reservation, the item will be converted at the scheduled recovery date and time. Therefore, the time until the scheduled recovery date and time is not wasted, and it does not interfere with playing, so even if the item conversion reservation is made, the frequency of playing does not decrease.
That is, unlike the embodiment, if the reservation is canceled in response to playing at these times, the time spent waiting for item conversion is wasted for the player. For this reason, in this form, the item conversion reservation becomes a factor of lowering the play frequency because it interferes with the play until the scheduled recovery date and time.

It should be noted that the item conversion unit 18c of the game terminal 10 executes this by satisfying the condition for item conversion even during play (S4: YES). However, the item conversion unit 18c is not limited to this, and the item conversion unit 18c stops counting the elapsed time until the scheduled recovery date and time when a play is performed between the item conversion reservation and the scheduled recovery date and time. good too. After the play ends, the item conversion unit 18c restarts counting the passage of time, and extends the scheduled recovery date and time by the counting suspension period.
For example, when the scheduled recovery date and time is "07:00 on January 10" and the play for 1 hour and 30 minutes is performed from "06:00 to 07:30", the item conversion unit 18c Period, stop counting the elapsed time until the scheduled recovery date and time. In addition, when the play ends at "07:30", the item conversion unit 18c extends the expected recovery date and time to "09:00 on January 10" by extending the count stop period of 1 hour and 30 minutes. After updating, restart counting. Subsequent processing is the same as the above processing (see FIG. 10B).
In this form, during play, item conversion will not occur unexpectedly. wait time is not wasted.

(Item use process)
The item use process is a process of reducing (converting) a right seed to a normal right by using the right seed, which is an item.
As shown in FIG. 8D, the item conversion unit 18c displays an item use screen 48 in response to the operation of the item use button 45c.
The item use screen 48 displays a conversion execution button 48a.
Also, the item use screen 48 displays information such as items owned by the player and conversion details.
The conversion execution button 48a is a button that accepts an operation for executing conversion from a right seed to a normal right. If the player wishes to execute conversion from the right seed to the normal right, the player can operate the conversion execution button 48a.

The item conversion unit 18c of the game terminal 10 converts one of the types of rights possessed by the player into normal rights in response to the operation of the conversion execution button 48a.
This conversion process increases the normal rights in the normal right storage units 16a and 26a. Players can use normal rights to play stages.
If the normal rights exceed the upper limit due to the use of the right seed, the item conversion units 18c and 28c store the excess rights in the excess rights storage units 16b and 26b as excess rights. good.

(Excess rights management processing)
FIG. 11 is a diagram showing the excess rights management screen 49 of the first embodiment.
FIG. 12 is a graph for explaining changes in normal rights and excess rights in the first embodiment.
As shown in FIG. 11, the rights management unit 18b of the game terminal 10 displays an excess rights management screen 49 on the touch panel 11 in the excess rights management process.
The excess rights management screen 49 displays a stage selection section 49a.
Further, the excessive rights management screen 49 displays information 49b such as information (acquisition date, number of points) regarding the owned excessive rights.

The stage selection section 49a displays a selection button 49c for the limited-time stage L1 and a selection button 49d for the event stage E20. These buttons correspond to stages that can be played by the player.
The rights management unit 18b selects, from among a plurality of stages, stages that satisfy at least the following two conditions as ones that the player can play.

(1) The stage was playable during the period when the excess right was granted to the player. The condition (1) will be described with reference to FIG. 12 as an example.
The player has 240 excess points as of "13:00 on January 11".
The rights management unit 18b gives the excess rights 240 points to the player from "13:00 on January 10th to 13:00 on January 11th". The stages that were playable during this period are the limited-time stage L1 and the event stage E20. In addition, at the present moment, the excess right granted during the playable period of the limited-time stage L1 and the event stage E20 remains without being extinguished.

The rights management unit 18b selects a limited-time stage L1 that was playable during the period "11:00 to 21:00 on January 10" when the excess right was granted to the player, as a stage playable with the excess right. Select event stage E20. Thus, excess rights have the attribute of being able to play the stage corresponding to the time of the increase (that is, the granted period).
It should be noted that the normal stage can be played by using the normal right even at "13:00 on January 11" at this time. For this reason, in the embodiment, the rights management unit 18b excludes the normal stage from the stages that can be played with the excess rights, but is not limited to this and may be included.

This allows excess rights to have different attributes than normal rights. In addition, since the excess rights retroactively make the stages that were playable at the time of increase (at the time of grant) playable, they can have attributes that reflect the situation at the time of the increase.

(2) It is possible to play with the excess rights held at the time the stage was opened As shown in the selection button 49c in FIG. In addition, at the time when the limited-time stage L1 was open (at any time between 13:00 and 14:00 on January 10), the excess holding right was 1 point or more.
Similarly, the required right for event stage E20 is 20 points. At the time when the event stage E20 was opened (at any time between January 1st and January 10th at 24:00), the excess holding rights are 20 points or more.
Therefore, the rights management unit 18b determines that these two stages satisfy the above conditions.

In this way, the rights management unit 18b determines that these two stages satisfy the conditions (1) and (2) above, and displays the selection button 49c for the limited-time stage L1 and the selection button 49d for the event stage E20. .
The rights management unit 18b may display, on the excess rights management screen 49, a list of buttons corresponding to the stages that satisfy the condition (1) above. In this case, only the button selection operation corresponding to the stage that satisfies the above (2) should be accepted.

When the excess rights management screen 49 is displayed, the player may select a selection button corresponding to a desired stage from among the limited-time stage L1 and the event stage E20.
The subsequent processing is the same as the play processing using normal rights (see FIG. 7(B), etc.).

Through the above processing, the game system 1 has the following actions and effects.
(1) It is possible to go back and play past stages by using excess rights. Therefore, the player can obtain the benefit of being able to play these stages, for example, by using the excess right even if he or she is too busy to play. In addition, even if the game is not played for a long time, the excess rights are gradually extinguished, so that there is an upper limit to the amount of possession, so fairness can be ensured between other players who frequently play the game.
(2) As mentioned above, excess rights are extinguished for a limited period of time. Therefore, even if there is a stage that the player cannot play, the game system 1 can prompt the player to play the stage before the excess right expires. As a result, it is possible to prevent the player from leaving the game.

(3) In general, players desire to play multiple stages, but the reality is that the number of stages that can be played in a short period of time is usually limited by the number of right points. For example, in the scene of FIG. 7(A) mentioned above, if the three stages of normal stages St10, St20, and event stage E20 are played, the necessary normal rights total 50 points, so it is possible to play more than that. Can not. However, the event stage E20 and the limited-time stage L1 can be played on the following day using excess rights. Therefore, the player can take a strategy such as playing more normal stages by using the normal right first, and carrying over the event stage E20 and the like to the next day to play. In this case, there is an advantage for the player, and there is an advantage for the system operator in that it encourages continued play and prevents the player from leaving the game.

(Rental rights processing)
13A and 13B are diagrams showing screen transitions in the lending right processing of the first embodiment.
The play start processing screen 50 of FIG. 13A and the play start processing screen 42 of FIG. 7A are similar screens. However, the two differ in the display content of the right information display section 42a (that is, the rights owned by the player), the display content of the stage selection section 42b (that is, the stage that the player is about to select), and the like.
At the time when the play start processing screen 50 of FIG. 13A is displayed (13:00 on January 10), the player has 10 normal rights. In addition, 50 normal rights are required to play the normal stage St50. Therefore, the normal right is 40 points short for the player to play the normal stage St50.
In such a case, the lending right processing is the processing of lending the lending right to the player as the right to play.

The player recognizes that the normal right is insufficient to play the normal stage St50 by checking the right information display section 50a in FIG. 13A and the display inside the selection button 50a of the normal stage St50. be able to.
As shown in FIG. 13B, when the player selects (for example, taps) the selection button 50b of the normal stage St50, the rights management unit 18b displays a lending rights display screen 51. FIG.
In this case, the right management unit 18b calculates the shortage of 40 points and displays it in the display area of the rental right of the right information display unit 50a.

In addition to displaying the 40-point lending right numerically, the right information display unit 50a displays a graph showing the 40-point lending right continuously to the graph showing the 10-point normal right. That is, the rights information display unit 50a continuously displays graphs for 50 points. It is possible to display to the player in an easy-to-understand manner the ordinary rights possessed, the lending rights to be lent, and the right obtained by adding them together.

After confirming the lending right display screen 51 of FIG. 13B, the player may further select (double-tap, etc.) the selection button 50b in order to continue the processing related to the play of the normal stage St50.
As shown in FIG. 13C, the right management unit 18b displays a lending right confirmation screen 52 accordingly.
The lending right confirmation screen 52 includes lending right information 52a for playing the normal stage St50 with the lending right (explanation that 40 points are insufficient to play the normal stage St50, and the lending right of the player after lending the lending right). total value, etc.).
In addition, the lending right confirmation screen 52 displays a play start button 52b.
The play start button 52b is a button that accepts a play start operation using the lending right.
After confirming the contents of the lending right information 52a, the player may operate the play start button 52b when starting to play the normal stage St50.

The subsequent processing is the same as the play processing using the normal right (see FIG. 7(B), etc.).
However, the play control unit 18a gives the player a privilege that is more advantageous than when playing the stage using the normal right when playing the stage using the lending right. Although the content of the advantageous privilege is not limited, for example, the defense power and offensive power of the player's character C can be improved.
Thereby, the game system 1 can strongly urge the player to play using the loan right.
Also, in order to play using the lending right, the player needs to use up the normal right by playing for a long time and playing frequently. Thereby, the game system 1 can encourage the player to continue playing.
Contrary to the above, the play control unit 18a may perform the play process under conditions disadvantageous to the player (lowering of offensive power, etc.) when using the lending right. In this case, it is possible to improve fairness between a player who frequently uses the lending right and a player who does not use it frequently.

(Collection of right to lend)
FIG. 14 is a diagram for explaining changes in normal rights and rental rights in the first embodiment.
After lending the right to lend to the player, the game system 1 performs processing for collecting it.
FIG. 14 shows changes in the lending right when lending the lending right to Ichiro (P011) in order to play the normal stage St50 in the above example. Therefore, at the start of the play of the normal stage St50, the normal right is reduced from 10 points to 0 points, and the lending right is given 40 points. In other words, the lending right exists by storing the lending right in the lending right storage units 16c and 26c.

In this case, the game system 1 collects the lending rights through the following steps.
(1) As indicated by an arrow A1 in FIG. 14A, if there is a lending right, the rights management unit 18b converts the normal right, which increases according to the recovery speed, to the recovery of the lending right (that is, the player's (returned from In other words, the rights management unit 18b uses the rights granted to the player to collect the lending rights stored in the lending right storage units 16c and 26c without increasing the rights in the normal right storage units 16a and 26a.
In the example of FIG. 14A, the lending right, which was 40 points, decreases over time, while the normal right is maintained at 0 points.
In this case, the rights management unit 18b may slow down the collection speed of the rental right (the amount of decrease in the rental right per unit time), for example, by several percent, compared to the normal right recovery speed. This causes the player to convert more rights than they have been loaned.
As a result, the game system 1 can ensure fairness between players who frequently use the lending rights and players who do not frequently use them.

(2) As a result of continuing the processing of (1) above, the right management unit 18b increases the normal right according to the lapse of time in response to the lending right becoming 0 points.
(3) As indicated by the arrow A2 in FIG. 14B, when the right increases according to the use of the right type, the increasing right is given to the lending right in the same manner as in (1) and (2) above. given priority to the return of

(4) As shown by the arrow A3 in FIG. 14(C), when the right is granted according to the player's LV up, after compensating for the lending right (that is, after collecting all), the normal Grant rights up to the maximum value. Therefore, if the player raises the level while borrowing the lending right to the maximum limit, the player can return the lending right without recovering the right or using the seed of the right. Thereby, the game system 1 can strongly urge the player to play a lot just before the LV is raised.

By the above processing, the game system 1 has the following actions and effects.
(1) The player can still play by requesting the lending right even if the normal right becomes 0.
In addition, even if the player has enough normal rights, if he/she further requests the lending of the rental rights, he/she can play for a long time according to the sum of the normal rights and the rental rights. As a result, the game system 1 can encourage the player to play a lot before a long period of non-playing (for example, before going to bed).

(2) Even if the player is slightly short of normal rights to play on the stage, by requesting the lending right, the player can play without waiting for recovery of the slight normal right. . As a result, for example, even if normal rights are slightly insufficient and only a short playing time can be secured (for example, the remaining few minutes of break time, etc.), that time can be effectively used for playing.

(3) As described above, the number of rights required to play on a stage increases as the stage progresses. On the other hand, the upper limit of normal rights is determined according to LV.
For this reason, for example, if the upper limit of the normal right corresponding to LV50 is 50 points, in a form different from the embodiment, even if the player of LV50 possesses 50 points of the normal right, 51 points of the normal right are required. You will not be able to play any stages. In the embodiment, even in such a case, the LV50 player can play because the total right becomes 51 points by borrowing 1 point of the lending right.

(4) Players can play in higher stages by increasing their LV, but the number of normal rights required for playing increases as the stage gets higher. In the embodiment, the upper limit of the right to lend is increased according to the LV up. For this reason, the player can borrow more lending rights even when the normal rights are insufficient due to playing in a higher stage as the LV increases.

Note that the right management unit 18b may lower the upper limit of the normal right according to the lending of the lending right. As a result, the game system 1 can ensure fairness between players who frequently use the lending rights and players who do not frequently use them. In this case, the upper limit of normal rights may be returned to the normal upper limit setting in accordance with the LV increase. For example, when the upper limit of a player of LV100 is lowered from 100 points to 99 points, the upper limit may be returned to 101 points in accordance with the LV increase to LV101. As a result, it is possible to further strongly encourage the player to play a lot just before the LV is raised.

In addition, in the item conversion process, the rights management unit 18b may lend the lending right and then convert the right held after lending into a right seed. In this case, after the item conversion screen 46 (see FIG. 8(B)), the right management unit 18b displays the lending right display screen 51 (see FIG. 13(B)), the lending right confirmation screen 52 (see FIG. 13(C) ))), it is possible to display insufficient rights, lent rights, and the like.

(Recovery speed management processing)
15A and 15B are diagrams for explaining the transition of screens displayed during recovery speed management processing according to the first embodiment.
As shown in FIG. 15A, the right management unit 18b of the game terminal 10 first displays a recovery speed setting screen 53 in the recovery speed management process.
The recovery speed setting screen 53 displays a boost processing button 53a and a schedule processing button 53b.
Each button is a button for transitioning to boost processing and schedule processing in recovery speed management. When the player selects a desired button, the rights management unit 18b accepts the operation and starts each process.

(boost processing)
The boost process is a process of increasing the normal right recovery speed to 20 (points/h), which is double the normal speed, in a set time. In the embodiment, such a process of doubling the recovery speed of normal rights is called a boost, and the period during which the boost is performed is also called a boost period. The cumulative time of the boost period in a period of one day (0:00 to 24:00) is set to an upper limit of 60 minutes or the like.
As shown in FIG. 15B, the rights management unit 18b displays a boost setting screen 54 during boost processing.
The boost setting screen 54 displays a start time display portion 54a, an end time display portion 54b, an accumulated boost time display portion 54c, and a boost start button 54d.

A start time display section 54a and an end time display section 54b display the start time point and the end time point of the boost period, respectively. The start time and end time can be set in units of one minute from the current time by operating the up/down button 54e.
The cumulative boost time display unit 54c displays the cumulative double speed time for one day in the form of "cumulative time/upper limit time". The right management unit 18b updates the display contents of the boost cumulative time display unit 54c according to the operation of the start time and end time. In the example of FIG. 15(B), "total time 30/60 minutes" is displayed. , indicates that the remaining 30 minutes can be additionally set.

The boost start button 54d is a button for confirming the setting of the start time and end time and starting boost recovery. The player can start boost recovery by checking the display contents of the start time display section 54a, the end time display section 54b, the cumulative boost time display section 54c, etc., and operating the boost start button 54d.

When receiving the operation of the boost start button 54d, the rights management units 18b and 28b of the game terminal 10 and the server 20 increase the normal right by boost recovery during the boost period. Note that the rights management units 18b and 28b increase the normal rights at normal recovery speed before and after the boost period (that is, before and after the boost period ends).

In this way, the game system 1 increases the normal rights at double the normal recovery speed for a short period of time (for example, within several tens of minutes). As a result, when a player concentrates on playing a plurality of stages in a short period of time, the speed at which normal rights decrease is slower than normal. This allows the player to play more stages during short periods of the day (for example, commuting time, school commute time, lunch break, etc.).

(schedule processing)
In the schedule processing, a recovery schedule is created by setting a plurality of recovery speed periods (1.5x speed, normal, 1/2 (half), stop) in one day (0:00 to 24:00), which is a set period. It is a process of creating and normally recovering rights based on this.
As shown in FIG. 15(C1), the right management unit 18b displays a schedule screen 55 during schedule processing.
The schedule screen 55 includes a schedule table 55a, a 1.5x speed selection section 55b, a normal selection section 55c, a 1/2 selection section 55d, a stop selection section 55e, a cumulative rights display section 55f, a daily button 55g, a weekday button 55h, and a confirmation button. 55i is displayed.

The schedule table 55a shows distribution of recovery speeds in one day in the form of a band graph with the horizontal axis as the time axis. The inside of the band is displayed with patterns and colors corresponding to 1.5 times speed, normal, 1/2 (half), and stop.
The 1.5x speed selection section 55b, the normal selection section 55c, the 1/2 selection section 55d, and the stop selection section 55e are buttons used to create the schedule table 55a. The 1.5x speed selection portion 55b, the normal selection portion 55c, the 1/2 selection portion 55d, and the stop selection portion 55e are displayed in corresponding patterns, colors, and the like.

The cumulative rights display section 55f displays the cumulative rights to be granted to the player based on the set schedule. The cumulative rights display section 55f displays the cumulative rights in the form of "cumulative rights/maximum rights". In the example of FIG. 15(C1), "cumulative right 230/maximum 240" is displayed, so there is still room for setting to increase by 10 points.
The maximum right is the maximum value of rights that can be granted within one day, which is the set period, at the normal recovery speed of 10 (points/h), and is 240 points in the embodiment.

The daily button 55g and the weekday button 55h are buttons for setting a period of one week during which the set schedule is reflected.
The confirm button 55i is a button for confirming the right restoration process based on the schedule table 55a.

The process and procedure for creating the schedule table 55a will be described.
(1) As shown in FIG. 15(C2), when the player displays the desired recovery speed selection section, the rights management section 18b displays the schedule table creation screen 56. FIG.
(2) The player drags the selected speed selection section onto the schedule table 55a. Based on this, the right management section 18b displays the dragged portion of the schedule table 55a in the color of the selected speed selection section. This sets the selected recovery speed in the schedule. The example of FIG. 15 (C2) is a scene in which the recovery speed of 1.5 times is set around 06:00.

(3) As shown in FIG. 15 (C3), the player can fine-tune the arrangement of the recovery speeds on the schedule table 55a by sliding, expanding (pitch-out), and reducing (pinch-in). . The right management unit 18b updates the display of the recovery speed arrangement range according to the player's operation.
(4) The right management unit 18b displays the schedule screen 55 shown in FIG. 15(C1) when the player performs the above operation for other recovery speeds.
Thereby, game terminal 10 can accept schedule setting in which a plurality of periods with different recovery speeds are arranged within the set period.

In addition, as described above, the right to increase in one day (the upper limit of the amount of increase within the set period) is up to 240 points. The right management unit 18b permits the arrangement of recovery speeds within a maximum range of 240 points at the time of schedule creation.
This allows a player to adjust their daily entitlement to up to 240 points to increase at different rates by scheduling periods of different recovery speeds to suit their schedule for the day.

For example, at nighttime, it is time to go to bed and the game is not played for a long period of time. Therefore, after the normal right reaches the upper limit, the period during which the upper limit is maintained tends to be longer. On the other hand, during commuting hours, lunch breaks, etc., there is a tendency for rights to be in short supply, as these are time periods in which games can be played continuously.
The example of FIG. 15 (C1) is a schedule created by the player taking these into account, and the recovery speed is set to 1/2 from around 0:00 at night to early morning. In addition, the recovery speed is set to 1.5 times for the commuting hours of about 1 hour after 06:00 and 18:00, and the lunch break of about 1 hour after 12:00. there is
As a result, the player can acquire rights during commuting hours, etc., which could not normally be acquired during bedtime due to the upper limit of rights.

(5) The player may operate the confirmation button 55i to confirm the schedule. Note that the player can operate the daily button 55g or the weekday button 55h before operating the confirmation button 55i if the period during which the set schedule is reflected is every day of the week or weekdays. .
In response to this, the right management units 18b and 28b execute the right recovery process from the next day based on the fixed schedule recovery speed.

FIG. 16 is a graph for explaining fluctuations in normal rights after normal right recovery speed is set according to the first embodiment.
FIG. 16A is a simulation in which normal rights are increased based on the schedule setting when the schedule is set. In other words, FIG. 16A shows the number of points (expected increase value) when it is assumed that the normal rights are increased as scheduled.
As shown in FIG. 16(B), the actual normal right decreases as the game is played. Therefore, even if the normal right exceeds the upper limit in the above schedule setting, the player can eliminate or reduce the period in which the upper limit is exceeded by playing for one day, which is the set period.
For this reason, the right management unit 18b ensures that even if there is a point in time when the upper limit of normal rights exceeds 100 points, the total value of the increment is within 240 points in the simulation at the time of schedule setting shown in FIG. 16(A). If there is, schedule setting is accepted.

Here, as shown in FIG. 16B, three stages are played during the period from 06:00 to 07:00 when the recovery speed is 1.5 times.
The normal right remaining amount A4 after the start of the third play is several points. Therefore, if this period were normal recovery speed, the player would either not be able to play the third stage, or would be playing a lower level stage with fewer entitlements.
In embodiments, the recovery speed scheduling allows the player to play this third stage.
The same applies to other periods (12:00 to 13:00 period, etc.) in which the recovery speed is 1.5 times.

In this way, the game system 1 can receive the setting of the recovery speed schedule in advance according to the player's daily schedule or the like.

As described above, the game system 1 of the present embodiment can use the play right more extensively than before by converting the normal right into an item, etc., and can prevent the player from leaving the game. Furthermore, the game system 1 can further improve the above functions and effects by providing excess rights and lending rights in addition to normal rights as play rights.
On the other hand, conventional game devices simply use the right to play for the purpose of playing, and the usage method is simple.

(Second embodiment)
Next, a second embodiment of the invention will be described.
In the following description and drawings, portions that perform the same functions as those of the first embodiment described above are denoted by the same reference numerals or the same reference numerals at the end (lower two digits) as appropriate, and overlapping explanations are omitted as appropriate. omitted.
FIG. 17 is a diagram illustrating the configuration of the game system 201 of the second embodiment.
FIG. 18 is a diagram for explaining information stored in the player information storage unit 25c and the sharing right storage units 216d and 226d of the second embodiment.
FIG. 19 is a diagram for explaining character-stage information included in the game program of the second embodiment.

[Overview of game system 201]
17 and 18, in this embodiment, Ichiro (P011), Jiro (P012), and Saburo (P013) form the same group G001. explain. Each player (P011, P012, P013) owns a game terminal 210 respectively.
Although the game system 201 has a plurality of group configurations, only the group configuration of the group G001 is illustrated in FIG. 17 for simplicity.

As shown in FIGS. 17 and 19, the game program stored in the game program storage unit 15a of the game terminal 210 includes character-stage information.
Characters C1 to C15 are characters C that can be possessed by each player.
Each of the characters C1 to C15 is given an attribute of fire, water, or wood.

Normal stages that can be played in the game are normal stages St1, St2, St3, . . . , St99. The normal rights required to play each stage are 1 point, 2, 3 points, . . . , 99 points, respectively. In each stage, enemies E1, E2, E3, .
Like the character C, the enemies E1, E2, E3, .
Details of the attribute will be described later.

The game terminal 210 also includes a shared rights storage unit 216d (shared play rights storage unit) and a rights management unit 218b.
The sharing rights storage unit 216d stores information about sharing rights. The shared right is a play right shared by the players (P011, P012, P013) of the same group G001 and available for play.

As shown in FIGS. 17 and 19, the game program in the game program storage unit 25a of the server 220 stores character-stage information, similarly to the game terminal 210. FIG.
The server 220 also includes a shared rights storage unit 226 d and a rights management unit 228 b similar to those of the game terminal 210 .
The game terminal 210 and the server 220 store the same information in the sharing right storage units 216d and 226d by communicating as necessary in the same manner as in the first embodiment.

[Summary of sharing rights]
An outline of rights information used in the game system 201 will be described.
FIG. 20 is a graph for explaining changes in normal rights and shared rights in the second embodiment.
FIGS. 20(A1), 20(A2), and 20(A3) are graphs showing changes in normal rights of Ichiro (P011), Jiro (P012), and Saburo (P013), respectively. 20(A1), 20(A2), and 20(A3) are stored in the normal right storage units 16a and 26a corresponding to Ichiro (P011), Jiro (P012), and Saburo (P013), respectively. .
Rights management units 218b and 228b manage the normal rights of each player, as in the first embodiment. For example, normal right recovery speed is 10 (points/h) as in the first embodiment.

After the normal right reaches the cap value, the shared right increases at the same recovery speed as the normal right recovery speed while the normal right remains at the cap value. In other words, after the owned rights reach the upper limit, the rights management units 218b and 228b treat the rights that exceed the upper limit as time elapses and recover as shared rights instead of normal rights. , 226d. That is, the rights management units 218b and 228b manage excess rights in the first embodiment as shared rights in the present embodiment.

If the players are in the same group, the rights management units 218b and 228b store them in the same shared rights storage units 216d and 226d.
In the example of FIG. 20(A), Jiro's (P012) normal rights reached the upper limit (120 points) at 11:00 on February 10, so the rights to be restored after this point are shared rights. It is stored in the storage units 216d and 226d (see FIG. 20(B)).
Similarly, in the example of FIG. 20 (A3), since the normal right of Saburo (P013) reached the upper limit (130 points) at 10:00 on February 10, it will be exceeded and recovered thereafter. The rights are stored in the shared rights storage units 216d and 226d (see FIG. 20(B)).
In the example of FIG. 20A1, the ordinary right of Jiro (P012) does not have a period during which it reaches the upper limit, so there is no right to be stored as a shared right.

When storing the shared rights in the shared rights storage sections 216d and 226d, the rights management sections 218b and 228b attach the attribute of the representative character of the character C owned by each player to the shared rights. Thus, the shared right will have attributes corresponding to the players who participated in its increase (memorization).
As shown in FIG. 18, therefore, shared right attributes are classified and stored in the shared right storage units 216d and 226d.
For example, the representative character of Jiro (P012) is character C2, whose attribute is water (see FIG. 18). Thus, the shared rights stored by Jiro (P012) have the attributes of water.

Note that the form in which the attribute corresponding to each player is assigned to the shared right is not limited to the form in which the attribute of the representative character is reflected, and may be another form. For example, regardless of the representative character, the game terminal 210 may accept from each player in advance the selection of the attribute of the shared right to be increased by the player.

[Processing related to use of shared rights]
The use of the shared rights stored in the shared right storage units 216d and 226d will be described.
21A and 21B are diagrams for explaining screen transitions when sharing rights are used according to the second embodiment.
An example in which Ichiro (P011) of the group G001 uses shared rights when the change in rights is in the state shown in the graph of FIG. 20 will be described below. It should be noted that the shared right can be used by all players within group G001, including the players involved in storing the shared right.
As shown in FIG. 21(A), the rights management units 218b and 228b first display a play start processing screen 242 on the touch panel 11 in the processing related to the use of shared rights. In other words, the rights management unit 218b starts the process related to the use of shared rights in response to the play start processing button 41a being operated and the play start processing screen 242 being displayed on the selection screen 41 shown in FIG.

(select stage, view shared rights attributes)
The play start processing screen 242 displays a right information display section 242a and a stage selection section 242b.
The right information display portion 242a displays a normal right display portion 242g and a shared right display portion 242h.
The normal right display part 242g and the shared right display part 242h show the holding amount of each right (normal right, shared right) with a belt-shaped graph and a point value, as in the first embodiment.
Since the scene in FIG. 20A is at 13:00 on February 10, the rights management unit 218b determines that Ichiro (P011) has 10 normal rights (see FIG. 20A1), group Information corresponding to 50 points of shared rights owned by G001 (see FIG. 20B) is displayed on the normal right display section 242g and the shared right display section 242h, respectively.

Selection buttons 242c, 242d, 242e, and 242f display the number of normal right points required to play in each stage, as in the first embodiment. Note that the stage selection unit 242b can display other stages by scrolling the screen.
In the example of FIG. 21A, the stage selection unit 242b displays selection buttons 242c and 242d for two normal stages St50 and St51 for the normal stages.
Inside the selection button 242c, the attribute "fire" of the enemy E50 appearing in the normal stage St50 is displayed. Similarly, inside the selection button 242d, the attribute "water" of the enemy E51 appearing in the normal stage St51 is displayed.

By referring to the play start processing screen 242, Ichiro (P011) finds that the normal rights he possesses are 10 points, so that he does not have enough normal rights to play in the normal stages St50 and St51. can confirm that there is Also, Ichiro (P011) can confirm that the group G001 has 50 points of shared rights.
If Ichiro (P011) wishes to play the missing normal rights by using the shared rights, he can select the selection buttons 242c and 242d corresponding to the normal stages St50 and St51. .

As shown in FIG. 21B, the rights management unit 218b displays a shared rights display screen 243 accordingly. Note that FIG. 21B shows the screen after selecting the selection button 242d corresponding to the normal stage St51.
The shared rights display screen 243 displays a shared rights display portion 243a, an attribute display portion 243b, a necessary rights display portion 243c, and a play start button 243d.
The shared rights display section 243a indicates the amount of shared rights owned by a point value, similar to the shared rights display section 242h of FIG. 21(A). Note that the shared right display unit 243a displays the point value of the shared right in an illustration imitating a storage tank, thereby making it appear as if the players (P011, P012, P013) of the group G001 have stored the shared right together. is doing.

The attribute display section 243b explains the details of the shared right attribute.
The attribute display section 243b displays each attribute in association with the point value. Since the attribute display section 243b in FIG. 21B corresponds to FIG. Display information such as 30 points (rights stored by Saburo (P013)).

The required right display section 243c displays an explanation about the right required to play in the normal stage St51. In this example, an explanation is displayed that Ichiro (P011) lacks 41 points of the normal right to play on the normal stage St51, and that he can play by using 41 points of the shared right. there is
The play start button 243d is a button that accepts a play start operation using shared rights. After confirming the display contents, Ichiro (P011) operates the play start button 243d to start playing the normal stage St51.

(Shared rights, attributes of Enemy E)
Shared rights, Enemy E's attributes will be explained.
In the game of this embodiment, the attack power of the character C against the enemy E and the defense power of the character C against the attack from the enemy E are determined according to the combination of the attribute of the shared right used in the play and the attribute of the enemy E. is set. The play control section 18a controls the play based on this setting.
An example is described below.

When the character C utilizes the right to share the attribute of fire and fights against the enemy E who has the attribute of wood, the offensive power and the defensive power of the character C are 1.5 times higher.
When the character C uses the right to share the attribute of water to fight against the enemy E who has the attribute of fire, the character C uses the right to share the attribute of wood to fight against the enemy E who has the attribute of water. The same is true for the case.
In addition to this, when character C utilizes the right to share the attribute of fire and fights against enemy E who has the attribute of water, character C's offensive power and defensive power are increased by 0.5 times, etc. may be

The play control unit 18a adjusts the offensive power and defensive power of the character C according to the ratio of the attribute when the shared right is used for at least part of the right.
In the example of FIG. 21(B), the ratio of shared rights used for the play of normal stage St51 is 41/51.
In addition, the right of each attribute among the shared rights is to be used according to the holding ratio. Therefore, among the shared rights used for play, the water attribute ratio is 20/50, and the tree attribute ratio is 30/50.
Therefore, of the play rights required for play, the water attribute ratio is about 32% (=41/51×20/50), and the wood attribute ratio is 48% (=41/51×30/50). is.
Note that the rights management unit 218b may display information on these ratios and the like on the touch panel 11 .

Therefore, in this play right state, the ratio of wood attribute is almost half, and fire attribute is not included. For this reason, this play right state is an advantageous condition for the stage in which the water-attribute enemy E appears. On the other hand, although this play right state has the attribute of water, the attribute of water is less than the attribute of wood. Therefore, the status of the right to play is disadvantageous information for the stage where the fire-attribute enemy E appears.

As shown by the selection button 242d in FIG. 21A, the enemy E51 appearing in the normal stage St51 has the attribute of water, so under this condition, it can be fought advantageously in the normal stage St51.
Therefore, after confirming these, Ichiro (P011) can operate the play start button 243d to start playing the normal stage St51.

In addition, although the above has explained the detailed ratio of the attributes, Ichiro (P011) confirms the number of points for each attribute in the attribute display section 243b, so that the current shared rights as a whole have a high tree attribute. It can be understood at a glance that it has a tendency, that it does not have the attribute of fire, and so on. Also, when playing under the conditions shown in FIG. 21(B), the ratio of shared rights is high (41/51), so it can be understood at a glance that the attributes of shared rights are reflected in the play at a high rate. .

Also, if the selected stage is disadvantageous in this state of the right to play, Ichiro (P011) confirms the display contents of the attribute display section 243b, displays the play start processing screen 242, and repeats the stage. can be selected.

(Stage play processing)
When the play start button 243d is operated on the shared right display screen 243 of FIG. 21(B), the play control unit 18a performs the play processing of the normal stage St51.
The play control unit 18a processes the play processing using rights including shared rights in the same manner as the play processing using only normal rights (see FIG. 7B, etc.), but differs only in the following processing. .

As described above, the attributes of shared rights are reflected in the offensive power against the enemy E and the defensive power against the enemy E. This makes it possible to reflect the attributes of shared rights for each player. In addition, when playing under conditions of advantageous attributes, advantageous benefits such as increased offensive power and defensive power can be given to the player.

When playing using the shared play right, regardless of attributes, the player may be given a benefit such as an increase in attack power or the like compared to when playing using only the normal right.
In this case, the game system 201 can strongly encourage the player to play using shared rights. Here, in order to play using the shared rights, the players need to use up their normal rights. Thereby, the game system 201 can encourage the player to continue playing.

In this way, each player can play with shared rights associated with storage by other players in the same group.
Here, a plurality of players in the same group may have different game playing periods and time zones depending on their schedules in the real world, life rhythms, circumstances, and the like. For example, in work in the real world, the busy season is different from the beginning of the month to the end of the month, and the life rhythm is different from morning people to night people. As a result, a period during which one player in the same group can concentrate on playing may be a period during which other players cannot play at all. In other words, a period during which one player tends to run out of rights may be a period during which other players tend to increase the amount of shared rights stored (that is, the amount owned). In such a case, one player can play by making up for the lack of normal rights with shared rights that the other player is involved in remembering.

[Share Rights Management]
In addition to the above description, the rights management units 218b and 228b perform the following processing and management regarding shared rights.
(1) Lower the upper limit of the shared play right according to the time during which the shared right of the shared right storage units 216d and 226d maintains the upper limit.
For example, if the upper limit of shared rights is 350 points, the upper limit of owned shared rights is reduced by 1 point each time 350 points are maintained continuously for one hour. For example, if 350 points are maintained for 10 hours, the upper limit of the group's shared rights is lowered to 340 points.
Lowering the upper limit of shared rights is disadvantageous for the players belonging to the group. Therefore, the game system 201 can prompt the player to play until the shared right is used. Thereby, the game system 201 can encourage the player to continue playing.

(2) An upper limit is set for the usage amount of the shared play right in the shared right storage units 216d and 226d. The upper limit of the amount of usage can be set as appropriate, for example, 10 times the upper limit of holding of shared rights. As a result, the game content can be such that the storage tank will be destroyed when the shared right for 10 storage tanks is used.
The rights management units 218b and 228b receive the setting of a new upper limit value after using the upper limit of the usage amount of the shared rights stored in the shared rights storage units 216d and 226d. The rights management units 218b and 228b may set the new upper limit on the condition that all or some of the players in the group are charged. In this case, the content of the game can be such that the group purchases a new storage tank.

As described above, the game system 201 of this embodiment can provide a game in which each player can play using the shared rights in which other players in the same group have been involved in memory.
As a result, each player can play using the shared rights even if the normal rights owned by the players are insufficient to play each stage.

It should be noted that the game system 201 may set an upper limit on the usage amount of shared rights per player. In this case, the rights management unit 218b displays, on the shared rights display screen 243 or the like, information about the usage amount of the shared rights of each player up to the present time, information about the upper limit value, and the like, to each player. , the usage up to the upper limit value should be permitted. In this case, shared rights can be distributed equally to multiple players within the same group.
Also, when using shared rights, it may be possible to play with a smaller amount of rights than the amount of normal rights used.

(Modification of the game system 201 of the second embodiment)
Furthermore, the game system 201 of the second embodiment may be modified so that the player can select the type of shared right and set the ratio of the types when using the shared right, as in the following other modes. .
FIG. 22 is a graph for explaining changes in shared rights of the game system 201 of another embodiment of the second embodiment, and a diagram showing a shared rights attribute selection screen 244 of the game terminal 210A of the second embodiment.
22(A1), 22(A2), and 22(A3) show the changes in shared rights shown in FIG. 20(B) by classifying them into those in which each player is involved. 22(A1), 22(A2), and 22(A3) are graphs corresponding to each attribute, showing changes in sharing rights stored in the sharing rights storage units 216d and 226d of FIG. 18(B). It is represented.

The shared right attribute selection screen 244 in FIG. 22B is used for Ichiro (P011) to select the type of shared right and set the ratio of the type when Ichiro (P011) uses the shared right to play. belongs to.
The right management unit 218b displays the shared right attribute selection screen 244 on the touch panel 11, for example, after the play start button 243d on the shared right display screen 243 of FIG. 21B is operated.
The shared rights attribute selection screen 244 displays an attribute selection section 244a, a total usage amount display section 244e, and a play start button 244f.

The attribute selection section 244a is a display section for receiving the setting of the usage amount of the shared right (the number of usage points) for each attribute.
The attribute selection section 244a displays storage tanks 244b with attributes (fire, water, and wood) in association with information 244c on the amount of shared rights used and held for each attribute.

The information 244c of the usage amount and the holding amount of the shared right of each attribute is displayed in the form of "use amount/holding amount".
The "holding amount" is the holding amount of the sharing rights of each attribute stored in the sharing rights storage units 216d and 226d.
Also, the usage amount of the shared right of each attribute is set by Ichiro (P011) operating the up-down key 244d.
For example, as shown in FIG. 22A1, the shared right of the attribute of fire has a holding amount of 0 points at 13:00 on February 10th. In this case, the rights management unit 218b does not accept the use of the fire-attribute sharing right, and displays the "use amount/holding amount" of the fire-attribute sharing right as "0/0".

Similarly, the shared right to the attribute of water has a holding amount of 20 points, and the shared right to the attribute of wood has a holding amount of 30 points.
Regarding the attribute of water, the right management unit 218b accepts setting operations within 20 points using the up/down keys 244d. The example of FIG. 22B is an example in which the usage amount of the shared right for the attribute of water is set to 11 points, and the rights management unit 218b displays "11/20" as the "use amount/holding amount".
Regarding tree attributes, the rights management unit 218b accepts setting operations within 30 points using the up/down keys 244d. The example of FIG. 22B is an example in which the amount of use of the shared right with the tree attribute is set to 30 points, and the right management unit 218b displays "30/30" as the "use amount/holding amount".

Here, in the normal stage St51, an enemy E51 with the attribute of water appears (see FIG. 21A), so it is advantageous for Ichiro (P011) to play with the ratio of the attribute of wood as high as possible. be. That is, Ichiro (P011) fully utilizes the shared rights of tree attributes as shown in FIG. I have set it.

The cumulative usage amount display section 244e displays the cumulative usage amount corresponding to the setting of the shared right. The cumulative usage amount display unit 244e displays the cumulative usage amount (cumulative number of points) and the required amount of shared rights (cumulative number of points) for playing the normal stage St51 in the form of "cumulative usage amount/required amount". indicate.
In the example of FIG. 22(B), the shared right required to make up for the lack of play in the normal stage St51 is 41 points (see FIG. 21(B)). The cumulative usage amount has reached 41 points. Therefore, the total usage amount display unit 244e displays "total usage amount/required amount" as "41/41".
Ichiro (P011) can start playing the normal stage St51 by operating the play start button 244f after setting the shared right attribute.

As described above, the game system 201 according to the second embodiment classifies shared rights according to attributes and stores them in the shared rights storage units 216d and 226d. Accepts the setting of the amount of usage of As a result, the player can set the usage amount of the shared rights of each attribute in detail so as to be advantageous to the attributes of the enemy E appearing on the stage.

Although the game system 201 of the present embodiment has been described as an example in which the shared rights can be used when the normal rights of each player are insufficient, the present invention is not limited to this. The game system 201, for example, even if the normal rights of each player are not insufficient (that is, if each player has the normal rights necessary to play the stage), A form in which shared rights can be used for all or part of the rights may be used. In this form, each player can set the attribute of the shared right used for playing to be advantageous to the enemy E appearing on the stage even if the normal right is not insufficient.

(Third embodiment)
FIG. 23 is a diagram illustrating the configuration of the game system 301 of the third embodiment.
The game system 301 of the third embodiment is the same as the system of the first embodiment, but allows normal rights to be lent as lending rights between players of the same group, and also enables item exchange between players.
As shown in FIG. 23, in this embodiment, as in the second embodiment, Ichiro (P011), Jiro (P012), and Saburo (P013) form the same group G001. An example of owning the terminal 310 will be described.
The game terminal 310 includes a lending rights storage unit 316c, a rights management unit 318b, and an item conversion unit 318c.
The server 320 also includes a lending right storage unit 326c, a right management unit 328b, and an item conversion unit 328c.
Details of each configuration will be described later.

FIG. 24 is a graph showing changes in normal rights and rental rights in the third embodiment.
FIGS. 24(A1), 24(A2), and 24(A3) are graphs showing changes in normal rights of Ichiro (P011), Jiro (P012), and Saburo (P013), respectively. 20(A1), 20(A2), and 20(A3) are stored in the normal right storage units 16a and 26a corresponding to Ichiro (P011), Jiro (P012), and Saburo (P013), respectively. .
FIGS. 24(B1) and 24(B2) are graphs showing changes in normal rights and lending rights of Ichiro (P011) and Jiro (P012) including lending processing of lending rights.

Rights management units 218b and 228b manage the normal rights of each player, as in the first and second embodiments.
However, the normal right storage unit 16a may normally store information of only the player who owns the game terminal 310 regarding the normal right.

Fig. 24 (A1), Fig. 24 (A2), Fig. 24 (A3) show normal rights from 0:00 on March 1 (Thursday) to the current time of March 7 (Wednesday) at 13:00. Show variation.
As shown in FIG. 24A1, Ichiro (P011) continues to play during these periods.
As shown in FIG. 24A2, Jiro (P012) concentrates on the weekends (March 3 (Saturday) and March 4 (Sunday)) during these periods.
As shown in FIG. 24(A3), Saburo (P013) continues to play during these periods on weekdays (days other than March 3 (Saturday) and March 4 (Sunday)). .
Details of FIGS. 24B1 and 24B2 will be described later.

25 and 26 are diagrams showing the display screen of the touch panel 11 during lending processing according to the third embodiment.
As shown in FIG. 25A, the right management units 318b and 328b display a group management screen 360 on the touch panel 11 when the group management button is operated on the selection screen (see FIGS. 5 and 6). .
The group management screen 360 displays an intra-group lending request button 360a, a lending permission setting section 360b, and an intra-group item conversion button 360c.
The intra-group lending request button 360a is a button for accepting a request from Ichiro (P011) to lend a lending right to a player other than Ichiro (P011) in the group.

The lending permission setting unit 360b is a display for setting whether or not Ichiro (P011) (other players) is permitted to lend the lending right to players other than Ichiro (P011) in the group (each player). Department.
In FIG. 25(A), "rejected" is displayed in the lending permission setting section 360b, indicating that Ichiro (P011) is refusing to lend the lending right. In the case of refusal, the rights management unit 318b does not accept a request for the lending of the lending right from a player other than Ichiro (P011) (details of the processing of lending the lending right will be described later). ). In other words, in the case of "Rejected", the rights management units 318b and 328b refuse to lend the normal rights possessed by Ichiro (P011) as lending rights to players other than Ichiro (P011). As a result, Ichiro (P011) will not have his normal rights suddenly reduced.
When Ichiro (P011) touches the area displaying "Rejected", the rights management units 318b and 328b switch the processing related to lending of the lending right from request refusal to request grant. In addition, the rights management units 318b and 328b switch the display in the lending permission setting unit 360b from "denying" to "permitting".
The same is true when the processing relating to the lending of the lending right is switched from request approval to request refusal.

The in-group item conversion button 360c is a button for accepting processing related to item conversion from Ichiro (P011) to a player other than Ichiro (P011) in the group.

(Rental processing of lending rights within the group)
The lending process of lending rights within the same group will be described.
In this example, Ichiro (P011) of group G001 requests Jiro (P012) in the same group to lend the lending right.
As shown in FIG. 25(B), the rights management units 318b and 328b display the normal rights change screen 361 by operating the intra-group lending request button 360a (see FIG. 25(A)) on the group management screen 360. Displayed on the touch panel 11 .
The normal right change screen 361 displays a normal right change graph 361a and a lending setting button 361b.
The normal right change graph 361a shows the normal rights changes of Jiro (P012) and Saburo (P013), who are players other than Ichiro (P011) in the same group, during a period of about one week from the current time (13:00 on March 7). It is a graph visually showing the history of changes in rights.

That is, the rights management units 318b and 328b refer to the information stored in the normal rights storage units 16a and 26a to display the normal rights change graph 361a showing the same information as in FIGS. 24(A2) and 24(A3). do. Note that the rights management unit 318b of the game terminal 310 may obtain these pieces of information by requesting the server 320 in response to the operation of the intra-group lending request button 360a (see FIG. 25A).
As a result, the rights management units 318b and 328b display the normal right holding information of Jiro (P012) and Saburo (P013) of the group G001 on the touch panel 11 of the game terminal 310 of Ichiro (P011) in the same group. can be done.

FIG. 25(B) displays information on changes in ordinary rights for the past one week from the current time (13:00 on March 7), but it may be for a longer period or a shorter period. . In this case, the right management units 318b and 328b may store normal right change information corresponding to the display period.
Further, when four or more players form the same group, the normal right change screen 361 may display the normal right change graphs 361a of three or more players other than the terminal owner by scrolling the screen. .
Furthermore, the format in which the normal right fluctuation screen 361 displays the normal right fluctuation is not limited to the normal right fluctuation graph 361a. The format for displaying the change in normal right may be any format that can display the change, and may be, for example, a tabular format.

By referring to the display screen of his game terminal 310, Ichiro (P011) can consider the following.
- With regard to Jiro (P012), he tends to play intensively on weekends, so his normal rights fluctuate greatly. On the other hand, on weekdays, there is a tendency not to play at all, so the normal right always maintains the upper limit. For this reason, normal rights are highly likely to be in short supply on weekends, but are unlikely to be used on weekdays because the upper limit is always maintained.
・As for Saburo (P013), it is the opposite of Jiro (P012). This means that you don't play at all on weekends, while you concentrate on playing on weekdays. For this reason, normal rights are less likely to be used on weekends, but more likely to be in short supply on weekdays.

The loan setting button 361b is displayed corresponding to each normal right change graph 361a.
The lending setting button 361b is a button for displaying an intra-group lending setting screen 362 (see FIG. 26A) corresponding to the normal right change graph 361a. That is, when the lending setting button 361b displayed next to the normal rights fluctuation graph 361a of Jiro (P012) is operated, the rights management units 318b and 328b lend the lending right to Jiro (P012). Display intra-group loan setting screen 362 for requesting. The same applies to the lending setting button 361b displayed next to the normal right change graph 361a of Saburo (P013).

Here, although illustration is omitted, Ichiro (P011) can confirm the normal rights that he currently possesses on the play start processing screen (see FIG. 7A) or the like. In other words, Ichiro (P011) can confirm that the normal right held at 13:00 on March 7th is 30 points (see FIG. 24A).
If Ichiro (P011) wants to play more from now on, when he thinks that the 30 points he has is not enough, he says to Jiro (P012) and Saburo (P013) in the same group, You can consider requesting the loan of the rental right.

Since it is a weekday at this point, as described above, there is a high possibility that Saburo (P013) will run out of normal rights, while Jiro (P012) will likely run out of normal rights.
Therefore, Ichiro (P011) requests Jiro (P012) to lend the loan right by operating the lending setting button 361b displayed next to Jiro's (P012) normal right fluctuation graph 361a. can be done. The game system 301 also processes this request.

As shown in FIG. 26A, the right management units 318b and 328b display an intra-group lending setting screen 362 on the touch panel 11 for requesting the lending of lending rights from Ichiro (P011) to Jiro (P012). indicate.
The intra-group lending setting screen 362 displays a lending points setting section 362a and a lending execution button 362d.
The lending point number setting unit 362a is a display unit that receives from Ichiro (P011) the setting of the number of points for the lending right to be requested.

The loan point number setting section 362a displays a set loan number display section 362b.
The set loan amount display section 362b displays the set point number in the form of set point number/maximum point number.
The number of set points is the number of points of the lending right to be requested. The set number of points can be changed within the maximum number of points by operating the up/down key 362c.
The maximum number of points is the maximum number of points of lending rights that can be lent to Ichiro (P011).

Note that, in this embodiment, each player can have a lending right corresponding to his or her LV, as in the first embodiment.
In this example, Ichiro (P011)'s LV 100 is lower than Jiro's (P012) LV 120, so the rights management units 318b and 328b display 100 points corresponding to Ichiro's (P011) LV as the maximum number of points. .
However, unlike this example, if Ichiro (P011)'s LV 100 is higher than Jiro's (P012) LV, the maximum number of points is the normal right point value held by Jiro (P012). In other words, if Jiro (P012) is LV80, it is the right to hold the normal rights that Jiro (P012) currently holds, and if he holds the upper limit of 80 points, 80 points are displayed.

The lending execution button 362d is a button for receiving an instruction from Ichiro (P011) to lend the lending rights based on the above settings.
The rights management units 318b and 328b execute the lending of the lending rights from Jiro (P012) to Ichiro (P011) based on the operation of the lending execution button 362d (graphs in FIGS. 24(B1) and 24(B2)). (see bold lines in ).
That is, 50 points of the ordinary rights held by Jiro (P012) are lent to Ichiro (P011) as the lending rights.

The right management units 318b and 328b store these right changes in the normal right storage units 16a and 26a and the rental right storage units 316c and 326c.
That is, the rights management unit 318b of the game terminal 310 of Ichiro (P011) and the rights management unit 328b of the server 320 store the information that Jiro (P012) has loaned 50 points to the lending rights storage units 316c and 326c.
The rights management unit 318b of the game terminal 310 of Jiro (P012) and the rights management unit 328b of the server 320 subtract 50 points from the normal rights held and update the information to 70 points in the normal rights storage units 16a and 26a. Also, information that 50 points have been lent to Ichiro (P011) is stored in the lending right storage units 316c and 326c.

24(B1) and 24(B2), the right management units 318b and 328b, after the lending process, transfer the normal rights of Ichiro (P011) and Jiro (P012) to the normal rights. Recovers at a recovery speed of 10 (points/h).

The rights management units 318b and 328b switch the screen display from the intra-group lending setting screen 362 to the selection screen based on the operation of the lending execution button 362d (see FIG. 7).
When Ichiro (P011) wants to play using the lending right, he can perform an operation to switch from the selection screen to the play start processing screen.
As shown in FIG. 26(B), the play control unit 18a displays a play start processing screen 342 on the touch panel 11 when receiving this operation.
The play start processing screen 342 is substantially the same as the play start processing screen 42 (see FIG. 7A) of the first embodiment, and differs only in the display regarding the lending rights.

That is, the right information display section 342a of the play start processing screen 342 includes a total display section 342g.
The total display portion 342g displays the total point value of the normal right held by Ichiro (P011) and the loan right lent by Jiro (P012). In the example of FIG. 26B, the total point value is 80 points.

Ichiro (P011) can use this total of 80 points as a play right to play on the stage.
Thus, Ichiro (P011) can play using the normal rights that Jiro (P012) has when he does not play. It should be noted that the system operator is also profitable because he/she can encourage the player to play for a long time.

(Intra-group lending right return processing)
Intra-group lending right return processing will be described.
The intra-group lending right return processing is processing for returning the lending right to the lending player after the lending right has been lent within the same group.
FIG. 27 is a flowchart of intra-group lending right return processing according to the third embodiment.
Here, in the above example, a case where Ichiro (P011) returns the loan right to Jiro (P012) will be described. Also, here, an example in which the right management unit 328b of the server 320 performs processing will be described, but as described in the first embodiment, each game terminal 310 and the server 320 perform processing while synchronizing each piece of stored information. may

In S301, the rights management unit 328b determines whether the normal rights of Ichiro (P011) have been fully restored by restoring the normal rights as described above, that is, whether or not the upper limit of 100 points has been reached. do. If the rights management units 318b and 328b determine that the full recovery has been achieved (S301: YES), the process proceeds to S304.

In S302, the rights management unit 328b determines whether or not Jiro (P012) has requested a compulsory return.
For example, when Jiro (P012) has lent the lending right and the normal right to play is insufficient, Jiro (P012) forcibly returns the lending right. It is a request to Ichiro (P011).

As shown in FIG. 26C, here, the rights management unit 318b of the game terminal 310 of Jiro (P012) displays the lending status display unit 360d on the group management screen 360 of the game terminal 310 of Jiro (P012). do.
The lending status display section 360d displays the lending status of the right to Ichiro (P011), that is, information indicating that 50 points of the lending right are being lent to Ichiro (P011).
In addition, the lending status display section 360d displays a forced return button 360e.
The rights management unit 328b of the server 320 accepts a forced return request based on the operation of the forced return button 360e by Jiro (P012).
If the rights management unit 328b determines that Jiro (P012) has requested a compulsory return (S302: YES), it proceeds to S303. The processing from S301 is repeated.

In S303, the rights management unit 328b determines whether or not all the lending rights lent to Ichiro (P011) can be returned to Jiro (P012). In other words, the rights management unit 328b refers to the normal rights storage unit 26a to determine whether or not the number of points of the normal rights of Ichiro (P011) is equal to or greater than 50 points for the lending rights.
When the rights management unit 328b determines that Ichiro (P011) can return all the lending rights (S303: YES), the rights management unit 328b proceeds to S303a. S303: NO), proceed to S304.

In S303a, the rights management unit 328b returns all the lending rights lent to Ichiro (P011) to Jiro (P012). In other words, the rights management unit 328b allocates 50 points of the normal rights owned by Ichiro (P011) to return the lending rights lent by Jiro (P012). As a result, the normal rights owned by Ichiro (P011) are reduced by 50 points, and the normal rights owned by Jiro (P012) are increased by 50 points.
If only a part of the lending right has been returned by the processing of (1) of S304 described later after Ichiro (P011)'s normal rights have been completely restored, the rest of the lending right is returned.
This completes the lending process between Ichiro (P011) and Jiro (P012) (S306).

In S304, the rights management unit 328b appropriates the rights owned by Ichiro (P011) to return the lending rights lent by Jiro (P012).
Here, when proceeding to S304, the situation is as follows. The right management unit 328b processes each scene as follows.

(1) The scene where all normal rights of Ichiro (P011) have been restored (S301: YES → S304)
Such a scene, for example, has a period in which Jiro (P012) does not play and Ichiro (P011) does not play on weekdays after the lending right is given, as Ichiro (P011) intended. For example, the normal rights of Ichiro (P011) are fully restored.
In this case, the right management unit 328b allocates the right recovered by exceeding the upper limit of the normal right to return the lending right.
Then, the processing of S304 is repeated by the processing of S305: NO, which will be described later, so that the lending right is sequentially returned as time elapses.

Through this process (1), Ichiro (P011) can return the lending rights that were lent when he wanted to play, with the rights that increase when he does not play.

(2) When Ichiro (P011)'s normal rights have not fully recovered, Jiro (P012) requests a compulsory return (S301: NO → S302: YES), and the normal rights held by Ichiro (P011) are lent. A scene where all lending rights cannot be returned because the number of rights points is less than 50 (S303: NO → S304)
In such a scene, for example, unlike Ichiro (P011)'s intentions, Jiro (P012)'s normal right is insufficient due to Jiro's (P012) playing on weekdays after lending the lending right, and This is the case, for example, when (P011) continues to play and the normal rights are not fully recovered. Also, for example, when Ichiro (P011) continues to play on weekdays, the normal rights are not fully recovered by the weekend, and the weekend arrives.

In this case, the rights management unit 328b lends all of the ordinary rights owned by Ichiro (P011) from Jiro (P012) even if the ordinary rights owned by Ichiro (P011) do not reach the upper limit. to return the loan rights received. As a result, the ordinary rights possessed by Ichiro (P011) are reduced by the returned amount, and the ordinary rights possessed by Jiro (P012) are increased.
Furthermore, the right management unit 328b uses the right to recover Ichiro (P011) to return the shortfall of the lending right. Then, similarly to the above (1), the lending right is sequentially returned according to the passage of time by repeating the processing of S304 by the processing of S305: NO, which will be described later. As a result, the normal rights of Ichiro (P011) will not increase until the loan rights are returned.

Through this process (2), Jiro (P012), even after lending the normal right as a lending right, if he wants to play, can transfer the restored normal right of Ichiro (P011) to his own normal right. can be obtained as As a result, Jiro's (P012) normal rights are restored at twice the speed of recovery, so there is little disadvantage for Jiro (P012). In addition, since Jiro (P012) has previously permitted the lending of the lending right by the lending permission setting unit 360b (see FIGS. 25A and 26C), the lending of the lending right Even if there is a shortage of ordinary rights for

In S305, the rights management unit 328b determines whether or not all lending rights have been returned. If the rights management unit 328b determines that all lending rights have been returned (S305: YES), it proceeds to S306. Repeat the process from
In S306, the rights management unit 328b performs a series of processes. In this case, the right management unit 328b erases the information on the lending of the lending right between Ichiro (P011) and Jiro (P012) stored in the lending right storage units 316c and 326c.

In this way, the game system 301 enables lending and borrowing of lending rights within the same group, so that each player can play for a long time using the normal rights of other players who are not playing. can.
Note that the rights management unit of the present embodiment may perform control to return more than the lent amount of the lent rights, as in the first embodiment. In this case, the player who has lent the lent right can acquire more normal rights than the lent right. Thereby, the game system 301 can prompt the player to lend the lending right.

(Item exchange process within the group)
Item exchange processing within the same group will be described.
FIG. 28 is a diagram showing a display screen of the touch panel 11 during item exchange processing within a group according to the third embodiment.
Here, at the present time (13:00 on March 7), Ichiro (P011) of group G001 performs an item conversion of Jiro (P012) in the same group.

(Acceptance of item exchange)
As shown in FIG. 28, when the item conversion button 370b is operated on the group management screen 360 (see FIG. 25A) of the game terminal 310 owned by Ichiro (P011), the item conversion units 318c and 328c , the in-group item conversion screen 370 is displayed on the touch panel 11 .
The in-group item conversion screen 370 displays a normal right change graph 370a and an item conversion button 370b.
The normal right change graph 370a is similar to the normal right change graph 361a of Jiro (P012) and Saburo (P013) in the normal right change screen 361 (see FIG. 25(B)).

The item conversion button 370b is displayed corresponding to each normal right change graph 370a.
That is, the in-group item conversion screen 370 displays the item conversion button 370b instead of the loan setting button 361b of the normal right change screen 361 (see FIG. 25(B)).
The item conversion button 370b is a button for requesting item conversion of the player corresponding to the normal right change graph 370a. That is, when the item conversion button 370b displayed next to the normal rights change graph 370a of Jiro (P012) is operated, the item conversion unit 318c executes item conversion of Jiro (P012). The same applies to the item conversion button 370b displayed next to the normal right change graph 370a of Saburo (P013).

The item conversion unit 318c accepts an item conversion request when the normal rights of Jiro (P012) and Saburo (P013) are at the upper limit. In other words, the item conversion units 318c and 328c accept an item conversion request from Ichiro (P011) when Jiro (P012) has 120 points, which is the upper limit of the normal right. Similarly, if Saburo (P013) has a normal right of 130 points, which is the upper limit, this is accepted.
For this reason, for Jiro (P012) and Saburo (P013), it is possible to prevent a situation in which the normal rights are extremely reduced during the neglected state, or are always in a low state.

When Ichiro (P011) operates the item conversion button 370b, the item conversion units 318c and 328c convert the player's item. For example, when Ichiro (P011) operates the item conversion button 370b corresponding to Jiro (P012), the ordinary right held by Jiro (P012) is converted into a right seed, which is an item.
In this way, the game system 301 converts the normal rights of Jiro (P012) (other players) in the same group to items owned by Jiro (P012) in response to a request from Ichiro (P011) (each player). Convert. In other words, Ichiro (P011) can request item conversion for Jiro (P012) on behalf of Jiro (P012). Similarly, Ichiro (P011) can also perform item conversion on Saburo (P013) instead of Saburo (P013).

The item conversion processing for Jiro (P012) and Saburo (P013) is the same as in the first embodiment. For example, when Jiro (P012) converts an item, the item conversion unit 318c of the game terminal 310 owned by Jiro (P012) and the item conversion unit 328c of the server 320 store the normal right storage unit 16a and the item storage unit 16a related to Jiro (P012). Normal rights within 25h, update information about items. In addition, Jiro (P012) can use the itemized seed of rights in the play of each stage by being processed in the same manner as in the first embodiment.

Here, since the normal right change graph 370a of Jiro (P012) and Saburo (P013) is displayed on the in-group item conversion screen 370, Ichiro (P011) refers to these as follows: , it is possible to consider which player's normal rights are to be converted into items.
In other words, since Jiro (P012) and Saburo (P013) respectively hold normal rights up to the upper limit, the item conversion units 318c and 328c are in a state where they can accept item conversions regarding Jiro (P012) and Saburo (P013). is.
However, in order for the player to use the seeds of rights once converted into items for play, it is necessary to re-convert them to normal rights again. This is a little troublesome for the player. It should be noted that since the right seed can be used for play by reconverting it to a normal right, there is no disadvantage regarding the play right that accompanies the item conversion.

Therefore, when Ichiro (P011) requests Jiro (P012) and Saburo (P013) to convert items with normal rights, it is not necessary for Jiro (P012) and Saburo (P013) to reconvert to normal rights. It is preferable to be
In this case, Ichiro (P011) can consider whether or not to request item conversion for Jiro (P012) and Saburo (P013), similar to lending the right to lend within the group. In other words, it is only necessary to request item conversion to a player who is expected not to play until the normal rights that have been reduced after item conversion are fully restored.

In the example of FIG. 28, Ichiro (P011) refers to the normal rights fluctuation graph 370a to play Jiro (P012) on weekdays in the same way as when referring to the normal rights fluctuation graph 361a of FIG. It can be expected that Saburo (P013) is likely to be played on weekdays.
Therefore, it can be expected that Ichiro (P011) will not play Jiro (P012) until all normal rights are restored after item conversion, while Saburo (P013) can be expected to play during this time. .

(Process after item exchange)
The item conversion units 318c and 328c process as follows when each player requests item conversion of another player in the same group.
Here, as in the above example, an example in which Ichiro (P011) requests Jiro (P012) to convert a normal right item will be described.

(1) The normal rights of Jiro (P012) are recovered as in the first embodiment.
For this reason, Jiro (P012) can have the normal rights held at the upper limit reduced to less than the upper limit by the item conversion request from Ichiro (P011). As a result, as in the first embodiment, Jiro (P012) has the advantage of being able to acquire the normal right to recover even if the idle time continues.
In other words, Jiro's (P012) normal rights are likely to remain at or below the upper limit even when left unattended (unplayable) for a long period of time. Therefore, Jiro (P012) has the advantage of being able to acquire more normal rights, which increase with the passage of time, even if the idle state (unplayable state) continues for a long time.

(2) After Ichiro (P011) converts Jiro (P012)'s right to play into an item, Jiro (P012) logs into the game within the time limit to give Ichiro (P011) a privilege.
The time limit is the elapsed time after item conversion. The time limit can be set in the game program or the like by the system operator, and can be set, for example, within 24 to 48 hours. The privilege may be anything that is advantageous to Ichiro (P011), such as a normal right or an item that can be worn by the character.
Also, Jiro's (P012) logging into the game may be any other operation as long as it accompanies an operation related to the game by Jiro (P012). An operation related to the game, for example, using the seeds of rights itemized in Jiro (P012) may be used.

With the processing of (2), the game system 301 may be able to obtain a privilege by requesting item conversion for Jiro (P012) even when Ichiro (P011) is short of normal rights. There is As a result, even if the game system 301 does not have enough normal rights for Ichiro (P011), the game system 301 can log on to the game to request item conversion from Jiro (P012) and the like. can encourage you to do so.
On the other hand, if Jiro (P012) continues to be left unattended, there is a high possibility that the normal rights that have reached the upper limit have been converted into items by Ichiro (P011) or the like. Therefore, Jiro (P012) has a desire to let Ichiro (P011) acquire the privilege. As a result, the game system 301 can prompt Jiro (P012) to log in to the game within the time limit without continuing the neglected state for a long time.
As a result, the game system 301 can continuously prompt the players forming the group to perform game-related operations, thereby suppressing withdrawal from the game.

In this way, the game system 301 performs item exchange processing within the same group. Therefore, the player can acquire more normal rights to recover by having the item converted in the idle state.

In this embodiment, an example is shown in which each player can convert the normal rights of other players in the same group into items, but the present invention is not limited to this.
For example, instead of normal rights, excess rights may be converted into items. In this case, the rights management unit displays a graph of changes in excess rights on the in-group item conversion screen 370 based on the information in the excess rights storage units 16b and 26b, and accepts the operation of the item conversion button 370b. All you have to do is In this case, the converted item may be a seed of rights corresponding to excess rights, which can be reconverted to excess rights. In this case, since the normal right does not decrease with the item conversion, the player does not have to reconvert the seed of the right to the normal right.

Although the embodiments of the present invention have been described above, the present invention is not limited to the above-described embodiments, and various modifications and changes are possible, such as modifications described later. It is within the technical scope of the present invention. Moreover, the effects described in the embodiments are merely enumerations of the most suitable effects produced by the present invention, and the effects of the present invention are not limited to those described in the embodiments. In addition, although the embodiment described above and the modification described later can be used in combination as appropriate, detailed description thereof will be omitted.

(deformed form)

(1) In the embodiment, the game program is downloaded to the game terminal and executed on the game terminal. However, the present invention is not limited to this. For example, the game program is executed by a server and may relate to a browser game that operates on a WEB page displayed on a game terminal.

(2) In the embodiment, an example was shown in which the points of the excess rights increase over time after the normal rights reached the upper limit value, but the present invention is not limited to this. The excess entitlement may itself be indicated by the elapsed time after the normal entitlement reaches the capped value. In this case, the parameter indicating the degree of normal rights is indicated by the elapsed time after the normal rights reach the upper limit value, and the player is given benefits (such as the right to play the stage for a limited time) according to the elapsed time. do it.

(3) In the embodiment, the type of game executed in the game system is RPG, but is not limited to this. The type of game may be any game to which the configuration of the embodiment can be applied, and may be, for example, a fighting game, a shooting game, or the like.

(4) In the embodiment, a group is described as a form in which a plurality of players are associated with each other by group ID, but the present invention is not limited to this. The form in which a plurality of players are associated may be any structure, and can be appropriately modified according to game specifications and the like. That is, a group is the concept of each player and other players related in some fashion. For example, in the case of a game specification in which each player can temporarily use characters of other players in the play of each stage, each player and the other players may be temporarily associated with each other. .

1, 201, 301... Game system 10, 210, 210A, 310... Game terminal 11... Touch panel 15a, 25a... Game program storage unit 15, 25... Storage unit 16, 26... Right information storage unit 16a, 26a... Normal right storage Part 16b, 26b... Excess right storage part 16c, 26c, 316c, 326c... Lending right storage part 18, 28... Control part 18a... Play control part 18b, 28b, 218b, 228b, 318b, 328b... Right management part 18c, 28c , 318c, 328c... Item conversion unit 20, 220, 320... Server 25b... Management program 25h... Item storage unit 25i... Group information storage unit 216d, 226d... Shared right storage unit

Claims (6)

A game system that can be played by using a right to play that increases according to an increase condition,
a right information storage unit that stores the increasing play right up to the holding upper limit value as the held play right owned by the player;
and a right management unit that manages play rights,
The rights management unit
lending a lending right, which is a playing right, to the player in response to a request from the player and storing it in the right information storage unit;
Equipped with a play control unit that controls the game play of this game system,
The play control unit
When playing using the loan right, giving the player a privilege that is more advantageous than when playing using the owned play right,
A game system characterized by A game system that can be played by using a right to play that increases according to an increase condition,
a right information storage unit that stores the increasing play right up to the holding upper limit value as the held play right owned by the player;
and a right management unit that manages play rights,
The rights management unit
lending a lending right, which is a playing right, to the player in response to a request from the player and storing it in the right information storage unit;
The rights management unit
lowering the holding upper limit value of the right information storage unit according to lending the lending right to the player;
A game system characterized by In the game system according to claim 1 or claim 2 ,
This game has player levels,
The lending upper limit value of lending right increases according to the player's level,
A game system characterized by In the game system according to any one of claims 1 to 3 ,
The rights management unit
When the lending right exists in the right information storage unit, allocating the playing right that increases according to the increase condition to the return of the lending right without increasing it as the owned play right,
A game system characterized by A computer provided with a game system that can be played by using the right to play that increases according to the increasing conditions,
a right information storage means for storing the increasing play right up to the holding upper limit value as the held play right held by the player;
Function as a right management means for managing play rights,
the rights management means,
In response to a player's request, the lending right, which is the playing right, is lent to the player and stored in the right information storage means;
function as play control means for controlling the game play of this game system,
the play control means,
When playing using the lending right, it functions so as to give a privilege more advantageous to the player than when playing using the owned play right,
A game program characterized by A computer provided with a game system that can be played by using the right to play that increases according to the increasing conditions,
a right information storage means for storing the increasing play right up to the holding upper limit value as the held play right held by the player;
Function as a right management means for managing play rights,
the rights management means,
In response to a player's request, the lending right, which is the playing right, is lent to the player and stored in the right information storage means;
the rights management means,
functioning to lower the holding upper limit value of the right information storage means according to lending the right to lend to the player;
A game program characterized by

Images