A method, device, electronic device and storage medium for game level editing

Abstract

The present disclosure provides a game level editing method, apparatus, electronic device, and storage medium. The method includes: displaying a level editing page of a target game; the level editing page includes a level flowchart editing area and an operation area; the level flowchart editing area is used for flowchart editing of the process relationship between level nodes; the operation area is used for node information editing for a selected level node; in response to a node editing operation acting on the level flowchart editing area, in the level flowchart editing area, perform a level node editing operation and edit the information of the target level node currently being edited in the operation area; in response to the entry level option for the target level node being triggered, display an in-level process editing page corresponding to the target level node, and edit the in-node process information of the target level node through the in-level process editing page.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technologies, and in particular, to a game level editing method, apparatus, electronic device, and storage medium. Background Art

[0002] With the development of Internet technologies, various electronic games have emerged. People can experience various electronic games through electronic devices, and electronic games have gradually become an important means of people's entertainment. However, no matter what kind of electronic game, it usually consists of a series of game levels, either complex or simple. Therefore, the editing of game level information has become an important issue in the game development process.

[0003] Conventional game level editing methods either have problems of high development requirements and high development difficulty, or need to rely on various button components created in the game, resulting in problems of poor development flexibility and inconvenience in game information expression, which affect the effect of game level editing. Summary of the Invention

[0004] Embodiments of the present disclosure at least provide a game level editing method, apparatus, electronic device, and storage medium.

[0005] In a first aspect, embodiments of the present disclosure provide a game level editing method, including:

[0006] Displaying a level editing page of a target game; the level editing page includes a level flowchart editing area and an operation area; the level flowchart editing area is used for flowchart editing of the process relationship between level nodes; the operation area is used for node information editing for a selected level node;

[0007] Responding to a node editing operation in the level flowchart editing area, performing a level node editing operation in the level flowchart editing area, and performing information editing on a target level node being currently edited in the operation area;

[0008] Responding to a trigger of an enter-level option for the target level node, displaying an in-level process editing page corresponding to the target level node, and editing the in-node process information of the target level node through the in-level process editing page.

[0009] In a possible implementation manner, the node editing operation includes a node addition operation; the target level node includes a newly added level node;

[0010] In response to a node editing operation performed in the level flowchart editing area, in the level flowchart editing area, perform a level node editing operation, and in the operation area, perform information editing on the target level node currently being edited, including:

[0011] In response to a node addition operation performed in the level flowchart editing area, in the level flowchart editing area, generate a new added level node having a connection relationship with the created level nodes in the level flowchart editing area;

[0012] In response to a triggering operation on the newly added level node, perform information editing on the newly added level node in the operation area.

[0013] In a possible implementation manner, the performing information editing on the newly added level node in the operation area in response to a triggering operation on the newly added level node includes:

[0014] In response to a triggering operation on the newly added level node, generate type selection buttons for indicating the creation of different types of nodes in the operation area;

[0015] In response to the triggering of a level selection button among the type selection buttons, determine that the newly added level node is a level type node with default level description information; wherein, the default level description information is displayed in the operation area;

[0016] In response to a modification operation on the default level description information in the operation area, obtain the input target level description information, and update the default level description information in the newly added level node to the target level description information, and display it in the level flowchart editing area.

[0017] In a possible implementation manner, the generating a new added level node having a connection relationship with the created level nodes in the level flowchart editing area in response to a node addition operation performed in the level flowchart editing area includes:

[0018] In response to a selection operation on the created level node, display each created exit point and created entry point of the created level node; wherein, the created exit point is used to establish a connection relationship between the created level node and subsequent level nodes, and the created entry point is used to establish a connection relationship between the created level node and previous level nodes;

[0019] In response to a node addition operation confirmed based on the displayed created exit points and created entry points, generate a new added level node having a connection relationship with the created level node in the level flowchart editing area.

[0020] In a possible implementation, in response to a node addition operation in the level flowchart editing area, generating, in the level flowchart editing area, a new level node having a connection relationship with the created level nodes in the level flowchart editing area includes:

[0021] In response to a configuration operation on the created level node, generating a node setting pop-up window including an option to add a level exit point;

[0022] In response to triggering the option to add an exit point in the node setting pop-up window, generating a new exit point for the created level node;

[0023] In the case where no other created level nodes in the level flowchart editing area are connected to the new exit point, generating, in the level flowchart editing area, a new level node having a connection relationship with the new exit point.

[0024] In a possible implementation, the node setting pop-up window further includes an option to enter the level; in response to the option to enter the level for the target level node being triggered, displaying an in-level process editing page corresponding to the target level node, including:

[0025] In response to the option to enter the level in the node setting pop-up window corresponding to the target level node being triggered, and in the case where it is determined that the node information corresponding to the target level node has been saved completely, entering the in-level process editing page corresponding to the target level node in the main view mode.

[0026] In a possible implementation, the node setting pop-up window further includes a node deletion option and / or an option to reduce the level exit points;

[0027] After generating the node setting pop-up window including the option to add a level exit point, the following at least one operation is further included:

[0028] In response to the node deletion option in the node setting pop-up window being triggered, determining the first node connection relationships corresponding to the respective created exit points and the respective created entry points of the created level node, and deleting the created level node and the first node connection relationships in the level flowchart editing area;

[0029] In response to the option to reduce the level exit points in the node setting pop-up window being triggered, determining the respective created exit points corresponding to the created level node, and generating an exit point selection pop-up window including the respective created exit points;

[0030] In response to a selection operation on any of the created exit points in the pop-up window for the selected exit point, determine the second node connection relationship corresponding to the created exit point, and delete the created exit point and the second node connection relationship.

[0031] In a possible implementation, a level view button is displayed on the in-level process editing page;

[0032] After displaying the in-level process editing page corresponding to the target level node, it further includes:

[0033] In response to a selection operation on the level view button, generate a level navigation floating layer; the latest switched level node corresponding to the target game, the previous level node and the subsequent node of the latest switched level node are displayed in the level navigation floating layer;

[0034] In response to the triggering of the previous level node, display the level description information of the previous level node in the level navigation floating layer;

[0035] In response to the triggering of the subsequent node, when the subsequent node is a subsequent level node, display the level description information of the subsequent level node in the level navigation floating layer; when the subsequent node is a subsequent ending node, display the ending description information of the subsequent ending node in the level navigation floating layer.

[0036] In a possible implementation, the target level node includes any created level node in the level flow chart editing area; the in-level process editing page further includes an information editing area, an in-level process editor area, and an entity display area; the in-level process editor area is used to display each in-level process node of the target level corresponding to the target level node; the entity display area is used to display the names of each entity object matching the target level; each in-level process node is used to represent at least one established in-level process corresponding to the target level;

[0037] The editing of the node internal process information of the target level node through the in-level process editing page includes:

[0038] In response to a node addition operation on a target process node in the in-level process nodes, in the in-level process editor area, generate an in-level node addition item having a connection relationship with the target process node, and in response to triggering the in-level node addition item, generate a first selection button for a new in-level node for indicating the creation of various in-level node types in the in-level process editor area;

[0039] In response to the triggering of a second selection button related to the node type within the target level, a new in-level node with the node type within the target level is generated in the in-level process editor area within the level; the new in-level node has a connection relationship with the target process node.

[0040] In a possible implementation manner, when the node type within the target level is a conditional judgment type, the step of generating, in response to the triggering of a second selection button related to the node type within the target level, a new in-level node with the node type within the target level in the in-level process editor area within the level includes:

[0041] In response to the triggering of a second selection button related to the conditional judgment type, a new conditional judgment node is generated in the in-level process editor area within the level, and a setting area for conditional judgment items is displayed in the information editing area; the setting area includes a setting box for judgment condition variables and a selection box for conditional judgment exits.

[0042] In response to the triggering of the setting box, the input first target condition variable is displayed.

[0043] In response to the triggering of the selection box, each created in-level exit is displayed, and the first target in-level exit selected from the created in-level exits is used as the in-level exit corresponding to the first target condition variable.

[0044] In a possible implementation manner, the in-level process node includes a node exit type node.

[0045] The editing of the in-level process information of the target level node through the in-level process editing page includes:

[0046] In response to the triggering of any node exit type node, an in-level exit setting box is displayed in the information editing area; the in-level exit setting box defaultly displays the in-level exits corresponding to the triggered node exit type node.

[0047] In response to the triggering of the in-level exit setting box, each created in-level exit corresponding to the target level is displayed.

[0048] In response to the triggering of any displayed created in-level exit, the triggered created in-level exit is used as the new in-level exit corresponding to the triggered node exit type node.

[0049] In a possible implementation manner, the in-level process node includes a trigger type node.

[0050] The editing of the in-level process information of the target level node through the in-level process editing page includes:

[0051] In response to triggering any trigger type node, a trigger list is displayed in the information editing area, and trigger attribute information of the trigger corresponding to the any trigger type node is displayed in the trigger list.

[0052] In a possible implementation manner, the in-level process nodes include trigger type nodes; the level editing page further includes a rendering area for displaying the game screen of the target game.

[0053] After displaying the in-level process editing page corresponding to the target level node, the following is further included:

[0054] In response to triggering any trigger type node, determine a target entity object and / or a target game screen area related to the trigger corresponding to the any trigger type node indicated by the trigger attribute information of the any trigger type node.

[0055] When the target entity object and / or the target game screen area meet preset conditions, prominently display the entity object name of the target entity object and / or the name of the target game screen area in the entity display area, and prominently display the target entity object and / or the target game screen area in the rendering area.

[0056] In a possible implementation manner, the in-level process nodes include condition judgment type nodes.

[0057] Editing the node internal process information of the target level node through the in-level process editing page includes:

[0058] In response to triggering any condition judgment type node, a condition judgment item setting area is displayed in the information editing area; the condition judgment item setting area displays an add button for condition judgment information and each created condition judgment item matching the condition judgment type node; the created condition judgment item includes a setting box displaying a selected condition variable and a selection box displaying a selected in-level exit.

[0059] In response to triggering the setting box in any of the created condition judgment items, obtain the input second target condition variable, and use the second target condition variable as the new selected condition variable of the triggered created condition judgment item.

[0060] In response to triggering the selection box in any of the created condition judgment items, display each created in-level exit, and use the second target in-level exit selected from the created in-level exits as the new selected in-level exit of the triggered created condition judgment item.

[0061] In a second aspect, embodiments of the present disclosure further provide a game level editing device, including:

[0062] A first display module, configured to display a level editing page of a target game; the level editing page includes a level flowchart editing area and an operation area; the level flowchart editing area is used for flowchart editing of the process relationship between level nodes; the operation area is used for node information editing for a selected level node;

[0063] A first editing module, configured to, in response to a node editing operation acting on the level flowchart editing area, perform a level node editing operation in the level flowchart editing area, and perform information editing on the target level node currently being edited in the operation area;

[0064] A second editing module, configured to, in response to a trigger of an enter-level option for the target level node, display an in-level process editing page corresponding to the target level node, and edit the in-node process information of the target level node through the in-level process editing page.

[0065] In a third aspect, an alternative implementation of the present disclosure further provides an electronic device, including a processor and a memory. The memory stores machine-readable instructions executable by the processor. The processor is configured to execute the machine-readable instructions stored in the memory. When the machine-readable instructions are executed by the processor, the machine-readable instructions execute the steps in the first aspect, or any possible implementation manner in the first aspect.

[0066] In a fourth aspect, an alternative implementation of the present disclosure further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is run, it executes the steps in the first aspect, or any possible implementation manner in the first aspect.

[0067] For the effect descriptions of the above game level editing device, electronic device, and computer-readable storage medium, refer to the description of the above game level editing method, which will not be elaborated here.

[0068] The game level editing method, device, electronic device, and storage medium provided by the embodiments of the present disclosure can implement the editing of level nodes corresponding to game levels (such as adding level nodes) in the level flowchart editing area by generating a level editing page including a level flowchart editing area and an operation area, and at the same time implement the information editing of the target level node being currently edited in the operation area, improving the convenience of level information editing. By dividing the game into individual levels and then performing level information editing in the operation area, not only can modular editing be achieved, but also the development difficulty of each module can be reduced. The entire created game process can also be reflected in the level flowchart editing area, which is beneficial for users to control the editing progress and content at any time according to the overall process shown in the level flowchart editing area, and is beneficial for improving the efficiency and accuracy of game process information editing. Moreover, by dividing the game into individual game levels for editing, the triggering of the entire game can be determined by the game process composed of each level, eliminating the need to use component triggering, which not only improves the flexibility of game development but also can accurately express game information through the game process.

