Game task starting control method and device and electronic equipment

Abstract

The application provides a game task starting control method and device and electronic equipment; wherein the method comprises: receiving a starting instruction of a target game task, determining a plurality of game accounts participating in the target game task; judging whether the plurality of game accounts meet initial starting conditions of the target game task; if the plurality of game accounts meet the initial starting conditions, obtaining game records of the plurality of game accounts; based on the game records of the plurality of game accounts, determining a starting progress, sending a confirmation request containing the starting progress; if at least part of the game accounts receives a confirmation instruction for the confirmation request, based on the starting progress, starting the target game task. This way makes the player know the progress of the game to be started, and participates in the game on the premise of confirming the progress, so that the player can control the progress of participating in the game, avoids the progress of the task being contaminated without the player's knowledge, and improves the game experience.

Description

Technical Field

[0001] This invention relates to the field of game technology, and in particular to a method, apparatus, and electronic device for initiating game tasks. Background Technology

[0002] Some dungeon games require multiple players to team up. These games typically feature multiple quests, with player progress indicating which quests they've successfully completed or are currently tackling. Some quests require all players in the team to have the same progress level. If a player is unfamiliar with the quest's start conditions and has a low progress level, but joins a team preparing to start a higher-level quest, their progress will be synchronized with the current quest's progress. This contaminates the player's progress, preventing them from participating in the lower-level quest and missing out on its rewards. Simultaneously, directly participating in the higher-level quest results in a lower success rate, leading to significant frustration and negatively impacting the overall gaming experience. Summary of the Invention

[0003] In view of this, the purpose of the present invention is to provide a method, device and electronic device for starting game tasks, so as to avoid the task progress being contaminated without the player's knowledge and improve the game experience.

[0004] In a first aspect, embodiments of the present invention provide a method for controlling the launch of a game task. The method includes: receiving a launch instruction for a target game task; determining multiple game accounts participating in the target game task; determining whether the multiple game accounts meet the initial launch conditions of the target game task; wherein the initial launch conditions are determined based on at least one of the following: a preset launch time period for the target game task, a preset number of participations in the target game task, and account attributes of the game accounts; if the multiple game accounts meet the initial launch conditions, acquiring the game records of the multiple game accounts; wherein the game records include: the completion progress of the game accounts for the target game task; based on the game records of the multiple game accounts, determining the progress to be launched, and sending a confirmation request containing the progress to be launched to at least some of the multiple game accounts; if a confirmation instruction for the confirmation request is received from at least some of the game accounts, launching the target game task based on the progress to be launched.

[0005] Secondly, embodiments of the present invention provide a game task launch control device, the device comprising: an account determination module, configured to receive a launch instruction for a target game task and determine multiple game accounts participating in the target game task; a condition judgment module, configured to determine whether the multiple game accounts meet the initial launch conditions of the target game task; wherein the initial launch conditions are determined based on at least one of the following: a preset launch time period for the target game task, a preset number of participations in the target game task, and account attributes of the game accounts; a record acquisition module, configured to acquire game records of the multiple game accounts if the multiple game accounts meet the initial launch conditions; wherein the game records include: the completion progress of the game accounts for the target game task; a request sending module, configured to determine the launch progress based on the game records of the multiple game accounts and send a confirmation request containing the launch progress to at least some of the multiple game accounts; and a game launch module, configured to launch the target game task based on the launch progress if a confirmation instruction for the confirmation request is received from at least some of the game accounts.

[0006] Thirdly, embodiments of the present invention provide an electronic device, including a processor and a memory, wherein the memory stores computer-executable instructions that can be executed by the processor, and the processor executes the computer-executable instructions to implement the above-mentioned game task launch control method.

[0007] Fourthly, embodiments of the present invention provide a computer-readable storage medium storing computer-executable instructions. When the computer-executable instructions are invoked and executed by a processor, the computer-executable instructions cause the processor to implement the aforementioned game task startup control method.

[0008] The embodiments of the present invention bring the following beneficial effects:

[0009] The aforementioned game task initiation control method, device, and electronic device receive an initiation command for a target game task, identify multiple game accounts participating in the target game task, determine whether the multiple game accounts meet the initial initiation conditions of the target game task, wherein the initial initiation conditions are determined based on at least one of the following: a preset initiation time period for the target game task, a preset number of participations in the target game task, and the account attributes of the game accounts; if the multiple game accounts meet the initial initiation conditions, acquire the game records of the multiple game accounts, wherein the game records include: the completion progress of the game accounts for the target game task; based on the game records of the multiple game accounts, determine the progress to be initiated, and send a confirmation request containing the progress to be initiated to at least some of the multiple game accounts; if a confirmation instruction for the confirmation request is received from at least some of the game accounts, start the target game task based on the progress to be initiated. In this method, the progress to be initiated can be determined based on the game records of the game accounts in the team, and a confirmation request for the progress to be initiated can be sent to the game accounts. Only after receiving the confirmation instruction for the confirmation request will the game be started according to the progress to be initiated. This method allows players to clearly know the progress of the game they are about to start and participate in the game only after confirming the progress. Players can control the progress of their participation in the game and avoid their task progress being corrupted without their knowledge, thus improving the game experience.

[0010] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention are realized and obtained in accordance with the structures particularly pointed out in the description, claims and drawings.

[0011] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0012] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0013] Figure 1 A flowchart illustrating a game task launch control method provided in an embodiment of the present invention;

[0014] Figure 2 A flowchart for determining whether multiple game accounts meet the initial launch conditions of a target game task, provided as an embodiment of the present invention;

[0015] Figure 3 A flowchart for launching a target game task based on game records is provided as an embodiment of the present invention;

[0016] Figure 4 A schematic diagram of the structure of a game task launch control device provided in an embodiment of the present invention;

[0017] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0019] Some dungeon games require multiple players to team up. Players in the team may have different progress levels, but players unfamiliar with the game may find it difficult to know whether the current game progress they are about to participate in matches their own. If the current game progress is higher than the player's, the player's progress will be forced to match the current game progress. On the one hand, this will pollute the player's progress, preventing them from participating in lower-level game tasks and missing out on the rewards. On the other hand, directly participating in higher-level game tasks will result in a lower success rate in completing the task cards, leading to a strong sense of frustration for the player and affecting the game experience.

[0020] Furthermore, some dungeon games have a limited number of challenge attempts within a certain period of time, such as 3 challenge attempts per week. In this case, players may waste the challenge attempts for the current time period, affecting the player experience.

[0021] In another scenario, if the current game progress is lower than the player's game progress, the player's game progress will be forced to match the current game progress, abandoning the player's existing game progress, which will also affect the player's game experience.

