JP2016101395A - Program and information processing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reflect the intention of a player having a special right in participation of an event performed in a group unit.SOLUTION: A program makes a computer to function as: first storage means for storing information for distinguishing one or more first players having a special right in a group from second players other than the first players in each group including one or more players belonging thereto; second storage means for storing information for determining whether a participation request for an event in a game performed in the group unit has been received or not by each group; and participation request reception means for, in a time period in which the participation request for the event can be performed, receiving a participation request for the event only from a terminal device operated by the first player, and updating information stored in the second storage means so as to allow the participation request for the event from the group, to which the first player performed the participation request for the event belongs, to be a received participation request.SELECTED DRAWING: Figure 5

Description

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

  In recent years, so-called social games in which a plurality of players can participate in the same game have been provided. In social games, a group battle event (such as a guild battle) in which a battle between specific groups such as a guild, a party, a team, and a community is known (see, for example, Patent Document 1).

Patent 5419113

  For example, in an in-game event that is performed on a group basis, the participation of the group in the event is performed automatically or when a predetermined number of players or more participate in the event in the group.

  Therefore, for example, even when a player having special authority such as an administrator is set in the group, the intention of the player having special authority (for example, whether to participate / not participate) is used for participation in the event. There was a problem that it could not be reflected.

  The present invention has been made in view of the above-described problems, and an object of the present invention is to reflect the intention of a player having a special authority in participation in an event performed in units of groups.

  In order to solve the above-described problem, claim 1 of the present application provides a computer for each group to which one or more players belong, one or more first players having special authority in the group, and the first First storage means for storing information for determining a second player other than the player, information for determining whether or not a request to participate in an event in a game performed in units of groups has been accepted, The second storage means for storing each group, and during the period in which the request for participation in the event can be made, accepts the participation request for the event only from the terminal device operated by the first player, and When a request for participation in the event is received, a request for participation in the event of the group to which the first player who made the request for participation in the event belongs is assigned. As the only with already, and said second storage means is a program for functioning as a participation request accepting means for updating the information stored.

  According to the present invention, it is possible to reflect the intention of a player having special authority in participation in an event performed in units of groups.

It is a lineblock diagram of an example of an information processing system concerning this embodiment. It is a hardware block diagram of an example of the computer which concerns on this embodiment. It is a processing block diagram of an example of an information processing system concerning this embodiment. It is a flowchart of an example showing the flow of the event of this embodiment. It is a flowchart of an example of the entry reception process to an event. It is a block diagram of an example of player information. It is a block diagram of an example of guild information. It is a block diagram of an example of event entry information. It is an image figure of an example of an entry cancellation possible screen. It is an image figure of an example of an entry possible screen. It is an image figure of an example of an entry impossible screen. It is an image figure of an example of the entry period in 2nd Embodiment. It is a flowchart of an example of the entry reception process to an event. It is an image figure of an example of an entry impossible screen. It is a flowchart of an example of a guild master exclusive screen selection process of step S32. It is a flowchart of an example of a guild member exclusive screen selection process of step S34. It is an image figure of an example of an entry completed screen. It is a flowchart of an example of a guild master exclusive screen selection process of step S32. It is a block diagram of the other example of event entry information. It is an image figure of an example of a screen which can be unblocked. It is an image figure of an example of an entry and a blockable screen. It is a flowchart of an example of a guild member exclusive screen selection process of step S34. It is an image figure of an example of a screen during a block.

Next, embodiments of the present invention will be described in detail. In addition, although this embodiment demonstrates the example of the guild battle event which battle | competes between groups as an example of the event in a game performed per group, it is not limited to a guild battle event. The present invention can be widely applied to events that accept participation in groups.
[First Embodiment]
<System configuration>
FIG. 1 is a configuration diagram of an example of an information processing system according to the present embodiment. In the information processing system 1 of FIG. 1, one or more client terminals 2 and a game server device 3 are connected via a network 4 such as the Internet.

  The client terminal 2 is a terminal device such as a PC, a smartphone, or a tablet operated by a player, or a terminal device such as a home or business game dedicated device. The game server device 3 performs game management and control performed by the player at the client terminal 2, billing processing within the game, and the like.

  The information processing system 1 in FIG. 1 is an example, and it goes without saying that there are various system configuration examples depending on the application and purpose. For example, the game server device 3 of FIG. 1 may be configured to be distributed among a plurality of computers.

