Component editing methods and program products

By generating operation guides and detecting user touch operations in the game editing scene, and automatically executing undetected operations, the problem of players having difficulty mastering component editing independently is solved, achieving more efficient teaching conversion and enriching game content.

CN123101971APending Publication Date: 2026-11-17NETEASE (HANGZHOU) NETWORK CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611216140.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-11
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In sandbox or UGC games, players struggle to independently master component editing operations, resulting in poor learning outcomes and low teaching conversion efficiency of editing systems. This is mainly because intelligent tools employ a black-box execution mode, making it impossible for players to perceive the spatial hierarchy and configuration logic of components.

Method used

This paper provides a component editing method that obtains the editing requirements of the game editing scene, generates and displays operation guidance, detects the user's touch operation, and automatically executes the guidance if no operation is received within the first time threshold, generating the next operation guidance. This enables flexible switching between manual and automatic modes, significantly reduces the operation threshold and improves the smoothness of human-computer interaction.

Benefits of technology

By making the editing process transparent, the cognitive threshold for operation is lowered, the continuous execution of editing tasks is ensured, users' enthusiasm for creating complex game content is increased, the richness of game content is enhanced, and the task scheduling efficiency of the graphical user interface is optimized.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123101971A_ABST
    Figure CN123101971A_ABST
Patent Text Reader

Abstract

This disclosure provides a component editing method and program product, which acquires editing requirements for a game editing scenario; generates and displays a first operation guide on the game editing scenario interface based on the editing requirements; detects whether a touch operation corresponding to the first operation guide is received through the graphical user interface within a first time threshold; if a touch operation is detected within the first time threshold, controls the execution of the editing operation corresponding to the first operation guide; if no touch operation is detected within the first time threshold, controls the automatic execution of the editing operation corresponding to the first operation guide; and generates a second operation guide when the editing operation corresponding to the first operation guide meets preset conditions. This allows the system to transform the black-box automatic editing process into a transparent step-by-step teaching demonstration in a visual manner without interrupting the user's current operation flow, thereby reducing the cognitive threshold of operation while ensuring the continuous execution of editing tasks.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the gaming industry, and in particular to a component editing method and program product. Background Technology

[0002] In sandbox or UGC games, players typically create custom content by dragging and dropping components, configuring parameters, and building scenes. The editor provides a variety of functional components for players to combine to achieve personalized gameplay design.

[0003] In related technologies, intelligent auxiliary tools typically complete component editing by receiving natural language commands and then directly writing data in the background or silently executing automated scripts. Players only receive the final result and have little to no awareness of the editing process. Meanwhile, some platforms employ a mentorship model where experienced users guide novices through social networks to configure components and build scenes.

[0004] However, since most intelligent tools in related technologies adopt a black-box execution mode, players cannot perceive the spatial hierarchy and configuration logic of components, and it is difficult to reproduce the operation independently after being removed from the guidance. This results in poor learning effect and low teaching conversion efficiency of the editing system. Summary of the Invention

[0005] The purpose of this disclosure is to provide a component editing method, apparatus, electronic device, and program product to solve the problem in the related art where black-box execution makes it difficult for players to independently master component editing operations.

[0006] In a first aspect, this disclosure provides a component editing method, which obtains editing requirements for a game editing scenario; generates and displays a first operation guide on the game editing scenario interface based on the editing requirements; detects whether a touch operation corresponding to the first operation guide is received through a graphical user interface within a first time threshold; if a touch operation is detected within the first time threshold, controls the execution of the editing operation corresponding to the first operation guide; if no touch operation is detected within the first time threshold, controls the automatic execution of the editing operation corresponding to the first operation guide; and generates a second operation guide when the editing operation corresponding to the first operation guide meets preset conditions.

[0007] Optionally, determine the component interaction trajectory data required to complete the editing based on the editing requirements; generate the first operation guide corresponding to the component interaction trajectory data.

[0008] Optionally, the component interaction trajectory data includes at least one of the following: the component's category affiliation information, spatial displacement information, and logic editing information; wherein, the category affiliation information includes: the category menu information to which the component belongs; the spatial displacement information includes: the component's movement position information in the game editing scene; and the logic editing information includes the code editing information that controls the execution of game logic.

[0009] Optionally, while displaying the operation guide corresponding to the editing needs or automatically executing the editing operation corresponding to the first operation guide, the interactive object in the game editing scene interface is kept in a triggerable state; in response to the touch operation on the interactive object, while maintaining the state of displaying the operation guide corresponding to the editing needs or automatically executing the editing operation corresponding to the first operation guide, the editing command corresponding to the touch operation is controlled to be executed.

[0010] Optionally, in response to a touch operation on an interactive object, if the editing instruction corresponding to the touch operation and the editing requirement meet a preset degree of irrelevance, and while the editing requirement is in a state of maintaining the display of the operation guide corresponding to the editing requirement or automatically executing the editing operation corresponding to the first operation guide, the editing instruction corresponding to the touch operation is controlled to be executed.

[0011] Optionally, the component interaction trajectory corresponding to the first operation guide can be dynamically displayed in the graphical user interface.

[0012] Optionally, control the display of an auxiliary demonstration panel in the graphical user interface, and display the component interaction trajectory corresponding to the first operation guide in the auxiliary demonstration panel.

[0013] Optionally, in response to the current display interface not meeting the conditions of the target interface, an auxiliary demonstration panel is controlled to be displayed, wherein the target interface is the interface targeted by the editing operation corresponding to the first operation guide; the editing operation being performed or to be performed in the target interface is controlled to be displayed in the auxiliary demonstration panel.

[0014] Optionally, obtain the scene status information after executing the editing operation corresponding to the first operation guide; generate the second operation guide based on the scene status information and editing requirements.

[0015] Optionally, the first operation guidance includes at least one of text prompts, voice prompts, and dynamic image demonstrations.

[0016] Optionally, in response to a trigger operation on the auxiliary demonstration panel, control the saving of the editing state of the currently displayed interface and control the jump from the current displayed interface to the target interface.

[0017] In a second aspect, this disclosure provides an electronic device including a processor and a memory, wherein the processor executes instructions in the memory to perform the steps in the component editing method described in any of the preceding claims.

[0018] Thirdly, this disclosure provides a computer program product that stores a computer program, which, when executed by a processor, performs the steps in the component editing method described in any of the preceding claims.

[0019] This disclosure provides a component editing method, electronic device, and program product. By acquiring editing requirements for game editing scenarios and generating corresponding operation guides, it can flexibly switch between manual and automatic execution modes based on user response status. This allows users with weaker learning abilities to understand the component editing logic during browsing, significantly reducing the operational threshold and improving the naturalness and smoothness of human-computer interaction. Simultaneously, by continuously detecting user touch responses under the first operation guide and automatically generating a second operation guide when conditions are met, it achieves automated connection and multi-step continuous demonstration of the editing tutorial process, effectively expanding the teachable component editing complexity and gameplay construction dimensions, thereby enhancing the richness of game content. Furthermore, by automatically executing the corresponding editing operation when no user operation is detected instead of entering an invalid waiting state, it reduces the processing idle time caused by waiting for user response, optimizing the task scheduling efficiency and overall performance of the graphical user interface. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 A schematic diagram of a system architecture according to an embodiment of this disclosure is shown; Figure 2 A flowchart illustrating a component editing method according to an embodiment of this disclosure is shown; Figure 3 A schematic diagram of a game editing scene interface according to an embodiment of this disclosure is shown. Figure 4 A schematic diagram of an interface for a first operation guide according to an embodiment of this disclosure is shown; Figure 5 A schematic diagram of an interface illustrating a second operation guide according to an embodiment of this disclosure is shown; Figure 6 A schematic diagram of an interface for displaying an auxiliary demonstration panel is shown in an embodiment of this disclosure; Figure 7 This illustration shows a graphical programming interface in an embodiment of the present disclosure; Figure 8A schematic diagram of an electronic device according to an embodiment of the present disclosure is shown. Detailed Implementation

[0022] Exemplary embodiments of this disclosure will be described more fully below with reference to the accompanying drawings.

[0023] The accompanying drawings are schematic illustrations of this disclosure and are not necessarily drawn to scale. Some block diagrams shown in the drawings may be functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in hardware modules or integrated circuits, or in networks, processors, or microcontrollers. Implementations can be carried out in various forms and should not be construed as limited to the examples set forth herein. The features, structures, or characteristics described in this disclosure can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough description of embodiments of this disclosure. However, those skilled in the art will recognize that one or more specific details may be omitted when implementing the technical solutions of this disclosure, or other methods, components, apparatuses, steps, etc., may be used to replace one or more specific details.

[0024] To make the objectives, technical solutions, and advantages of this disclosure clearer, the embodiments of this disclosure will be described in further detail below with reference to the accompanying drawings.

[0025] Figure 1A system architecture diagram of the operating environment of this embodiment is shown. This system architecture may include a first client 110, a second client 120, and a server 130. The first client 110 and the second client 120 are terminal devices that have installed and run game client programs, such as mobile phones, tablets, personal computers, smart wearable devices, game consoles, etc. They have display functions and can display a graphical user interface, which may include the operating system interface or the application interface. The first client 110 is the client used by the first game account, and the second client 120 is the client used by the second game account; that is, the game client program running on the first client 110 is logged into the first game account, and the game client program running on the second client 120 is logged into the second game account. The server 130 generally refers to the backend system providing game services in this exemplary embodiment; it can be a single server or a cluster of multiple servers. A game server program is deployed on the server 130 to perform server-side game data processing. The first client 110, the second client 120, and the server 130 can be connected via wired or wireless communication links for data transmission. For example, the first client 110 can send information (such as an editing assistance request) to the second client 120 through the server 130, and the second client 120 can send information (such as an edited first game lineup) to the first client 110 through the server 130. In addition, the first client 110 and the second client 120 can also communicate directly through wired or wireless means.

[0026] In one implementation, the above method can be implemented and executed based on a cloud interaction system. The cloud interaction system can be based on the aforementioned system architecture. Various cloud applications can run under the cloud interaction system, such as cloud gaming. Taking cloud gaming as an example, cloud gaming refers to a gaming method based on cloud computing. In the cloud gaming operating mode, the game program's execution entity and the game screen presentation entity are separated. The storage and execution of in-game control and interaction methods are completed on the cloud gaming server (such as the aforementioned server 130). The cloud gaming client (such as the aforementioned first client 110 and second client 120) includes receiving and sending data, as well as presenting the game screen. For example, the cloud gaming client can be a display device with data transmission capabilities located close to the user, such as a mobile terminal, television, computer, or PDA; while the information processing is performed by the cloud gaming server in the cloud. When playing or editing, the player operates the cloud gaming client to send operation commands to the cloud gaming server. The cloud gaming server runs the game according to the operation commands, encodes and compresses game screen data, returns it to the cloud gaming client via the network, and finally decodes and outputs the game screen through the cloud gaming client.