[0069] To make the above objects, features, and advantages of the present disclosure more obvious and understandable, the following specific preferred embodiments are given and described in detail in conjunction with the accompanying drawings as follows. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] To more clearly illustrate the technical solutions of the embodiments of the present disclosure, the accompanying drawings required for use in the embodiments will be briefly introduced below. The accompanying drawings are incorporated into the specification and form a part of this specification. These drawings illustrate embodiments that conform to the present disclosure and are used together with the specification to explain the technical solutions of the present disclosure. It should be understood that the following drawings only illustrate certain embodiments of the present disclosure and should not be regarded as limiting the scope. For those of ordinary skill in the art, other related drawings can be obtained based on these drawings without creative efforts.

[0071] Figure 1 Shows a flowchart of a game level editing method provided by an embodiment of the present disclosure;

[0072] Figure 2 Shows a schematic diagram of a level editing page provided by an embodiment of the present disclosure;

[0073] Figure 3 Shows a schematic diagram of adding a level node provided by an embodiment of the present disclosure;

[0074] Figure 4 Shows a schematic diagram of generating type selection buttons for indicating the creation of different types of nodes in the operation area provided by an embodiment of the present disclosure;

[0075] Figure 5Shows a schematic diagram of a new level node of a level type provided by an embodiment of the present disclosure;

[0076] Figure 6 Shows a schematic diagram of showing a created exit node and a created entry point provided by an embodiment of the present disclosure;

[0077] Figure 7a Shows a schematic diagram of a node setting pop-up window provided by an embodiment of the present disclosure;

[0078] Figure 7b Shows a schematic diagram of an exit point selection pop-up window provided by an embodiment of the present disclosure;

[0079] Figure 8a Shows a schematic diagram of triggering a target exit point provided by an embodiment of the present disclosure;

[0080] Figure 8b Shows a connection schematic diagram between an exit point D and a level node 5 provided by an embodiment of the present disclosure;

[0081] Figure 8c Shows a schematic diagram of a mouse in a preset state provided by an embodiment of the present disclosure;

[0082] Figure 8d Shows a schematic diagram of a connection line between a level node 4 and a level node 5 provided by an embodiment of the present disclosure;

[0083] Figure 9 Shows a schematic diagram of displaying ending description information in an operation area provided by an embodiment of the present disclosure;

[0084] Figure 10a Shows a connection schematic diagram of an exit point of a level node provided by an embodiment of the present disclosure;

[0085] Figure 10b Shows a connection schematic diagram of an exit point of an in-level process node provided by an embodiment of the present disclosure;

[0086] Figure 10c Shows a connection schematic diagram of an exit point provided by an embodiment of the present disclosure;

[0087] Figure 11 Shows a schematic diagram of an in-level process editing page provided by an embodiment of the present disclosure;

[0088] Figure 12a Shows a schematic diagram of a level navigation floating layer provided by an embodiment of the present disclosure;

[0089] Figure 12bShows a schematic diagram of presenting the level description information of the previous level node in a description information display pop-up window provided by an embodiment of the present disclosure;

[0090] Figure 13 Shows a schematic diagram of a first selection button provided by an embodiment of the present disclosure;

[0091] Figure 14 Shows a schematic diagram of an in-level exit setting box provided by an embodiment of the present disclosure;

[0092] Figure 15 Shows a schematic diagram of a trigger list provided by an embodiment of the present disclosure;

[0093] Figure 16 Shows a schematic diagram of a trigger condition judgment type node provided by an embodiment of the present disclosure;

[0094] Figure 17 Shows a schematic diagram of an in-level setting pop-up window provided by an embodiment of the present disclosure;

[0095] Figure 18 Shows a schematic diagram of an in-level setting pop-up window corresponding to a task type node provided by an embodiment of the present disclosure;

[0096] Figure 19 Shows a schematic diagram of a game level editing device provided by an embodiment of the present disclosure;

[0097] Figure 20 Shows a schematic diagram of the structure of an electronic device provided by an embodiment of the present disclosure. Detailed implementation manners

[0098] To make the objectives, technical solutions, and advantages of the embodiments of the present disclosure clearer, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present disclosure. Apparently, the described embodiments are only some of the embodiments of the present disclosure, rather than all the embodiments. Usually, the components of the embodiments of the present disclosure described and illustrated herein can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present disclosure is not intended to limit the scope of the present disclosure claimed, but merely represents selected embodiments of the present disclosure. All other embodiments obtained by those skilled in the art based on the embodiments of the present disclosure without creative efforts fall within the scope of protection of the present disclosure.

[0099] In addition, in the description, claims, and the above-mentioned drawings of the embodiments of the present disclosure, terms such as "first" and "second" are used to distinguish similar objects, and do not necessarily describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances so that the embodiments described here can be implemented in an order other than that illustrated or described here.

[0100] As used herein, "a plurality of" or "several" means two or more. "And / or" describes the association relationship of associated objects and indicates that three relationships may exist. For example, A and / or B may represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0101] Through research, it is found that conventional game level editing tools may include Build Box 3 and RecRoom. Among them, Build Box 3 is a drag-and-drop cross-platform game development tool, and RecRoom is a game development and social platform integrating multiple gameplay modes. However, when using Build Box 3 for game development, the parameters to be set are too detailed, resulting in the need for developers to master more programming knowledge during the development process, with relatively high development requirements and difficulties. For RecRoom, during the game development process, it is necessary to rely on creating button components in the game and then using the button components for process development, which reduces the flexibility of process development. Moreover, for the expression of game plots, using button components cannot accurately and easily express the plots, further highlighting the disadvantages of RecRoom.

[0102] Based on the above research, the present disclosure provides a game level editing method, device, electronic device, and storage medium. By generating a level editing page including a level flowchart editing area and an operation area, it is possible to edit the level nodes corresponding to the game levels (such as adding level nodes) in the level flowchart editing area, and at the same time, edit the information of the currently edited target level node in the operation area, improving the convenience of level information editing. By dividing the game into individual levels and editing the level information in the operation area, it is possible to achieve modular editing and reduce the development difficulty of each module. The entire created game process can also be reflected in the level flowchart editing area, which is conducive to users controlling the editing progress and content at any time according to the overall process shown in the level flowchart editing area, and is conducive to improving the efficiency and accuracy of game process information editing. Moreover, by dividing the game into individual game levels for editing, the triggering of the entire game can be determined by the game process composed of each level, without the need to use component triggering, which not only improves the flexibility of game development but also can accurately express game information through the game process.

[0103] Regarding the defects existing in the above solutions, they are all the results obtained by the inventor after practice and careful research. Therefore, the process of discovering the above problems and the solutions proposed by the present disclosure for the above problems in the following text should both be the contributions made by the inventor to the present disclosure during the process of the present disclosure.

[0104] It should be noted that similar reference numerals and letters represent similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings.

[0105] To facilitate the understanding of this embodiment, first, a game level editing method disclosed in the embodiments of the present disclosure will be introduced in detail. The execution subject of the game level editing method provided by the embodiments of the present disclosure is generally a terminal device or other processing device with certain computing capabilities. Among them, the terminal device may be a user equipment (UE), a mobile device, a user terminal, a terminal, a personal digital assistant device (PDA), a handheld device, an electronic device, etc.; in some possible implementation manners, the game level editing method may be implemented by a processor invoking computer-readable instructions stored in a memory.

[0106] The game level editing method provided by the embodiments of the present disclosure will be described below by taking the execution subject as an electronic device as an example.

[0107] As Figure 1 shown, it is a flowchart of a game level editing method provided by the embodiments of the present disclosure, which may include the following steps:

[0108] S101: Display a level editing page of a target game; the level editing page includes a level flowchart editing area and an operation area; the level flowchart editing area is used for flowchart editing of the process relationship between level nodes; the operation area is used for node information editing for a selected level node.

[0109] Here, the target game can be any game that requires level process development. In the level process corresponding to the target game, there can be process nodes of different node types. Specifically, the node types can include level types and ending types. The level node of the level type is a level corresponding to the target game, and the ending node of the ending type is an ending corresponding to the target game. There can be a process relationship between level nodes, and this process relationship is used to indicate the sequence order between each node. For example, the subsequent node of level node 1 is level node 2, and the previous node of level node 1 is level node 3. The level editing page is a page for developing process nodes of various node types in the level process corresponding to the target game. In the embodiments of the present disclosure, taking the editing of the level node of the level type as an example, the game level editing method provided by the embodiments of the present disclosure will be described in detail.

[0110] When there is corresponding ending information for a level node, a level node can correspond to at least one ending node, and different ending nodes correspond to different ending information. The relationship between a level node and the corresponding ending node can be represented by a connection line in the flowchart. That is, if there is a connection line between a level node and an ending node, it can indicate that the ending information corresponding to this ending node is the ending information of this level node. When there is no corresponding ending information for a level node, there may be no connected ending nodes.

[0111] The level flowchart editing area can be used to edit the flowchart of the process relationship between level nodes. Specifically, in implementation, after responding to a game level editing operation for the target game initiated in the level editor, the process corresponding to the target game can be displayed in the level flowchart editing area on the level editing page, and this process can include the created level nodes and created ending nodes corresponding to the target game. The operation area is used to edit information for the selected level node, or it can also be used to edit the node information of a newly created level node or ending node. Among them, the game level editing operation can include the operation of clicking the global level button on the main page.

[0112] As Figure 2 shown, it is a schematic diagram of a level editing page provided by the embodiments of the present disclosure. In addition to the level flowchart editing area and the operation area, the level editing page can also display a cancel button for canceling the editing, a save button for saving the editing, and an enter specified level node button for entering a specified level node.

[0113] During specific implementation, in response to a game level editing operation initiated by a user for a target game, a level editing page can be generated and displayed, and the level process corresponding to the target game can be displayed in the level flow chart editing area of the level editing page. The level process can include each created level node and created ending node corresponding to the target game.

[0114] In addition, the position of the level flow chart editing area can be dragged using the middle mouse button, and the size of the level flow chart editing area can be modified by scrolling the mouse wheel.

[0115] S102: In response to a node editing operation performed in the level flow chart editing area, perform a level node editing operation in the level flow chart editing area, and edit the information of the target level node being currently edited in the operation area.

[0116] Here, the node editing operation can include editing operations (such as modification, deletion, movement, etc.) on the created process nodes displayed in the level flow chart editing area and operations for creating new process nodes (such as creating a new joint node, creating a new ending node).

[0117] The target level node is the level node currently being edited in the level flow chart editing area, and can include created joint nodes and newly created level nodes.

[0118] Exemplarily, in response to a click operation on any created level node in the level flow chart editing area, the selection of the created level node can be achieved (i.e., determining the created level node as the target level node). Then, in the level flow chart editing area, a level node editing operation can be performed on the target level node, and at the same time, the node information of the target level node can be displayed in the operation area, and the displayed node information can be edited.

[0119] S103: In response to the trigger of the option to enter the level for the target level node, display the in-level process editing page corresponding to the target level node, and edit the in-node process information of the target level node through the in-level process editing page.

[0120] Here, the in-level process editing page is used to edit the in-node process corresponding to the created level node; the in-level process editing page may include an information editing area, an in-level process editor area, a rendering area, a level viewing button, an entity display area, etc. The in-node process information is used to represent each in-level process node of the target level corresponding to the target level node; each in-level process node is used to represent at least one established in-level process corresponding to the target level. Among them, the information editing area is used to view and edit the node information of any in-level process node of the target level corresponding to the target level node, the in-level process editor area can be used to display each in-level process node corresponding to the target level node, the rendering area is used to display the game screen of the target game, the level viewing button is used to view the node information of the created level node corresponding to the target game, and to trigger the generation of the level editing page, and the entity display area is used to display each entity object corresponding to the target game.

[0121] The operations triggered when the enter level option is triggered may specifically include the operation of double-clicking the target level node and / or the operation of clicking the enter level option in the node setting pop-up window corresponding to the target level node. The node setting pop-up window will be introduced in detail later.

