KR20060122236A - Method and system for performing quest by agent player in on-line game - Google Patents

Abstract

A method and a system for vicariously performing a quest in an online game are provided to enable a user requesting vicarious quest performance to offer proper rewards to the user vicariously performing the quest by allowing other users to vicariously perform the quest of the user. A game server(108) relays game data transmitted from multiple user clients(100-104) and controls game progress. An account server(106) manages user state information includes game money and possessed item information of the users. A quest server(110) manages question information provided to the users, and receives and stores quest agent acceptance information from a master or slave user in case that at least one slave user accepts a quest agent request of the master user. In the case that the slave user vicariously completes the quest of the master user, the quest server provides the rewards to the master and slave user.

Description

Method and System for Performing Quest by Agent Player in On-line Game}

1 is a view showing a schematic configuration of a quest surrogate performing system according to an embodiment of the present invention.

2 is a conceptual diagram illustrating a master user granting a quest to a slave user according to an exemplary embodiment of the present invention.

3A illustrates an example of a user interface provided to a master user for delegating quest surrogate performance to a slave user.

 3B illustrates an example of a user interface provided to a slave user when delegated to perform a quest surrogate from a master user.

4 is a diagram illustrating an example of a screen displayed by a market place when a quest proxy performer is found through a market place.

5 is a diagram showing the module configuration of the quest server according to an embodiment of the present invention.

6 is a diagram illustrating a field configuration of a quest database according to an embodiment of the present invention.

Figure 7 is a flow chart showing the overall flow of the quest surrogate performing method according to an embodiment of the present invention.

8A is a flow diagram of a process for a master user to delegate quest surrogate directly to a slave user without going through a market place.

8B is a flowchart illustrating a process in which a master user delegates a quest surrogate to a slave user according to another embodiment of the present invention.

9 is a flowchart illustrating a reward process when performing a quest according to an exemplary embodiment of the present invention.

10 is a diagram illustrating the structure of a quest packet according to an embodiment of the present invention.

11 is a diagram illustrating an example of a screen for checking the status of quests delegated to slave users by a master user according to an exemplary embodiment of the present invention.

The present invention relates to an online game, and more particularly, to an online game using a quest method that gives a user a specific task and provides a reward according to a result of the execution.

Recently, with the development of network technology, high-speed transmission of large-capacity multimedia data is possible, and the online game market is rapidly growing with the widespread use of user terminals that can be connected to the network.

In the past, games have mainly been packaged games that mainly sell recording media such as CDs as products, but the number of online game users is increasing more recently than packaged games. This is because online games, in which a large number of users compete or cooperate with each other, compared to a packaged game, have gained favorable response from users compared to a packaged game that is played alone.

There are various types of online games such as GoStop, board games such as poker, sports games such as golf and baseball, and Massively Multi-player Online Role Playing Game (MMORPG).

One of the game types that has the largest user base among online games is MMORPG. MMORPG refers to a game in which a large number of users share a map while growing their characters through competition or cooperation. MMORPG is a game genre that has evolved so that many users can play role-playing games in existing package games.

Early MMORPG games grew their character by leveling up through experience gained from eliminating monsters or acquiring items obtained through monster elimination. However, such a game method has a problem that makes the MMORPG game boring by allowing the users to remove only the monster without any sense of purpose.

In order to solve the problems of the MMORPG game, the quest method was introduced in the MMORPG game. The quest method is a method of granting a specific quest to the user and providing experience and / or items when the user completes the quest to naturally grow the character while solving the quest. A representative example of the quest-based MMORPG game is the World of Warcraft game published by Blizzard, which allows natural character growth by solving only the quests provided to the user, and through the quests, the user's story of the whole game. To understand.

As the quest method was introduced in the MMORPG game, although the problem of the MMORPG game that the simple task must be repeated repeatedly was largely solved, the quest type game exposed the following problems.

First of all, the quest method has a problem in that the degree of freedom, which is one of the advantages of the MMORPG game, is reduced in that most users must perform the same quest. One of the appeals of the MMORPG game is that it is possible to grow a character in a way that has its own personality, but with the introduction of the quest method, all users perform the same quest, resulting in uniform character growth.

In addition, users have a problem in that even if the quest that they do not want to perform the quest in order to grow the character. There are various types of quests, such as exploration quests, monster removal quests, and item acquisition quests. Although the user's preferred quests are different, there are problems that users have to perform all kinds of quests.

In addition, the difficulty quests given a lot of experience and good items often require a long time more than 3-4 hours to solve the bar users, such as office workers can not play for a long time had a lot of difficulty in growing the character.

In order to solve the problems of the prior art as described above, in the present invention, the user can perform the quest of a specific user, and the user who requested the quest surrogate can provide an appropriate reward to the user who performed the quest surrogate. The present invention proposes a method and a system for providing a quest proxy performing service in an online game.

Another object of the present invention is to propose a method and system for providing a quest surrogate service in an online game where users can grow their characters while mainly performing their preferred quests.

