A method, apparatus, and storage medium for controlling the operation of virtual attributes.

Abstract

This application discloses a method, apparatus, and storage medium for controlling the operation of virtual attributes. The method includes: acquiring a first input operation and detecting whether the first input operation satisfies a preset virtual attribute operation conversion condition; if the virtual attribute operation conversion condition is satisfied, determining a target virtual attribute update ratio corresponding to the first input operation; the target virtual attribute update ratio defines the update ratio of the user's virtual attribute in response to the input operation; acquiring a second input operation and updating the user's virtual attribute according to the second input operation and the target virtual attribute update ratio. Thus, by introducing virtual attribute operation conversion conditions and a corresponding virtual attribute update ratio mechanism based on the user's input operation, dynamic adaptation between the user's operation intention and attribute update behavior is achieved.

Description

Technical Field

[0001] This application relates to the field of game interaction operation technology, and in particular to a method, device and storage medium for operating and controlling virtual attributes. Background Technology

[0002] With the popularization of online games and interactive entertainment, virtual attributes (such as wealth, resources, and experience points in games) have become important indicators for evaluating player growth and decision-making. Traditional attribute enhancement operation modes often rely on simple clicks or repeated clicks of interface buttons, or on performing operations by inputting fixed values.

[0003] Players can increase or decrease virtual attribute values ​​step by step by clicking buttons. This can meet basic needs at low levels or in the early stages, but when attribute accumulation is rapid and upgrade requirements increase sharply, players often need to click continuously to manipulate attribute values. This is not only tedious and time-consuming, but also prone to failure due to mismatched operation speed. In addition, some games allow players to directly input fixed values ​​in the interface to manipulate virtual attributes. While this allows for precise control of values, the operation is cumbersome, affecting the smoothness of player operation. Furthermore, it requires switching to numerical input mode during operation, and it is not easy to see the value changes immediately. Summary of the Invention

[0004] This application provides a method, device, and storage medium for controlling the operation of virtual attributes, which enables players to quickly, accurately, and in real-time operate virtual attributes with high accumulated values ​​in the game, while maintaining the continuity of game operation.

[0005] In a first aspect, embodiments of this application provide a method for controlling the operation of a virtual attribute, comprising: acquiring a first input operation and detecting whether the first input operation satisfies a preset virtual attribute operation conversion condition, wherein the first input operation includes control operation information, the control operation information including at least one type of control event such as touch screen swiping operation, touch screen pressing operation, mouse long press operation, or mouse wheel operation; if the virtual attribute operation conversion condition is detected to be satisfied, determining a target virtual attribute update ratio corresponding to the first input operation; the target virtual attribute update ratio defining the update ratio of the user virtual attribute in response to the input operation; acquiring a second input operation and updating the user virtual attribute according to the second input operation and the target virtual attribute update ratio.

[0006] Secondly, embodiments of this application provide an operation control device for virtual attributes, comprising: a conversion detection unit, configured to acquire a first input operation and detect whether the first input operation satisfies a preset virtual attribute operation conversion condition; a multiplier determination unit, configured to determine a target virtual attribute update multiplier corresponding to the first input operation when the virtual attribute operation conversion condition is detected to be satisfied; the target virtual attribute update multiplier defines the update multiplier of a user virtual attribute in response to an input operation; and an attribute update unit, configured to acquire a second input operation and update the user virtual attribute according to the second input operation and the target virtual attribute update multiplier.

[0007] Thirdly, an electronic device is provided, comprising: at least one processor, and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the steps of the virtual attribute operation control method of any embodiment of the present application.

[0008] Fourthly, embodiments of this application provide a storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the operation control method for virtual attributes in any embodiment of this application.

[0009] The virtual attribute operation control method and system provided in this application can produce at least the following technical effects:

[0010] By introducing virtual attribute operation conversion conditions and corresponding virtual attribute update multiplier mechanisms based on user input operations, dynamic adaptation between user operation intentions and attribute update behaviors is achieved. This allows for the automatic identification of the user's current operational needs based on their initial operation, determining an appropriate attribute response multiplier accordingly, and updating attributes at this multiplier in subsequent operations. This ensures that attribute changes possess both responsiveness and operational continuity and smoothness. Through this mechanism, by establishing a dynamic response relationship between input behavior and attribute updates, the feedback mechanism and control logic in the virtual attribute operation process are optimized. This not only effectively reduces repetitive operations and improves the efficiency of virtual attribute updates but also avoids the lack of continuity caused by interface switching or operational fragmentation in traditional input methods. Furthermore, considering that limitations such as long presses and scroll wheel swipes may make it difficult for users to accurately control the scale of attribute value multiplier changes, the methods and devices provided in this application also set a time buffer during operation to avoid user operation errors, thereby improving the control accuracy of multiplier increases and the user experience. Attached Figure Description

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

[0012] Figure 1 A flowchart illustrating an example of an operation control method for a virtual attribute according to an embodiment of this application is shown;

