KR20220095516A - Apparatus and method for managing game event - Google Patents

Abstract

Embodiments disclosed in the present specification relate to a game event management device and a game event management method. According to an embodiment of the present invention, a game event management method may comprise the steps of: detecting the occurrence of a game event; and executing a game client based on the detected game event.

Description

Game event management device and game event management method {APPARATUS AND METHOD FOR MANAGING GAME EVENT}

Embodiments disclosed herein relate to a game event management apparatus and a game event management method, and more particularly, to an apparatus and method for managing a game event so that a user can easily participate in the game event.

Online games have evolved dramatically in recent years. In particular, with the rapid development of data transmission speed through the Internet, users can easily enjoy games anytime, anywhere through the game client installed on their terminal.

Meanwhile, in-game events are often provided to stimulate the interest of users and to activate the game. For example, an event may include a reward or promotion. The provision of such game events is an important factor in game operation in that it maintains the user's game immersion and interest.

Users want to actively participate in events to get the rewards they want, but these events often occur at times that are difficult for users to predict. For example, it is often difficult to know a season-specific event unless a user is continuously interested in and monitoring the exact date and time that the event is provided even when the corresponding season approaches. As the user's effort is required to participate in the game event, the user's will to participate in the game event is sometimes weakened.

In relation to the related art, according to Korean Patent Application Laid-Open No. 10-2014-0066274, the above-described prior art automatically determines a reward item by evaluating each of a plurality of game event generation conditions, and the user selects one of the event generation conditions. When one is satisfied, it only describes that a reward corresponding to the corresponding reward item is provided to the user, so it only suggests a method for generating an event, but does not support the user to easily participate in the event.

Therefore, there is a need for a new level of function to solve the above problems and further improve the satisfaction of game users.

On the other hand, the above-mentioned background art is technical information that the inventor possessed for the purpose of derivation of the present invention or acquired during the derivation process of the present invention, and it cannot be said that it is necessarily known technology disclosed to the general public before the filing of the present invention. .

Embodiments disclosed herein, it is an object to provide a game event management apparatus and a game event management method.

Another object of the embodiments disclosed herein is to provide a game event management apparatus and a game event management method for inducing a user to participate in a game event by automatically executing a game.

Another object of the embodiments disclosed in this specification is to provide a game event management apparatus and a game event management method for configuring a game environment so that a user can immediately play a game when he or she wants to play the game.

Another object of the embodiments disclosed herein is to provide a game event management apparatus and a game event management method capable of increasing user satisfaction with a game by increasing user participation in a game event.

As a technical means for achieving the above-described technical problem, according to an embodiment, a method for managing a game event by a game event management device, the step of detecting the occurrence of a game event, and based on the detected game event It may include the step of running the game client.

According to another embodiment, the game event management apparatus may include a communication unit for communicating with the game server, and a control unit that, when detecting occurrence of a game event, executes a game client based on the detected game event.

According to another embodiment, a computer-readable recording medium in which a program for performing a game event management method is recorded is disclosed. The game event management method may include detecting the occurrence of a game event, and executing a game client based on the detected game event.

According to another embodiment, a computer program stored in a medium for performing a game event management method is disclosed. The game event management method may include detecting the occurrence of a game event, and executing a game client based on the detected game event.

According to any one of the above-mentioned problem solving means, a game event management apparatus and a game event management method are provided.

According to any one of the above-described problem solving means, it is possible to provide a game event management apparatus and a game event management method for inducing a user to participate in a game event by automatically executing a game.

According to any one of the above-described problem solving means, it is possible to provide a game event management apparatus and a game event management method for configuring a game environment so that a user can immediately play a game when he or she wants to play the game.

According to any one of the above-mentioned problem solving means, it is possible to provide a game event management apparatus and a game event management method capable of increasing user satisfaction with a game by increasing user participation in a game event.

Effects obtainable in the disclosed embodiments are not limited to the above-mentioned effects, and other effects not mentioned are clear to those of ordinary skill in the art to which the embodiments disclosed from the description below belong. can be understood clearly.

1 is a block diagram illustrating a game event management apparatus according to an embodiment.
2 to 4 are flowcharts illustrating a game event management method according to an exemplary embodiment.
5 is an exemplary diagram for explaining a game event management method according to an embodiment.

Hereinafter, various embodiments will be described in detail with reference to the accompanying drawings. The embodiments described below may be modified and implemented in various different forms. In order to more clearly describe the characteristics of the embodiments, detailed descriptions of matters widely known to those of ordinary skill in the art to which the following embodiments belong are omitted. And in the drawings, parts irrelevant to the description of the embodiments are omitted, and similar reference numerals are attached to similar parts throughout the specification.