[0122] Exemplarily, in response to the operation of clicking the enter level option in the node setting pop-up window corresponding to the target level node, the in-level process editing page corresponding to the target level node may be displayed, and the in-node process information of the target level node may be edited through the information editing area and the in-level process editor area in the in-level process editing page.

[0123] In this way, by editing the in-node process information of the target level node on the in-level process editing page, flexible editing of the in-level information of each target level corresponding to the target game can be achieved.

[0124] In one embodiment, the node editing operation may include a node addition operation, and the target level node may include a newly added level node generated in response to the node addition operation. For the above S102, it may be implemented according to the following steps:

[0125] S102-1: In response to the node addition operation acting on the level flowchart editing area, in the level flowchart editing area, a newly added level node having a connection relationship with the created level node in the level flowchart editing area is generated.

[0126] Here, the node addition operation is an operation used to add a new level node to the target game.

[0127] In specific implementation, the user can initiate an operation to add a node for any created level node displayed in the level flow chart editing area. After that, in response to this node addition operation, a new level node having a connection relationship with the created level node can be generated in the level flow chart editing area.

[0128] As Figure 3 shown, it is a schematic diagram of adding a new level node provided by an embodiment of the present disclosure. Figure 3 In the level flow chart editing area in it, there are two created level nodes (level node 1 and level node 2) with different level description information, one created ending node (i.e., ending node 1) with ending description information, and one new level node. Among them, the level description information corresponding to level node 1 is level description information 1 (i.e., Figure 3 in " Figure 3 the brave warrior received a reward task to defeat the demon king and rescue the princess"); the level description information corresponding to level node 2 is level description information 2 (i.e., Figure 3 in " Figure 3 the brave warrior set off on a journey alone and was defeated by the general of the demon king"). The level description information corresponding to ending node 1 is ending description information 1 (i.e., Figure 3 in " Figure 3 ending: the brave warrior was dejected"). In Figure 3 , in response to the node addition operation initiated by the user for level node 2, a new level node having a connection relationship with level node 2 can be generated, and the node information of level node 2 (i.e., the node description information of level node 2) can be displayed in the operation area. At this time, the operation area will become a level setting area. In addition, in the case of an editing need, in addition to displaying the node description information of level node 2, the node description information of other level nodes can also be displayed in the operation area. Regarding whether to display the node description information of other level nodes, it can be set according to development experience, and the embodiments of the present disclosure do not make specific limitations.

[0129] Optionally, even if the node addition operation for level node 2 is initiated, after the new level node having a connection relationship with level node 2 is generated, the operation area can also be a blank area without displaying any information.

[0130] S102-2: In response to the trigger operation for the new level node, perform information editing on the new level node in the operation area.

[0131] Here, the trigger operation for the new level node can be operations such as clicking on the new level node or double-clicking on the new level node.

[0132] In specific implementation, it can respond to the user's Figure 3For the triggering operation of the newly added level node, the default node information corresponding to the newly added level node is displayed in the operation area. Then, in response to the editing operation of the user on the default information in the operation area, the new node information input by the user can be obtained. Finally, the new node information can be used as the node information of the newly added level node, thereby realizing the information editing of the newly added level node.

[0133] In this way, by generating a level editing page including a level flowchart editing area and an operation area, it is possible to realize the editing of the level nodes corresponding to the game levels (such as newly added level nodes) in the level flowchart editing area, and at the same time realize the information editing of the target level node currently being edited in the operation area, improving the convenience of level information editing. By dividing the game into each level and then performing level information editing in the operation area, it is possible to achieve modular editing and reduce the development difficulty of each module. The entire created game process can also be reflected in the level flowchart editing area, which is beneficial for users to control the editing progress and content at any time according to the overall process displayed in the level flowchart editing area, and is beneficial for improving the efficiency and accuracy of game process information editing. Moreover, by dividing the game into each game level for editing, the triggering of the entire game can be determined by the game process composed of each level, without using component triggering, which not only improves the flexibility of game development but also can accurately express game information through the game process.

[0134] In one embodiment, for the above S102-2, it can be implemented according to the following steps:

[0135] S102-2-1: In response to the triggering operation for the newly added level node, generate type selection buttons in the operation area for indicating the creation of different types of nodes.

[0136] Here, the type selection buttons are used to indicate the creation of process nodes that match the node types corresponding to the type selection buttons. Specifically, the type selection buttons may include a new level button for indicating the creation of process nodes of the level type and a new ending button for indicating the creation of process nodes of the ending type. As Figure 4 shown, it is a schematic diagram of generating type selection buttons in the operation area for indicating the creation of different types of nodes provided by an embodiment of the present disclosure, where the type selection buttons include a new level button and a new ending button. In addition, Figure 4 a save button for saving the editing and a cancel button for canceling the editing may also be displayed.

[0137] Exemplarily, in response to the user clicking Figure 3 the operation of the newly added level node, generate and display a new level button and a new ending button in the operation area, that is, generate Figure 4 the page shown.

[0138] S102-2-2: In response to the level selection button among the type selection buttons being triggered, determine that the newly added level node is a level type node with default level description information; wherein, the default level description information is displayed in the operation area.

[0139] Here, after the user clicks the level selection button among the type selection buttons, the level selection button can be triggered.

[0140] The default level description information can be "New Level + the serial number of the new level", such as New Level 1, New Level 2. Among them, the serial number of the new level can be determined according to the number of existing newly added level nodes. For example, when the number of existing newly added level nodes is 0, the serial number of the new level can be 1, and when the number of existing newly added level nodes is 2, the serial number of the new level can be 3.

[0141] Exemplarily, it can be in response to the user clicking Figure 4 the operation of the New Level button in the operation area, it can be determined that the newly added level node is a level type node with default level description information, and the default node information is displayed in the operation area, and is also displayed in the corresponding newly added level node in the level flowchart editing area. As Figure 5 shown, it is a schematic diagram of a newly added level node of a level type provided by an embodiment of the present disclosure. Among them, Figure 5 is a page that can be generated after clicking the New Level button in the operation area of Figure 4 . Figure 5 The level flowchart editing area in shows New Level 1, and the operation area shows the default level description information corresponding to New Level 1 (i.e., New Level 1).

[0142] S102-2-3: In response to a modification operation on the default level description information in the operation area, obtain the input target level description information, and update the default level description information in the newly added level node to the target level description information, and display it in the level flowchart editing area.

[0143] Here, the modification operation on the default level description information in the operation area can be, for example, deleting the default level description information, modifying the default level description information, adding level description information, etc. The target level description information can be the level description information related to New Level 1 input by the user in the operation area of Figure 5 .

[0144] Exemplarily, it can be in response to the modification operation on the default level description information in the operation area for Figure 5 to obtain the level description information input by the user. In response to the user's operation on the default level description information in the operation area of Figure 5Operate the trigger save button, and use the level description information obtained at this time as the target level description information. Then, the target level description information can be saved as the node description information of the newly created level 1. At the same time, the obtained target level description information can be synchronously updated and displayed in the newly created level 1 in the level flow chart editing area, that is, the node description information corresponding to the newly created level 1 in the level flow chart editing area is also synchronously updated to the target level description information.

[0145] If the user triggers Figure 5 the cancel button in, the current edit can be cancelled in response to this trigger operation, and all the obtained level description information can be ignored. The node description information of the newly created level 1 remains the default level description information.

[0146] In another implementation, it is also possible to respond to the trigger Figure 4 the ending selection button among the type selection buttons shown, determine that the newly added level node is a newly added ending node with preset ending description information, and display the preset ending description information in the operation area, and the preset ending description information can also be displayed in the corresponding newly added ending node in the level flow chart editing area.

[0147] After that, in response to the modification operation on the preset ending description information in the operation area, the newly input ending description information can be obtained, and the preset ending description information in the newly added level node can be updated to the new ending description information. At the same time, the new ending description information can be synchronously updated and displayed in the newly created ending node in the level flow chart editing area.

[0148] In one embodiment, for the above S102-1, it can be implemented according to the following steps:

[0149] S102-1-1: In response to the selection operation on the created level node, display each created exit point and created entry point of the created level node; wherein, the created exit point is used to establish the connection relationship between the created level node and the subsequent level node, and the created entry point is used to establish the connection relationship between the created level node and the previous level node.

[0150] Here, the previous level node is the level node located in front of the created level node, the subsequent level node is the level node located behind the created level node, and the created exit point can be used to establish the connection relationship between the created level node and the subsequent level node or the subsequent ending node. For example, in Figure 3 Level node 1 is the previous level node of level node 2, and ending node 1 is the subsequent ending node of level node 2.

[0151] In one embodiment, a created exit point of a created level node can also be used to establish a connection relationship with a created entry point of the created level node. In this way, a loop of the level corresponding to the created level node can be achieved.

[0152] A level node can have at least one exit point and at least one entry point, and the exit points and entry points corresponding to each level node can be created at any time as needed.

[0153] For the selection operation on a created level node, it can be an operation where the user hovers the mouse over the created level node for more than a preset duration. After responding to the selection operation on the created level node, in addition to displaying the created exit points and created entry points of the created level node, the created level node can also be placed in a floating state. Among them, the floating state can be, for example, a grayed-out state, a floating state, etc.

[0154] Exemplarily, it can respond to the user's Figure 3 selection operation on level node 2 in Figure 6 to generate a page as shown in Figure 6 . Among them, Figure 6 in the page, two created exit nodes (i.e., created exit node 1 and created exit node 2) and one created entry point (i.e., created entry point 1) are correspondingly displayed for level node 2, and

[0155] S102-1-2: Respond to the node addition operation confirmed based on the displayed created exit points and created entry points, and generate a new added level node having a connection relationship with the created level node in the level flow chart editing area.

[0156] Here, the node addition operation is an operation of clicking on a created level node that displays created exit points and created entry points and is in a floating state; or, it can also be an operation of clicking on any displayed created exit point or created entry point.

[0157] In specific implementation, it can respond to the operation of clicking on a created level node, and in the level flow chart editing area, determine whether there is a created exit point of the created level node that does not have a connection relationship. If so, a new added level node having a connection relationship with the created exit point can be generated. If not, a new created exit point can be automatically generated for the created level node, and a new added level node having a connection relationship with the new created exit point can be generated.

[0158] Alternatively, in response to an operation of clicking on any of the created exit points that do not have a connection relationship, a new level node having a connection relationship with the created exit point may be generated.

[0159] In another embodiment, for the above S102-1, it may also be implemented according to the following steps:

[0160] Step 1: In response to a configuration operation on the created level node, a node setting pop-up window including an option to add a level exit point is generated.

[0161] Here, the configuration operation on the created level node may be, for example, an operation of right-clicking on the created level node.

[0162] The node setting pop-up window may include an option to add a level exit point, an option to delete a node, an option to reduce a level exit point, and an option to enter a level. Among them, the option to add a level exit point is used to indicate generating a new level exit point, the option to delete a node is used to indicate deleting the created level node, the option to reduce a level exit point is used to indicate deleting one of the created exit points corresponding to the created level node, and the option to enter a level is used to indicate entering the created level node, that is, entering the in-level process editing page described below.

[0163] Exemplarily, in response to a configuration operation by the user on Figure 3 the level node 2, a node setting pop-up window as shown in Figure 7a may be generated on one side of the level node 2.

[0164] In addition, if the user initiates a configuration operation on the created ending node, after responding to the configuration operation, a node setting pop-up window including only the option to delete a node may be generated.

[0165] Step 2: In response to triggering the option to add an exit point in the node setting pop-up window, a new exit point is generated for the created level node.

[0166] Here, triggering the option to add an exit point may specifically be clicking on the option to add an exit point. The exit point name of the new exit point may be incremented sequentially according to the names of the created exit points corresponding to the created level node. For example, if the created exit points corresponding to the created level node include exit point A, exit point B, and exit point C, then the exit point name of the new exit point may be exit point D.

[0167] Step 3: In the case where the new exit point is not connected to other created level nodes in the level flow chart editing area, a new level node having a connection relationship with the new exit point is generated in the level flow chart editing area.

