Task fixed-point scene automatic recovery method and device, electronic equipment and medium

Abstract

The application provides a task freeze scene automatic recovery method and device, electronic equipment and medium, the task freeze scene automatic recovery method comprises the following steps: obtaining a second task sequentially executed in a freeze scene, combining the second task to obtain a first task; determining the freeze state of each second task according to the task event group corresponding to the second task, the task event group is used for representing the event behavior associated with the freeze state, according to the interruption time node of the task freeze scene, the second task freeze state corresponding to the interruption time node is found, and the recovery of the task freeze scene is performed. The beneficial effects of the application are that the number of freeze scenes that need to be recovered in the task is greatly reduced, and the state in each scene is as simple as possible; the error-prone and unpredictable nature of the recovery content is effectively reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer games, and particularly relates to a task freeze scene automatic recovery method and device, electronic equipment and medium. BACKGROUND

[0002] There is a task system implemented in the game to provide players with game content experience of a specific process, and to support interruption of the experience process at any progress and resumption of the progress at any time to continue the experience, for example, a player leaves the game during a complex performance experience task, and when the player logs in next time, all related scene arrangements, NPC states and positions, special effects and other task performances of the task progress or the adjacent task progress of the player at the offline time need to be restored.

[0003] In the existing basic task system, a planner needs to configure the actual performance content of each task, and separately configure all the contents to be restored for each task. The player can experience the task content according to the normal process according to the planner's configuration content, and when re-entering after interrupting the task process, the experience environment is restored according to the planner's configuration and the experience process is continued.

[0004] In the original recovery scheme depending on the planner's configuration, the restored content depends on the planner's manual configuration, and such scene recovery has the following defects:

[0005] (1) Complexity. The number of tasks in the game is large and the content is complex, usually a large number of NPCs are involved in a continuous performance, and the performance is composed of multiple tasks, and the player may interrupt at any task in the middle, which increases the number of scenes to be restored, and the content to be restored for each task is numerous and complex.

[0006] (2) Uncertainty. The performance content in the game is complex and most of them belong to dynamic performance, which also leads to uncertainty of the environment in which the player character is located during the transition between two tasks due to different completion times of the tasks by the player.

[0007] (3) Error-prone. Since the recovery content of the task is numerous and complex, the manual configuration is extremely unreliable, and the recovery content needs to be maintained synchronously every time the task content is modified, and such high-frequency modification greatly increases the probability of errors.

[0008] (4) Unpredictability. The manually configured content usually needs to be tested under various conditions to verify its correctness and completeness to prevent unexpected situations in different operations. In a complex and unpredictable actual environment such as a network game, the cost required for covering tests on a large number of tasks is unbearable, which also leads to the unreliability of the recovery content configured by humans. SUMMARY

[0009] The main purpose of the embodiment of the present application is to provide a task freeze scene automatic recovery method, device, electronic equipment and medium, which reduces the system resource consumption of freeze scene recovery, reduces the error-prone and unpredictability of the recovered content.

[0010] One aspect of the present application provides a task freeze scene automatic recovery method, characterized in that it comprises:

[0011] Obtaining a second task executed in sequence in a freeze scene, and combining the second task to obtain a first task;

[0012] According to the task event group corresponding to the second task, determining the freeze state of each second task, and the task event group is used to represent the event behavior associated with the freeze state;

[0013] According to the interruption time node of the task freeze scene, finding the second task freeze state corresponding to the interruption time node, and executing the recovery of the task freeze scene.

[0014] According to the task freeze scene automatic recovery method, wherein according to the recovery request of the task freeze scene, the first task in the freeze scene is obtained, comprising:

[0015] Reading a plurality of second tasks in the task freeze scene, and combining the second tasks according to the execution sequence to obtain the first task.

[0016] According to the task freeze scene automatic recovery method, wherein the task event group comprises a plurality of sequentially executed event behaviors, the event behaviors comprise at least one of creating an NPC, NPC movement control, playing special effects and playing timeline animation, and the event behaviors affecting the task freeze scene are obtained by traversing and filtering the task event group.

[0017] According to the task freeze scene automatic recovery method, wherein according to the task event group corresponding to the second task, the freeze state of each second task is determined, further comprising:

[0018] The current freeze state of the second task is determined by the freeze state of the previous task of the second task and the task event group, and when the task scene is interrupted, the freeze state of the previous task of the second task is taken as the current freeze state of the second task, and the previous task of the second task and the second task are respectively executed before and after the task.