It is still another object of the present invention to propose a method and system for providing a quest surrogate performance in an online game where a user who does not have much time such as an office worker can promote smooth character growth through quest surrogate performance.

It is still another object of the present invention to propose a method and system for providing a quest proxy performing service in an online game that can further diversify the economic system of an online game by incorporating quests and users as transactions.

In order to achieve the above objects, according to an aspect of the present invention, providing an interface that can delegate a specific quest owned by the master user to at least one slave user; Storing quest acceptance information when at least one slave user accepts a master user's quest surrogate through the interface; When the slave user who accepts the quest surrogate is completed, the quest surrogate performance service is provided in the online game including providing a reward to the master user and the slave user.

The interface may include means for setting reward information to be provided to the slave user by the master user when the slave user completes the quest.

The interface includes means for selecting a quest to delegate to a slave user; And means for inputting a slave user to perform the quest on behalf of, and when the master user inputs all of the reward information, the quest to be delegated, and the slave user to perform the quest, a quest packet corresponding to the input information is corresponding. It is preferably sent to the slave user.

The interface further includes means for selecting a quest to be delegated to a slave user, and when the master user enters both the reward information and the quest information to be delegated, the input information is registered in the marketplace of the online game, and the other user They may select a quest to be performed on behalf of the master user using the information registered in the market place.

When a plurality of slave users want to perform a quest of a master user registered in the market place, the slave user who performs the quest on behalf of the competitor may be determined by a competitive bidding scheme.

The reward that the master user provides to the slave user is determined by the contract between the parties, and may include the game money of the master user or the item of the master user.

When the slave user completes the quest of the master user, the master user is preferably provided with the original reward provided when the quest is completed.

The quest acceptance information may include master user / slave user information related to the accepted quest, quest identification information, and reward information provided by the master user to the slave user when the quest is completed.

When the slave user accepts the quest surrogate of the master user, the client program or the quest server of the slave user may monitor whether the slave user completes the quest.

On the other hand, according to another aspect of the present invention, a game server for relaying game data transmitted from the client of a plurality of users, and controls the progress of the game; An account server for managing user status information including game money and item information of users; Manages the quest information provided to the user, when at least one slave user accepts the quest surrogate request of the master user, receives and stores the quest surrogate performance acceptance information from the master or slave user, the slave user When the quest surrogate performance of the master user is completed, a quest surrogate performance service providing system is provided in an online game including a quest server that rewards the master user and the slave user.

According to another aspect of the present invention, a combination of instructions executed in a user client terminal to provide a quest surrogate function in an online game is tangibly implemented, and a recording medium having recorded thereon a program that can be read by the client terminal. A quest proxy performing interface module for providing an interface for inputting slave user information to perform a quest on behalf of the user, quest information to be performed by the slave user, and reward information to be provided to the slave user when the quest of the slave user is completed; A quest packet generation module for generating a quest packet to be transmitted to the slave user using information input through the quest surrogate execution interface module; It includes a quest list management module for managing the information of the quests received from the quest server or other users from the user, when the slave user completes the quest, to provide the reward information and the slave user from the quest server to the slave user A recording medium is provided which records a program for receiving compensation information to be performed.

Hereinafter, with reference to the accompanying drawings will be described in detail a preferred embodiment of the method and system for providing a quest proxy performing service in the online game according to the present invention.

1 is a view showing a schematic configuration of a quest surrogate performance system according to an embodiment of the present invention.

Referring to FIG. 1, a quest proxy performing system according to an embodiment of the present invention includes a plurality of game clients 100, 102, 104, an account server 106, a game server 108, a quest server 110, and a quest. Database 112 may be included.

The game clients 100, 102, and 104 are installed with a game client program necessary for performing an online game. Here, the online game may be an MMORPG game adopting a quest method, and the MMORPG game may include any kind of online game in which a quest is granted and executed. For example, in recent years, even in a shooting game or a strategy simulation game, there are a number of games in which a plurality of players are granted quests and perform the quests, even in the form of an RPG. It may be included in the category of the game to which it applies. However, for convenience of description, in the present embodiment, a method and a system for performing quest surrogate will be described using MMORPG as an example.

The game client 100, 102, 104 communicates with the game server 108, the account server 106, the quest server 110, etc. through the installed game client, and communicates with the servers configuring the game system. It provides a function of providing an online game service to a user.

The game clients 100, 102, 104 may include any type of data processing device capable of executing a game client program and communicating over a network. For example, game clients 100, 102, 104 may include desktop PCs, notebook computers, PDAs, mobile communication terminals, console game machines, portable game machines, and the like.

The game client program is not necessarily installed in the game clients 100, 102, and 104, and a game service may be provided only by a web browser without a separate client program. As described above, game clients 100, 102, 104 communicate with servers 106, 108, 110 constituting a game system via a network, where a wired network such as an internet network, a private network, Of course, it can include all wireless networks such as wireless Internet network, mobile communication network.