<Hardware configuration>
<< Client terminal and game server apparatus >>
The client terminal 2 and the game server device 3 in FIG. 1 are realized by, for example, a computer having a hardware configuration shown in FIG. FIG. 2 is a hardware configuration diagram of an example of a computer according to the present embodiment.

  The computer in FIG. 2 includes an input device 501, a display device 502, an external I / F 503, a RAM 504, a ROM 505, a CPU 506, a communication I / F 507, an HDD 508, and the like. Note that the input device 501 and the display device 502 may be connected and used when necessary.

  The input device 501 is a touch panel, operation keys and buttons, a keyboard, a mouse, and the like used by the player to input various signals. The display device 502 is a display such as a liquid crystal or an organic EL that displays a screen. A communication I / F 507 is an interface for connecting a computer to the network 4. Accordingly, the computer can perform data communication via the communication I / F 507.

  The HDD 508 is an example of a non-volatile storage device that stores programs and data. The stored programs and data include an OS that is basic software for controlling the entire computer, and applications that provide various functions on the OS.

  Note that the computer may use a drive device (for example, a solid state drive: SSD) that uses a flash memory as a storage medium instead of the HDD 508.

  The external I / F 503 is an interface with an external device. The external device includes a recording medium 503a. Accordingly, the computer 500 can read and / or write the recording medium 503a via the external I / F 503. Examples of the recording medium 503a include a flexible disk, a CD, a DVD, an SD memory card, and a USB memory.

  The ROM 505 is an example of a nonvolatile semiconductor memory (storage device) that can retain programs and data even when the power is turned off. The ROM 505 stores programs and data such as BIOS, OS settings, and network settings that are executed when the computer is started. The RAM 504 is an example of a volatile semiconductor memory (storage device) that temporarily stores programs and data.

  The CPU 506 is an arithmetic unit that realizes control and functions of the entire computer by reading a program and data from a storage device such as the ROM 505 and the HDD 508 onto the RAM 504 and executing processing. Further, the CPU 506 also has a function as a time measuring unit that counts elapsed time, and is configured to be able to execute a program that branches under a condition according to the counted elapsed time. In addition, you may comprise said time measuring means with another hardware instead of CPU506.

  The client terminal 2 and the game server device 3 according to the present embodiment can implement various processes as described later by executing a program on a computer having the above-described hardware configuration.

<Software configuration>
A software configuration of the information processing system 1 according to the present embodiment will be described. The information processing system 1 in FIG. 1 is realized by, for example, the processing blocks shown in FIG. FIG. 3 is a processing block diagram of an example of the information processing system according to the present embodiment.

  The game server device 3 of the information processing system 1 implements the communication unit 10, the control unit 12, and the storage unit 14 by executing a program. The control unit 12 includes a game progression unit 20, an event progression unit 22, and an entry reception unit 24. The storage unit 14 includes an event entry information storage unit 30, a player information storage unit 32, and a guild information storage unit 34.

  Further, the client terminal 2 of the information processing system 1 implements an operation receiving unit 50, a control unit 52, a storage unit 54, a communication unit 56, and a screen display unit 58 by executing a program. The control unit 52 includes an operation content transmission unit 66 and a display control unit 68. The communication unit 10 of the game server device 3 communicates with the client terminal 2.

  The control part 12 performs the process regarding a game and a guild battle event (henceforth an event), and advances a game and an event. The memory | storage part 14 memorize | stores the information regarding a game and an event.

  The game progression unit 20 of the control unit 12 advances the game based on the operation content received by the client terminal 2 from the player. The event progression unit 22 advances the event based on the operation content received by the client terminal 2 from the player.

  Moreover, the entry reception part 24 receives the entry (participation) from the player who operates the client terminal 2 per guild unit during an entry period. The event progression unit 22 matches the opponents of each guild after the deadline for entry, and causes the guild to fight against each other after the event starts.

  Based on the progress of the game, the game progress unit 20 responds to the client terminal 2 with parameters for displaying various screens on the client terminal 2. Further, the event progression unit 22 responds to the client terminal 2 with parameters for displaying various screens on the client terminal 2 based on the progression of the event. Furthermore, the entry reception unit 24 responds to the client terminal 2 with parameters for causing the client terminal 2 to display various screens for receiving entry to the event.

  The parameter for displaying various screens on the client terminal 2 is information for identifying screen data, for example, when selecting a screen on the game server device 3 side. The parameter for displaying various screens on the client terminal 2 is information for selecting a screen, for example, when selecting a screen on the client terminal 2 side.

  The event entry information storage unit 30 of the storage unit 14 stores, for each guild, whether an entry has been made to the event. The player information storage unit 32 stores player information related to the player, and includes, for example, information for identifying a guild to which the player belongs. The guild information storage unit 34 stores guild information related to the guild, and includes information for identifying the guild master, for example. The guild master is an example of a player who has special authority in the guild. For example, the guild master may be another name such as an administrator or a leader.

  The player having special authority may be a player having the highest authority in the guild, a player having authority to manage the guild, a player having authority to enter the event, or the like. The guild may be another name for identifying a group of one or more players as a group, such as a team or an alliance. Furthermore, for example, a player with a name such as a submaster or a subleader may be included in the guild master in the present invention as a role to assist the player having the highest authority. As a result, there may be more than one guild master in a guild.

  The operation receiving unit 50 of the client terminal 2 receives an operation from a player who operates the client terminal 2. In addition, the control unit 52 performs processing related to a game, an event, and an entry to the event in the client terminal 2. The operation content transmission unit 66 of the control unit 52 transmits the content of the operation received by the operation receiving unit 50 from the player to the game server device 3.

  The display control unit 68 receives parameters for displaying various screens as a response to the operation content transmitted by the operation content transmission unit 66 to the game server device 3. The display control unit 68 performs control so that a screen corresponding to the received parameter is displayed on the screen display unit 58.

  The storage unit 54 stores information necessary for the client terminal 2. For example, the storage unit 54 stores screen data of a screen displayed by the screen display unit 58. The communication unit 56 communicates with the game server device 3. The screen display unit 58 performs screen display according to the control of the display control unit 68.

  The configuration of the information processing system 1 in FIG. 3 is an example, and at least a part of the processing blocks on the game server device 3 side may be provided on the client terminal 2 side. For example, the game progress unit 20, the event progress unit 22, and the entry reception unit 24 provided in the game server device 3 in the information processing system 1 of FIG. 3 may be provided in the control unit 52 of the client terminal 2. . The game progress unit 20 provided in the client terminal 2 acquires necessary information from the game server device 3 based on the progress of the game.

  As described above, the information processing system 1 according to the present embodiment may perform the progress of the game and the event and accept the entry to the event at the client terminal 2 or the game server device 3. In addition, the information processing system 1 according to the present embodiment may perform event progress and event entry reception by a server device other than the game server device 3.

  The control unit 52 of the client terminal 2 receives page data described in HTML (Hyper Text Markup Language) or the like, a script included in the page data from the game server device 3, and performs processing related to the game or event. There is a browser type. The control unit 52 of the client terminal 2 includes an application type that performs processing related to a game or an event based on an installed application.