[0019] According to the task snapshot scene automatic recovery method, wherein according to the interruption time node of the task snapshot scene, the second task snapshot state corresponding to the interruption time node is searched, and the recovery of the task snapshot scene is performed, including:

[0020] The first second task of the first task is searched as a starting task, and an empty state is created as the snapshot state of the starting task.

[0021] The first task is traversed from the starting task, the task event affecting the snapshot state in the first task is substituted into the snapshot state of the second task according to the execution order for calculation, and the state after the event execution of the second task is obtained; after the calculation of all event behaviors of the second task, the obtained snapshot state is the starting state of the next task.

[0022] The above step is repeated until all snapshot states of the first task are completed.

[0023] According to the snapshot state corresponding to the interruption time node, the task snapshot scene is recovered.

[0024] According to the task snapshot scene automatic recovery method, wherein the method further includes:

[0025] If the first task includes a plurality of second tasks, the snapshot states of the plurality of second tasks are calculated according to the execution order of the second tasks, the snapshot states of all second tasks of the first task are taken as the snapshot state of the first task, and the task snapshot scene recovery is performed.

[0026] Another aspect of the embodiment of the application provides a task snapshot scene automatic recovery device, including:

[0027] The first module is configured to acquire a first task in a snapshot scene according to a recovery request of the task snapshot scene, wherein the first task includes sequentially executed second tasks.

[0028] The second module is configured to determine a snapshot state of each second task according to a task event group corresponding to the second task, wherein the task event group is used to represent event behaviors associated with the snapshot state.

[0029] The third module is configured to search for a second task snapshot state corresponding to an interruption time node of the task snapshot scene according to the interruption time node, and perform recovery of the task snapshot scene.

[0030] Another aspect of the embodiment of the application provides an electronic device including a processor and a memory.

[0031] The memory is configured to store a program.

[0032] The processor executes the program to implement the task freeze scene automatic recovery method described above.

[0033] The embodiment of the application further discloses a computer program product or a computer program, which comprises computer instructions stored in a computer readable storage medium. A processor of a computer device can read the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method described above.

[0034] Additional aspects and advantages of the application will be described in the following description, become apparent from the following description, or be learned from practice of the application. BRIEF DESCRIPTION OF DRAWINGS

[0035] The above and / or additional aspects and advantages of the application will become apparent and be readily understood by considering the following detailed description, including the accompanying drawings, in which:

[0036] Figure 1 is a task freeze scene automatic recovery method of the embodiment of the application.

[0037] Figure 2 is a task merge flowchart of the embodiment of the application.

[0038] Figure 3 is a task freeze state configuration flowchart of the embodiment of the application.

[0039] Figure 4 is a task freeze scene detailed recovery flowchart of the embodiment of the application.

[0040] Figure 5 is a task freeze scene recovery flowchart of the embodiment of the application.

[0041] Figure 6 is a task freeze scene recovery flowchart of the embodiment of the application.

[0042] Figure 7 is a task freeze scene automatic recovery device of the embodiment of the application. DETAILED DESCRIPTION

[0043] Embodiments of the present application are described in detail below with reference to the attached drawings, which show examples of embodiments of the present application. The same or similar components have the same or similar designations throughout the attached drawings and the detailed description. In the following description, suffixes "module" and "unit" for components are used only in order to facilitate description of the present application, and are not intended to have specific meanings or roles distinct from each other. Therefore, "module" and "unit" can be used interchangeably. "First", "second", etc. are used only to distinguish technical features for the purpose of description, and cannot be understood to indicate or imply relative importance or to implicitly indicate the number of technical features indicated or the order of technical features indicated. In the following description, consecutive numbers of method steps are used for the convenience of review and understanding, and adjusting the order of implementation between steps does not affect the technical effects achieved by the overall technical solution of the present application and the logical relationship between the steps. The embodiments described below with reference to the drawings are exemplary and are used only to explain the present application, and cannot be understood as limiting the present application.

[0044] Terminology:

[0045] NPC, non-player character

[0046] Timeline, timeline animation

[0047] Reference Figure 1 , wherein Figure 1 is a task freeze scene automatic recovery method of an embodiment of the present application, which includes but is not limited to steps S100-S300:

[0048] S100, acquiring a second task sequentially executed in a freeze scene, and combining the second task to obtain a first task.