[0013] Figure 2 A flowchart illustrating an example of constructing an event multiplier library according to an embodiment of this application is shown.

[0014] Figure 3 A flowchart illustrating an example of constructing or updating an initialization event multiplier relationship according to an embodiment of this application is shown.

[0015] Figure 4 A structural block diagram of an example of an operation control device for a virtual attribute according to an embodiment of this application is shown;

[0016] Figure 5 This is a schematic diagram of the structure of an embodiment of the electronic device of this application. Detailed Implementation

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

[0018] The technical solutions in this application, including the collection, storage, use, processing, transmission, provision, and disclosure of users' personal information, comply with relevant laws and regulations and do not violate public order and good morals.

[0019] Figure 1 A flowchart illustrating an example of an operation control method for a virtual attribute according to an embodiment of this application is shown.

[0020] Regarding the execution subject of the method in the embodiments of this application, it can be any controller or processor with computing or processing capabilities. By detecting the initial input to trigger the virtual attribute operation conversion, determining the target update ratio, and then performing attribute updates according to subsequent inputs, dynamic adaptive control of virtual attribute updates is realized, which improves response speed, operation accuracy and real-time feedback effect.

[0021] In some examples, it can be integrated into electronic devices, terminals, or servers through software, hardware, or a combination of both, and the types of terminals, electronic devices, or servers can be diverse, such as mobile phones, tablets, or desktop computers, etc.

[0022] When the method for handling virtual items in a game runs on a server, this method can be implemented and executed based on a cloud interaction system, which includes a server and client devices.

[0023] In an optional implementation, various cloud applications, such as cloud gaming, can run under the cloud interaction system. 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 and the game screen presentation are separate. The storage and execution of virtual items in the game are completed on the cloud gaming server. The client device is used for data reception, transmission, and game screen presentation. For example, the client device can be a display device with data transmission capabilities located close to the user, such as a mobile terminal, television, computer, or PDA; however, the information processing is performed by the cloud gaming server in the cloud. When playing the game, the player operates the client device to send operation commands to the cloud gaming server. The cloud gaming server runs the game according to the operation commands, encodes and compresses the game screen and other data, returns it to the client device via the network, and finally, the client device decodes and outputs the game screen.

[0024] like Figure 1 As shown, in step S110, a first input operation is obtained, and it is detected whether the first input operation meets the preset virtual attribute operation conversion conditions. The first input operation includes control operation information, which includes at least one type of control event such as touch screen sliding operation, touch screen pressing operation, mouse long press operation, or mouse wheel operation.

[0025] It should be noted that virtual attributes refer to numerical or hierarchical data items used in a virtual environment constructed by a computer system to represent aspects such as user status, growth progress, resource accumulation, ability changes, or interaction permissions. These data items are usually not directly mapped to physical assets in the real world, but they have clear logical functions and interactive value in the virtual system. Examples include virtual currency, reputation points, and skill points in various online games, simulation software, interactive application systems, and digital social platforms.

[0026] In some implementations, event listeners deployed in the user interface can capture user input operations in real time, such as mouse clicks, scroll wheel operations, touch screen operations, or gesture recognition. High-frequency sampling can also be used to record the timestamps, durations, and frequencies of user input to ensure the integrity of the input data.

[0027] It should be noted that the virtual attribute operation conversion conditions can be preset by the system or set according to user needs. They can be set based on the following multi-dimensional indicators, such as operation duration, mouse wheel rotation angle, operation range or movement trajectory. For example, a long press operation reaching a preset duration or multiple consecutive clicks can be regarded as a conversion trigger condition.

[0028] Specifically, the system uses a detection module to compare the collected input data with predefined conditions in real time. When the input operation parameters (such as duration, frequency, operation range, or movement trajectory) reach a preset threshold, the current operation is considered to meet the virtual attribute operation conversion conditions. Therefore, by dynamically judging the first input operation, the system effectively avoids the problem of adjusting virtual attributes with a fixed granularity for all operations. This allows the system to automatically switch attribute update modes based on the user's actual operation, improving the accuracy of input intent recognition and the intelligence of the system response.

[0029] In some examples of embodiments of this application, the control point coordinates and control operation information contained in the first input operation are parsed, and then the preset virtual attribute operation conversion conditions are checked based on the control point coordinates and control operation information. The control operation information includes at least one of the following types of control events: touch screen swipe operation, touch screen press operation, mouse long press operation, or mouse wheel operation.

[0030] Specifically, when the system receives the user's first input operation, it not only records the timing and type of the input, but also extracts the control point area (e.g., pressing directly on a preset area of ​​the touchscreen or the corresponding graphical user interface, or clicking on a preset area of ​​the interface or the corresponding graphical user interface) and detailed control operation information. Based on the control point coordinates, it determines whether the input is located within a specified virtual attribute operation area (e.g., above a resource bar, value display box, or operation button), and analyzes whether the preset "operation conversion conditions" are met in conjunction with the control event type. For example, if the user presses and holds for more than 1 second or scrolls the mouse more than 180° within a specific control area, it can be considered that the user wishes to switch the current virtual attribute control mode to "high-rate update" mode.