In FIG. 1, only an account server 106, a game server 108, and a quest server 110 are illustrated as servers constituting a game system. In FIG. 1, only servers necessary for performing a quest proxy according to the present invention are illustrated. It will be apparent to those skilled in the art that more servers may be included for other functions. In addition, it will be apparent to those skilled in the art that the account server 106, game server 108, and quest server 110 shown in FIG. 1 may be integrated into one or more servers as needed.

The account server 106 functions to manage user's account information. The account server 106 manages information of the character possessed by the user, that is, character status information such as character level, HP, and MP, and inventory (equipment, inventory) information possessed by the character. When the user acquires experience values or new items during the game, the acquisition information is provided from the game server 108 to the account server 106, and the account server updates the new state change information.

The game server 108 functions to control the user's game progress through communication with a program installed in the client. In the MMORPG game, the game server 108 transmits the information of other users in the region to which the user belongs to the user's client, and the status change information of another user (for example, the movement of another user, item acquisition, level change, etc.) By providing the user with a multi-party game is possible. In addition, the game server 108 also performs a function of relaying conversations, item transactions, and the like between users.

The quest server 110 manages quest information, and functions to grant a quest to a user who satisfies a condition and provide a corresponding reward when the quest is achieved. Quests are usually received from non-player characters (NPCs) or through special quest start items.

Leveling up in an MMORPG game is accomplished by accumulating experience gained by performing quests or eliminating monsters in the game. There are various kinds of quests, such as quests that can be completed by investing a few minutes and quests that require more than three hours to complete. MMORPG game is a game that draws the fun of the game through cooperation and competition among users, users such as office workers relatively lack of time has a difficult aspect to perform all the quests one by one.

In addition, the quests are divided into various types such as search quests that require a specific area search, hunting quests that require a specific monster to be removed, and item acquisition quests that require a specific item to be acquired. Kinds are different. For example, some users prefer new local exploration quests, but do not prefer quests for hunting monsters, while others prefer hunting quests over exploration quests. As such, although the preferred quests are different for each user, all quests set in the game should be performed for level up regardless of the user's preference.

In the present invention, in order to solve the problems as described above, the quest server 110 of the present invention enables the other user to perform the quest of a specific user on behalf of. That is, when the first user needs to perform the quest A, the first user may request that the second user perform the A quest given by the NPC or the quest start item, and the quest server of the present invention Quest surrogate and reward process according to the quest between the users is controlled. Hereinafter, a user requesting to perform a proxy quest is referred to as a 'master user', and a user who performs a request for a quest from the master user is referred to as a 'slave user'.

When the quest delegation is made between users, the quest server 110 receives the quest delegation information and stores the information in the quest database 112. An interface for delegating quests between users may be provided by a client program installed in the client, or may be dynamically generated in the quest server 110 and provided to each user.

According to a preferred embodiment of the present invention, in the case of performing quest surrogate, the reward originally given in the game according to the quest execution is provided to the master user who requested to perform the surrogate quest. The slave user who performs the quest on behalf of the quest is provided with the rewards contracted with the master user in the game from the quest server. For example, the master user may contract with the slave user for 20 gold of game money in exchange for performing the quest surrogate. Upon completion of the corresponding quest of the slave user, the slave user is rewarded with 20 gold. In this case, 20 gold of the game money of the master user is deducted. In addition to the game money, a specific item possessed by the master user may be rewarded to the slave user. When delegating a quest, contract information about compensation between a master user and a slave user is transmitted to the quest server, and the quest database stores the information.

Of course, the rewards for performing quest surrogate may be preset in the game according to the difficulty of the quest, not the contract between the parties.

The quest server 110 monitors whether users complete the quest and provides a preset reward upon completion of the quest. The monitoring of the completion of the quest may be performed in the client program. In this case, when the quest is completed, the quest server 110 receives quest completion information from the client program, and provides a reward for the corresponding quest to the user. When the quest server 110 receives the quest completion information, the quest server 110 determines whether it is a general quest or a surrogate quest. If the surrogate quest is performed, the quest server 110 provides the slave user with a reward promised between the master user and the slave user.

The quest database 112 stores information about quests provided by the game and quest information to be performed for each user. In the present invention, the quest surrogate performance is supported, and the quest database is preferably stored separately from the quest received directly from the NPC and the quest provided from the master user.

2 is a diagram illustrating a conceptual diagram in which a master user grants a quest to a slave user according to an exemplary embodiment of the present invention.

Referring to FIG. 2, AA and BB users, who are master users, receive a quest from a quest server. AA and BB users are given a quest from the quest server by talking to the NPC granting the quest or obtaining a specific quest start item. When the quest is granted from the quest server, the quests granted from the server are added to the quest list of the AA and BB users.

The AA user and the BB user delegate the quest surrogate to the slave users Aa and Ab users or Ba users and Bb users. As shown in FIG. 2, delegation of a quest may be made for a plurality of slave users instead of one slave user. In this case, the user who performs the quest first among the Aa and Ab users who receive the quest delegation from the AA user may be provided with the promised reward from the AA user.