[0049] In some embodiments, the freeze state of the second task is determined by the freeze state of the first task and the task event of the first task, and is irrelevant to the event of the second task. The freeze state is the state before the task is performed (i.e., the freeze state of the second task refers to the state before the second task is executed).

[0050] In some embodiments, the first task represents a collection of a plurality of second tasks of the player in the freeze scene, for example, the player simultaneously receives a plurality of tasks in the scene, and each task has a corresponding freeze scene.

[0051] In some embodiments, reference is made to Figure 2 , a task merging process schematic diagram, which includes but is not limited to step S110:

[0052] S110, reading a plurality of second tasks in a task freeze scene, and combining the second tasks according to the execution order to obtain a first task.

[0053] In some embodiments, a plurality of second tasks performed by the player in the scene can be read, and the plurality of second tasks are combined to obtain the first task according to the order in which the tasks are performed.

[0054] S200, determining the freeze state of each second task according to the task event group corresponding to the second task, the task event group being used to represent the event behavior associated with the freeze state.

[0055] In some embodiments, in order to simplify the recovery of the freeze scene, reference is made to Figure 3 which illustrates the task freeze state configuration process intent, including but not limited to step S120:

[0056] S120, traversing and screening the task event group to obtain the event behavior affecting the task freeze scene.

[0057] S300, according to the interruption time node of the task freeze scene, searching for the second task freeze state corresponding to the interruption time node, and performing the recovery of the task freeze scene.

[0058] In some embodiments, the second task has no freeze state, and only the second task has a freeze state, and the plurality of second tasks are combined into one task to reduce the number of freeze states.

[0059] In some embodiments, reference is made to Figure 4 which illustrates the detailed recovery process diagram of the task freeze scene, including but not limited to steps S310-S340:

[0060] S310, searching for the first second task of the first task as a starting task, and creating an empty state as the freeze state of the starting task;

[0061] S320, starting from the starting task to traverse the first task, and substituting the task event affecting the freeze state in the first task into the freeze state of the second task according to the execution order to calculate the state after the event execution of the second task, and obtaining the freeze state after the calculation of all event behaviors of the second task as the starting state of the next task;

[0062] S330, repeating the previous step until all freeze states of the first task are completed;

[0063] S340, according to the freeze state corresponding to the interruption time node, recovering the task freeze scene.

[0064] Exemplarily, reference is made to Figure 5 , Figure 5is a still scene recovery flowchart of multiple tasks of an embodiment of the present application. It indicates that in a continuous plot performance, complex performance content is combined into one task, which is then divided into several subtasks. If the task flow is interrupted at any stage in the subtasks, the task flow will be resumed to the same still frame state and the flow of the first subtask will be restarted when the task flow is resumed next time. The subtasks are equivalent to the second tasks shown above, and the combined task is the first task shown above.

[0065] Exemplarily, with reference to Figure 6 , wherein Figure 6 is a still scene recovery flowchart of an embodiment of the present application with task iteration. It indicates that in the presence of iterative tasks (the first task includes multiple second tasks (subtasks)), including:

[0066] The specific performance of a single task is completed by sequentially combining task events in the task. Each task event completes a simple performance content, such as creating an NPC, controlling the movement of an NPC, playing a special effect, playing a Timeline, etc. Then, the configured task events are sequentially executed when the task is taken or completed to complete a performance content. Therefore, the still state of each task can be calculated from the still state of the previous task and the task events of the previous task. The calculation process is as follows:

[0067] Sort the task events of each task, and filter out the task events that will affect the still state of the task and record them in order. For example, creating an NPC and playing a Timeline will affect the still state of the task, and events such as issuing rewards will not affect the still state of the task.

[0068] Find the starting task of a series of tasks, and create an empty state as the still state of the starting task.

[0069] Starting from the starting task, the task events that will affect the still state are sequentially substituted into the still state of the task to calculate the state after the events are executed. After all the events of the task are calculated, the still state obtained is the starting state of the next task.

[0070] Repeat the previous step to calculate and save the still state of each task.

[0071] Through the embodiments of the present application, the technical solutions of the present application at least have the following beneficial effects: By combining complex content in the performance, each still state is determined, rather than being different according to the specific performance occasion. In this way, a specific calculation process can be used to calculate the determined state data after the performance from the set performance process, and the appropriate still state can be restored at any time according to the state data.

[0072] Figure 7 is a schematic diagram of an apparatus for automatic recovery of a task snapshot scene according to an embodiment of the present application.

[0073] The apparatus comprises a first module 701, a second module 702 and a third module 703.