[0031] In step S120, if the virtual attribute operation conversion condition is detected to be met, the target virtual attribute update ratio corresponding to the first input operation is determined. The target virtual attribute update ratio defines the update ratio of the user virtual attribute in response to the input operation.

[0032] Here, the system sets a target virtual attribute update multiplier based on the specific conditions met by the first input operation (such as longer press time, more consecutive clicks, larger swipe gestures, etc.). This multiplier value can be a fixed level (such as ×1, ×10, ×100, etc.) or a continuously adjustable variable, dynamically adjusted according to the intensity of the user's operation, the behavioral context, or the current virtual attribute level. Thus, by introducing a multiplier adjustment mechanism, flexible control over the attribute update speed under different user operation intentions is achieved, significantly improving the response speed of virtual attribute control and the degree of user freedom, enhancing the personalization of interaction and the system's adaptability.

[0033] In some implementations, the system can also intelligently derive the corresponding virtual attribute update multiplier by combining the operation event type and the coordinate position of the control point. For example, if a user performs a touch screen swipe, press, or scroll the mouse wheel upwards in the "resource area," the system can set the multiplier to twice the current value for rapid resource accumulation; if a user long-presses the "level bar control" for a certain period of time, the multiplier can dynamically increase with the pressing time (e.g., doubling every 0.5 seconds, up to a set upper limit); if a user double-clicks the attribute display box, the system directly switches to a preset high multiplier level (e.g., ×100) for easy batch operations. Thus, the multiplier setting logic can be comprehensively calculated based on factors such as the control area, operation type, and operation duration, achieving intelligent multiplier setting and real-time feedback mechanisms. This ensures precise alignment between user input intent and virtual attribute control behavior, significantly improving the interactive intelligence, adaptability, and operational efficiency of the virtual attribute system.

[0034] In some possible embodiments, when the multiplier update dynamically corresponds to the user's operation, the method further includes: obtaining the real-time virtual attribute multiplier value under the first input operation state; when the virtual attribute multiplier value reaches a preset value, pausing the update of the virtual attribute multiplier value within a preset time interval, and generating user prompt information;

[0035] Here, during the initial input operation's multiplier update process, at least one pause point can be set to prevent user errors or misjudgments during the operation. Corresponding to the first input operation, at least one preset value can be set. This preset value can be a fixed number, such as 50% or 60% of the multiplier update range. For example, if the current multiplier is 10 and the maximum multiplier can be set to 100, when the preset value is 50%, the multiplier increases to 55. This value can also be dynamically set based on user habits, game plot, etc. When the virtual attribute multiplier value reaches the preset value, even if the user continues to long-press the touchscreen or scroll the wheel, the multiplier update will pause within the preset time interval to allow the user to determine if an operational error has occurred. This preset time interval can be set according to factors such as game operation smoothness and user experience, for example, 0.5 seconds, 1 second, 2 seconds, etc. Simultaneously, to further prompt the user, a user prompt message can be generated, indicating the current multiplier update value. If the user wants to continue updating the multiplier, there's no need to stop the operation; simply continue pressing and holding the touchscreen or scrolling the wheel. After a preset time interval, the multiplier value will continue to update based on the user's actions. User actions during the paused update period are counted in the total update multiplier by default. Alternatively, in practice, they can be counted from the moment updates resume, depending on the user's pre-configuration. In step S130, the second input operation is obtained, and the user's virtual attribute is updated based on the second input operation and the target virtual attribute update multiplier.

[0036] Here, after the multiplier is determined, the system focuses on collecting subsequent second input operations, which can take the form of a click, swipe, or other interaction. Based on the combination of the second input operation and the target multiplier, the system performs specific virtual attribute update calculations:

[0037] f 新 =f 原 +(λ 输入 ×N), Equation (1)

[0038] In the formula, f 新 This represents the updated virtual attribute value, f. 原 λ represents the original virtual attribute value. 输入 This represents the attribute update value corresponding to the second input operation value, and N represents the target virtual attribute update multiplier. Therefore, by integrating the multiplier mechanism, players can achieve significant attribute updates with minimal input, avoiding the tedious operations caused by excessive repetitive clicks or frequent input.

[0039] Through the embodiments of this application, by using preset virtual attribute operation conversion conditions and dynamic multiplier algorithms, the operation mode can be automatically adjusted according to different player behaviors and game progress. By reducing continuous repeated clicks, providing real-time feedback and precise adjustments, the operation burden and lag problems in traditional virtual attribute operations are greatly alleviated, allowing players to maintain a smooth and continuous experience in a fast-paced game.

[0040] In some examples of embodiments of this application, the method further includes: obtaining the updated value of the user virtual attribute, and rendering a virtual attribute adjustment progress bar based on the updated value of the user virtual attribute and the range of user virtual attribute values, wherein the range of user virtual attribute values ​​is the numerical range between the upper limit value and the lower limit value of the user virtual attribute.