[0027] This embodiment provides a component editing method. Figure 2 This is a flowchart of a component editing method according to an embodiment of the present disclosure, such as... Figure 2 As shown, the process includes the following steps: Step S110: Obtain the editing requirements for the game editing scenario; Step S120: Generate and display the first operation guide in the game editing scene interface according to the editing requirements; Step S130: Detect whether a touch operation corresponding to the first operation guide is received through the graphical user interface within the first time threshold. Step S140: If a touch operation is detected within the first time threshold, control the execution of the editing operation corresponding to the first operation guide. Step S150: If no touch operation is detected within the first time threshold, control the automatic execution of the editing operation corresponding to the first operation guide; Step S160: When the editing operation corresponding to the first operation guide meets the preset conditions, a second operation guide is generated.

[0028] The method provided in this embodiment enables the system to transform the black-box automated editing process into a transparent, step-by-step tutorial demonstration in a visual manner without interrupting the user's current workflow. This lowers the cognitive threshold for operation while ensuring the continuous execution of editing tasks. Through non-interrupting guidance and an automatic fallback mechanism, this method significantly improves the human-computer interaction experience for users creating game content. By transforming abstract logical configurations into followable, concrete operational steps, it effectively stimulates users' enthusiasm for creating complex game content, thereby enhancing the overall richness of the game content. Furthermore, by transforming background automated execution into visible, step-by-step guidance and status progression in the foreground, it effectively solves the technical problem of user dependency caused by information gaps in intelligent editing tools.

[0029] The steps described above are explained in detail below.

[0030] In step S110, the editing requirements for the game editing scenario are obtained. Specifically, in response to the user's input behavior, the system collects the user's editing intent or logic building requirements, which are used to instruct the system to execute subsequent component editing or logic generation functions.

[0031] The game editing scene interface provides users with a graphical interactive window that allows for the visual arrangement of virtual components and the configuration of logical rules. The embodiments of this application are not limited to the specific form of the interface; for example, it can be a two-dimensional planar layout editing window, a three-dimensional spatial editing viewport, or a layered, overlaid editing panel.

[0032] In some embodiments, the game editing scene interface is a multi-functional integrated panel that includes a menu bar, a canvas area, and an attribute bar. For example, Figure 3 As shown, a hierarchical navigation menu is distributed at the top of the panel, the main canvas in the middle is for dragging and arranging components, and the configuration properties of the currently selected object are displayed on the right.

[0033] In some embodiments, the game editing scene interface is a responsive editing window with a flexible layout that adapts to different terminal resolutions. For example, on mobile terminals, the toolbar and editing area are presented in a vertically stacked manner, while on tablet terminals, the auxiliary information bar is expanded and displayed in a horizontally split manner.

[0034] The embodiments of this application are not limited to the above-mentioned interface forms. For example, the system can provide a fixed-layout desktop editing interface, or it can automatically switch to a responsive layout according to the device type, supporting multiple interface presentation forms in the same system.

[0035] The game editing scene serves as a spatial carrier for users to freely arrange virtual game components and configure their operational logic. The embodiments of this application are not limited to the specific form of the scene; for example, it can be an open-world sandbox, small scene units with level-based structures, or a modular, piecemeal scene space.

[0036] In some embodiments, the game editing scene is a three-dimensional spatial editing area that supports nested multi-level objects. For example, after placing basic buildings on the main surface area, the user can overlay floating platforms on them and place trigger mechanisms inside the platforms to form a three-dimensional scene structure.

[0037] In some embodiments, the game editing scene is a planar editing canvas that employs a grid snapping mechanism. For example, the user drags and drops the character's spawn point, obstacles, and finish line flag into the corresponding grid cells on the canvas, and the system automatically aligns each component to a standard coordinate grid to maintain a neat scene layout.

[0038] The embodiments of this application are not limited to the above-described scenario forms. For example, the system can provide a pure flat canvas scene, or allow users to switch to a three-dimensional space mode in a flat scene through specific operations, thereby realizing the integration of two-dimensional and three-dimensional editing capabilities.

[0039] Interactive controls are interface elements deployed in the editing interface to allow users to trigger editing functions or provide feedback on input commands. This application's embodiments are not limited to the specific form of interactive controls; for example, they can be function buttons floating on the scene, option icons in the edge toolbar, or selectable component entities within the scene. Interactive operations can be implemented through clicking, swiping, long-pressing, etc. Taking clicking as an example, users use a stylus or finger to select a function entry point on the interface, conveying editing requests to the system.

[0040] In some embodiments, the interactive control is a mode switching button located in the function navigation bar at the bottom of the interface. For example, such as Figure 3 As shown, users can enter an editing state specifically for configuring component trigger relationships by clicking the logic editing mode button on the navigation bar.

[0041] In some embodiments, the interactive control is a target component within the scene canvas that can be directly clicked. For example, when a user long-presses and releases an enemy unit icon in the scene, the system recognizes this as an instruction to edit the component's attributes and pops up the corresponding parameter adjustment panel.

[0042] The embodiments of this application are not limited to the above-described interactive control forms. For example, the system can provide global function buttons in the edge toolbar, or it can provide selectable component entities in the scene at the same time, so that users can initiate editing interactions through multiple entry points.

[0043] The method for obtaining editing requests is not limited to one specific approach. For example, it could involve receiving text descriptions input by the user, identifying scene objects selected by the user, or parsing function menu commands triggered by the user. Taking a click operation as an example, when a user selects a target menu item or virtual component in the graphical user interface, the system obtains the editing requests specific to the game's editing scenario.

[0044] In some embodiments, obtaining editing requirements refers to logical construction instructions determined after natural language text is entered into the input box and its semantics are parsed. For example, such as Figure 3 As shown, when a user enters the phrase "add jump mechanism" in the text field of a pop-up window on the interface, the system determines, after semantic parsing, that a trigger-type jump platform needs to be configured in the current level.

[0045] In some embodiments, obtaining an edit request is a scene arrangement request determined in response to a user selecting a target object in the component library. For example, if a user selects an enemy unit icon in the category list in the sidebar and drags it to the scene canvas, the system recognizes an edit request to add an enemy character.

[0046] The embodiments of this application are not limited to the above-described acquisition methods. For example, users can describe the overall logic through text input, or they can select a single object from the component library while inputting text. The system determines the current editing requirements based on the combined results of multiple inputs.

[0047] In step S120, a first operation guide is generated and displayed on the game editing scene interface according to the editing requirements. Specifically, the system analyzes the component editing logic to be executed based on the parsed editing requirements, generates corresponding visual teaching prompts, and renders the prompts to the corresponding display area of ​​the game editing scene interface to guide the user's operation.

[0048] In this application, the first operation guide is generated according to the editing requirements. The specific generation method is not limited to the specific generation method. For example, the natural language requirements can be decomposed into menu navigation paths, the object configuration intent can be mapped into the attribute adjustment order, or the logical building requirements can be compiled into component assembly steps.

[0049] In some embodiments, a first operation guide is generated based on editing requirements. The editing requirements can be parsed into a step-by-step guided script that includes the target component category and the target placement location. For example, if the system analyzes that a pickable prop needs to be added to the scene, a guided script can be generated that first selects a square box from the resource library and then drags it to the specified coordinates in the scene.

[0050] In some embodiments, a first operation guide is generated based on editing needs, which can generate structured prompt data containing the operation object identifier and execution sequence number. For example, if the system determines that lighting and camera parameters need to be adjusted, it generates guidance data to sequentially select the sunlight icon and modify the brightness slider, then select the view controller and zoom in.

[0051] The embodiments of this application are not limited to the above-described generation methods. For example, the system can generate a simple guide script containing only a single step, or it can simultaneously generate multi-stage composite guide data that includes component selection, position dragging, and parameter adjustment.

[0052] In this embodiment, the first operation guide is displayed in the game editing scene interface. The specific display form is not limited to this embodiment. For example, the guide mark can be rendered on the floating layer at the edge of the scene, the interaction trajectory can be superimposed on the scene canvas, or the focus frame can be presented around the target component.

[0053] In some embodiments, displaying the first operation guide in the game editing scene interface can be done using a non-modal pop-up, presenting prompts and dynamic arrows in the corner areas of the interface. For example, displaying guidance information for adding obstacles in the upper right corner of the interface, with a semi-transparent animated arrow pointing to the corresponding block category entry in the component library, such as... Figure 4 As shown, arrows are displayed on component 2 to guide the player's actions. Furthermore, the number of these first action guides can be one or more. When the system breaks down the editing requirements to obtain the editing logic, it can control the simultaneous display of one or more action guides based on complexity, relevance, or other conditions. For example... Figure 4 The first operation guide (1) and the first operation guide (2) shown in the text indicate that component 2 is dragged from the component interface to a specific position in the game editing scene.

[0054] In some embodiments, when displaying a first operation guide in the game editing scene interface, the operation guide can be rendered in sync with the scene layer, so that the guide marker maintains a fixed relative position as the scene view moves. For example, a halo marker that follows the screen coordinates is generated above the target component, and the halo always floats directly above the component when the user rotates the scene view.

[0055] The embodiments of this application are not limited to the above display forms. For example, the system can display static indicator guidance at the edge of the interface, or it can overlay a dynamic highlight mark in the center of the scene while displaying the indicator to achieve dual text and image prompts.

[0056] In step S130, it is detected whether a touch operation corresponding to the first operation guide is received through the graphical user interface within a first time threshold. Specifically, after generating and displaying the first operation guide, the system starts timing monitoring to determine whether an expected touch event triggered by the user on the graphical user interface according to the guide is collected within a set time range.

[0057] Among them, the detection of whether a touch operation corresponding to the first operation guide is received within the first time threshold is not limited to the specific form of detection in this application embodiment. For example, it can detect whether the user clicked the button pointed to by the guide within a specified number of seconds, whether the sliding trajectory was completed according to the guide path, or whether a long press gesture was performed on a specified area.