Throughout the specification, when a component is said to be “connected” with another component, it includes not only a case of 'directly connected' but also a case of 'connected with another component interposed therebetween'. In addition, when a component "includes" a component, it means that other components may be further included, rather than excluding other components, unless otherwise stated.

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings.

However, before explaining this, the meaning of the terms used below is first defined.

First, an 'event' is a type of promotion that provides a reward to a user as long as the user satisfies a predetermined condition presented to the user. In this case, the condition may be a user's access, play for a predetermined time, or achievement of a predetermined quest, and the reward may be an item, experience, level, or the like. Conditions and compensation are not limited to the above-described examples.

Events are, for example, an access event (or attendance event) that provides rewards when the connection requirements are met, an experience point event that gives additional experience points when playing for a predetermined period of time, and an item that can be played for a predetermined period There may be an item event, a seasonal event that allows you to purchase items specific to each season for free or at a low price, and a weekly event that provides periodic rewards.

Terms that require explanation other than those defined above will be separately explained below.

1 is a block diagram illustrating a game event management apparatus 100 according to an exemplary embodiment.

The game event management device 100 shown in FIG. 1 is a device that detects a game event generated in a game providing device (not shown) and executes a game client accordingly, and is included in the game providing device (not shown) or provides a game It may include a device (not shown), or it may be implemented as a device separate from the game providing device (not shown) to transmit and receive information for performing a game event management method while communicating with the game providing device (not shown). .

In this regard, the game providing device (not shown) may be implemented as a server-client system, for example, the game providing device (not shown) may be configured with a game server and a game client. The game client connects to the game server to play an online game, and may be installed in an electronic terminal to be described later, and the game server may provide a game service related to overall online game progress as a game client.

The game event management apparatus 100 may execute the game client while communicating with the game client or may transmit predetermined data to the game client. In addition, it is possible to detect the occurrence of an event in the game while communicating with the game server.

Such a game event management apparatus 100 may be implemented as an electronic terminal installed with an application capable of interacting with a game user or may be implemented as a server-client system, for example, the game event management apparatus 100 may include an event management server and It consists of an event management client, and the event management client may be installed in the electronic terminal.

In this case, the electronic terminal may be implemented as a computer, a portable terminal, a television, a wearable device, etc. that can be connected to a remote server through a network or can be connected to other terminals and servers. Here, the computer includes, for example, a laptop, a desktop, and a laptop equipped with a web browser, and the portable terminal is, for example, a wireless communication device that ensures portability and mobility. , PCS (Personal Communication System), PDC (Personal Digital Cellular), PHS (Personal Handyphone System), PDA (Personal Digital Assistant), GSM (Global System for Mobile communications), IMT (International Mobile Telecommunication)-2000, CDMA (Code) All kinds of handhelds such as Division Multiple Access)-2000, W-Code Division Multiple Access (W-CDMA), Wireless Broadband Internet (Wibro), Smart Phone, Mobile Worldwide Interoperability for Microwave Access (WiMAX), etc. It may include a (Handheld)-based wireless communication device. In addition, the television may include IPTV (Internet Protocol Television), Internet TV (Internet Television), terrestrial TV, cable TV, and the like. Furthermore, a wearable device is, for example, a type of information processing device that can be worn directly on the human body, such as a watch, glasses, accessories, clothes, shoes, etc. can be connected with

In addition, the event management server may be implemented as a computer capable of communication through a network with an electronic terminal in which an application for interaction with a user is installed, or may be implemented as a cloud computing server. In addition, the event management server may include a storage device capable of storing data or may store data through a third server. In addition, the component constituting the event management server may be performed in a plurality of physically separated servers or may be performed in one server.

Accordingly, according to the embodiment, the event management client constituting the game event management apparatus 100 may be installed in an electronic terminal in which the game client is installed, and may communicate with the game server or the event management server.

For example, when the event management client communicates with the game server, an event occurring in the game may be detected while communicating with the game server.

Also, for example, when the event management client communicates with the event management server, the event management server can detect an event occurring in the game while communicating with the game server, and the event management client receives the occurrence of the event from the event management server. can

Meanwhile, the game event management apparatus 100 according to the embodiment may include an input/output unit 110 , a communication unit 120 , a memory 130 , and a control unit 140 .