[0041] Here, to facilitate users' intuitive understanding of the current attribute status, the system normalizes the value based on its range and renders a dynamically adjusted virtual attribute progress bar accordingly. The system calculates the current attribute position in real time and visualizes it as a progress bar in the user interface.

[0042] It should be understood that progress bars can use different rendering methods, such as linearly stretched bar charts. Furthermore, if an attribute value reaches or exceeds a certain threshold (such as approaching the upper limit), the system can provide visual feedback (such as the color turning red or the prompt text "Approaching maximum value") to alert the user. Therefore, visually displaying the changes in virtual attribute values ​​as a progress bar helps users quickly understand the current state of the virtual attribute, avoiding the cognitive burden caused by purely numerical displays and improving the efficiency of perceiving attribute changes.

[0043] Regarding the specific implementation details of determining the target virtual attribute update ratio in step S120, in some examples of embodiments of this application, the target virtual attribute update ratio is determined based on the event ratio library and the control event corresponding to the parsed control operation information. The event ratio library contains multiple event ratio relationships, which define the control event and the corresponding virtual attribute update ratio.

[0044] Here, an event multiplier library is introduced as the basis for mapping the relationship between operation events and multipliers. Specifically, the event multiplier library can be a preset or dynamically updatable data structure used to store different types of user operation events and their corresponding multiplier factors, such as a single touch press (left mouse button / right mouse double click) -1x, a double touch press (left mouse button / right mouse double click) -10x, and so on. Through the embodiments of this application, by using the event multiplier library to predefine and configure different operation events, the system can quickly determine the corresponding multiplier value without complex judgment logic, thereby improving the speed and accuracy of multiplier response and ensuring that user operations have instant feedback.

[0045] Regarding the implementation details of step S130, in some examples of embodiments of this application, the second input operation includes a touch screen swiping operation or a mouse wheel scrolling operation. By parsing the touch screen swiping distance and swiping direction or the mouse wheel scrolling width and direction corresponding to the second input operation, the user's virtual attributes are updated according to the parsed touch screen swiping distance and swiping direction or the mouse wheel scrolling width and direction, and in combination with the target virtual attribute update ratio.

[0046] Here, the system further refines attribute values ​​by listening to and parsing key parameters in touchscreen swipe events or mouse wheel events. Specifically, touchscreen swipe distance is the distance covered by a single continuous swipe on the touchscreen, and mouse wheel scroll amplitude represents the magnitude or unit scroll amount of each scroll, usually provided by event parameters from the operating system (such as ±120, with positive and negative values ​​indicating direction). Touchscreen swipe direction refers to the trajectory of the continuous swipe on the touchscreen, and mouse wheel direction is determined by the sign of the scroll amplitude to determine whether the wheel is scrolling up (usually increasing the attribute value) or down (usually decreasing the attribute value), thus determining the direction of the update.

[0047] Then, the target virtual attribute update ratio is combined with the parsed roll and direction parameters to calculate the actual attribute change value. The final calculation result can be positive or negative, representing an increase or decrease in the virtual attribute, respectively. Based on the calculated attribute change value, the system performs an update operation on the target virtual attribute, and the update result is synchronously fed back to the front-end interface, including visual feedback such as attribute value changes and progress bars, ensuring that the user's operation results are visualized.

[0048] Through the embodiments of this application, taking advantage of the inherent support for continuous input and rapid changes in touch screen sliding or mouse wheel operation, by introducing a parsing mechanism for touch screen sliding or mouse wheel operation in the second input operation, the user's control dimension over virtual attribute operation is expanded, making attribute value changes more continuous, dynamic and controllable, and realizing precise linkage between input intensity and output result.

[0049] Figure 2 A flowchart illustrating an example of constructing an event multiplier library according to an embodiment of this application is shown. In this embodiment, the event multiplier library may be customized for the user.

[0050] like Figure 2 As shown, in step S210, at least one initialization event multiplier relationship is obtained, and the virtual attribute upgrade control notification interface is rendered according to each initialization event multiplier relationship.

[0051] Here, the virtual attribute upgrade control notification interface contains multiple virtual attribute control upgrade notification options, each of which is used to present the corresponding initialization event multiplier relationship.

[0052] Specifically, when initializing the virtual attribute operation mechanism or triggering the upgrade guidance process, the system can pre-set or recommend a set of initialization event multiplier relationships. Each event multiplier relationship defines a specific control event (such as single touch, double touch, long press, swipe, and mouse click, double click, long press, scroll wheel, etc.) and its corresponding virtual attribute update multiplier.

[0053] Based on this initial multiplier relationship, the front end can dynamically render a virtual attribute upgrade control notification interface. This interface includes multiple virtual attribute control upgrade notification options, each option graphically displaying a control event and its corresponding multiplier, such as: icon + operation instructions + current multiplier value, and can also display animated simulation operation effects.

