Game operation method and device, mobile equipment and storage medium

Abstract

The invention discloses a game operation method and device, mobile equipment and a storage medium, and belongs to the technical field of games. The method is applied to the mobile device with a touch screen. The method comprises the steps of displaying a game interface of a game application program; in response to a received first input of a user to the game interface, determining an input signal type of the first input according to an input device of the first input; storing the input information of the first input into a target event data structure corresponding to the input signal type; identifying a user operation behavior corresponding to the first input based on information in the target event data structure; and executing player operation corresponding to the user operation behavior on the game interface. The flexibility of game operation can be improved.

Description

Technical Field

[0001] The present application belongs to the field of game technology, and in particular relates to a game operation method, device, mobile device and storage medium. Background Art

[0002] With the rapid development of technology, mobile devices, thanks to their exceptional portability, have become an indispensable tool in people's daily lives. To promote the widespread use of mobile devices in the entertainment field and enrich users' entertainment lives, more and more game manufacturers have begun to develop mobile devices that can run on mobile devices.

[0003] Currently, mobile devices with touch screens can support multiple game applications in various operation modes, such as controller operation mode and touchscreen operation mode. However, in related art, users can only interact with the game application through a single input device for each operation mode. For example, in controller operation mode, users can only interact with the game application through the controller; in touchscreen operation mode, users can only interact with the game application through the touchscreen, resulting in low game operation flexibility. Summary of the Invention

[0004] Embodiments of the present application provide a game operation method, apparatus, mobile device, and storage medium, which can improve the flexibility of game operation.

[0005] In a first aspect, an embodiment of the present application provides a game operation method, which is applied to a mobile device with a touch screen; the method includes: displaying a game interface of a game application; in response to receiving a first input from a user on the game interface, determining the input signal type of the first input according to the input device of the first input; storing the input information of the first input in a target event data structure corresponding to the input signal type; based on the information in the target event data structure, identifying the user operation behavior corresponding to the first input; and executing a player operation corresponding to the user operation behavior on the game interface.

[0006] In a second aspect, an embodiment of the present application provides a game operation device, which is applied to a mobile device with a touch screen; the device includes: a display module for displaying a game interface of a game application; a determination module for responding to a first input received from a user on the game interface, and determining the input signal type of the first input according to the input device of the first input; an operation module for storing the input information of the first input in a target event data structure corresponding to the input signal type; based on the information in the target event data structure, identifying the user operation behavior corresponding to the first input; and an execution module for executing a player operation corresponding to the user operation behavior on the game interface.

[0007] In a third aspect, an embodiment of the present application provides a mobile device, comprising a processor and a memory storing computer program instructions; the processor implements the game operation method according to the first aspect when executing the computer program instructions.

[0008] In a fourth aspect, an embodiment of the present application provides a computer storage medium, storing computer program instructions, which, when executed by a processor, implement the game operation method according to the first aspect.

[0009] In a fifth aspect, an embodiment of the present application provides a computer program product, instructions in the computer program product being executed by a processor of a mobile device, so that the mobile device executes the game operation method according to the first aspect.

[0010] In the embodiment of the present application, after receiving the first input of the game interface of the game application by the user through any input device, the mobile device can first determine the input signal type of the first input according to the input device of the first input. No matter what the input signal type of the first input is, the mobile device can identify the user operation behavior corresponding to the first input and execute the corresponding player operation in the game interface. Specifically, the mobile device can store the input information of the first input into the target event data structure corresponding to the input signal type thereof, and identify the user operation behavior corresponding thereto based on the information in the target event data structure through the target input module corresponding to the input signal type thereof. That is, the embodiment of the present application can store the input information of different input signal types separately through different event data structures, so that the input modules of different input signal types can call the corresponding event data structures for operation identification, so that the input processing of the mobile device for different input signal types is independent of each other and does not affect each other, thereby realizing the coexistence and compatibility of different types of inputs in the same operation mode, and further improving the flexibility of game operation. BRIEF DESCRIPTION OF DRAWINGS

[0011] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the embodiments of the present application will be briefly introduced. For those skilled in the art, other drawings can also be obtained without creative labor on the basis of these drawings.

[0012] Figure 1 is one of the flowcharts of the game operation method provided by the embodiments of the present application;

[0013] Figure 2 is a schematic diagram of the operation mode switching inquiry information provided by the embodiments of the present application;

[0014] Figure 3is a second flowchart of a game operation method provided by an embodiment of the present application;

[0015] Figure 4 is a structural schematic diagram of a game operation device provided by an embodiment of the present application;

[0016] Figure 5 is a structural schematic diagram of a mobile device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0017] The features and exemplary embodiments of various aspects of the present application will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are intended to explain the present application, but not to limit the present application. The present application can be implemented without some of the specific details described below. The following description of the embodiments is merely intended to provide a better understanding of the present application by showing examples of the present application.

