JP2023041928A - Game system, computer program used therefor, and server device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a game system capable of limiting sharing of an event set by one user with other users.

SOLUTION: A game system 1 provides a quiz game that permits setting of a private event PE by one user U of a plurality of users. When sharing of the private event PE with another user of the plurality of users, in other words, changing of the private event PE into an official event, is permitted on the basis of a permission condition, the game system 1 issues an authentication code indicating the permission of the sharing (turning into the official event), and acquires log information required for sharing the private event PE with the another user as the official event OE on condition that the permission information is issued.

SELECTED DRAWING: Figure 4

COPYRIGHT: (C)2023,JPO&INPIT

Description

There is an application for the application of Article 30, Paragraph 2 of the Patent Act. Disclosure through telecommunication lines Website publication date March 15, 2017 Website address https://www. youtube. com/watch? v=_rOcM7wnc-A&t=1940s2. Disclosure through telecommunication lines Date of website publication May 17, 2017 Website address https://www. youtube. com/watch? v=v_bmDqfA7o43. Disclosure through Telecommunications Line Date of website publication May 26, 2017 Website address http://eam. 573. jp/app/web/post/ and https://twitter. com/QMA_staff

The present invention relates to a game system or the like that provides a game that allows one of a plurality of users to set an event.

There are game systems that provide games that allow setting of events by one of a plurality of users. As such a game, there is known a system that provides a game in which an event corresponding to an option selected by the user is set (see Patent Document 1, for example).

JP 2017-113175 A

In the system of Patent Literature 1, since an event is set through options prepared in advance, there is no concept of determining whether the event is permitted or not permitted. On the other hand, depending on the type of event, it may be defined by the holding period or place (target). In some cases, such an event period or the like may be arbitrarily set by the user. In such a case, it may not be possible to unconditionally accept the user's settings, such as when the event periods and venues overlap.

SUMMARY OF THE INVENTION Accordingly, it is an object of the present invention to provide a game system or the like capable of restricting sharing of an event set by one user with other users.

A game system of the present invention is a game system that provides a game that allows setting of an event by one user out of a plurality of users, wherein sharing of the event with other users out of the plurality of users is information issuing means for issuing permission information indicating permission for sharing when permission is granted based on permission conditions; an information acquiring means for acquiring play information relating to the play status of the event.

On the other hand, a computer program of the present invention is configured to cause a computer connected to an input device and an output device used for playing the game to function as each means of the game system described above. Also, the server device of the present invention is connected via a network to the input device and output device used to play the game, and functions as each means of the game system described above.

1 is a diagram showing a schematic configuration of a game system according to one embodiment of the present invention; FIG. FIG. 3 is a functional block diagram showing the essential parts of the control system of the game system; Explanatory diagram for explaining the game range of the quiz game. Explanatory drawing for demonstrating the outline|summary of an example of an event service. The figure which shows an example of a structure of permission data. The figure which shows an example of a structure of official event data. The figure which shows an example of a structure of private event data. 4 is a flowchart showing an example of the procedure of permission issuing processing; 4 is a flowchart showing an example of an event processing procedure; 4 is a flowchart showing an example of the procedure of log acquisition processing;

An example of a game system according to one embodiment of the present invention will be described below. First, referring to FIG. 1, the overall configuration of a game system according to one embodiment of the present invention will be described. A game system 1 includes a center server 2 as a server device, and a plurality of game machines 3 and a plurality of user terminal devices 4 as client devices connectable to the center server 2 via a predetermined network 5 . The center server 2 is configured as one logical server device by combining server units 2A, 2B, . . . as a plurality of computer devices. However, the center server 2 may be composed of a single server unit. Alternatively, the center server 2 may be logically configured using cloud computing.

The game machine 3 is configured as a commercial (business) game machine that allows a user to play a game within a range corresponding to the play fee in exchange for payment of a predetermined play fee. This type of game machine 3 is sometimes called an arcade game machine. The game machine 3 is a computer device installed in a predetermined facility such as a store 6 for the main purpose of making a large number of users repeatedly play the game to make a profit. The game machine 3 is configured as a game machine for playing a so-called quiz game in which answers are entered for questions. Note that the game machine 3 is not limited to the quiz game, and may appropriately provide various games.

The user terminal device 4 is a computer device that can be connected to a network and is used for personal use by the user. For example, a stationary or book-type personal computer (hereinafter referred to as PC) 4a or a mobile terminal device 4b such as a mobile phone (including a smart phone) is used as the user terminal device 4. FIG. In addition, various computer devices such as stationary home game machines, portable game machines, portable tablet terminals, etc., which can be connected to a network and are used for personal use by users, are used as the user terminal device 4. you can The user terminal device 4 can allow users to enjoy various services provided by the center server 2 by installing various computer software.

The network 5 may be configured appropriately as long as the game machine 3 and the user terminal device 4 can be connected to the center server 2 . As an example, the network 5 is configured to implement network communications using the TCP/IP protocol. Typically, the Internet 5A as a WAN and LANs 5B and 5C connecting the center server 2 and the game machine 3 to the Internet 5A are connected via a router 5D. The user terminal device 4 is also connected to the Internet 5A with an appropriate configuration. A local server may be installed between the game machine 3 and the router 5D of the store 6, and the game machine 3 may be communicably connected to the center server 2 via the local server. The server units 2A, 2B, .