In addition, Aa users who have been delegated quests may re-delete the quests to other users. 2 illustrates a case in which Aa user delegates a quest to a CC user who is another user. If Aa user re-delegates the quest to CC user, another contract will be made between Aa user and CC user regarding compensation. If the Aa user re-delegates the quest to the CC user and the CC user performs the quest, the reward set in the game for the quest is preferably provided to the AA user, and the Aa user and the CC user are provided with the rewards determined by the contract. It is preferable.

The master user and the slave user can determine whether or not to perform the proxy of the quest by the dialogue between the users and compensation when performing the proxy. Most MMORPG games provide various chat functions between users, and through these chat functions, it is possible to find a slave user who can perform the quest on behalf of them and discuss the reward. For example, if a master user sends a message via a public dialog to find a user to perform a specific quest on behalf of the user, the interested user responds to the master user's message by sending a message to the slave. You will find the user.

In addition to using dialogs, it can also provide the ability to find slave users to perform quests through marketplaces such as auction houses. At present, most MMORPG games allow users to trade by providing a market place such as an auction house, and provide another fun for the user by introducing a real economy concept such as an auction in the market place. The trading target of such a market place is limited to the item, but in the present invention, the quest may be a trading target.

As such, when delegating the execution of a quest through a dialogue or a market place between users, an online game should provide an interface for setting the delegation of the quest and rewards between the parties. FIGS. 3A, 3B, and FIG. We will look at these interfaces in section 4.

FIG. 3A illustrates an example of a user interface provided to a master user to delegate a quest surrogate to a slave user, and FIG. 3B illustrates an example of a user interface provided to a slave user when delegated to perform a quest surrogate from a master user. Figure is a diagram.

As described above, users negotiate with each other whether or not to perform quests and rewards for performing quest surrogate. When the quest surrogate is performed and the reward is negotiated, the master user selects a quest to delegate the surrogate and inputs a slave user ID to surrogate the quest in the blank of the quest surrogate part in the interface shown in FIG. 3A. If it is agreed to use quest rewards as game money, enter the negotiated game money in the field labeled Gold. When negotiated to use quest rewards as items, the master user places the negotiated items in the item field. The master user can place an item in the item column by dragging the item from his inventory.

In the interface of FIG. 3A, when the master user inputs all items and clicks the OK button, the slave user is provided with the user interface screen as shown in FIG. 3B. As shown in FIG. 3B, the slave user is provided with the quest selected by the master user and reward information according to the quest surrogate, and is provided with an interface for determining whether to accept. The slave user accepts the quest surrogate by clicking on the 'Yes' button if the displayed items match the items negotiated through the dialogue.

4 is a diagram illustrating an example of a screen displayed by a market place when a quest substitute performer is found through the market place.

The master user may register quests and rewards to be performed on behalf of the market place. When the master user completes the registration, other users may enter the market place as shown in FIG. 4.

As shown in FIG. 4, the title of the quest, the requested user ID, the level at which the quest can be performed, the reward information according to the quest is displayed, and the interested user selects one of the quests registered in the marketplace. Quest will be granted from the master user. It may not be easy to find a slave user to perform the quest through a dialogue. In this case, if a quest is registered in the marketplace, the quest information requested by other users may be read even if the master user is offline.

4 illustrates a screen for a case in which a master user determines a reward and registers in a market place, but a reward for a quest may be determined by competitive bidding of slave users. Also, although not shown in FIGS. 3 and 4, an interface for setting period information for performing quests when delegating quests may be additionally provided.

5 is a diagram illustrating a module configuration of a quest server according to an exemplary embodiment of the present invention.

Referring to FIG. 5, a quest server according to an embodiment of the present invention includes a quest list management module 500, a quest grant module 502, a surrogate quest management module 504, a quest completion monitoring module 506, and a reward process. Module 508 may be included.

The quest list management module 500 functions to manage quest information provided in the game. The quest list is updated by the administrator.

The quest grant module 502 functions to provide a quest associated with the NPC or the quest item to the user who has requested the quest when the user requests a quest grant by talking to the NPC providing the quest or clicking a quest start item. . There may be various ways for the user to request quest grant in addition to NPC conversation and quest item click. When the user requests a quest through an NPC conversation or the like, the game client program or the game server provides the quest server with the unique ID information of the quest requested by the user, and the quest server extracts the quest information corresponding to the unique ID from the quest database. To the user.

The surrogate quest management module 504 controls the quest surrogate performance contract procedure between users, and stores the corresponding contract information when a quest surrogate performance contract is made between users. When the master user requests a quest from the slave user, the proxy quest management module 504 generates a quest packet including the quest content and reward condition information, and transmits the generated quest packet to the slave user. When the slave user accepts the master user's quest surrogate request, the surrogate quest management module 504 receives surrogate quest acceptance information from the slave user or the master user, and stores the received information in the quest database. The quest packet may not be generated in the surrogate quest management module 504 but may be generated in the game client program of the master user and transmitted directly to the slave user through a P2P method or a relay of the game server.