[0022] Based on the above, the present invention provides a game task initiation control method, device, and electronic device, which can be applied to team-based games, dungeon games, or other games.

[0023] To facilitate understanding of this embodiment, a method for starting and controlling a game task disclosed in this embodiment of the invention will first be described in detail, such as... Figure 1As shown, the method for launching this game task can be implemented through a game server or through a terminal device. This method includes the following steps:

[0024] Step S102: Receive the start command for the target game task and identify the multiple game accounts participating in the target game task;

[0025] The graphical user interface for the target game mission is displayed on the player's terminal device. The graphical user interface can be set with controls such as "Enter Dungeon" and "Participate in Game". By clicking the control, the player can send the start command for the target game mission. When the start command is received, the server obtains multiple game accounts that will participate in the target game mission.

[0026] Each game account corresponds to one player, and multiple players participate in the target game task in a team. The target game task can be a level-based game, such as a strategy game or a puzzle game; the aforementioned start command can be triggered by a player from any of the multiple game accounts, or by a player from the game account that is the team leader.

[0027] Before sending the activation command, a team needs to be formed. For example, when multiple game accounts are logged into a designated game room, the player corresponding to one of the game accounts can trigger the aforementioned activation command. The number of game accounts can be determined according to the requirements of the target game task, such as 3-5 game accounts.

[0028] Step S104: Determine whether multiple game accounts meet the initial launch conditions of the target game task; wherein, the initial launch conditions are determined based on at least one of the following: the preset launch time period of the target game task, the preset number of times to participate in the target game task, and the account attributes of the game account.

[0029] Initial launch conditions can be set based on the requirements of the target game task. For example, the preset launch time of the target game task can be set in advance, such as 8:00-22:00 every day; the preset number of times to participate in the target game task can be set, such as a maximum of 3 times per player per week; the account attributes of the game account can also be set, such as the number of game accounts participating in one target game task, such as a minimum of 3 people; the level of the game account participating in the target game task, such as a minimum level of 5, etc. The account attributes can also include the faction to which the game account belongs.

[0030] If the initial launch conditions cannot be met, the target game task cannot be started. Specifically, if any one of the multiple game accounts does not meet the above initial launch conditions, the target game task cannot be started and subsequent steps cannot be executed; or, if all of the multiple game accounts does not meet the above initial launch conditions, the target game task cannot be started and subsequent steps cannot be executed.

[0031] Step S106: If multiple game accounts meet the initial launch conditions, obtain the game records of the multiple game accounts; wherein, the game records include: the completion progress of the game accounts for the target game task;

[0032] In this embodiment, after multiple game accounts meet the initial launch conditions, further processing is required based on the game records of these accounts to ensure that each player is aware of the progress of the target game task. Specifically, once the initial launch conditions are met, the game records of each game account can be obtained. The target game task may contain multiple game tasks or game levels. Taking a game task as an example, multiple game tasks need to be completed sequentially. The target game task may also contain multiple game levels, and each game level may contain multiple game tasks. Each game account's game record shows the game tasks or game levels that the account has completed, or the game tasks or game levels that the account needs to complete.

[0033] The game log can also record other game accounts that participated in a particular task with this game account. If a game account participates in the target game task for the first time, there may be no game log record.

[0034] Step S108: Based on the game records of multiple game accounts, determine the progress to be launched, and send a confirmation request containing the progress to be launched to at least some of the multiple game accounts;

[0035] Game records from multiple accounts may generate various data points. If the completion progress recorded in each account's game record is the same (e.g., all have completed task A), then the subsequent task B of task A can be considered as the pending progress. If the completion progress recorded in the game records of multiple accounts is not entirely the same (e.g., one account's completion progress is lower than the others), then the pending progress can be determined based on the lower completion progress, the higher completion progress, or even the first task or the first level of the target game task.

[0036] Once the start-up progress is determined, a confirmation request containing the start-up progress is sent to all or some of the game accounts across multiple game accounts. This confirmation request informs the player corresponding to the game account receiving the request of the progress of the target game task to be launched and sends an instruction on whether they agree to participate in the target game task at that progress. In one approach, the confirmation request containing the start-up progress is sent to all the game accounts across multiple game accounts; in another approach, the confirmation request is sent to game accounts whose start-up progress does not match the start-up progress. Here, "mismatch" can be understood as either the game account's completion progress being lower or higher than the start-up progress.

[0037] Step S110: If confirmation instructions for the confirmation request are received from at least some game accounts, the target game task is started based on the progress of the game to be started.

[0038] In one approach, if each game account that receives a confirmation request sends a confirmation instruction, it means that each game account agrees to participate in the target game task according to the progress of the game to be started. If all or some game accounts do not send confirmation instructions, or send rejection instructions, they cannot participate in the target game task according to the progress of the game to be started. In this case, the game accounts in the current team can be changed, or confirmation requests can be sent again to the game accounts that did not send confirmation instructions, until each game account that receives a confirmation request sends a confirmation instruction.

[0039] When a target game task is launched, the game client receives the game progress to be launched, loads the game resource file corresponding to the game progress to be launched, renders and displays the game scene corresponding to the game task where the game progress to be launched is located on the graphical user interface, and controls the game characters corresponding to multiple game accounts to enter the game scene to start the game task.

[0040] The aforementioned game task initiation control method involves receiving an initiation command for a target game task, identifying multiple game accounts participating in the target game task, determining whether the multiple game accounts meet the initial initiation conditions of the target game task, wherein the initial initiation conditions are determined based on at least one of the following: a preset initiation time period for the target game task, a preset number of participations in the target game task, and the account attributes of the game accounts; if the multiple game accounts meet the initial initiation conditions, acquiring the game records of the multiple game accounts, wherein the game records include: the completion progress of the game accounts for the target game task; based on the game records of the multiple game accounts, determining the progress to be initiated, and sending a confirmation request containing the progress to be initiated to at least some of the multiple game accounts; if a confirmation instruction for the confirmation request is received from at least some of the game accounts, starting the target game task based on the progress to be initiated. In this method, the progress to be initiated can be determined based on the game records of the game accounts in the team, and a confirmation request for the progress to be initiated can be sent to the game accounts. Only after receiving the confirmation instruction for the confirmation request will the game be started according to the progress to be initiated. This method allows players to clearly know the progress of the game they are about to start and participate in the game only after confirming the progress. Players can control the progress of their participation in the game and avoid their task progress being corrupted without their knowledge, thus improving the game experience.