[0074] The first module is configured to acquire a first task in the task snapshot scene according to a recovery request of the task snapshot scene, the first task comprising sequentially executed second tasks; the second module is configured to determine a snapshot state of each second task according to a task event group corresponding to the second task, the task event group being used to represent an event behavior associated with the snapshot state; and the third module is configured to find a second task snapshot state corresponding to an interruption time node of the task snapshot scene according to the interruption time node, and perform recovery of the task snapshot scene.

[0075] Exemplarily, under cooperation of the first module, the second module and the third module in the apparatus, the embodiment apparatus can implement any one of the foregoing automatic recovery methods of the task snapshot scene, i.e., acquiring sequentially executed second tasks in the task snapshot scene, combining the second tasks to obtain a first task, determining a snapshot state of each second task according to a task event group corresponding to the second task, the task event group being used to represent an event behavior associated with the snapshot state, and finding a second task snapshot state corresponding to an interruption time node of the task snapshot scene according to the interruption time node, and performing recovery of the task snapshot scene. Through merging of the tasks themselves, complexity and uncertainty of the tasks are greatly reduced, an uncertain task environment is changed into a determined task snapshot state, and subsequent task environment recovery becomes more accurate and reasonable. In addition, through changing manual configuration of the task snapshot state into automatic calculation, a probability of error of the state data itself is effectively reduced, and detailed testing on each task snapshot state data is no longer needed.

[0076] In some alternative embodiments, the functions / operations mentioned in the block diagram can not occur in the order mentioned in the operation diagram. For example, depending on the functions / operations involved, two blocks shown in succession can actually be executed substantially simultaneously or the blocks can sometimes be executed in reverse order. In addition, the embodiments presented and described in the flowcharts of the present application are provided by way of example, and the purpose is to provide a more comprehensive understanding of the technology. The disclosed method is not limited to the operations and logical flows presented herein. Alternative embodiments are contemplated in which the order of various operations is changed and in which sub-operations described as part of larger operations are independently executed.

[0077] The embodiment of the present application further discloses a computer program product or computer program, which comprises computer instructions stored in a computer readable storage medium. A processor of a computer device can read the computer instructions from the computer readable storage medium, and the processor executes the computer instructions to enable the computer device to perform the aforementioned task framing scene automatic recovery method.

[0078] Furthermore, although the present application is described in the context of functional modules, it is to be understood that one or more of the described functions and / or features can be integrated in a single physical device and / or software module, or one or more functions and / or features can be implemented in separate physical devices or software modules, unless otherwise specified. It is also to be understood that detailed discussion of the actual implementation of each module is unnecessary to an understanding of the present application. Rather, the actual implementation is to be understood within the context of the properties, functions and internal relationships of the various functional modules disclosed herein. Thus, those skilled in the art using ordinary skill can practice the present application with the benefit of the teachings presented in this document without undue experimentation. It is also to be understood that the particular concepts disclosed are meant to be illustrative only and not limiting of the scope of the application, which is to be determined by the full scope of the claims and equivalents thereof.

[0079] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the parts of the technical solutions that essentially contribute to the prior art can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0080] The logic and / or steps represented in the flowcharts and / or described herein, for example, can be embodied in non-transitory computer-readable media, executed by one or more computing devices, and / or in any other way. The logic and / or steps represented in the flowcharts and / or described herein, for example, can be considered a list of executable instructions for implementing logic functions, and can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor- containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For purposes of this specification, a "computer-readable medium" can be any apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer-readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium include the following: an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber (optical), and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium can even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, for example via an optical scanner, then compiled, interpreted, or otherwise processed, and stored in a computer memory in a form that can be later executed by a computer. In this context, a "computer-readable medium" can be any means that can store the program for use by or in connection with the instruction execution system, apparatus, or device.

[0081] The foregoing description of various embodiments of the application has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the application to the precise form disclosed, and various modifications and variations are possible in light of the above teachings. It is intended that the scope of the application be limited not with this detailed description, but rather by the claims appended hereto.

[0082] It will be appreciated that portions of the present application can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, and in another embodiment, any of the following technologies known in the art, or a combination thereof, can be used: discrete logic circuitry having logic gates for implementing logic functions upon an application of data signals, application specific integrated circuits having appropriate combinational logic gates, programmable gate arrays (PGA), field programmable gate arrays (FPGA), and the like.