The center server 2 provides various game machine services to the game machines 3 or their users. Game machine services include event services for setting official events in quiz games. Specifically, when the event service includes an event service for the game machine 3 provided to the game machine 3 and an event service for the user terminal device 4 provided to the user terminal device 4, the game machine service contains an event service for game machine 3. Details of the event service will be described later.

Note that the game machine service may include a service for receiving user identification information from the game machine 3 and authenticating the user. Further, the service may include a service of receiving play data of the authenticated user from the game machine 3 and storing it, or providing the game machine 3 with the play data to be stored. Furthermore, the game machine service includes a service for distributing and updating programs or data for the game machine 3 via the network 5, and matching users when a plurality of users play a common game via the network 5. It may include a matching service, a billing service for collecting fees from users, or the like.

Similarly, the center server 2 provides various web services to users of the user terminal devices 4 via the network 5 . The web service includes an event service for the user terminal device 4 if the event service includes an event service for the user terminal device 4 . The Web service includes a game information service that provides various information related to the game provided by the game machine 3, a distribution service that distributes various data or software (including updates of data, etc.) to each user terminal device 4, It may include services such as a community service that provides a place for interaction such as information transmission, exchange, and sharing by users, and a service that assigns a user ID for identifying each user.

Next, the main part of the control system of the game system 1 will be described with reference to FIG. First, the center server 2 is provided with a game service management section 21 and a storage section 23 as data storage means. The game service management unit 21 is a logical device realized by combining computer hardware of the center server 2 (including a CPU and a memory as an internal storage device required for its operation) and software. The storage unit 23 is an external storage device implemented by a storage unit including a nonvolatile storage medium (computer-readable storage medium) such as a hard disk array. The storage unit 23 may be configured to hold all data in one storage unit, or may be configured to store data in a distributed manner in a plurality of storage units. A computer program PG1 as software for causing the computer hardware resources of the center server 2 to function as the game service management section 21 is recorded in the storage section 23 . Various types of data are also recorded in the storage unit 23. In FIG. 2, permission data 51 and official event data ED1 are shown. Details of the permission data 51 and the official event data ED1 will be described later.

The game service management unit 21 provides the game machine service described above to the game machine 3 . The game service management unit 21 is further provided with an event providing unit 24 as a logical device. The event providing unit 24 provides various processes for realizing event services. Such various types of processing include processing that should be performed on the server side among event processing for managing official events. In addition, the event providing unit 24 also executes log acquisition processing for managing official events and permission issuing processing for adding new official events as such various types of processing. Procedures for event processing, log acquisition processing, and permission issuing processing will be described later.

Next, the game machine 3 is provided with a game control section 31 and a storage section 32 as storage means. The game control unit 31 is a logical device realized by a combination of hardware of the game machine 3 (including a CPU and a memory as its internal storage device) and a computer program PG2 as software. The game control unit 31 executes various kinds of arithmetic control necessary for the progress of the game, and also executes various processes necessary for enjoying the game machine services provided by the game service management unit 21 of the center server 2. . The game control unit 31 is provided with a game providing unit 33 as a further logical device. The game providing unit 33 cooperates with the event providing unit 24 of the center server 2 to perform processing necessary for realizing various events.

The storage unit 32 is an external storage device implemented by a storage unit including a nonvolatile storage medium (computer-readable storage medium) such as a hard disk or a semiconductor storage device. Various data are recorded in the storage unit 32 together with the program PG2 described above, and event data ED is shown in FIG. The event data ED is data for managing various events set in the quiz game. The event data ED includes official event data ED1 provided by the center server 2 and private event data ED2. Details of the private event data ED2 will be described later together with the official event data ED1.

Note that the storage unit 32 also records other game data. The game data includes various data necessary for making the user play a predetermined quiz game according to the program PG2. Specifically, the game data includes various data such as quizzes to be presented to the user and quiz data for managing answers to the quizzes. Also, the game data may include the play data described above. The play data is data for handing over the play results (past achievements) up to the previous time to the next and subsequent times, or data for handing over the setting contents unique to each user. However, illustration of these is omitted.

The game machine 3 is provided with various input/output devices such as an input device 36 for outputting signals corresponding to user operations, a display device 37 and a card reader 38 as output devices for presenting game screens and the like to the user. . The card reader 38 is a device for reading a unique card ID recorded on the card 39 held by the user. The card 39 may be used for user authentication, fee collection, and the like.

Next, the details of the quiz game event and event service will be described. FIG. 3 is an explanatory diagram for explaining the game range of the quiz game. As shown in FIG. 3, the game range of the quiz game includes normal play mode and event mode. The normal play mode is a mode in which the quiz game is played normally. On the other hand, the event mode is a mode that provides various events. Here, an event means a competition (competition) in which a plurality of users participate and compete for the results of a quiz game. Events may allow participation by groups of users as well as individual users. It should be noted that events are not limited to competitions, and include various events (occasions ).

The event mode includes official event OE and private event PE. The private event PE is an event appropriately set by the user of each game machine 3, the operator of the store 6, or the like. The private event PE may be shared not only by the user (which may include the manager of the store 6) who set it, but also by other users among a plurality of users who use the game system 1. It may be provided only to the user. Each user terminal device 4 or each game machine 3 may be used to set the private event PE. In addition, a privilege given by each user or operator (for example, a physical privilege such as a figure, or a complimentary ticket at the store 6, etc.) may be set in the private event PE.