[0041] In one specific implementation, the initial launch conditions specifically include at least one of the following: the time of sending the launch command is within the preset launch time period of the target game task; the number of accounts of multiple game accounts meets a preset quantity threshold; at least some of the game accounts among the multiple game accounts have an account level that meets a preset level threshold; and the remaining number of participations of a specified account among the multiple game accounts is greater than a preset number of participations threshold.

[0042] The time when the launch command is sent can be either the time when the player sends the launch command through their terminal device or the time when the launch command arrives at the game server. The preset launch time period for the target game task can be set based on game requirements; for example, the preset launch time period could be "Monday 12:00 to Sunday 23:00".

[0043] The aforementioned preset quantity threshold can be a minimum quantity or a quantity range. For example, the minimum quantity is 3, and when the number of game accounts is equal to or greater than 3, it can be considered that the quantity threshold is met; or the quantity range is 3-5, and when the number of game accounts is 3, 4 or 5, it can all be considered that the quantity threshold is met.

[0044] The aforementioned level threshold can be a minimum level, a maximum level, or a range of levels. In one approach, each of the multiple game accounts must meet the level threshold; alternatively, some of the game accounts may meet the level threshold. In another approach, the multiple game accounts are divided according to their role attributes, such as team leader and team member, with different level thresholds set for accounts with different role attributes.

[0045] The aforementioned threshold can be 0 times. A maximum number of participations per game account within a specified time period can be preset. Each time a target game task is participated in, the remaining participation count is reduced by 1. When a game account has 0 remaining participation counts, it cannot participate in the target game task again within that time period. The aforementioned designated account can be an account with specific identity attributes among multiple game accounts, such as the team leader; or it can be each of the multiple game accounts.

[0046] like Figure 2 As shown, the process can be automated to determine whether multiple game accounts meet the initial launch requirements, including the following steps:

[0047] Step S202: Determine that the time of sending the start command is within the preset start time period of the target game task;

[0048] If not, proceed to step S203, send the first information containing the preset start time period to the terminal device corresponding to the game account, and end; if yes, proceed to step S204.

[0049] Step S204: Determine if the number of multiple game accounts meets the preset number threshold;

[0050] If not, proceed to step S205, send the second information to the terminal device corresponding to the game account, the second information including the above-mentioned preset quantity threshold, and a prompt message indicating that the number of multiple game accounts does not meet the preset quantity threshold, and end; if yes, proceed to step S206.

[0051] Step S206: Determine whether the account level of at least some of the multiple game accounts meets the preset level threshold.

[0052] If not, proceed to step S207, send third information to the terminal device corresponding to the game account, the third information including the aforementioned preset level threshold and the game account that does not meet the level threshold, and end; if yes, proceed to step S208.

[0053] Step S208: Determine that the remaining number of times a specified account among multiple game accounts has more than a preset threshold number of times;

[0054] If not, proceed to step S209, determine that the aforementioned initial startup conditions are not met, refuse to start the target game task, and end; if yes, proceed to step S210, determine that the aforementioned initial startup conditions are met.

[0055] The following examples further describe how to determine the progress of startup.

[0056] In one approach, for the first game account among multiple game accounts, if any first game account has no game records, or if the game records of the first game accounts are different, the progress to be started is determined as the first task of the target game task; wherein, the first game account is the game account with the first designated identity; the target game task includes multiple tasks, which are arranged in order of completion, and the first task is the first task to be completed among the multiple tasks.

[0057] For example, if the first designated identity is a team member, then the first game account is a team member in a team composed of multiple game accounts. This first designated identity can also be a team leader, group leader, or other identities. If there is a first game account with no game history, this first game account may have never participated in the target game task. If the game history of multiple first game accounts differs, their game progress will differ. In this case, it is necessary to start participating in the target game task from the beginning, that is, from the first task of the target game task.

[0058] For level-based games, the target game mission includes multiple tasks arranged in a specific order, which players must complete sequentially. The aforementioned first task is the first task a player needs to complete when participating in the target game mission. If all first-player accounts have game records, and these records are identical, then subsequent judgment steps can proceed.

[0059] Specifically, if all first game accounts have game records and the game records of the first game accounts are the same, determine whether the second game account among the multiple game accounts has game records and whether the game records of the second game account are the same as the game records of the first game account; wherein, the second game account is a game account with a second designated identity; if the second game account has no game records, or the game records of the second game account are different from the game records of the first game account, determine the progress to be started as the first task of the target game task.

[0060] The second designated identity here is usually different from the aforementioned first designated identity. For example, when the first designated identity is a team member, the second designated identity is the team leader; when the first designated identity is the team leader, the second designated identity is a team member. When the second game account has game records, and the game records of the second game account are the same as those of the first game account, it can be understood that the game progress of multiple game accounts is the same. In this case, they can continue to participate in the target game task according to the game progress in their game records. If the second game account has no game records, or the game records of the second game account are different from those of the first game account, then all game accounts need to start participating in the target game task from the beginning, that is, the first task of the target game task to be started.

[0061] If the second game account has game records, and the game records of the second game account are the same as those of the first game account, obtain the progress generation time from the game records of the second game account; determine whether the time between the progress generation time and the current time is less than a preset time threshold; if the time is greater than the preset time threshold, determine the progress to be started as the first task of the target game task.

[0062] When all game accounts have identical game records, it's also necessary to determine if the second game account's task has timed out. Specifically, the second game account's game record shows the last completed game task and its completion time, which is the aforementioned progress generation time. To encourage players to complete the tasks in the target game task as quickly as possible, the game system can set a preset time threshold. When the time elapsed between the progress generation time and the current time is greater than or equal to the preset time threshold, it can be understood that the progress recorded in the second game account's game record has expired. In this case, it's necessary to start participating in the target game task from the beginning, i.e., the progress to be started is the first task of the target game task.

[0063] If the game duration exceeds a preset threshold, a task token is sent to the second game account and its historical teammates' accounts. The completion progress recorded in the second game account's game history is the result of joint participation by both the historical teammates' accounts and the second game account. The task token is used to distribute task rewards. In this scenario, if the time elapsed between the second game account's progress generation time and the current time exceeds the preset threshold, it indicates that the second game account's task has timed out. The second game account can no longer continue the target game task based on its recorded progress. To encourage players, a task token is sent to both the second game account and its historical teammates' accounts. Completed tasks recorded in the second game account are those completed jointly by the second game account and its historical teammates' accounts. Players can claim certain task rewards, such as items and coins, using the task token.

[0064] In another scenario, if the duration is less than or equal to a preset duration threshold, the progress to be started is determined based on the completion progress in the second game account's game history. In this case, the next task after a completed task recorded in the second game account's game history can be identified as the progress to be started. When the second game account is the team leader, it can lead other team members to continue participating in subsequent tasks of the target game mission based on the second game account's current progress.