[0083] In the description of the present application, the use of the terms "one embodiment", "some embodiments", "an example", "a specific example", or "some examples" to describe certain aspects of the application, is not meant to limit or restrict the scope of the application to such embodiments, examples, or examples alone. Rather, these terms are used herein to describe a particular embodiment, example, or example in connection with which a feature, structure, material, or characteristic is being described. The use of these terms in the description is not intended to exclude from the scope of the application other embodiments or examples of the application that do not include the recited feature, structure, material, or characteristic.

[0084] While the embodiments of the application have been shown and described, it is to be understood that the embodiments described are merely exemplary and are not to be taken as limiting the scope of the application. The scope of the application is defined by the claims and their equivalents.

[0085] The above is a specific description of the preferred embodiment of the present application, but the present application is not limited to the described embodiment, and those skilled in the art can make various equivalent modifications or replacements without departing from the spirit of the present application, and these equivalent modifications or replacements are all included in the scope defined by the claims of the present application.

Claims

1. A method for automatically recovering a task-scoped scene, characterized in that, The method comprises: According to the recovery request of the task freeze scene, a second task in the freeze scene is obtained, and the second task is combined to obtain a first task, wherein the second task comprises at most one freeze state; According to the task event group corresponding to the second task, the freeze state of each second task is determined, and the task event group is used to represent the event behavior associated with the freeze state; According to the interruption time node of the task freeze scene, the second task freeze state corresponding to the interruption time node is found, and the recovery of the task freeze scene is performed, wherein the method comprises: finding a first second task of the first task as a starting task, and creating an empty state as the freeze state of the starting task; the task event affecting the freeze state in the first task is substituted into the freeze state of the second task according to the execution order, and the state after the event execution of the second task is calculated, so that the starting state of the next task is obtained after all event behaviors of the second task are calculated; the above step is repeated until all freeze states of the first task are completed; and the task freeze scene is recovered according to the freeze state corresponding to the interruption time node.

2. The automatic task snapshot recovery method according to claim 1, wherein, The method comprises: The second task in the task freeze scene is read, and the second task is combined according to the execution order to obtain the first task.

3. The automatic task snapshot recovery method according to claim 1, wherein, The task event group comprises a plurality of event behaviors executed in sequence, and the event behavior comprises at least one of creating an NPC, NPC movement control, playing a special effect, and playing a timeline animation; the event behavior is obtained by traversing and screening the task event group, and the event behavior affects the task freeze scene.

4. The automatic task snapshot recovery method according to claim 1, wherein, The method comprises: The current freeze state of the second task is determined by the freeze state of the previous task of the second task and the task event group; when the task freeze scene is interrupted, the freeze state of the previous task of the second task is taken as the current freeze state of the second task; the previous task of the second task and the second task are tasks executed in sequence.

5. The method of claim 1, wherein, The method further comprises: If the first task comprises a plurality of second tasks, the freeze states of the plurality of second tasks are calculated according to the execution order of the second tasks, the freeze states of all second tasks of the first task are taken as the freeze state of the first task, and the recovery of the task freeze scene is performed.

6. A task staging scene automatic recovery apparatus characterized by comprising: The method comprises: A first module is configured to obtain a first task in a task freeze scene according to a recovery request of the task freeze scene, the first task comprising a second task executed in sequence, and the second task comprising at most one freeze state; A second module is configured to determine a freeze state of each second task according to a task event group corresponding to the second task, the task event group being used to represent an event behavior associated with the freeze state; A third module is configured to find a second task freeze state corresponding to an interruption time node of the task freeze scene, and perform recovery of the task freeze scene. The third module is configured to find the second task snapshot corresponding to the interrupt time node of the task snapshot, and perform recovery of the task snapshot, and includes the following steps: finding a first second task of the first task as a starting task, and creating an empty state as a snapshot of the starting task; starting from the starting task, traversing the first task, and calculating the task events of the first task that affect the snapshot into the snapshot of the second task according to the execution order to obtain the state of the second task after event execution; after calculating all event behaviors of the second task, the obtained snapshot is the starting state of the next task; repeating the above step until all snapshots of the first task are completed; and performing recovery of the task snapshot according to the snapshot corresponding to the interrupt time node.

7. An electronic device, comprising: comprise a processor and a memory; the memory is configured to store a program; the processor executes the program to implement the task snapshot automatic recovery method according to any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The storage medium stores a program, and the program is executed by the processor to implement the task snapshot automatic recovery method according to any one of claims 1-5.

Images