[0054] In terms of business application scenarios, this interface can be presented when a player unlocks the quick attribute operation function for the first time in a game, or when a virtual attribute reaches a stage node (such as before an upgrade) to prompt advanced control strategies. This clearly demonstrates to users the control events supported by the system and their corresponding attribute update efficiency, using a visual interactive guidance method to improve the discoverability and acceptance of the function, and helps reduce the learning cost.

[0055] In step S221, when a user confirmation operation is detected for the virtual attribute upgrade control notification interface, an event multiplier library is constructed based on the multiplier relationships of each initialization event.

[0056] In some implementations, when a user confirms their choice in the virtual attribute upgrade control notification interface (e.g., by clicking the "Confirm Use" or "One-Click Activation" buttons), the system assumes the user has accepted the initial multiplier settings. At this point, the system directly constructs an event multiplier library for subsequent operations based on this initial event multiplier relationship and stores this library in the user's local or server-side profile, supporting subsequent loading, updates, or version switching. This quickly completes the initial configuration process of the system's multiplier mechanism, reduces user operational costs, and ensures that the event multiplier library content has a clear user confirmation source, avoiding misjudgments in attribute multiplier control.

[0057] In step S223, when a user modification operation is detected on the virtual attribute upgrade control notification interface, a multiplier configuration user request is obtained, and an event multiplier library is constructed based on the configuration event multiplier relationship indicated by the multiplier configuration user request and the multiplier relationships of each initialization event.

[0058] Here, if the user does not directly confirm the initial configuration but instead makes custom modifications to the multiplier relationships (i.e., "modification operation"), the system will enter the multiplier configuration process. Specifically, the system listens for user modifications to multiplier options in the interface, such as adjusting multiplier values ​​(e.g., changing the multiplier of a double-tap from ×10 to ×15, or the multiplier of a double-tap from ×10 to ×15), replacing control events (e.g., changing "long press" to "Shift + single click"), deleting infrequently used events, or adding new operation methods, etc. Finally, based on the user's modified multiplier configuration request and the original initial multiplier relationships, the system generates a user-customized event multiplier library.

[0059] Furthermore, after the user completes the modifications, the system can save the custom multiplier library to the user's preferences settings, supporting reuse in different virtual attribute operation scenarios, as well as one-click reset or export / import functions. This provides "soft configuration capabilities" for the multiplier mechanism, enabling user-defined and personalized configuration, and supporting expansion and compatibility across various business scenarios, thus enhancing system flexibility.

[0060] Regarding the implementation details of step S223, in some examples of embodiments of this application, it is detected whether the multiplier configuration user request is triggered by a user operation on the virtual attribute manipulation upgrade notification option. If yes, the first initialization event multiplier relationship corresponding to the first virtual attribute manipulation upgrade notification option is deleted, and an event multiplier library is constructed based on the configured event multiplier relationship and the updated initialization event multiplier relationships; if no, the event multiplier library is constructed based on the configured event multiplier relationship and the initialization event multiplier relationships.

[0061] Here, in order to improve the intelligence and context response capability of the event multiplier configuration mechanism, the system first determines the triggering source of the request before processing the user's multiplier configuration request, thereby distinguishing different operation paths and formulating different update strategies.

[0062] Specifically, the system listens to and analyzes the background of the multiplier configuration request, such as whether the user has modified a specific multiplier notification option (e.g., double-pressing the touchscreen or double-clicking the mouse ×10) in the virtual attribute control upgrade notification interface, such as deleting or canceling an operation event, or replacing the original event with a new operation method, and records the initialization event multiplier relationship corresponding to the modified notification option.

[0063] On the one hand, if the option triggers a negative result, it is considered that the user has not explicitly performed a targeted operation on the notification interface. This indicates that the user request for multiplier configuration is not intended to modify the original event multiplier relationship, but rather to add a relationship to the library. For example, a multiplier configuration user request initiated through system settings, preference panel, or other entry points allows the system to add the configured event multiplier relationship to the multiplier library as a supplement or overriding relationship instead of deleting the original initial multiplier relationship.

[0064] On the other hand, if the option triggers the detection result, the system recognizes that the user intends to modify or discard a certain default suggested operation method in the notification interface, and should delete the "first initialization event multiplier relationship" (i.e., default item) corresponding to the notification option, merge the new configuration event multiplier relationship specified by the user with the remaining initialization multiplier relationships, and generate the final event multiplier library.

[0065] Through the embodiments of this application, by determining the source of the configuration request, the system can distinguish between two types of user intents: "actively updating suggested items" and "extended configuration items," thereby adopting the most appropriate multiplier library update method. Users can not only add their own operation preferences but also explicitly remove the system-recommended default multiplier relationships, achieving a higher degree of freedom in choosing control strategies and enhancing user dominance in virtual attribute interactions. Therefore, by hierarchically identifying and differentiatedly processing user intents during event multiplier configuration, not only is a strong degree of configuration freedom and control provided, but the system's responsiveness and user behavior modeling capabilities are also enhanced, significantly improving the interaction depth and usability of the entire virtual attribute operating system.