The input/output unit 110 may include an input unit for receiving an input from a game user and an output unit for displaying information such as a request message to be provided by the performance result of a task or the game event management apparatus 100 . For example, the input/output unit 110 may include an operation panel for receiving an input from a game user, a display panel for displaying a screen, and the like.

Specifically, the input unit may include devices capable of receiving various types of inputs, such as a keyboard, a physical button, a touch screen, a camera, or a microphone. Also, the output unit may include a display panel or a speaker. However, the present invention is not limited thereto, and the input/output unit 110 may include a configuration supporting various input/output.

According to an embodiment, the input unit may receive an input for registering an event to be notified among various events provided in the game from the game user. Also, the output unit may output an operation result of the game event management apparatus 100 or output a request message requesting to play a game as an event occurs.

The communication unit 120 may perform wired/wireless communication with other devices or networks. For example, the communication unit 120 may communicate with a third server to transmit/receive various types of information for performing a game event management method. To this end, the communication unit 120 may include a communication module that supports at least one of various wired and wireless communication methods. For example, the communication module may be implemented in the form of a chipset.

In this case, the wireless communication supported by the communication unit 120 may be, for example, Wireless Fidelity (Wi-Fi), Wi-Fi Direct, Bluetooth, Ultra Wide Band (UWB), or Near Field Communication (NFC). . In addition, the wired communication supported by the communication unit 120 may be, for example, USB or High Definition Multimedia Interface (HDMI).

According to an embodiment, the game event management apparatus 100 may communicate with a game server, and by obtaining information about the occurrence of a game event from the game server, the controller 140, which will be described later, may detect that a game event occurs. .

Various types of data such as files, applications, and programs may be installed and stored in the memory 130 . The controller 140 to be described later may access and use data stored in the memory 130 , or may store new data in the memory 130 . Also, the controller 140 may execute a program installed in the memory 130 . For example, the memory 130 may install a program for performing the game event management method, and may store a game event registration list for performing the game event management method as described above.

Meanwhile, the controller 140 controls the overall operation of the game event management apparatus 100 and may include a processor such as a CPU. The controller 140 may control other components included in the game event management apparatus 100 to perform an operation corresponding to a game user's input. For example, the controller 140 may execute a program stored in the memory 130 to be described later, read a file stored in the memory 130 , or store a new file in the memory 130 .

According to an embodiment, the controller 140 may execute a game client upon detecting the occurrence of a game event.

To this end, the controller 140 may register a game event that the game user wants to receive,

That is, the controller 140 may create a game event registration list including information about a game event to be notified when it occurs in a game.

According to an exemplary embodiment, one or more game events scheduled to occur may be provided to a game user, and a game event registration list including a selected game event may be generated. For example, in order to generate a game event registration list in the first week of October, the controller 140 may provide a 'Halloween Freaky Event' and a 'Happy Christmas Event' that are scheduled to occur, and among them, a 'Happy Christmas Event' may be selected by the user. If is selected, a new game event registration list can be created by creating a game event registration list including 'Happy Christmas Event' or adding 'Happy Christmas Event' to the pre-created game event registration list.

According to another embodiment, a game event registration list including the keyword as metadata may be generated so that a keyword may be input from a game user and the user may be provided with a game event including the keyword as metadata. .

In this case, the metadata is information for describing the corresponding event, and may include, for example, the title of the event, the contents of the event, the reward corresponding to the event, the event execution time, and the user's tendency to prefer the corresponding event. .

For example, when the keyword 'connection' is obtained from the user, the controller 140 selects a game event including 'connection' as an event title from among several game events provided in the game, and registers the game event consisting of the selected event. You can create a list. Or, for example, when the keyword 'item K' is obtained from the user, the controller 140 selects a game event that provides item K as a reward from among various game events provided in the game, and a game event consisting of the selected event. You can create a registration list. Or, for example, when the keyword 'combat type' is obtained from the user, the controller 140 selects and selects a game event in which 'combat type' is registered as metadata as a user preference among various game events provided in the game. It is possible to create a game event registration list composed of events that have been made.

The controller 140 may allow the user to edit the list by providing the generated game event registration list to the user.

Also, as an event included in the game event registration list, if the game client is executed according to the corresponding event, the controller 140 may delete the corresponding event from the game event registration list.

Based on the game event registration list as described above, the controller 140 may wait for the game event to occur.

In addition, the controller 140 may execute the game client based on the game event.

That is, when the game client is not running, the controller 140 may execute the game client when detecting that a game event has occurred.