[0058] In some embodiments, detecting whether a touch operation corresponding to the first operation guide is received within a first time threshold can involve listening for whether the user has selected the target interactive object within a five-second window period after the guide is displayed. For example, the system prompts the user to drag a red square to the blue area, and then continuously detects whether the user has performed a valid tap or drag action on the red square within a countdown.

[0059] In some embodiments, detecting whether a touch operation corresponding to the first operation guide is received within a first time threshold can be achieved by continuously comparing the overlap between the user's touch coordinates and a preset effective touch area during the operation guide activation period. For example, if the system prompts the user to click on the property panel in the upper right corner, the system compares each touch position of the user with the screen area of ​​the property panel during the listening period to determine whether the corresponding touch operation has been received.

[0060] The embodiments of this application are not limited to the above detection methods. For example, the system can determine whether there is a valid click only at the end of a fixed time period, or it can continuously compare the overlap between the touch trajectory and the area within a fixed time period. The two detection mechanisms can run in parallel to improve the recognition accuracy.

[0061] In step S140, if a touch operation is detected within the first time threshold, the system controls the execution of the editing operation corresponding to the first operation guide. Specifically, when the system determines that the user has completed the corresponding touch operation according to the first operation guide within a specified time, the system controls the game editing scene to execute the component change or logic configuration function corresponding to the guide.

[0062] In this embodiment, the control of the editing operation corresponding to the first operation guide is not limited to the specific execution content. For example, it may be to control the addition of the selected component to the target position, to assign new behavioral attributes to a specified object, or to adjust the spatial pose of existing elements in the scene.

[0063] In some embodiments, if a touch operation is detected within a first time threshold, the system controls the execution of the editing operation corresponding to the first operation guide. For example, after the user selects a springboard in the component library, the system instantiates the virtual object and places it at the ground coordinates of the scene. For instance, if the user clicks the spring device icon under the terrain enhancement category within the time limit, the system immediately generates a physical model of the spring device at the current cursor position in the scene.

[0064] In some embodiments, if a touch operation is detected within a first time threshold, the system controls the execution of the editing operation corresponding to the first operation guide. This can be achieved by the system modifying the physical parameters of the corresponding component based on the endpoint value of the slider after the user drags the attribute slider. For example, if the user drags the resistance adjustment slider from the default value to the maximum value within a time limit, the system updates the resistance coefficient configuration of the fluid region in the scene accordingly.

[0065] The embodiments of this application are not limited to the above-described execution methods. For example, the system can either perform the addition operation after the user selects the component, or automatically adjust its initial attribute parameters according to the user's additional touch input while adding the component.

[0066] It should be noted that the editing operation corresponding to the first operation guide can be executed in a semi-automatic manner. That is, it detects the initial operation triggered by the user and then automatically executes the target result embedded in the operation guide, such as the target generation location, the target value of the attribute, or other logic. Alternatively, it can execute the corresponding logic entirely based on the user's operation. However, since the user's operation is based on the first operation guide, the user's final operation corresponds to the operation expectation corresponding to the first operation guide.

[0067] In step S150, if no touch operation is detected within the first time threshold, the system automatically executes the editing operation corresponding to the first operation guide. Specifically, if the system detects that no touch response from the user based on the first operation guide has been collected by the end of the set time, the background automatically completes the editing operation corresponding to that guide to ensure that the editing process is not interrupted.

[0068] When no touch operation is detected within the first time threshold, the editing operation is automatically executed. The embodiments of this application are not limited to specific automatic execution methods. For example, it can be to automatically insert the target component into the specified scene coordinates, automatically establish a default connection relationship for logical nodes, or automatically restore the preset standard template configuration.

[0069] In some embodiments, if no touch operation is detected within the first time threshold, the system can automatically execute the editing operation corresponding to the first operation guide. At the end of the time limit, the system can move the block component corresponding to the current prompt from the resource area to the building area. For example, as... Figure 4 As shown, the system prompts the user to drag and drop component 2, but the user does not perform any operation. After three seconds, the system automatically places the component in the suggested position in the game editing scene and completes the angle initialization. Figure 5 The target component is shown in the image.

[0070] In some embodiments, if no touch operation is detected within the first time threshold, the system can automatically execute the editing operation corresponding to the first operation guide, and silently trigger a preset script to complete the missing content entities in the current editing stage. For example, if the system prompts to add a trigger but the user does not respond, the system will then automatically generate a sensing area of ​​a default size near the scene channel object according to the editing needs and bind an activation event.

[0071] The embodiments of this application are not limited to the above-described automatic execution methods. For example, the system can either automatically drag and drop to place components, or automatically continue to assign associated attributes after placement, forming a complete automatic editing loop.

[0072] In step S160, when the editing operation corresponding to the first operation guide meets the preset conditions, a second operation guide is generated. Specifically, the system evaluates whether the currently executed editing operation has achieved a stage goal or met specific state conditions. When the conditions are met, guidance information for the next operation step is generated and output to advance the overall editing process.

[0073] In this embodiment, the generation of the second operation guide is not limited to specific triggering content. For example, it may be a selection guide for the next component after the current component is placed, a parameter adjustment prompt for the next node after the current logical node is connected, or a global effect preview guide after the current scene area is arranged.

[0074] In some embodiments, a second operation guide is generated when the editing operation corresponding to the first operation guide meets preset conditions. This second operation guide can be generated after detecting that the previous component has been successfully placed on the target canvas, and the system can output a dynamic prompt pointing to the configuration of attributes for the previous component. For example, ... Figure 5After confirming that the player has placed the starting platform at the origin of the coordinates, the system generates a second operation guide (1) to guide the player to select the component, and after clicking the second operation guide (1), the player selects the second operation guide (2) of the attribute settings from the corresponding navigation bar.

[0075] In some embodiments, a second operation guide is generated when the editing operation corresponding to the first operation guide meets preset conditions. This allows the system to generate subsequent guidance prompting the user to perform an overall functional test after the current editing operation reaches the minimum operable unit state. For example, after automatically connecting the trigger and the door opening mechanism, the system generates a second operation guide guiding the user to click the test button in the upper right corner of the interface to verify whether the current mechanism can operate normally.

[0076] The embodiments of this application are not limited to the above generation method. For example, the system can generate the next component addition guide after a single component is placed, or it can output the attribute adjustment guide synchronously when the component configuration is completed, so as to realize parallel multi-dimensional teaching prompts.

[0077] like Figure 3 , 4 As shown in Figure 5, an exemplary application of this application embodiment in a real-world scenario will be described below. The user opens the game editor, and the graphical user interface displays a game editing scene interface containing virtual terrain and a bottom toolbar. The user enters their editing requirements in a dialog box. After the system parses the requirements, a first operation guide appears in the upper right corner of the interface, prompting the user to first select a rotating platform model from the component library and then drag it to the designated position in the center of the scene. The user completes the dragging within three seconds following the guide, and the system immediately executes the corresponding operation, instantiating the rotating platform and placing it in the center of the scene. Next, the system determines that this step is complete and automatically generates a second operation guide, prompting the user to select the platform and adjust the rotation speed in the properties panel. Throughout the process, the guide is displayed as a floating bubble, without interrupting the user's editing operations.

[0078] In one possible implementation, the steps of generating and displaying the first operation guide in the game editing scene interface include: Step S210: Determine the component interaction trajectory data required to complete the editing requirements based on the editing requirements; Step S220: Generate the first operation guide corresponding to the component interaction trajectory data.

[0079] The method provided in this embodiment decodes abstract editing requirements into structured component interaction trajectory data, and then maps it into a visual first operation guide. This makes the background execution logic, which was originally invisible to the user, transparent into perceptible spatial path information. This reduces the user's understanding cost and operation threshold, while expanding the granularity and depth of the game editing function that can be broken down and presented. It also solves the technical problems of missing process data and black box dependence caused by traditional background data writing. This achieves the technical goals of significantly improving the interactive experience, effectively enhancing the richness of game editing, and making the computer execution process transparent.

[0080] The above plan will be explained in detail below.

[0081] For step S210, after the system obtains the user's editing requirements for the game editing scenario, it parses them to obtain a series of component operation path information required to complete the requirements, that is, the complete interaction trajectory data of the component from the source area to the target area.

[0082] The component interaction trajectory data can be understood as structured interaction trajectory data obtained by parsing abstract editing requirements. It includes the component's source location, target spatial path, and program logic editing. This step provides underlying path information support for the subsequent generation of the first operation guide. The interaction trajectory can refer to the change of component position in the scene, or it can refer to the temporal relationship between different interactions, such as the order of operations on different components, or the order of editing different editing contents of the same component.

[0083] Optionally, the system can extract functional keywords from the editing requirements using semantic recognition algorithms and match them with preset component path templates; it can also automatically generate assembly sequence paths based on the hierarchical dependencies between components; or it can calculate the optimal component placement trajectory by combining scene space layout constraints; or it can extract the corresponding logical control requirements according to the editing requirements, thereby generating code editing results, and generating corresponding program code based on the code editing results; or it can rely on the programming system provided by the system to convert it into programming instructions corresponding to the programming system, such as controlling the generation of different code blocks and filling in the corresponding parameters or creating custom functions, etc.

[0084] Taking single component dragging as an example, the system parses the functional description in the editing requirements, extracts the source index of the target component and its target placement area in the scene editing canvas, and forms drag path data containing the spatial coordinates of the menu source and destination. For example, when the editing requirement is to build a teleportation trigger area in the scene, the system parses out that a collision detection module needs to be selected from the physical object set and moved to the central channel coordinates of the scene, generating complete trajectory data of the module from the source area to the target position.

[0085] If the editing requirements involve assembling multiple components, the system can break down the required component nodes step by step according to the logical functional hierarchy, and determine the order and coordinate information of each node in the editing space, forming a time-sequential interaction trajectory data. For example, when creating a points statistics function, the system determines that three components need to be selected from the interface element library in sequence: a text display box, a value binder, and a background container, and specifies the order and relative coordinates of dragging them to the top, middle, and bottom areas of the canvas, respectively.

[0086] Furthermore, if the editing requirements involve custom control logic, the system can analyze the code construction scheme that conforms to the custom control logic based on the code editing functions provided by the system, including which code and parameters are required. For example, if a user needs to create a lighthouse that can fire automatically, then when breaking down the editing requirements, the system needs to generate source guidance for each component, target placement area, and the order in which different components are built. It also needs to determine the code construction scheme that can achieve automatic firing, such as determining the required code blocks (event blocks, control blocks, detection blocks), the splicing order between different blocks, and the parameters that need to be filled in the blocks. Through the above requirements analysis, the final component trajectory data is determined.