[0168] In specific implementation, after generating a new exit point, it can be determined whether the user has actively established a connection relationship for the new exit point, that is, it is determined whether the new exit point has a connection relationship. Here, whether the new exit point has a connection relationship means: whether the new exit point has a connection relationship with the created entry points corresponding to other created level nodes in the level flow chart editing area, and whether the new exit point has a connection relationship with the created entry points of the created level node itself. If not, then a new level node having a connection relationship with the new exit point can be generated in the level flow chart editing area. If so, then no new level node is generated.

[0169] In one embodiment, the node setting pop-up window may further include an option to enter the level. In specific implementation, in response to the option to enter the level in the node setting pop-up window corresponding to any created level node being triggered, and when it is determined that all the node information corresponding to the created level node has been saved, the in-level process editing page corresponding to the created level node can be entered in the main view mode.

[0170] Here, the main view mode is the view mode corresponding to the in-level process editing page introduced below. The node information includes all the node information related to the triggered created level node. For example, the node information may include level description information, created exit points, created entry points, connection relationships, and other information. The in-level process editing page is used to edit the in-level process corresponding to the created level node. Specific information about the in-level process editing page will be introduced in detail later.

[0171] Since the page where the node setting pop-up window is displayed is the level editing page, the node information corresponding to the created level node can be edited. Therefore, at this time, there may also be some partially edited node information that has not been saved. Therefore, before entering the in-level process editing page corresponding to the created level node, it is necessary to determine whether the node information corresponding to the created level node has been saved. If so, the in-level process editing page corresponding to the created level node can be directly entered in the main view mode.

[0172] If not, a jump confirmation pop-up window can be generated. The jump confirmation pop-up window is used to confirm with the user whether to save the node information corresponding to the created level node and enter the in-level process editing page. Specifically, the jump confirmation pop-up window may display an indication message "Whether to save the node information corresponding to the created level node and enter the in-level process editing page", as well as an OK button and a Cancel button.

[0173] Further, in response to the user clicking the OK button in the jump confirmation pop-up window, the node information corresponding to the created level node can be saved, and the in-level process editing page corresponding to the created level node can be entered in the main view mode. Alternatively, in response to the user clicking the Cancel button in the jump confirmation pop-up window, it can be determined that the user cancels entering the in-level process editing page, and the previous page can be returned.

[0174] For S103, in response to the entry into the level option in the node setting pop-up window corresponding to the target level node being triggered, in the case where it is determined that all the node information corresponding to the target level node has been saved, the in-level process editing page corresponding to the target level node can be entered in the main view mode.

[0175] In the case where it is determined that the node information corresponding to the target level node has not been saved completely, a jump confirmation pop-up window can be generated. Then, in response to the user clicking the OK button in the jump confirmation pop-up window, the node information corresponding to the target level node can be saved, and the in-level process editing page corresponding to the target level node can be entered in the main view mode.

[0176] In one embodiment, in the case where the node setting pop-up window further includes a node deletion option and / or a reduce level exit point option, after the node setting pop-up window is generated, the following at least one operation can be performed according to the node setting pop-up window:

[0177] Operation 1: In response to the node deletion option in the node setting pop-up window being triggered, determine the first node connection relationships corresponding to the respective created exit points and the respective created entry points of the created level node, and delete the created level node and the first node connection relationships in the level flowchart editing area.

[0178] Here, the triggering of the node deletion option can specifically be an operation of clicking the node deletion option.

[0179] The first node connection relationships include the connection relationships corresponding to the respective created exit points of the created level node and the node connection relationships corresponding to the respective created entry points. For example, for Figure 6 the level node 2, the first connection relationship corresponding to the level node 2 can include the connection relationship between the created exit node 1 and the ending node 1 and the connection relationship between the created entry point 1 and the level node 1.

[0180] During specific implementation, in response to a user clicking on the node deletion option in the node settings pop-up window, the respective created exit points and created entry points of the created level node corresponding to the node settings pop-up window can be determined, and the first node connection relationships corresponding to the respective created exit points and the first node connection relationships corresponding to the respective created entry points can be determined. Subsequently, in the level flowchart editing area, the created level node can be deleted, the respective created exit points and their corresponding first node connection relationships can be deleted, and the respective created entry points and their corresponding first node connection relationships can be deleted; at the same time, all background storage data related to the created level node can also be deleted.

[0181] Operation 2: In response to the reduction of level exit points option in the node settings pop-up window being triggered, determine the respective created exit points corresponding to the created level node, and generate an exit point selection pop-up window including the respective created exit points.

[0182] Here, the reduction of level exit points option in the node settings pop-up window being triggered can specifically be an operation of clicking on the reduction of level exit points option. The exit point selection pop-up window can include the respective created exit points. For example, in the case where the created exit points include exit point A, exit point B, and exit point C, exit point A, exit point B, and exit point C can be shown in the exit point selection pop-up window.

[0183] As Figure 7b shown, it is a schematic diagram of an exit point selection pop-up window provided by an embodiment of the present disclosure. For Figure 7b , after responding to a user clicking on the reduction of level exit points option in the node settings pop-up window shown in Figure 7a , according to the respective created exit points corresponding to level node 2 in Figure 7a , an exit point selection pop-up window as shown in Figure 7b can be generated. Among them, since level node 2 in Figure 7a has two created exit points (i.e., exit point 1 and exit point 2), so exit point 1 and exit point 2 are shown in the exit point selection pop-up window shown in Figure 7b .

[0184] Furthermore, in response to a selection operation on any of the created exit points in the exit point selection pop-up window, the second node connection relationship corresponding to the created exit point can be determined, and the created exit point and the second node connection relationship can be deleted.

[0185] Here, the second node connection relationship is the connection relationship corresponding to the created exit point to be deleted.

[0186] Exemplarily, in response to the user's operation of clicking on the created exit point 1 in the exit point selection pop-up window, determine that the second connection relationship corresponding to the created exit point 1 is the connection relationship with the ending node 1. After that, the created exit point 1, the connection relationship between the created exit point 1 and the ending node 1 can be deleted, and at the same time, all the background saved data related to the created exit point 1 can be deleted.

[0187] In one implementation, after generating the level editing page, it is also possible to generate the to-be-connected exit point of the created level node and the connection line corresponding to the to-be-connected exit point in response to the operation of creating the connection relationship for the created level node in the level flow chart editing area.

[0188] Here, the to-be-connected exit point can be an exit point generated at any position (such as the right side) of the created level node, and the connection line is used to establish the connection relationship between the to-be-connected exit point and the created entry point of other level nodes, or to establish the connection relationship between the to-be-connected exit point and any created entry point corresponding to the created level node. The connection relationship creation operation can be the operation of hovering the mouse over the created level node.

[0189] Exemplarily, it can be in response to the user's Figure 3 operation of creating the connection relationship for the level node 1 in, generate the to-be-connected exit point and the connection line corresponding to the to-be-connected exit point on the right side of the level node 1.

[0190] After that, in response to moving the connection line to any other created level node (or any created entry point corresponding to other created level nodes) in the level flow chart editing area, establish the connection relationship between the to-be-connected exit point and any other created level node.

[0191] Exemplarily, it can be in response to the operation of moving the connection line to the newly added level node in the level flow chart editing area, and establish the connection relationship between the to-be-connected exit point and the created entry point of the newly added level node.

[0192] In one implementation, for any created level node displayed in the level flow chart editing area, in response to the trigger operation for the exit point of the created level node, display the exit point name of the triggered target exit point. After that, in response to the user's connection operation for the target exit point, determine the target created node (including the created level node and the created ending node) for which the connection relationship needs to be established, and establish the connection relationship between the target exit point and the target created node. Among them, the connection operation for the target exit point can be the operation of dragging the target exit point.

[0193] Exemplarily, as Figure 8a shown, it is a schematic diagram of triggering a target exit point provided by an example of the present disclosure, where,Figure 8a In the level flow chart editing area in [reference], a game start node, created level nodes 4 and 5 are shown. Among them, level node 4 and level node 5 have no connection relationship, and the operation area shows the level description information of the level nodes. After the user triggers the target exit point of level node 4, the trigger operation can be responded to, and the exit point name of the target exit point (i.e., exit point D in the figure) can be shown. After that, after the user drags exit point D to level node 5, the drag operation can be responded to, and it can be determined that a connection relationship needs to be established with level node 5, and the connection relationship between exit point D and level node 5 is established. As Figure 8b shown, it is a connection schematic diagram of exit point D and level node 5 provided by an embodiment of the present disclosure.

[0194] In addition, it can also respond to the user's drag operation on any created node, place the mouse in a preset state, update the position of the created node in the level flow chart editing area, and update the shape of the connection line of the created node. Exemplarily, in response to the drag operation on Figure 8b the shown level node 5, place the mouse in a preset state (such as Figure 8c the mouse shown in the preset state), and then, determine the operation position corresponding to the drag operation, and update the position of level node 5 in the level flow chart editing area from the position shown in Figure 8b to the position shown in Figure 8d ; and update the shape of the connection line between level node 4 and level node 5 from the shape shown in Figure 8b to the shape shown in Figure 8d . In this way, the user can flexibly update the position of the created node.

[0195] In one implementation, in the case that a created ending node of the ending type (such as the ending node 1 shown in Figure 3 ) is also shown in the level flow chart editing area, after generating the level editing page, it can also respond to the trigger operation on the created ending node, and display the initial ending description information of the created ending node in the operation area.

[0196] Here, the trigger operation on the created ending node can specifically be an operation of clicking on any created ending node shown in the level flow chart editing area. The initial ending description information is the node description information of the created ending node. For the ending node 1 shown in Figure 3 , its corresponding initial ending description information is ending description information 1.

[0197] Exemplarily, it can respond to the user's click on the ending node 1 in Figure 3 , and display the initial ending description information corresponding to the ending node 1 in the operation area, as shown in Figure 9As shown, the operation area displays the ending description information 1 (i.e., "Ending: The brave warrior is dejected").

[0198] Then, in response to a modification operation on the initial ending description information in the operation area, the target ending description information input by the user can be obtained. After that, the initial ending description information of the created ending node can be updated to the target ending description information and displayed in the created ending node in the level flowchart editing area.

[0199] Exemplarily, in response to the user's modification operation on the ending description information 1 in the operation area as shown Figure 9 the target ending description information input by the user can be obtained. After that, the node description information corresponding to ending node 1 can be updated to the target ending description information, and the target ending description information can be displayed in ending node 1 in the level flowchart editing area.

[0200] It should be noted that for the ending node of the ending type, there can only be an entry point and no exit point. For the entry point of the process node, whether it is the entry point of the level node or the entry point of the ending node, the entry point of a process node can establish a connection relationship with at least one exit point. Since during the game process, there is no situation where one comes out of an exit point of a level node and enters two level nodes at the same time, for any exit point of a level node, if the subsequent node of this exit point is a node of the level type, then this exit point is only allowed to have a connection relationship with one entry point of this subsequent node. And if an exit point of a process node has a connection relationship with multiple entry points, then this exit point must be the exit point of an in-level process node of a certain level node. As Figure 10a shown, it is a connection schematic diagram of the exit point of a level node provided by an embodiment of the present disclosure. Among them, nodes A, B, and C are all level nodes. Node A has two exit points (exit point X and exit point Y). Among them, exit point X has a connection relationship with one entry point of node B, and exit point Y has a connection relationship with one entry point of node C. As Figure 10b shown, it is a connection schematic diagram of the exit point of an in-level process node provided by an embodiment of the present disclosure. Among them, nodes D, E, F, and G are all in-level process nodes. Node D has two exit points (exit point W and exit point Z). Among them, exit point W has a connection relationship with one entry point of node E and at the same time has a connection relationship with one entry point of node F, and exit point Z has a connection relationship with one entry point of node G. As Figure 10cAs shown in the figure, it is a schematic diagram of the connection of an exit point provided by an embodiment of the present disclosure. Among them, nodes H, I, J, and K can all be checkpoint nodes, or node K can also be an ending node. Nodes H, I, and J each show an exit point, and nodes I and K each show an entrance point. The exit point of node H has a connection relationship with the entrance point of node I. The exit points of node I and node J both have a connection relationship with the entrance point of node K. For the entrance point of node K, this entrance point can be triggered once by the exit point that first reaches this entrance point. For example, if the exit point of node I reaches the entrance point of node K earlier than the exit point of node J, then node K will be triggered by the exit point of node I. When the exit point of node J reaches the entrance point of node K, node K will not be triggered by the exit point of node J. Conversely, if the exit point of node J reaches the entrance point of node K earlier than the exit point of node I, then node K will be triggered by the exit point of node J. When the exit point of node I reaches the entrance point of node K, node K will not be triggered by the exit point of node I.