[0018] It should be noted that, in this document, relational terms such as first and second and the like can be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without more limitations, an element defined by the phrase "comprising a... " does not exclude the existence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0019] The game operation method provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings and some embodiments and application scenarios.

[0020] The game operation method of the embodiments of the present application can be applied to a mobile device with a touch screen. In actual implementation, the method can be executed by the mobile device, or by a component of the mobile device, such as a processor, a chip, or a chip system of the mobile device, or by a logic module or software that implements all or part of the functions of the mobile device. In actual application, the mobile device can be a smart phone, a tablet computer, or the like.

[0021] Referring to Figure 1 , Figure 1 is a first flowchart of a game operation method provided by an embodiment of the present application.

[0022] like Figure 1 As shown, the game operation method of the embodiment of the present application may include but is not limited to the following steps:

[0023] Step 101: Display the game interface of the game application.

[0024] In response to the user's start input of the game application, the mobile device can display a game interface of the game application for the user to interact with the game interface.

[0025] Step 102: In response to receiving a first input from a user on a game interface, determine an input signal type of the first input according to an input device of the first input.

[0026] In a specific implementation, the user can interact with the game interface through various input devices supported by the mobile device and perform input on the game interface. After receiving the input performed by the user on the game interface, the mobile device can obtain the input device of the input and the input information of the input.

[0027] In the embodiment of the present application, the input devices supported by the mobile device may include, but are not limited to: a touch screen of the mobile device, a handle connected to the mobile device. The handle may be connected to the mobile device via a wired or wireless connection.

[0028] The signal types (also referred to as input signal types) of user inputs to the game interface using different input devices may be different. For example, the signal type of input using a gamepad may be referred to as gamepad input, while the signal type of input using a touch screen may be referred to as touch screen input.

[0029] In some embodiments, the game engine (Unreal Engine, UE) of the game application itself supports controller input and touch screen input in the input layer (InputInterface) of the mobile device's operating system. The AddActionBinding and AddTouchBinding methods are used in the BasePlayerController (BaseController) to bind controller input events and touch screen input events, thereby implementing the processing of controller and touch screen input.

[0030] In step 102, the first input may be any input performed by the user on the game interface through any input device. After receiving the first input, the mobile device may determine the input signal type of the first input based on the input device obtained for the first input.

[0031] Specifically, in response to the input device of the first input being a touch screen, it can be determined that the input signal type of the first input can be a touch screen input. In response to the input device of the first input being a handle, it can be determined that the input signal type of the first input is a handle input.

[0032] In step 103, the input information of the first input is stored into a target event data structure corresponding to the input signal type; and based on the information in the target event data structure, a user operation behavior corresponding to the first input is identified.

[0033] In the embodiments of the present application, the game application program can support multiple operation modes, and the main input device corresponding to different operation modes is different. The operation modes supported by the game application program can include a handle operation mode and a touch screen operation mode. It can be understood that the main input device corresponding to the touch screen operation mode is the touch screen of the mobile device, and the main input device corresponding to the handle operation mode is the handle connected to the mobile device.

[0034] In the embodiments of the present application, no matter what operation mode the game application program is in when receiving the first input, and what input signal type the first input is, the mobile device can identify the user operation behavior corresponding to the first input and perform the corresponding player operation in the game interface. That is, no matter what operation mode the game application program is in when receiving the first input, and what input signal type the first input is, the mobile device can respond to it and perform the corresponding response operation in the game interface.

[0035] In the implementation, the mobile device can set a corresponding event data structure (EventData) for different input signal types, and the IDs of different EventData are different, that is, the EventData corresponding to different input signal types are independent of each other.

[0036] The EventData corresponding to each input signal type can be used to store the input information of the input signal type. In this way, since the EventData corresponding to different input signal types are independent of each other, the input information of different input signal types will not affect each other, and the mobile device can separate and independently process the inputs of different input signal types. In this way, no matter what input device the user uses to perform input on the game interface, the mobile device can accurately identify and respond to it, thereby realizing the coexistence and compatibility of different types of input, that is, the user can interact with the game interface through the handle and the touch screen in the same operation mode of the game application program, thereby improving the flexibility of game operation.

[0037] Based on this, in step 103, the input information of the first input can be stored in the target EventData corresponding to the input signal type of the first input. In actual implementation, before storing the input information of the first input in the target EventData corresponding to the input signal type of the first input, if the target EventData is not empty, the information in the target EventData can be updated to the input information of the first input in response to receiving the first input; if the target EventData is empty, the input information of the first input can be stored in the target EventData in response to receiving the first input.

[0038] Subsequently, the first input can be operated and recognized based on the input information of the first input stored in the target EventData, to obtain the user operation behavior corresponding to the first input.