The quest completion monitoring module 506 functions to monitor whether the user who has received the quest achieves the quest and reflects the quest completion information in the quest database when the quest is completed.

According to one embodiment of the present invention, the actual monitoring of the completion of the quest is performed by the client program, the quest completion monitoring module 506 receives only the completion information of the quest from the client program and the received information to the quest database Reflect.

For example, if the quest given to the user is a quest that needs to talk to an NPC named 'A', the client program will display the location of the NPC 'A' on the minimap if the user moves to an area with an NPC named 'A'. By displaying or specifying an effect specific to NPC 'A' (for example, by placing a question mark on the head of NPC 'A'), it provides the NPC information related to the quest performance. When the user completes the quest by talking to the corresponding NPC, the client program transmits the quest completion information including the unique ID information of the completed quest to the quest server, and the quest completion monitoring module 506 receives the quest completion information. Reflected in the quest database.

As another example, if the quest given to the user is a quest that removes 10 specific monsters, the client program indicates that each time the user removes that monster one by one, the target 10 is removed and all 10 When the quest is completed by removing, the quest completion information is provided to the quest completion monitoring module 506.

Monitoring of quest completion may be performed by the quest server, not the client program. For example, if a user has a quest that encounters an NPC named 'A', the Quest Completion Monitoring module monitors whether the user moves to the region where the NPC 'A' is located, and if the user moves to that region, the NPC Provide control signals to the game client so that a specific mark, such as a question mark, appears at 'A'. In addition, when detecting that the user has completed the conversation with the NPC 'A' through communication with the game server, the quest completion monitoring module 506 delivers the quest completion information to the user's client program and stores the quest completion information in the database. Reflect on.

The reward processing module 508 functions to process the reward for completing the quest when the user completes the quest. Since the reward for completing the general quest is preset in the database, the preset reward is provided to the user. For example, if the reward is set to reward 500 and 10 gold when completing a specific quest, the reward processing module 508 states that the user has earned 500 and 10 gold through communication with the account server. Request to change the information, and transmits a control signal to the client of the user to display the compensation information so that the user can check the compensation information.

The reward processing module 508 determines whether the quest completed by the user is a general quest or a surrogate quest. If the quest is a general quest, the reward processing module 508 processes the reward in the above-described manner. To deal with.

If the quest completed by the user is a surrogate quest, the reward processing module 508 displays the quest database as a master user of the quest, reward information originally set for the quest, and reward information set as a contract between the master user and the slave user. Extract from.

The reward processing module 506 requests the account server to change the status information of the master user to provide the master user with the reward originally set for the quest. If the master user is online, the reward processing module 506 may transmit a message informing the slave user of the quest completion and the reward to the master user in real time. In addition, the compensation processing module 506 requests the account server to change the status information of the master user and the slave user so that the reward promised between the slave user and the master user is made to the slave user. For example, if a contract is made to provide 50 gold in exchange for quest surrogate, the reward processing module 506 may subtract 50 gold from the master user's game money and increase or decrease 50 gold in the slave user's game money. Send request information to the accounting server. As another example, when a contract is made in which the master user provides an item dagger in exchange for performing a quest surrogate, the reward processing module 506 removes the dagger from the master user's inventory and allows the dagger to be added to the slave user's inventory. Send the request information to the accounting server.

When an item is contracted between a master user and a slave user as a reward for performing a quest surrogate, if the master user disposes the item before performing the quest of the slave user, the slave user cannot be compensated, so trading or destroying the item is impossible. It is preferable to set.

6 is a diagram illustrating a field configuration of a quest database according to an embodiment of the present invention.

6, a quest database according to an embodiment of the present invention includes a quest type field 600, a quest region field 602, a quest ID field 604, a level field 606, a reward field 608, It may include a completion field 610, a master / slave user field 612, and a proxy compensation field 610.

The fields shown in FIG. 6 are fields for information stored in an area managing quest information of each user in the quest database. In addition to the quests assigned to each user, the quest database will manage the entire quest information in a separate area, and the field configuration for this area is not shown in FIG.

In the quest type field 600, identification information for determining whether the quest is a general quest, a quest delegated to another user, and a quest delegated from another user is recorded. For example, when a general quest is received through an NPC or a quest start item, the identification information of the quest is recorded as' 00 ', and when the general quest is delegated to another slave user, the identification information of the delegated quest is' 01 'is recorded, and quest information delegated from another master user is recorded as' 10'.

In the quest region field 602, region information on which the quest should be performed is recorded. The Quest Region field is one criterion for classifying quests, and other classification criteria may be used. In a typical RPG game, it is common to classify quests for each region of the map. However, quests may be classified by character's occupation or level.

In the quest ID field 604, preset identification information for uniquely identifying each quest is recorded.

In the level field 606, minimum level information capable of performing a quest is recorded. In general, an MMORPG game adopting a quest method sets minimum level information for performing a quest for each quest, and the information is recorded in the level field 606. Of course, if there is no level limit for the quest, the level field 606 may not be provided.