[0066] Regarding the explanation of the initialization event multiplier relationship, in some implementations, it is a system-preset initialization event multiplier relationship, which can be dynamically updated based on the behavior analysis of the player user group.

[0067] Figure 3 A flowchart illustrating an example of constructing or updating an initialization event multiplier relationship according to an embodiment of this application is shown.

[0068] like Figure 3 As shown, in step S310, the multiplier configuration user request dataset for the corresponding historical time period is obtained, and the configuration manipulation events and corresponding configuration virtual attribute multipliers in each multiplier configuration user request are parsed.

[0069] In some implementations, the system logs all multiplier configuration requests submitted by a group of players (not limited to individual players) within a certain historical period in the background. The logs store configuration control event identifiers (such as clicks, long presses, swipes, etc.), the multiplier values ​​submitted by users (reflecting players' needs and preferences for virtual attribute updates), and timestamps and contextual information (used to distinguish behavioral characteristics in different time periods and scenarios). Furthermore, the collected data is formatted and stored in a structured manner, forming a standardized data format for subsequent feature extraction.

[0070] In step S320, feature vectors of configuration control events corresponding to user requests for each multiplier configuration are constructed, and corresponding control event clusters are obtained through clustering.

[0071] In some implementations, event attribute information of the configuration control events in each scaling configuration request is extracted, such as operation type (e.g., click / scroll wheel / long press), operation parameters (e.g., duration, scroll wheel width, etc.), and operation key combinations (whether they include Ctrl / Shift, etc.), and then the corresponding configuration control event feature vector is constructed.

[0072] Here, all vectors are input into clustering algorithms (such as K-means, DBSCAN, HDBSCAN, etc.) to generate several clusters of manipulation events. The events within each cluster are highly similar in terms of operation methods and user preferences. Therefore, using unsupervised learning techniques, features of players' virtual attribute operations are automatically extracted, reducing subjective intervention and enabling the system to dynamically adapt to the actual operational behaviors of different player groups. This achieves similarity modeling of user operation behaviors, merging semantically similar but formally different input methods.

[0073] In step S330, a preset number of target control event clusters are selected from each control event cluster according to the sorting result of the cluster cardinality, and the event name of each target control event cluster is defined as the corresponding initialization control event.

[0074] In some implementations, the system sorts all control event clusters in descending order of the number of data points within each cluster (cluster cardinality), and selects the top M clusters (M being a preset value, such as 5, 8, or 10) as target control event clusters. Each target cluster represents a type of mainstream user preference behavior. Further, the cluster center or most frequent event is extracted for each cluster and used as the initial control event name for that cluster, such as "left-click and hold for 3 seconds," "scroll wheel up quickly," or "right-click + Shift." Thus, the system sorts clusters based on the number of data points (i.e., the frequency or representativeness of control events) to determine which clusters are more typical and common, ensuring that the selected target control events are highly representative and reflect the overall operational preferences of the player group.

[0075] In step S340, for each target control event cluster, the average value of the configuration virtual attribute multiplier indicated by each data point within the target control event cluster is calculated and used as the corresponding initial virtual attribute multiplier.

[0076] More specifically, for each target manipulation event cluster, the virtual attribute multipliers are extracted from all data points within it, and obvious outliers are eliminated (e.g., by using median or pruning methods to further ensure data stability). The arithmetic mean or weighted average (weighting can be based on factors such as event frequency) is calculated as the initial virtual attribute multiplier for that event cluster. Furthermore, an error detection mechanism can be introduced, such as detecting the standard deviation of each data point or the proportion of outliers, to ensure that the calculation results are statistically significant and stable.

[0077] Therefore, the initial multiplier corresponding to the initial control event can be accurately set based on the historical data distribution of the player group, and can be dynamically adjusted and updated over time, thus better adapting to the needs of different game stages.

[0078] In step S350, the initialization event multiplier relationship is constructed or updated based on each initialization control event and the corresponding initialization virtual attribute multiplier.

[0079] Here, the preset name and corresponding initial virtual attribute multiplier of each of the aforementioned target manipulation events are integrated into a mapping relationship (e.g., stored through a dictionary, configuration table, or database table) to form a complete initialization event multiplier relationship, which is used as the system's default configuration parameter in virtual attribute operations and is recommended to the user or directly invoked during the player's operation response process.

[0080] Furthermore, the system can periodically review and update the mapping relationships, and also supports manual intervention and debugging by operations personnel to ensure the system flexibly adapts to different scenario requirements. Thus, the constructed multiplier relationships guarantee that the system responds based on data in actual operation, and dynamic updates enable the system to continuously adapt to changes in player behavior, achieving precise control and optimization.

[0081] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of combined actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Secondly, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application. In the above embodiments, the descriptions of each embodiment have their own emphasis; for parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0082] Figure 4 A structural block diagram of an example of an operation control device for a virtual attribute according to an embodiment of this application is shown.