At this time, if the controller 140 determines that it is a game event registered by the user among the generated game events, the controller 140 may execute the game client. can determine whether

Therefore, according to an embodiment, when detecting the occurrence of a game event, the controller 140 may execute an unplayed game client.

According to another embodiment, the controller 140 may execute a game client based on a game event and execution conditions.

For example, even if it detects that a game event registered in the game event registration list occurs, the controller 140 may execute the game client only when the execution condition is satisfied.

The 'execution condition' is a condition for triggering execution of the game client, and may include, for example, at least one of time, location, user input state, and terminal state. These execution conditions may be set by the user or may be preset. Accordingly, even if it detects that a game event has occurred, the controller 140 may wait for the game client to be executed and execute the game client when the execution condition is satisfied.

For example, there may be a time as an execution condition, and the execution condition may be set so that the game client is executed at a specific time on a specific date or at a specific time of the day. If the execution condition is set to be executed, the controller 140 may execute the game client in the evening.

Also, for example, there may be a location as an execution condition. For example, if the execution condition is set so that the game client is executed when the user's electronic terminal is located in 'OO-gu', which is his home location, the game event is Even if it occurs at the work location 'XX-gu', the controller 140 may run the game client when the user arrives at home, without running the game client.

In addition, for example, there may be a user input state as an execution condition. For example, when a user input is detected for an electronic terminal in which the game client is installed, the game client may not be executed by notifying it with a push message that an event has occurred, , when the user is not inputting the electronic terminal in which the game client is installed, the controller 140 may execute the game client.

In addition, for example, there may be a state of the terminal as an execution condition. The state of the terminal is a state of an electronic terminal in which a game client is installed, and may include a remaining battery rate, the number of running applications, and whether or not an airplane mode is present. For example, even when a game event occurs, the game client can be executed only when the battery remaining rate of the electronic terminal in which the game client is installed is equal to or greater than a predetermined value, or by running the game client only when the number of applications being executed is less than or equal to the predetermined number. It is possible to prevent wastage of resources of the electronic terminal due to the execution of the game client.

In addition, if the controller 140 detects that the game client is being executed after the game event occurs and before the controller 140 executes the game client, the controller 140 may not execute the game client.

Meanwhile, the controller 140 may request to obtain patch data for the execution of the game client based on the game event.

That is, in order to play the game, it is necessary to update the game client by accessing the game server and downloading the patch data.

Accordingly, patch data of the game client may be downloaded for updating the game client, and according to an embodiment, the controller 140 may request and obtain the patch data from the game server, and update the game client with the patch data.

According to another embodiment, the controller 140 may request to obtain patch data for the execution of the game client by automatically downloading the patch data at the request of the game client as the game client is executed, and the patch data is applied. After the game client is updated, you can restart the game client.

In this way, by completing the update for game play before the user plays the game, the user does not need to invest time in the update, and accordingly, the user who is aware of the desired event is not frustrated by application update, etc. make sure not to

On the other hand, the controller 140 may provide a request message for requesting a user input to the game client after the game client is executed.

That is, even when the controller 140 executes the game client, there are cases in which the user does not recognize the automatic execution of the game client.

To this end, the controller 140 may provide the user with a request message for inducing the user to play the game after executing the game client.

The request message may be implemented as text, image, or video, and may be provided through a push notification or the like.

According to an embodiment, the controller 140 may provide a request message to the user at the same time or immediately after the execution of the game client.

According to another embodiment, the controller 140 may provide a request message to the user when a predetermined time elapses from the execution time of the game client.

In this case, the predetermined time may be set by the user, or may be set to be the same as or similar to the time the user started playing after the execution of the game client in the past, or the time it takes for a plurality of other users to start playing after the execution of the game client. It can be set as an average of time.

According to another embodiment, it is possible to inquire whether the user is to be provided with a request message, and only when the user sets that the request message is to be provided, the controller 140 may provide the request message to the user.

Meanwhile, the controller 140 may execute the game client, generate user input information corresponding to the game event and transmit it to the game client.

For example, when the control unit 140 executes the game client according to the detection of an access event, it generates input information for processing a login input so as to automatically log in to the game client, or the same input as input for a button corresponding to attendance. Input information that generates an input can be generated and transmitted to the game client.

According to an embodiment, if a user input is not generated within a predetermined time after executing the game client, the controller 140 may generate user input information and transmit it to the game client so that the user participates in the corresponding event.

According to another embodiment, after the execution of the game client and the request message are provided, the controller 140 may generate user input information corresponding to the game event and transmit it to the game client.