<Processing>
<Outline of the event>
Here, an overview of the event of the present embodiment will be described. FIG. 4 is a flowchart showing an example of an event flow according to this embodiment. As shown in FIG. 4, the event of this embodiment participates in guild units, and proceeds in the order of entry, matching, and battle.

  In step S11, the information processing system 1 according to the present embodiment receives an entry for an event in guild units within the entry period. The entry period is a period during which an entry can be made to an event provided before the period during which the event can be played.

  In step S12, the information processing system 1 of the present embodiment matches the opponents of each guild that has been entered after the entry period has elapsed. And in step S13, the information processing system 1 of this embodiment makes a battle | competition between the matched guilds in the period which can play an event.

  In the information processing system 1 of the present embodiment, a match can be performed between matched guilds even in an asynchronous state in which the player is not logged in at the same time, but in a synchronized state in which the player is not logged in at the same time.

  For example, in the information processing system 1 according to the present embodiment, when each player belonging to the guild challenges a single player belonging to the opponent's guild, the player who has been challenged is logged in. Even if it is not, it is possible to perform a battle using information necessary for the battle, such as a deck preset by the player. In addition, you may make it the information processing system 1 of this embodiment perform a battle | competition in a synchronized state between the matched guilds.

  And after progress of the period which can play an event, the information processing system 1 of this embodiment performs required post-processes, such as confirmation of the order according to a battle result, and provision of a reward. In the case of an event where matching is performed a plurality of times in one entry, matching of the opponent and the battle with the matched opponent are repeated.