[0201] In one embodiment, a checkpoint viewing button can be displayed on the in-level process editing page.

[0202] As Figure 11 shown in the figure, it is a schematic diagram of an in-level process editing page provided by an embodiment of the present disclosure. Among them, the information editing area in the in-level process editing page can be used to view and edit the node information of any in-level process node of the game level corresponding to any created checkpoint node. The in-level process editor area can be used to display each in-level process node corresponding to any created checkpoint node. The rendering area is used to display the game screen of the target game. The checkpoint viewing button is used to view the node information of the created checkpoint node corresponding to the target game and to trigger the generation of the level editing page. Figure 11 The edit level button indicates that the level is currently being edited; by triggering the shown edit map button, it can be used to edit the game map of the target game; by triggering the shown edit house button, it can be used to edit the map object of the house type. By triggering Figure 11 the shown recycle bin button, the deleted information corresponding to the target game can be obtained. By triggering Figure 11 the shown settings button, it can be used to set the level editing page. Figure 11 The shown folder button is used to select the target game, Figure 11 The shown play button is used to control the play and pause of the game screen. Figure 11 The shown global button is used to create global objects, and the in-level button is used to create in-level entity objects.

[0203] In Figure 11Among them, the entity display area is used to display each entity corresponding to the target game. The entity display area may specifically include an in-level entity display area, a global entity display area, an entity list selection button, and a trigger area selection button. Among them, the in-level entity display area is used to display the entity object names of each entity object in the currently triggered level, specifically including Entity A to Entity E; the global entity display area is used to display the entity object names of entity objects that appear in each level corresponding to the target game, specifically including Entity F and Entity G. The trigger area selection button is used to trigger the display of the names of each game screen area in the entity display area. For example, Game Screen Area A, Game Screen Area B, etc. The move button is used to move entity objects and game screens, the rotation button is used to rotate entity objects and game screens, and the zoom button is used to zoom entity objects and game screens.

[0204] After displaying the in-level process editing page corresponding to the target level node, a level editing page can also be generated in response to the triggering of the level viewing button.

[0205] Here, the triggering of the level viewing button can specifically be the clicking of the level viewing button.

[0206] Exemplarily, it can respond to the user clicking Figure 11 the shown level viewing button to generate Figure 2 the shown level editing page.

[0207] In addition, after displaying the in-level process editing page corresponding to the target level node, information viewing can also be performed according to the following steps:

[0208] S1: Generate a level navigation floating layer in response to the selection operation on the level viewing button.

[0209] Here, the selection operation on the level viewing button can be the operation of hovering the mouse over the level viewing button.

[0210] The level navigation floating layer displays the latest switched level node corresponding to the target game, the previous level node and the subsequent nodes of the latest switched level node. The latest switched level node can be a level node with the smallest difference between the editing time and the current time, or can be a level node with the smallest difference between the viewing time and the current time. Exemplarily, the latest switched level node can be the target level node. The subsequent node of the latest switched level node can be a subsequent level node or a subsequent ending node. The node description information of the latest switched level node can be displayed in the latest switched level node, but the node description information of the previous level node and the description information of the two subsequent nodes are not displayed. For example Figure 12aAs shown in the figure, it is a schematic diagram of a level navigation floating layer provided by an embodiment of the present disclosure. Among them, the latest switched level node, a previous level node and two subsequent nodes of the latest switched level node are displayed in the level navigation floating layer, and the node description information of the latest switched level node is "The brave man sets off alone and is defeated by the general of the demon king."

[0211] Optionally, all level nodes corresponding to the target game and the process relationship between the nodes can be displayed in the level navigation floating layer. When the game is initialized, the latest switched level node can be the default level, and the level name can be "Unnamed Level".

[0212] Exemplarily, it can respond to the user hovering the mouse over Figure 11 the shown level viewing button operation to generate a level navigation floating layer.

[0213] S2: In response to the previous level node being triggered, display the level description information of the previous level node in the level navigation floating layer.

[0214] Here, the operation of the previous level node being triggered can be the operation of the user moving the mouse to the previous level node and hovering over it.

[0215] Taking the level description information of the previous level node as "The brave man receives the task of defeating the demon king" as an example, it can respond to Figure 12a the shown previous level node being triggered, generate a description information display pop-up window in the level navigation floating layer, and display the level description information of the previous level node (i.e., "The brave man receives the task of defeating the demon king") in the description information display pop-up window. And, the node description information of the latest switched level node can still be displayed in the latest switched level node. As Figure 12b shown, it is a schematic diagram of displaying the level description information of the previous level node in the description information display pop-up window provided by an embodiment of the present disclosure, where the level description information of the previous level node (i.e., "The brave man receives the task of defeating the demon king").

[0216] S3: In response to the subsequent node being triggered, when the subsequent node is a subsequent level node, display the level description information of the subsequent level node in the level navigation floating layer; when the subsequent node is a subsequent ending node, display the ending description information of the subsequent ending node in the level navigation floating layer.

[0217] Here, the operation of the subsequent node being triggered can be the operation of the user moving the mouse to the subsequent node and hovering over it.

[0218] During specific implementation, when the subsequent node is a subsequent level node, a description information display pop-up window can be generated in the level display floating layer, and the level description information of the subsequent level node can be displayed in the description information display pop-up window; or, when the subsequent node is a subsequent ending node, the ending description information of the subsequent ending node can be displayed in the description information display pop-up window.

[0219] In one embodiment, the target level node can also include any created level node in the level flow chart editing area. Exemplarily, when the node editing operation is an editing operation for the created level node 1 in the level flow chart editing area, the target level node is the created level node 1. From the above Figure 11 It can also be known that the in-level process editing page further includes an information editing area, an in-level process editor area, and an entity display area; the in-level process editor area is used to display each in-level process node of the target level corresponding to the created level node; the entity display area is used to display the names of each entity object matching the target level; each in-level process node is used to represent at least one established in-level process corresponding to the target level. Among them, the target level is the actual game level corresponding to the target level node in the game. The entity object is each game object that appears in the target level, for example, characters, buildings, objects, etc. in the level. An entity object has an entity object name. For example, the entity object name corresponding to character A is Xiaohong, and the entity object name corresponding to building A is Library.

[0220] The target level can include at least one established in-level process node. Different in-level process nodes can have different in-level node types, such as conditional judgment type, node exit type, trigger type, task type, performance type, etc. Each in-level process node can at least form the main process corresponding to the target level. Of course, the in-level process nodes can also form a side process other than the main process.

[0221] After generating and displaying the in-level process editing page, for the step of "editing the in-node process information of the target level node through the in-level process editing page" in S103, the in-level process of the created level node can also be edited according to the following steps:

[0222] P1: In response to a node addition operation for the target process node in the in-level process node, in the in-level process editor area, generate an in-level node addition item having a connection relationship with the target process node, and in response to triggering the in-level node addition item, generate a first selection button in the in-level process editor area for indicating the creation of various in-level node types of new in-level nodes.

[0223] Here, the target process node can be any one of the process nodes in the in-level process nodes. The node addition operation is an operation for adding a new process node to the target level. Regarding the node addition operation for the target process node, reference can be made to the above-mentioned node addition operation in the in-level flowchart editing area, which will not be elaborated here.

[0224] As Figure 13 shown, it is a schematic diagram of a first selection button provided by an embodiment of the present disclosure. Among them, two processes are displayed in the in-level process editor area, namely the main process and Process 13. The main process trigger node is used to indicate the trigger of the main process, and Process 13 is used to indicate the trigger of the branch process. Both the main process and Process 13 are trigger type nodes. In response to the node addition operation for the target process node (the node corresponding to Process 13), a new in-level node addition item as shown in Figure 13 can be generated. Then, the user can click on the in-level node addition item to generate a first selection button in the in-level process editor area (i.e., the Figure 13 corresponding new task button for the task type, the new performance button for the performance type, the new condition judgment button for the condition judgment type, and the new node exit button for the node exit type shown).

[0225] After any first selection button is triggered, the in-level node addition item will become a node with the in-level node type corresponding to the first selection button, and will be named by default according to the in-level node type. Such as [Task / Performance / Judgment / Exit|X], where in tasks and performances, X is the task name or performance name, in condition judgments, X is the judgment condition, and at the exit point, X is the exit name.

[0226] P2: In response to the second selection button related to the target in-level node type being triggered, a new in-level node with the target in-level node type is generated in the in-level process editor area; the new in-level node has a connection relationship with the target process node.

[0227] Here, the second selection button can be the first selection button actually triggered by the user. For example, in the case where the user clicks the new performance button in Figure 13 , the second selection button is the new performance. The target in-level node type is the in-level node type corresponding to the second selection button.

[0228] Exemplarily, in response to the new task button for the task type being triggered, a task node of the task type can be generated in the in-level process editor area, and the default information corresponding to the newly generated task node is displayed in the information editing area. Then, in response to the user's modification operation on the default information, the modified node information corresponding to the newly generated task node can be obtained.

[0229] In one embodiment, when the node type in the target level is of the conditional judgment type, for the above P2, the following steps can be implemented:

[0230] First, in response to the triggering of a second selection button related to the conditional judgment type (i.e., in response to clicking the new conditional judgment button), a new conditional judgment node can be generated in the in-level process editor area, and a setting area for conditional judgment items can be displayed in the information editing area; the setting area includes a setting box for judgment condition variables and a selection box for conditional judgment exits.

[0231] Here, the setting box for judgment condition variables can be used to set the variables corresponding to the judgment conditions. For example, "variable = False", "variable C = True", etc. The selection box for conditional judgment exits can be used to select the conditional judgment exit points. Among them, the available conditional judgment exits for selection can be the exits within the created level, and the exits within the created level can specifically include the exits created for the new conditional judgment node and the exits created for other nodes within the created level.

[0232] When a new conditional judgment node is newly generated, a default exit point can be created for the new conditional judgment node.

[0233] The preset conditional judgment description information, that is, "find the first exit that meets the condition from top to bottom", can also be displayed by default in the setting area. That is, one judgment condition variable corresponds to one conditional judgment exit point. When there are multiple conditional judgment exit points, different conditional judgment variables have different judgment priorities. When performing conditional judgment, it is possible to determine whether the judgment condition variables are met according to the priorities, and use the conditional judgment exit point corresponding to the first met conditional judgment variable as the determined exit point.

[0234] Second, in response to the triggering of the setting box, the input first target conditional variable can be displayed.

[0235] Here, the operation of triggering the setting box can be the operation of clicking the setting box.

[0236] Optionally, after responding to the clicking of the setting box, the conditional variable actively input by the user in the setting box can also be obtained and used as the first target conditional variable.

[0237] Finally, in response to the triggering of the selection box, all the exits within the created level are displayed, and the first target in-level exit selected from the exits within the created level is used as the target in-level exit corresponding to the first target conditional variable.

[0238] Here, the operation of triggering the setting box can be the operation of clicking the drop-down button in the selection box.

[0239] The function of the exit within the target level corresponding to the target conditional variable is to use the exit within the target level as the exit when the target conditional variable is satisfied.

[0240] In specific implementation, after determining the first target conditional variable and the exit within the first target level, it indicates that a judgment condition corresponding to the newly created conditional judgment node is set, and a newly created conditional judgment node can correspond to one or more judgment conditions.

[0241] To add a judgment condition to the newly created conditional judgment node, the setting area may also include an add button for conditional judgment information. In specific implementation, in response to triggering the add button, a new setting box and a new selection box can be generated. In the new setting box and the new selection box, default information can be displayed or it can be empty. Then, in response to triggering the new setting box, the third target conditional variable input by the user can be obtained. And, in response to triggering the new selection box, the exits within each created level are displayed, and the exit within the third target level selected from the exits within the created levels is used as the exit within the target level corresponding to the third target conditional variable. In addition, it is possible to add a judgment condition to any conditional judgment node.

[0242] In one embodiment, when the node type within the target level is the node exit type, for the above P2, the following steps can be implemented:

[0243] In response to the second selection button related to the node exit type being triggered (that is, in response to the new node exit button being clicked), a newly created exit within the level with default exit information is generated in the in-level process editor area, and an in-level exit setting box is displayed in the information editing area; the in-level exit setting box defaults to displaying the newly created exit within the level.