On the other hand, the official event OE is an event shared by multiple users playing the quiz game. In the official event OE, the play status is managed by the operator of the center server 2 (hereinafter sometimes referred to as the server administrator). As a result, in official events OE, there are many cases in which the server administrator ranks the play situations, and gives predetermined benefits according to the results. Also, as such a predetermined privilege, a privilege used in a quiz game (for example, an item for a quiz game, etc.) is often given. The official event OE includes a qualifying event OE1 as a privilege event and a main event OE2 as a special event. The main battle event OE2 is a special event in which participation is permitted when participation conditions are satisfied. Participation conditions include achievements in qualifying event OE1. Specifically, the participation condition is that the points (which may vary depending on the value of the prize) given to the winners of the preliminary event (winner, runner-up, special prize, etc.) are equal to or greater than a predetermined value. may be satisfied if Also, such points may be awarded through a plurality of qualifying events OE1 (hereinafter sometimes referred to as a series of qualifying events OE1). In the qualifying event OE1, participation in the main event OE2 may be used as a predetermined privilege through such points.

The event service includes a formalization service for formalizing the private event PE. The formalization service also includes a service for registering private event PE as qualifying event OE1. In other words, the event service includes a service for turning the private event PE into a qualifying event. Then, the private event PE may function as the qualifying event OE1 through such a service. In such a case, even if it is a private event PE, the points required for participation conditions are awarded. In other words, such a private event PE is inevitably shared not only by the user U who set it, but also by other users who use the game machine 3 of the A store 6 .

FIG. 4 is an explanatory diagram for explaining an outline of an example of an event service when functioning as a service for turning a private event PE into a qualifying event. The example of FIG. 4 shows a case where a private event PE called "A store tournament" set by a user U of A store 6 is turned into a qualifying event (official event) (functions as a qualifying event OE1). In this case, as shown in FIG. 4, the event service includes an application process and a formalization process. Also, in this case, the user U functions as one user of the present invention, and the other user who plays the private event PE functions as another user of the present invention.

The application process is a process for applying to the center server 2 (or the server administrator) for private event PEs to be made into qualifying events. In the application process, the user U first transmits information about the "A store tournament" to the center server 2 via the user terminal device 4 (step S1). This holding information includes the tournament name (event name), tournament grade (event level), tournament date and time (may be held period), number of participants, competition format (for example, tournament or league), and venue (A store 6 , or each game machine 3 of store A 6, etc.). Such transmission may also be accomplished through a dedicated website (not shown) for entering event information. In this case, such transmission functions as at least part of an event service for user terminal 4 . It should be noted that the application may be carried out through paperwork. Also, transmission (application) of event information may be executed through the game machine 3 . In this case, the game machine 3 may provide a dedicated application screen (not shown) instead of the dedicated website. Also, the holding information may be different from or common to the information necessary for setting the private event PE.

After sending the event information, if the event information satisfies the permission conditions, the center server 2 (or the server administrator may be) sends the application information to the operator of the store 6, that is, the store A 6 in the application process. It is transmitted (step S2). When the operator of store A 6 acquires the application information, it determines whether or not to approve the private event PE as an official event based on the application information, and sends the determination result (approval result) to the center server 2 (or server administrator) (step S3). These transmissions may be performed through a dedicated website or through the game machine 3 in the same manner as the application. Alternatively, when the center server 2 or various devices such as the game machine 3 manage the mail address of the manager of the center server 2 or the store A 6, it may be executed through mail.

After obtaining the approval result from the A store 6, the center server 2 (or the server administrator may be sufficient) transmits the approval result to the user U (applicant) in the application process (step S4). This transmission is through the transmission of permission information that permits the private event PE to be applied for as a qualifying event if it is approved for official event conversion, and if it is not approved (rejected), it is not permitted. Each is executed through the transmission of the information indicated. Specifically, when the official event is approved, the center server 2 issues an authentication code indicating permission for the qualifying event as permission information, and transmits the authentication code to the user terminal device 4 . Issuance of the authentication code is performed based on the authorization data 51 that uniquely manages the authentication code and associates the event information. Also, the authentication code may be sent via a dedicated website, or may be sent via e-mail if the event information includes the e-mail address of the user U (applicant). Such transmission functions as at least part of an event service for the user terminal 4 when implemented through a dedicated website or e-mail.

Note that the transmission of permission (permission information such as an authentication code) may be realized by mailing documents. Also, the permission conditions may include the approval of the operator of store A 6 as a requirement. That is, the permission condition may be satisfied when approved by the operator of store A 6 . In this case, the permission conditions include the first requirement based on the related information and the second requirement based on the approval result, the procedure of step S2 is executed when the first requirement is met, and the step The procedure of S4 may be performed.

On the other hand, the formalization process is a process for actually setting the private event PE permitted to be made into a qualifying event as a qualifying event OE1. The formalization process identifies the game machine 3 that actually provides the qualifying event OE1 that has changed from the private event PE, such that the private event PE actually functions as the qualifying event OE1, and assigns the private event PE to the game machine 3. Executed to provide the information needed to make a preliminary event. Specifically, in the formalization process, the authentication code (authorization information) is first input into the game machine 3 by the user U (who may be the operator of store A 6) who has received the authentication code (step S5). That is, the user U provides the authentication code to the game machine 3 . When acquiring the authentication code, the game machine 3 transmits it to the center server 2 (step S6).