《Event entry acceptance process》
In step S11 of FIG. 4, the information processing system 1 according to the present embodiment receives an entry from the guild master to the event within the event entry period according to the procedure shown in FIG. FIG. 5 is a flowchart of an example of an event entry acceptance process.

  For example, when the entry receiving unit 24 of the game server device 3 receives the content of an operation for displaying the event TOP screen from the client terminal 2 within the event deadline (for example, an operation of tapping an event button or an event banner), the event shown in FIG. The entry acceptance process is started.

  In step S <b> 21, the entry receiving unit 24 determines whether or not the player who has performed an operation for displaying the event TOP screen on the client terminal 2 is a guild master. For example, the entry receiving unit 24 acquires the guild ID of the guild to which the player belongs based on the player information as shown in FIG. 6 stored in the player information storage unit 32.

  FIG. 6 is a configuration diagram of an example of player information. The player information in FIG. 6 is information representing a guild to which each player belongs. In the player information of FIG. 6, a player ID for identifying a player, a player name, and a guild ID for identifying a guild are associated with each other.

  Further, the entry receiving unit 24 determines whether or not the player is a guild master based on the guild information as shown in FIG. 7 stored in the guild information storage unit 34. FIG. 7 is a configuration diagram of an example of guild information. The guild information in FIG. 7 is information representing the guild master of each guild. In the guild information in FIG. 7, the guild ID and the player ID of the guild master are associated with each other. Therefore, the entry receiving unit 24 can determine whether or not the player is a guild master from the player information of FIG. 6 and the guild information of FIG.

  If the player who has performed an operation for displaying the TOP screen of the event at the client terminal 2 is a guild master, in step S22, the entry receiving unit 24 determines whether or not the event has been entered. For example, the entry receiving unit 24 acquires information indicating whether or not the entry has been made to the event based on the event entry information as illustrated in FIG. 8 stored in the event entry information storage unit 30.

  FIG. 8 is a configuration diagram of an example of event entry information. The event entry information in FIG. 8 is information indicating whether each guild has already been entered in the event. In the event entry information of FIG. 8, a guild ID for identifying a guild is associated with an entry flag that is “ON” when the event has already been entered and “OFF” when the event has not been entered. Therefore, the entry receiving unit 24 can determine from the event entry information shown in FIG. 8 whether or not the guild to which the player belongs has already been entered in the event.

  If the guild to which the player belongs has already been entered in the event, the entry receiving unit 24 selects an entry cancelable screen 1000 as shown in FIG. 9 in step S23. FIG. 9 is an image diagram of an example of an entry cancelable screen.

  The entry cancelable screen 1000 in FIG. 9 is provided with an “cancel entry” button 1001. The guild master can request to cancel the entry within the entry period by pressing the “cancel entry” button 1001 on the entry cancelable screen 1000.

  When the process proceeds from step S23 to step S25, the entry receiving unit 24 transmits the parameter for displaying the entry cancelable screen 1000 to the client terminal 2, so that the entry cancelable screen 1000 in FIG. To display. The client terminal 2 can receive an entry cancellation request from the guild master from the entry cancellation enable screen 1000 of FIG. 9 and can transmit the entry cancellation request to the entry reception unit 24 of the game server device 3.

  Upon receiving the entry cancellation request, the entry receiving unit 24 cancels the entry to the event by changing the entry flag of the event entry information shown in FIG. 8 from “ON” to “OFF”.

  Therefore, the guild master can cancel the entry of the entered event from the entry cancelable screen 1000 of FIG. 9 displayed by the screen display unit 58 of the client terminal 2.

  If the guild to which the player belongs is not already entered in the event, the entry receiving unit 24 selects the entry possible screen 1010 in FIG. 10 in step S24. FIG. 10 is an image diagram of an example of an entry enable screen.

  The entry possible screen 1010 of FIG. 10 is provided with an “entry” button 1011. The guild master can request an entry within the entry period by pressing an “entry” button 1011 on the entry possible screen 1010.

  In addition, when progressing to step S25 from step S24, the entry reception part 24 displays the entry possible screen 1010 of FIG. 10 on the client terminal 2 by transmitting the parameter for displaying the entry possible screen 1010 to the client terminal 2. Let The client terminal 2 can receive an entry request from the guild master from the entry-possible screen 1010 in FIG. 10, and can transmit the entry request to the entry accepting unit 24 of the game server device 3.

  Upon receipt of the entry request, the entry receiving unit 24 changes the entry flag of the event entry information as shown in FIG. 8 from “OFF” to “ON” to enter the event. Therefore, the guild master can enter the event from the entry possible screen 1010 of FIG. 10 displayed by the screen display unit 58 of the client terminal 2.

  If the entry receiving unit 24 determines in step S21 that the player who performed the operation for displaying the event TOP screen is not a guild master, the entry receiving unit 24 is a guild member who cannot enter the event. Exit. At this time, the entry receiving unit 24 may select the entry impossible screen 1020 in FIG.

  FIG. 11 is an image diagram of an example of an entry impossible screen. The entry impossible screen 1020 in FIG. 11 is provided with a message 1021 indicating that only the guild master can enter. The entry accepting unit 24 can display the entry impossible screen 1020 of FIG. 11 on the client terminal 2 by transmitting the parameter for displaying the entry impossible screen 1020 to the client terminal 2.

  Therefore, the guild member can know that only the guild master can enter the event from the entry disable screen 1020 of FIG. 11 displayed by the screen display unit 58 of the client terminal 2.

(Summary)
According to the information processing system 1 of the first embodiment, since only the guild master can enter the event, the intention of the guild master can be reflected in the entry to the event.