For example, if the control unit 140 provides a request message and a user input to the game client does not occur within a predetermined period, and if the game event is a chatting event with a guild member, the control unit 140 provides a chatting message composed of arbitrary phrases. Input information can be generated so that a message is input and delivered to the game client.

In this way, input information is generated and transmitted to the game client so that the user can obtain the desired reward without missing a game event.

Meanwhile, FIGS. 2 to 4 are flowcharts illustrating a game event management method according to an exemplary embodiment. The game event management method shown in FIGS. 2 to 4 includes the steps of time-series processing in the game event management apparatus 100 shown in FIG. 1 . Therefore, even if omitted below, the content described above with respect to the game event management apparatus 100 illustrated in FIG. 1 may also be used in the game event management method according to the embodiment illustrated in FIGS. 2 to 4 .

In relation to this, FIG. 5 is an exemplary diagram for explaining a method for managing a game event according to an embodiment. 2 to 4 are described with reference to FIG. 5 .

As shown in FIG. 2 , the game event management apparatus 100 allows the user to register an event that the user wants to know ( S210 ).

That is, the game event management apparatus 100 may create a game event registration list.

In addition, the game event management apparatus 100 may detect the occurrence of an event (S220).

In this case, the game event management device 100 may acquire information about a game event generated in the game through the game server while communicating with the game server, and compare the obtained information with the registration list to generate an event included in the registration list It can be determined whether

When the game event management apparatus 100 detects the occurrence of an event (S220), it may determine whether the game client is being executed (S230). If the game client is already running, it can be provided as a push message that the event has occurred through the game client.

On the other hand, if the game client is not running, the game event management apparatus 100 may execute the game client (S240).

In this case, the game event management apparatus 100 may execute the game client only when the execution condition is satisfied.

For example, the game event management apparatus 100 may execute the game client based on an execution condition for the execution of the game client and a game event.

Meanwhile, as shown in FIG. 3 , the game event management apparatus 100 may request to acquire patch data in order to execute the game client ( S300 ).

The game event management apparatus 100 may generate and provide a request message when a predetermined time elapses after executing the game client (S410) (S420).

In relation to FIG. 5 , the screen D of the electronic terminal constituting the game event management apparatus 100 is shown.

Referring to FIG. 5 , a request message 500 for requesting to play a game may be provided. The game event management device 100 may inform that the game client of the game B has been executed to participate in the event A through the request message 500, and the user through the running app information displayed for each operating system of the electronic terminal allows the user to play the game B By confirming that is running or selecting a launcher corresponding to game B, it is possible to directly enter the game screen and play the game.

After providing the request message as described above, if there is no user input for a predetermined period of time (S430), the game event management apparatus 100 may generate input information corresponding to the game event and transmit it to the game client (S440) .

That is, even when the game client is executed, the user may not be playing the game. If this state continues for a predetermined period, the game event management apparatus 100 may generate input information and transmit it to the game client.

For example, in the event of a visit to a predetermined space in the game, the game event management apparatus 100 transmits input information for generating an input for moving a character to the corresponding space to the game client, and processes the input as generated by the game client This allows users to receive rewards according to the event.

According to the game event management method according to the above-described embodiment, the user can recognize when a corresponding event occurs without having to take care of each event he/she wants to participate in. In addition, since preparations for participation in the event (eg, update of the game client) are completed, the user's participation in the event is not frustrated due to other factors such as the need to additionally download game patch data. This helps to achieve the intended purpose of the game event and, as a result, maintains game retention.

The term '~ unit' used in the above embodiments means software or hardware components such as field programmable gate array (FPGA) or ASIC, and '~ unit' performs certain roles. However, '-part' is not limited to software or hardware. '~' may be configured to reside on an addressable storage medium or may be configured to refresh one or more processors. Accordingly, as an example, '~' indicates components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, and procedures. , subroutines, segments of program patent code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.

The functions provided in the components and '~ units' may be combined into a smaller number of elements and '~ units' or separated from additional components and '~ units'.

In addition, components and '~ units' may be implemented to play one or more CPUs in a device or secure multimedia card.

The game event management method according to the embodiments described with reference to FIGS. 2 to 4 may also be implemented in the form of a computer-readable medium for storing instructions and data executable by a computer. In this case, the instructions and data may be stored in the form of program codes, and when executed by the processor, a predetermined program module may be generated to perform a predetermined operation. In addition, computer-readable media can be any available media that can be accessed by a computer, and includes both volatile and nonvolatile media, removable and non-removable media. In addition, the computer-readable medium may be a computer recording medium, which is a volatile and non-volatile and non-volatile storage medium implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. It may include both volatile, removable and non-removable media. For example, the computer recording medium may be a magnetic storage medium such as HDD and SSD, an optical recording medium such as CD, DVD, and Blu-ray disc, or a memory included in a server accessible through a network.