[0244] Here, the default exit information can be the exit name information obtained after incrementing the name of the newly created exit within the level in sequence. The in-level exit setting box defaults to displaying the newly created exit within the level. Among them, during the process of creating the exit within the level, in response to the user clicking the drop-down button in the in-level exit setting box, the exits within each created level are displayed, and the exits within the created levels include the newly created exit within the level. In this way, the user can timely obtain each exit within the created levels.

[0245] In one embodiment, the in-level process node can include a node of the node exit type, and a node of the node exit type can be displayed in the in-level process editor area. For the node of the node exit type, in response to triggering any node of the node exit type (such as clicking any node of the node exit type), an in-level exit setting box is displayed in the information editing area; the in-level exit setting box defaults to displaying the exit within the level corresponding to the triggered node of the node exit type.

[0246] As shown Figure 14 in the figure, it is a schematic diagram of an in-level exit setting box provided by an embodiment of the present disclosure. Among them, after responding to the user's click on Figure 14 the node exit type node (Exit A) in it, the in-level exit setting box can be displayed in the information editing area. The in-level exit setting box defaults to display Exit A and the drop-down button.

[0247] After that, in response to triggering the in-level exit setting box, each created in-level exit corresponding to the target level can be displayed.

[0248] Here, the operation of triggering the in-level exit setting box can be the operation of clicking the drop-down button of the in-level exit setting box. The created in-level exits can include the in-level exits corresponding to all the created in-level nodes corresponding to the target level.

[0249] Exemplarily, after responding to the user's click on the drop-down button in the in-level exit setting box of Figure 14 , a drop-down box with Exit A, Exit B, and Exit C can be displayed.

[0250] Finally, in response to any of the displayed created in-level exits being triggered, the triggered created in-level exit can be used as the new in-level exit corresponding to the triggered node exit type node.

[0251] Exemplarily, it can be determined that the node exit type node changes from Exit A to Exit B in response to the user's click on Exit B in the drop-down box with Exit A, Exit B, and Exit C displayed.

[0252] It should be noted that there is no exit for the node exit type node. That is, a node exit type node cannot have other node exit type nodes with a connection relationship.

[0253] In one embodiment, the in-level process nodes include trigger type nodes, such as Figure 13 the main process trigger node and the process 13 trigger node shown.

[0254] Specifically, when implementing, the node information of the trigger type node can be edited according to the following steps:

[0255] In response to triggering any trigger type node, a trigger list is displayed in the information editing area, and the trigger attribute information of the trigger corresponding to any trigger type node is displayed in the trigger list.

[0256] Here, the trigger attribute information can include information such as the trigger count, output conditions, target entity objects related to the trigger, and target game screen areas. The trigger list is used to display the trigger information of each trigger.

[0257] As shown Figure 15 in the figure, it is a schematic diagram of a trigger list provided by the present disclosure. Among them, Figure 15 it can be a page generated after the user triggers the Figure 13 node 13 of the process shown. The information displayed in the trigger list scrolls to the trigger attribute information of the trigger corresponding to node 13 of the process, as well as the trigger attribute information corresponding to the condition judgment node. For the trigger attribute information of each trigger, it can include a trigger times setting box for setting the trigger times, a delete button for deleting the trigger, and a sorting button for changing the position of the trigger attribute information in the trigger list. The trigger list can also include a trigger addition button for adding a new trigger and its corresponding trigger attribute information. The addition of the trigger and the trigger attribute information can be achieved by triggering the trigger button

[0258] In one embodiment, when the in-level process node includes a trigger type node and the level editing page includes a rendering area for displaying the game screen of the target game, after displaying the in-level process editing page corresponding to the target level node, it can also respond to triggering any trigger type node, and determine the target entity object and / or the target game screen area related to the trigger corresponding to any trigger type node indicated by the trigger attribute information corresponding to any trigger type node

[0259] Exemplarily, for Figure 13 the trigger corresponding to node 13 of the process shown, the target entity object related to this trigger can be Entity B, and the target game screen area related to this trigger can be game screen area A

[0260] Furthermore, when the target entity object and / or the target game screen area meet the preset conditions, the entity object name of the target entity object and / or the target game screen area name can be prominently displayed in the entity display area, and the target entity object and / or the target game screen area can be prominently displayed in the rendering area

[0261] Here, the preset conditions can be that the target entity object is an entity object inside the house, and the target game screen area is the game screen area inside the house

[0262] In specific implementation, when the target entity object and / or the target game screen area meet the preset conditions, the entity object name of the target entity object can be prominently displayed in the entity display area by default, and the target entity object can be prominently displayed in the rendering area. At the same time, in response to the user's operation of clicking the selection button in the trigger area, the target game screen area name can be prominently displayed in the entity display area, and the target game screen area can be prominently displayed in the rendering area

[0263] Exemplarily, in Figure 15 , the target entity object corresponding to the node of process 13 is entity B, and entity B is an entity object inside the house in the rendering area. Therefore, when responding to the user clicking on the node of process 13, entity B can also be prominently displayed in the rendering area, and the entity object name of entity B can be prominently displayed in the entity object display area. Moreover, the basic information and pose of entity B corresponding to the trigger can also be displayed in the information editing area.

[0264] If the target entity object related to the trigger corresponding to any trigger type node triggered does not meet the preset conditions, or the target game screen area related to the trigger does not meet the preset conditions, then it may not be displayed in the rendering area and the entity object display area.

[0265] Exemplarily, if entity B corresponding to the node of process 13 is an entity object outside the house, then it is not prominently displayed in the rendering area and the entity object display area.

[0266] In one embodiment, when the process nodes in the level include condition judgment type nodes, the information of the condition judgment type nodes can also be modified according to the following steps:

[0267] In response to triggering any condition judgment type node, a condition judgment item setting area is displayed in the information editing area; the condition judgment item setting area displays an add button for condition judgment information and each created condition judgment item matching the condition judgment type node; the created condition judgment item includes a setting box displaying the selected condition variable and a selection box displaying the selected exit within the level.