On the other hand, when the center server 2 acquires the authentication code from the game machine 3, it transmits to the game machine 3 the information necessary for actually turning the private event PE into a qualifying event (official event) (step S7). Specifically, the center server 2 first refers to the permission data 51 and acquires information about the private event PE related to the authentication code acquired from the game machine 3 . After that, the center server 2 adds the qualifying event OE1 corresponding to the acquired holding information to the official event data ED1. Then, the center server 2 transmits the added official event data ED1 to the game machine 3 (the game machine 3 that has transmitted the authentication code) as information necessary for turning the private event PE into a qualifying event (official event). If the private event PE is made into a qualifying event as a part of the series of qualifying events OE1, it may be associated with the series of qualifying events OE1 through the official event data ED1. That is, in step S7, the center server 2 generates the official event data ED1 so that the private event PE to be applied for functions as a series of qualifying events OE1, and transmits such official event data ED1 to the game machine 3. good. In addition, information for functioning as a series of qualifying events OE1 (information designating a series of qualifying events OE1, etc.) may be included in the holding information. Alternatively, the private event PE may be automatically sorted into a series of qualifying events OE1 based on various information such as holding period, scale, location, etc., and the result may function as such information.

After obtaining the official event data ED1 from the center server 2, the game machine 3 displays the official event OE included in the event mode based on the obtained official event data ED1 (step S8). This official event data ED1 officially includes the private event PE, which has been requested to be converted into a qualifying event, as an official event OE. Therefore, the official event OE is displayed so as to include the qualifying event OE1 called "A store competition". As a result, "A Store Tournament" is selected and functions as an official event OE. In other words, the "A store tournament" is actually provided as the qualifying event OE1 (made into a qualifying event).

Note that the game machine 3 may update the content of the private event data ED2 as the official event data ED1 is acquired. Specifically, the game machine 3 changes the contents of the private event data ED2 so as to delete the private event PE corresponding to the "A shop tournament" based on the user's deletion instruction or information included in the official event data ED1. may be updated. In this case, "A Store Tournament" disappears from the display of the private event PE as it becomes an official event. In other words, as if it had been moved from the private event PE to the official event OE, "A store tournament" is deleted from the target of the private event PE. In addition, various rewards (privileges) may be provided to the person who set up the private event PE or the applicant who applied for the private event PE to become an official event, in order to promote such setting. Such remuneration may be given at an appropriate time, such as at the time of setting (or at the time of application), at the time of holding, or at the time of permission.

Furthermore, when the official event OE is held, the game machine 3 provides the log (various achievements) of the official event to the center server 2 (step S9). The log information is information necessary for realizing the official event OE. Specifically, the log information includes information on the play status of the official event OE (for example, the number of points earned for the main event OE2, etc.). Then, the center server 2 manages the results of the official event OE based on the log information, and provides (shares with each user) the information on the play results to each user terminal device 4 as part of the web service. you can If the private event PE is made into an official event, this log also contains the log information of that private event PE. In other words, the center server 2 may manage or provide the results so as to include the play status of the private event PE that has been turned into a qualifying event. Specifically, the center server 2 sets a ranking for each user based on the overall play status (for example, point award status) of a series of qualifying events OE1 including such a private event PE, Whether or not to participate in the main battle event OE2 may be determined according to the ranking result. In such a case, this log information functions as play information of the present invention. Also, the procedure of steps S6 to S7 and S9 of the formalization process functions as an event service for the game machine. As an example, an event service is provided in this way.

Note that each user may participate in only part of the series of qualifying events OE1. In this case, the overall ranking of the series of qualifying events OE1 may be determined based on some of the achievements, and it may be determined whether or not to participate in the main event OE2. Also, when the event service is used by the operator of the shop 6, steps S1 and S4 may be executed for the shop 6 (the game machine 3 or the user terminal device 4 for the operator, etc.). In this case, the procedures of steps S2 and S3 may be omitted. Also, when setting a private event, if ID information for identifying a setter such as a user ID for identifying each user or an operator ID for identifying an operator of each store 6 is requested, such ID information may be used. Applicants for official events or non-applicants for official events may be determined based on this. Specifically, for example, if the setter of the private event is the manager of the store 6 or a specific user certified by the server administrator based on the degree of reliability, etc., the private event is automatically set based on the ID information. It may be determined as an official event application subject, and an official event may be promoted according to the procedure of the event service. On the other hand, setting up a private event and formalizing it (providing event services) may be performed simultaneously. That is, setting up a private event may be performed as part of the event service, for example through a dedicated website. In such a case, the type of event to be set (for example, private event or official event) may be specified in the event service. Alternatively, all private events may be subject to an application process or the like so that they are all official events. In other words, an event that is actually executed as a private event does not have to exist. Furthermore, other information other than the log information may be used to determine the official event OE play results such as rankings. Specifically, the manager of the store 6 transmits additional information (for example, information on actual winning results) regarding the play status of the event to the server manager, and the play result is determined with this additional information taken into consideration. good too. Such additional information is, for example, when the log information alone cannot identify achievements (for example, winning results), in other words, when the event information does not include battle format information, or when the placement of each user in a tournament, etc., the center server 2 This may be used in cases such as when does not manage detailed information on the battle format.

Next, details of the permission data 51, the official event data ED1, and the private event data ED2 will be described. The permission data 51 is data for uniquely managing permission information. Specifically, the permission data 51 is a set of records uniquely describing permission information. FIG. 5 is a diagram showing an example of the configuration of permission data 51. As shown in FIG. As shown in FIG. 5, the permission data 51 includes a permission record 51R that associates unique permission information with the corresponding private event PE for each private event PE. The permission record 51R includes information of "permission", "event ID", and "details".