[0065] When the startup progress determined in the aforementioned embodiments is different, the implementation method of sending a confirmation request containing the startup progress is also different.

[0066] Specifically, if any one of the multiple game accounts has no game history, or if the game history of the multiple game accounts is different, a confirmation request containing the progress of the game to be launched is sent to each of the multiple game accounts; or, if any one of the multiple game accounts has no game history, or if the game history of the multiple game accounts is different, a confirmation request containing the progress of the game to be launched is sent to the game account with game history.

[0067] In the above scenario, the game progress of multiple game accounts differs. In this case, the task to be started is the first task in the target game mission. In this situation, a confirmation request can be sent to each of the multiple game accounts so that every player in the team knows the progress of the target game mission. Alternatively, since the task to be started is the first task, players with game records need to abandon their game progress and start over from the first task. In this case, a confirmation request containing the progress to be started can be sent only to the game account with game records.

[0068] In another approach, if multiple game accounts have game records, and the game records of the multiple game accounts are identical, and the time elapsed between the progress generation time and the current time in the game record of the second game account is greater than a preset time elapsed threshold, a confirmation request containing the progress to be started is sent to each of the multiple game accounts; or, if multiple game accounts have game records, and the game records of the multiple game accounts are identical, and the time elapsed between the progress generation time and the current time in the game record of the second game account is greater than a preset time elapsed threshold, a confirmation request containing the progress to be started is sent to the game accounts other than the second game account.

[0069] In the above scenario, multiple game accounts have the same game progress, but the second game account's task has timed out. In this case, a confirmation request can be sent to each of the multiple game accounts so that every player in the team is aware of the pending progress of the target game task. Alternatively, since the pending task is the first task, and considering that game accounts other than the second game account have higher game progress, these players need to abandon their game progress and start over from the first task. In this case, a confirmation request containing the pending progress can be sent only to the game account with game records.

[0070] In another scenario, if multiple game accounts have game records, and the game records of the multiple game accounts are the same, and the time between the progress generation time and the current time in the game record of the second game account is less than or equal to a preset time threshold, a confirmation request containing the progress to be started is sent to the game accounts other than the second game account.

[0071] In this scenario, multiple game accounts have game records, and the game progress recorded in these records is identical. In this case, the task to be started is determined based on the game progress recorded in the game records. For example, if the game record shows that task A has been completed, then the task to be started could be the next task after task A, such as task B. This situation requires sending a confirmation request to all game accounts other than the second game account so that each player is aware of the task progress to be started.

[0072] After sending a confirmation request using the above method, if at least one rejection instruction is received in response to the confirmation request, the launch of the target game task will be stopped. If a rejection instruction is received, it can be understood that at least one game account refuses to participate in the game according to the pending launch progress. In this case, the game account that sent the rejection instruction can be replaced with another game account, or you can continue to send confirmation requests to that game account until you receive a confirmation instruction from the game account.

[0073] In one approach, detailed information indicating that a target game quest has been stopped from starting is sent to multiple game accounts; this detailed information includes the game account that sent the rejection command. This detailed information allows players to know which player has refused to participate in the target game quest from the pending progress, enabling players to make more informed decisions.

[0074] like Figure 3 As shown, this embodiment provides a determination step for starting the target game task based on game records after the aforementioned initial startup conditions are met. In this example, the first game account is specifically a team member's game account, and the second game account is the team leader's game account; it includes the following steps:

[0075] Step S301: Determine whether all team members' game accounts have game records, and whether the game records of the first game accounts are the same; if yes, proceed to step S302; if no, proceed to step S303.

[0076] Step S302: Determine whether all of the team leader's game accounts have game records, and whether the game records of the first game accounts are the same; if yes, proceed to step S304; if no, proceed to step S305.

[0077] Step S303: Determine the progress to be started as the first progress of the target game task; send confirmation requests to all game accounts; if confirmation instructions are received from all game accounts, start the target game task; if rejection instructions are received from any game account, end.

[0078] Step S304: Obtain the progress generation time from the game records of the second game account; determine whether the time elapsed between the progress generation time and the current time is less than a preset time threshold; if yes, proceed to step S306; if no, proceed to step S307.

[0079] Step S305: Determine the progress to be started as the first progress of the target game task; send confirmation requests to all game accounts; if confirmation instructions are received from all game accounts, start the target game task; if rejection instructions are received from any game account, send details of the game account that rejected starting the target game task to the other game accounts, and end.

[0080] Step S306: Based on the completion progress in the game record of the second game account, determine the progress to be started; send a confirmation request containing the progress to be started to the game accounts other than the second game account among the multiple game accounts; if confirmation instructions are received from all game accounts, start the target game task; if a rejection instruction is received from any game account, send the details of the game account that refused to start the target game task to the other game accounts, and end.

[0081] Step S307: Determine the progress to be started as the first progress of the target game task; send confirmation requests to all game accounts; if confirmation instructions are received from all game accounts, start the target game task; if rejection instructions are received from any game account, send details of the game account that rejected starting the target game task to the other game accounts, and end.

[0082] In related technologies, during multi-player team games, players may exit the game due to network outages or other uncontrollable factors, resulting in a poor team game experience. To address this issue, this embodiment provides a method for rejoining the game.

[0083] Specifically, after starting the target game task, the account identifiers of multiple game accounts participating in the target game task are recorded, and the game records of multiple game accounts are updated; if an application to participate in the target game task is received from an external game account, the application is rejected, and rejection information related to the external game account is sent to multiple game accounts; where the external game account is a game account other than the multiple game accounts.

[0084] Once the target game task is launched, the game accounts participating in the target game task will be recorded. Only the recorded game accounts can enter and participate in the target game task. When an unrecorded game account applies to participate in the target game task, the application will be rejected, and the relevant information of the game account in the target game task will be provided.

[0085] In another scenario, during the execution of the target game task, if a request to leave from a third game account among multiple game accounts is received, the account identifier group of multiple game accounts is saved; wherein the account identifier group includes the account identifier of each game account; the third game account is controlled to leave the target game task. If a request to enter the target game task from a third game account is received, it is determined that the account identifier of the third game account belongs to the account identifier group, and the third game scene is controlled to enter the target game task.

[0086] Because the system records the account identifiers of those who jointly participate in the target game mission, when a third game account leaves midway and then applies to rejoin, it can be controlled to re-enter the target game mission. This method allows players to return to the game after accidentally leaving, improving the gaming experience of team games.