In addition, according to the information processing system 1 of the first embodiment, since the guild that has made an entry participates in the event, there is no problem caused by the participation of an already neglected guild in the event. For example, according to the information processing system 1 of the first embodiment, there is no problem that an extra load is applied to the game server device 3 when an already neglected guild participates in the event. In addition, according to the information processing system 1 of the first embodiment, there is no problem that the opponent's guild must compete with a neglected guild.
[Second Embodiment]
In the first embodiment, only the guild master makes an entry to the event. In the second embodiment, as shown in FIG. 12, a period during which only a guild master can enter is provided after a period during which only a guild master can enter.

  FIG. 12 is an image diagram of an example of an entry period in the second embodiment. As shown in FIG. 12, in the second embodiment, the entry periods are divided, the previous entry period is a period during which only the guild master can enter, and the subsequent entry period is a period during which guild members can also enter. Note that the second embodiment is the same as the first embodiment except for a part thereof, and thus description thereof will be omitted as appropriate.

《Event entry acceptance process》
In step S11 of FIG. 4, the information processing system 1 according to the second embodiment receives an entry from the guild master or guild member in the event according to the procedure shown in FIG. 13 within the event entry period. FIG. 13 is a flowchart of an example of an event entry acceptance process.

  For example, when the entry receiving unit 24 of the game server device 3 receives the content of the operation for displaying the TOP screen of the event from the client terminal 2 within the event deadline, the entry receiving process for the event of FIG. 13 is started.

  In step S31, the entry receiving unit 24 determines whether or not the player who has performed an operation for displaying the event TOP screen on the client terminal 2 is a guild master.

  If the player who performed the operation for displaying the event TOP screen at the client terminal 2 is a guild master, the entry reception unit 24 performs a guild master dedicated screen selection process at step S32. Details of the guild master dedicated screen selection process in step S32 will be described later.

  When the process proceeds from step S32 to step S35, the entry receiving unit 24 displays the guild master dedicated screen on the client terminal 2 by transmitting the parameters for displaying the guild master dedicated screen selected in step S32 to the client terminal 2. Let The client terminal 2 can receive a process corresponding to the guild master dedicated screen selected in step S32 from the guild master and transmit a request corresponding to the process to the entry receiving unit 24 of the game server device 3.

  If the entry receiving unit 24 determines in step S31 that the player who performed the operation for displaying the TOP screen of the event is not the guild master, the entry receiving unit 24 performs the process of step S33. In step S33, the entry receiving unit 24 determines whether or not the guild member shown in FIG.

  If the guild member can also enter, the entry receiving unit 24 performs a guild member-specific screen selection process in step S34. Details of the guild member-only screen selection process in step S34 will be described later.

  When the process proceeds from step S34 to step S35, the entry receiving unit 24 displays the guild member dedicated screen on the client terminal 2 by transmitting the parameter for displaying the guild member dedicated screen selected in step S34 to the client terminal 2. Let The client terminal 2 can receive a process corresponding to the guild member dedicated screen selected in step S34 from the guild member and transmit a request corresponding to the process to the entry receiving unit 24 of the game server device 3.

  Further, in step S33, if the guild member is not in a period in which entry is possible, the entry receiving unit 24 cannot receive an event entry from the guild member, and thus the processing of the flowchart in FIG.

  At this time, the entry receiving unit 24 may select the entry impossible screen 1030 in FIG. FIG. 14 is an image diagram of an example of an entry impossible screen. 14 is provided with a message 1031 indicating that only the guild master can currently enter. The entry accepting unit 24 can display the entry impossible screen 1030 of FIG. 14 on the client terminal 2 by transmitting a parameter for displaying the entry impossible screen 1030 to the client terminal 2.

  Therefore, the guild member can know that only the guild master can currently enter the event from the entry impossible screen 1030 of FIG. 14 displayed by the screen display unit 58 of the client terminal 2.

  FIG. 15 is a flowchart of an example of the guild master dedicated screen selection process in step S32. In step S41, the entry receiving unit 24 determines whether or not the event has already been entered.

  If the guild to which the player belongs has already been entered in the event, the entry receiving unit 24 selects an entry cancelable screen 1000 as shown in FIG. 9 in step S42. The guild master can request cancellation of the entry within the entry period by pressing the “cancel entry” button 1001 on the entry cancellation possible screen 1000.

  If the guild to which the player belongs is not already entered in the event, the entry receiving unit 24 selects the entry possible screen 1010 in FIG. 10 in step S43. The guild master can request an entry within the entry period by pressing the “enter” button 1011 on the entry possible screen 1010.

  FIG. 16 is a flowchart of an example of the guild member dedicated screen selection process in step S34. In step S51, the entry receiving unit 24 determines whether or not the event has already been entered.

  If the guild to which the player belongs has already been entered in the event, the entry receiving unit 24 selects the entry-completed screen 1040 in FIG. 17 in step S52. FIG. 17 is an image diagram of an example of an entered screen.

  The entry completed screen 1040 in FIG. 17 is provided with a message 1041 indicating that entry has been made, but is not provided with the “cancel entry” button 1001 as shown in FIG. Thus, the guild member can confirm that the entry has been made, but cannot request cancellation of the entry.

  In addition, when progressing to step S35 from step S52, the entry reception part 24 displays the entry completed screen 1040 of FIG. 17 on the client terminal 2 by transmitting the parameter for displaying the entry completed screen 1040 to the client terminal 2. Let The guild member can confirm that the event has been entered from the entry completed screen 1040 shown in FIG. 17 displayed on the client terminal 2.

  If the guild to which the player belongs is not already entered in the event, the entry receiving unit 24 selects the entry possible screen 1010 in FIG. 10 in step S53. The guild member can request entry by pressing the “entry” button 1011 on the entry possible screen 1010 so that the “guild member can also enter” period shown in FIG.

  In addition, when progressing to step S35 from step S53, the entry reception part 24 displays the entry possible screen 1010 of FIG. 10 on the client terminal 2 by transmitting the parameter for displaying the entry possible screen 1010 to the client terminal 2. Let The client terminal 2 can receive an entry request from the guild member from the entry-possible screen 1010 in FIG. 10 and transmit the entry request to the entry accepting unit 24 of the game server device 3.

  Upon receipt of the entry request, the entry receiving unit 24 changes the entry flag of the event entry information as shown in FIG. 8 from “OFF” to “ON” to enter the event.

  Therefore, the guild member can enter the event from the entry possible screen 1010 of FIG. 10 displayed by the screen display unit 58 of the client terminal 2.