[0039] In some embodiments, the mobile device can call the target input module corresponding to the input signal type of the first input, and operate and recognize the first input based on the target EventData. That is, the input module (InputModule) corresponding to different input signal types calls the information in the corresponding EventData to perform operation recognition of the input of the corresponding type.

[0040] InputModule is a component in the UI framework for processing input. Different input modules can process input performed by the user through different types of input devices. In some embodiments, a standalone input module (StandaloneInputModule) can be used to process input performed by the user through a handle, and a touch screen input module (TouchInputModule) can be used to process input performed by the user through a touch screen.

[0041] Step 104: performing the player operation corresponding to the user operation behavior in the game interface.

[0042] After recognizing the user operation behavior corresponding to the first input, the user operation behavior corresponding to the first input can be converted into an input event (UE.EInputEvent) recognizable by the UE. Subsequently, the player operation corresponding to the input event is obtained, and the player operation is performed in the game interface. In this way, the response of the game application to the first input is completed, and the interaction between the user and the game application is realized.

[0043] In the game operation method of the embodiment of the present application, after the mobile device receives the first input of the user to the game interface of the game application through any input device, it can first determine the input signal type of the first input according to the input device of the first input. Regardless of the input signal type of the first input, the mobile device can identify the user operation behavior corresponding to the first input and perform the corresponding player operation on the game interface. Specifically, the mobile device can store the input information of the first input in the target event data structure corresponding to its input signal type, and identify the corresponding user operation behavior based on the information in the target event data structure through the target input module corresponding to its input signal type. In other words, the embodiment of the present application can store the input information of different input signal types separately through different event data structures. In this way, the input modules of different input signal types can call the corresponding event data structure for operation identification, so that the input processing of different input signal types by the mobile device is independent of each other and does not affect each other, thereby achieving the coexistence and compatibility of different types of inputs under the same operation mode, thereby improving the flexibility of game operation.

[0044] In some embodiments, the mobile device may be provided with a first event data structure and a second event data structure; wherein the first event data structure is an event data structure dedicated to storing handle input information, and the second event data structure is an event data structure dedicated to storing touch screen input information;

[0045] In the case where the input device is a handle connected to the mobile device, the input signal type is handle input, and the target event data storage structure is the first event data structure;

[0046] In the case where the input device is a touch screen, the input signal type is touch screen input, and the target event data storage structure is a second event data structure.

[0047] In these embodiments, the mobile device may be provided with a first EventData specifically for storing input information input by the user via the handle, and a second EventData specifically for storing input information input by the user via the touch screen. In some embodiments, the EventDataID of the first EventData may be 0, and the EventDataID of the second EventData may be 1000, but are not limited thereto.

[0048] When it is determined that the input device of the first input is a handle, the input information of the first input can be stored in the first EventData, and then the operation of the first input can be identified based on the first EventData. Furthermore, the operation of the first input can be identified based on the first EventData by the StandaloneInputModule. It is worth noting that in this case, if another new touch screen input performed by the user through the touch screen is received during the processing of the first input, since the input information of this input will be stored in the second EventData, and then the operation of this input will be identified based on the second EventData by the TouchInputModule, this touch screen input will not affect the processing of the first input, that is, it will not cause interruption to the processing of the first input, so that the coexistence and compatibility of the handle input and the touch screen input in the handle operation mode can be achieved, thereby improving the flexibility of the game operation.

[0049] When it is determined that the input device of the first input is a touch screen, the input information of the first input can be stored in the second EventData, and then the operation of the first input can be identified based on the second EventData. Furthermore, the operation of the first input can be identified based on the second EventData by the TouchInputModule. It is worth noting that in this case, if another new handle input is received from the user through the touch screen during the processing of the first input, since the input information of this input will be stored in the first EventData, and then the operation of this input will be identified by the StandaloneInputModule based on the first EventData, this handle input will not affect the processing of the first input, that is, it will not interrupt the processing of the first input, so that the coexistence and compatibility of the handle input and the touch screen input in the handle operation mode can be achieved, thereby improving the flexibility of the game operation.

[0050] It can be seen that by setting a first EventData dedicated to storing input information input by the user through the handle, and a second EventData dedicated to storing input information input by the user through the touch screen, the coexistence and compatibility of handle input and touch screen input can be achieved in the same operation mode, thereby improving the flexibility of game operations.

[0051] The following is a detailed description of how player operations are determined.

[0052] As can be seen from the foregoing, after identifying the user operation behavior corresponding to the received input, the mobile device can convert the user operation behavior into an input event that can be recognized by the UE, and then obtain the player operation corresponding to the input event.

[0053] In some embodiments of the present application, for each operating mode, the mobile device may pre-store processing functions for each input event corresponding to the primary input device, and interfaces for each input event corresponding to the non-primary input device, wherein the interfaces for the input events may be understood as processing logic for the input events.