[0087] The two methods mentioned above can also be used in combination. For example, the system can extract a single path by matching a preset template with semantic keywords, and also decompose complex requirements containing multiple component nodes hierarchically to generate more complete component interaction trajectory data.

[0088] For step S220, the system converts the determined component interaction trajectory data into visual guidance content that can be presented in the graphical user interface, namely the first operation guide.

[0089] The primary function of the operation guide is to adapt structured interactive trajectory data into visual guidance information for the graphical user interface, providing users with perceptible interactive prompts such as the source and landing point of components. Optionally, the system can encode the trajectory data into a path preview line at the interface level for rendering, or adaptively adjust the display position and stacking order of the guidance elements according to the current interface layout, or choose a presentation format such as a highlighted frame or a fade-out guidance pop-up based on the player's historical operation habits.

[0090] Taking single component dragging as an example, the system renders the component source index and target area coordinates in the trajectory data as guide markers that can be directly identified in the editing scene interface. For example, for the trajectory of a collision detection module dragged from a collection of physical objects to the central passage of the scene, a first operation guide is generated, which includes a highlighted border of the source area, the movement trajectory of the module's ghost image, and a halo marker at the target location.

[0091] For multi-component assembly, the system can generate step-by-step navigation paths and previews of stage landing points based on the time sequence nodes in the trajectory data. For example, for the three components required for the points calculation function, breathing light effects pointing to the corresponding items in the interface element library are generated in sequence, and dashed frame previews of the first landing point, the second landing point, and the third landing point are displayed at the top, middle, and bottom of the canvas, respectively, forming a coherent step-by-step first operation guide.

[0092] The two guidance generation methods mentioned above can coexist. For example, while generating the first operation guidance containing the guidance identifier, a step-by-step navigation path and a time-series preview can be overlaid to combine static guidance with dynamic navigation.

[0093] In one exemplary application of this embodiment, a player submits an editing request for creating portal logic via an auxiliary input panel in the game editing scene interface. Upon receiving this request, the system determines that a region trigger component needs to be selected from the functional component library and dragged to the right boundary coordinates of the scene channel. This generates component interaction trajectory data containing the component's source and target coordinates. This trajectory data is then converted into a first operation guide displayed in the lower right corner of the game editing scene interface. The region trigger component is highlighted on the interface, and its target landing point displays a pulsed halo, allowing the player to follow the guide to complete the component placement and parameter configuration.

[0094] In one possible implementation, the component interaction trajectory data required to complete the editing requirement is determined based on the editing needs. This component interaction trajectory data includes at least one of category affiliation information, spatial displacement information, and logical editing information.

[0095] The category attribution information describes the component's affiliation path within the editing system's menu structure, including the category menu information to which the component belongs. This application's embodiments are not limited to the specific form of the category attribution information; for example, it could be a source directory index, functional grouping tags, or hierarchical nesting identifiers.

[0096] In one possible implementation, the category attribution information is component source path data determined based on the preset functional hierarchy architecture within the game editing system. For example, when building a platforming game, obstacle components belong to the dynamic obstacle submenu under the mechanism item library. The category attribution information records this attribution path to prompt the user to select the target component from the corresponding category menu in the first operation guide.

[0097] For example, when creating a task trigger in a role-playing game, the category information includes the main category of the event system to which the trigger belongs and its subcategories of story triggers, so as to prompt the user to go to the corresponding functional module to retrieve the component in the first operation guide.

[0098] The spatial displacement information includes the component's movement position information within the game editing scene, used to describe the component's layout and placement point in the scene space. This application's embodiments are not limited to the specific form of the spatial displacement information; for example, it can be absolute coordinates, relative coordinates, rotation angles, or scaling factors.

[0099] In one possible implementation, spatial displacement information is a vector displacement record that documents the movement of a component from its initial position to its target placement point within the scene canvas. For example, when placing a starting line marker in a racing game, the spatial displacement information describes the planar coordinate position of the marker component as it is dragged from the resource preview area to the midpoint of the left boundary line of the scene track, and this spatial transfer process is demonstrated in the first operation guide as an animated trajectory.

[0100] The logic editing information includes code editing information that controls the execution of game logic, used to describe the game rules and triggering conditions associated with the component. This application's embodiments are not limited to the specific form of the logic editing information; for example, it can be a visual programming language, script code, conditional judgment parameters, or numerical calculation rules, etc.

[0101] In one possible implementation, the logic editing information is a set of control instructions that describe the behavioral logic of a component through a visual programming language or script code. For example, when editing the door opening and closing mechanism in a puzzle game, the logic editing information includes conditional trigger code that controls the door component to switch from a closed state to an open state when the player character touches the area in front of the door and holds the corresponding key item.

[0102] For example, when creating a resource gathering point in a survival game, the logic editing information records that the remaining storage value of the gathering point decreases after each interaction, and triggers the state transition rules of component appearance change and function failure when the storage reaches zero.

[0103] The following will describe an exemplary application of the embodiments of this application in a real-world application scenario.

[0104] When a player inputs an editing request in the graphical user interface to bind enemy patrol paths to the scene's corridor area, the system determines the component interaction trajectory data required to complete this editing request. This includes category information indicating that the patrol path component belongs to the enemy movement pattern category menu in the AI ​​behavior tree library; spatial displacement information representing the component's movement position from the starting point to the ending point in the corridor area; and logical editing information including code editing information to control the enemy to trigger a backtracking behavior at the path endpoints. Based on the aforementioned component interaction trajectory data, the system generates a corresponding first operation guide and displays it in the game's editing scene interface, guiding the player to complete the selection of the patrol path, spatial layout, and configuration of the associated behavioral logic.

[0105] In one possible implementation, the step of generating the second operation instruction described above may include: Step S310: Obtain scene status information after executing the editing operation corresponding to the first operation guide; Step S320: Generate a second operation guide based on the scene status information and editing requirements.

[0106] Specifically, step S310 is used to collect the component states in the game editing scene after the player completes the editing operation corresponding to the first operation guide, in order to determine the scene changes brought about by the editing operation. The collection methods include, but are not limited to: extracting difference component information by comparing scene snapshots, listening to the editing log to trace back the state change records, and capturing the state change amount in real time based on the component attribute change callback interface.

[0107] Optionally, in one embodiment, in response to the completion of the editing operation corresponding to the first operation guide, a comprehensive collection of the current position, attribute parameters, and hierarchical relationships of each interactive object in the game editing scene is automatically triggered, and a difference comparison is performed with the baseline state before the operation. For example, after the system detects that the player drags the target component from the category menu to the canvas coordinates (120, 240), it automatically extracts the position coordinates, scaling ratio, visibility, and other attributes of all components in the current canvas, compares them with the scene snapshot before the operation, and records the differences as scene state information for use in the subsequent generation and judgment of the second operation guide.

[0108] In another embodiment, during the editing operation, real-time status data of each functional component in the scene is collected in a polling cycle according to a preset period. The system monitors changes in component position, attribute modifications, and additions or deletions, and continuously aggregates the data to form a set of status information reflecting the latest status of the current editing scene. For example, the system reads the current spatial coordinates, rotation angle, and scaling ratio of each interactive object in the game editing scene once per second, while simultaneously detecting whether new components have been added or existing components have been removed. The collected real-time data is then summarized and temporarily stored in a memory buffer.

[0109] It should be noted that the two methods described above can be used individually or in combination. For example, the difference results obtained from automatic triggering can be merged with the real-time data obtained from periodic polling to form complete scene status information.

[0110] For example, after receiving the first operation guide in the game editing scene, the player drags a functional component of a specified type from the category menu to the target location. After detecting that the drag operation has been completed, the system immediately obtains the spatial layout and attribute configuration of each component in the current game editing scene as scene state information, providing a data basis for generating the next operation guide.

[0111] Step S320 is used to deduce the incomplete editing tasks based on the matching relationship between the latest scene state and the original editing requirements, and then generate a second operation guide to guide the user to continue to perform subsequent editing steps. The generation methods include, but are not limited to: matching the gap between rule templates and state requirements, activating the subtask queue in sequence, and calculating the remaining steps based on the requirement goal.

[0112] Optionally, in one embodiment, the scene state information is compared item by item with the editing requirements to identify functional components and logical relationships that are not yet configured or are incompletely configured in the current scene, determine the incomplete editing sub-tasks, and generate the next operation prompts directly corresponding to these incomplete sub-tasks. For example, if the system finds that the current scene lacks the interactive trigger component specified by the editing requirements, a second operation guide is generated, prompting the player to select the trigger icon from the "Logic" tab under the component category menu and drag it to the preset blank mounting point area in the scene editing interface (such as coordinates (300, 500)).

[0113] In another embodiment, the logical dependencies and execution order between functional modules in the editing requirements are analyzed. Combined with the current scene state, the currently met preconditions and unlockable subsequent editing operations are determined. Based on this, a second operation guide is generated to guide the user to execute the next logical configuration step. For example, when the scene status information shows that the terrain laying component has been placed, the system generates a second operation guide based on the rule that the event triggering logic in the editing requirements depends on the terrain preconditions. This guide prompts the player to click to enter the event configuration panel and add collision detection and response logic to the laid terrain area.

[0114] The two generation methods described above can also be used in combination. For example, the comparison results of incomplete tasks can be merged with the logical dependency resolution results to generate a comprehensive second operation guide that includes multiple sub-guides.

[0115] In one exemplary application of this embodiment, a player triggers an editing logic request in the game's scene editing interface via a graphical user interface. Based on this, the system generates a first operation guide, prompting the player to drag a specified functional component from the category menu to the target area on the canvas. After the player performs this operation within the time limit, the system immediately obtains the scene state information after the editing operation, confirming that the functional component has been correctly placed and its attribute parameters have taken effect. Subsequently, based on the comparison between the scene state information and the original editing request, the system generates a second operation guide prompting the player to continue configuring the event response logic of the functional component, thereby realizing progressive editing guidance based on scene state feedback.

[0116] This application embodiment avoids the problem of fixed-sequence guidance being disconnected from the actual state of the scene by promptly sensing changes in the scene state after the execution of the first operation guide and dynamically generating a coherent second operation guide in combination with the original editing requirements. Players obtain a coherent interactive experience while receiving step-by-step guidance. The guidance content, which is adaptively adjusted according to scene changes, further enriches the layers and possibilities of editing operations. At the same time, it realizes a closed loop of state feedback for operation guide generation at the computer interaction level, improving the responsiveness and intelligence level of human-computer interaction.