(Summary)
According to the information processing system 1 of the second embodiment, since the period during which only the guild master can enter is provided after the period during which only the guild master can enter, the guild master can preferentially enter. Thus, for example, when selecting an event to be entered from a plurality of events having different contents, difficulty levels, etc., according to the information processing system 1 of the second embodiment, the intention of the guild master can be reflected with priority. it can.

Further, according to the information processing system 1 of the second embodiment, since a period during which guild members can also enter is provided, even if the guild master cannot log into the game for some reason and cannot execute the entry process. , Guild members can enter. This allows a guild with one player who wants to enter the event to enter the event.
[Third Embodiment]
In the second embodiment, since a period during which guild members can also enter is provided, the intention of the guild master not to enter the event cannot be reflected. Therefore, in the third embodiment, the guild master can block (prohibit) entry of the guild member into the event.

  Note that the third embodiment is the same as the second embodiment except for a part thereof, and thus description thereof will be omitted as appropriate.

《Event entry acceptance process》
In step S11 of FIG. 4, in the information processing system 1 according to the third embodiment, as in the second embodiment, an entry from the guild master or guild member to the event is accepted according to the procedure shown in FIG.

  The information processing system 1 according to the third embodiment differs from the second embodiment in the guild master dedicated screen selection process in step S32 and the guild member dedicated screen selection process in step S34. Hereinafter, the guild master dedicated screen selection process in step S32 and the guild member dedicated screen selection process in step S34, which are different from the second embodiment, will be described.

  FIG. 18 is a flowchart of an example of the guild master dedicated screen selection process in step S32. In step S61, the entry receiving unit 24 determines whether or not the event has already been entered. For example, the entry receiving unit 24 acquires information indicating whether or not the entry has been made to the event based on the event entry information as illustrated in FIG. 19 stored in the event entry information storage unit 30.

  FIG. 19 is a configuration diagram of another example of event entry information. In the event entry information shown in FIG. 19, information indicating whether or not an event has been entered and information indicating whether or not the entry to the event is blocked are set for each guild.

  In the event entry information of FIG. 19, the guild ID for identifying the guild, the entry flag that is “ON” when the event has already been entered and “OFF” when the event has not been entered, and the entry to the event are blocked. Is associated with a block flag that is “ON” and “OFF” when the entry to the event is not blocked. Accordingly, the entry receiving unit 24 can determine from the event entry information shown in FIG. 19 whether the guild to which the player belongs has already been entered in the event, and whether the entry to the event is blocked.

  If the guild to which the player belongs has already been entered in the event, the entry receiving unit 24 selects an entry cancelable screen 1000 as shown in FIG. 9 in step S62. The guild master can request cancellation of the entry within the entry period by pressing the “cancel entry” button 1001 on the entry cancellation possible screen 1000.

  If the guild to which the player belongs is not already entered in the event, the entry receiving unit 24 determines in step S63 whether the entry to the event is blocked. For example, the entry receiving unit 24 determines whether or not an entry to the event is blocked based on the event entry information of FIG. 19 stored in the event entry information storage unit 30.

  If the entry to the event is blocked, the entry receiving unit 24 selects the unblockable screen 1050 in FIG. 20 in step S64. FIG. 20 is an image diagram of an example of a screen that can be unblocked.

  The unblockable screen 1050 in FIG. 20 is provided with a “cancel entry block” button 1051. The guild master can request release of the entry block within the entry period by pressing the “release entry block” button 1051 on the unblockable screen 1050.

  In addition, when progressing to step S35 from step S64, the entry reception part 24 transmits the parameter for displaying the unblockable screen 1050 of FIG. 20 to the client terminal 2, and thereby the unblockable screen 1050 of FIG. 20 is displayed. It is displayed on the client terminal 2. The client terminal 2 can receive an entry block release request from the guild master from the unblockable screen 1050 of FIG. 20 and transmit the block release request to the entry reception unit 24 of the game server device 3.

  Upon receipt of the block release request, the entry receiving unit 24 changes the block flag of the event entry information shown in FIG. 19 from “ON” to “OFF” to release the entry block.

  Therefore, the guild master can unblock the entry from the unblockable screen 1050 of FIG. 20 displayed by the screen display unit 58 of the client terminal 2.

  On the other hand, if the entry to the event is not blocked, the entry receiving unit 24 selects the entry and blockable screen 1060 shown in FIG. 21 in step S65. FIG. 21 is an image diagram of an example of an entry and blockable screen.

  The entry / blockable screen 1060 shown in FIG. 21 is provided with an “entry” button 1061 and an “block entry” button 1062. The guild master can request an entry within the entry period by pressing an “entry” button 1061 on the entry and block available screen 1060. Further, the guild master can request a block of an entry within the entry period by pressing the “block entry” button 1062 on the entry / blockable screen 1060.

  When the process proceeds from step S65 to step S35, the entry receiving unit 24 transmits the parameters for displaying the entry and blockable screen 1060 to the client terminal 2, so that the entry and blockable screen 1060 in FIG. It is displayed on the terminal 2.

  The client terminal 2 can receive an entry request from the guild master from the entry and blockable screen 1060 of FIG. 21, and can transmit the entry request to the entry accepting unit 24 of the game server device 3.

  Further, the client terminal 2 can receive the entry block request from the guild master from the entry and blockable screen 1060 of FIG. 21 and can transmit the entry block request to the entry reception unit 24 of the game server device 3.

  Upon receiving the entry request, the entry receiving unit 24 changes the entry flag of the event entry information as shown in FIG. 19 to “ON” to enter the event.

  Further, the entry receiving unit 24 that has received the entry block request performs event entry blocking by changing the block flag of the event entry information as shown in FIG. 19 from “OFF” to “ON”.

  Therefore, the guild master can perform entry to an event and block entry from the entry and block enable screen 1060 of FIG. 21 displayed by the screen display unit 58 of the client terminal 2.

  FIG. 22 is a flowchart of an example of the guild member dedicated screen selection process in step S34. In step S71, the entry receiving unit 24 determines whether or not the event has been entered based on the event entry information in FIG.

  If the guild to which the player belongs has already been entered in the event, the entry receiving unit 24 selects the entry-completed screen 1040 in FIG. 17 in step S72. The guild member can confirm that the entry has been made from the entry completed screen 1040, but cannot request cancellation of the entry.

  If the guild to which the player belongs is not already entered in the event, the entry receiving unit 24 determines in step S73 whether the entry to the event is blocked.

  If the entry to the event is blocked, the entry receiving unit 24 selects the in-block screen 1070 in FIG. 23 in step S74. FIG. 23 is an image diagram of an example of the in-block screen.

  The in-block screen 1070 of FIG. 23 is provided with a message 1071 indicating that the guild master is blocking the entry. The entry receiving unit 24 can display the in-block screen 1070 of FIG. 23 on the client terminal 2 by transmitting a parameter for displaying the in-block screen 1070 to the client terminal 2.

  Therefore, the guild member can know from the in-block screen 1070 of FIG. 23 displayed by the screen display unit 58 of the client terminal 2 that the guild master is blocking entry to the event.

  On the other hand, if the entry to the event is not blocked, the entry receiving unit 24 selects the entry possible screen 1010 shown in FIG. 10 in step S75. The guild member can request entry by pressing the “entry” button 1011 on the entry possible screen 1010 so that the “guild member can also enter” period shown in FIG.

  Therefore, the guild member can enter the event from the entry possible screen 1010 of FIG. 10 displayed by the screen display unit 58 of the client terminal 2.