[0054] In this way, after the mobile device converts the input event corresponding to the input performed by the user through the main input device, it can directly call the processing function corresponding to this input event to obtain the corresponding player operation. In this way, the efficiency of obtaining the player operation corresponding to the input performed by the user through the main input device can be improved.

[0055] After converting the input event corresponding to the input performed by the user through the non-primary input device, the mobile device can directly call the class or method of the interface corresponding to this input event to dynamically process this input event and obtain the corresponding player operation. In this way, the flexibility of obtaining the player operation corresponding to the input performed by the user through the non-primary input device can be improved.

[0056] Based on this, when the game application is in handle operation mode, if the first input is handle input, that is, the input device of the first input is the main input device of the handle operation mode, the mobile device can directly call the processing function corresponding to the input event of the first input to obtain the corresponding player operation.

[0057] In some embodiments, when the game application is in a gamepad operation mode, if the first input device is a touch screen, performing a player operation corresponding to the user operation behavior on the game interface may include:

[0058] Convert user actions into input events in the game application;

[0059] Call the interface corresponding to the input event to determine the player operation corresponding to the user operation behavior;

[0060] Perform player actions in the game interface.

[0061] In these embodiments, the input device for the first input is a touch screen, that is, the input device for the first input is not the primary input device for the gamepad operation mode. Therefore, after converting the input event corresponding to the first input, the interface corresponding to the input event can be called to dynamically process the input event, find the player operation corresponding to the first input, and then execute the player operation on the game interface. This can improve the flexibility of processing the first input.

[0062] As can be seen from the foregoing, game applications can support multiple operating modes.

[0063] In some embodiments, the processing flow of input received by the mobile device can be the same for different operation modes. For example, regardless of whether the game application is in a gamepad operation mode or a touch screen operation mode, the input can be processed in step 103. In these embodiments, the coexistence and compatibility of different types of input can be achieved in both the gamepad operation mode and the touch screen operation mode, thereby improving the flexibility of game operation.

[0064] In other embodiments, the mobile device may process input received in different operating modes differently. Therefore, after receiving a first input, to determine the processing flow for the first input, the mobile device may first obtain the operating mode in which the gaming application receives the first input, and then process the first input accordingly based on the operating mode.

[0065] Optionally, storing input information of the first input into a target event data structure corresponding to the input signal type; and identifying a user operation behavior corresponding to the first input based on the information in the target event data structure, including:

[0066] Get the target operation mode of the game application;

[0067] When the target operation mode is the handle operation mode, the input information of the first input is stored in the target event data structure corresponding to the input signal type; based on the information in the target event data structure, the user operation behavior corresponding to the first input is identified.

[0068] The target operation mode can be understood as: the operation mode in which the game application is located when receiving the first input.

[0069] In an embodiment of the present application, a mobile device can record and update the operating mode of a game application in real time. Specifically, after determining the initial operating mode of the game application when the game application is launched: if a switch in the operating mode of the game application is detected, the operating mode of the game application can be updated to the switched operating mode; if a switch in the operating mode of the game application is not detected, the operating mode of the game application can be maintained at the initial operating mode.

[0070] The embodiments of the present application do not limit the initial operating mode of the game application when the game application is started. In some embodiments, the initial operating mode of the game application when the game application is started can be set by default; in other embodiments, the initial operating mode of the game application when the game application is started can be determined based on whether the mobile device is connected to a handle when the game application is started. Specifically, if the mobile device is not connected to a handle when the game application is started, the initial operating mode can be determined to be the touch screen operation mode; if the mobile device is connected to a handle when the game application is started, it can be determined based on the sequence of the handle connection time and the start time of the game application. For details, please refer to the relevant description below and it will not be described here.

[0071] The mobile device may use the operation mode of the application program recorded when the first input is received as the operation mode of the game application program when the first input is received, ie, the target operation mode.

[0072] In this optional implementation, when the target operation mode is the handle operation mode, the first input can be processed by the implementation method of step 103. The specific processing flow can be found in the above-mentioned related description and will not be repeated here.

[0073] In this way, when the game application is in controller operation mode, regardless of the first input signal type, the mobile device can respond to it and perform the corresponding response operation in the game interface. This allows the coexistence and compatibility of different types of input in controller operation mode, thereby improving the flexibility of game operation.

[0074] In some embodiments, after obtaining the target operation mode of the game application, the method may further include:

[0075] When the target operation mode is the touch screen operation mode, in response to the input signal type being touch screen input, storing input information of the first input into a second event data structure; identifying a user operation behavior corresponding to the first input based on the information in the second event data structure; and executing a player operation corresponding to the user operation behavior on the game interface; wherein the second event data structure is an event data structure dedicated to storing touch screen input information;