“Permission” is permission information indicating permission to make an official event. Specifically, information indicating an authentication code as permission information is described in "permission". A unique number having a predetermined number of digits may be described as information indicating such an authentication code. "Event ID" is information indicating a unique event ID for each official event to identify each official event. "Details" is information indicating the details of the official event corresponding to the "event ID". In "details", the aforementioned event information (information provided at the time of application) may be described as information indicating the details of the official event. These pieces of information are associated with each other and recorded in the permission record 51R.

The official event data ED1 is data for managing each official event OE of the quiz game. The official event data ED1 is a set of records defining each official event OE. FIG. 6 is a diagram showing an example of the structure of official event data ED1. As shown in FIG. 6, the official event data ED1 includes official event records RS1 that associate each official event OE with its details. The official event record RS1 includes information of "event ID", "details", "approval range", and "type". “Event ID” and “details” are information similar to the permission data 51 .

On the other hand, the "approval range" is information indicating the range of approval for official events. Specifically, in the "approval range", a cabinet ID (a unique ID for each game machine 3 to identify each game machine 3) indicating a game machine 3 that has been permitted to become an official event through the transmission of permission information. information is described (if permitted for each store 6, store ID information for identifying each store 6 may be described). In the case of the official event OE set by the server administrator of the center server 2 (which is provided as the official event OE from the beginning), the same information as the venue information included in the "details" information is Scope”, or the information on the “Approval Scope” may be omitted. "Type" is information indicating the type of official event corresponding to the "event ID". Information indicating the main event OE2, the qualifying event OE1, or the private event PE (formulated from the private event PE) may be used as the “type” information. “Relationship” is information indicating the relation of each event. "Relationship" includes information that associates each qualifying event OE1 functioning as a series of qualifying events OE1 (including a private event PE converted into a qualifying event) with each other (for example, a unique ID or number for each series of qualifying events OE1). may be described. These pieces of information are recorded in the official event record RS1 in association with each other. In addition, when the corresponding private event PE is deleted from the private event data ED2 as the event becomes an official event, the official event data ED1 stores the information of the "private ID" described later in order to identify such a private event PE. may contain. Further, the event information included in the "details" functions as the event information of the present invention, and the information on the cabinet ID included in the "approval range" functions as the game identification information of the present invention. By including these, the official event data ED1 functions as the event data of the present invention.

The private event data ED2 is data for managing the private event PE of the quiz game. The private event data ED2 is a set of records defining each private event PE. FIG. 7 is a diagram showing an example of the configuration of private event data ED2. As shown in FIG. 7, private event data ED2 includes private event records RS2 that associate each private event PE with its details. The private event record RS2 includes information of "private ID" and "details". "Details" is the same information as the official event data ED1. "Private ID" is information indicating a unique private ID for each private event PE to identify each private event PE. These pieces of information are recorded in the private event record RS2 in association with each other.

Note that the official event record RS1 including the “type” information indicating the private event PE may function as the private event record RS2. That is, the private event data ED2 may function as part of the official event data ED1. In this case, event ID information may be described in the “private ID”. That is, as the information of "event ID" (or "private ID"), information of event ID that uniquely manages all events so as to identify not only each private event PE but also each official event OE may be used. Also, the private event data ED2 may be managed by the center server 2 in the same manner as the official event data ED1. Furthermore, these private event data ED2 and official event data ED1 may not be provided to the game machine 3. In other words, the center server 2 centrally manages the private event PE and the official event OE, and the game machine 3 does not have to recognize them. In this case, the official event OE etc. is notified through e-mail, website, etc., not through the game machine 3, and the center server 2 goes to the game machine 3 to obtain the log information corresponding to the holding period etc. OE, etc. may be implemented.

Next, with reference to FIGS. 8 to 10, procedures of permission issuing processing, event processing, and log acquisition processing executed by the event providing unit 24 or the game providing unit 33 will be described. Permission issuance processing is processing for issuing permission information based on an application for turning the private event PE into an official event. When the event information to be applied for is acquired (or at a predetermined interval after acquisition), the event providing unit 24 starts the permission issuing process of FIG. is satisfied (step S101). Even if the permission conditions are satisfied when the holding conditions of the private event PE meet the predetermined conditions (for example, when all items are properly entered, or when there is a predetermined participation scale, participation period, etc.) Alternatively, it may be satisfied when an operation indicating permission is performed on the private event PE by the operator based on the event information. In addition, when the permission conditions include the first condition and the second condition, the first condition is satisfied based on such holding conditions, and the second condition is satisfied when the store 6 approves the official event. you can Then, the permission condition may be satisfied when both the first condition and the second condition are satisfied. Based on these, if the private event PE does not satisfy the permission conditions, the event providing unit 24 skips subsequent processing and ends the current processing.

On the other hand, if the private event PE satisfies the permission conditions, the event provision unit 24 issues permission information to the private event PE that satisfies the permission conditions (step S102). More specifically, the event providing unit 24 newly issues a unique authentication code as permission information to the private event PE while referring to the permission data 51 . Subsequently, the event providing unit 24 transmits the issued permission information (for example, the newly issued authentication code) to the applicant (step S103). This transmission may be performed through E-MAIL (eg, which may be included in the event information) or through a dedicated website (eg, notification by posting on a dedicated website). After transmitting the permission information, the event providing unit 24 terminates the current process. As a result, it is determined whether or not to make the official event based on the permission conditions, and when the official event is permitted, permission information indicating the permission is issued and sent to the applicant. More specifically, steps S1 and S4 in the application process in the example of FIG. 4 are implemented.