[0117] In some embodiments, after generating the first operation guide, the terminal can also control the dynamic display of the component interaction trajectory corresponding to the first operation guide in the graphical user interface. For example, the component interaction trajectory is used to indicate the spatial displacement and category affiliation changes of the components required to complete the editing needs within the game editing scene.

[0118] Optionally, dynamically displaying the component interaction trajectory includes, but is not limited to, at least one of the following: playing the complete path of the component's displacement from the source menu level to the scene target coordinates frame by frame at preset time intervals; or breaking down the component interaction trajectory into multiple continuous sub-actions according to the execution sequence and displaying them sequentially.

[0119] In one optional implementation, the terminal plays the complete path of a component moving from the source menu level to the scene target coordinates frame by frame at preset time intervals, and displays the component's category and spatial coordinates at the start and end points of the path, so that the user can intuitively observe the association logic between the component's category and spatial location. For example, when receiving an editing request to add an enemy patrol unit to the scene, the terminal sequentially demonstrates the operation trajectory of dragging the patrol template from the character component library into the scene editor and establishing a movement association between path point A and path point B.

[0120] In another optional implementation, the terminal breaks down the component interaction trajectory into multiple consecutive sub-actions according to the execution sequence, uses a highlighted cursor to connect the start and end states of each sub-action, and inserts transition prompts between adjacent sub-actions to clearly indicate the transition nodes of the operation rhythm. For example, when the editing requirement involves adjusting the logical configuration of weapon attributes, the interface dynamically displays a continuous trajectory segment from expanding the sub-menu of the weapon category, selecting the damage coefficient adjustment slider, and dragging it to the target value area.

[0121] In one specific application, after a user inputs their editing request to add a pickup weapon crate to the scene in the graphical user interface, the terminal dynamically displays a component interaction trajectory between the right-hand item category bar and the central scene canvas in the game scene editing interface. This trajectory uses flashing arrows to sequentially indicate the complete path from selecting the corresponding icon in the weapon crate category menu and dragging it to a preset coordinate point in the scene. After observing this dynamic trajectory, the user performs the corresponding touch operation within a first time threshold, and the terminal then executes the weapon crate placement editing operation and generates a second operation guide for the next step.

[0122] It should be noted that the two implementation methods described above can be used individually or in combination. For example, when used in combination, the terminal can both fully demonstrate the global path and emphasize key sub-action nodes, thus balancing overall viewing with detailed understanding. This application does not limit the specific visual presentation method of dynamic display.

[0123] This embodiment dynamically displays the component interaction trajectory, transforming the component spatial displacement and category logic, originally hidden in the background, into a visual dynamic path presented in the editing scene interface. As a result, users can perceive the complete movement relationship of components from the menu level to the scene coordinates within the same visual space while following or observing the operation guidance, reducing cognitive loss from repeatedly switching between different functional areas and improving the interactive experience. Simultaneously, this concrete and reproducible operation path demonstration lowers the learning threshold of the editing tool, enabling more users to independently master the methods of calling and arranging complex components, stimulating users' creative willingness to generate content and the diversity of scene design, effectively enhancing the game's richness. Furthermore, by dynamically rendering the editing operation trajectory in real time at the graphical user interface level, replacing the traditional silent background scrolling or static text prompts, it solves the problem of information gaps in human-computer interaction caused by the invisible operation chain in existing computer interfaces, improving the completeness and transparency of interface feedback in the editing scene.

[0124] In one possible implementation, the step of controlling the dynamic display of the component interaction trajectory corresponding to the first operation guide in the graphical user interface may include: Step S410: Control the display of an auxiliary demonstration panel in the graphical user interface, and display the component interaction trajectory corresponding to the first operation guide in the auxiliary demonstration panel.

[0125] For example, the auxiliary demonstration panel is used to create a separate, lightweight display area within the game editing scene interface, presenting the interaction trajectory on the same screen. Its presentation forms include, but are not limited to: being attached to the edge of the scene as a sidebar, floating in a picture-in-picture window within a portion of the interface, or embedding the current view as a draggable floating card. For instance, in a 3D scene editing interface, an auxiliary demonstration panel occupying approximately one-quarter of the display area can pop up on the right side of the screen, displayed alongside the main editing scene on the left; alternatively, a semi-transparent floating window can be generated in the lower right corner, without obscuring the central content of the scene.

[0126] The interactive trajectory display methods within the auxiliary demonstration panel include, but are not limited to: outlining the component movement contours sequentially with highlighted outlines, representing continuous displacement with afterimage trailing animations, and displaying category jumps and landing points with node blinking and connection animations. Optionally, the panel can reproduce the complete path of a component dragged from the category menu and moved to the target location in real time, or it can use a step-by-step highlighting combined with path outlining: first, use a highlighted border to select the target component category in the category menu, then use dynamic connections to point to the target landing point area on the simulated canvas, and use blinking dots to indicate the current operation progress.

[0127] In one specific application, the player inputs "add a logic component to trigger a teleportation function" through the AI ​​editing assistant in the graphical user interface. After the system analyzes the request, it generates the first operation guide and pops up an auxiliary demonstration panel occupying about a quarter of the display area on the right side of the screen. Within the panel, a virtual element representing the teleportation component gradually appears and is dragged out from the simulated logic component category menu, then smoothly moves along a curved path with dynamic arrows to the target grid position on the simulated scene canvas. The player can observe the complete trajectory without switching interfaces, while maintaining the main scene editing operation, and then independently reproduce the operation.

[0128] like Figure 6 As shown, in another example, the player needs to create an interactive treasure chest mechanism in the game editing scene. After receiving this request, the system displays a semi-transparent auxiliary demonstration panel in the lower left corner of the graphical user interface. Within the panel, the treasure chest component icon is first highlighted from the simulated mechanism category menu, and then smoothly dragged along a path with guide markers to the target coordinates in the simulated scene. The entire demonstration process is unmasked and the touch buttons on the main interface are not locked, allowing the player to refer to it at any time during the editing process.

[0129] The method provided in this embodiment enables the display of an auxiliary demonstration panel in the graphical user interface, dynamically presenting the component interaction trajectory corresponding to the first operation guide. This compresses the original multi-step operation tutorial into a seamless comparison within the same screen, improving interaction continuity and operational efficiency. This embodiment displays the auxiliary demonstration panel alongside the main editing scene, completing the trajectory demonstration without modal masking. This allows players to obtain the component retrieval path and placement position during editing operations, reducing the learning cost and avoiding the interaction interruption caused by traditional pop-ups obscuring the main editing area.

[0130] In some embodiments, the step of controlling the display of an auxiliary demonstration panel in a graphical user interface includes steps S510-S520.

[0131] Step S510: In response to the current display interface not meeting the target interface conditions, control the display of the auxiliary demonstration panel, wherein the target interface is the interface targeted by the editing operation corresponding to the first operation guide.

[0132] Step S520: Control the display of editing operations being performed or to be performed in the target interface within the auxiliary demonstration panel.

[0133] The method provided in this implementation allows the system to automatically invoke an auxiliary demonstration panel when the user's current interface is not the target interface, and simultaneously display the operation trajectory at the target interface. This eliminates the need for players to forcibly switch interfaces, allowing them to preview the interface context required for subsequent editing operations within their current field of view. This avoids the disruption of flow and increased cognitive load caused by frequent window switching. The parallel information presentation of the auxiliary demonstration panel and the main interface also enables the parallel transmission of information from multiple interfaces in a low-blocking state, reducing system resource overhead and processing latency caused by repeated interface switching.

[0134] In step S510, in response to the current display interface not meeting the target interface conditions, the auxiliary demonstration panel is displayed. Here, the target interface is the interface targeted by the editing operation corresponding to the first operation guide. Specifically, the system detects whether the current display interface is consistent with the functional interface required to complete the current editing operation. If they are inconsistent, the auxiliary demonstration panel is automatically invoked to display the demonstration content of the editing operation at the target interface.

[0135] There are several reasons why the current displayed interface may not meet the conditions for the target interface. In some embodiments, the system monitors the player's interface history switching sequence and preloads the auxiliary demonstration panel when it predicts that the next step will require a jump to the target interface. In other embodiments, the system automatically invokes the auxiliary demonstration panel based on the component selection state in the current editing scene when it detects that a component associated with the target interface has been triggered. In still other embodiments, the system proactively displays the auxiliary demonstration panel based on the task flow nodes of the editing needs when the default interface corresponding to the current task node is inconsistent with the currently displayed interface.

[0136] In some embodiments, situations where the current display interface does not meet the target interface conditions include situations where the current display interface is inconsistent with the functional interface required to perform the editing operation. For example, if the player is in a 3D scene arrangement interface, but the current step requires variable configuration in the logic code interface, the system will pop up an auxiliary demonstration panel in the edge area of ​​the graphical user interface. This panel occupies about a quarter of the screen space and continuously displays the operation trajectory in the logic code interface.

[0137] In other embodiments, situations where the current displayed interface does not meet the target interface conditions include the current displayed interface lacking a specific menu level upon which the editing operation depends. For example, if the player has not entered the component attribute configuration page, but the first operation guide requires demonstrating the path to adjust color parameters, the system will invoke an auxiliary demonstration panel on the side of the screen, simultaneously presenting the component selection and parameter adjustment process within the attribute configuration page.

[0138] The embodiments of this application are not limited to the conditions for activating the auxiliary demonstration panel. The above-mentioned situations can be judged independently or triggered in combination. For example, the system can simultaneously activate the panel when the interface does not match and a specific menu level is missing, and directly position the panel to the missing menu level.

[0139] Furthermore, to avoid frequent control of the auxiliary demonstration panel, when inconsistencies are detected between the current and target interfaces, it's possible to further detect whether the current and target interfaces are triggered by a jump or have significant obstruction. Since jumps or significant obstruction between the target and current interfaces can interfere with the player's normal editing operations when the system automatically executes editing functions, an auxiliary demonstration panel is popped up to display the necessary editing operations without interfering with the player's normal editing. For example, if the current interface displays as follows... Figure 6 The game editing scene and the component panel on the right are shown, while the target interface is as follows: Figure 5 The property panel shown does not involve large-area obstruction, therefore the auxiliary demonstration panel will not be displayed. If the target interface is... Figure 7 The graphical programming interface shown has been completely replaced. Figure 6 The current interface shown prevents the user from continuing. Figure 6 When editing the current interface shown, a pop-up window will appear, forming... Figure 6 The state shown is that the auxiliary demonstration panel is displayed in the current interface, and the editing process of the target interface is displayed through the auxiliary demonstration panel.