In addition, the game event management method according to the embodiments described with reference to FIGS. 2 to 4 may be implemented as a computer program (or computer program product) including instructions executable by a computer. The computer program includes programmable machine instructions processed by a processor, and may be implemented in a high-level programming language, an object-oriented programming language, an assembly language, or a machine language. . In addition, the computer program may be recorded in a tangible computer-readable recording medium (eg, a memory, a hard disk, a magnetic/optical medium, or a solid-state drive (SSD), etc.).

Accordingly, the game event management method according to the embodiments described with reference to FIGS. 2 to 4 may be implemented by executing the computer program as described above by the computing device. The computing device may include at least a portion of a processor, a memory, a storage device, a high-speed interface connected to the memory and the high-speed expansion port, and a low-speed interface connected to the low-speed bus and the storage device. Each of these components is connected to each other using various buses, and may be mounted on a common motherboard or in any other suitable manner.

Here, the processor may process a command within the computing device, such as, for example, to display graphic information for providing a graphic user interface (GUI) on an external input or output device, such as a display connected to a high-speed interface. Examples are instructions stored in memory or a storage device. In other embodiments, multiple processors and/or multiple buses may be used with multiple memories and types of memory as appropriate. In addition, the processor may be implemented as a chipset formed by chips including a plurality of independent analog and/or digital processors.

The memory also stores information within the computing device. As an example, the memory may be configured as a volatile memory unit or a set thereof. As another example, the memory may be configured as a non-volatile memory unit or a set thereof. The memory may also be another form of computer readable medium, such as, for example, a magnetic or optical disk.

In addition, the storage device may provide a large-capacity storage space to the computing device. A storage device may be a computer-readable medium or a component comprising such a medium, and may include, for example, devices or other components within a storage area network (SAN), a floppy disk device, a hard disk device, an optical disk device, or a tape device, a flash memory, or other semiconductor memory device or device array similar thereto.

The above-described embodiments are for illustration, and those of ordinary skill in the art to which the above-described embodiments pertain can easily transform into other specific forms without changing the technical idea or essential features of the above-described embodiments. you will understand Therefore, it should be understood that the above-described embodiments are illustrative in all respects and not restrictive. For example, each component described as a single type may be implemented in a dispersed form, and likewise components described as distributed may be implemented in a combined form.

The scope to be protected through the present specification is indicated by the claims described below rather than the above detailed description, and should be construed to include all changes or modifications derived from the meaning and scope of the claims and their equivalents. .

100: game event management device
110: input/output unit 120: communication unit
130: memory 140: control unit

Claims (14)

A game event management device, as a method for managing game events,
detecting the occurrence of a game event; and
A method for managing game events, comprising the step of executing a game client based on the sensed game event. The method of claim 1,
The step of running the game client is,
Including the step of executing the game client based on the game event and an execution condition for the execution of the game client, game event management method. According to claim 1,
Further comprising the step of providing a request message for requesting a user input to the game client, the game event management method. 4. The method of claim 3,
Providing the request message comprises:
and providing the request message when a predetermined time elapses from the execution time of the game client. According to claim 1,
The method further comprising generating user input information corresponding to the event and transmitting the generated user input information to the game client. According to claim 1,
The step of running the game client is,
Further comprising the step of requesting to obtain patch data for the execution of the game client, the game event management method. According to claim 1,
Further comprising the step of registering the game event, game event management method. A computer-readable recording medium in which a program for performing the method according to claim 1 is recorded. A computer program stored in a medium for performing the game event management method according to claim 1, which is performed by the game event management device. game event management device,
a communication unit for communicating with the game server; and
When the occurrence of a game event is detected, the game event management device comprising a controller for executing a game client based on the sensed game event. 11. The method of claim 10,
The control unit is
A game event management device for executing the game client based on the game event and an execution condition for the execution of the game client. 11. The method of claim 10,
The control unit is
A game event management device that provides a request message for requesting a user input to the game client. 11. The method of claim 10,
The control unit is
Requesting to obtain patch data for the execution of the game client, game event management device. 11. The method of claim 10,
The control unit is
A game event management device for registering the game event.

Images