[0087] In practice, when a player issues a leave command while participating in a target game mission, a confirmation dialog box usually pops up for the player to confirm before leaving. Taking a third game account as an example, when the third game account requests to re-enter the game, it needs to wait for the remaining game accounts in the target game mission to finish their battles before the team leader game account brings the third game account back into the target game mission.

[0088] If the team leader's account leaves during the target game mission, the remaining game accounts in the target game mission can continue to participate in the target game mission. After the game ends, the game result is recorded, and the remaining game accounts are informed that the team leader's account has left, the team has been disbanded, and they need to form a new team to enter the game.

[0089] In one specific implementation, the team leader's game account can trigger a return to the game. The game log records the team leader's game account's progress from the last time they participated in the target game task, as well as the teammate game accounts. After the team leader's game account forms a team, if any game account is not recorded in the game log, the target game task needs to be restarted; if all game accounts in the team are recorded in the game log, and the team leader's task has not expired, they can return to the target game task according to the progress in the game log; if the timeout has occurred, the target game task needs to be restarted.

[0090] For the corresponding method embodiments described above, see [link to relevant documentation]. Figure 4 The diagram shows a structural schematic of a game task activation control device, which includes:

[0091] The account identification module 40 is used to receive the start command of the target game task and identify multiple game accounts participating in the target game task.

[0092] The condition judgment module 42 is used to determine whether multiple game accounts meet the initial start conditions of the target game task; wherein, the initial start conditions are determined based on at least one of the following: the preset start time period of the target game task, the preset number of times to participate in the target game task, and the account attributes of the game account.

[0093] The record acquisition module 44 is used to acquire the game records of multiple game accounts if multiple game accounts meet the initial launch conditions; wherein, the game records include: the completion progress of the game accounts for the target game task;

[0094] The request sending module 46 is used to determine the progress to be started based on the game records of multiple game accounts, and send a confirmation request containing the progress to be started to at least some of the multiple game accounts.

[0095] The game launch module 48 is used to launch the target game task based on the progress of the game to be launched if a confirmation instruction for the confirmation request is received from at least some game accounts.

[0096] The aforementioned game task activation control device receives an activation command for the target game task, identifies multiple game accounts participating in the target game task, and determines whether the multiple game accounts meet the initial activation conditions of the target game task. The initial activation conditions are determined based on at least one of the following: a preset activation time period for the target game task, a preset number of participations in the target game task, and the account attributes of the game accounts. If the multiple game accounts meet the initial activation conditions, the device acquires the game records of the multiple game accounts. The game records include the game accounts' progress towards the target game task. Based on the game records of the multiple game accounts, the device determines the progress to be activated and sends a confirmation request containing the progress to be activated to at least some of the multiple game accounts. If a confirmation instruction for the confirmation request is received from at least some of the game accounts, the target game task is activated based on the progress to be activated. In this method, the progress to be activated can be determined based on the game records of the game accounts in the team, and a confirmation request for the progress to be activated can be sent to the game accounts. Only after receiving the confirmation instruction for the confirmation request will the game be activated according to the progress to be activated. This method allows players to clearly know the progress of the game they are about to start and participate in the game only after confirming the progress. Players can control the progress of their participation in the game and avoid their task progress being corrupted without their knowledge, thus improving the game experience.

[0097] The aforementioned initial launch conditions specifically include at least one of the following: the launch command is sent within the preset launch time period of the target game task; the number of accounts of multiple game accounts meets a preset quantity threshold; at least some of the game accounts among the multiple game accounts meet a preset level threshold; and the remaining participation count of a specified account among the multiple game accounts is greater than a preset number of participations threshold.

[0098] The aforementioned request sending module is further configured to: for the first game account among multiple game accounts, if any first game account has no game record, or if the game records of the first game accounts are different, determine the progress to be started as the first task of the target game task; wherein, the first game account is a game account with a first designated identity; the target game task includes multiple tasks, the multiple tasks are arranged in order of completion, and the first task is the first task to be completed among the multiple tasks.

[0099] The aforementioned device further includes a first determining module, configured to: if all first game accounts have game records and the game records of the first game accounts are identical, determine whether a second game account among the multiple game accounts has game records and the game records of the second game account are identical to the game records of the first game account; wherein, the second game account is a game account with a second designated identity; if the second game account has no game records, or the game records of the second game account are different from the game records of the first game account, determine the progress to be started as the first task of the target game task.

[0100] The aforementioned device further includes a second determining module, configured to: if the second game account has game records and the game records of the second game account are the same as those of the first game account, obtain the progress generation time from the game records of the second game account; determine whether the time elapsed between the progress generation time and the current time is less than a preset time elapsed threshold; if the time elapsed is greater than the preset time elapsed threshold, determine the progress to be started as the first task of the target game task.

[0101] The aforementioned device also includes a third determining module, used to: if the duration is less than or equal to a preset duration threshold, determine the progress to be started based on the completion progress in the game record of the second game account.

[0102] The aforementioned device also includes a credential sending module, used to: send a task credential to the second game account and the historical teammate accounts of the second game account if the duration exceeds a preset duration threshold; wherein, the completion progress in the game record of the second game account is obtained by the historical teammate accounts and the second game account participating in the game together; the task credential is used to: distribute task rewards.

[0103] The aforementioned request sending module is further configured to: send a confirmation request containing the pending start progress to each of the multiple game accounts if any one of the multiple game accounts has no game records, or if the game records of the multiple game accounts are different; or, if any one of the multiple game accounts has no game records, or if the game records of the multiple game accounts are different, send a confirmation request containing the pending start progress to the game account with game records.

[0104] The aforementioned request sending module is further configured to: if multiple game accounts have game records, and the game records of the multiple game accounts are identical, and the time elapsed between the progress generation time and the current time in the game record of the second game account is greater than a preset time elapsed threshold, send a confirmation request containing the progress to be started to each of the multiple game accounts; or, if multiple game accounts have game records, and the game records of the multiple game accounts are identical, and the time elapsed between the progress generation time and the current time in the game record of the second game account is greater than a preset time elapsed threshold, send a confirmation request containing the progress to be started to the game accounts other than the second game account among the multiple game accounts.

[0105] The aforementioned request sending module is further configured to: if multiple game accounts have game records, and the game records of the multiple game accounts are the same, and the time between the progress generation time and the current time in the game record of the second game account is less than or equal to a preset time threshold, send a confirmation request containing the pending start progress to the game accounts other than the second game account among the multiple game accounts.

[0106] The aforementioned device also includes a stop module for: stopping the startup of the target game task if at least one rejection instruction for a confirmation request is received.

[0107] The aforementioned device also includes an information sending module, used to: send detailed information about the target game task stopping its startup to multiple game accounts; wherein the detailed information includes: the game account that sent the rejection command.