The event processing is processing for providing a private event PE permitted to be made into an official event as an official event OE. More specifically, a private event PE permitted to be made into an official event is managed as an official event OE through event processing. The left side of the example in FIG. 9 shows the processing of the game providing unit 33 of the game machine 3, and the right side shows the processing of the event providing unit 24 of the center server 2, respectively.

When the approval operation is executed to approve the actual provision of the private event PE permitted to be made into an official event as the official event OE, the game providing unit 33 starts the event processing of FIG. 9, and first acquires permission information. (step S201). More specifically, the game providing unit 33 acquires the authentication code information corresponding to the private event PE as the permission information. The information of the authentication code may be acquired from the input result when the operation of inputting the authentication code is included in the approval operation. Alternatively, if the authentication code information (permission information) is provided directly to the game machine 3, such as when the application is executed through the game machine 3, the information of the authentication code is the provision result (acquisition result). may be obtained from Subsequently, the game providing unit 33 transmits the acquired permission information to the center server 2 (step S202).

When the event provision unit 24 of the center server 2 acquires the permission information, it starts the event processing of FIG. 9, and first updates the data so as to reflect the acquired permission information (step S301). Specifically, the event providing unit 24 updates the official event data ED1 so as to add the official event record RS1 corresponding to the acquired permission information. This addition provides the same quiz game of the store 6 when the target of the official event OE is the unit of the store 6 (that is, the permission information is sent from the game machine 3 of one of the stores 6). It may be executed in all game machines 3) or may be executed in units of each game machine 3). Further, the event providing unit 24 may implement this addition by acquiring event information while referring to the permission data 51 based on the permission information. Further, by including "associated" information in the official event data ED1, such additions may serve as associations for functioning as a series of qualifying events OE1. In other words, in step S301, the event providing unit 24 adds the official event record RS1 including the information of "related" based on the specified information, thereby setting the relation to the private event PE so as to function as a series of qualifying events OE1. you can Subsequently, the event providing unit 24 transmits the updated data to the game machine 3 (step S302). Specifically, the event providing unit 24 transmits to the game machine 3 the latest official event data ED1 including the official event record RS1 corresponding to the acquired permission information. After transmitting the latest official event data ED1 to the game machine 3, the event providing unit 24 ends the current process.

On the other hand, when acquiring the latest official event data ED1, the game providing unit 33 of the game machine 3 updates the data (step S203). Specifically, the game providing unit 33 updates the official event data ED1 so as to replace the existing official event data ED1 with the acquired latest official event data ED1. In addition, when the corresponding private event PE is deleted from the private event data ED2 as the event becomes an official event, the game providing unit 33 updates the official event data ED1 and deletes the corresponding private event PE from the private event data. ED2 may be updated. Alternatively, if the private event data ED2 is managed by the center server 2, such deletion may be updated and transmitted by the center server 2 together with the update and transmission of the official event data ED1. In step S203, the game providing unit 33 may update the private event data ED2 as well as the official event data ED1. The game providing unit 33 ends the current process after updating the data in step S203. As a result, the private event PE permitted to be made into an official event is actually managed and provided as an official event OE. Also, when associated with another qualifying event OE1, such private event PE is provided as one of a series of qualifying events OE1. More specifically, a formulation process corresponding to steps S6-S8 in the example of FIG. 4 is implemented.

On the other hand, the log acquisition process is a process for managing log information of the official event OE. The example of FIG. 10 shows a case where the results of the official event OE are shared by each user terminal device 4 based on the log information. Also, the example of FIG. 10 shows a case where the center server 2 side acquires logs (detailed information on event achievements such as play results) from each game machine 3 of a store 6 that holds an official event OE at a predetermined cycle. ing. The log may be transmitted from the game machine 3 side to the center server 2 at an appropriate time after the end of the event. In this case, steps S401 and S402 in the example of FIG. 10 may be omitted.

At a predetermined cycle, the event providing unit 24 starts the log acquisition process of FIG. 10, and first acquires the official event data ED1 (step S401). Subsequently, the event providing unit 24 identifies targets for which log information is to be obtained (step S402). Specifically, the event providing unit 24 identifies each game machine 3 that actually holds the official event OE based on the information of the "approval range" (or the venue included in the "details") of the official event data ED1. . Next, the event providing unit 24 acquires a log regarding the corresponding official event OE from each specified game machine 3 (step S403). Further, when acquiring the log information from each game machine 3, the event providing unit 24 generates related information related to each official event OE (step S404). Related information is information that should be shared with each user through the Web service as information about each official event OE (for example, the ranking of winners, the number of points earned by each participant, etc.). In addition, in the case of a series of qualifying events OE1, the related information may include information on the play status such as the prize winning status of the whole event. That is, in step S403, the event providing unit 24 may generate the ranking of each user in each official event OE, or generate the ranking of each user in the entire series of qualifying events OE1. Then, the event providing unit 24 provides each user with the created related information as a part of the Web service, and ends the current process. As a result, logs related to official events are acquired by the center server 2 and shared with each user as part of the web service. In addition, in the case of an official event OE changed from a private event PE, such acquisition is limited to the game machine 3 that has permitted the event (provided the authentication code). More specifically, a formulation step corresponding to step S9 in the example of FIG. 4 is implemented.