[0076] In response to the input signal type being a handle input, an operation mode switching inquiry message is displayed, and based on the user's second input to the operation mode switching inquiry message, the operation mode of the game application is determined; wherein the operation mode switching inquiry message is used to ask the user whether to switch the operation mode of the game application to the handle operation mode.

[0077] In these embodiments, the mobile device is in a touch screen mode of operation when the first input is received.

[0078] In touch screen operation mode, the mobile device may only respond to touch screen input, but handle input may trigger the mobile device to display an operation mode switching inquiry message to ask the user whether to switch the operation mode of the game application from touch screen operation mode to handle operation mode.

[0079] In specific implementation, if the input signal type of the first input is touch screen input, the input information of the first input can be stored in a second EventData dedicated to storing touch screen input information, and then the operation of the first input can be identified based on the second EventData through the TouchInputModule to obtain the user operation behavior corresponding to the first input, and the player operation corresponding to the user operation behavior is executed in the game interface. Its specific implementation is consistent with the processing flow of touch screen input in the handle operation mode. For details, please refer to the above-mentioned related description, which will not be repeated here.

[0080] If the input signal type of the first input is a controller input, the mobile device can display an operation mode switching inquiry message in response to the input. The user can perform a second input in response to the operation mode switching inquiry message to determine whether to switch the operation mode of the game application from the touch screen operation mode to the controller operation mode.

[0081] In some implementations, the operation mode switching query information may include a switch control and a pause control. In these implementations, the second input may be a user touch input to the switch control or the pause control. If the second input is a touch input to the switch control, the mobile device may switch the operation mode of the gaming application from the touchscreen operation mode to the controller operation mode in response to the second input; if the second input is a touch input to the pause control, the mobile device may maintain the operation mode of the gaming application in the touchscreen operation mode in response to the second input.

[0082] In other implementations, the second input may be a voice input. If the second input indicates a switch, the mobile device may switch the operating mode of the gaming application from the touchscreen operating mode to the controller operating mode in response to the second input; if the second input indicates no switch, the mobile device may maintain the operating mode of the gaming application in the touchscreen operating mode in response to the second input.

[0083] In these embodiments, in touchscreen operation mode, if a touchscreen input corresponding to the game interface is received, the mobile device can execute the corresponding player operation on the game interface in response to the touchscreen input; if a controller input corresponding to the game interface is received, the mobile device can display an operation mode switching query message in response to the controller input, allowing the user to decide whether to switch the operation mode of the game application from touchscreen operation mode to controller operation mode. This can improve the flexibility of game operation.

[0084] The determination of the operation mode of the game application is specifically explained below.

[0085] In some embodiments, the method can further include:

[0086] In the case that the game application is in the handle operation mode, if the target condition is met, the game application is switched to the touch screen operation mode;

[0087] The target condition includes any of the following:

[0088] The game application determines that the game application is disconnected from the handle based on the handle connection state detected by the operating system of the mobile device;

[0089] The user's touch input on the exit control corresponding to the handle operation mode in the game application is received.

[0090] In these embodiments, the mobile device can switch the game application to the touch screen operation mode if the target condition is met.

[0091] In some implementations, the operating system of the mobile device can detect the connection state of the handle and transmit the handle connection state to the InputInterface of the UI, and the InputInterface of the UI can determine whether the game application is disconnected from the handle based on the handle connection state.

[0092] If it is determined that the game application is disconnected from the handle, the mobile device can automatically switch to the touch screen operation mode, so that the hot switching of the operation mode of the game application can be realized without the user's awareness, so that the game application can interact with the user even if the handle is disconnected, thereby improving the smoothness and flexibility of game operation.

[0093] In other implementations, an exit control corresponding to the handle operation mode can be set in the game application, and the user can trigger the mobile device to switch to the touch screen operation mode by touching the exit control.

[0094] Through the above embodiments, in the case that the game application is in the handle operation mode, the mobile device can determine whether to switch to the touch screen operation mode by whether the target condition is met, so that the determination autonomy of the operation mode of the game application can be improved, and the flexibility of game operation can be improved.

[0095] In some embodiments, the method can further include:

[0096] The first time when the mobile device is connected to the handle and the second time when the mobile device starts the game application are obtained;

[0097] determining, based on the order of the first time and the second time, an initial operation mode of the game application when the game application is started;

[0098] Among them, in response to the first time being before the second time, the initial operation mode is the handle operation mode; in response to the first time being after the second time, the initial operation mode is the touch screen operation mode.

[0099] In these embodiments, when a mobile device is connected to a handle, the operation mode of the game application when the game application is started can be determined based on the order of the controller connection time of the mobile device and the game application startup time.

[0100] In a specific implementation, if the controller connection time is earlier than the game application startup time, the operation mode of the game application when the game application is started can be determined as the controller operation mode.