In the reward field 608, reward information preset for the quest is recorded. Compensation information originally set for the quest is recorded in the compensation field 608, and compensation information by a contract between the master user and the slave user is recorded in the proxy compensation field 614. When the slave user completes the quest, the master user is provided with the reward recorded in the reward field 608, and the slave user is provided with the reward recorded in the proxy reward field 614. If it is not a delegated quest, no information is recorded in the proxy reward field 614.

In the completion field 610, information about whether the user has completed the quest is recorded. In the case of a normal quest, when the user completes the quest, the completion information is recorded in the completion field 610. When the quest is delegated to the slave user, the completion information is recorded in the completion field 610 when the slave user completes the quest.

In the case of a quest in which another user is authorized to perform the quest, the master user or slave user information is recorded in the master / slave user field 612. In the above example, when the quest type is '01', that is, a quest delegated to the slave user by the master user, the slave user information is recorded in the master / slave user field 612. In the above example, when the quest type is '10', that is, a quest delegated by the slave user from the master user, the master user information is recorded in the master / slave user field 612.

7 is a flowchart illustrating the overall flow of a method of performing quest surrogate according to an embodiment of the present invention.

Referring to FIG. 7, the master user requests the quest to the quest server in a manner such as talking to an NPC or clicking a quest start item (step 700).

When the master user requests a quest, the quest server determines whether the master user satisfies a condition for performing the quest (step 702). For example, the quest execution condition may include the level of the user and whether the previous quest is completed. When the lowest level set for the requested quest is 45 levels, when a user who is less than 45 levels requests a quest, the quest server determines that the user cannot perform the quest. In addition, certain quests can be performed after completing the preceding quests. In the case of such a quest, the quest server determines whether the corresponding quest has been completed by the user. If the quest is not completed, the quest server determines that the quest cannot be performed by the user. In addition to the above-described quest execution conditions, there may be various quest execution conditions, and the determination may be made in the quest server. Of course, the determination of whether the quest can be performed may be made in the client program, not the quest server.

If the master user cannot perform the requested quest, the quest server or client program deactivates the quest providing procedure or provides a message indicating that the quest cannot be performed (step 704).

If the master user who requested the quest is a quest that can be performed, the quest server extracts the corresponding quest information and provides it to the master user (step 706). When the quest is provided to the master user, the provided quest information is added to the quest list of the master user, and the quest acquisition information of the master user is recorded in the quest database.

The master user who receives the quest may delegate the execution of the quest to another user through a conversation with another user or a market place. When the surrogate and reward terms of the quest are agreed through the conversation or the slave user accepts the surrogate of the quest through the marketplace, the slave user receives the quest packet from the master user or the quest server (step 708).

When the master user delegates the quest surrogate to the slave user, the delegated quest is added to the quest list of the slave user, and the slave user performs the quest (step 710).

The quest server or the client program monitors whether the slave user completes the quest, and when the slave user completes the quest, performs the reward processing preset to the master user and the slave user (step 716). As described above, the master user is provided with a reward set in game for the quest, and the slave user is preferably provided with a contract rewarded between the master user and the slave user. If the slave user fails to perform the quest or the slave user gives up the quest for the specified time, the quest server sends a quest execution failure message to the master user. If the master user is offline, the master server will be able to see quest failure messages when connecting to the game server.

FIG. 8A is a flowchart of a process in which a master user directly delegates a quest surrogate to a slave user without passing through a market place.

Referring to FIG. 8A, the master user selects a quest to delegate proxy performance (step 800). The quest may be selected using the quest list of the master user.

When the quest is selected, an interface screen as shown in FIG. 3A is provided to the master user, who inputs the ID of the slave user and negotiated reward information to be performed on behalf of the master. When the OK button is clicked on the entered information, the quest packet is sent to the slave user. 8 illustrates a case in which the quest packet is directly transmitted from the master user's client to the slave user's client, the quest packet may be transmitted to the slave user through the quest server or the game server.

10 is a diagram illustrating the structure of a quest packet according to an embodiment of the present invention.

Referring to FIG. 10, a quest packet according to an embodiment of the present invention includes a master user ID 1000, a slave user ID 1002, a quest ID 1004, a server ID 1006, a data size 1008, and a body. Data information 1010.

In FIG. 10, the server ID field 1006 records the ID address of the game server to which the current master user and slave user are connected.

In the data size field 1008, total size information of packet data is recorded. In the body data field 1010, contents of a quest and reward information input by the master user through the interface of FIG. 3A are recorded.

10 illustrates an example of a quest packet structure, and it will be apparent to those skilled in the art that the structure of the quest packet can be variously changed while achieving the same purpose as the present invention.

When the quest packet is transmitted to the slave user, the slave user is provided with an interface as shown in FIG. 3B. That is, the slave user can check the quest information requested by the master user and the reward information accordingly. If the slave user wants to perform the quest requested by the master user, the slave user accepts the quest surrogate through an interface such as a confirmation button (step 804).