As explained above, according to this form, the private event PE can be turned into an official event through the event service. Specifically, the center server 2 acquires the log information necessary for sharing the play status of the private event PE as the official event OE on the condition that permission information (authentication code) is issued based on the permission conditions. This makes it possible to limit the acquisition of log information necessary for sharing a private event PE to when permission information is issued, that is, when formalization of the private event PE is permitted. In other words, for example, the permission information for sharing the play status of the private event PE with other users, such as the result of giving points for functioning as the qualifying event OE1, in other words, the case where the private event PE actually functions as the official event OE is issued.

Furthermore, when such a private event PE is applied for by a user who plays the game, the store 6 functioning as the venue for the private event PE is given an opportunity of approval. The official event data ED1 (including the official event record RS1 corresponding to such a private event PE) for making the private event PE function as the official event OE is provided to the game machine 3 that actually obtained the permission information. is limited to Also, if such official event data ED1 does not exist, the private event PE is neither displayed nor provided as the official event OE. That is, after providing such official event data ED1, the private event PE is actually provided as the official event OE, and log information is also obtained. As a result, depending on whether or not the permission information is used (for example, whether or not it is actually transmitted to the center server 2 via the game machine 3), the operator of the shop 6 that holds the private event PE actually receives the private event. An opportunity to determine whether or not to provide the event PE as an official event OE can be given. In other words, the cases where the private event PE actually functions as the official event OE can be further restricted to cases where the manager of the shop 6 approves. As a result, it is possible to restrict inappropriate private event PEs from becoming official events, for example, when the event period overlaps with another official event OE, or when the event scale (number of participants or period) is not sufficient.

In addition, through such an event service, a private event PE made into a qualifying event is set as part of a series of qualifying events OE1. Specifically, based on the holding information of such a private event PE, a series of qualifying events OE1 including the private event PE are associated, and each user is ranked in the entire series of qualifying events OE1. In other words, not only the preliminarily prepared qualifying event OE1 but also the private event PE that is set after the event is provided as a series of qualifying events OE1 to be ranked. Thereby, a series of qualifying events OE1 including such a private event PE can be set after the fact. More specifically, for example, after a series of qualifying events OE1 has been established, a new series of qualifying events separate from it may be created, or after an existing series of qualifying events OE1 has been established. A series of qualifying events OE1 can be set up including such a private event PE such that event OE1 is added. As a result, compared to the case where such a private event PE is realized by operation, that is, the case where the play situation is tallied by operation, the operator of the shop 6 and the server administrator can save time and effort. Furthermore, even if the private event PE is set with a high degree of freedom, a series of qualifying events OE1 including such a private event PE can be set after the fact. That is, a private event PE arbitrarily defined by the user can be allowed to be added to the series of qualifying events OE1.

Furthermore, since the private event PE can function as the official event OE through such an event service, more official event OE can be provided than when such a private event PE is not provided. More specifically, for example, more qualifying events OE1 can be provided through such private events PE. As a result, the achievements of the private event PE can be used as part of the conditions for participating in the main event OE2, so compared to the case where such a private event PE is not provided, the main battle event based on more achievements It is possible to determine whether or not to participate in OE2. As a result, it is possible to more appropriately determine whether or not to participate. Also, it is possible to improve the attractiveness of the private event PE. Furthermore, when such information related to the private event PE is shared with other users through a web service, the play status (results) of the private event PE, such as rankings and points awarded, can be shared with each user terminal device. 4 can be shared with other users. This makes it possible to increase the user's interest in the private event PE.

In the above embodiment, the event providing unit 24 of the center server 2 functions as an example of information issuing means of the present invention by executing step S102 of the routine of FIG. Further, the event providing unit 24 of the center server 2 functions as an example of the information obtaining means and related information providing means of the present invention by executing the routine of FIG. More specifically, the event providing unit 24 functions as an example of information acquisition means by executing step S403 of FIG. 9, and as an example of related information providing means by executing step S405. Also, the event providing unit 24 of the center server 2 functions as an example of event information providing means and data updating means of the present invention by executing the routine of FIG. More specifically, the event providing unit 24 functions as an example of event information providing means by executing step S302 of FIG. 9, and functions as an example of data updating means by executing step S301. On the other hand, the storage unit 23 of the center server 2 stores the official event data ED1, thereby functioning as data storage means of the present invention.

The present invention is not limited to the forms described above, and may be implemented in forms with appropriate modifications or changes. For example, in the above embodiment, the game machine 3 is configured as an arcade game machine. However, the game machine 3 is not limited to a game machine configured as an arcade game machine. The user terminal device 4 or the like may function as the game machine 3 . Also, the game machine 3 may be configured as a game machine that virtually operates on a server such as the center server 2 while using the user terminal device 4 or the like as a remote input/output device. On the other hand, the game machine 3 may function as the center server 2 . That is, the game machine 3 may perform all or part of the roles (various processes, etc.) of the center server 2 in the above-described mode. Alternatively, the center server 2 may be omitted and the game machine 3 may function as the game system 1 .

Various aspects of the present invention derived from each of the embodiments and modifications described above are described below. In the following description, in order to facilitate understanding of each aspect of the present invention, corresponding members illustrated in the accompanying drawings are added in parentheses, but the present invention is thereby limited to the illustrated form. not a thing

The game system (1) of the present invention is a game system that provides a game that allows one user (U) among a plurality of users to set an event, wherein the plurality of users information issuing means (24) for issuing permission information indicating permission for sharing when sharing of the event with another user of is permitted based on permission conditions; and information acquiring means (24) for acquiring play information relating to the play status of the event necessary for sharing the event with the other users.