[0108] The aforementioned device also includes an application rejection module, used to: record the account identifiers of multiple game accounts participating in the target game task, and update the game records of the multiple game accounts; if an application to participate in the target game task is received from an external game account, the application to participate is rejected, and rejection information related to the external game account is sent to the multiple game accounts; wherein, the external game account is a game account other than the multiple game accounts.

[0109] The aforementioned device also includes an exit control module, used for: during the execution of the target game task, if an exit request is received from a third game account among multiple game accounts, saving an account identifier group of multiple game accounts; wherein the account identifier group includes the account identifier of each game account; and controlling the third game account to exit the target game task.

[0110] The aforementioned device also includes an entry control module, used to: if an entry request from a third game account to enter the target game task is received, determine that the account identifier of the third game account belongs to the account identifier group, and control the third game scene to enter the target game task.

[0111] This embodiment also provides an electronic device, including a processor and a memory. The memory stores computer-executable instructions that can be executed by the processor. The processor executes the computer-executable instructions to implement the aforementioned game task launch control method. This electronic device can be a server or a terminal device.

[0112] See Figure 5 As shown, the electronic device includes a processor 100 and a memory 101. The memory 101 stores computer-executable instructions that can be executed by the processor 100. The processor 100 executes the computer-executable instructions to implement the above-mentioned game task launch control method.

[0113] Furthermore, Figure 5 The electronic device shown also includes a bus 102 and a communication interface 103, with the processor 100, the communication interface 103 and the memory 101 connected via the bus 102.

[0114] The memory 101 may include high-speed random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Communication between this system network element and at least one other network element is achieved through at least one communication interface 103 (which can be wired or wireless), such as the Internet, wide area network, local area network, or metropolitan area network. The bus 102 may be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 5 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0115] Processor 100 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of processor 100 or by instructions in software form. Processor 100 may be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this invention. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this invention can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software module can reside in a readily available storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory 101, and the processor 100 reads the information from memory 101 and, in conjunction with its hardware, completes the steps of the method described in the foregoing embodiments.

[0116] The processor in the aforementioned electronic device, by executing computer-executable instructions, can perform the following operations in the aforementioned game task launch control method:

[0117] The system receives a start command for a target game task and identifies multiple game accounts participating in the target game task. It then determines whether the multiple game accounts meet the initial start conditions for the target game task. These initial start conditions are determined based on at least one of the following: a preset start time period for the target game task, a preset number of participations in the target game task, and the account attributes of the game accounts. If the multiple game accounts meet the initial start conditions, the system obtains the game records of the multiple game accounts. These game records include the game accounts' progress towards the target game task. Based on the game records of the multiple game accounts, the system determines the progress to be started and sends confirmation requests containing the progress to be started to at least some of the multiple game accounts. If confirmation commands are received from at least some of the game accounts in response to the confirmation requests, the system starts the target game task based on the progress to be started.

[0118] The initial launch conditions specifically include at least one of the following: the launch command is sent within the preset launch time period of the target game task; the number of accounts of multiple game accounts meets the preset number threshold; at least some of the game accounts among the multiple game accounts meet the preset level threshold; and the remaining number of participation attempts of the specified account among the multiple game accounts is greater than the preset number of participation attempts threshold.

[0119] For the first game account among multiple game accounts, if any first game account has no game records, or if the game records of the first game accounts are different, the progress to be started is determined as the first task of the target game task; wherein, the first game account is the game account with the first designated identity; the target game task includes multiple tasks, which are arranged in order of completion, and the first task is the first task to be completed among the multiple tasks.

[0120] If all first game accounts have game records, and the game records of the first game accounts are the same, determine whether the second game account among the multiple game accounts has game records, and whether the game records of the second game account are the same as the game records of the first game account; wherein, the second game account is a game account with a second designated identity; if the second game account has no game records, or the game records of the second game account are different from the game records of the first game account, determine the progress to be started as the first task of the target game task.

[0121] If the second game account has game records, and the game records of the second game account are the same as those of the first game account, obtain the progress generation time from the game records of the second game account; determine whether the time between the progress generation time and the current time is less than a preset time threshold; if the time is greater than the preset time threshold, determine the progress to be started as the first task of the target game task.

[0122] If the duration is less than or equal to the preset duration threshold, the progress to be started is determined based on the completion progress in the game record of the second game account.

[0123] If the duration exceeds a preset duration threshold, a task token is sent to the second game account and the historical teammate accounts of the second game account. The completion progress in the game record of the second game account is obtained by the historical teammate accounts and the second game account participating in the game together. The task token is used to distribute task rewards.

[0124] If any one of the multiple game accounts has no game history, or if the game history of the multiple game accounts is different, send a confirmation request containing the progress of the game to be started to each of the multiple game accounts; or, if any one of the multiple game accounts has no game history, or if the game history of the multiple game accounts is different, send a confirmation request containing the progress of the game to be started to the game account with game history.

[0125] If multiple game accounts have game records, and the game records of the multiple game accounts are the same, and the time elapsed since the progress generation time in the game record of the second game account is greater than a preset time elapsed threshold, send a confirmation request containing the progress to be started to each of the multiple game accounts; or, if multiple game accounts have game records, and the game records of the multiple game accounts are the same, and the time elapsed since the progress generation time in the game record of the second game account is greater than a preset time elapsed threshold, send a confirmation request containing the progress to be started to all game accounts except the second game account.

[0126] If multiple game accounts have game records, and the game records of the multiple game accounts are the same, and the time between the progress generation time and the current time in the game record of the second game account is less than or equal to a preset time threshold, a confirmation request containing the progress to be started is sent to the game accounts other than the second game account.

[0127] If at least one rejection instruction is received for the confirmation request, stop launching the target game mission.

[0128] Send detailed information about stopping the target game mission to multiple game accounts; the details include the game account that sent the rejection command.

[0129] Record the account identifiers of multiple game accounts participating in the target game task and update the game records of multiple game accounts; if a participation application for the target game task is received from an external game account, reject the participation application and send rejection information related to the external game account to multiple game accounts; where the external game account is a game account other than the multiple game accounts.

[0130] During the execution of the target game task, if a request to leave from a third game account among multiple game accounts is received, the account identifier group of multiple game accounts is saved; wherein, the account identifier group includes the account identifier of each game account; and the third game account is controlled to leave the target game task.

[0131] If a request is received from a third game account to enter the target game task, determine that the account identifier of the third game account belongs to the account identifier group, and control the third game scene to enter the target game task.