(Summary)
According to the information processing system 1 of the third embodiment, the guild master's intention not to enter the event can be reflected. This allows the guild master to choose whether or not to enter each event.

  For example, according to the information processing system 1 of the third embodiment, when a plurality of events are held at the same time, an event that the guild master enters and an event that does not enter can be selected. Therefore, by entering only a specific event, it is possible to reflect various intentions of the guild master, such as focusing on a specific event and aiming for a higher ranking in the event.

  The present invention is not limited to the specifically disclosed embodiments, and various modifications and changes can be made without departing from the scope of the claims. The guild of this embodiment is an example of a group to which one or more players belong. The guild master is an example of a first player who has special authority in the group. A guild member is an example of a second player other than the first player.

  The player information storage unit 32 and the guild information storage unit 34 are examples of first storage means. The event entry information storage unit 30 is an example of a second storage unit. The entry period is an example of a period during which an event participation request can be made. The entry receiving unit 24 is an example of a participation request receiving unit.

DESCRIPTION OF SYMBOLS 1 Information processing system 2 Client terminal 3 Game server apparatus 4 Network 10, 56 Communication part 12, 52 Control part 14, 54 Storage part 20 Game progress part 22 Event progress part 24 Entry reception part 30 Event entry information storage part 32 Player information storage Unit 34 guild information storage unit 50 operation receiving unit 58 screen display unit 66 operation content transmission unit 68 display control unit 501 input device 502 display device 503 external I / F
503a Recording medium 504 RAM
505 ROM
506 CPU
507 Communication I / F
508 HDD
1000 Entry cancelable screen 1010 Entry possible screen 1020, 1030 Entry impossible screen 1040 Entry completed screen 1050 Unblockable screen 1060 Entry and blockable screen 1070 Blocking screen B bus