[0083] like Figure 4 As shown, a virtual attribute operation control device 400 includes a conversion detection unit 410, a multiplier determination unit 420, and an attribute update unit 430.

[0084] The conversion detection unit 410 is used to acquire the first input operation and detect whether the first input operation meets the preset virtual attribute operation conversion conditions.

[0085] The rate determination unit 420 is used to determine the target virtual attribute update rate corresponding to the first input operation when the virtual attribute operation conversion condition is detected to be met; the target virtual attribute update rate defines the update rate of the user virtual attribute in response to the input operation.

[0086] The attribute update unit 430 is used to obtain the second input operation and update the user virtual attribute according to the second input operation and the target virtual attribute update ratio.

[0087] In some embodiments, this application provides a non-volatile computer-readable storage medium storing one or more programs including execution instructions. The execution instructions can be read and executed by an electronic device (including but not limited to a computer, server, or network device) to perform the steps of the operation control method for any of the virtual attributes described above in this application.

[0088] In some embodiments, this application also provides a computer program product, the computer program product including a computer program stored on a non-volatile computer-readable storage medium, the computer program including program instructions, which, when executed by a computer, cause the computer to perform the steps of the operation control method for any of the above-mentioned virtual attributes.

[0089] In some embodiments, this application also provides an electronic device, which includes: at least one processor and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the steps of an operation control method for virtual attributes.

[0090] Figure 5 This is a schematic diagram of the hardware structure of an electronic device for executing a virtual attribute operation control method according to another embodiment of this application, as shown below. Figure 5 As shown, the device includes:

[0091] One or more processors 510 and memory 520, Figure 5 Take the 510 processor as an example.

[0092] The device for executing the operation control method of virtual attributes may further include: an input device 530 and an output device 540.

[0093] The processor 510, memory 520, input device 530, and output device 540 can be connected via a bus or other means. Figure 5 Taking the bus connection between China and Israel as an example.

[0094] The memory 520, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as the program instructions / modules corresponding to the virtual attribute operation control method in the embodiments of this application. The processor 510 executes various functional applications and data processing of the server by running the non-volatile software programs, instructions, and modules stored in the memory 520, thereby implementing the virtual attribute operation control method of the above-described method embodiments.

[0095] The memory 520 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the electronic device. Furthermore, the memory 520 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 520 may optionally include memory remotely located relative to the processor 510, and these remote memories can be connected to the electronic device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0096] Input device 530 can receive input digital or character information and generate signals related to user settings and function control of the electronic device. Output device 540 may include display devices such as a display screen.

[0097] The one or more modules are stored in the memory 520, and when executed by the one or more processors 510, they execute the virtual attribute operation control method in any of the above method embodiments.

[0098] The above-described product can perform the methods provided in the embodiments of this application, and has the corresponding functional modules and beneficial effects for performing the methods. Technical details not described in detail in this embodiment can be found in the methods provided in the embodiments of this application.

[0099] The electronic devices in this application embodiments exist in various forms, including but not limited to:

[0100] (1) Mobile communication devices: These devices are characterized by their mobile communication capabilities and primarily aim to provide voice and data communication. These terminals include smartphones, multimedia phones, feature phones, and low-end phones.

[0101] (2) Ultra-mobile personal computer devices: These devices fall under the category of personal computers, possessing computing and processing capabilities, and generally also have mobile internet access features. These terminals include: PDAs, MIDs, and UMPCs, etc.

[0102] (3) Portable entertainment devices: These devices can display and play multimedia content. This category includes audio and video players, handheld game consoles, e-book readers, as well as smart toys and portable car navigation devices.

[0103] (4) Other airborne electronic devices with data interaction capabilities, such as vehicle-mounted systems installed on vehicles.

[0104] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0105] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented using software plus a general-purpose hardware platform, or of course, using hardware. Based on this understanding, the above technical solutions, in essence or the parts that contribute to the related technology, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0106] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for controlling the operation of virtual attributes in a game, comprising: A first input operation is obtained, and it is detected whether the first input operation meets the preset virtual attribute operation conversion conditions. The first input operation includes control operation information, which includes at least one type of control event, such as touch screen swipe operation, touch screen press operation, mouse long press operation, or mouse wheel operation. If the virtual attribute operation conversion condition is met, the target virtual attribute update ratio corresponding to the first input operation is determined according to the event multiplier library and the control event corresponding to the parsed control operation information. The target virtual attribute update ratio defines the update ratio of the user virtual attribute in response to input operations; The event multiplier relationship defines the manipulation event and the corresponding virtual attribute update multiplier; Obtain a second input operation, and update the user's virtual attributes based on the second input operation and the target virtual attribute update ratio; The event multiplier library is constructed based on at least one initial event multiplier relationship; The construction or updating of the initialization event multiplier relationship includes: Obtain the dataset of user requests for multiplier configuration for the corresponding historical time period, and parse the configuration manipulation events and corresponding configuration virtual attribute multipliers in each user request for multiplier configuration. Construct feature vectors of configuration control events corresponding to each of the aforementioned multiplier configuration user requests, and obtain corresponding control event clusters through clustering processing; Based on the sorting result of the cluster cardinality, a preset number of target control event clusters are selected from each control event cluster, and the event name of each target control event cluster is defined as the corresponding initialization control event. For each target control event cluster, the average value of the configuration virtual attribute multiplier indicated by each data point within the target control event cluster is calculated and used as the corresponding initial virtual attribute multiplier. Based on each of the initialization control events and the corresponding initialization virtual attribute multipliers, construct or update the initialization event multiplier relationship.