[0132] In the above method, the game's progress to be launched can be determined based on the game records of the accounts in the team. A confirmation request for this progress is then sent to the game account. Only after receiving confirmation of this request will the game be launched according to the planned progress. This method allows players to clearly know the progress of the game to be launched and participate in the game only after confirming the progress. Players can control their participation in the game and avoid their progress being corrupted without their knowledge, thus improving the gaming experience.

[0133] This embodiment also provides a computer-readable storage medium storing computer-executable instructions. When the computer-executable instructions are called and executed by a processor, the computer-executable instructions cause the processor to implement the above-mentioned game task startup control method.

[0134] The computer-executable instructions stored in the aforementioned computer-readable storage medium can, by executing the aforementioned computer-executable instructions, perform the following operations in the game task startup control method:

[0135] The system receives a start command for a target game task and identifies multiple game accounts participating in the target game task. It then determines whether the multiple game accounts meet the initial start conditions for the target game task. These initial start conditions are determined based on at least one of the following: a preset start time period for the target game task, a preset number of participations in the target game task, and the account attributes of the game accounts. If the multiple game accounts meet the initial start conditions, the system obtains the game records of the multiple game accounts. These game records include the game accounts' progress towards the target game task. Based on the game records of the multiple game accounts, the system determines the progress to be started and sends confirmation requests containing the progress to be started to at least some of the multiple game accounts. If confirmation commands are received from at least some of the game accounts in response to the confirmation requests, the system starts the target game task based on the progress to be started.

[0136] The initial launch conditions specifically include at least one of the following: the launch command is sent within the preset launch time period of the target game task; the number of accounts of multiple game accounts meets the preset number threshold; at least some of the game accounts among the multiple game accounts meet the preset level threshold; and the remaining number of participation attempts of the specified account among the multiple game accounts is greater than the preset number of participation attempts threshold.

[0137] For the first game account among multiple game accounts, if any first game account has no game records, or if the game records of the first game accounts are different, the progress to be started is determined as the first task of the target game task; wherein, the first game account is the game account with the first designated identity; the target game task includes multiple tasks, which are arranged in order of completion, and the first task is the first task to be completed among the multiple tasks.

[0138] If all first game accounts have game records, and the game records of the first game accounts are the same, determine whether the second game account among the multiple game accounts has game records, and whether the game records of the second game account are the same as the game records of the first game account; wherein, the second game account is a game account with a second designated identity; if the second game account has no game records, or the game records of the second game account are different from the game records of the first game account, determine the progress to be started as the first task of the target game task.

[0139] If the second game account has game records, and the game records of the second game account are the same as those of the first game account, obtain the progress generation time from the game records of the second game account; determine whether the time between the progress generation time and the current time is less than a preset time threshold; if the time is greater than the preset time threshold, determine the progress to be started as the first task of the target game task.

[0140] If the duration is less than or equal to the preset duration threshold, the progress to be started is determined based on the completion progress in the game record of the second game account.

[0141] If the duration exceeds a preset duration threshold, a task token is sent to the second game account and the historical teammate accounts of the second game account. The completion progress in the game record of the second game account is obtained by the historical teammate accounts and the second game account participating in the game together. The task token is used to distribute task rewards.

[0142] If any one of the multiple game accounts has no game history, or if the game history of the multiple game accounts is different, send a confirmation request containing the progress of the game to be started to each of the multiple game accounts; or, if any one of the multiple game accounts has no game history, or if the game history of the multiple game accounts is different, send a confirmation request containing the progress of the game to be started to the game account with game history.

[0143] If multiple game accounts have game records, and the game records of the multiple game accounts are the same, and the time elapsed since the progress generation time in the game record of the second game account is greater than a preset time elapsed threshold, send a confirmation request containing the progress to be started to each of the multiple game accounts; or, if multiple game accounts have game records, and the game records of the multiple game accounts are the same, and the time elapsed since the progress generation time in the game record of the second game account is greater than a preset time elapsed threshold, send a confirmation request containing the progress to be started to all game accounts except the second game account.

[0144] If multiple game accounts have game records, and the game records of the multiple game accounts are the same, and the time between the progress generation time and the current time in the game record of the second game account is less than or equal to a preset time threshold, a confirmation request containing the progress to be started is sent to the game accounts other than the second game account.

[0145] If at least one rejection instruction is received for the confirmation request, stop launching the target game mission.

[0146] Send detailed information about stopping the target game mission to multiple game accounts; the details include the game account that sent the rejection command.

[0147] Record the account identifiers of multiple game accounts participating in the target game task and update the game records of multiple game accounts; if a participation application for the target game task is received from an external game account, reject the participation application and send rejection information related to the external game account to multiple game accounts; where the external game account is a game account other than the multiple game accounts.

[0148] During the execution of the target game task, if a request to leave from a third game account among multiple game accounts is received, the account identifier group of multiple game accounts is saved; wherein, the account identifier group includes the account identifier of each game account; and the third game account is controlled to leave the target game task.

[0149] If a request is received from a third game account to enter the target game task, determine that the account identifier of the third game account belongs to the account identifier group, and control the third game scene to enter the target game task.

[0150] In the above method, the game's progress to be launched can be determined based on the game records of the accounts in the team. A confirmation request for this progress is then sent to the game account. Only after receiving confirmation of this request will the game be launched according to the planned progress. This method allows players to clearly know the progress of the game to be launched and participate in the game only after confirming the progress. Players can control their participation in the game and avoid their progress being corrupted without their knowledge, thus improving the gaming experience.

[0151] The computer program products of the game task launch control method, apparatus and electronic device provided in the embodiments of the present invention include a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the methods described in the preceding method embodiments. For specific implementation, please refer to the method embodiments, which will not be repeated here.

[0152] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the system and apparatus described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0153] Furthermore, in the description of the embodiments of the present invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in the present invention based on the specific circumstances.

[0154] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0155] In the description of this invention, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing the invention and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0156] Finally, it should be noted that the above embodiments are merely specific implementations of the present invention, used to illustrate the technical solutions of the present invention, and not to limit it. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments within the technical scope disclosed in the present invention, or make equivalent substitutions for some of the technical features; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for controlling the initiation of a game task, characterized in that, The method includes: Receive the start command for the target game task and identify multiple game accounts participating in the target game task; Determine whether the plurality of game accounts meet the initial launch conditions of the target game task; wherein the initial launch conditions are determined based on at least one of the following: the preset launch time period of the target game task, the preset number of times to participate in the target game task, and the account attributes of the game account; If the multiple game accounts meet the initial launch conditions, obtain the game records of the multiple game accounts; wherein, the game records include: the completion progress of the game account for the target game task; Based on the game records of the multiple game accounts, a startup progress is determined; a confirmation request containing the startup progress is sent to at least some of the multiple game accounts; wherein, if all the multiple game accounts have game records, and the game records of the multiple game accounts are the same, and in the game record of the second game account, the time elapsed since the progress generation time is less than or equal to a preset time threshold, a confirmation request containing the startup progress is sent to the game accounts other than the second game account; the second game account is a game account with a second designated identity; If a confirmation instruction is received from at least some of the game accounts in response to the confirmation request, the target game task is started based on the pending startup progress.