If the slave user accepts the quest surrogate performance, the quest acceptance information is sent to the quest server (step 806), and the quest acceptance information is also sent to the master user via the quest server (step 808). Of course, the quest acceptance information may be sent directly to the master user without passing through the quest server.

If the slave user accepts the quest surrogate, the quest list of the slave user is updated to add a newly received quest (810).

If the slave user accepts the quest surrogate performance and the corresponding information is transmitted to the quest server, the quest server updates the quest information of the slave user and the master user (step 812). In addition, the quest list of the master user is further updated with information indicating that a specific quest is delegated to the slave user (step 814).

If the slave user accepts the quest, the slave user's client program or quest server monitors whether or not the quest has been accomplished (step 816), and the master user's client program or quest server delegates to the slave user. Release monitoring for the quest (step 818).

8B is a flowchart illustrating a process of delegating a quest surrogate to a slave user by a master user according to another embodiment of the present invention.

8B is a flowchart of a process in which a master user delegates a quest surrogate to a slave user through a market place.

Referring to FIG. 8B, the master user first accesses the market place and then selects a quest to delegate proxy performance (step 850).

The master user registers the selected quest in the market place and the registered information is sent to the quest server (step 852). When the master user registers the quest information to be delegated to other users, other users can check the quest delegation information as shown in FIG. 4 through the marketplace. In this case, unlike the packet of FIG. 10, the quest packet transmitted to the quest server will not include slave user information. The slave user who wants to perform the quest of the master user requests to perform the proxy for the registered quest (854).

The quest server determines whether the slave user who requested the quest surrogate meets the conditions for performing the quest (for example, whether the quest satisfies the minimum level for fulfilling the quest), and if the condition is satisfied, the slave Accept the user's quest surrogate request (step 856).

8B illustrates a process of registering a quest in a market place and a function of providing quest information registered in a market place to another user in a quest server, but a market place function for registering and inquiring a quest is a game. It may be provided by a server or another server. In this case, when the slave user requests to perform the quest surrogate registered in the market place, the server providing the market place function determines whether the slave user can perform the quest, and accepts the quest surrogate request of the slave user, and the quest acceptance information is requested. Provide it to the server.

When the quest server accepts the quest surrogate request from the slave user or receives quest acceptance information from another server, the quest server sends the quest acceptance information to the slave user and the master user (step 858).

After the quest server accepts the quest, the quest server reflects the information in the quest database that the quest of the master user is delegated to a specific slave user (step 860).

When the master user receives the quest acceptance information from the quest server, the master user's client program updates the master user's quest list (step 862). At this time, the quest list displays information that a specific quest is delegated to the corresponding slave user. In addition, the client program of the master user releases monitoring whether the master user performs the quest (step 866).

Upon receiving the quest acceptance information from the slave user's quest server, the slave user's client program initiates monitoring whether the slave user performs the quest (step 864).

9 is a flowchart illustrating a compensation process when a quest is performed according to an exemplary embodiment of the present invention.

Referring to FIG. 9, the client program of the slave user determines whether the slave user is in a quest execution state (operation 900). For example, in the case of a quest talking to a specific NPC, the client program determines whether the slave user enters the region where the NPC is located. The client program may provide a function of displaying the location of the NPC when the user enters an area where the corresponding NPC is located.

The client program monitors whether the slave user completes the available quest (step 902).

When the slave user completes the quest (step 904), the quest completion information is sent to the quest server (step 906). The quest server determines whether the slave user has completed the general quest or the quest delegated from the master user. According to an embodiment of the present invention, the quest completion information transmitted by the slave user may include information about whether the quest is delegated or a general quest.

When the slave user completes the quest delegated by the master user, the quest server extracts reward information to be provided to the master user and the slave user from the quest database (step 908).

The quest server transmits reward information to the slave user so that the slave user can check the reward according to the execution of the quest (step 910).

In addition, the quest server determines whether the master user of the quest performed by the slave user is online (step 912), and if the master user is online, transmits the quest completion information of the slave user to the master user in real time (step 914). .

The quest server records the quest completion information in the quest database and transmits reward information of the master user and the slave user to the account server (step 916). The account server updates the reward information of the master user and the slave user.

The quest server preferably provides information for the master user to confirm whether or not the quest of the slave user is completed.

FIG. 11 is a diagram illustrating a screen for checking a state of quests delegated to slave users by a master user according to an exemplary embodiment of the present invention.

As shown in FIG. 11, the master user is provided with a list of quests delegated to slave users and slave user information related to the quest, information on whether or not it is completed, and reward information upon completion. When the master user requests quest status information from the quest server, the quest server provides the master user with the information of the quest database.

As described above, according to the method and system for providing a quest proxy performing service in an online game according to the present invention, there is an advantage that users can grow their characters while mainly performing their preferred quests.

In addition, according to the present invention, even a user who does not have a lot of time, such as office workers has the advantage that can facilitate the character growth through the quest proxy.

In addition, quests and users also have the advantage of diversifying the economic system of online games by incorporating them into the trading target.