[0140] The target interface is the interface to which the editing operation corresponding to the first operation guide is performed. In other words, the functional interface in which the editing operation indicated by the first operation guide is completed is the target interface. The target interface can be a child configuration interface that has a parent-child cascade relationship with the current editing level, an attribute editing interface that is automatically mapped according to the component type, or the default interface for the current step in the editing process under the standard workflow.

[0141] In some embodiments, the target interface is the code editing canvas interface that the system points to when performing component logic orchestration operations. For example, when the first operation guide requires logically connecting the event triggering component and the action execution component, the target interface is a code editing canvas containing the component node connection area, and the auxiliary demonstration panel displays the node dragging and connection operations in the canvas accordingly.

[0142] In other embodiments, the target interface is the 3D scene coordinate editing interface that the system points to when performing spatial layout adjustment operations. For example, when the first operation guide requires placing a virtual prop model from the resource library to a specific coordinate in the scene, the target interface is a scene editing view containing 3D coordinate axes and mesh references, and the auxiliary demonstration panel displays the model selection and displacement path within this view accordingly.

[0143] The embodiments of this application are not limited to the specific form of the target interface. For different steps in the same editing process, the target interface can correspond to the code editing canvas interface and the 3D scene coordinate editing interface respectively. When generating the first operation guide, the system dynamically determines the direction of the target interface according to the type of the current editing operation.

[0144] In step S520, the editing operations being performed or about to be performed in the target interface are displayed in the auxiliary demonstration panel. Specifically, after the auxiliary demonstration panel is activated, the operations that are happening or about to be performed in real time in the target interface are visualized and mapped to the auxiliary demonstration panel, so that the player can synchronously obtain the editing operation content in the target interface without switching the current main interface.

[0145] Displaying ongoing or pending editing operations on the target interface within the auxiliary demonstration panel can be achieved in several ways: rendering the complete operation process of the target interface in real-time as thumbnails within the auxiliary demonstration panel; sequentially displaying the pending editing sub-operations as step-by-step cards within the auxiliary demonstration panel; or highlighting the functional areas of the target interface directly related to the current editing needs within the auxiliary demonstration panel using a semi-transparent overlay.

[0146] In some embodiments, the auxiliary demonstration panel displays the component dragging and parameter configuration process currently in progress within the target interface in the form of a real-time screen recording stream. For example, when the system automatically demonstrates establishing a connection between the input node and the processing node in the code editing canvas of the target interface, the auxiliary demonstration panel synchronously plays a real-time stream of this connection process, allowing the player to observe the complete node interaction trajectory on the main interface.

[0147] In other embodiments, the auxiliary demonstration panel sequentially displays the sequence of editing operations to be performed in a step-by-step static diagram format. For example, when the first operation guide includes a series of steps to select a target component from the resource library and drag it to a specific location in the scene, the auxiliary demonstration panel sequentially displays a component selection highlight box and a displacement path arrow to preview the complete operation chain to be executed in a static diagram format.

[0148] This application's embodiments are not limited to the display format within the auxiliary demonstration panel; real-time screen recordings and step-by-step static diagrams can be presented simultaneously. For example, step-by-step static diagrams can be overlaid below the screen recording, allowing players to observe dynamic operation details while quickly grasping the overall step structure of the operation through static diagrams.

[0149] The following will describe an exemplary application of the embodiments of this application in a real-world application scenario.

[0150] When players edit the game scene through the graphical user interface, the current displayed interface is the 3D terrain layout interface. Players browse the scene terrain and place terrain components in this interface. Based on the editing requirements, the system determines that the next step needs to establish a connection between the terrain trigger and the sound effect player in the component logic configuration interface, and generates the first operation guide accordingly. Since the target interface for the editing operation corresponding to this first operation guide is the component logic configuration interface, while the player's current interface is the 3D terrain layout interface, the target interface conditions are not met. Therefore, the system controls the display of an auxiliary demonstration panel on the side edge of the currently displayed interface.

[0151] After the auxiliary demonstration panel is displayed, players can continue their existing terrain editing operations in the 3D terrain layout interface. The system dynamically displays the node connection trajectory being executed in the component logic configuration interface, as well as the attribute parameter configuration steps to be executed, within the auxiliary demonstration panel. While maintaining 3D terrain layout operations, players can simultaneously grasp the complete editing context within the target interface through the auxiliary demonstration panel, previewing the operation sequence required for logic configuration without immediately switching interfaces.

[0152] In some embodiments, the editor can respond to a trigger operation on the auxiliary presentation panel by controlling the saving of the current display interface's editing state and controlling the jump from the current display interface to the target interface. It should be noted that the saving and jumping operations are both performed under the same trigger operation, and together they constitute a complete cross-interface editing process.

[0153] That is, in Figure 6 Based on the illustrated embodiment, the above-mentioned saving of the editing state of the current display interface can be achieved in at least one of the following ways, but not limited to: taking snapshots of the positional attributes and hierarchical relationships of each component in the current canvas; writing unsubmitted editing data and logical configurations in the current display interface into a temporary queue; and saving the overall interface view state and tool panel expansion status. For example, when a player has placed multiple vegetation components and adjusted their scaling and positional attributes in the 3D terrain interface of the game editing scene, triggering the auxiliary demonstration panel automatically locks the work progress and generates a corresponding editing snapshot for later restoration.

[0154] The aforementioned transition from the current display interface to the target interface can be achieved by combining the target interface's identification information: after saving the current editing state, the editor loads the corresponding editing function modules and workspace of the target interface, maintaining a complete mapping of editing data during the switching process. For example, when a player triggers the auxiliary demonstration panel in the 3D scene editing interface, the system saves the scene editing progress and immediately switches to the logic code editing interface, allowing the player to directly enter the target environment required to perform the next editing operation and continue completing the conditional trigger configuration and logic connections.

[0155] It should be noted that the saving of the editing state and the target interface jump in this embodiment can be implemented in combination. That is, while the system saves the component parameters and layout information of the current interface in a snapshot, it writes the unsubmitted editing data into a temporary queue, and then switches to the target interface according to the preset editing requirement path and locates the local functional area where the component to be edited is located.

[0156] In summary, the method provided in this embodiment allows players to directly access the workspace required for editing operations with a single click from any non-target interface using the auxiliary demonstration panel, avoiding the need to manually search for function entry points. At the same time, by automatically saving the editing state, it effectively prevents the loss of configuration data and the breakage of the editing context during interface switching, ensuring the continuity and integrity of the cross-interface editing process.

[0157] In some embodiments, while the terminal displays operation instructions corresponding to the editing requirements or automatically executes the editing operation corresponding to the first operation instruction, the interactive object in the game editing scene interface remains in a triggerable state; in response to a touch operation on the interactive object, the terminal controls the execution of the editing instruction corresponding to the touch operation while maintaining the display of operation instructions or the automatic execution of the editing operation.

[0158] Specifically, when displaying operation instructions or automatically performing editing operations, the terminal does not render the interactive objects inoperable, but rather keeps the interface continuously triggerable. This non-blocking control method allows users to observe the guidance while performing editing operations. Optionally, the terminal can also only block the touch response of the area involved in the current operation and release the rest of the area, or dynamically adjust the trigger priority of the interactive objects based on spatial distance, or establish event distribution channels for the demonstration layer and the object layer respectively, to support richer concurrent interaction scenarios. Here, the demonstration layer refers to the layer used to render and display operation instructions or perform editing operations corresponding to the operation instructions, such as the auxiliary demonstration panel mentioned in the aforementioned implementation scheme.

[0159] In one alternative implementation, when the terminal displays operation instructions in a local area of ​​the graphical user interface, the function entries, editing tools, and scene objects within the game editing scene interface do not enter a modal lock state and can still be touched by the user. For example, when the terminal is dynamically demonstrating how to drag logic components from the menu into the event stream, the player can simultaneously click on the terrain directory in the scene object tree to expand the subdirectories. This click request is responded to normally and will not terminate or pause the currently playing trajectory demonstration.

[0160] In another optional implementation, when the terminal automatically executes the editing operation sequence according to preset requirements, the main canvas and surrounding controls of the scene editor do not generate a mask layer to intercept touch events, and all virtual objects and control nodes remain selectable and editable. For example, when the terminal automatically places a set of default markers in the background, the player can still touch to select an existing decorative model in the scene and invoke the delete command. The execution of the delete command and the background automatic placement process are concurrent and do not block each other.

[0161] It should be noted that the two optional implementation methods mentioned above can be used individually or in combination. For example, the terminal can keep the object triggerable only when displaying operation instructions, or it can keep the object triggerable during automatic execution, or it can use differentiated triggering strategies for different types of interactive objects when both occur simultaneously. This application does not impose any restrictions on this.

[0162] The interactive objects in the game editing scene interface include virtual model objects such as scene components located in the game editing scene, and may also include interactive controls in the interface, such as function panels for different functions, navigation bars, etc.

[0163] In one specific application, a user is building a racetrack map for a racing game. The terminal automatically places a leaderboard component in the finish line area based on editing needs, and simultaneously displays the placement process in a small floating window in the upper left corner of the interface. At this point, the user notices that the lighting in the starting area is too dim, so they directly select a parallel light source object in the scene and increase its brightness. While maintaining the automatic leaderboard placement, the terminal successfully responds to the user's instruction to modify the light source parameters. The results of both editing operations are simultaneously written to the same scene data, and the user experiences no forced waiting or interface locking throughout the entire process.

[0164] When a user touches an interactive object while the terminal is displaying operation instructions or automatically performing editing operations, the terminal will maintain the continuity and visibility of the current instruction display or automatic execution process, parse the touch operation to generate corresponding editing instructions and execute them, thereby realizing concurrent processing of user-initiated editing and system-guided behavior.

[0165] Optionally, the terminal can achieve the above concurrent processing by allocating background time slices for automatic execution and placing user touch in the foreground response queue, or by establishing checkpoints during automatic execution to support the rapid insertion and resumption of user commands, or by encapsulating user touch events as high-priority tasks to suspend the current instruction sequence. Touch operations can be click operations, swipe operations, long press operations, etc., and this application does not limit the specific form of touch operations.

[0166] Taking click operations as an example, when a user clicks on an interactive object in the scene while the operation guide is continuously displayed, the terminal recognizes the editing command corresponding to the click and executes it immediately, while maintaining the display of the guide or the automatic execution in the background without interruption. This allows the player's independent editing and the system's assisted process to proceed synchronously within the same interface cycle.