[0268] As Figure 16 shown, it is a schematic diagram of triggering a condition judgment type node provided by an embodiment of the present disclosure. Among them, the process nodes within the level include a condition judgment type node (i.e., the "judgment [variable C = false]" node in Figure 16 , and this condition judgment type node currently has two exits, namely exit A and exit B. The preset condition judgment description information, i.e., "find the first exit that meets the condition from top to bottom", is displayed in the condition judgment item setting area. There are two created condition judgment items matching the "judgment [variable C = false]" node. In the setting box of the first created condition judgment item, variable C = False is displayed, and exit A is displayed in the selection box; in the setting box of the second created condition judgment item, variable C = True is displayed, and exit B is displayed in the selection box. The add button is the button located below the second created condition judgment item in Figure 16 .

[0269] Exemplarily, when clicking on Figure 16After the "Judge [Variable C = false]" node in, the content displayed in the information editing area is as follows Figure 16 as shown.

[0270] It should be noted that whether it is a process node within a level or a level node and an ending node, when they are clicked, they can all be set to a preset color. For example, blue, gray, etc.

[0271] In response to triggering the setting box in any of the created condition judgment items, obtain the input second target condition variable, and use the second target condition variable as the new selected condition variable of the triggered created condition judgment item.

[0272] Exemplarily, it can respond to the user's click Figure 16 on the setting box of the first created condition judgment item in, obtain the new input second target condition variable by the user in the setting box, and use the second target condition variable as the new selected condition variable of the "Judge [Variable C = false]" node.

[0273] In response to triggering the selection box in any of the created condition judgment items, display each created exit within the level, and use the second target exit within the level selected from the created exits within the level as the new selected exit within the level of the triggered created condition judgment item.

[0274] Exemplarily, it can respond to the user's click Figure 16 on the drop-down button in the selection box of the first created condition judgment item in, generate a drop-down box for displaying each created exit within the level, that is Figure 16 the drop-down box shown in which shows Exit A and Exit B. After that, it can respond to the user's operation of clicking Exit B in the drop-down box, and use Exit B as the second target exit within the level. Finally, Exit B can be used as the new selected exit within the level of the "Judge [Variable C = false]" node.

[0275] In addition, in Figure 16 for each created condition judgment item, there can also be a delete button and a sort button corresponding to it. Among them, the delete button is used to delete the created condition judgment item, and the sort button is used to change the up and down sorting of the created condition judgment items.

[0276] Exemplarily, it can respond to the user's click Figure 16 on the delete button corresponding to the second created condition judgment item in, and delete the second created condition judgment item.

[0277] Exemplarily, it can respond to the user in Figure 16In the condition judgment item setting area, the operation of dragging the sorting button corresponding to the second created condition judgment item will move the second created condition judgment item to the position of the first created condition judgment item, and the original position of the first created condition judgment item will adaptively move to the position of the second created condition judgment item.

[0278] In one embodiment, after presenting the in-level process editing page, it is also possible to generate an in-level setting pop-up window including an option to add a process node exit point in response to a configuration operation for a process node to be modified among the in-level process nodes.

[0279] Here, the process node to be modified is the in-level process node where the user places the mouse above and clicks the right mouse button.

[0280] As Figure 17 shown, it is a schematic diagram of an in-level setting pop-up window provided by an embodiment of the present disclosure. After responding to the user's right-click operation on the performance type node (i.e., performance 1 node) in Figure 17 , it is possible to generate an in-level setting pop-up window including an option to add a process node exit point (i.e., add an exit point in Figure 17 ), an option to delete an in-level process node (i.e., delete in Figure 17 ), and an option to reduce the process node exit point (i.e., reduce the exit point in Figure 17 ).

[0281] After that, it is possible to determine the third node connection relationships corresponding to each created in-level exit point and each created in-level entry point of the process node to be modified in response to the trigger of the in-level process node deletion option (e.g., clicking the in-level process node deletion option), and delete the process node to be modified and the third node connection relationships in the in-level process editor area.

[0282] Here, the functions of the various options in the in-level setting pop-up window can refer to the options in the node setting pop-up window. Regarding the operation of deleting the process node to be modified, it can refer to the operation of deleting the created in-level node and the first node connection relationship in the above embodiment.

[0283] In the case where the process node to be modified is a task type node, a trigger type node, and a node exit type node, after responding to the configuration operation for the process node to be modified, the in-level setting pop-up window generated may only include an option to delete an in-level process node. As Figure 18 shown, it is a schematic diagram of an in-level setting pop-up window corresponding to a task type node provided by an embodiment of the present disclosure, which only includes an option to delete an in-level process node.

[0284] If the trigger type node is deleted, the corresponding target entity object and / or target game screen area of the trigger type node will be deleted, but each other in-level process node having a connection relationship with the trigger type node will not be deleted.

[0285] In one implementation, it is also possible to respond to the triggering of adding a process node exit point option to generate a new in-level exit point for the process node to be modified.

[0286] Exemplarily, it can respond to the user clicking Figure 17 the add process node exit point option in the in-level settings pop-up window shown in the figure to generate a new in-level exit point for the performance 1 node, and sequentially increment the naming for the new in-level exit point. For example, the new in-level exit point corresponding to the performance 1 node can be exit point 0.

[0287] Furthermore, in the case where the new in-level exit point is determined and there is no connection between the new in-level exit point and other in-level process nodes except the process node to be modified among the in-level process nodes, an in-level node new item having a connection relationship with the new in-level exit point is generated in the in-level process editor area.

[0288] Exemplarily, in the case where exit point 0 is not connected to Figure 17 the task type node shown in the figure, an in-level node new item having a connection relationship with exit point 0 can be generated, and this in-level node new item is also the in-level node new item corresponding to the performance 1 node.

[0289] Regarding the operation of generating a new in-level exit point for the process node to be modified, reference can be made to the operation of generating a new exit point for the created in-level node in the above embodiment, and details will not be repeated here.

[0290] Of course, it is also possible to respond to the triggering of the reduce process node exit point option, determine each created in-level exit point corresponding to the process node to be modified, and generate an in-level exit point selection pop-up window including each created in-level exit point.

[0291] In response to the selection operation for any created in-level exit point in the in-level exit point selection pop-up window, determine the fourth node connection relationship corresponding to the created in-level exit point, and delete the created in-level exit point and the fourth node connection relationship.

[0292] Here, regarding the operation after the reduce process node exit point option is triggered, reference can be made to the operation when the node deletion option in the node settings pop-up window in the above embodiment is triggered, and details will not be repeated here.

[0293] It should be noted that for operations such as deletion, movement, and connection of process nodes within a level, the operation types such as deletion, movement, and connection of the created level nodes in the above embodiments, and the specific operation processes, can all refer to the introduction of the created level nodes above, and will not be elaborated here.

[0294] Those skilled in the art can understand that in the above method of the specific implementation manner, the writing order of each step does not mean a strict execution order that constitutes any limitation on the implementation process, and the specific execution order of each step should be determined according to its function and possible internal logic.

[0295] Based on the same inventive concept, the embodiments of the present disclosure also provide a game level editing device corresponding to the game level editing method. Since the principle of solving problems by the device in the embodiments of the present disclosure is similar to the above game level editing method of the embodiments of the present disclosure, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be elaborated.

[0296] As Figure 19 shown, it is a schematic diagram of a game level editing device provided by an embodiment of the present disclosure, including:

[0297] A first display module 1901, configured to display a level editing page of a target game; the level editing page includes a level flow chart editing area and an operation area; the level flow chart editing area is used to perform flow chart editing on the flow relationship between level nodes; the operation area is used to perform node information editing on the selected level node;

[0298] A first editing module 1902, configured to, in response to a node editing operation acting on the level flow chart editing area, perform a level node editing operation in the level flow chart editing area, and perform information editing on the target level node currently being edited in the operation area;

[0299] A second editing module 1903, configured to, in response to the entry level option for the target level node being triggered, display an in-level process editing page corresponding to the target level node, and edit the in-node process information of the target level node through the in-level process editing page.

[0300] In a possible implementation manner, the node editing operation includes a node addition operation; the target level node includes an added level node.

[0301] When the first editing module 1902 performs a level node editing operation in the level flow chart editing area and performs information editing on the target level node currently being edited in the operation area in response to a node editing operation acting on the level flow chart editing area, it is used for:

[0302] In response to a node addition operation acting on the level flowchart editing area, in the level flowchart editing area, a new level node having a connection relationship with the created level nodes in the level flowchart editing area is generated;

[0303] In response to a trigger operation on the new level node, information editing of the new level node is performed in the operation area.

[0304] In a possible implementation manner, when the first editing module 1902 performs information editing of the new level node in the operation area in response to a trigger operation on the new level node, it is used for:

[0305] In response to a trigger operation on the new level node, type selection buttons for indicating the creation of different types of nodes are generated in the operation area;

[0306] In response to the trigger of the level selection button among the type selection buttons, it is determined that the new level node is a level type node with default level description information; wherein, the default level description information is displayed in the operation area;

[0307] In response to a modification operation on the default level description information in the operation area, the input target level description information is obtained, and the default level description information in the new level node is updated to the target level description information and displayed in the level flowchart editing area.

[0308] In a possible implementation manner, when the first editing module 1902 generates a new level node having a connection relationship with the created level nodes in the level flowchart editing area in response to a node addition operation acting on the level flowchart editing area, it is used for:

[0309] In response to a selection operation on the created level node, all the created exit points and created entry points of the created level node are displayed; wherein, the created exit points are used to establish the connection relationship between the created level node and subsequent level nodes, and the created entry points are used to establish the connection relationship between the created level node and previous level nodes;

[0310] In response to a node addition operation confirmed based on the displayed created exit points and created entry points, a new level node having a connection relationship with the created level node is generated in the level flowchart editing area.

[0311] In a possible implementation, when the first editing module 1902 generates a newly added level node having a connection relationship with the created level nodes in the level flowchart editing area in response to a node addition operation in the level flowchart editing area, it is used for:

[0312] Generating a node setting pop-up window including an option to add a level exit point in response to a configuration operation on the created level node;

[0313] Generating a newly added exit point for the created level node in response to triggering the option to add an exit point in the node setting pop-up window;

[0314] In the case where no other created level nodes in the level flowchart editing area are connected to the newly added exit point, generating a newly added level node having a connection relationship with the newly added exit point in the level flowchart editing area.

[0315] In a possible implementation, the node setting pop-up window further includes the option to enter the level;

[0316] When the second editing module 1903 displays the in-level process editing page corresponding to the target level node in response to the option to enter the level for the target level node being triggered, it is used for:

[0317] In response to the option to enter the level in the node setting pop-up window corresponding to the target level node being triggered, and when it is determined that all the node information corresponding to the target level node has been saved, entering the in-level process editing page corresponding to the target level node in the main view mode.

[0318] In a possible implementation, the node setting pop-up window further includes a node deletion option and / or an option to reduce the level exit points;

[0319] The device further includes: a processing module 1904, configured to perform at least one of the following operations after generating the node setting pop-up window including the option to add a level exit point:

[0320] In response to the node deletion option in the node setting pop-up window being triggered, determining the first node connection relationships corresponding to the respective created exit points and the respective created entry points of the created level node, and deleting the created level node and the first node connection relationships in the level flowchart editing area;

[0321] In response to the option to reduce the level exit points in the node setting pop-up window being triggered, determining the respective created exit points corresponding to the created level node, and generating an exit point selection pop-up window including the respective created exit points;

[0322] In response to a selection operation on any of the created exit points in the pop-up window for the selected exit point, determine the second node connection relationship corresponding to the created exit point, and delete the created exit point and the second node connection relationship.

[0323] In a possible implementation manner, a level viewing button is displayed on the in-level process editing page; the device further includes:

[0324] A second display module 1905, after displaying the in-level process editing page corresponding to the target level node, is configured to:

[0325] In response to a selection operation on the level viewing button, generate a level navigation floating layer; the latest switched level node corresponding to the target game, the previous level node and the subsequent node of the latest switched level node are displayed in the level navigation floating layer;

[0326] In response to the triggering of the previous level node, display the level description information of the previous level node in the level navigation floating layer;

[0327] In response to the triggering of the subsequent node, when the subsequent node is a subsequent level node, display the level description information of the subsequent level node in the level navigation floating layer; when the subsequent node is a subsequent ending node, display the ending description information of the subsequent ending node in the level navigation floating layer.

[0328] In a possible implementation manner, the target level node includes any created level node in the level flowchart editing area; the in-level process editing page further includes an information editing area, an in-level process editor area, and an entity display area; the in-level process editor area is configured to display each in-level process node of the target level corresponding to the target level node; the entity display area is configured to display the names of each entity object matching the target level; each in-level process node is used to represent at least one established in-level process corresponding to the target level;

[0329] The second editing module 1903, when editing the node internal process information of the target level node through the in-level process editing page, is configured to:

[0330] In response to a node addition operation on a target process node in the in-level process node, in the in-level process editor area, generate an in-level node addition item having a connection relationship with the target process node, and in response to triggering the in-level node addition item, generate a first selection button for indicating the creation of various types of in-level nodes for creating a new in-level node in the in-level process editor area;

[0331] In response to the triggering of a second selection button related to the node type within the target level, a new in-level node with the node type within the target level is generated in the in-level process editor area within the level; the new in-level node has a connection relationship with the target process node.

[0332] In a possible implementation manner, when the node type within the target level is a conditional judgment type, the second editing module 1903, when generating a new in-level node with the node type within the target level in the in-level process editor area in response to the triggering of the second selection button related to the node type within the target level, is configured to:

[0333] In response to the triggering of the second selection button related to the conditional judgment type, a new conditional judgment node is generated in the in-level process editor area, and a setting area for conditional judgment items is displayed in the information editing area; the setting area includes a setting box for judgment condition variables and a selection box for conditional judgment exits.

[0334] In response to the triggering of the setting box, the input first target condition variable is displayed.

[0335] In response to the triggering of the selection box, each created in-level exit is displayed, and the first target in-level exit selected from the created in-level exits is used as the in-level exit corresponding to the first target condition variable.

[0336] In a possible implementation manner, the in-level process node includes a node exit type node.

[0337] The second editing module 1903, when editing the in-level process information of the target level node through the in-level process editing page, is configured to:

[0338] In response to the triggering of any node exit type node, an in-level exit setting box is displayed in the information editing area; the in-level exit setting box defaults to displaying the in-level exits corresponding to the triggered node exit type node.

[0339] In response to the triggering of the in-level exit setting box, each created in-level exit corresponding to the target level is displayed.

[0340] In response to the triggering of any displayed created in-level exit, the triggered created in-level exit is used as the new in-level exit corresponding to the triggered node exit type node.

[0341] In a possible implementation manner, the in-level process node includes a trigger type node.

[0342] The second editing module 1903, when editing the in-level process information of the target level node through the in-level process editing page, is used for:

[0343] In response to triggering any trigger type node, display a trigger list in the information editing area, and display the trigger attribute information of the trigger corresponding to the any trigger type node in the trigger list.

[0344] In a possible implementation manner, the in-level process node includes a trigger type node; the level editing page further includes a rendering area, and the rendering area is used for displaying the game screen of the target game;

[0345] The device further includes:

[0346] A rendering module 1906, configured to, after displaying the in-level process editing page corresponding to the target level node, in response to triggering any trigger type node, determine a target entity object and / or a target game screen area related to the trigger corresponding to the any trigger type node indicated by the trigger attribute information of the any trigger type node;

[0347] When the target entity object and / or the target game screen area meet the preset conditions, prominently display the entity object name of the target entity object and / or the name of the target game screen area in the entity display area, and prominently display the target entity object and / or the target game screen area in the rendering area.

[0348] In a possible implementation manner, the in-level process node includes a condition judgment type node;

[0349] The second editing module 1903, when editing the in-level process information of the target level node through the in-level process editing page, is used for:

[0350] In response to triggering any condition judgment type node, display a condition judgment item setting area in the information editing area; the condition judgment item setting area displays an add button for condition judgment information and each created condition judgment item matching the condition judgment type node; the created condition judgment item includes a setting box displaying a selected condition variable and a selection box displaying a selected in-level exit;

[0351] In response to triggering the setting box in any of the created condition judgment items, obtain the input second target condition variable, and use the second target condition variable as the new selected condition variable of the triggered created condition judgment item;

[0352] In response to triggering the selection box in any of the created condition judgment items, display the exits within each created level, and use the exit within the second target level selected from the exits within the created levels as the new selected exit within the level for the triggered created condition judgment item.

[0353] For the processing flow of each module in the device and the interaction flow between modules, reference can be made to the relevant descriptions in the above method embodiments and will not be elaborated here.

[0354] Based on the same technical concept, an embodiment of the present application also provides an electronic device. Referring to Figure 20 As shown, it is a schematic structural diagram of an electronic device provided by an embodiment of the present application, including:

[0355] A processor 2001, a memory 2002, and a bus 2003. Among them, the memory 2002 stores machine-readable instructions executable by the processor 2001. The processor 2001 is used to execute the machine-readable instructions stored in the memory 2002. When the machine-readable instructions are executed by the processor 2001, the processor 2001 performs the following steps: S101: Display a level editing page of a target game; the level editing page includes a level flow chart editing area and an operation area; the level flow chart editing area is used to edit the flow chart of the flow relationship between level nodes; the operation area is used to edit node information for the selected level node; S102: In response to a node editing operation acting on the level flow chart editing area, perform a level node editing operation in the level flow chart editing area, and edit the information of the target level node currently being edited in the operation area, and S103: In response to the entry level option for the target level node being triggered, display a level internal flow editing page corresponding to the target level node, and edit the node internal flow information of the target level node through the level internal flow editing page.

[0356] The above memory 2002 includes an internal memory 2021 and an external memory 2022; the internal memory 2021 here is also called the main memory, which is used to temporarily store the operation data in the processor 2001 and the data exchanged with the external memory 2022 such as the hard disk. The processor 2001 exchanges data with the external memory 2022 through the internal memory 2021. When the electronic device is running, the processor 2001 communicates with the memory 2002 through the bus 2003, so that the processor 2001 executes the execution instructions mentioned in the above method embodiments.

[0357] An embodiment of the present disclosure also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is run by a processor, it executes the steps of the game level editing method described in the foregoing method embodiment. Among them, the storage medium may be a volatile or non-volatile computer-readable storage medium.

[0358] A computer program product of the game level editing method provided by the embodiments of the present disclosure includes a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the steps of the game level editing method described in the foregoing method embodiment. For details, reference can be made to the foregoing method embodiment and will not be elaborated herein.

[0359] The computer program product can be specifically implemented in a manner of hardware, software, or a combination thereof. In an optional embodiment, the computer program product is specifically embodied as a computer storage medium. In another optional embodiment, the computer program product is specifically embodied as a software product, such as a Software Development Kit (SDK), etc.

[0360] Those skilled in the art can clearly understand that for the convenience and conciseness of description, the specific working process of the device described above can refer to the corresponding process in the foregoing method embodiment and will not be elaborated herein. In several embodiments provided by the present disclosure, it should be understood that the disclosed device and method can be implemented in other ways. The device embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and there may be other division methods in actual implementation. For another example, multiple units or components can be combined, or some features can be ignored, or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection to each other can be through some communication interfaces. The indirect coupling or communication connection of the device or unit can be in an electrical, mechanical or other form.

[0361] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place, or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0362] In addition, in each embodiment of the present disclosure, the functional units can be integrated into one processing unit, or each unit exists physically alone, or two or more units are integrated into one unit.