According to the present invention, play information necessary for sharing the play status of an event is acquired on the condition that permission information is issued based on permission conditions. This makes it possible to limit acquisition of play information necessary for event sharing to cases where permission information is issued. That is, sharing of an event set by one user with other users can be restricted when permission information is issued. As a result, it is possible to restrict sharing of inappropriate events with other users, such as when holding periods overlap.

Various occurrences may be employed as events. For example, as an event, an event specified by information related to the execution such as the period and venue (target), or an event specified by the participation results such as when a predetermined privilege is given to the participants is adopted. you can Specifically, in one aspect of the game system of the present invention, when the game includes a privilege event (OE1) for imparting a predetermined privilege, the information issuing means has The authorization information may be issued for the event to function.

Where an event is identified by the presence or absence of predetermined perks, such predetermined perks may or may not be related to the game. Also, such a predetermined privilege may be a physical privilege or may be an electronic privilege. Further, such benefits may be tangible benefits, including electronic benefits, or intangible benefits, such as eligibility to participate in another event. Specifically, for example, in one aspect of the game system of the present invention, the game further includes a special event (OE2) in which participation is permitted when achievements in the privilege event satisfy participation conditions. , participation in the special event may be used as the predetermined privilege. In this case, the event results set by one user can be used as part of the conditions for participating in the special event. Accordingly, it is possible to determine whether or not to participate in a special event based on more achievements than when such an event is not used, so that it is possible to determine whether or not to participate more appropriately. . As a result, it is also possible to improve the attractiveness of events set by one user.

Games such as those described above may be provided directly by a game system or indirectly through a game machine. That is, a single game machine that provides games as described above may function as the game system of the present invention, or the game system of the present invention is connected to a game machine that provides games as described above. good too. Specifically, for example, in one aspect of the game system of the present invention, when the game is provided via a game machine (3) connected via a network (5), the information acquisition means The play information may be acquired from the game machine. When a game is provided through a game machine, the above concept of user includes not only the user of the game machine (person who plays the game) but also the operator (administrator) of the game machine. may be included. In addition, the acquisition of play information is not limited to the case where only the play information of the relevant event is extracted and acquired from the game machine, but also various events acquired regardless of permission or disapproval (share disapproval set by the user) (including event) by extracting the play information necessary for sharing the event from various information. In other words, the information acquisition means acquires information about various events (for example, from the game machine if there is a game machine intervening), and then acquires the play information necessary for sharing the sharing-permitted event from the acquired information. You may (extract).

In the case where the game described above is provided via a gaming machine, the authorization information may be issued directly to the gaming machine. Alternatively, the permission information may be indirectly issued through provision (e.g., e-mail, etc.) to the administrator, etc. of the game machine, and provided (input) to the game machine via such administrator, etc. . Furthermore, the play information may be automatically acquired from the game machine along with the issuance of the permission condition, or a further condition may be set for the acquisition of the play information. For example, the game system of the present invention further comprises event information providing means (24) for providing event information for realizing the event to the game machine when the permission information is acquired from the game machine, The information acquisition means may acquire the play information from the game machine when the game machine provides the event after acquiring the event information. Further, as such an aspect, when a plurality of game machines that respectively provide the game are connected via the network, the game providing the event out of the game machine identification information for identifying each game machine data storage means (23) for storing event data (ED1) in which the game machine identification information (for example, "approval range" information) of the game machine and the event are described in association; and the game for which the permission information is acquired. and data updating means (24) for updating the event data so that the game machine is associated with the event, wherein the event information providing means sends the event information to the game machine associated with the event by the event data. An aspect of providing may be adopted. In these cases, the destination of the event information is limited to the game machine that actually obtained the permission information. Also, the play information is acquired after the event information is provided. As a result, if there is another entity that determines whether or not to share the event, such as when the game machine is operated by another operator, whether or not to use the permission information (for example, the event information providing means ), the other entity may be given an opportunity to determine whether event sharing is actually achieved.

The play information may be used as appropriate. For example, as one aspect of the game system of the present invention, when a plurality of user terminal devices (4) respectively used by the plurality of users are connected through a network (5), the event is performed based on the play information. A mode may be employed that further comprises related information providing means (24) for providing related related information to each user terminal. In this case, for example, by using the play status information as related information, the event play status information can be shared with each user via each user terminal device. Note that when a game machine is interposed, each user terminal device may be connected via the same network as the game machine, or may be connected via a different network (including partial sharing).

On the other hand, the computer program of the present invention causes the computer (24) connected to the input device (36) and output device (37) used for playing the game to function as each means of the game system described above. It is constructed. In addition, the server device (2) of the present invention is connected to the input device (36) and output device (37) used for playing the game via the network (5), and as each means of the game system described above, It works. The game system of the present invention can be realized through the computer program or server device of the present invention.

1 game system 2 center server 3 game machine 4 user terminal device 5 network 23 storage unit (data storage means)
24 event providing unit (computer, information issuing means, information acquiring means, event information providing means, data updating means)
36 input device 37 display device (output device)
U user (one user)
PE private event (event)
OE1 qualifying event (event for benefits)
OE2 main battle event (special event)
ED1 Official event data (event data)

Claims (1)

A game system that provides a game that allows one of a plurality of users to set an event,
information issuing means for issuing permission information indicating permission for sharing when sharing of the event with another user among the plurality of users is permitted based on a permission condition;
information acquisition means for acquiring play information regarding the play status of the event necessary for sharing the event with the other users on the condition that the permission information is issued;
A game system with

Images