[0101] If the controller connection time is later than the game application launch time, the game application's operating mode can be determined to be the touchscreen operation mode when the game application is launched. Furthermore, in this case, the mobile device can display an operation mode switching query message on the game interface to allow the user to decide whether to switch the game application's operating mode from the touchscreen operation mode to the controller operation mode. The specific implementation of this is described in the previous section and will not be repeated here.

[0102] In this way, the method of determining the operation mode of the game application can be enriched, thereby improving the flexibility of the game operation.

[0103] It should be noted that, in the absence of conflict, the embodiments and features of the embodiments in this application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0104] For ease of understanding, a specific embodiment is used as an example for illustration:

[0105]

Handle identification

[0106] ① If the mobile device is first connected to the handle device (referred to as the handle), and then the client (i.e. the game application) is opened, the interactive interface of [handle operation] will be directly presented after entering the game.

[0107] ② If the mobile device opens the client first and then connects the handle device, after entering the game, if the input of the handle controller is detected, you can Figure 2 As shown, a pop-up window will be displayed (i.e., the operation mode switching inquiry information will be displayed). Click OK to switch to the [Handle Operation] interactive interface.

[0108]

Operation compatibility

[0109] ① In the interactive interface of [Handle Operation], players can use the [Handle] to input, and can also operate the interface by touching the screen with their fingers at the same time. Independent input parameters are set for the two operation modes. For example, using the joystick of the handle to control the rotation of the lens, and dragging the screen with your fingers to control the rotation of the lens. By using the differentiation of input parameters, the final effect presented is: two ways of controlling the lens can both conform to their respective operating habits and experience (there will be no abnormal touch screen input due to the intervention of the handle).

[0110] 1) When the mobile device client is in controller operation mode, when it receives input from the player, it will first determine the hardware from which the input comes, that is, [touch screen] or [controller].

[0111] 2) After determining the input hardware type, in addition to common operational logic such as basic tap feedback, the client will also match the unique operational parameters of the [Touch Screen] or [Controller] type in real time, such as linear input sensitivity (specifically reflected in camera movement) and drag sensitivity (specifically reflected in UI scrolling), to ensure that both operational experiences are in line with player habits.

[0112] 3) The client monitors and determines the type of input signal in real time and can execute the above process at any time during operation.

[0113] 4) Overcoming the difficulty of real-time judgment and matching of two operating parameters on the mobile client, including performance optimization (no lag or crashes when the game coexists), judgment accuracy, and real-time hand tracking response. This can be achieved through the following steps:

[0114] 1. The UE itself supports controller and touch screen operations in the input layer of the mobile platform (i.e., the operating system). Taking the Android platform as an example, in the send control event (SendControllerEvents) of the game engine's input module (AndroidInputInterface) in the Android operating system, the UE supports processing controller and touch screen input data. AndroidInputInterface is the interface used by the UE to interact with the Android system, and is responsible for receiving input sent by the Android system, such as touch input, controller input, etc. SendControllerEvents is a key method in AndroidInputInterface, which is used to convert the input of the Android platform (such as touch input, controller input) into input events that the UE can recognize, and send it to the UE's input processing system.

[0115] 2. Bind the input in BasePlayerController (AddActionBinding, AddTouchBinding) to get the input from the controller and touch screen.

[0116] 3. When forwarding the player's input data to the UI underlying framework, the touch screen data will be additionally distinguished in controller mode to prevent the touch screen operation data and the controller operation data from affecting each other.

[0117] Specifically:

[0118] 1. The UI underlying framework detects EventData based on the current input mode in each frame to determine the user's operation behavior. In controller mode or touch screen mode, the corresponding input mode needs to be switched, that is, in controller mode, it switches to StandaloneInputModule, and in touch mode, it switches to TouchInputModule.

[0119] 2. By default, an EventData with EventDataId of 0 will be created, and the StandaloneInputModule and TouchInputModule will perform operation recognition based on this EventData.

[0120] 3. However, when in controller mode, events with EventDataId 0 will be detected by the StandaloneInputModule. If touch input also modifies events with EventDataId 0, some controller operations may be affected and interrupted. Based on this, if you want to allow touch input to be recognized without affecting the original controller input data, you can create a new EventData data (to avoid the ID being affected by subsequent expansion, the default starts from 1000).

[0121] 4. The TouchInputModule previously required two separate interfaces to detect EventData events per frame to identify clicks, drags, and other logic. In controller mode, the StandaloneInputModule now detects data per frame. Therefore, after receiving touch input, it can create additional EventData and call different interfaces based on the type of UE.EInputEvent detected (press, lift, move), ensuring that touch functionality can trigger UI logic even in controller mode.

[0122] For easier understanding, see Figure 3The input module of the game engine in the Android Input Interface and the IOS operating system (IOS Input Interface) both support processing of handle input and touch screen input.

[0123] After receiving the user input through the Android Input Interface or the IOS Input Interface, the user input can be identified as touch screen input or handle input through the BaseController.