[0363] When the above-mentioned functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium executable by a processor. Based on this understanding, the technical solution of the present disclosure, in essence, or the part that contributes to the prior art, or a part of this 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 enable an electronic device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks, or optical discs.

[0364] If the technical solution of this application involves personal information, before the product applying the technical solution of this application processes personal information, it has clearly informed the personal information processing rules and obtained the personal's autonomous consent. If the technical solution of this application involves sensitive personal information, before the product applying the technical solution of this application processes sensitive personal information, it has obtained the personal's separate consent and at the same time meets the requirement of "express consent". For example, at a personal information collection device such as a camera, a clear and prominent label is set to inform that the personal information collection range has been entered and personal information will be collected. If an individual voluntarily enters the collection range, it is regarded as consenting to the collection of their personal information; or on the personal information processing device, when the personal information processing rules are informed by obvious labels / information, personal authorization is obtained through pop-up messages or by asking the individual to upload their personal information by themselves; among them, the personal information processing rules may include information such as the personal information processor, the purpose of personal information processing, the processing method, and the types of personal information processed.

[0365] Finally, it should be noted that: the above-mentioned embodiments are only specific implementation manners of the present disclosure, used to illustrate the technical solutions of the present disclosure, rather than limiting them. The protection scope of the present disclosure is not limited thereto. Although the present disclosure has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: any person skilled in the art within the technical scope disclosed by the present disclosure can still modify the technical solutions recorded in the foregoing embodiments or can easily think of changes, or perform equivalent replacements on some of the technical features; and these modifications, changes, or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure, and should all be covered within the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be subject to the protection scope of the claims.

Claims

1. A game level editing method, characterized in that, Including: Display a level editing page of the target game; the level editing page includes a level flow chart editing area and an operation area; The level flow chart editing area is used to edit the flow chart of the flow relationship between level nodes; The operation area is used to edit node information for the selected level node; In response to a node editing operation acting on the level flow chart editing area, in the level flow chart editing area, perform a level node editing operation, and in the operation area, edit the information of the target level node being currently edited; In response to the trigger of the enter level option for the target level node, display the in-level flow editing page corresponding to the target level node, and edit the in-node flow information of the target level node through the in-level flow editing page.

2. The method according to claim 1, characterized in that, The node editing operation includes a node addition operation; the target level node includes a newly added level node; The in response to a node editing operation acting on the level flow chart editing area, in the level flow chart editing area, perform a level node editing operation, and in the operation area, edit the information of the target level node being currently edited, includes: In response to a node addition operation acting on the level flow chart editing area, in the level flow chart editing area, generate a newly added level node having a connection relationship with the created level nodes in the level flow chart editing area; In response to a trigger operation for the newly added level node, edit the information of the newly added level node in the operation area.

3. The method according to claim 2, wherein The in response to a trigger operation for the newly added level node, edit the information of the newly added level node in the operation area, includes: In response to a trigger operation for the newly added level node, generate type selection buttons for indicating the creation of different types of nodes in the operation area; In response to the trigger of the level selection button in the type selection buttons, determine that the newly added level node is a level type node with default level description information; wherein, the default level description information is displayed in the operation area; In response to a modification operation for the default level description information in the operation area, obtain the input target level description information, and update the default level description information in the newly added level node to the target level description information, and display it in the level flow chart editing area.

4. The method according to claim 2, characterized in that The in response to a node addition operation acting on the level flow chart editing area, in the level flow chart editing area, generate a newly added level node having a connection relationship with the created level nodes in the level flow chart editing area, includes: In response to a selection operation for the created level node, display each created exit point and created entry point of the created level node; wherein, the created exit point is used to establish a connection relationship between the created level node and subsequent level nodes, and the created entry point is used to establish a connection relationship between the created level node and previous level nodes; In response to a node addition operation confirmed based on the displayed created exit points and created entry points, in the level flowchart editing area, a new level node having a connection relationship with the created level node is generated.

5. The method according to claim 2, wherein The generating, in the level flowchart editing area, a new level node having a connection relationship with the created level node in the level flowchart editing area in response to a node addition operation performed in the level flowchart editing area includes: In response to a configuration operation on the created level node, a node setting pop-up window including an option to add a level exit point is generated; In response to triggering the option to add an exit point in the node setting pop-up window, a new exit point is generated for the created level node; In the case where the new exit point is not connected to other created level nodes in the level flowchart editing area, in the level flowchart editing area, a new level node having a connection relationship with the new exit point is generated.

6. The method according to claim 5, characterized in that The node setting pop-up window further includes the option to enter the level; The displaying, in response to the option to enter the level being triggered for the target level node, the in-level process editing page corresponding to the target level node includes: In response to the option to enter the level in the node setting pop-up window corresponding to the target level node being triggered, in the case where it is determined that the node information corresponding to the target level node has been saved completely, enter the in-level process editing page corresponding to the target level node in the main view mode.

7. The method according to claim 5, characterized in that, The node setting pop-up window further includes a node deletion option and / or an option to reduce level exit points; After generating the node setting pop-up window including the option to add a level exit point, the following at least one operation is further included: In response to the node deletion option in the node setting pop-up window being triggered, determine the first node connection relationships corresponding to each of the created exit points and each of the created entry points of the created level node, and delete the created level node and the first node connection relationships in the level flowchart editing area; In response to the option to reduce level exit points in the node setting pop-up window being triggered, determine each of the created exit points corresponding to the created level node, and generate an exit point selection pop-up window including each of the created exit points; In response to a selection operation on any of the created exit points in the exit point selection pop-up window, determine the second node connection relationship corresponding to the created exit point, and delete the created exit point and the second node connection relationship.

8. The method according to claim 1, characterized in that, A level viewing button is displayed in the in-level process editing page; After displaying the in-level process editing page corresponding to the target level node, the following is further included: In response to a selection operation on the level viewing button, a level navigation floating layer is generated; the latest switched level node corresponding to the target game, the previous level node and the subsequent nodes of the latest switched level node are displayed in the level navigation floating layer; In response to the previous level node being triggered, display the level description information of the previous level node in the level navigation floating layer; In response to the triggering of the subsequent node, when the subsequent node is a subsequent level node, display the level description information of the subsequent level node in the level navigation floating layer; when the subsequent node is a subsequent ending node, display the ending description information of the subsequent ending node in the level navigation floating layer.

9. The method according to claim 1, wherein The target level node includes any created level node in the level flow chart editing area; the in-level process editing page further includes an information editing area, an in-level process editor area, and an entity display area; the in-level process editor area is used to display each in-level process node of the target level corresponding to the target level node; the entity display area is used to display the names of each entity object matching the target level; each in-level process node is used to represent at least one established in-level process corresponding to the target level. The editing of the node in-level process information of the target level node through the in-level process editing page includes: In response to a node addition operation for a target process node in the in-level process nodes, in the in-level process editor area, generate a new in-level node item having a connection relationship with the target process node, and in response to triggering the new in-level node item, generate a first selection button for indicating the creation of various types of in-level nodes for the new in-level node in the in-level process editor area. In response to the triggering of a second selection button related to the target in-level node type, generate a new in-level node having the target in-level node type in the in-level process editor area; the new in-level node has a connection relationship with the target process node.

10. The method according to claim 9, characterized in that, When the target in-level node type is a conditional judgment type, the generating, in response to the triggering of a second selection button related to the target in-level node type, of a new in-level node having the target in-level node type in the in-level process editor area includes: In response to the triggering of a second selection button related to the conditional judgment type, generate a new conditional judgment node in the in-level process editor area, and display a setting area for conditional judgment items in the information editing area; the setting area includes a setting box for judgment condition variables and a selection box for conditional judgment exits. In response to the triggering of the setting box, display the input first target condition variable. In response to the triggering of the selection box, display each created in-level exit, and use the first target in-level exit selected from the created in-level exits as the target in-level exit corresponding to the first target condition variable.

11. The method according to claim 9, wherein The in-level process node includes a node exit type node. The editing of the node in-level process information of the target level node through the in-level process editing page includes: In response to triggering any node exit type node, display an in-level exit setting box in the information editing area; the in-level exit setting box defaults to displaying the in-level exit corresponding to the triggered node exit type node. In response to triggering the exit setting box within the level, display each created in-level exit corresponding to the target level; In response to any of the displayed created in-level exits being triggered, use the triggered created in-level exit as the new in-level exit corresponding to the triggered node exit type node.

12. The method according to claim 9, characterized in that, The in-level process nodes include trigger type nodes; Editing the node internal process information of the target level node through the in-level process editing page includes: In response to triggering any trigger type node, display a trigger list in the information editing area, and display the trigger attribute information of the trigger corresponding to the any trigger type node in the trigger list.

13. The method according to claim 9, wherein The in-level process nodes include trigger type nodes; the level editing page further includes a rendering area for displaying the game screen of the target game; After displaying the in-level process editing page corresponding to the target level node, further include: In response to triggering any trigger type node, determine the target entity object and / or target game screen area related to the trigger corresponding to the any trigger type node indicated by the trigger attribute information of the any trigger type node; When the target entity object and / or target game screen area meet the preset conditions, prominently display the entity object name of the target entity object and / or the name of the target game screen area in the entity display area, and prominently display the target entity object and / or the target game screen area in the rendering area.

14. The method according to claim 9, characterized in that, The in-level process nodes include condition judgment type nodes; Editing the node internal process information of the target level node through the in-level process editing page includes: In response to triggering any condition judgment type node, display a condition judgment item setting area in the information editing area; the condition judgment item setting area displays an add button for condition judgment information and each created condition judgment item matching the condition judgment type node; the created condition judgment item includes a setting box displaying the selected condition variable and a selection box displaying the selected in-level exit; In response to triggering the setting box in any of the created condition judgment items, obtain the input second target condition variable, and use the second target condition variable as the new selected condition variable of the triggered created condition judgment item; In response to triggering the selection box in any of the created condition judgment items, display each created in-level exit, and use the second target in-level exit selected from the created in-level exits as the new selected in-level exit of the triggered created condition judgment item.

15. A game level editing device, characterized in that, Include: A first display module for displaying the level editing page of the target game; the level editing page includes a level flow chart editing area and an operation area; The level flow chart editing area is used for flowchart editing of the process relationship between level nodes; The operation area is used for editing node information for the selected level node; The first editing module is configured to, in response to a node editing operation performed in the level flowchart editing area, perform a level node editing operation in the level flowchart editing area and perform information editing on the target level node being currently edited in the operation area; The second editing module is configured to, in response to the entry level option for the target level node being triggered, display the in-level process editing page corresponding to the target level node and edit the in-node process information of the target level node through the in-level process editing page.

16. An electronic device, characterized in that, Comprising: A processor and a memory, where the memory stores machine-readable instructions executable by the processor, and the processor is configured to execute the machine-readable instructions stored in the memory. When the machine-readable instructions are executed by the processor, the processor performs the steps of the game level editing method according to any one of claims 1 to 14.

17. A computer-readable storage medium, characterized in that, A computer program is stored on the computer-readable storage medium. When the computer program is run by an electronic device, the electronic device performs the steps of the game level editing method according to any one of claims 1 to 14.

Images