Method and apparatus for controlling virtual object, device, and storage medium
By generating multiple capture attempts with a single trigger operation, the problem of low capture efficiency for virtual pets is solved, achieving the effects of simplified operation, improved efficiency, and enhanced gaming experience.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- TENCENT TECHNOLOGY (SHENZHEN) CO LTD
- Filing Date
- 2025-10-15
- Publication Date
- 2026-05-07
AI Technical Summary
In existing technologies, capturing virtual pets requires multiple executions of the capture control operation, which increases time costs, reduces capture efficiency, increases repetitiveness and continuity of operations, and may also affect the gaming experience and server load.
By triggering a single operation, multiple capture attempts are generated consecutively, with each capture success probability less than 1. The capture operation is automatically executed until success is achieved or the number of attempts is exhausted, reducing the number of user interactions and optimizing the operation logic.
The operation steps have been simplified, reducing the user's workload and time consumption, improving capture efficiency, and enhancing the game's fun and server processing capabilities.
Smart Images

Figure CN2025127809_07052026_PF_FP_ABST
Abstract
Description
Methods, devices, equipment, and storage media for controlling virtual objects
[0001] Cross-references to related applications
[0002] This application is based on Chinese Patent Application No. 202411548436.4, filed on October 31, 2024, and claims priority to that Chinese Patent Application, the entire contents of which are incorporated herein by reference. Technical Field
[0003] This application relates to the field of computer technology, and in particular to a method, apparatus, device, and storage medium for controlling virtual objects. Background Technology
[0004] In most games, if a user wants to have their own pet, they need to capture the virtual pet by controlling the main virtual object. Once the virtual pet is successfully captured, it becomes the pet of the main virtual object.
[0005] In related technologies, when controlling a master virtual object to capture a virtual pet, it is necessary to execute operations on the capture control. For example, each time an operation is executed on the capture control, the virtual pet is captured once. If the virtual pet is not captured successfully, the operation on the capture control is executed again, and the virtual pet is captured again, until the virtual pet is captured.
[0006] However, in the aforementioned technologies, each capture of a virtual pet corresponds to an operation on the capture control. That is, each capture of a virtual pet requires triggering the capture control separately, and the user needs to repeat the operation multiple times. The repetitiveness of the operation steps directly leads to increased time costs, and the interval between multiple operations may reduce the continuity of capture, resulting in low capture efficiency for virtual pets. Summary of the Invention
[0007] This application provides a method, apparatus, device, and storage medium for controlling virtual objects, which can improve the efficiency of capturing virtual pets. The technical solution provided by this application is as follows:
[0008] This application provides a method for controlling a virtual object, the method comprising:
[0009] Display a virtual environment, which includes a main virtual object and a virtual pet;
[0010] The system receives a first trigger operation from a capture control for the virtual pet, wherein the first trigger operation is used to generate multiple consecutive capture operations for the virtual pet, and the probability of successfully capturing the virtual pet in each capture operation is less than 1.
[0011] In response to the first triggering operation, the master virtual object is controlled to perform at least one capture operation on the virtual pet until the virtual pet is successfully captured or the number of capture operations generated by the first triggering operation is exhausted.
[0012] This application provides a control device for a virtual object, the device comprising:
[0013] The display module is configured to display a virtual environment, which includes a main virtual object and a virtual pet.
[0014] The receiving module is configured to receive a first trigger operation of the capture control for the virtual pet, wherein the first trigger operation is used to generate multiple consecutive capture operations for the virtual pet, and the probability of successfully capturing the virtual pet in each capture operation is less than 1.
[0015] The control module is configured to respond to the first trigger operation by controlling the main virtual object to perform at least one capture operation on the virtual pet until the virtual pet is successfully captured or the number of capture operations generated by the first trigger operation is exhausted.
[0016] This application provides a terminal device, which includes a processor and a memory. The memory stores a computer program, which is loaded and executed by the processor to implement the above-described virtual object control method.
[0017] This application provides a computer-readable storage medium storing a computer program, which is loaded and executed by a processor to implement the above-described virtual object control method.
[0018] This application provides a computer program product, which includes a computer program that is loaded and executed by a processor to implement the above-described virtual object control method.
[0019] The embodiments of this application can bring the following beneficial effects:
[0020] Considering the low capture efficiency caused by the need to perform an operation on the capture control for each capture in related technologies, the technical solution provided in this application can generate multiple consecutive capture operations for virtual pets through one step or one operation on the capture control (i.e., the first trigger operation). The success probability of each capture is independent (all less than 1). This relaxation reduces the number of user interactions from the source of operation. Users do not need to perform a separate trigger action for each capture; instead, they can start the continuous capture process with a single operation. Thus, the operation steps in related technologies are simplified from multiple triggers to a single trigger, reducing the user's operational burden and time consumption. Simultaneously, the continuity of continuous capture avoids the efficiency loss that may be caused by intervals between single operations, allowing more capture attempts to be completed within the same time frame. Ultimately, without changing the success probability of a single capture, this application eliminates the need to perform multiple operations on the capture control. By optimizing the operation logic, the operation steps are simplified, improving the capture efficiency for virtual pets. Attached Figure Description
[0021] Figure 1 is a schematic diagram of the implementation environment of the solution provided in the embodiments of this application;
[0022] Figure 2 is a schematic diagram of the virtual pet capture method provided by the related technology;
[0023] Figure 3 is a flowchart of the virtual object control method provided in an embodiment of this application;
[0024] Figure 4 is a flowchart of the virtual object control method provided in an embodiment of this application;
[0025] Figure 5 is a flowchart of the virtual object control method provided in an embodiment of this application;
[0026] Figure 6 is a schematic diagram of the crosshair and capture probability provided in the embodiments of this application;
[0027] Figure 7 is a schematic diagram of a single capture operation provided in an embodiment of this application;
[0028] Figure 8 is a schematic diagram of the countdown reduction provided in an embodiment of this application;
[0029] Figure 9 is a schematic diagram of the execution process of the first triggering operation provided in the embodiment of this application;
[0030] Figure 10 is a schematic diagram of the number of triggering operations provided in the embodiments of this application;
[0031] Figure 11 is a schematic diagram of the refresh of duration indication information provided in an embodiment of this application;
[0032] Figure 12 is a schematic diagram of different postures of the main virtual object throwing and capturing props provided in the embodiments of this application;
[0033] Figure 13 is a schematic diagram of at least one capture operation provided in an embodiment of this application;
[0034] Figure 14 is a schematic diagram showing the continuous decrease in the number of capture operations provided in the embodiments of this application;
[0035] Figure 15 is a schematic diagram of successfully capturing a virtual pet according to an embodiment of this application;
[0036] Figure 16 is a schematic diagram of the return of the capture tool provided in an embodiment of this application;
[0037] Figure 17 is a schematic diagram of the virtual pet capture process provided in the embodiments of this application;
[0038] Figure 18 is a block diagram of a virtual object control device provided in an embodiment of this application;
[0039] Figure 19 is a structural block diagram of the terminal device provided in an embodiment of this application. Detailed Implementation
[0040] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.
[0041] Before introducing the embodiments of this application, the following explanations are provided for the terms appearing in this solution to facilitate understanding:
[0042] 1. Virtual Environment: This is the environment displayed (or provided) by an application when it runs on a terminal device. This virtual environment can be a simulation of the real world, a semi-simulated / semi-fictional three-dimensional world, or a purely fictional three-dimensional world. The virtual environment can be any of a two-dimensional, 2.5-dimensional, or three-dimensional virtual environment. Optionally, this virtual environment is also used for virtual environment battles between at least two virtual characters, and it contains virtual resources available for use by at least two virtual characters. Optionally, this virtual environment includes freely moving virtual pets, and the controlling virtual object can choose which virtual pet to capture.
[0043] 2. Virtual Objects: These refer to both movable and immovable objects in a virtual scene. Movable objects can be at least one of virtual characters, virtual animals, or anime characters. Immovable objects can be at least one of virtual buildings, virtual plants, or virtual terrain. Optionally, when the virtual scene is a three-dimensional virtual scene, the virtual objects can be three-dimensional virtual models. Each virtual object has its own shape and volume in the three-dimensional virtual scene and occupies a portion of the space within the scene. Optionally, the virtual object is a three-dimensional character constructed based on three-dimensional human skeleton technology. This virtual object achieves different appearances by wearing different skins. In some implementations, virtual objects can also be implemented using 2.5D or 2D models; this application does not limit this. Depending on the method of controlling the virtual objects, they can be divided into user-controlled virtual objects and server-controlled virtual objects. User-controlled virtual objects are movable objects controlled by the client in the virtual scene. Server-controlled virtual objects are virtual objects controlled by automatic control algorithms or artificial intelligence programs on the client or server. Server-controlled virtual objects include both movable and immovable objects in the virtual scene. An inactive object can respond to or influence the activities of an active object. For example, an active object can destroy an inactive object, or the active object can enter an inactive state when it enters an inactive object.
[0044] 3. Virtual Character: Refers to an active virtual object controlled by a user within the application's client. This virtual character can be at least one of a virtual human, a virtual animal, or an anime character. Optionally, when the virtual scene is a three-dimensional virtual scene, the virtual character can be a three-dimensional virtual model, each virtual character having its own shape and volume within the three-dimensional virtual scene and occupying a portion of the space within the scene. Optionally, the virtual character is a three-dimensional character constructed based on three-dimensional human skeleton technology, achieving different external appearances by wearing different skins. In some implementations, the virtual character can also be implemented using a 2.5D or 2D model; this application does not limit this aspect.
[0045] 4. Virtual Pet: A virtual pet is an interactive virtual object owned by a virtual character. Virtual pets can be controlled by users through a client application, or by automated control algorithms or artificial intelligence programs on the client or server. Therefore, some of a virtual pet's behavior is controlled by the user through the client, while other behaviors are controlled by automated control algorithms or artificial intelligence programs on the client or server. Users can manage at least one virtual pet owned by their virtual character. For example, users can issue commands to the virtual pet in the client application, allowing the virtual pet to perform tasks corresponding to the commands, including but not limited to combat, construction, farming, and industrial production. Virtual pets can perform related tasks based on automated control algorithms or artificial intelligence programs on the client or server, including but not limited to combat, construction, farming, and industrial production, and can also control virtual objects. The virtual pet can be a virtual object designed based on a real animal, a virtual object designed based on an anime character, or a virtual object designed by technicians. Optionally, when the virtual scene is a three-dimensional virtual scene, the virtual pet can be a three-dimensional virtual model, with each virtual pet having its own shape and volume in the three-dimensional virtual scene and occupying a portion of the space in the three-dimensional virtual scene. Optionally, the virtual pet is a three-dimensional object constructed based on three-dimensional skeletal technology. The virtual pet can achieve different appearances by wearing different skins. In some implementations, the virtual pet can also be implemented using a 2.5D or 2D model, and this application embodiment does not limit this.
[0046] 5. Non-player character: refers to a virtual object controlled by an automatic control algorithm or artificial intelligence program on the client or server. The non-player character can be at least one of virtual characters, virtual animals, virtual pets, or anime characters. Optionally, when the virtual scene is a three-dimensional virtual scene, the non-player character can be a three-dimensional virtual model, each non-player character having its own shape and volume in the three-dimensional virtual scene and occupying a portion of the space in the three-dimensional virtual scene. Optionally, the non-player character is a three-dimensional character constructed based on three-dimensional human skeleton technology, and the non-player character achieves different external appearances by wearing different skins. In some implementations, the non-player character can also be implemented using a 2.5D or 2D model; this application embodiment does not limit this. For example, the non-player character is a virtual pet.
[0047] 6. User Interface (UI) Controls: Any visible control or element on the application's user interface, such as images, input boxes, text boxes, buttons, labels, etc. Some of these UI controls respond to user actions; for example, a capture control used to capture a virtual pet. The user presses the capture control to capture the virtual pet. The UI controls involved in this application's embodiments include, but are not limited to, capture controls.
[0048] Please refer to Figure 1, which shows a schematic diagram of a computer system provided in an embodiment of this application. This computer system can realize a control system for virtual objects. The computer system may include: a terminal device 10 and a server 20.
[0049] There may be one or more terminal devices 10. Terminal devices 10 may be electronic devices such as mobile phones, tablets, game consoles, e-book readers, multimedia playback devices, wearable devices, PCs (Personal Computers), and in-vehicle terminals. A client for a target application (such as a game application) may be installed on the terminal device 10. Optionally, the target application may be an application that requires downloading and installation, or it may be an application that can be used instantly; this embodiment of the application does not limit this.
[0050] In this embodiment, the target application is an application that provides a virtual pet. This target application can be any of the following: a simulation program, a shooting game, a virtual reality (VR) application, an augmented reality (AR) application, a 3D mapping application, a virtual reality game, an augmented reality game, a first-person shooter (FPS) game, a multiplayer shooting survival game, a third-person shooter (TPS) game, a multiplayer online battle arena (MOBA) game, a strategy game (SLG), a social application, or an interactive entertainment application. Furthermore, the form or shape of the virtual character and virtual pet provided by different applications will vary, and their corresponding skills will also differ; this embodiment does not limit this. Optionally, the terminal device 10 runs a client of the aforementioned application. In some embodiments, the above-mentioned application is an application developed based on a three-dimensional virtual scene engine, such as the Unity engine. This virtual scene engine can construct three-dimensional virtual scenes, virtual objects, and virtual props, bringing users a more immersive gaming experience.
[0051] The aforementioned virtual scenes refer to scenarios created for the main virtual objects and virtual pets to engage in activities (such as gaming competitions), such as virtual houses, virtual islands, and virtual maps.
[0052] The aforementioned virtual objects refer to virtual characters, virtual vehicles, virtual items, etc., controlled by a user account within the target application; this application does not limit this. Taking a game application as an example, a virtual object refers to a game object controlled by a user account within the game application. Virtual objects can be in the form of a character, an animal, a cartoon character, or other forms; this application does not limit this. The main virtual object in this application is a virtual object controlled by the client. While the main virtual object in this application is a virtual object controlled by the client, virtual pets can also be virtual objects controlled by the server.
[0053] Server 20 is used to provide backend services for the client of the target application in terminal device 10. For example, server 20 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms, but it is not limited to these.
[0054] Terminal device 10 and server 20 can communicate with each other via a network. This network can be a wired network or a wireless network.
[0055] Before introducing the specific solution of this application, the relevant background technology will be briefly explained below.
[0056] In the relevant technology, as shown in Figure 2, the player presses the capture control, an aiming reticle appears, the player aims at the unit to be captured, and releases or clicks the capture control to control the main virtual object 200 to throw the capture item. After the capture item flies through the air or rolls on the ground for a certain distance, if the capture item hits the target (i.e., the target pet) 210, the capture begins. If it misses the target, the capture fails, and the capture item is consumed. If the player fails to capture and wants to continue capturing, the player needs to repeat the above process until a successful capture is achieved.
[0057] The relevant technologies suffer from at least the following drawbacks: ① Inefficiency: When players need to capture a target pet multiple times, they must use capture items and trigger capture controls each time, increasing the game's time cost and operational complexity. ② Repetitive Labor: Repeatedly performing the same capture actions can easily become monotonous and boring for players, reducing the game's enjoyment. ③ Frequent Item Use: Frequent use of capture items requires players to constantly replenish their inventory, and players cannot accurately predict the number of items required for multiple captures. ④ Poor Experience: Each capture may fail, and consecutive failures can severely impact player motivation and the overall gaming experience. ⑤ Lack of Strategy: Simple repetitive operations lack depth and strategy, making it difficult for players to improve their capture success rate through skill or strategy. ⑥ Single Mode: Currently, most games only support one fixed capture mode, lacking diverse and personalized capture methods. ⑦ Server Pressure: A large number of continuous capture requests may put significant pressure on the game server, affecting the game's stability and response speed.
[0058] Based on the shortcomings of the aforementioned related technologies, this application aims to solve the following problems: ① Simplified operation: By continuously pressing a button or mouse, players can use capture items continuously in one operation, reducing the number of repetitive operations. ② Increased efficiency: The new continuous capture method improves capture efficiency, allowing players to complete multiple captures in a shorter time. ③ Enhanced game presentation: Introducing different action expressions and feedback mechanisms provides a new visual and sensory experience for each capture, increasing the game's fun and appeal. ④ Facilitates player resource management: Although capture items are still consumed, the continuous capture method allows players to use and manage resources more strategically, avoiding waste. ⑤ Optimizes server load: Each capture requires the transmission of relevant data (such as pet status, item usage information, etc.), and continuous capture can merge these data transmissions. ⑥ Possesses rich and diverse expansion potential: The continuous capture mechanism allows for the addition of more types of capture effects and animations in the game, and players can choose the most suitable capture rhythm and strategy based on the characteristics of different pets. Specifically, the technical solutions provided by the embodiments of this application will be explained and described in conjunction with the following examples, which will not be elaborated here.
[0059] Please refer to Figure 3, which shows a flowchart of the virtual object control method provided in this application embodiment. The executing entity of each step of this method can be the terminal device 10 in the computer system shown in Figure 1, such as the client of the aforementioned target application. In the following method embodiments, for ease of description, only the executing entity of each step will be referred to as the "client". The method may include at least one of the following steps (310-330):
[0060] Step 310: Display the virtual environment, which includes the main virtual object and the virtual pet.
[0061] In this embodiment, when displaying a virtual environment on a terminal device, there are at least three display methods. The first is a first-person perspective, where a virtual camera is installed above the head of the main virtual object, and the view of the virtual environment observed by this virtual camera is used as the displayed virtual environment image. In this case, the displayed virtual environment image does not include the main virtual object. The second is a third-person perspective, where a virtual camera is installed behind the main virtual object, and the view of the virtual environment observed by this virtual camera is used as the displayed virtual environment image. In this case, the displayed virtual environment image may include part or all of the main virtual object. The orientation of both the first-person and third-person perspectives changes with the orientation of the main virtual object. The third is another perspective with a specific direction, whose orientation does not change with the orientation of the main virtual object. That is, the view of the entire virtual environment observed by the virtual camera according to a specific orientation is used as the displayed virtual environment image. At this time, the main virtual object can be displayed in the center of the virtual environment's display screen, or in other positions on the virtual environment's display screen, or not displayed at all; this application does not limit this. The virtual environment in this application's embodiments is considered to be at least one of a three-dimensional virtual environment, a two-dimensional virtual environment, or a 2.5-dimensional virtual environment; this application does not limit this.
[0062] The master-controlled virtual object mentioned in this application refers to a virtual object controlled by a user account in the client of a target application (such as a game application). The terminal device described above has the client of the target application installed. In some embodiments, the terminal device 10 in FIG1 includes a first terminal device and a second terminal device, wherein the first terminal device has the first client of the target application installed, and the second terminal device has the second client of the target application installed. The first user's first user account controls the first virtual object (also referred to as the master-controlled virtual object) in the first client of the target application, and the second user's second user account controls the second virtual object in the second client of the target application. Of course, in this application embodiment, the second virtual object, in addition to being a user-controlled virtual object, can also be a server-controlled virtual object (artificial intelligence virtual object). The first virtual object and the second virtual object can reside in the same virtual environment. The first virtual object and the second virtual object can also belong to the same faction, the same team, the same organization, have a friend relationship, or have temporary communication permissions; in this case, the second virtual object can be considered a friendly virtual object of the first virtual object. The first virtual object and the second virtual object can also belong to different factions, different teams, different organizations, or have an adversarial relationship; in this case, the second virtual object can be considered an adversary virtual object of the first virtual object. The client installed on the first terminal device and the second terminal device can be the same, or the client installed on the first terminal device and the second terminal device can be the same type of client on different operating system platforms (such as Android or iOS). The first terminal device can refer to one of a plurality of terminal devices, and the second terminal device can refer to another of a plurality of terminal devices. This embodiment only uses the first terminal device and the second terminal device as examples.
[0063] In some embodiments, the virtual environment includes virtual pets. The virtual pet mentioned in this application refers to a virtual object in the virtual environment that is different from the main virtual object. In some embodiments, the virtual pet may be the aforementioned second virtual object. The virtual pet may be a user-controlled virtual object or a server-controlled virtual object; this application does not limit this. When the virtual pet is a user-controlled virtual object, the main virtual object can capture other user-controlled virtual objects and use them as its pets. When the virtual pet is a server-controlled virtual object, the main virtual object can capture artificial intelligence virtual objects in the virtual environment controlled by the server according to a preset algorithm and use them as its pets. Once a virtual pet becomes the pet of the main virtual object, it is controlled by the main virtual object or by the user account controlling the main virtual object.
[0064] This application does not limit the number, shape, or location of virtual pets. The virtual pet can be an active or inactive object in the virtual environment.
[0065] Step 320: Receive the first trigger operation of the capture control for the virtual pet. The first trigger operation is used to generate multiple consecutive capture operations for the virtual pet. The probability of successfully capturing the virtual pet in each capture operation is less than 1.
[0066] In some embodiments, the capture control is a UI control. In some embodiments, the capture control is always displayed on the user interface. In some embodiments, the capture control is displayed on the user interface when the distance between the master virtual object and the virtual pet is less than or equal to a first threshold. The first threshold is a preset value. In some embodiments, the capture control is displayed in response to a click operation on a capture item (see explanation below).
[0067] In some embodiments, the capture control is not always displayed on the user interface. It is displayed in response to a press operation. The capture control is displayed at the press location of the press operation. The center point of the capture control is also the press location of the press operation.
[0068] In some embodiments, "displaying the capture control in response to a press operation" can refer to displaying the capture control in response to a press operation directly on the screen of the terminal device. Alternatively, it can refer to displaying the capture control in response to an operation on an external device connected to the terminal device. The external device refers to a device directly or indirectly connected to the terminal device. The external device includes, but is not limited to, at least one of the following: a mouse, a gamepad, a touchscreen, etc. "Displaying the capture control in response to a press operation" can refer to displaying the capture control in response to mouse operations (such as click operations, press operations, long press operations, etc.), gamepad operations (such as click operations, press operations, long press operations, etc.), or touchscreen operations (such as click operations, press operations, long press operations, etc.).
[0069] In some embodiments, in addition to operations directly targeting the capture controls displayed on the terminal device screen, operations targeting external devices connected to the terminal device can also be considered as the first triggering operation. Operations targeting external devices connected to the terminal device are considered as the first triggering operation targeting the capture controls. Operations targeting the joystick on a gamepad are considered as the first triggering operation targeting the capture controls. Operations targeting the mouse are considered as the first triggering operation targeting the capture controls. Operations targeting the touchscreen are considered as the first triggering operation targeting the capture controls.
[0070] The first triggering operation mentioned in the embodiments of this application can be a one-step operation in which the finger (or other part in contact with the device) does not leave the device. A user's long-press operation of a capture control is considered a first triggering operation. A user's long-press operation of a joystick on a gamepad is considered a first triggering operation. A user's long-press operation of at least one of the left mouse button, right mouse button, or scroll wheel is considered a first triggering operation. A user's long-press operation of a touchscreen is considered a first triggering operation.
[0071] In some embodiments, the first triggering operation is considered to have ended when the user's finger (or other part that came into contact with the device) leaves the device.
[0072] In some embodiments, the first triggering operation generates multiple consecutive capture operations against the virtual pet. The number of capture operations is determined based on the duration of the first triggering operation, the location of the first triggering operation, and the intensity of the first triggering operation. For details, please refer to the explanations of the embodiments below; further elaboration is not required here.
[0073] In some embodiments, a capture operation may not necessarily succeed in capturing a virtual pet. The probability of successfully capturing a virtual pet in each capture operation is less than 1. In some embodiments, each capture operation requires a certain operation time to complete. The probability of successfully capturing a virtual pet in each capture operation is a preset probability value. The probability of successfully capturing a virtual pet in each capture operation is different.
[0074] Step 330: In response to the first trigger operation, control the main virtual object to perform at least one capture operation on the virtual pet until the virtual pet is successfully captured or the number of capture operations generated by the first trigger operation is exhausted.
[0075] In some embodiments, after the first triggering operation ends, the controlling virtual object performs at least one capture operation on the virtual pet.
[0076] In some embodiments, taking K as an example, where K is an integer greater than 1, the number of capture operations generated by the first triggering operation is K. After the first triggering operation ends, the master virtual object has the capability to perform K capture operations. After the first triggering operation ends, the master virtual object is controlled to automatically execute capture operations. The master virtual object is controlled to start performing the first capture operation on the virtual pet. If the first capture operation successfully captures the virtual pet, no further capture operations are performed. If the first capture operation fails to capture the virtual pet, the master virtual object is controlled to perform the second capture operation on the virtual pet, until the virtual pet is successfully captured. In these K capture operations, there is a possibility that the virtual pet is successfully captured in the first capture operation. In these K capture operations, there is also a possibility that all K capture operations are used up without successfully capturing the virtual pet.
[0077] In some embodiments, the control virtual object in this application performs at least one capture operation on the virtual pet, one after another, with no time interval between two capture operations or a time interval less than a duration threshold. The duration threshold refers to the upper limit of time that ensures the user cannot perceive the interval between two capture operations. Specifically, it can be determined based on the persistence of human vision (100-150 milliseconds) and game interaction design conventions (50-100 milliseconds), while also considering the data processing capabilities of the terminal device. For example, setting the duration threshold to within 100 milliseconds avoids both user perception interruption due to excessively long intervals and system performance issues caused by excessively short intervals. After the previous capture operation ends, if the virtual pet is not successfully captured, the next capture operation automatically begins. In contrast, in related technologies, the user clicks the capture control again after one capture operation ends to achieve the next capture. Considering that the user clicking the capture control and the response from the terminal device, server, etc., all require time, the second capture operation in the related technologies must start later than the automatically executed second capture operation in this application. Therefore, this application can reduce the time required for multiple capture operations and improve capture efficiency.
[0078] This application does not limit how the capture operation is implemented. It can be achieved by using capture tools, by controlling the main virtual object itself to capture the virtual pet (e.g., by controlling the main virtual object to release capture skills), or by using the main virtual object to set traps to capture the virtual pet. In the following embodiments of this application, the capture operation is mainly described using capture tools as an example.
[0079] The technical solution provided in this application addresses the problem of low capture efficiency caused by the need to perform an operation on the capture control for each capture in related technologies. By performing an operation on the capture control in one step (i.e., the first trigger operation), multiple consecutive capture operations can be generated for the virtual pet, and the success probability of each capture exists independently (all less than 1). This relaxation reduces the number of user interactions from the source of operation. Users do not need to perform a separate trigger action for each capture, but can start the continuous capture process with a single operation. Thus, the operation steps are simplified from multiple triggers in related technologies to a single trigger, reducing the user's operational burden and operation time. At the same time, the continuity of continuous capture avoids the efficiency loss that may be caused by the interval between single operations, allowing more capture attempts to be completed in the same amount of time. Ultimately, without changing the success probability of a single capture, this application does not require multiple operations on the capture control. By optimizing the operation logic, the operation steps are simplified, and the capture efficiency of virtual pets is improved.
[0080] Please refer to Figure 4, which shows a flowchart of the virtual object control method provided in this application embodiment. The executing entity of each step of this method can be the terminal device 10 in the computer system shown in Figure 1, such as the client of the aforementioned target application. In the following method embodiments, for ease of description, only the executing entity of each step will be referred to as the "client". The method may include at least one of the following steps (410-440):
[0081] Step 410: Display the virtual environment, which includes the main virtual object and the virtual pet.
[0082] Step 420: Receive the first trigger operation of the capture control for the virtual pet. The first trigger operation is used to generate multiple consecutive capture operations for the virtual pet. The probability of successfully capturing the virtual pet in each capture operation is less than 1.
[0083] Step 430: Display the number of capture operations generated by the first trigger operation. The number of capture operations is determined based on the duration of the continuous press operation.
[0084] In some embodiments, the first triggering operation is a continuous press operation. The number of capture operations is determined based on the duration of the continuous press operation. A pre-defined correspondence table between continuous press duration and the number of capture operations is used. Once the continuous press duration is determined, the number of capture operations corresponding to that duration is determined from the correspondence table. A pre-defined functional relationship between continuous press duration and the number of capture operations is also used. Once the continuous press duration is determined, the number of capture operations corresponding to that duration is calculated based on the functional relationship.
[0085] In some embodiments, the number of capture operations is continuously increased during the execution of the first triggering operation.
[0086] During the execution of the first trigger operation, a capture operation is added each time the continuous press duration meets the first duration. For example, if the first duration is 3 seconds, during the execution of the first trigger operation, when the continuous press duration reaches 3 seconds, the number of capture operations is determined to be 1; when the continuous press duration reaches 6 seconds, a capture operation is added, and the number of capture operations is determined to be 2; when the continuous press duration reaches 9 seconds, another capture operation is added, and the number of capture operations is determined to be 3.
[0087] For example, as the number of capture operations increases, the press duration required for each additional capture operation changes. In one approach, the press duration required for each additional capture operation increases with the number of capture operations. For example, initially, a capture operation is added every 3 seconds, and after reaching 3 captures, a capture operation is added every 6 seconds. For instance, during the execution of the first trigger operation, when the continuous press duration reaches 9 seconds, the number of capture operations is determined to be 3; when the continuous press duration reaches 15 seconds, the number of capture operations is determined to be 4 (i.e., a capture operation is added every 6 seconds after the 9th second). In another approach, the press duration required for each additional capture operation decreases with the number of captures. For example, initially, a capture operation is added every 3 seconds, and after reaching 3 captures, a capture operation is added every 1 second. For example, during the execution of the first trigger operation, when the continuous press duration reaches 9 seconds, the number of capture operations is determined to be 3; when the continuous press duration reaches 15 seconds, the number of capture operations is determined to be 9 (that is, one capture operation is added every second for the next 6 seconds after the 9th second, for a total of 6 additional capture operations). This method of increasing the number of capture operations at unequal intervals reflects the diversity of methods for determining the number of capture operations. For example, the first method can increase the difficulty of increasing the number of capture operations, while the second method can quickly increase the number of capture operations, which is beneficial for enriching the forms of human-computer interaction.
[0088] In practical applications, as the first trigger operation is executed, the user interface displays the increasing number of capture operations as the duration of the continuous press increases. In some embodiments, the number of capture operations is displayed numerically. In some embodiments, the number of capture operations is indicated by a progress bar. As shown in Figure 9, the user interface displays the increasing number of capture operations as the duration of the continuous press increases, such as the number of capture operations changing from 910 to 920, that is, from 8 times to 18 times. As shown in Figure 10, the number of capture operations 1000 (i.e., the number 18) represents the current duration of continuous press, corresponding to 18 capture operations.
[0089] The technical solution provided in this application, by displaying the number of capture operations, allows users to have a clearer perception of the capture count, enriching both the display format and the human-computer interaction. Furthermore, real-time display of the capture operation count and progress facilitates targeted decision-making by users, preventing misoperations or experience interruptions due to information gaps. Simultaneously, the count display enhances the sense of feedback and controllability. Although continuous capture is initiated by a single trigger, the real-time updated count provides continuous interactive feedback to the user, allowing them to perceive that the terminal device is executing the capture process as expected, rather than being unresponsive. This feedback mechanism increases user trust in the operation, reduces operational doubts caused by a lack of transparency, and ultimately, by simplifying operations and improving efficiency, further enhances the integrity and satisfaction of the user experience.
[0090] The above embodiments describe a method for determining the number of capture operations based on the duration of a continuous press. Several other methods for determining the number of capture operations are described below.
[0091] In some embodiments, the number of capture operations is determined based on the operation position of the first triggering operation.
[0092] In practical applications, the number of capture operations varies depending on the location of the first trigger operation. For example, the response area containing the capture control can be divided into multiple sub-areas, each corresponding to a different number of capture operations. For example, after pressing the capture control, a prompt message indicating the number of capture operations for each sub-area is displayed. For instance, a prompt message is displayed in response to a press operation on the capture control, and the number of capture operations is determined in response to a drag operation. This drag operation is initiated by the press operation. Based on the endpoint of the drag operation, the sub-area containing that endpoint is determined, and the number of capture operations corresponding to that sub-area is further determined. This prompt message indicates the boundary positions of different sub-areas and the number of capture operations corresponding to each sub-area.
[0093] In some embodiments, the number of capture operations is determined based on the force of the first trigger operation. For example, the first trigger operation is a press operation.
[0094] In practical applications, the pressure sensor of the terminal device acquires the force of the first trigger operation. There is a positive correlation between the force of the first trigger operation and the number of capture operations; that is, the greater the force of the first trigger operation, the more capture operations are performed. Conversely, the smaller the force of the first trigger operation, the fewer capture operations are performed. After acquiring the force of the first trigger operation through the pressure sensor of the terminal device, the number of capture operations corresponding to that force is determined based on the relationship between the force and the number of capture operations.
[0095] The technical solution provided in this application, in addition to the duration of continuous pressing, can also flexibly determine the number of capture operations through operation position, operation force, etc. Compared with continuous pressing, flexibly determining the number of capture operations through operation position, operation force, etc. is simpler and takes less time. This application enriches the methods for determining the number of capture operations and reduces processing costs. This is because operation position, operation force, etc. are instantaneous operation characteristics. By binding instantaneous operation characteristics with the number of capture operations, the user only needs to make a precise position selection or force control once to instantly complete the number of times setting, without waiting. This shortens the operation time and reduces the probability of errors caused by continuous action. Meanwhile, this type of operation is more in line with users' natural interaction habits. For example, users can tap the sub-area on the left side of the screen for 5 captures and the sub-area on the right side for 10 captures, or lightly press for 3 captures and hard press for 8 captures. This makes the operation logic more consistent with human instincts and reduces the learning cost. In addition, different operation methods can adapt to diverse scenario needs (such as using force control to improve efficiency when capturing quickly and continuously, and using position selection to enhance accuracy when setting precise number of captures). On the basis of enriching the interaction forms, it further reduces the pressure on the terminal device to recognize and process continuous actions through instant operation and real-time feedback. This reduces the user's operational burden and indirectly optimizes the terminal device's resource consumption, achieving a dual improvement in user experience and technical cost.
[0096] Step 440: In response to the first trigger operation, control the main virtual object to perform at least one capture operation on the virtual pet until the virtual pet is successfully captured or the number of capture operations generated by the first trigger operation is exhausted.
[0097] In some embodiments, each capture operation consumes one capture operation count. As shown in Figure 13, after the first trigger operation ends, at least one capture operation is performed, and the capture result is determined. The remaining capture operation count changes from 52 to 51.
[0098] In practical applications, during the process of controlling the main virtual object to perform at least one capture operation on the virtual pet, each capture operation consumes one capture operation count. The decreasing number of capture operations can be displayed during this process. As shown in Figure 14, each capture operation consumes one capture operation count; for example, the number of capture operations decreases from 50 to 49, and then to 48.
[0099] For example, the number of capture operations generated by the first triggering operation is K. After one capture operation is performed, the number of capture operations displayed is K-1. After two capture operations are performed, the number of capture operations displayed is K-2. During the process of controlling the main virtual object to perform at least one capture operation on the virtual pet, the updated number of capture operations displayed can be understood as the remaining number of capture operations.
[0100] The technical solution provided in this application embodiment dynamically changes the number of capture operations by continuously increasing the number of capture operations during the execution of the first trigger operation, and by consuming one capture operation count for each capture operation. Similarly, displaying the dynamically changing number of capture operations facilitates the continuation or cessation of the continuous press operation, and also allows the user to know the number of capture operations already performed by the main virtual object and the remaining number of capture operations, enabling the user to make targeted decisions (such as waiting when there are enough remaining counts, or preparing to supplement the operation in advance when there are not enough counts), avoiding misoperations or experience interruptions caused by information gaps.
[0101] The following describes the number of capture items consumed in each capture operation.
[0102] In some embodiments, the number of capture items consumed in each capture operation within at least one capture operation is the same.
[0103] In practical applications, capture items are used to capture virtual pets. Capture items are virtual items that the main virtual object obtains from the virtual environment, or they can be obtained by exchanging virtual resources acquired from the virtual environment.
[0104] For example, each capture operation requires the consumption of capture items, and the number of capture items consumed in each capture operation is the same. For example, each capture operation consumes a first value of capture items, which is a preset value that can be set according to actual needs, such as setting the first value to 1.
[0105] Understandably, once the capture item is depleted, even if there are still capture attempts available, the main virtual object cannot be controlled to perform a capture operation. In other words, a capture operation can only be performed after the capture item is consumed.
[0106] For example, when the master virtual object has 10 capture items and each capture operation consumes 1 capture item, the maximum number of capture operations that can be performed is 10, that is, the number of capture operations generated by the first trigger operation is 10.
[0107] In some embodiments, the number of capture items consumed in the i-th capture operation in at least one capture operation is positively correlated with the value of i, where i is a positive integer.
[0108] For example, the larger i is, the more capture items are consumed in the i-th capture operation. For instance, the i-th capture operation consumes i capture items, that is, the first capture operation consumes 1 capture item, the second capture operation consumes 2 capture items, the third capture operation consumes 3 capture items, and so on.
[0109] For example, the larger i is, the more or less the number of capture items consumed in the i-th capture operation remains the same or increases. For instance, based on the number of operations i is in, the first to third capture operations corresponding to that number of operations consume 1 capture item each; the fourth to sixth capture operations consume 2 capture items each; the seventh to ninth capture operations consume 3 capture items each, and so on.
[0110] In some embodiments, the number of capture items consumed in each capture operation within at least one capture operation is positively correlated with the rarity of the virtual pet.
[0111] In practical applications, virtual pets can be divided into rarity levels (such as common, rare, epic, and legendary), and corresponding single capture item consumption standards can be set for different levels. The consumption increases positively with the rarity. At the same time, in combination with continuous capture scenarios, the single consumption standard will be applied to each capture operation to ensure that the higher the rarity of the target, the higher the total item cost for single capture and continuous capture. For example, if a common-level virtual pet requires 1 capture item per capture, then 10 consecutive captures would require 10 capture items. Rare-level virtual pets, due to their increased rarity, require 2 capture items per capture, and 20 basic items would be needed for 10 consecutive captures. Epic-level virtual pets require 3 capture items per capture, with the total cost for consecutive captures increasing accordingly. Legendary-level virtual pets, being the highest rarity target, require 5 capture items per capture. This tiered approach to item consumption visually reflects the difference in capture costs for pets of different rarity, aligning with users' understanding that high-value targets require high investment. It also reinforces the scarcity of rare pets and the sense of accomplishment in acquiring them through cost differentiation.
[0112] The technical solution provided in this application embodiment allows for different or the same number of capture items consumed in each capture operation. The more capture operations performed, the greater the number of capture items consumed in each operation, demonstrating that continuous captures require additional conditions, thus providing users with a richer capture experience and more diverse capture methods. Furthermore, this application embodiment supports differentiated capture item consumption (e.g., increasing with the number of captures or dynamically changing based on the rarity of the virtual pet), providing users with multiple decision-making options. For example, users can choose a stable mode with low number of captures and low consumption, or an efficient mode with high number of captures and high consumption, based on their item reserves, upgrading the capture behavior from a simple operation to a strategic resource allocation. Simultaneously, differentiated item consumption methods can match diverse game scenario needs. For example, for ordinary virtual pets, a fixed item consumption can lower the operational threshold; for rare virtual pets, increasing the capture challenge by requiring more capture items with more capture operations makes acquiring rare virtual pets more valuable and avoids monotonous gameplay due to uniform item consumption. In addition, this approach can guide users to manage game resources more rationally, reduce the waste or excessive consumption of props, and enhance the depth and fun of gameplay through the linkage mechanism of "operation-resource-result" on the basis of enriching the capture methods, so that users can have a more layered experience in the capture process, rather than simply repeating operations.
[0113] The following describes the timing for the main virtual object to throw and capture items.
[0114] In some embodiments, during the execution of the first triggering operation, if the number of capture operations increases, the main virtual object is controlled to throw a capture item at the virtual pet once.
[0115] For example, during the execution of the first trigger operation, if the number of capture operations increases, for example, from 1 to 2, the main virtual object is controlled to throw a capture item at the virtual pet once, and the number of capture items thrown is the same as the number of capture items consumed in the second capture operation. For example, if each capture operation consumes 1 capture item, then if the number of capture operations increases by one, the main virtual object is controlled to throw a capture item at the virtual pet.
[0116] For example, the terminal device may also display a throwing animation of the controlling virtual object throwing a capture item at the virtual pet.
[0117] In some embodiments, before each capture operation in at least one capture operation, the controlling virtual object throws a capture item at the virtual pet once.
[0118] For example, during the execution of the first triggering operation, the main virtual object is not controlled to throw a capture item at the virtual pet. However, after the first triggering operation ends, when the main virtual object is controlled to perform a capture operation, it is controlled to throw a capture item at the virtual pet. For example, before performing the i-th capture operation in at least one capture operation, the main virtual object is controlled to throw the capture item consumed by the i-th capture operation at the virtual pet.
[0119] The technical solution provided in this application, on the one hand, controls the main virtual object to throw capture items at the virtual pet during the execution of the first trigger operation, making the execution process of the first trigger operation no longer monotonous, but combined with the throwing animation on the user interface, enriching the display elements of the screen. On the other hand, controlling the main virtual object to throw capture items before each capture operation in at least one capture operation, combining the throwing animation with each capture operation, can give users a more vivid capture experience.
[0120] In some embodiments, the master virtual object adopts a different posture each time it throws a capture item.
[0121] For example, the throwing posture of the master virtual object differs during different throws of the capture item. For example, the user can know the current number of capture operations by observing the throwing posture of the master virtual object. The posture of the master virtual object throwing the capture item each time includes at least one of the following: throwing the capture item with one hand while sideways, throwing the capture item with both heads raised overhead, or kicking the capture item.
[0122] For example, the master virtual object is shown throwing capture props in different postures, each posture corresponding to a different number of capture operations, or a different number of capture operations already performed. As shown in sub-figures a, b, and c of Figure 12, the master virtual object throws capture props in different postures.
[0123] The technical solution provided in this application enriches the display elements of the screen by using different throwing postures for capturing props. For example, a relaxed one-handed throwing posture is used for the first throw, while a forceful two-handed throwing posture is used for the fifth throw. The subtle differences in different postures (such as the amplitude of arm swing and changes in the body's center of gravity) can create a richer sense of dynamics in the screen, transforming the continuous capture process from mechanical repetition into a rhythmic visual presentation and enhancing the user's immersive experience. On the other hand, different postures indicate different capture operations, which also improves information display efficiency and provides users with a more diverse capture experience. That is, binding posture differences with the number of captures (such as a specific posture corresponding to a fixed number of captures) allows users to visually judge the current capture progress without having to check the number of captures. For example, seeing the main virtual object make a high-amplitude throwing posture can quickly identify that it has entered a high-capture stage. This posture-as-information transmission method integrates visual perception and information acquisition, reduces the user's information retrieval cost, and improves the efficiency of operational decision-making. Furthermore, differentiated poses can imbue the capture process with emotional and strategic connections. For example, when capturing rare virtual pets, a more ritualistic special throwing pose can be used, which not only visually reinforces the specialness of rare targets but also gives users a stronger sense of participation and anticipation during the operation. Ultimately, on the basis of enriching visual elements and improving information efficiency, the capture gameplay is further enhanced in terms of fun and memorability through visual storytelling.
[0124] The following section explains how to obtain and return capture items.
[0125] In some embodiments, if a virtual pet is successfully captured and the number of capture attempts generated by the first triggering operation has not been exhausted, the capture items corresponding to the unused capture attempts are returned to the inventory of the main virtual object. The capture items thrown by the main virtual object are obtained from the inventory of the main virtual object.
[0126] For example, the number of capture operations generated by the first triggering operation corresponds to multiple capture items. Specifically, the method for determining the total number of capture items consumed by the number of capture operations is explained in the above embodiments, and will not be repeated here.
[0127] For example, the number of capture operations generated by the first trigger operation is K, and the total number of capture items required is L, where L is an integer greater than or equal to K.
[0128] If the virtual pet is successfully captured on the nth capture operation (where n is an integer less than K), then the number of capture operations generated by the first trigger operation has not been exhausted. If the first n capture operations consumed a total of M capture items (where M is less than L), then the capture items corresponding to the remaining (Kn) capture operations are returned to the main virtual object's inventory. The remaining (LM) unused capture items are also returned to the main virtual object's inventory.
[0129] For example, if the number of capture operations generated by the first triggering operation is K, and the total number of L capture items required is obtained from the inventory of the main virtual object, then when returning the items, they will also be returned to the inventory of the main virtual object. As shown in Figure 16, by returning the capture items corresponding to the unused capture attempts to the inventory of the main virtual object, the number of capture items changes from 42 to 89.
[0130] The technical solution provided in this application returns the capture items corresponding to unused capture attempts to the inventory of the main virtual object, avoiding waste of capture items and enabling flexible application of capture items. Furthermore, in continuous capture scenarios, if the items corresponding to unused attempts are directly consumed and cannot be returned, users may be forced to reduce their capture attempts due to concerns about wasting items, or experience negative experiences after a successful capture because remaining items cannot be recovered, limiting the flexibility of operational strategies. The item return mechanism completely eliminates this concern, allowing users to confidently choose a higher number of consecutive capture attempts (such as a preset 10 captures) without worrying about wasting the remaining 9 capture attempts after a successful capture. This allows for more flexible adjustment of strategies based on the rarity and capture difficulty of the virtual pet (e.g., directly using the maximum number of capture attempts for high-difficulty targets without reserving items). Meanwhile, this approach enhances the controllability of item resources, meaning returned items can be reused in other capture scenarios, preventing resources from being idle during a single capture and improving overall item utilization. This is especially beneficial when item acquisition incurs costs (such as requiring quest unlocks or in-game currency exchange), reducing the pressure on users to acquire resources and extending the item's lifespan. Furthermore, the item return system enhances user trust through a closed-loop process of operation-result-resource feedback, allowing users to perceive reasonable resource management and avoiding concerns about resource depletion due to opaque rules. Ultimately, by preventing waste and increasing flexibility, it further enhances user acceptance and exploration of the capture gameplay through a sense of resource security.
[0131] The following section introduces the flexible selection of capture tools.
[0132] In some embodiments, in response to a first triggering operation, at least one virtual prop is displayed, each virtual prop employing a different capture method to capture a virtual pet.
[0133] For example, the first triggering operation is a press operation. In response to a press operation on the capture control, marking information corresponding to at least one virtual item is displayed, with different marking information corresponding to different virtual items. These at least one virtual item are all used to capture virtual pets, and different virtual items capture virtual pets in different ways, such as by binding, stunning, or using traps, etc.
[0134] In some embodiments, in response to a selection operation for a first virtual item among at least one virtual item, the first virtual item is determined as the capture item consumed by the capture operation, wherein the selection operation is a sliding operation that starts from the trigger position of the first trigger operation and ends at the position of the first virtual item.
[0135] In some embodiments, in response to a selection operation of the tag information corresponding to a first virtual item among at least one virtual item, the first virtual item is determined as the capture item consumed by the capture operation.
[0136] For example, after selecting the marker information corresponding to the first virtual item, you can slide back to the capture control and maintain the previous continuous press state without interrupting the first trigger operation. It is understood that the capture item to be consumed is also selected during the execution of the first trigger operation.
[0137] The technical solution provided in this application allows users to choose the capture items consumed during the first trigger operation, demonstrating the flexibility and diversity of item selection. This also avoids interrupting the first trigger operation, eliminating extra steps and improving operational efficiency. Furthermore, considering that if item selection needs to be completed before the first trigger operation, users facing unexpected scenarios (such as discovering the target is more sensitive to a specific item during capture) would need to interrupt the current continuous capture process and re-enter the item selection interface, increasing operational steps and potentially causing missed capture opportunities; supporting dynamic selection of capture items during the first trigger operation allows users to flexibly switch item types (such as switching to rarer items with higher success rates) based on real-time capture feedback (such as previous failures with ordinary items) without interrupting the continuous capture rhythm, achieving efficient interaction with uninterrupted operation and adaptable strategies. Meanwhile, this approach gives item selection greater scene adaptability. Users don't need to predict the capture difficulty in advance; they can adjust item combinations in real time during continuous capture based on the target's performance (such as the intensity of the virtual pet's struggle and escape probability indicators). This avoids low capture efficiency caused by choosing the wrong items in the early stages. In addition, dynamic item selection enhances the user's sense of control. Compared to the passive consumption of fixed items, users can actively switch items to control the capture process. Especially when multiple items have their own advantages (such as item A having low consumption and item B having a high success rate), it allows for a more precise balance between resource consumption and capture effect. Ultimately, while ensuring operational efficiency, the increased strategic freedom makes the capture process more personalized and controllable, avoiding the limitations of using a single item.
[0138] The following describes the continuous capture process, including at least one of the following steps S1 to S3 (not shown in the figure).
[0139] Step S1: For the i-th capture operation in at least one capture operation, control the main virtual object to perform the i-th capture operation on the virtual pet, where i is a positive integer.
[0140] For example, starting from the first capture operation, it is determined whether each capture operation successfully captures the virtual pet. If the virtual pet is not successfully captured, the next capture operation continues. If the virtual pet is successfully captured, the capture operation stops.
[0141] Step S2: If the virtual pet is not successfully captured in the i-th capture operation, execute the (i+1)-th capture operation in at least one capture operation until the number of capture operations generated by the first trigger operation is exhausted.
[0142] For example, if the last capture operation still fails to capture the virtual pet, it is assumed that the capture operation triggered by the first trigger operation has exhausted its attempts and also failed to capture the virtual pet.
[0143] Step S3: If the virtual pet is successfully captured in the i-th capture operation, no further capture operations will be performed, and the virtual pet will become the pet owned by the main virtual object.
[0144] For example, if the virtual pet is successfully captured in the i-th capture operation, a success capture animation is displayed. This success capture animation informs the user that the virtual pet has been successfully captured. As shown in Figure 15, if the virtual pet is successfully captured in the i-th capture operation after consuming 1500 capture items, a success capture animation 1510 is displayed.
[0145] For example, after a virtual pet becomes the pet owned by a controlling virtual object, the controlling virtual object (or user account) can control the virtual pet, such as controlling its movement, releasing skills, performing tasks, etc. Once a virtual pet becomes the pet owned by a controlling virtual object, it will always be located near the controlling virtual object.
[0146] The technical solution provided in this application sequentially determines whether each capture operation successfully captures a virtual pet. If the virtual pet is successfully captured, subsequent captures are not performed. If the virtual pet is not successfully captured, the next capture operation is performed. This reflects the capture pattern of multiple consecutive capture operations, which is beneficial for achieving multiple consecutive captures while avoiding the waste of capture operations.
[0147] Please refer to Figure 5, which shows a flowchart of the virtual object control method provided in this application embodiment. The executing entity of each step of this method can be the terminal device 10 in the computer system shown in Figure 1, such as the client of the aforementioned target application. In the following method embodiments, for ease of description, only the executing entity of each step will be referred to as the "client". This method may include at least one of the following steps (510-550):
[0148] Step 510: Display the virtual environment, which includes the main virtual object and the virtual pet.
[0149] The following section, in conjunction with steps 520 and 530, explains that a capture operation needs to be triggered before triggering multiple consecutive captures.
[0150] Step 520: Receive a second trigger operation for the capture control, the second trigger operation being used to generate a capture operation for the virtual pet.
[0151] In some embodiments, the second triggering operation is an operation on the capture control, such as a press operation, a click operation, etc.
[0152] Step 530: In response to the second trigger operation, control the main virtual object to perform a capture operation on the virtual pet.
[0153] In some embodiments, after the second triggering operation ends, the main virtual object is controlled to perform a capture operation on the virtual pet. For example, this capture operation also consumes capture items. This capture operation is the same as one of the multiple capture operations described above, and the probability of successfully capturing the virtual pet in this single capture operation is less than 1.
[0154] The technical solution provided in this application, before triggering multiple consecutive capture operations, first triggers a capture operation, which then leads to multiple consecutive capture operations. This enriches the forms of capturing virtual pets and reflects the diversity and flexibility of capturing virtual pets. Moreover, the progressive approach of single trigger → consecutive trigger provides users with a natural operational buffer. The first capture can serve as a trial-and-error and perception stage, allowing users to intuitively understand the current capture difficulty of the virtual pet (such as success probability and reaction to items) and the feedback effect of a single operation (such as throwing animation and failure prompts), thereby determining whether to initiate subsequent consecutive captures and avoiding the risks of blindly starting the continuous mode. At the same time, this approach conforms to users' operational cognitive habits. The progression from single attempt to batch execution simulates the decision-making logic of testing before investing in reality, reducing the learning threshold of the continuous capture function and eliminating the need to directly understand complex continuous operation rules. In addition, the first capture can also serve as a process connector. If the first capture is successful, the process can be ended directly, avoiding resource redundancy caused by continuous operation. If the first capture fails, the user can adjust the strategy based on the failure feedback (such as prompts to need enhancement items) and then start continuous capture. This changes the capture behavior from passive execution to precise operation based on active judgment. Ultimately, by enriching the capture forms and improving the smoothness of operation transitions and the controllability of decision-making, the user's sense of security and the smoothness of the experience are further enhanced.
[0155] In some embodiments, step 530 includes at least one of steps 531 to 534 (not shown in the figures).
[0156] Step 531, in response to a press operation on the capture control, display the crosshair of the capture item consumed in one capture operation.
[0157] As shown in Figure 6, in response to a press operation on the capture control 610, the crosshair 620 of the capture item consumed in one capture operation is displayed.
[0158] The crosshair here refers to the aiming reticle of the capture tool, which is used to indicate the position to be aimed at when throwing the capture tool.
[0159] Step 532: In response to a drag operation on the capture control, the position of the crosshair changes. The drag operation is an operation that starts from the pressing position of the press operation, and the position of the crosshair is related to the real-time position of the drag operation.
[0160] For example, dragging the capture control can change the aiming reticle of the capture tool, thus changing the aiming position of the capture tool.
[0161] Step 533: If the crosshair hits the virtual pet, display the first capture probability of the virtual pet. The first capture probability is the probability of successfully capturing the virtual pet in one capture operation.
[0162] As shown in Figure 6, when the crosshair hits the virtual pet, the first capture probability for the virtual pet is displayed as 630.
[0163] For example, the probability of capturing the virtual pet varies depending on where the crosshair hits. For instance, the probability of capturing the virtual pet when the crosshair hits its arm is lower than the probability of capturing it when the crosshair hits its head.
[0164] For example, the probability of capturing a virtual object varies depending on which virtual object the crosshair hits. The probability of capturing a virtual object is 0 when the crosshair hits an uncapable virtual object. Similarly, the probability of capturing different captable virtual pets varies depending on which virtual pet the crosshair hits.
[0165] Step 534: In response to the end of the drag operation, control the main virtual object to throw the capture item consumed by one capture operation at the virtual pet, and capture the virtual pet with the first capture probability.
[0166] For example, the dragging operation is considered complete when the finger performing the dragging operation leaves the capture control. The main virtual object is controlled to throw the capture item consumed in one capture operation towards the crosshair position to capture the virtual pet with a first capture probability.
[0167] As shown in Figure 7, the main virtual object is controlled to throw the capture item 710 consumed in one capture operation to the virtual pet, and the animation 720 of the capture item capturing the virtual pet is displayed.
[0168] For example, if the capture operation fails to capture the virtual pet, subsequent capture operations are performed multiple times consecutively. If the capture operation successfully captures the virtual pet, subsequent capture operations are not performed multiple times consecutively.
[0169] In this embodiment, if the capture operation fails to capture the virtual pet, the first capture probability remains unchanged during at least one subsequent capture operation. By consistently aiming at the virtual pet during these subsequent capture operations, manual aiming is eliminated, which improves the hit rate.
[0170] The technical solution provided in this application first uses a single capture operation to lead to multiple subsequent captures. This allows for a single aiming action within a single capture operation, eliminating the need for repeated aiming in subsequent captures. Subsequent captures directly utilize this aiming result, eliminating the need for manual calibration by the user. This automatic capture operation avoids the redundancy caused by multiple aiming actions and ensures that subsequent captures consistently and accurately target the virtual pet, reducing invalid captures due to aiming errors. This simplifies the operation and improves capture efficiency. Furthermore, by maintaining a constant initial capture probability in subsequent captures, users do not need to worry about probability fluctuations after the first capture. They can predict the capture result based on the initial aiming state and fixed probability, further reducing decision-making interference. For example, after confirming correct aiming and the expected probability through the first capture, users can confidently trigger continuous captures without needing to adjust aiming or judge probability during the process, achieving a dual guarantee of simplified operation and controllable results. Furthermore, this method of triggering a continuous process with a single trigger makes the capture process smoother and avoids rhythm breaks caused by multiple independent operations. Especially in virtual pet movement scenarios, a single aim can lock onto the target and continuously capture it, reducing aiming failures caused by target movement. Ultimately, by simplifying steps and improving efficiency, the dual support of aiming stability and probabilistic stability further enhances users' confidence and experience in successfully capturing the target.
[0171] The following is an introduction to duration indication information.
[0172] In some embodiments, after step 530, duration indication information is displayed, which indicates the remaining duration for receiving the first trigger operation.
[0173] For example, after the above-mentioned capture operation begins, a duration indicator is displayed. This duration indicator can be in the form of a progress bar countdown, showing the remaining time for receiving the first trigger operation. For example, this duration indicator initially indicates a preset duration, such as 10 seconds. As time passes, the remaining time indicated by the duration indicator decreases. As shown in Figure 8, the progress bar 810 continuously decreases to progress bar 820, and the indicated remaining time also continuously decreases. As shown in Figure 8, the number of capture operations decreases from 830 to 1.
[0174] In some embodiments, step 540 can only be performed if the duration indication information indicates that the remaining duration is greater than a first value.
[0175] For example, step 540 can only be executed if the duration indicator shows that the remaining duration is greater than a first value. For example, if the first value is 0, step 540 can only be executed if the progress bar indicates that the remaining duration is greater than 0. Conversely, if the progress bar indicates that the remaining duration is 0, step 540 cannot be executed, that is, multiple consecutive capture operations cannot be triggered.
[0176] The technical solution provided in this application does not trigger continuous capture operations at any time, but rather at specific triggering times. The first trigger operation is only received when the remaining duration indicates that the duration is greater than a first value, thus triggering continuous capture operations. This application provides a triggering method for continuous capture operations, which helps enrich human-computer interaction and improve the user's capture experience.
[0177] Step 540: Receive the first trigger operation of the capture control for the virtual pet. The first trigger operation is used to generate multiple consecutive capture operations for the virtual pet. The probability of successfully capturing the virtual pet in each capture operation is less than 1.
[0178] The technical solution provided in this application sets the triggering time through a duration threshold, ensuring that continuous capture can only be initiated within a valid window period. For example, triggering is only enabled when the remaining duration of the capture window is sufficient to support at least two consecutive captures (greater than a first value). This avoids the ineffective waste of time when a user initiates continuous capture with only one second remaining, only to complete one operation due to insufficient time, thus ensuring the effectiveness of the operation. Simultaneously, this triggering method enhances the guidance of human-computer interaction. The binding of duration indication information with triggering permissions intuitively prompts the user whether the current scenario is suitable for continuous capture, reducing misoperations caused by information gaps. Users no longer need to manually judge the window length; reasonable triggering times are pre-selected through rules, reducing operational decision-making costs. Furthermore, this method makes the capture process more rhythmic. Users need to judge the start time based on the duration prompt, rather than triggering randomly. This observation-judgment-trigger interaction logic transforms continuous capture from a disordered operation into a strategic timing selection, enriching the interaction form and making the capture experience more logical and controllable through improved scenario matching. This avoids operational chaos caused by triggering at any time, further optimizing the overall smoothness of the interaction.
[0179] The following describes how to refresh the duration indicator information.
[0180] In some embodiments, in response to a first triggering operation, if the number of capture operations increases, the duration indication information is updated with a preset duration, which is the maximum value of the remaining duration.
[0181] For example, during the execution of the first trigger operation, if the number of capture operations increases, the duration indicator information is updated with a preset duration, which is the maximum remaining duration. For example, if the number of capture operations displayed in real-time corresponding to the first trigger operation changes from 2 to 3, the duration indicator information is refreshed with the preset duration at the same time the number changes to 3. If the number of capture operations displayed in real-time corresponding to the first trigger operation changes from 2 to 3, the remaining duration indicated by the duration indicator information is refreshed to the maximum remaining duration of 10 seconds. As shown in Figures 10 and 11, when the number of capture operations changes from 18 to 19, the remaining duration indicated by the duration indicator information (progress bar 1100) is refreshed.
[0182] For example, a third trigger operation is allowed to be received if the remaining duration indicated by the updated duration indication information is greater than a first value. The third trigger operation is a different trigger operation from the first trigger operation, which is used to generate multiple consecutive capture operations for the virtual pet.
[0183] The technical solution provided in this application refreshes the duration indication information synchronously with a preset maximum duration. This provides sufficient time buffer for new operations while the user adjusts the number of attempts. For example, when the number of attempts increases from 2 to 3, the remaining duration is immediately reset to the maximum value, ensuring that all three captures can be completed within the effective window period, avoiding process interruption due to insufficient duration. Simultaneously, this refresh method strengthens the real-time correlation between operation and feedback. The user's action of adjusting the number of attempts and the visual feedback of duration reset occur simultaneously, allowing for an intuitive perception that the increase in attempts is accompanied by sufficient duration, eliminating the need for additional confirmation of whether the duration is sufficient and reducing decision-making hesitation. Especially during continuous capture, users can flexibly increase the number of attempts based on real-time capture results (such as the first two failures), while the duration refresh mechanism eliminates concerns about insufficient time when increasing the number of attempts, allowing for more decisive strategy adjustments.
[0184] The following describes the timing for triggering continuous capture.
[0185] In some embodiments, in response to the end of the first triggering operation, if the duration indication information indicates that the remaining duration is less than or equal to a first value, the step of controlling the master virtual object to perform at least one capture operation on the virtual pet is executed.
[0186] For example, after the first trigger operation ends, if the duration indicator shows that the remaining duration is greater than the first value, the process continues to wait until the duration indicator shows that the remaining duration is less than or equal to the first value before triggering step 550. During the waiting process, the first trigger operation has ended, and the number of capture operations generated by the first trigger operation is displayed. Of course, during the waiting process, a third trigger operation from the needle capture control can also be received. The third trigger operation is similar to the first trigger operation and will not be described in detail.
[0187] For example, based on the third triggering operation, the number of capture operations generated by the third triggering operation is determined. After the third triggering operation ends, if the duration indicator information indicates that the remaining duration is less than or equal to a first value, then subsequent consecutive capture operations are triggered. In this case, the number of subsequent consecutive capture operations is the sum of the number of capture operations generated by the first triggering operation and the number of capture operations generated by the third triggering operation.
[0188] For example, after the third triggering operation ends, if the duration indicator shows that the remaining duration is greater than the first value, the process continues to wait until the duration indicator shows that the remaining duration is less than or equal to the first value. Of course, during this waiting period, the user can execute the fourth triggering operation, the fifth triggering operation, and so on. The fourth and fifth triggering operations are similar to the third triggering operation and will not be described in detail.
[0189] The technical solution provided in this application does not immediately begin continuous capture after the first trigger operation ends. Instead, it waits for the duration indicator information to show that the remaining duration is less than or equal to a first value before starting continuous capture. This method provides the user with a certain reaction time. If the number of capture operations is insufficient, the trigger operation on the capture control can be executed again to increase the number of capture operations. Of course, if the increase in the number of capture operations is interrupted due to accidentally releasing the control during the execution of the first trigger operation, a second trigger operation can be executed to continue increasing the number of capture operations. This demonstrates the flexibility in determining the number of capture operations. Furthermore, by refreshing the duration indicator information, a buffer time is provided to re-execute the trigger operation at any subsequent interruption, thereby giving the user a better capture experience.
[0190] Step 550: In response to the first trigger operation, control the main virtual object to perform at least one capture operation on the virtual pet until the virtual pet is successfully captured or the number of capture operations generated by the first trigger operation is exhausted.
[0191] The following describes when to send a request to the server.
[0192] In some embodiments, in response to the end of the first triggering operation, an acquisition request is sent, the acquisition request including operation information of the first triggering operation, and the acquisition request is used to request the acquisition of the number of capture operations generated by the first triggering operation.
[0193] For example, in response to the end of the first triggering operation, the terminal device sends an acquisition request to the server. The acquisition request includes operation information of the first triggering operation and is used to request the acquisition of the number of capture operations generated by the first triggering operation.
[0194] For example, the operation information of the first triggering operation includes at least one of the following: the duration of continuous pressing, the operation location, and the operation force of the first triggering operation. The server obtains the acquisition request and determines the number of capture operations generated by the first triggering operation based on at least one of the duration of continuous pressing, the operation location, and the operation force carried in the request. The server sends the number of capture operations to the terminal device.
[0195] Compared to related technologies, where each capture operation involves an information exchange between the terminal device and the server, the technical solution provided in this application only requires one interaction after the first trigger operation ends to determine the number of capture operations generated by the first trigger. This helps reduce the number of interactions and the server load.
[0196] In some embodiments, after performing at least one capture operation, until the number of capture operations generated by the first trigger operation is exhausted, the terminal device sends a capture information to the server. This capture information is used to indicate whether the virtual pet has been successfully captured, as well as the status of the virtual pet, the number of capture operations, etc.
[0197] For example, in related technologies, each capture operation requires the terminal device to send capture information to the server once. This application, through continuous capture, combines the number of transmissions, reducing multiple transmissions into a single transmission, and also reducing the server load.
[0198] In some embodiments, as shown in FIG17, it is a schematic diagram of the virtual pet capture process provided in the embodiments of this application, which includes at least one of the following steps P1 to 10 (not shown in the figure).
[0199] Step P1: The player presses the capture button (i.e., the capture control).
[0200] The client puts the player's camera into aiming mode, at which point a crosshair will appear in the center of the screen. Players can move and adjust the crosshair and camera focus by dragging the capture item button.
[0201] In step P2, the player moves the crosshair onto the target that can be captured.
[0202] The client determines the type of target the crosshair is currently pointing at by emitting a ray from the crosshair, such as terrain, units, buildings, etc.
[0203] Step P3: Pre-display the capture probability at the target location.
[0204] If the crosshair is aimed at a target, the client reads the target's capture success rate configuration and displays the probability of successful capture at the target location through the UI. At this point, the player will clearly understand the probability information and can freely decide whether to proceed with the next capture operation.
[0205] Step P4: The player releases the button, and the capture operation begins.
[0206] The client initiates the protocol first, and then the server returns the captured result to the client.
[0207] In step P5, should the player press and hold the capture button again?
[0208] True: Yes, enter continuous capture process. False: No, enter single capture process.
[0209] In step P6, the player consumes a capture item to refresh the capture countdown timer and increase the consecutive capture count.
[0210] The client reads the time the player holds down the capture button and reports the data to the server. The server then uses this data to deduct items and increase the player's consecutive capture count before sending it back to the client.
[0211] Step P7: Should the player continue to hold down the capture button?
[0212] True: Yes, return to step P6. False: No, the system (i.e., the terminal device or server) begins to evaluate the results of continuous capture.
[0213] In step P8, the system sequentially reduces the count to determine the capture result.
[0214] During the system's judgment process, the count will be decremented sequentially, and a capture result judgment will be performed once. This count can be understood as the remaining number of capture operations.
[0215] In step P9, if the capture fails, the count is reduced and the next judgment is performed; if the judgment is successful, the counting stops and the continuous capture process ends; if the count decreases to 0, the judgment stops and the continuous capture process also ends.
[0216] In step P10, after a successful determination, the system will return the unused capture items to the player and capture the target as the player's pet.
[0217] The goal here is the virtual pet mentioned above.
[0218] The technical solution provided in this application, by allowing players to continuously press buttons or the mouse to capture pets, brings several beneficial effects. First, it improves the convenience of operation and simplifies repetitive and tedious action processes. Second, this innovative approach enriches the gameplay experience, increasing the game's fun and appeal through different action expressions and feedback mechanisms. Simultaneously, continuous capture significantly improves capture efficiency, enabling players to achieve game objectives faster, optimizing resource utilization, and reducing server load. Furthermore, it provides game developers with more design space, promotes social interaction, thereby increasing user stickiness and enhancing brand image. Overall, this application not only improves the player's gaming experience but also brings new opportunities and challenges to the development of the gaming industry.
[0219] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.
[0220] Please refer to Figure 18, which shows a block diagram of a control device for a virtual object provided in an embodiment of this application. This device has the function of implementing the aforementioned control method for the virtual object. This function can be implemented in hardware or by hardware executing corresponding software. The device can be the terminal device described above, or it can be installed within a terminal device. As shown in Figure 18, the device 1800 may include: a display module 1810, a receiving module 1820, and a control module 1830.
[0221] Display module 1810 is configured to display a virtual environment, which includes a main virtual object and a virtual pet.
[0222] The receiving module 1820 is configured to receive a first trigger operation of the capture control for the virtual pet. The first trigger operation is used to generate multiple consecutive capture operations for the virtual pet, and the probability of successfully capturing the virtual pet in each capture operation is less than 1.
[0223] The control module 1830 is configured to respond to the first trigger operation by controlling the main virtual object to perform at least one capture operation on the virtual pet until the virtual pet is successfully captured or the number of capture operations generated by the first trigger operation is exhausted.
[0224] In some embodiments, the first triggering operation is a continuous pressing operation.
[0225] In some embodiments, the display module 1810 is configured to display the number of capture operations generated by the first trigger operation, the number of capture operations being determined based on the duration of the continuous press operation.
[0226] In some embodiments, the control module 1830 is configured to continuously increase the number of capture operations during the execution of the first triggering operation.
[0227] In some embodiments, the control module 1830 is configured to consume one capture operation count for each capture operation performed.
[0228] In some embodiments, the number of capture items consumed in each capture operation of the at least one capture operation is the same; or, the number of capture items consumed in the i-th capture operation of the at least one capture operation is positively correlated with the value of i, where i is a positive integer; the number of capture items consumed in each capture operation of the at least one capture operation is positively correlated with the rarity of the virtual pet; wherein, the capture items are used to capture the virtual pet.
[0229] In some embodiments, the control module 1830 is configured to, during the execution of the first triggering operation, if the number of capture operations increases, control the main virtual object to throw the capture item at the virtual pet once.
[0230] In some embodiments, the control module 1830 is configured to control the master virtual object to throw the capture item at the virtual pet once before each capture operation in the at least one capture operation.
[0231] In some embodiments, the master virtual object throws the capture item in a different posture each time.
[0232] In some embodiments, the control module 1830 is configured to return the capture items corresponding to the unused capture counts to the inventory of the main virtual object if the virtual pet is successfully captured and the number of capture operations generated by the first triggering operation has not been exhausted. The capture items thrown by the main virtual object are obtained from the inventory of the main virtual object.
[0233] In some embodiments, the display module 1810 is configured to display at least one virtual item in response to the first triggering operation, each virtual item employing a different capture method to capture the virtual pet.
[0234] In some embodiments, the control module 1830 is configured to determine the first virtual prop as the capture prop consumed by the capture operation in response to a selection operation for a first virtual prop among the at least one virtual prop, wherein the selection operation is a sliding operation that starts from the trigger position of the first trigger operation and ends at the position of the first virtual prop.
[0235] In some embodiments, the control module 1830 is configured to, for the i-th capture operation in the at least one capture operation, control the master virtual object to perform the i-th capture operation on the virtual pet, where i is a positive integer; if the i-th capture operation fails to capture the virtual pet, perform the (i+1)-th capture operation in the at least one capture operation until the number of capture operations generated by the first triggering operation is exhausted; if the i-th capture operation successfully captures the virtual pet, no further capture operations are performed, and the virtual pet is controlled to become a pet owned by the master virtual object.
[0236] In some embodiments, the receiving module 1820 is configured to receive a second trigger operation for the capture control, the second trigger operation being used to generate a capture operation for the virtual pet.
[0237] In some embodiments, the control module 1830 is configured to, in response to the second triggering operation, control the master virtual object to perform a capture operation on the virtual pet; and after starting to perform a capture operation, execute the step of receiving the first triggering operation for the capture control of the virtual pet.
[0238] In some embodiments, the display module 1810 is configured to display duration indication information, which is used to indicate the remaining duration for receiving the first trigger operation.
[0239] In some embodiments, the receiving module 1820 is configured to receive the first trigger operation when the duration indication information indicates that the remaining duration is greater than a first value.
[0240] In some embodiments, the control module 1830 is configured to, in response to the first trigger operation, update the duration indication information for a preset duration if the number of capture operations increases, wherein the preset duration is the maximum value of the remaining duration; wherein, if the remaining duration indicated by the updated duration indication information is greater than the first value, a third trigger operation is allowed to be received, wherein the third trigger operation is another trigger operation different from the first trigger operation for generating multiple consecutive capture operations for the virtual pet.
[0241] In some embodiments, the control module 1830 is configured to, in response to the end of the first triggering operation, execute the step of controlling the master virtual object to perform at least one capture operation on the virtual pet when the duration indication information indicates that the remaining duration is less than or equal to the first value.
[0242] In some embodiments, the control module 1830 is configured to, in response to a press operation on the capture control, display the crosshair of the capture item consumed in the capture operation; in response to a drag operation on the capture control, control the position of the crosshair to change, the drag operation being an operation starting from the press position of the press operation, the position of the crosshair being related to the real-time position of the drag operation; if the crosshair hits the virtual pet, display a first capture probability for the virtual pet, the first capture probability being the probability of successfully capturing the virtual pet in the capture operation; and in response to the end of the drag operation, control the main virtual object to throw the capture item consumed in the capture operation at the virtual pet to capture the virtual pet with the first capture probability.
[0243] In some embodiments, the control module 1830 is configured to send an acquisition request in response to the end of the first triggering operation. The acquisition request includes operation information of the first triggering operation and is used to request the acquisition of the number of capture operations generated by the first triggering operation.
[0244] The technical solution provided in this application addresses the problem of low capture efficiency caused by the need to perform an operation on the capture control for each capture in related technologies. By performing an operation on the capture control in a single step (i.e., the first trigger operation), multiple consecutive capture operations on the virtual pet can be generated. This application simplifies the operation steps and improves the capture efficiency of virtual pets by eliminating the need for multiple operations on the capture control.
[0245] It should be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above functional modules when implementing its functions. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.
[0246] Please refer to Figure 19, which shows a structural block diagram of a terminal device 1900 provided in an embodiment of this application. This terminal device 1900 can be a terminal device in the computer system shown in Figure 1, used to implement the virtual object control method provided in the above embodiments. Specifically:
[0247] Typically, terminal device 1900 includes a processor 1901 and a memory 1902.
[0248] Processor 1901 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 1901 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field Programmable Gate Array), and PLA (Programmable Logic Array). Processor 1901 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 1901 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the screen. In some embodiments, processor 1901 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.
[0249] The memory 1902 may include one or more computer-readable storage media, which may be non-transitory. The memory 1902 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in the memory 1902 are used to store a computer program configured to be executed by one or more processors to implement the control method for the virtual object described above.
[0250] In some embodiments, the terminal device 1900 may also optionally include a peripheral device interface 1903 and at least one peripheral device. The processor 1901, memory 1902, and peripheral device interface 1903 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 1903 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of a radio frequency circuit 1904, a display screen 1905, an audio circuit 1907, and a power supply 1908.
[0251] Those skilled in the art will understand that the structure shown in FIG19 does not constitute a limitation on the terminal device 1900, and may include more or fewer components than shown, or combine certain components, or use different component arrangements.
[0252] In an exemplary embodiment, a computer-readable storage medium is also provided, wherein a computer program is stored therein, which, when executed by a processor, implements a method for controlling a virtual object.
[0253] In some embodiments, the computer-readable storage medium may include ROM (Read-Only Memory), RAM (Random Access Memory), SSD (Solid State Drives), or optical disc, etc. The random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).
[0254] In an exemplary embodiment, a computer program product is also provided, the computer program product including a computer program stored in a computer-readable storage medium. A processor of a terminal device reads the computer program from the computer-readable storage medium, and the processor executes the computer program, causing the terminal device to perform the aforementioned virtual object control method.
[0255] It should be noted that this application may display prompt interfaces, pop-ups, or output voice prompts before and during the collection of user data. These prompt interfaces, pop-ups, or voice prompts are used to inform users that their data is being collected. This ensures that the application only begins the steps for collecting user data after receiving confirmation from the user regarding the prompt interface or pop-up; otherwise (i.e., without receiving confirmation from the user), the steps for collecting user data end, meaning no user data is collected. In other words, all user data collected by this application is processed strictly in accordance with the requirements of relevant national laws and regulations. The informed consent or separate consent of the data subject is obtained only with the user's consent and authorization. Subsequent data use and processing are conducted within the scope of laws, regulations, and the data subject's authorization, and the collection, use, and processing of relevant user data must comply with the relevant laws, regulations, and standards of the relevant countries and regions.
[0256] It should be understood that "multiple" as used herein refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. Furthermore, the step numbers described herein are merely illustrative of one possible execution order. In some other embodiments, the steps may not be executed in numerical order, such as two steps with different numbers being executed simultaneously, or two steps with different numbers being executed in the reverse order of the illustration. This application does not limit this.
[0257] The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.
Claims
1. A method for controlling a virtual object, wherein, The method is executed by a terminal device, and the method includes: Display a virtual environment, which includes a main virtual object and a virtual pet; A first trigger operation is received for the capture control of the virtual pet. The first trigger operation is used to generate multiple consecutive capture operations for the virtual pet, and the probability of successfully capturing the virtual pet in each capture operation is less than 1. In response to the first triggering operation, the master virtual object is controlled to perform at least one capture operation on the virtual pet until the virtual pet is successfully captured or the number of capture operations generated by the first triggering operation is exhausted.
2. The method according to claim 1, wherein, The first triggering operation is a continuous pressing operation, and the method further includes: The display shows the number of capture operations generated by the first trigger operation, the number of capture operations being determined based on the duration of the continuous press operation.
3. The method according to any one of claims 1 to 2, wherein, The method further includes at least one of the following: During the execution of the first triggering operation, the number of capture operations is continuously increased; Each capture operation consumes one capture operation count.
4. The method according to any one of claims 1 to 3, wherein, The number of capture items consumed in each capture operation in the at least one capture operation is the same; or, The number of capture items consumed in the i-th capture operation in the at least one capture operation is positively correlated with the value of i, where i is a positive integer; The number of capture items consumed in each capture operation in the at least one capture operation is positively correlated with the rarity of the virtual pet; The capturing tool is used to capture the virtual pet.
5. The method according to any one of claims 1 to 4, wherein, The method further includes: During the execution of the first triggering operation, if the number of capture operations increases, the main virtual object is controlled to throw the capture item at the virtual pet once; or, Before each capture operation in the at least one capture operation, the master virtual object is controlled to throw the capture item at the virtual pet once.
6. The method according to any one of claims 1 to 5, wherein, The main virtual object throws the capture item in a different posture each time.
7. The method according to claim 5 or 6, wherein, The method further includes: If the virtual pet is successfully captured and the number of capture attempts generated by the first triggering operation has not been exhausted, the capture items corresponding to the unused capture attempts are returned to the inventory of the main virtual object. The capture items thrown by the main virtual object are obtained from the inventory of the main virtual object.
8. The method according to any one of claims 4 to 7, wherein, The method further includes: In response to the first triggering operation, at least one virtual item is displayed, each virtual item using a different capture method to capture the virtual pet; In response to a selection operation for a first virtual item among the at least one virtual item, the first virtual item is identified as the capture item consumed by the capture operation, wherein the selection operation is a sliding operation that starts from the trigger position of the first trigger operation and ends at the position of the first virtual item.
9. The method according to any one of claims 1 to 8, wherein, The control of the master virtual object to perform at least one capture operation on the virtual pet includes: For the i-th capture operation in the at least one capture operation, control the main virtual object to perform the i-th capture operation on the virtual pet, where i is a positive integer; If the virtual pet is not successfully captured in the i-th capture operation, the (i+1)-th capture operation in the at least one capture operation is executed until the number of capture operations generated by the first triggering operation is exhausted; If the virtual pet is successfully captured in the i-th capture operation, no further capture operations will be performed, and the virtual pet will become the pet owned by the controlling virtual object.
10. The method according to any one of claims 1 to 9, wherein, The method further includes: Receive a second trigger operation for the capture control, the second trigger operation being used to generate a capture operation for the virtual pet; In response to the second triggering operation, the main virtual object is controlled to perform a capture operation on the virtual pet; After initiating a capture operation, the first trigger operation of the received capture control for the virtual pet is executed.
11. The method according to any one of claims 1 to 10, wherein, The method further includes: Display duration indication information, the duration indication information being used to indicate the remaining duration for receiving the first trigger operation; The first trigger operation for receiving the capture control for the virtual pet includes: If the duration indication information indicates that the remaining duration is greater than a first value, the first trigger operation is received.
12. The method according to any one of claims 1 to 11, wherein, The method further includes: In response to the first triggering operation, if the number of capture operations increases, the duration indication information is updated for a preset duration, where the preset duration is the maximum value of the remaining duration. Specifically, if the remaining duration indicated by the updated duration indication information is greater than the first value, a third trigger operation is allowed to be received. The third trigger operation is a different trigger operation from the first trigger operation, which is used to generate multiple consecutive capture operations for the virtual pet.
13. The method according to claim 11 or 12, wherein, The method further includes: In response to the end of the first triggering operation, if the duration indication information indicates that the remaining duration is less than or equal to the first value, the step of controlling the master virtual object to perform at least one capture operation on the virtual pet is executed.
14. The method according to any one of claims 10 to 13, wherein, The step of responding to the second triggering operation by controlling the main virtual object to perform a capture operation on the virtual pet includes: In response to a press operation on the capture control, the crosshair of the capture item consumed in the capture operation is displayed; In response to a drag operation on the capture control, the position of the crosshair is changed. The drag operation is an operation that starts from the pressing position of the pressing operation, and the position of the crosshair is related to the real-time position of the drag operation. When the crosshair hits the virtual pet, the first capture probability for the virtual pet is displayed, where the first capture probability is the probability that the virtual pet is successfully captured in a single capture operation. In response to the end of the drag operation, the main virtual object is controlled to throw the capture item consumed in the capture operation at the virtual pet, and the virtual pet is captured with the first capture probability.
15. The method according to any one of claims 1 to 14, wherein, The method further includes: In response to the end of the first triggering operation, an acquisition request is sent. The acquisition request includes the operation information of the first triggering operation and is used to request the acquisition of the number of capture operations generated by the first triggering operation.
16. A control device for a virtual object, the device comprising: The display module is configured to display a virtual environment, which includes a main virtual object and a virtual pet. The receiving module is configured to receive a first trigger operation of the capture control for the virtual pet, wherein the first trigger operation is used to generate multiple consecutive capture operations for the virtual pet, and the probability of successfully capturing the virtual pet in each capture operation is less than 1. The control module is configured to respond to the first trigger operation by controlling the main virtual object to perform at least one capture operation on the virtual pet until the virtual pet is successfully captured or the number of capture operations generated by the first trigger operation is exhausted.
17. A terminal device comprising a processor and a memory, the memory storing a computer program, the computer program being loaded and executed by the processor to implement the method for controlling a virtual object as described in any one of claims 1 to 15.
18. A computer-readable storage medium storing a computer program, the computer program being loaded and executed by a processor to implement the method for controlling a virtual object as described in any one of claims 1 to 15.
19. A computer program product comprising a computer program loaded and executed by a processor to implement the method for controlling a virtual object as described in any one of claims 1 to 15.
Citation Information
Patent Citations
Elf catching device, system and method
CN106621322A
Virtual object control method, virtual object control device, computer equipment and computer storage medium
CN107529442A
Virtual prop control method and device, storage medium and electronic device
CN111104021A
Virtual object interaction method and device, computer equipment and storage medium
CN116962835A
Capture information display method and device based on virtual world, equipment and medium
CN117618901A