Detailed Description
The technical solutions of the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which are obtained by a person skilled in the art based on the embodiments of the present application, fall within the scope of protection of the present application.
The terms first, second and the like in the description and in the claims, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that embodiments of the application may be practiced otherwise than as specifically illustrated or described herein. The objects identified by "first", "second", etc. are generally one type, and the number of the objects is not limited, for example, the first object may be one or a plurality of first objects. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/", generally means that the associated object is an "or" relationship.
The following describes in detail the method for processing the reminding event provided by the embodiment of the application through specific embodiments and application scenarios thereof with reference to the accompanying drawings.
Fig. 1 is a schematic flow chart of a method for processing a reminder event according to an embodiment of the present application, including steps 201 to 203:
step 201, the reminding event processing device determines whether a game interface of a game application program is displayed on the reminding event processing device under the condition that the reminding event reaches the reminding time.
The game interface comprises a local game object.
In the embodiment of the present application, the reminding event may be an alarm clock or a schedule, which is not limited in the embodiment of the present application. The calendar application may be set, for example.
In the embodiment of the application, the reminding time can comprise at least one of the following years, months, days, hours, minutes and seconds.
Optionally, the game interface may further include at least one of at least one non-player game object and at least one peer game object, which is not limited by the embodiment of the present application.
In the embodiment of the present application, the game corresponding to the game application may be a strategic game, a chess game, or any possible game, which is not limited in the embodiment of the present application. For example, the game application may correspond to a multiplayer online competitive game (multiplayer online battle ARENA GAMES, MOBA), which may also be referred to as an action instant strategy game.
It should be noted that, after the user triggers the alert event processing device to set the alert event, the alert event processing device may synchronize the alert event to the game application.
Step 202, the reminding event processing device determines the game state corresponding to the game interface under the condition that the game interface of the game application program is displayed.
In an embodiment of the present application, the above game states may include at least one state. The above game state may be an idle game state (a first game state described below) or an active game state (a second game state described below), which is not limited by the embodiment of the present application.
Optionally, in the embodiment of the present application, the determining the game state corresponding to the game interface in the step 202 may specifically include the step that the reminding event processing device may determine the game state corresponding to the game interface according to the estimated death frequency corresponding to the game object in the game interface. The game objects in the game interface comprise at least one of a local game object, at least one non-player game object and at least one opposite-end game object.
The reminding event processing device may determine that the game state is the first game state when the estimated death frequency is smaller than a first preset threshold value, and determine that the game state is the second game state when the estimated death frequency is greater than or equal to the first preset threshold value.
For example, the alert event processing apparatus may be divided into two scenes, namely, scene a and scene B, according to the intensity of combat around the own game object when the game is running. The scene A indicates that the fight intensity around the game object is mild, the game object may be strolling or fighting a soldier, and the like, at this time, the game character frequent death does not generally occur around the game object, at this time, the scene A may be determined to be in an idle game state, the scene B indicates that the fight intensity around the game object is tense, the game object may be fighting a monster (boss) with great difficulty, and the like, at this time, the game character frequent death may occur around the game object, and at this time, the scene B may be determined to be in an active game state.
Note that, the reminder event processing device may not perform any operation in the case where the game interface of the game application is not displayed.
The reminding event processing device can analyze the reminding event with the reminding time later than the current time under the condition that the game interface of the game application program is displayed.
And 203, keeping displaying the game interface and executing target operation by the reminding event processing device under the condition that the game state is in the target game state.
The target operation comprises at least one of displaying a prompt message of the prompt event in a message display area of the game interface and outputting the prompt message through target game object voice.
In the embodiment of the present application, the target game state may be the idle game state or the active game state, which is not limited in the embodiment of the present application.
In the embodiment of the present application, the prompting message may be a text message or a voice message, which is not limited in the embodiment of the present application. It should be noted that, when the prompting message is a text message, the prompting event processing device may convert the text message into a voice message, and when the prompting message is a voice message, the prompting event processing device may convert the voice message into a text message.
In the embodiment of the present application, the target game object may be a local game object, a non-player game object, or an opposite game object, which may be specifically set according to actual requirements, and the embodiment of the present application is not limited to this.
The above-mentioned holding and displaying of the game interface means that the game interface is still in progress and the game screen is still updated in real time.
Optionally, in the embodiment of the present application, in the case that the reminding event reaches the reminding time, the reminding event processing device may remind the user in at least two possible ways without affecting the game of the user.
In a first possible implementation:
For example, in the case where the target game state is the first game state, the step 203 may specifically include the following steps A1 to A3:
And A1, displaying N non-player game objects in the game interface when the game state is in the first game state by the reminding event processing device.
Wherein, a non-player game object is used for triggering an operation aiming at the reminding event, and N is a positive integer.
The N non-player game objects may be original non-player game objects or newly added non-player game objects, which is not limited in the embodiment of the present application.
In one example, the original non-player game object is a non-player game object displayed in a game interface, and the added non-player game object is a non-player game object that is not displayed in the game interface but is present in a game application.
And step A2, the reminding event processing device receives a first input of a user to a first non-player game object in the N non-player game objects.
The first input may be, for example, a click input of the first non-player game object by the user, or a click input of the first control by the user, or a voice command input by the user, or a specific gesture input by the user, which may be specifically determined according to the actual use requirement, and the embodiment of the present application is not limited to this. The first control may be an original control or an added control, which is not limited in the embodiment of the present application.
The specific gesture in the embodiment of the application can be any one of a single-click gesture, a sliding gesture, a dragging gesture, a pressure recognition gesture, a long-press gesture, an area change gesture, a double-press gesture and a double-click gesture, and the click input in the embodiment of the application can be single-click input, double-click input or any-time click input, and the like, and can also be long-press input or short-press input.
The first non-player game object may be one or more, which is not limited in the embodiment of the present application.
And step A3, responding to the first input, keeping the game interface displayed by the reminding event processing device, and executing target operation.
Wherein the target game object is the first non-player game object.
For example, when the user sets the alarm clock 1 through the mobile phone and plays MOBA games. As shown in fig. 2, the handset displays a game interface 31 for a MOBA game application, where the game interface 31 displays a native player character 32 (i.e., the native game object described above) and 1 non-player character (NPC). Wherein, the 1 NPC is NPC1. When the alarm clock 1 reaches the reminding time, after the mobile phone detects that the game interface 31 is displayed on the mobile phone, the mobile phone can detect the game state of the game interface 31. When the handset detects that the native player character 32 is strolling, the handset may display the text "reminder" above the NPC1 as shown in fig. 3. If the user wants to learn the text content in the alarm clock 1, the user can aim at the NPC1 and click the "attack" button (i.e. the first input described above), i.e. hit the NPC1. At this time, the mobile phone can keep displaying the game interface 31 and voice broadcast the text content in the alarm clock 1 through the NPC1.
Optionally, in an embodiment of the present application, after displaying N non-player game objects in the game interface in the step A1, the method may further include the following steps A4 and A5:
And step A4, the reminding event processing device receives a second input of a second non-player game object in the N non-player game objects by a user.
The second input may be, for example, a click input of the second non-player game object by the user, or a click input of the second control by the user, or a voice command input by the user, or a specific gesture input by the user, which may be specifically determined according to the actual use requirement, and the embodiment of the present application is not limited to this. The second control may be an original control or an added control, which is not limited in the embodiment of the present application.
The second non-player game object may be one or more, which is not limited in the embodiment of the present application.
And step A5, responding to the second input to remind the event processing device to execute the first operation.
The first operation includes any one of keeping the game interface displayed and deferring the reminding time of the reminding event, instructing a game system of the game application program to take over a local game object and display the reminding interface of the reminding event, instructing the game system to hang up the local game object and display the reminding interface.
For example, when the handset detects that the native player character 32 is strolling, as shown in fig. 3, the handset may additionally display 3 NPCs, NPC2, NPC3, and NPC4, respectively. And the text "deferred" is displayed above NPC2, the text "takeover" is displayed above NPC3, and the text "on hook" is displayed above NPC4. When the user wants to postpone the alarm clock 1, the user can aim at the NPC2 and click the "attack" button (i.e. the second input described above), i.e. hit the NPC2. At this time, the mobile phone can keep displaying the game interface 31 and delay the next reminding time of the alarm clock 1 for 5 minutes. When the user wants the gaming system to take over the native player character, the user can aim at NPC3 and click the "attack" button (i.e., the second input described above), i.e., hit the NPC3. At this point, the handset can instruct MOBA the gaming system of the gaming application to take over the native player character 32 and display the alert interface of the alarm 1 full screen. When the user wants the native player character to hang up, the user can aim at the NPC4 and click the "attack" button (i.e., the second input described above), i.e., strike the NPC4. At this time, the mobile phone can instruct the game system to hang up the local player character 32 and display the prompt interface of the alarm clock 1 in full screen.
Therefore, the user can rapidly realize different operations on the alarm clock through the plurality of non-player game objects displayed by the reminding event processing device, and thus, the interaction between the user and the reminding event processing device is enriched.
Optionally, in the embodiment of the present application, in a case where the first operation is to keep displaying the game interface and delay the reminding time of the reminding event, after the step A4, the method further includes the following step A6:
and step A6, responding to the second input, and canceling the display of all or part of the N non-player game objects in the game interface by the reminding event processing device.
In an exemplary embodiment, if all of the N non-player game objects are non-player game objects that are not displayed in the game interface, the alert event processing device may cancel displaying the N non-player game objects in the game interface, and if some of the N non-player game objects are non-player game objects that are not displayed in the game interface, the alert event processing device may cancel displaying some of the non-player game objects in the game interface.
It should be noted that, the reminding event processing device has no obvious sequence when executing the step A6 and the step A5. For example, the alert event processing apparatus may execute the step A5 before executing the step A6, may execute the step A5 after executing the step A6, and may execute the step A5 while executing the step A6.
For example, in connection with FIG. 3, after the user aims at NPC2 and clicks on the "attack" button (i.e., the second input described above), the handset may remain displaying the game interface 31 and cancel the NPC2, NPC3 and NPC4 in the game interface 31 as shown in FIG. 2.
In a second possible implementation:
For example, in the case where the target game state is the second game state, the step 203 may specifically include the following steps B1 and B2:
And B1, under the condition that the game state is in a second game state, the reminding event processing device determines whether at least one game object in the at least one opposite-end game object survives.
The at least one game object at the opposite end is a game object corresponding to another user.
The alert event processing device may illustratively determine whether the at least one peer gaming object is alive by reading data in the gaming application.
And B2, keeping displaying the game interface and executing target operation by the reminding event processing device under the condition that at least one game object does not survive.
For example, in connection with FIG. 2, 2 peer player characters, namely a teammate player character and an enemy player character of the native player character 32, are also displayed in the game interface 31. When the alarm clock 1 reaches the reminding time, after the mobile phone detects that the game interface 31 is displayed on the mobile phone, the mobile phone can detect the game state of the game interface 31. When the mobile phone detects that the player character 32 is in the battle, if the mobile phone determines that the player character of the teammate or the enemy player is dead, as shown in fig. 4, the mobile phone can keep displaying the game interface 31, display the text content in the alarm clock 1 in the message display area above the game interface 31, and broadcast the text content through the player character 32 in voice.
Optionally, in an embodiment of the present application, the method may further include the following steps B3 to B6:
and B3, under the condition that the game state is in the second game state, the reminding event processing device determines whether the local game object survives.
The alert event processing device may illustratively determine whether the native game object survives by reading data in the game application.
In one example, the alert event processing apparatus may perform step B3 described above after step B2 described above.
And B4, displaying M marks in the game interface by the reminding event processing device under the condition that the local game object does not survive.
Wherein, an identifier is used for triggering an operation aiming at the reminding event, and M is a positive integer.
Illustratively, the characters, symbols, images and the like used for indicating the information are identified in the embodiment of the application, and controls or other containers can be used as carriers for displaying the information, including but not limited to the characters, the symbols and the images.
And step B5, the reminding event processing device receives a third input of a user on the target identifier in the M identifiers.
The third input may be, for example, a click input of the target identifier by the user, or a voice command input by the user, or a specific gesture input by the user, which may be specifically determined according to the actual use requirement, which is not limited by the embodiment of the present application.
And step B6, responding to the third input to remind the event processing device to execute a second operation.
The second operation includes any one of keeping the game interface displayed and deferring the reminding time of the reminding event, instructing the game system of the game application program to take over the local game object and display the reminding interface of the reminding event, instructing the game system to hang the local game object and display the reminding interface.
For example, in connection with FIG. 2, when the handset detects that the native player character 32 is in a battle, the handset may detect whether the native player character 32 is alive. In the event that the handset determines that the native player character 32 is dead, the handset may display 3 options in the game interface 31, a "postpone" option 41, a "take over" option 42 and an "hang up" option 43, respectively, as shown in fig. 5. When the user wants to defer the alarm clock 1, the user can click on the "defer" option 41 (i.e. the third input described above). At this time, the mobile phone can keep displaying the game interface 31 and delay the next reminding time of the alarm clock 1 for 10 minutes. When the user wants the gaming system to take over the native player character, the user can click on the "take over" option 42 (i.e., the third input described above). At this point, the handset can instruct MOBA the gaming system of the gaming application to take over the native player character 32 and display the alert interface of the alarm 1 full screen. When the user wants the native player character to hang up, the user can click on the "hang up" option 43 (i.e., the third input described above). At this time, the mobile phone can instruct the game system to hang up the local player character 32 and display the prompt interface of the alarm clock 1 in full screen.
Therefore, the reminding event processing device can remind the user in different modes under the condition of different game states, so that the user can be effectively reminded under the condition that the game of the user is not influenced, and interaction between the user and the reminding event processing device can be enriched.
Optionally, in an embodiment of the present application, in a case where the game application does not include a revival timer, after the step B3, the method may further include the following steps B7 and B8:
and B7, when the local game object does not survive, the reminding event processing device increases a revival timer in the game application program and displays the timing time of the revival timer in the game interface.
Illustratively, the above-described game application does not include a revival timer, which refers to the case where the native game object is revived immediately after death, and thus the revival timer is not required.
Illustratively, the revival timer may be a positive timer or a negative timer, which is not limited in the embodiment of the present application.
And step B8, the reminding event processing device instructs the game system to revive the local game object again under the condition that the timing time meets the first condition.
For example, the first condition may be that the counted time reaches the preset time, or that the counted time is greater than or equal to the second preset threshold, which is not limited in the embodiment of the present application.
For example, in the case where the handset determines that the native player character 32 is dead, the handset may add a revival timer to the game application, and in connection with fig. 5, the countdown time of the revival timer is also displayed above the game interface 31 for 20 seconds, and when the countdown time reaches 0 seconds, the handset may instruct the game system to revive the native game object again. In this way, time can be provided for the user to operate the alarm clock.
According to the reminding event processing method provided by the embodiment of the application, the reminding event processing device can determine whether the game interface of the game application program is displayed or not under the condition that the reminding event reaches the reminding moment. Then, the reminder event processing device can determine the game state corresponding to the game interface of the game application program when the game interface is displayed. Finally, the reminding event processing device can keep displaying the game interface and execute the target operation under the condition that the game state is in the target game state. The game interface comprises a local game object, and the target operation comprises at least one of displaying a prompt message of a prompt event in a message display area of the game interface and outputting the prompt message through the voice of the target game object. Through the scheme, compared with the scheme that the interaction between the electronic equipment and the user is single in the alarm clock reminding mode in the related art, which possibly causes that the user forgets to do things, the reminding event processing device can combine the game with the reminding event, and under the condition that the reminding event reaches the reminding moment, if the fact that the electronic equipment displays the game interface of the game application program and the game state of the game interface is in the target game state is determined, the reminding event processing device can keep displaying the game interface and display the reminding message of the reminding event in the message display area of the game interface, or output the reminding message through the voice of the target game object, so that the aim of reminding the user is achieved. Therefore, the interest of the user game experience is improved, the user can be effectively reminded under the condition that the user game is not influenced, and interaction between the user and the electronic equipment is enriched.
It should be noted that, in the method for processing a reminder event according to the embodiment of the present application, the execution body may be a reminder event processing device, or a control module for executing the method for processing a reminder event in the reminder event processing device. In the embodiment of the application, the reminding event processing device is described by taking the method for executing the reminding event processing by the reminding event processing device as an example.
Fig. 6 is a schematic diagram of a possible structure of a reminder event processing device according to an embodiment of the present application, where the reminder event processing device 500 includes a determining module 501, a display module 502, and an executing module 503, where the determining module 501 is configured to determine whether a game interface of a game application is displayed when a reminder event reaches a reminder time, the game interface includes a native game object, and determine a game state corresponding to the game interface when the game interface of the game application is displayed, the display module 502 is configured to keep displaying the game interface when the determining module 501 determines that the game state is in a target game state, and the executing module 503 is configured to execute a target operation when the determining module 501 determines that the game state is in the target game state, where the target operation includes at least one of displaying a reminder message of the reminder event in a message display area of the game interface, and outputting the reminder message through voice of the target game object.
Optionally, the game interface comprises at least one non-player game object and at least one opposite game object, and a determining module 501, specifically configured to determine a game state corresponding to the game interface according to an estimated death frequency corresponding to the game object in the game interface.
Optionally, as shown in fig. 6, the alert event processing apparatus 500 further includes a receiving module 504, where the target game state is a first game state, a display module 502 further configured to display N non-player game objects in the game interface, where one non-player game object is used to trigger an operation for an alert event, and N is a positive integer, a receiving module 504 configured to receive a first input from a user to a first non-player game object in the N non-player game objects, a display module 502 specifically configured to keep displaying the game interface in response to the first input received by the receiving module 504, and an executing module 503 specifically configured to execute the target operation in response to the first input received by the receiving module 504, where the target game object is the first non-player game object.
Optionally, the receiving module 504 is further configured to receive a second input from the user to a second non-player game object of the N non-player game objects, and the executing module 503 is further configured to execute, in response to the second input received by the receiving module 504, a first operation, where the first operation includes any one of maintaining to display the game interface and deferring a reminder of the reminder event, instructing a game system of the game application to take over the native game object and display the reminder interface of the reminder event, and instructing the game system to hang the native game object and display the reminder interface.
Optionally, the first operation is to keep displaying the game interface and postpone the reminding time of the reminding event, and the display module 502 is further configured to cancel displaying all or part of the N non-player game objects in the game interface in response to the second input received by the receiving module 504.
Optionally, the target game state is a second game state, the determining module 501 is further configured to determine whether at least one game object of the at least one peer game objects is alive when the game state is in the second game state, the display module 502 is specifically configured to keep displaying the game interface when the determining module 501 determines that the at least one game object is not alive, and the executing module 603 is specifically configured to execute the target operation when the determining module 501 determines that the at least one game object is not alive.
Optionally, as shown in fig. 6, the alert event processing apparatus 500 further includes a receiving module 504, a determining module 501 further configured to determine whether the local game object survives in the case where the game state is in the second game state, a display module 502 further configured to display M identifiers in the game interface in the case where the determining module 501 determines that the local game object is not survived, one identifier is a positive integer for triggering an operation for an alert event, the receiving module 504 further configured to receive a third input of a user to a target identifier in the M identifiers, and an executing module 503 further configured to execute the second operation in response to the third input received by the receiving module 504, where the second operation includes any one of maintaining the game interface and deferring the alert time of the alert event, instructing a game system of the game application to take over the local game object and display the alert event, and instructing the game system to hang the local game object and display the alert event.
It should be noted that, as shown in fig. 6, the modules that are necessarily included in the alert event processing apparatus 500 are illustrated by solid line boxes, such as the determining module 501, and the modules that may or may not be included in the alert event processing apparatus 500 are illustrated by dashed line boxes, such as the receiving module 504.
According to the reminding event processing device provided by the embodiment of the application, whether the game interface of the game application program is displayed can be determined under the condition that the reminding event reaches the reminding moment. Then, the reminder event processing device can determine the game state corresponding to the game interface of the game application program when the game interface is displayed. Finally, the reminding event processing device can keep displaying the game interface and execute the target operation under the condition that the game state is in the target game state. The game interface comprises a local game object, and the target operation comprises at least one of displaying a prompt message of a prompt event in a message display area of the game interface and outputting the prompt message through the voice of the target game object. Through the scheme, compared with the scheme that the interaction between the electronic equipment and the user is single in the alarm clock reminding mode in the related art, which possibly causes that the user forgets to do things, the reminding event processing device can combine the game with the reminding event, and under the condition that the reminding event reaches the reminding moment, if the reminding event processing device is determined to display the game interface of the game application program and the game state of the game interface is in the target game state, the reminding event processing device can keep displaying the game interface and display the reminding message of the reminding event in the message display area of the game interface, or output the reminding message through the target game object voice, so that the aim of reminding the user is fulfilled. Therefore, the interest of the user game experience is improved, the user can be effectively reminded under the condition that the user game is not influenced, and interaction between the user and the electronic equipment is enriched.
The beneficial effects of the various implementation manners in this embodiment may be specifically referred to the beneficial effects of the corresponding implementation manners in the foregoing method embodiment, and in order to avoid repetition, the description is omitted here.
The reminding event processing device in the embodiment of the application can be a device, and can also be a component, an integrated circuit or a chip in the terminal. The device may be a mobile electronic device or a non-mobile electronic device. By way of example, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook or Personal Digital Assistant (PDA), etc., and the non-mobile electronic device may be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a Television (TV), a teller machine, a self-service machine, etc., and the embodiments of the present application are not limited in particular.
The reminding event processing device in the embodiment of the application can be a device with an operating system. The operating system may be an Android operating system, an ios operating system, or other possible operating systems, and the embodiment of the present application is not limited specifically.
The reminding event processing device provided by the embodiment of the application can realize each process realized by the method embodiments of fig. 1 to 5, and in order to avoid repetition, the description is omitted here.
Optionally, as shown in fig. 7, the embodiment of the present application further provides an electronic device 600, including a processor 601, a memory 602, and a program or an instruction stored in the memory 602 and capable of running on the processor 601, where the program or the instruction implements each process of the above embodiment of the alert event processing method when executed by the processor 601, and the process can achieve the same technical effect, so that repetition is avoided, and no further description is given here.
It should be noted that, the electronic device in the embodiment of the present application includes the mobile electronic device and the non-mobile electronic device described above.
Fig. 8 is a schematic diagram of a hardware structure of an electronic device implementing an embodiment of the present application.
The electronic device 100 includes, but is not limited to, a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, and a processor 110.
Those skilled in the art will appreciate that the electronic device 100 may further include a power source (e.g., a battery) for powering the various components, and that the power source may be logically coupled to the processor 110 via a power management system to perform functions such as managing charging, discharging, and power consumption via the power management system. The electronic device structure shown in fig. 8 does not constitute a limitation of the electronic device, and the electronic device may include more or less components than shown, or may combine certain components, or may be arranged in different components, which are not described in detail herein.
The game device comprises a processor 110, a display unit 106 and a processor 110, wherein the processor 110 is used for determining whether a game interface of a game application program is displayed or not when a reminding event reaches a reminding moment, the game interface comprises a local game object, and determining a game state corresponding to the game interface when the game interface of the game application program is displayed, the display unit 106 is used for keeping displaying the game interface when the processor 110 determines that the game state is in a target game state, and the processor 110 is further used for executing target operation when the game state is determined to be in the target game state, wherein the target operation comprises at least one of displaying a reminding message of the reminding event in a message display area of the game interface and outputting the reminding message through voice of the target game object.
Optionally, the game interface includes at least one non-player game object and at least one opposite game object, and the processor 110 is specifically configured to determine a game state corresponding to the game interface according to an estimated death frequency corresponding to the game object in the game interface.
Optionally, the target game state is a first game state, the display unit 106 is further configured to display N non-player game objects in the game interface, where N is a positive integer, and one non-player game object is used to trigger an operation for a reminder event, the user input unit 107 is configured to receive a first input from a user to a first non-player game object in the N non-player game objects, the display unit 106 is specifically configured to respond to the first input received by the user input unit 107, keep displaying the game interface, and the processor 110 is specifically configured to respond to the first input received by the user input unit 107, and execute a target operation, where the target game object is the first non-player game object.
Optionally, the user input unit 107 is further configured to receive a second input from a user to a second non-player game object of the N non-player game objects, and the processor 110 is further configured to perform, in response to the second input received by the user input unit 107, a first operation including any one of maintaining the game interface displayed and deferring a reminder of the reminder event, instructing the game system of the game application to take over the native game object and display the reminder interface of the reminder event, instructing the game system to hang the native game object and display the reminder interface.
Optionally, the first operation is to keep displaying the game interface and postpone the reminding time of the reminding event, and the display unit 106 is further configured to cancel displaying all or part of the N non-player game objects in the game interface in response to the second input received by the user input unit 107.
Optionally, the target game state is a second game state, the processor 110 is further configured to determine whether at least one game object of the at least one peer game object is alive when the game state is in the second game state, the display unit 106 is specifically configured to keep displaying the game interface when the processor 110 determines that the at least one game object is not alive, and to perform the target operation when the at least one game object is not alive.
Optionally, the processor 110 is further configured to determine whether the local game object survives in the case that the game state is in the second game state, the display unit 106 is further configured to display M identifiers in the game interface in the case that the processor 110 determines that the local game object is not survived, one identifier is configured to trigger an operation for a reminder event, M is a positive integer, the user input unit 107 is further configured to receive a third input of a target identifier from the M identifiers by a user, and the processor 110 is further configured to perform the second operation in response to the third input received by the user input unit 107, where the second operation includes any one of maintaining the game interface and deferring a reminder time of the reminder event, instructing a game system of the game application to take over the local game object and display the reminder interface of the reminder event, instructing the game system to hang the local game object, and displaying the reminder interface.
According to the electronic device provided by the embodiment of the application, the electronic device can determine whether the game interface of the game application program is displayed or not under the condition that the reminding event reaches the reminding moment. Then, the electronic device may determine, in a case where a game interface of the game application is displayed, a game state corresponding to the game interface. Finally, the electronic device may remain displayed on the game interface and perform the target operation if the game state is in the target game state. The game interface comprises a local game object, and the target operation comprises at least one of displaying a prompt message of a prompt event in a message display area of the game interface and outputting the prompt message through the voice of the target game object. Through the scheme, compared with the scheme that the interaction between the electronic equipment and the user is single in the alarm clock reminding mode in the related art, which possibly causes that the user forgets to do things, the electronic equipment can combine the game with the reminding event, and under the condition that the reminding event reaches the reminding moment, if the electronic equipment is determined to display the game interface of the game application program and the game state of the game interface is in the target game state, the electronic equipment can keep displaying the game interface and display the reminding message of the reminding event in the message display area of the game interface, or output the reminding message through the target game object voice, so that the aim of reminding the user is fulfilled. Therefore, the interest of the user game experience is improved, the user can be effectively reminded under the condition that the user game is not influenced, and interaction between the user and the electronic equipment is enriched.
The beneficial effects of the various implementation manners in this embodiment may be specifically referred to the beneficial effects of the corresponding implementation manners in the foregoing method embodiment, and in order to avoid repetition, the description is omitted here.
It should be appreciated that in embodiments of the present application, the input unit 104 may include a graphics processor (Graphics Processing Unit, GPU) 1041 and a microphone 1042, the graphics processor 1041 processing image data of still pictures or video obtained by an image capturing device (e.g. a camera) in a video capturing mode or an image capturing mode. The display unit 106 may include a display panel 1061, and the display panel 1061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 107 includes a touch panel 1071 and other input devices 1072. The touch panel 1071 is also referred to as a touch screen. The touch panel 1071 may include two parts of a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein. Memory 109 may be used to store software programs as well as various data including, but not limited to, application programs and an operating system. The processor 110 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 110.
The embodiment of the application also provides a readable storage medium, and the readable storage medium stores a program or an instruction, which when executed by a processor, implements each process of the above embodiment of the method for processing a reminder event, and can achieve the same technical effect, so that repetition is avoided and no further description is given here.
Wherein the processor is a processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium such as a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
The embodiment of the application further provides a chip, which comprises a processor and a communication interface, wherein the communication interface is coupled with the processor, and the processor is used for running programs or instructions to realize the processes of the embodiment of the reminding event processing method, and the same technical effects can be achieved, so that repetition is avoided, and the description is omitted here.
It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, chip systems, or system-on-chip chips, etc.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation 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 may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a computer software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present application.
The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are to be protected by the present application.