[0124] If the input is touch screen input, the business layer can be used to determine the current operation mode. If the current operation mode is the handle mode, the TouchInputModule interface can be called by modifying the EventDataID. If the current operation mode is the touch screen mode, the EventData data can be modified.

[0125] If the input is handle input, the business layer can be used to determine the current operation mode. If the current operation mode is the handle mode, the StandaloneInputModule can be called to modify the EventData data. If the current operation mode is the touch screen mode, a connection pop-up window can be displayed according to the current conditions, that is, the operation mode switching query information is displayed.

[0126] In some embodiments, the operating system can notify the Input Interface of the state of disconnection of the handle, so that the UI determines whether the client is disconnected from the handle. If the client is disconnected from the handle, the client can be switched to the touch screen mode under the target condition, so that the problem that the player can only choose to kill the process to restart the game and cannot perform any operation due to disconnection of the handle can be avoided, thereby improving the smoothness of the game operation.

[0127] ②Compatibility range:

[0128] The input operation of the user can be a handle rocker, a handle key, a single-point touch screen, or a finger sliding operation.

[0129] The embodiments of the present application do not limit the product type of the handle. In some embodiments, the handle can be a handle product supporting any communication protocol such as an xbox protocol or a Sony protocol.

[0130]

Exit handle operation

[0131] ①A button for exiting the game system is provided, and the touch screen mode is returned.

[0132] ②If the player disconnects the handle connection in the main interface, the client can also identify and automatically switch back to the touch screen mode of the interactive interface.

[0133] Based on the game operation method provided in the above embodiments, the application further provides a specific implementation of a game operation device. Please refer to the following embodiments.

[0134] Referring to Figure 4 The game operation device provided in the embodiments of the application can include:

[0135] The display module 401 is configured to display a game interface of a game application.

[0136] The determination module 402 is configured to, in response to the received first input of the user to the game interface, determine the input signal type of the first input according to the input device of the first input.

[0137] The operation module 403 is configured to store the input information of the first input into a target event data structure corresponding to the input signal type, and identify the user operation behavior corresponding to the first input based on the information in the target event data structure.

[0138] The execution module 404 is configured to execute the player operation corresponding to the user operation behavior in the game interface.

[0139] The game operation device provided in the embodiments of the application can achieve Figure 1 The processes in the method embodiments will not be repeated here to avoid repetition.

[0140] Figure 5 A hardware structure schematic diagram of the game operation provided in the embodiments of the application is shown.

[0141] The mobile device can include a processor 501 and a memory 502 storing computer program instructions.

[0142] Specifically, the processor 501 can include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or can be configured to implement one or more integrated circuits of the embodiments of the application.

[0143] The memory 502 can include a mass storage for data or instructions. By way of example and not limitation, the memory 502 can include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. Where appropriate, the memory 502 can include removable or non-removable (or fixed) media. Where appropriate, the memory 502 can be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, the memory 502 is a non-volatile solid-state memory.

[0144] The memory can include read-only memory (ROM), random access memory (RAM), magnetic disk storage mediums, optical storage mediums, flash memory devices, electrical, optical, or other physical / tangible memory storage devices. Thus, in general, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software that, when executed (by one or more processors), is operable to perform operations described with reference to the methods according to an aspect of the present disclosure.

[0145] The processor 501 implements the game operation method of any one of the above embodiments by reading and executing the computer program instructions stored in the memory 502.

[0146] In one example, the mobile device can further include a communication interface 505 and a bus 510. Wherein, as shown in the figure, the processor 501, the memory 502, the communication interface 505 are connected through the bus 510 and complete the communication between each other. Figure 5

[0147] The communication interface 505 is mainly used to realize the communication between each module, device, unit and / or equipment in the embodiments of the present application.

[0148] The bus 510 includes hardware, software or both, which couples the components of the mobile device to each other. By way of example, and not limitation, such hardware, software, or both, can include common buses such as a bus for passing control information and a bus for passing data with a bus bridge coupled to it for supporting the transfer of control and data between and among various bus adapters and devices coupled to the bus 510.

[0149] ​The bus can include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infmiband interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or another suitable bus or a combination of two or more of these. Where suitable, bus 510 can include one or more buses. Although specific buses are described and illustrated in the embodiments herein, the application contemplates any suitable bus or interconnect.

[0150] In addition, in combination with the game operation method in the above embodiments, the embodiments of the present application can provide a computer storage medium for implementation. The computer storage medium has computer program instructions stored thereon; the computer program instructions are executed by a processor to implement any one of the game operation methods in the above embodiments.

[0151] The embodiments of the present application can also provide a computer program product, instructions in the computer program product are executed by a processor of a mobile device to make the mobile device execute any one of the game operation methods in the above embodiments.