Claims (8)

Computer
For each group to which one or more players belong, a first information for storing one or more first players who have special authority in the group and a second player other than the first player is stored. Storage means,
Second storage means for storing, for each group, information for determining whether or not a request to participate in an in-game event performed in units of groups has been received;
When a request to participate in the event is received only from a terminal device operated by the first player during a period in which the request to participate in the event can be made, and a request to participate in the event is received, the event is entered. Function as a participation request receiving means for updating information stored in the second storage means so that a request to participate in the event of the group to which the first player who made the participation request belongs has been received. Program to let you. The participation request receiving means divides a period during which a request to participate in the event can be made into a first period and a second period that comes after the first period has elapsed, A request for participation in the event is accepted only from a terminal device operated by the first player, and a request for participation in the event is received from at least the terminal device operated by the second player during the second period. The program according to claim 1. The second storage means stores, for each group, information for determining whether a request to participate in the event is prohibited from being accepted,
The participation request reception means belongs to the first player who has made a request for prohibiting participation in the event when receiving a request for prohibiting participation in the event from a terminal device operated by the first player. 3. The program according to claim 2, wherein the information stored in the second storage means is updated so that a request to participate in the event of the group is prohibited. The participation request accepting unit accepts a request for canceling participation in the event from a terminal device operated by the first player when a request for participation in the event has been received, and cancels participation in the event. 2. The information stored in the second storage means is updated so that a request to participate in the event of the group to which the first player who has made the request belongs is not accepted. The program according to any one of 3 to 3. When the participation request accepting unit has accepted the event participation request, the participation request accepting unit replaces a screen for accepting the event participation request from the terminal device operated by the second player, and participates in the event. 4. The program according to claim 2, wherein a screen including contents for which the request has been received is displayed. The participation request reception means receives a cancellation request for the participation prohibition request for the event from the terminal device operated by the first player when the request for participation in the event is prohibited. Updating the information stored in the second storage means so that a request to participate in the event of the group to which the first player who made the request to cancel the participation prohibition request belongs can be accepted. The program according to claim 3, wherein: The participation request receiving means replaces a screen for receiving a request for participation in the event from a terminal device operated by the second player when a request for participation in the event is prohibited. The program according to claim 3 or 6, wherein a screen including a content whose request is prohibited by the first player is displayed. An information processing system comprising: a terminal device operated by a player; and an information processing device that is communicably connected to the terminal device via a network,
For each group to which one or more players belong, a first information for storing one or more first players who have special authority in the group and a second player other than the first player is stored. Storage means,
Second storage means for storing, for each group, information for determining whether or not a request to participate in an in-game event performed in units of groups has been received;
When a request to participate in the event is received only from the terminal device operated by the first player and a request to participate in the event is received during a period in which the request to participate in the event can be performed, the event Participation request receiving means for updating the information stored in the second storage means so that the request to participate in the event of the group to which the first player who made the participation request belongs has been received. ,
An information processing system comprising:

Images