[0167] In one alternative implementation, while the terminal is demonstrating the interaction trajectory of components within the same graphical user interface, the user's editing commands to the main interface scene nodes and the currently playing demonstration animation are encapsulated as independent processing tasks, which are then scheduled and executed in parallel by different threads or event loops. For example, when a player is watching a demonstration of how to associate a timer component with the scoring system, and simultaneously clicks on a background music object and turns down its volume, the terminal, while maintaining the continuity of the demonstration, schedules and executes the volume adjustment editing command, and the results of the two operations are recorded in their respective modules.

[0168] In another alternative implementation, during the background automatic execution of the editing operation sequence, the terminal identifies real-time editing requests triggered by the player through the interface as high-priority events, inserts them into the current processing loop for priority response, and seamlessly resumes the automatic execution sequence from the previously saved interruption point after the player's command is completed. For example, while the terminal is automatically adding a batch of rule triggers to the scene, if the player touches to select an existing trigger and modifies its parameters, the terminal immediately resumes the remaining batch addition tasks after executing the modification, without reloading the scene or resetting the operation state throughout the process.

[0169] It should be noted that the above-mentioned concurrent processing methods can be used individually or in combination depending on the type of operation. For example, simple click commands can be processed using a parallel task mechanism, while complex long-press and drag commands can be processed using an interrupt recovery mechanism. This application does not impose any restrictions on this.

[0170] In one exemplary application of this embodiment, the user enters the scene editing mode of a racing game through a graphical user interface. After inputting editing requirements, the terminal demonstrates, in the center of the interface, how to drag a checkpoint component from the top menu to the target position on the track curve using a semi-transparent arrow sequence. During this demonstration, the component property panel on the right side of the interface, the terrain toolbar at the bottom, and the system menu in the upper left corner remain accessible. The user observes that the width of the track starting point needs adjustment, so they directly select the starting arch object and increase its scaling factor. While maintaining the uninterrupted arrow demonstration, the terminal simultaneously executes the scaling adjustment command and displays the checkpoint placement and arch scaling results in real time on the same scene canvas. The user can complete concurrent self-editing operations without pausing or exiting the guided process.

[0171] In summary, the method provided in this embodiment ensures that the interactive object remains continuously triggerable and responsive to user touch during system-displayed operation guidance or automatic editing processes. This avoids the forced preemption of interface events by traditional strong modal masking, improving the smoothness and naturalness of the interaction. Simultaneously, users can freely execute additional editing commands during the guidance process, expanding the interactive space and creative richness of game editing. This solves the problem of mutual preemption and process interruption when instructional demonstrations and manual editing coexist in the same graphical user interface, achieving a fusion of system assistance and player autonomy.

[0172] In one possible implementation, the above-mentioned response to a touch operation on an interactive object, while maintaining the state of displaying an operation guide corresponding to the editing needs or automatically executing the editing operation corresponding to the first operation guide, controlling the execution of the editing instruction corresponding to the touch operation may include: Step S610: In response to a touch operation on the interactive object, if the editing instruction corresponding to the touch operation and the editing requirement meet a preset degree of irrelevance, while maintaining the display of the operation guide corresponding to the editing requirement or automatically executing the editing operation corresponding to the first operation guide, control the execution of the editing instruction corresponding to the touch operation.

[0173] The preset degree of irrelevance is used to measure the correlation between the user's current touch intent and the predetermined editing goal. The lower the correlation, the more likely the touch operation can be determined as a parallel editing behavior independent of the current teaching flow, and the system can process it concurrently with the editing guidance flow without blocking each other. The determination methods include, but are not limited to: comparing the semantic features of the touch command with the semantic features of the editing requirement; comparing the component category affected by the touch command with the component category pointed to by the editing requirement; and analyzing the interface level corresponding to the touch command and the interface level where the editing requirement is located.

[0174] If the correlation is high, it is assumed that the user's current touch operation may affect the predetermined editing goal. In this case, the user will be prompted to perform the operation again through a secondary confirmation. If the user continues to operate, the current auxiliary editing function will be interrupted, that is, the current and subsequent operation prompts will be interrupted, and the automatic execution of the editing operation to achieve the editing requirements will be stopped.

[0175] In one embodiment, the preset degree of irrelevance can be determined by judging whether there is any overlap in the functional dimensions of the two. For example, a user touches an interactive control to adjust the ambient lighting parameters in a 3D scene, while the current editing requirement is to build a conditional trigger in the logic editor. The two act on the visual rendering layer and the logic event layer respectively, and their functional dimensions have no overlap. After the system determines that the lighting adjustment instruction meets the preset degree of irrelevance, it continues to display the first operation guide in the game editing scene interface and executes the lighting parameter adjustment.

[0176] In another embodiment, the preset degree of irrelevance can be determined based on whether the interface layers where the two actions are performed are separate. For example, the current editing requirement points to the logical condition block configuration in the code editing interface, while the user's touch operation occurs on the preset vegetation density slider control in the 3D scene interface. The two belong to the script logic layer and the scene object layer, respectively. The system recognizes that the vegetation adjustment instruction is at a different interface layer than the current code editing requirement, determines that the preset degree of irrelevance is met, and responds to the vegetation density adjustment operation while maintaining the normal display of the first operation guide.

[0177] It should be noted that the two determination methods mentioned above can be used in combination. The system can determine based solely on the functional dimension, or it can combine the functional dimension and the interface hierarchy for a comprehensive determination to more accurately identify user operations that can be executed in parallel.

[0178] While maintaining the display of operation guidance corresponding to the editing needs or automatically executing the editing operation corresponding to the first operation guidance, the system's response to the touch command maintains two parallel channels at the underlying level: the teaching guidance channel maintains the guidance rendering output, and the user editing channel receives and executes the editing operation corresponding to the touch command in real time. Specific implementation methods include, but are not limited to: continuously rendering dynamic guidance and synchronously providing feedback on the touch operation results in the main canvas area; maintaining underlying touch event listening during the automated execution of guidance steps; and processing the writing of editing data in a background thread while maintaining the refresh of text prompt information.

[0179] In one embodiment, while the system continuously displays the first operation guide in the game editing scene interface, it simultaneously receives and responds to the user's touch editing request on the main editing canvas, ensuring that the guide display and the user's editing operation occur simultaneously without obstructing each other. For example, if the system is displaying a guide to direct the user to drag and drop a target component, and the user clicks and rotates the orientation of the scene model in the main editing canvas, the system will immediately execute the rotation command and update the model display while maintaining the guide display.

[0180] In another embodiment, while automatically executing the editing operation corresponding to the first operation guide, the system retains the underlying touch event listening channel, allowing the user's triggering operations on unrelated interactive controls to be responded to in real time. For example, if the system is automatically executing the component laying step and the user clicks on a material option in the property panel that is unrelated to the current editing needs, after the system recognizes that the operation meets the preset degree of irrelevance, it opens the material editing panel for the user to adjust while maintaining automatic execution.

[0181] In one specific application, the player triggers an editing tutorial in the 3D scene editing interface. The system displays initial instructions in the game's editing scene interface based on the editing requirements. During the tutorial, the player touches the terrain height adjustment control. The system determines that the terrain editing command and the current building requirements meet a preset level of irrelevance in terms of function and interface hierarchy. While maintaining the initial instructions continuously displayed, the system synchronously adjusts the terrain height. The player can complete the editing independently without interrupting the tutorial.

[0182] This application embodiment enables the teaching guidance flow and the user's self-editing flow to be executed in parallel on the same interface by pre-determining the degree of irrelevance. During the guidance period, it identifies and responds to low-association touch commands, avoiding the obstruction of user's free editing by forced modal masking. At the same time, it reduces unnecessary interface state switching and process waiting overhead, and improves the response efficiency and flexibility of users performing concurrent editing operations in the guidance scenario.

[0183] In some embodiments, the first operation guidance may include at least one of text prompts, voice prompts, and dynamic image demonstrations. Depending on different editing needs, the system may employ a single information format or combine multiple formats to allow users to obtain operation information through the most suitable sensory channel.

[0184] Text prompts are displayed in character form in the graphical user interface. Common methods include: displaying a floating label next to the component to be operated, such as "Drag to the center of the scene to generate basic terrain" next to the component icon when dragging a terrain component; displaying step-by-step instructions in the interface information bar, such as "Step 1: Select the target component; Step 2: Drag to the target area; Step 3: Configure properties", and automatically updating the remaining prompts after the user completes each step.

[0185] Voice prompts announce the operation content via audio. One method is to simultaneously announce the complete operation command while the first operation guide is displayed, such as "Please select the basic terrain component from the left-hand category menu"; another method is to automatically activate a short reminder announcement when the user's gaze leaves the screen for more than a preset time, such as "Current step is pending completion, please select the basic terrain component".

[0186] Dynamic image demonstrations showcase the component interaction process through animation or highlighted paths. For example, the system can pop up a picture-in-picture window in the lower right corner of the interface, looping the full path animation of selecting a decorative component from the component library and dragging it to the target area; it can also automatically skip completed segments and continue playing the demonstration of the remaining steps based on the user's progress.

[0187] In practical applications, the above-mentioned information formats can work together. After a user inputs the editing requirement of "adding a spawn point in the center of the scene and configuring basic attributes," the system displays the text prompt "Step 1: Select the default spawn point from the spawn point component library" in the top information bar, while simultaneously playing a voice prompt and looping a highlighted border animation next to the component library icon. After the user completes the corresponding operation according to the multimodal guidance, the system detects that the operation meets the preset conditions and continues to generate a second operation guide.

[0188] Through the above methods, the first operation guide can convey editing operation-related content to users through one or more combinations of text, voice, and dynamic images, satisfying the cognitive habits and perceptual channel preferences of different user groups and improving the friendliness and inclusiveness of the interactive experience; at the same time, by redundantly conveying key operation information through multiple channels such as hearing and vision, the probability of operation stagnation caused by the obstruction of a single information channel or the distraction of user attention is reduced, thus optimizing the efficiency of human-computer interaction.

[0189] This disclosure provides an electronic device including a processor and a memory, wherein the processor executes instructions in the memory to perform steps in the component editing method described in any of the preceding claims.