2. The method according to claim 1, wherein, The step of detecting whether the first input operation meets the preset virtual attribute operation conversion conditions includes: Parse the control point coordinates and control operation information contained in the first input operation; Based on the control point coordinates and control operation information, check whether the preset virtual attribute operation conversion conditions are met.

3. The method according to claim 1, wherein, The second input operation includes touch screen swiping or mouse wheel scrolling. The step of updating the user's virtual attributes based on the second input operation and the target virtual attribute update ratio includes: Analyze the touch screen swipe distance and touch screen swipe direction, or the mouse wheel scroll width and mouse wheel direction of the second input operation; The user's virtual attributes are updated based on the analyzed touch screen swipe distance and swipe direction or mouse wheel scroll width and direction, combined with the target virtual attribute update ratio.

4. The method according to claim 1, wherein, The construction of the event multiplier library also includes: At least one initialization event multiplier relationship is obtained, and a virtual attribute upgrade control notification interface is rendered according to each of the initialization event multiplier relationships; the virtual attribute upgrade control notification interface includes multiple virtual attribute control upgrade notification options, and each of the virtual attribute control upgrade notification options is used to present the corresponding initialization event multiplier relationship. Upon detecting a user confirmation operation on the virtual attribute upgrade control notification interface, an event multiplier library is constructed based on the multiplier relationships of each initialization event. Upon detecting a user modification operation on the virtual attribute upgrade control notification interface, a multiplier configuration user request is obtained, and an event multiplier library is constructed based on the configuration event multiplier relationship indicated by the multiplier configuration user request and each of the initialization event multiplier relationships.

5. The method according to claim 4, wherein, The step of constructing an event multiplier library based on the configuration event multiplier relationship indicated by the user request and the various initialization event multiplier relationships includes: Detect whether the multiplier configuration user request was triggered by a user action targeting the virtual attribute control upgrade notification option; If so, delete the first initialization event multiplier relationship corresponding to the first virtual attribute control upgrade notification option, and construct an event multiplier library based on the configured event multiplier relationship and the updated initialization event multiplier relationships; If not, then an event multiplier library is constructed based on the configured event multiplier relationship and each of the initialization event multiplier relationships.

6. The method according to claim 1, wherein, The method further includes updating the user's virtual attributes based on the second input operation and the target virtual attribute update ratio: Obtain the real-time virtual attribute multiplier value under the first input operation state; When the virtual attribute multiplier value reaches the preset value, the virtual attribute multiplier value will pause updating within the preset time interval, and a user prompt message will be generated.

7. A device for controlling the operation of virtual attributes in a game, comprising: A conversion detection unit is used to acquire a first input operation and detect whether the first input operation meets a preset virtual attribute operation conversion condition. The first input operation includes control operation information, which includes at least one type of control event such as touch screen swipe operation, touch screen press operation, mouse long press operation, or mouse wheel operation. The multiplier determination unit is used to determine the target virtual attribute update multiplier corresponding to the first input operation based on the event multiplier library and the control event corresponding to the parsed control operation information when the virtual attribute operation conversion condition is detected. The target virtual attribute update ratio defines the update ratio of the user virtual attribute in response to input operations; The event multiplier relationship defines the manipulation event and the corresponding virtual attribute update multiplier; An attribute update unit is used to obtain a second input operation and update the user's virtual attributes according to the second input operation and the target virtual attribute update ratio; The event multiplier library is constructed based on at least one initial event multiplier relationship; The construction or updating of the initialization event multiplier relationship includes: Obtain the dataset of user requests for multiplier configuration for the corresponding historical time period, and parse the configuration manipulation events and corresponding configuration virtual attribute multipliers in each user request for multiplier configuration. Construct feature vectors of configuration control events corresponding to each of the aforementioned multiplier configuration user requests, and obtain corresponding control event clusters through clustering processing; Based on the sorting result of the cluster cardinality, a preset number of target control event clusters are selected from each control event cluster, and the event name of each target control event cluster is defined as the corresponding initialization control event. For each target control event cluster, the average value of the configuration virtual attribute multiplier indicated by each data point within the target control event cluster is calculated and used as the corresponding initial virtual attribute multiplier. Based on each of the initialization control events and the corresponding initialization virtual attribute multipliers, construct or update the initialization event multiplier relationship.

Images