2. The method according to claim 1, characterized in that, The initial startup conditions specifically include at least one of the following: The start command is sent within a preset start time period of the target game task; The number of the multiple game accounts meets the preset number threshold; At least some of the game accounts among the plurality of game accounts have account levels that meet a preset level threshold. The remaining number of times a specified account among the multiple game accounts is greater than a preset threshold.

3. The method according to claim 1, characterized in that, The steps for determining the progress to be launched based on the game records of the multiple game accounts include: For the first game account among the plurality of game accounts, if any of the first game accounts has no game record, or if the game records of the first game accounts are different, the progress to be started is determined to be the first task of the target game task; The first game account is a game account with a first designated identity; the target game task includes multiple tasks, which are arranged in order of completion, and the first task is the first task to be completed among the multiple tasks.

4. The method according to claim 3, characterized in that, The method further includes: If all the first game accounts have game records, and the game records of the first game accounts are the same, determine whether the second game account among the multiple game accounts has the game records, and whether the game records of the second game account are the same as the game records of the first game account; If the second game account does not have the game record, or the game record of the second game account is different from the game record of the first game account, the progress to be started is determined to be the first task of the target game task.

5. The method according to claim 4, characterized in that, The method further includes: If the second game account has game records, and the game records of the second game account are the same as those of the first game account, obtain the progress generation time from the game records of the second game account; Determine whether the time elapsed between the progress generation time and the current time is less than a preset time threshold; If the duration exceeds the preset duration threshold, the progress to be started is determined to be the first task of the target game task.

6. The method according to claim 5, characterized in that, The method further includes: If the duration is less than or equal to the preset duration threshold, the progress to be started is determined based on the completion progress in the game record of the second game account.

7. The method according to claim 5, characterized in that, The method further includes: If the duration exceeds the preset duration threshold, a task credential is sent to the second game account and the historical teammate accounts of the second game account; wherein, the completion progress in the game record of the second game account is obtained by the historical teammate accounts and the second game account participating in the game together; the task credential is used to: issue task rewards.

8. The method according to claim 1, characterized in that, The step of sending a confirmation request containing the pending startup progress to at least some of the plurality of game accounts includes: If any of the multiple game accounts has no game records, or if the game records of the multiple game accounts are different, a confirmation request containing the pending start progress is sent to each of the multiple game accounts; or, If any of the multiple game accounts has no game history, or if the game history of the multiple game accounts is different, a confirmation request containing the pending start progress is sent to the game account with game history.

9. The method according to claim 1, characterized in that, The step of sending a confirmation request containing the pending startup progress to at least some of the plurality of game accounts includes: If all the multiple game accounts have game records, and the game records of the multiple game accounts are the same, and the time elapsed between the progress generation time and the current time in the game record of the second game account is greater than a preset time threshold, a confirmation request containing the progress to be started is sent to each of the multiple game accounts. or, If all the multiple game accounts have game records, and the game records of the multiple game accounts are the same, and the time elapsed between the progress generation time and the current time in the game record of the second game account is greater than a preset time elapsed threshold, a confirmation request containing the pending progress is sent to the game accounts other than the second game account among the multiple game accounts.

10. The method according to claim 1, characterized in that, The method further includes: If at least one rejection instruction is received for the confirmation request, the launch of the target game task is stopped.

11. The method according to claim 10, characterized in that, If at least one rejection instruction is received for the confirmation request, after stopping the step of starting the target game task, the method further includes: Send detailed information about stopping the target game task from starting to the multiple game accounts; wherein, the detailed information includes: the game account that sent the rejection command.

12. The method according to claim 1, characterized in that, If a confirmation instruction for the confirmation request is received from at least some of the game accounts, and the step of starting the target game task based on the pending progress is followed, the method further includes: Record the account identifiers of the multiple game accounts participating in the target game task, and update the game records of the multiple game accounts; If a participation request for the target game task is received from an external game account, the participation request is rejected, and rejection information related to the external game account is sent to the multiple game accounts; wherein, the external game account is a game account other than the multiple game accounts.

13. The method according to claim 1, characterized in that, If a confirmation instruction for the confirmation request is received from at least some of the game accounts, and the step of starting the target game task based on the pending progress is followed, the method further includes: During the execution of the target game task, if a request to leave is received from a third game account among the multiple game accounts, the account identifier group of the multiple game accounts is saved; wherein, the account identifier group includes the account identifier of each game account; Control the third game account to leave the target game task.

14. The method according to claim 13, characterized in that, After the step of controlling the third game account to leave the target game task, the method further includes: If an entry request is received from the third game account to enter the target game task, it is determined that the account identifier of the third game account belongs to the account identifier group, and the third game account is controlled to enter the target game task.

15. A game task initiation control device, characterized in that, The device includes: The account determination module is used to receive the start command of the target game task and determine the multiple game accounts participating in the target game task; The condition judgment module is used to determine whether the plurality of game accounts meet the initial launch conditions of the target game task; wherein the initial launch conditions are determined based on at least one of the following: the preset launch time period of the target game task, the preset number of times to participate in the target game task, and the account attributes of the game account; The record acquisition module is used to acquire the game records of the multiple game accounts if the multiple game accounts meet the initial launch conditions; wherein, the game records include: the completion progress of the game account for the target game task; A request sending module is configured to determine the launch progress based on the game records of the multiple game accounts, and send a confirmation request containing the launch progress to at least a portion of the multiple game accounts; wherein, if all the multiple game accounts have game records, and the game records of the multiple game accounts are the same, and the time elapsed between the progress generation time and the current time in the game record of the second game account is less than or equal to a preset time elapsed threshold, a confirmation request containing the launch progress is sent to the game accounts other than the second game account among the multiple game accounts; the second game account is a game account with a second designated identity; The game launch module is used to launch the target game task based on the pending launch progress if it receives a confirmation instruction from at least some of the game accounts in response to the confirmation request.

16. An electronic device, characterized in that, The system includes a processor and a memory, the memory storing computer-executable instructions that can be executed by the processor, the processor executing the computer-executable instructions to implement the game task launch control method according to any one of claims 1-14.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when invoked and executed by a processor, cause the processor to implement the game task launch control method according to any one of claims 1-14.

Images