[0152] It needs to be clear that the present application is not limited to the specific configurations and processes described above and shown in the drawings. For the sake of brevity, detailed descriptions of well-known methods are omitted herein. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present application are not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between steps, after understanding the spirit of the present application.

[0153] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application-specific integrated circuit (ASIC), appropriate firmware, a plug-in unit, a function card, etc. When implemented in software, the elements of the present application are programs or code segments that are used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable medium" can include any medium that can store or transmit information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROMs, flash memories, erasable ROMs, floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

[0154] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps. In other words, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0155] Aspects of the present disclosure have been described above with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the implementation of the function / action specified in one or more boxes of the flowchart and / or block diagram. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor or a field programmable logic circuit. It is also understood that each box in the block diagram and / or flowchart and the combination of the boxes in the block diagram and / or flowchart can also be implemented by dedicated hardware that performs the specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.

[0156] The above description is only a specific embodiment of the present application. Those skilled in the art will clearly understand that for the convenience and brevity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the scope of protection of the present application is not limited thereto. Any person skilled in the art can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present application, and these modifications or replacements should be included in the scope of protection of the present application.

Claims

1. A game operation method, characterized in that: Applicable to a mobile device with a touch screen; the method includes: Display the game interface of the game application; In response to receiving a first input from a user on the game interface, determining an input signal type of the first input according to an input device of the first input; Storing the input information of the first input in a target event data structure corresponding to the input signal type; and identifying the user operation behavior corresponding to the first input based on the information in the target event data structure; Execute player operations corresponding to the user operation behavior in the game interface.

2. The method according to claim 1, characterized in that The mobile device is provided with a first event data structure and a second event data structure; wherein the first event data structure is an event data structure dedicated to storing handle input information, and the second event data structure is an event data structure dedicated to storing touch screen input information; In the case where the input device is a handle connected to the mobile device, the input signal type is handle input, and the target event data storage structure is the first event data structure; In the case where the input device is the touch screen, the input signal type is touch screen input, and the target event data storage structure is a second event data structure.

3. The method according to claim 1, characterized in that In the case where the input device is the touch screen, the player operation corresponding to the user operation behavior performed on the game interface includes: Converting the user operation behavior into an input event in the game application; Calling the interface corresponding to the input event to determine the player operation corresponding to the user operation behavior; Execute the player operation on the game interface.

4. The method according to claim 1, wherein storing the input information of the first input into a target event data structure corresponding to the input signal type; Identifying a user operation behavior corresponding to the first input based on information in the target event data structure includes: Obtaining a target operation mode of the game application; When the target operation mode is the handle operation mode, the input information of the first input is stored in the target event data structure corresponding to the input signal type; based on the information in the target event data structure, the user operation behavior corresponding to the first input is identified.

5. The method according to claim 4, characterized in that After obtaining the target operation mode of the game application, the method further includes: When the target operation mode is the touch screen operation mode, in response to the input signal type being touch screen input, the input information of the first input is stored in a second event data structure; based on the information in the second event data structure, a user operation behavior corresponding to the first input is identified; and a player operation corresponding to the user operation behavior is executed on the game interface; wherein the second event data structure is an event data structure dedicated to storing touch screen input information; In response to the input signal type being a handle input, an operation mode switching inquiry message is displayed, and based on the user's second input to the operation mode switching inquiry message, the operation mode of the game application is determined; wherein the operation mode switching inquiry message is used to inquire the user whether to switch the operation mode of the game application to the handle operation mode.

6. The method according to claim 4, characterized in that The method further comprises: When the game application is in a handle operation mode, if a target condition is met, switching the game application to a touch screen operation mode; The target conditions include any of the following: The game application determines, based on the connection status of the controller detected by the operating system of the mobile device, that the game application is disconnected from the controller; A user touch input to an exit control corresponding to the handle operation mode in the game application is received.

7. The method according to claim 4, characterized in that The method further comprises: Obtaining a first time when the mobile device is connected to a controller, and a second time when the mobile device starts the game application; determining, according to a sequence of the first time and the second time, an initial operation mode of the game application when the game application is started; In which, in response to the first time being earlier than the second time, the initial operation mode is the handle operation mode; in response to the first time being later than the second time, the initial operation mode is the touch screen operation mode.

8. A game operating device, characterized in that: Applicable to a mobile device with a touch screen; the device comprises: A display module, used to display the game interface of the game application; a determination module, configured to determine, in response to a first input received from a user on the game interface, an input signal type of the first input according to an input device of the first input; an operation module, configured to store the input information of the first input into a target event data structure corresponding to the input signal type; and identify a user operation behavior corresponding to the first input based on the information in the target event data structure; An execution module is used to execute the player operation corresponding to the user operation behavior on the game interface.

9. A mobile device, characterized in that: The device comprises: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the game operation method according to any one of claims 1 to 8 is implemented.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the game operation method according to any one of claims 1 to 8.

Images