[0190] The apparatus provided in this disclosure has the following technical effects: By acquiring editing requirements for game editing scenarios and generating corresponding operation guides, the system can flexibly switch between manual and automatic execution modes based on user response status. This allows users with weaker learning abilities to perceive component editing logic during unobstructed browsing, significantly lowering the operational threshold and improving the naturalness and smoothness of human-computer interaction. Simultaneously, by continuously detecting user touch responses under the first operation guide and automatically generating a second operation guide when conditions are met, the system achieves automated connection and multi-step continuous demonstration of the editing tutorial process. This effectively expands the teachable complexity of component editing and the dimensions of gameplay construction, thereby enhancing the richness of game content. Furthermore, by automatically executing corresponding editing operations when no user operation is detected, instead of entering an invalid waiting state, the system reduces processing idle time caused by waiting for user responses, optimizing the task scheduling efficiency and overall performance of the graphical user interface.

[0191] The specific details of each part of the above-mentioned device have been described in detail in the method section of the implementation plan. For any undisclosed details, please refer to the implementation plan of the method section, and therefore will not be repeated here.

[0192] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to exemplary embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0193] Exemplary embodiments of this disclosure also provide a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the methods described above.

[0194] Implementing the above method steps using a computer program has the following technical effects: By acquiring editing requirements for game editing scenarios and generating corresponding operation guides, the system can flexibly switch between manual and automatic execution modes based on user response status. This allows users with weaker learning abilities to perceive component editing logic during unobstructed browsing, significantly lowering the operational threshold and improving the naturalness and smoothness of human-computer interaction. Simultaneously, by continuously detecting user touch responses under the first operation guide and automatically generating a second operation guide when conditions are met, the system achieves automated connection and multi-step continuous demonstration of the editing tutorial process. This effectively expands the teachable complexity of component editing and the dimensions of gameplay construction, thereby enhancing the richness of game content. Furthermore, by automatically executing corresponding editing operations when no user operation is detected, instead of entering an invalid waiting state, the system reduces processing idle time caused by waiting for user responses, optimizing the task scheduling efficiency and overall performance of the graphical user interface.

[0195] In one implementation, the computer program product can be a tangible product, such as a computer-readable storage medium storing a computer program. The readable storage medium can be based on electrical, magnetic, optical, electromagnetic, infrared, or other signals, and includes, but is not limited to: random access memory (RAM), read-only memory (ROM), magnetic tape, floppy disk, flash memory, hard disk drive (HDD), solid-state drive (SSD), etc. For example, the computer program product can be a non-volatile storage medium storing a computer program, such as read-only memory, NAND flash memory, etc.

[0196] In one implementation, the computer program product can be an intangible product. For example, the computer program product can be a virtual digital product, such as an executable file or installation package containing a computer program.

[0197] Computer program code can be written in one or more programming languages. Examples of programming languages ​​include C, Java, and C++. Program code can execute entirely on the user's computing device, partially on the user's computing device, or as a standalone software package. It can also execute partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, such as a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via an internet connection provided by a mobile network operator).

[0198] Computer programs can be carried or transmitted via signals such as electrical, magnetic, optical, electromagnetic, and infrared rays. Electronic devices can convert signals carrying computer programs into digital signals, thereby running the computer programs. When a computer program runs on an electronic device, its code is used to cause the electronic device to execute (more specifically, to be executed by the processor of the electronic device) the method steps of various embodiments of this disclosure.

[0199] Exemplary embodiments of this disclosure also provide an electronic device, which may be the first client 110, the second client 120, or the server 130 described above. The electronic device includes a processor and a memory. The memory stores executable instructions for the processor, such as computer programs. The processor executes these executable instructions to perform the method steps of various exemplary embodiments of this disclosure.

[0200] Implementing the above method steps using electronic devices has the following technical advantages: This disclosure provides a component editing method, apparatus, electronic device, and program product. By acquiring editing requirements for game editing scenarios and generating corresponding operation guides, it can flexibly switch between manual and automatic execution modes based on user response status. This allows users with weaker learning abilities to perceive component editing logic during unobstructed browsing, significantly reducing the operational threshold and improving the naturalness and fluency of human-computer interaction. Simultaneously, by continuously detecting user touch responses under the first operation guide and automatically generating a second operation guide when conditions are met, it achieves automated connection and multi-step continuous demonstration of the editing tutorial process, effectively expanding the teachable component editing complexity and gameplay construction dimensions, thereby enhancing the richness of game content. Furthermore, by automatically executing the corresponding editing operation without detecting user operation instead of entering an invalid waiting state, it reduces the processing idle time caused by waiting for user response, optimizing the task scheduling efficiency and overall operating performance of the graphical user interface.

[0201] The following is for reference. Figure 8The electronic device is illustrated by way of a general-purpose computing device. It should be understood that... Figure 8 The electronic device 1100 shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0202] like Figure 8 As shown, the electronic device 1100 may include: a processor 1110, a memory 1120, a bus 1130, an I / O (input / output) interface 1140, and a network adapter 1150.

[0203] Memory 1120 may include volatile memory, such as RAM 1121 and cache unit 1122, and may also include non-volatile memory, such as ROM 1123. Memory 1120 may also include one or more program modules 1124, such program modules 1124 including, but not limited to: operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. For example, program module 1124 may include the modules in the above-described apparatus.

[0204] The processor 1110 may include one or more processing units, such as an AP (Application Processor), a modem processor, a GPU (Graphics Processing Unit), an ISP (Image Signal Processor), a controller, an encoder, a decoder, a DSP (Digital Signal Processor), a baseband processor, and / or an NPU (Neural-Network Processing Unit).

[0205] The processor 1110 can be used to execute executable instructions stored in the memory 1120 to perform method steps of various embodiments of the present disclosure.

[0206] Bus 1130 is used to connect different components of electronic device 1100 and may include a data bus, an address bus and a control bus.

[0207] Electronic device 1100 can communicate with one or more external devices 1200 (such as keyboard, mouse, external controller, etc.) through I / O interface 1140.

[0208] Electronic device 1100 can communicate with one or more networks via network adapter 1150. For example, network adapter 1150 can provide mobile communication solutions such as 3G / 4G / 5G, or wireless communication solutions such as wireless LAN, Bluetooth, and near-field communication. Network adapter 1150 can communicate with other modules of electronic device 1100 via bus 1130.

[0209] In one embodiment, the electronic device 1100 further includes a display for displaying a graphical user interface.

[0210] although Figure 8 As not shown in the diagram, other hardware and / or software modules may also be configured in the electronic device 1100, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (Redundant Arrays of Independent Disks) systems, tape drives, and data backup storage systems.

[0211] As can be seen from the above, the technical solutions disclosed herein can be implemented as methods, apparatus, systems, computer program products, storage media, electronic devices, etc. Those skilled in the art will understand that various aspects of this disclosure can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or an implementation combining hardware and software aspects, which may be referred to as "circuit," "module," or "system," respectively.

[0212] It should be understood that this disclosure is not limited to the specific methods, steps, or structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. Those skilled in the art will readily conceive of other embodiments based on the specific implementations provided in this disclosure. Therefore, the specific implementations provided in this disclosure are merely exemplary, and the scope and spirit of this disclosure are indicated by the claims, and should cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary technical means in the art not disclosed in this disclosure.

Claims

1. An assembly editing method characterized by, The method of displaying a game editing scene interface through a graphical user interface, wherein the displayed content of the game editing scene interface includes a game editing scene and interactive controls, includes: Obtain the editing requirements for the game editing scenario; A first operation guide is generated and displayed on the game editing scene interface according to the editing requirements; Detect whether a touch operation corresponding to the first operation guide is received through the graphical user interface within a first time threshold. If the touch operation is detected within the first time threshold, the editing operation corresponding to the first operation instruction is executed. If the touch operation is not detected within the first time threshold, the system automatically executes the editing operation corresponding to the first operation guide. When the editing operation corresponding to the first operation guide meets the preset conditions, a second operation guide is generated.

2. The method of claim 1, wherein, The step of generating and displaying the first operation guide in the game editing scene interface includes: Determine the component interaction trajectory data required to complete the editing requirements based on the editing requirements; Generate the first operation guide corresponding to the interaction trajectory data of the component.

3. The method of claim 2, wherein, The component interaction trajectory data includes at least one of the following: component category affiliation information, spatial displacement information, and logic editing information; wherein, the category affiliation information includes: the category menu information to which the component belongs; the spatial displacement information includes: the component's movement position information in the game editing scene; and the logic editing information includes code editing information that controls the execution of game logic.

4. The method of claim 1, wherein, The method further includes: During the display of operation instructions corresponding to the editing requirements or the automatic execution of the editing operation corresponding to the first operation instructions, the interactive objects in the game editing scene interface are kept in a triggerable state; In response to a touch operation on the interactive object, while maintaining the display of an operation guide corresponding to the editing requirement or automatically executing the editing operation corresponding to the first operation guide, the system controls the execution of the editing instruction corresponding to the touch operation.

5. The method of claim 4, wherein, The step of controlling the execution of the editing instruction corresponding to the touch operation in response to a touch operation on the interactive object, while maintaining the display of the operation guide corresponding to the editing requirement or automatically executing the editing operation corresponding to the first operation guide, includes: In response to a touch operation on the interactive object, if the editing instruction corresponding to the touch operation and the editing requirement meet a preset degree of irrelevance, and the editing requirement is maintained in the state of displaying the operation guide corresponding to the editing requirement or automatically executing the editing operation corresponding to the first operation guide, the editing instruction corresponding to the touch operation is controlled to be executed.

6. The method of claim 1, wherein, The method further includes: Control the dynamic display of the component interaction trajectory corresponding to the first operation guide in the graphical user interface.

7. The method of claim 6, wherein, The step of controlling the dynamic display of the component interaction trajectory corresponding to the first operation guide in the graphical user interface includes: The system controls the display of an auxiliary demonstration panel in the graphical user interface, which displays the component interaction trajectory corresponding to the first operation guide.

8. The method of claim 7, wherein, The steps of controlling the display of the auxiliary demonstration panel in the graphical user interface include: In response to the current display interface not meeting the conditions of the target interface, the auxiliary demonstration panel is controlled to be displayed, wherein the target interface is the interface targeted by the editing operation corresponding to the first operation guide; The control panel displays the editing operations that are being performed or are about to be performed on the target interface.

9. The method of claim 1, wherein, The steps for generating the second operation guide include: Obtain scene status information after executing the editing operation corresponding to the first operation guide; The second operation guide is generated based on the scene status information and the editing requirements.

10. A computer program product storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method according to any one of claims 1 to 9.