Although the above has been described with reference to a preferred embodiment of the present invention, those skilled in the art to which the present invention pertains without departing from the spirit and scope of the present invention as set forth in the claims below It will be appreciated that modifications and variations can be made.

Claims (20)

Providing an interface capable of delegating a specific quest possessed by a master user to at least one slave user; Storing quest acceptance information when at least one slave user accepts a master user's quest surrogate through the interface; And providing a reward to the master user and the slave user when the slave user who accepts the quest proxy execution completes the corresponding quest. The method of claim 1, And the interface comprises means for setting reward information to be provided to the slave user by the master user when the slave user completes the quest. The method of claim 2, The interface includes means for selecting a quest to delegate to a slave user; And And a means for inputting a slave user to perform the quest on behalf of, and when the master user inputs all the reward information, the quest to be delegated, and the slave user to perform the quest, a quest packet corresponding to the input information is assigned to the slave. Method for providing a quest surrogate service in the online game, characterized in that transmitted to the user. The method of claim 2, The interface further includes means for selecting a quest to be delegated to a slave user, and when the master user enters both the reward information and the quest information to be delegated, the input information is registered in the marketplace of the online game, and the other user Method for providing a quest agent performing service in an online game, characterized in that for selecting the quest to be performed on behalf of a master user using the information registered in the market place. The method of claim 4, wherein If a plurality of slave users want to perform the quests of the master users registered in the marketplace instead, the slave users who will perform the quests are determined by a competitive bidding method. . The method of claim 1, The reward that the master user provides to the slave user is determined by the agreement between the parties, the game user of the master user or a method of providing a quest surrogate service in the online game, characterized in that it comprises an item of the master user. The method of claim 6, When the slave user completes the quest of the master user, the master user is provided with a quest surrogate performance service in the online game, characterized in that the original reward provided when the quest is completed. The method of claim 1, The quest acceptance information includes a master user / slave user information associated with the accepted quest, quest identification information, and reward information provided by the master user to the slave user when the quest is completed. . The method of claim 1, When the slave user accepts the master user's quest surrogate, the client program or the quest server of the slave user monitors whether the slave user's quest completion service providing method in an online game. A game server for relaying game data transmitted from clients of a plurality of users and controlling game progress; An account server for managing user status information including game money and item information of users; Manages the quest information provided to the user, when at least one slave user accepts the quest surrogate request of the master user, receives and stores the quest surrogate performance acceptance information from the master or slave user, the slave user A quest surrogate performance service providing system in an online game comprising a quest server for rewarding the master user and the slave user when completing the master quest surrogate. The method of claim 10, When the slave user completes the quest surrogate of the master user, the quest server transmits the reward information of the master user and the slave user to the account server, and the account server corresponds to the reward information provided from the quest server. Quest surrogate performance service providing system in the online game, characterized in that for changing the state information of the master user and the slave user. The method of claim 10, The master user inputs a quest to be delegated to a slave user through a client program or an interface provided from the quest server, a slave user to perform a quest on behalf of the user, and a reward provided to the slave user when the quest is completed, and corresponds to the inputted information. A quest proxy performing service providing system in an online game, characterized in that a quest packet is generated from a client of a master user and transmitted to a corresponding slave user. The method of claim 10, The quest acceptance information, Quest-related master user / slave user information, quest identification information, and reward information provided by the master user to the slave user when the quest is performed, and upon receiving the quest acceptance information, the quest server receives the quest acceptance information from the quest database. Quest surrogate performance providing system in an online game, characterized in that reflected in. The method of claim 10, At least one of the game server or the quest server may include a market place module for registering a quest for which the master user requests to perform a proxy and providing a market place function for other users to view the registered quests. Quest surrogate service delivery system in the online game. The method of claim 10, When the slave user selects one of the quests registered in the market place and accepts the quest surrogate performance, the quest acceptance information is stored in the quest database. The method of claim 10, The reward that the master user provides to the slave user is determined by the contract between the parties, and the game user or quest proxy service providing system in the online game, characterized in that it comprises an item of the master user. The method of claim 16, When the slave user completes the quest of the master user, the master user is provided with a quest surrogate performance service system in the online game, characterized in that the original reward provided when the quest is completed. A combination of instructions executed in a user client terminal to provide a quest surrogate function in an online game is tangibly implemented, and is a recording medium recording a program that can be read by the client terminal. A quest proxy performing interface module for providing an interface for inputting slave user information to perform a quest on behalf of the user, quest information to be performed by the slave user, and reward information to be provided to the slave user when the quest of the slave user is completed; A quest packet generation module for generating a quest packet to be transmitted to the slave user using information input through the quest surrogate execution interface module; Includes a quest list management module for managing the information of the quests that the user received from the quest server or other users, And, when the slave user completes the quest, receiving the reward information according to the completion of the quest and the reward information to be provided to the slave user from the quest server. The method of claim 18, The reward that the master user provides to the slave user is determined by a contract between the parties, and includes a game money of the master user or an item of the master user. The method of claim 18, And the master user is provided with the original reward provided upon completion of the quest when the slave user completes the quest of the master user.

Images