JP7704935B2 - PROGRAM AND INFORMATION PROCESSING APPARATUS - Google Patents

Description

Patent Law Article 30, Paragraph 2 applied. On December 5, 2017, information regarding the game program was posted on the official website (https://colopl.co.jp/alicegearaegis/).

Article 30, paragraph 2 of the Patent Act applies. Article published on the website (http://www.4gamer.net/games/388/G038881/20180112120/) on January 16, 2018.

Application of Article 30, Paragraph 2 of the Patent Act Article published on the website (https://game.watch.impress.co.jp/docs/review/1100213.html) on January 15, 2018

Article 30, paragraph 2 of the Patent Act applied. Article published on the website (https://www.inside-games.jp/article/2018/01/18/112234.html) on January 18, 2018.

Application of Article 30, Paragraph 2 of the Patent Act Article published on the website (https://www.gamer.ne.jp/news/201801150001/) on January 15, 2018

Article 30, paragraph 2 of the Patent Law applied. Article published on the website (https://gamewith.jp/gamedb/article/game/show/2209/760) on January 12, 2018.

Application of Article 30, Paragraph 2 of the Patent Law Article published on the website (https://altema.jp/alicegearaegitest) on January 15, 2018

Article 30, paragraph 2 of the Patent Act applied. Article published on the website (https://games.app-liv.jp/archives/334329) on January 15, 2018.

Article 30, paragraph 2 of the Patent Law applied. Article published on the website (http://gamebiz.jp/?p=201902) on January 18, 2018.

Application of Article 30, Paragraph 2 of the Patent Act Article published on the website (https://app.famitsu.com/20180115_1213509/) on January 15, 2018

Article 30, paragraph 2 of the Patent Law applied. Article published on the website (https://appli-style.jp/newspage.php?id=689) on January 15, 2018.

Article 30, paragraph 2 of the Patent Law applied. Article published on the website (https://gamy.jp/alicegearaegis/alicegear-review) on January 15, 2018.

Patent Law Article 30, Paragraph 2 applied. On January 22, 2018, the game application "Alice Gear Aegis" Ver. 1.0.1 was released for iOS (https://itunes.apple.com/jp/app/Alice-Gear-Aegis/id1245550834?mt=8) and Android (https://play.google.com/store/apps/details?id=jp.colopl.alice&hl=ja).

Patent Law Article 30, Paragraph 2 applied. On January 26, 2018, the game application "Alice Gear Aegis" Ver. 1.0.3 was released for iOS (https://itunes.apple.com/jp/app/Alice-Gear-Aegis/id1245550834?mt=8) and Android (https://play.google.com/store/apps/details?id=jp.colopl.alice&hl=ja).

Patent Law Article 30, Paragraph 2 applied. On February 14, 2018, the game application "Alice Gear Aegis" Ver. 1.1.0 was released for iOS (https://itunes.apple.com/jp/app/Alice-Gear-Aegis/id1245550834?mt=8) and Android (https://play.google.com/store/apps/details?id=jp.colopl.alice&hl=ja).

Patent Law Article 30, Paragraph 2 applied. On February 27, 2018, the game application "Alice Gear Aegis" Ver. 1.2.1 was released for iOS (https://itunes.apple.com/jp/app/Alice-Gear-Aegis/id1245550834?mt=8) and Android (https://play.google.com/store/apps/details?id=jp.colopl.alice&hl=ja).

The present invention relates to a program and an information processing device.

One example of a device that performs processing in response to touch operations on a touch panel is a game device that charges energy by continuing to touch a charge button on the screen, and performs a specific process that affects an enemy character by releasing the touch operation (for example, non-patent document 1).

"R-TYPE", [online], [searched February 26, 2018], Internet <http://www.konami.jp/products/dl_wiiu_r-type_vc/>

However, "releasing the touch operation", which is the trigger for performing a specific process, is an act of stopping the operation, and is therefore not considered an active operation by the user. In this way, in the game device described in Non-Patent Document 1, a specific process is actively performed based on an operation that cannot be considered active. As a result, a discrepancy occurs between the user's operation and the game process, causing the user to feel uncomfortable. Furthermore, because "releasing the touch operation" is an operation that cannot be considered active, it causes a problem in that it is difficult to find the right timing to perform a specific process. As a result, there is a risk that interest cannot be improved.

The present invention was conceived in light of this situation, and its purpose is to provide a program and an information processing device that can enhance interest.

According to an aspect of an embodiment of the present disclosure, a program is provided. The program causes a computer to function as an execution means for executing control in response to an operation on a touch screen, and the execution means executes a first control in response to receiving a tap operation on the touch screen after a touch operation on the touch screen is continued for a predetermined time, and executes a second control in response to a specific operation on the touch screen that is different from the first control and corresponds to the specific operation, in response to a specific operation different from the tap operation on the touch screen, and executes the second control in response to the specific operation without executing the first control even if the specific operation is received after the touch operation that has been continued for the predetermined time is released, and after the specific operation is received after the touch operation that has been continued for the predetermined time is released, the first control is not executed even if a tap operation is received unless the touch operation that has been continued for the predetermined time is released again.

According to one aspect of an embodiment, an information processing device is provided. The information processing device is an information processing device having a touch screen, and includes an execution means for executing a control according to an operation on the touch screen, and the execution means executes a first control in response to receiving a tap operation on the touch screen after the touch operation is released when the touch operation on the touch screen continues for a predetermined time, executes a second control that is a control different from the first control and corresponds to the specific operation in response to a specific operation on the touch screen that is different from the tap operation, executes the second control according to the specific operation without executing the first control even if the specific operation is received after the release of the touch operation that has continued for the predetermined time, and does not execute the first control after the specific operation is received after the release of the touch operation that has continued for the predetermined time, unless the touch operation that has continued for the predetermined time is released again, even if a tap operation is received.

According to one aspect of an embodiment, a method is provided. The method includes an execution means for executing a control in response to an operation on a touch screen by a computer, the execution means executing a first control in response to receiving a tap operation on the touch screen after a touch operation on the touch screen is continued for a predetermined time and releasing the touch operation, executing a second control in response to a specific operation on the touch screen that is different from the first control and in response to the specific operation, and executing the second control in response to the specific operation without executing the first control even if the specific operation is received after the release of the touch operation that has been continued for the predetermined time.

The present invention can increase interest.

FIG. 2 is a diagram showing the hardware configuration of the game system according to the present embodiment. FIG. 2 is a block diagram showing the functional configuration of a user terminal and a server according to the embodiment. 10 is a flowchart showing a part of the operation of a processor provided in the user terminal. (A) is an illustrative diagram showing an example of a game screen, (B) is an illustrative diagram showing an example of a UI object displayed when locked on to an enemy character in front, (C) is an illustrative diagram showing an example of a UI object displayed when a charge shot is possible at an enemy character in front, (D) is an illustrative diagram showing an example of a UI object displayed when locked on to a nearby enemy character, and (E) is an illustrative diagram showing an example of a UI object displayed when a charge shot is possible at a nearby enemy character.

The game system according to the present disclosure is a system for providing a game to multiple users. The game system will be described below with reference to the drawings. Note that the present invention is not limited to these examples, but is indicated by the claims, and it is intended that all modifications within the meaning and scope equivalent to the claims are included in the present invention. In the following description, the same elements in the description of the drawings will be given the same reference numerals, and redundant description will not be repeated.

<Hardware Configuration of Game System 1>
1 is a diagram showing a hardware configuration of a game system 1. As shown in the figure, the game system 1 includes a plurality of user terminals 100 and a server 200. Each user terminal 100 is connected to the server 200 via a network 2. The network 2 is composed of the Internet and various mobile communication systems constructed by wireless base stations (not shown). Examples of such mobile communication systems include so-called 3G and 4G mobile communication systems, LTE (Long Term Evolution), and wireless networks (e.g., Wi-Fi (registered trademark)) that can be connected to the Internet via a predetermined access point.

The server 200 (computer, information processing device) may be a general-purpose computer such as a workstation or a personal computer. The server 200 comprises a processor 20, a memory 21, a storage 22, a communication IF 23, and an input/output IF 24. These components of the server 200 are electrically connected to each other by a communication bus.

The user terminal 100 (computer, information processing device) may be a mobile terminal such as a smartphone, a feature phone, a PDA (Personal Digital Assistant), or a tablet computer. The user terminal 100 may be a gaming device suitable for playing games. As shown in the figure, the user terminal 100 includes a processor 10, a memory 11, a storage 12, a communication interface (IF) 13, an input/output IF 14, a touch screen 15 (display unit), a camera 17, and a distance measurement sensor 18. These components of the user terminal 100 are electrically connected to each other by a communication bus. Note that the user terminal 100 may include an input/output IF 14 to which a display (display unit) configured separately from the user terminal 100 body can be connected instead of or in addition to the touch screen 15.

As shown in FIG. 1, the user terminal 100 may be configured to be able to communicate with one or more controllers 1020. The controller 1020 establishes communication with the user terminal 100 according to a communication standard such as Bluetooth (registered trademark). The controller 1020 may have one or more buttons, etc., and transmits output values based on user input operations on the buttons, etc., to the user terminal 100. The controller 1020 may also have various sensors such as an acceleration sensor and an angular velocity sensor, and transmits output values of the various sensors to the user terminal 100.

In addition to or in addition to the user terminal 100 being equipped with the camera 17 and distance measurement sensor 18, the controller 1020 may have the camera 17 and distance measurement sensor 18.

For example, when starting a game, the user terminal 100 desirably has the user using the controller 1020 input user identification information, such as the user's name or login ID, via the controller 1020. This enables the user terminal 100 to link the controller 1020 with the user, and to identify which user the output value belongs to based on the source (controller 1020) of the received output value.

When the user terminal 100 communicates with multiple controllers 1020, each user can hold a controller 1020 and realize a multi-play on the single user terminal 100 without communicating with other devices such as the server 200 via the network 2. In addition, the user terminals 100 can realize a multi-play locally by connecting to each other via a wireless standard such as a wireless LAN (Local Area Network) standard (connecting to communicate without going through the server 200). When the above-mentioned multi-play is realized locally by a single user terminal 100, the user terminal 100 may further include at least some of the various functions of the server 200, which will be described later. In addition, when the above-mentioned multi-play is realized locally by multiple user terminals 100, the multiple user terminals 100 may have various functions of the server 200, which will be described later, distributed among them.

Note that even when the above-mentioned multiplay is realized locally, the user terminal 100 may communicate with the server 200. For example, information indicating the results of a game, such as the score or win/loss, may be associated with user identification information and transmitted to the server 200. The controller 1020 may be configured to be detachable from the user terminal 100. In this case, a connection part for the controller 1020 may be provided on at least one surface of the housing of the user terminal 100. When the user terminal 100 and the controller 1020 are connected by a wire via the connection part, the user terminal 100 and the controller 1020 transmit and receive signals via the wire.

As shown in FIG. 1, the user terminal 100 may accept the attachment of a storage medium 1030 such as an external memory card via the input/output IF 14. This allows the user terminal 100 to read programs and data recorded on the storage medium 1030. The program recorded on the storage medium 1030 is, for example, a game program.

The user terminal 100 may store in the memory 11 of the user terminal 100 a game program acquired by communicating with an external device such as the server 200, or may store in the memory 11 a game program acquired by reading it from the storage medium 1030.

As described above, the user terminal 100 includes a communication IF 13, an input/output IF 14, a touch screen 15, a camera 17, and a distance sensor 18 as examples of mechanisms for inputting information to the user terminal 100. Each of the above-mentioned components as input mechanisms can be considered as an operation unit configured to accept input operations by the user.

For example, when the operation unit is composed of at least one of the camera 17 and the distance measurement sensor 18, the operation unit detects an object 1010 in the vicinity of the user terminal 100 and identifies an input operation from the detection result of the object. As an example, a user's hand or a marker of a predetermined shape is detected as the object 1010, and the input operation is identified based on the color, shape, movement, or type of the object 1010 obtained as the detection result. More specifically, when the user's hand is detected from an image captured by the camera 17, the user terminal 100 identifies and accepts a gesture (a series of movements of the user's hand) detected based on the captured image as the user's input operation. Note that the captured image may be a still image or a video.

Alternatively, if the operation unit is configured with a touch screen 15, the user terminal 100 identifies and accepts a user operation performed on the input unit 151 of the touch screen 15 as a user input operation. Alternatively, if the operation unit is configured with a communication IF 13, the user terminal 100 identifies and accepts a signal (e.g., an output value) transmitted from the controller 1020 as a user input operation. Alternatively, if the operation unit is configured with an input/output IF 14, the user terminal 100 identifies and accepts a signal output from an input device (not shown) connected to the input/output IF 14 and different from the controller 1020 as a user input operation.

＜Game Overview＞
The game system 1 is a system for executing a game in which a user is given a reward according to the progress of the game. The game executed in this embodiment is, for example, a 3D shooting action game in which a user set as a newly appointed captain guides girls wearing gear (weapons) and repels enemy characters by making full use of shooting, close-combat attacks, skills, and the like.

The games executed by the game system 1 are not limited to a specific genre, and may be a system for executing games of various genres. For example, the games may be games based on sports such as tennis, table tennis, dodgeball, baseball, soccer, and hockey, puzzle games, quiz games, RPGs, adventure games, simulation games, and training games.

The game system 1 may also be a system for executing a single-play type game. A single-play type game is a game that is executed on a single user terminal 100. In this case, the exchange of information necessary to execute the single-play type game on the user terminal 100 is carried out between the user terminal 100 and the server 200.

The game system 1 may also be a system for executing a multiplayer game. A multiplayer game is a game in which users of multiple user terminals 100 can participate in one game and play against each other or cooperate with each other. In this case, at least a portion of the data related to the game is shared via the server 200 between the user terminal 100 operated by the user and one or more other user terminals 100 operated by one or more other users.

The game system 1 is not limited to single-play or multi-play types, and may be a system for executing games of various play formats.

<Hardware components of each device>
The processor 10 controls the overall operation of the user terminal 100. The processor 20 controls the overall operation of the server 200. The processors 10 and 20 each include a central processing unit (CPU), a micro processing unit (MPU), and a graphics processing unit (GPU).

Processor 10 reads the program from storage 12, which will be described later, and expands it in memory 11, which will be described later. Processor 20 reads the program from storage 22, which will be described later, and expands it in memory 21, which will be described later. Processor 10 and processor 20 execute the expanded programs.

Memories 11 and 21 are main storage devices. Memories 11 and 21 are composed of storage devices such as ROM (Read Only Memory) and RAM (Random Access Memory). Memory 11 provides a working area for processor 10 by temporarily storing programs and various data that processor 10 reads from storage 12, which will be described later. Memory 11 also temporarily stores various data generated while processor 10 is operating according to a program. Memory 21 provides a working area for processor 20 by temporarily storing various programs and data that processor 20 reads from storage 22, which will be described later. Memory 21 also temporarily stores various data generated while processor 20 is operating according to a program.

In this embodiment, the program may be a game program for realizing a game by the user terminal 100. Alternatively, the program may be a game program for realizing the game through cooperation between the user terminal 100 and the server 200. Alternatively, the program may be a game program for realizing the game through cooperation between multiple user terminals 100. In addition, the various data include data related to the game, such as user information and game information, as well as instructions or notifications transmitted and received between the user terminal 100 and the server 200 or between multiple user terminals 100.

Storages 12 and 22 are auxiliary storage devices. Storages 12 and 22 are configured with storage devices such as flash memory or HDDs (Hard Disk Drives). Storage 12 and storage 22 store various data related to the game.

The communication IF 13 controls the transmission and reception of various data in the user terminal 100. The communication IF 23 controls the transmission and reception of various data in the server 200. The communication IFs 13 and 23 control, for example, communication via a wireless LAN (Local Area Network), Internet communication via a wired LAN, a wireless LAN, or a mobile phone network, and communication using short-range wireless communication, etc.

The input/output IF 14 is an interface through which the user terminal 100 accepts data input, and is also an interface through which the user terminal 100 outputs data. The input/output IF 14 may input and output data via a USB (Universal Serial Bus) or the like. The input/output IF 14 may include, for example, a physical button, a camera, a microphone, or a speaker of the user terminal 100.

The input/output IF 24 of the server 200 is an interface through which the server 200 accepts data input, and is also an interface through which the server 200 outputs data. The input/output IF 24 may include, for example, an input unit that is an information input device such as a mouse or keyboard, and a display unit that is a device that displays and outputs images.

The touch screen 15 of the user terminal 100 is an electronic component that combines an input unit 151 and a display unit 152. The input unit 151 is, for example, a touch-sensitive device, and is configured, for example, by a touchpad. The display unit 152 is, for example, configured by a liquid crystal display or an organic EL (Electro-Luminescence) display.

The input unit 151 has a function of detecting the position where a user operation (mainly a physical contact operation such as a touch operation, a slide operation, a swipe operation, or a tap operation) is input on the input surface, and transmitting information indicating the position as an input signal. The input unit 151 may be provided with a touch sensing unit (not shown). The touch sensing unit may be of any type, such as a capacitive type or a resistive film type.

Although not shown, the user terminal 100 may have one or more sensors for identifying the holding orientation of the user terminal 100. The sensor may be, for example, an acceleration sensor or an angular velocity sensor. If the user terminal 100 has a sensor, the processor 10 may identify the holding orientation of the user terminal 100 from the output of the sensor and perform processing according to the holding orientation. For example, when the user terminal 100 is held in portrait orientation, the processor 10 may perform a portrait screen display in which a vertically elongated image is displayed on the display unit 152. On the other hand, when the user terminal 100 is held in landscape orientation, the processor 10 may perform a landscape screen display in which a horizontally elongated image is displayed on the display unit. In this way, the processor 10 may be able to switch between portrait screen display and landscape screen display according to the holding orientation of the user terminal 100.

The camera 17 includes an image sensor and generates a captured image by converting the light incident through the lens into an electrical signal.

The distance measurement sensor 18 is a sensor that measures the distance to the measurement object. The distance measurement sensor 18 includes, for example, a light source that emits pulse-converted light and a light receiving element that receives the light. The distance measurement sensor 18 measures the distance to the measurement object based on the timing of light emission from the light source and the timing of receiving reflected light that is generated when the light emitted from the light source hits the measurement object and is reflected. The distance measurement sensor 18 may have a light source that emits directional light.

Here, an example will be further described in which the user terminal 100 uses the camera 17 and the distance measurement sensor 18 to detect an object 1010 in the vicinity of the user terminal 100, and receives the detection result as a user input operation. The camera 17 and the distance measurement sensor 18 may be provided, for example, on the side of the housing of the user terminal 100. The distance measurement sensor 18 may be provided near the camera 17. For example, an infrared camera can be used as the camera 17. In this case, a lighting device that irradiates infrared rays and a filter that blocks visible light, etc. may be provided on the camera 17. This can further improve the accuracy of object detection based on the image captured by the camera 17, regardless of whether it is outdoors or indoors.

The processor 10 may perform, for example, one or more of the processes shown in (1) to (5) below on the image captured by the camera 17. (1) The processor 10 performs image recognition processing on the image captured by the camera 17 to determine whether or not the captured image includes the user's hand. The processor 10 may use, for example, a pattern matching technique as an analysis technique employed in the above-mentioned image recognition processing. (2) The processor 10 also detects a user's gesture from the shape of the user's hand. The processor 10, for example, determines the number of fingers of the user (the number of fingers extended) from the shape of the user's hand detected from the captured image. The processor 10 further determines the gesture made by the user from the determined number of fingers. For example, if the number of fingers is five, the processor 10 determines that the user has made a "paper" gesture. If the number of fingers is zero (no fingers are detected), the processor 10 determines that the user has made a "rock" gesture. Furthermore, when the number of fingers is two, the processor 10 determines that the user has made a "scissors" gesture. (3) The processor 10 performs image recognition processing on the image captured by the camera 17 to detect whether the user's fingers are in a state where only the index finger is raised, or whether the user's fingers are moving like flicking. (4) The processor 10 detects the distance between the object 1010 (such as the user's hand) near the user terminal 100 and the user terminal 100 based on at least one of the image recognition result of the image captured by the camera 17 and the output value of the distance measuring sensor 18. For example, the processor 10 detects whether the user's hand is near the user terminal 100 (e.g., a distance less than a predetermined value) or far away (e.g., a distance equal to or greater than a predetermined value) based on the size of the shape of the user's hand identified from the image captured by the camera 17. Note that when the captured image is a video, the processor 10 may detect whether the user's hand is approaching or moving away from the user terminal 100. (5) When it is determined that the distance between the user terminal 100 and the user's hand is changing while the user's hand is detected based on the image recognition result of the image captured by the camera 17, the processor 10 recognizes that the user is waving his/her hand in the capturing direction of the camera 17. When an object is sometimes detected and sometimes not detected by the distance measuring sensor 18, which has a higher directivity than the capturing range of the camera 17, the processor 10 recognizes that the user is waving his/her hand in a direction perpendicular to the capturing direction of the camera.

In this way, the processor 10 detects whether the user has clenched his/her hand (whether it is a "rock" gesture or another gesture (e.g., "paper")) by image recognition of the image captured by the camera 17. The processor 10 also detects how the user is moving the hand along with the shape of the user's hand. The processor 10 also detects whether the user is moving the hand closer to or farther away from the user terminal 100. Such an operation can correspond to an operation using a pointing device such as a mouse or a touch panel. For example, the user terminal 100 moves the pointer on the touch screen 15 in response to the movement of the user's hand and detects the user's "rock" gesture. In this case, the user terminal 100 recognizes that the user is continuing the selection operation. The continuation of the selection operation corresponds, for example, to the mouse being clicked and kept pressed, or to the touch panel being kept touched after a touchdown operation. Furthermore, when the user moves his/her hand further while the user terminal 100 has detected the user gesture "rock," the user terminal 100 can recognize such a series of gestures as an operation corresponding to a swipe operation (or a drag operation). Furthermore, when the user terminal 100 detects a gesture of the user flicking his/her fingers based on the detection result of the user's hand from the image captured by the camera 17, the user terminal 100 may recognize the gesture as an operation corresponding to a mouse click or a tap operation on a touch panel.

<Functional Configuration of Game System 1>
2 is a block diagram showing the functional configuration of the server 200 and the user terminal 100 included in the game system 1. Each of the server 200 and the user terminal 100 may include a functional configuration (not shown) required to function as a general computer, and a functional configuration required to realize well-known functions in a game.

The user terminal 100 functions as an input device that accepts input operations from the user, and as an output device that outputs game images and sounds. The user terminal 100 functions as a control unit 110 and a storage unit 120 through cooperation of the processor 10, memory 11, storage 12, communication IF 13, input/output IF 14, etc.

The server 200 has a function of communicating with each user terminal 100 and assisting the user terminal 100 in progressing through the game. If the game is a multiplayer game, the server 200 may have a function of communicating with each user terminal 100 participating in the game and mediating interactions between the user terminals 100. The server 200 functions as a control unit 210 and a storage unit 220 through cooperation of the processor 20, memory 21, storage 22, communication IF 23, input/output IF 24, etc.

The memory unit 120 stores a game program 121, game information 122, and user information 123. The memory unit 220 stores a game program 221, game information 222, and user information 223. The game program 121 is a game program executed by the user terminal 100. The game program 221 is a game program executed by the server 200. The game information 122 is data that the control unit 110 refers to when executing the game program 121. The game information 222 is data that the control unit 210 refers to when executing the game program 221. The user information 123 and 223 are data related to the user's account. In the memory unit 220, the game information 222 and the user information 223 are stored for each user terminal 100.

(Functional configuration of server 200)
The control unit 210 performs overall control of the server 200 by executing the game program 221 stored in the storage unit 220. For example, the control unit 210 transmits various data, programs, and the like to the user terminal 100. The control unit 210 receives a part or all of the game information or user information from the user terminal 100. If the game is a multiplayer game, the control unit 210 may receive a request for multiplayer synchronization from the user terminal 100 and transmit data for synchronization to the user terminal 100.

The control unit 210 functions according to the description of the game program 221. Depending on the nature of the game being executed, the control unit 210 can also function as other functional blocks (not shown) to support the progress of the game on the user terminal 100.

(Functional configuration of user terminal 100)
The control unit 110 executes a game program 121 stored in the storage unit 120 to exercise overall control over the user terminal 100. For example, the control unit 110 progresses the game in accordance with the game program 121 and user operations. Furthermore, while the game is progressing, the control unit 110 communicates with the server 200 as necessary to transmit and receive information.

The control unit 110 functions as an operation reception unit 111, a user interface (hereinafter, UI) control unit 112, an animation generation unit 113, a display control unit 114, and a game progression unit 115 according to the description of the game program 121. The control unit 110 can also function as other functional blocks (not shown) in order to progress the game according to the nature of the game being executed.

The operation reception unit 111 detects and receives user input operations on the input unit 151. The operation reception unit 111 determines what kind of input operation has been performed based on the actions performed by the user on the touch screen 15 and the console via the other input/output IF 14, and outputs the results to each element of the control unit 110.

For example, the operation reception unit 111 receives an input operation on the input unit 151, detects the coordinates of the input position of the input operation, and identifies the type of the input operation. The operation reception unit 111 identifies, for example, a touch operation, a slide operation, a swipe operation, a drag operation, and a tap operation as the type of input operation. Furthermore, when a continuously detected input is interrupted, the operation reception unit 111 detects that the contact input from the touch screen 15 has been released.

The UI control unit 112 controls UI objects to be displayed on the display unit 152 in order to construct a UI. UI objects are tools that allow the user to input to the user terminal 100 necessary for the progress of the game, or tools that allow the user to obtain information from the user terminal 100 that is output during the progress of the game. Examples of UI objects include, but are not limited to, icons, buttons, lists, and menu screens.

The animation generation unit 113 generates animations showing the motion of various objects based on the control modes of the various objects. For example, it may generate animations showing a girl fighting an enemy character in battle.

The display control unit 114 outputs to the display unit 152 of the touch screen 15 a game screen reflecting the results of the processing performed by each of the above-mentioned elements. The display control unit 114 may display on the display unit 152 a game screen including the animation generated by the animation generation unit 113. The UI control unit 112 may also draw the above-mentioned UI objects superimposed on the game screen.

Hereinafter, the operation reception unit 111 detecting and receiving an input operation to the input unit 151 will also be described simply as "the input operation is received." Additionally, the output of various game screens by other functional blocks to the display unit 152 via the display control unit 114 will also be described simply as "displaying."

The game progression unit 115 performs various processes related to the progression of the game. For example, the game progression unit 115 interprets the user's instructions indicated by the coordinates of the input position of the input operation received by the operation reception unit 111 and the type of operation, and performs a process to progress the game based on the interpretation. Also, for example, the game progression unit 115 adds, updates, or deletes game information 122 or user information 123 according to the progress of the game. Also, for example, the game progression unit 115 performs various judgment processes related to the progress of the game.

For example, in a game where a quest is provided in which a playable character (in this embodiment, one of the girls guided by the user) operated by the user fights an enemy character, the game progression unit 115 progresses the battle by determining the actions of the playable character based on the user's operation. In this case, the game progression unit 115 also determines whether the playable character or the enemy character has won based on the progress of the battle.

Note that the functions of the server 200 and the user terminal 100 shown in FIG. 2 are merely examples. The server 200 may have at least some of the functions of the user terminal 100. The user terminal 100 may also have at least some of the functions of the server 200. Furthermore, devices other than the user terminal 100 and the server 200 may be components of the game system 1, and the other devices may execute some of the processing in the game system 1. That is, the computer that executes the game program in this embodiment may be any of the user terminal 100, the server 200, and other devices, or may be realized by a combination of multiple devices.

<Processing flow and screen examples>
Next, a process flow of attack control for controlling normal shots and charge shots performed on enemy characters appearing in each stage will be described among the processes executed by the user terminal 100 based on the game program 121. The attack control process will be described using the flowchart shown in Figure 3, the screen example shown in Figure 4(A), the locked-on character LC1 shown in Figures 4(B) to 4(D), and the locked-on character LC2 shown in Figures 4(E) to 4(F).

A normal shot is a shot that fires one bullet with normal destructive power, and a charge shot is a shot that fires one or more bullets with great destructive power. In other words, the attack control of a charge shot is a control that gives a more advantageous effect to the user than the attack control of a normal shot. Furthermore, the attack control process is executed by the operation reception unit 111, the UI control unit 112, the display control unit 114, etc. Furthermore, in the following explanation, the flow of a series of processing steps explained using a flowchart is described as being executed by the user terminal 100, but at least a part of these processing steps may be executed by the server 200.

The attack control process is executed in a scene in which the playable character PC1 fights enemy characters EC1 to EC3, as shown in FIG. 4(A). According to FIG. 4(A), a virtual camera is placed behind the playable character PC1, and the battle scene is displayed from the viewpoint of the virtual camera. As an example of a battle scene, FIG. 4(A) shows a scene in which the playable character PC1 and enemy characters EC1 to EC3 are all flying in a mountainous area. In the battle scene, the playable character PC1 uses the shot gear he is holding to shoot down the enemy characters EC1 to EC3.

The bottom of the screen displays an indicator showing the remaining HP (health points) of the playable character PC1, and UI objects representing the skills that the playable character PC1 can use. Also, the left side of the screen displays a facial image of another character (a girl). The other character is a character who can team up with the playable character PC1 and fight in place of the playable character PC1 if, for example, the playable character PC1 is defeated.

The attack control process will be described with reference to FIG. 3. In step S01, an enemy character flying approximately in front of the playable character PC1 is locked on as an attack target, and the lock-on is notified. Note that locking on means continuously tracking the attack target.

If there is one flying enemy character, that enemy character will be locked on as the main attack target. On the other hand, if there are two or more flying enemy characters, one of the enemy characters will be locked on as the main attack target, and the other enemy characters will be locked on as sub-attack targets.

For enemy characters locked on as the main attack target, the lock-on character LC1 is displayed at the position of the enemy character, and the display position of the lock-on character LC1 is moved so as to pursue the enemy character. For enemy characters locked on as the sub-attack target, the lock-on character LC2 is displayed at the position of the enemy character, and the display position of the lock-on character LC2 is moved so as to pursue the enemy character.

In the example of FIG. 4(A), enemy character EC1 is locked on as the main attack target, and enemy characters EC2 and EC3 are locked on as sub-attack targets. Locked-on character LC1 is composed of a circular portion R1 that is larger in diameter than the display size of the enemy character, and a shot count indicator D1 located to the left of the circular portion. Locked-on character LC2 is composed of a rectangular frame that is smaller than locked-on character LC1, and the character string ENEMY.

The shot count indicator D1 is an indicator that shows the number of bullets (shot count) that will be fired by a charge shot. The illumination state of the shot count indicator D1 changes in four stages, from level 1 to level 4, depending on the set number of shots.

In step S02, it is determined whether or not a position on the touch screen 15 has been touched on (whether or not a touch operation has started) based on an input signal from the touch screen 15. If it is determined that a position has been touched on, then in step S03, it is started to measure the time during which the touch-on continues (touch time), and in step S04, it is determined whether or not the measured time has reached or exceeded a predetermined charge completion time (e.g., 0.5 seconds).

If it is not determined that the touch time is equal to or longer than the charge completion time, then in step S05, a process according to the touch position is executed. For example, if a drag operation is performed while touching on, a process of moving the position of the playable character PC1, a process of moving the background image, a process of moving the orientation of the virtual camera, and the like is executed according to the direction of the drag operation and the movement distance of the touch position. In step S06, it is determined whether or not the touch has been released (whether or not the touch operation has ended) based on the input signal from the touch screen 15, and if it is not determined that the touch has been released, the process returns to step S04.

In contrast, when it is determined that touch-off has occurred, normal shot processing is executed in step S07. Specifically, for example, one bullet with normal destructive force is fired from the shot gear held by the playable character PC1 toward the main attack target. When the normal shot processing is completed, the process returns to step S01. In step S01, lock-on is executed again to an enemy character flying approximately in front of the playable character PC1. If the main attack target is shot down by the normal shot processing, a different enemy character is locked on as the main attack target. On the other hand, if the main attack target cannot be shot down by the normal shot processing, the same enemy character continues to be locked on as the main attack target.

If it is determined in step S04 that the touch time is equal to or greater than the charge completion time, the process proceeds to step S08 to prepare for the charge shot. In step S08, the number of shots in the charge shot is set to one, and a notification is issued that charging is complete and the number of shots has been set to one.

The notification is made by transitioning the display mode of the locked-on character LC1 from FIG. 4(B) to FIG. 4(C). As shown in FIG. 4(C), the word "Charge Complete" is written slightly below the center of the circular portion that constitutes the locked-on character LC1 to notify that charging is complete, and the shot count indicator D1 is lit at level 1 to notify that the number of shots has been set to one.

In step S09, it is determined whether or not the touch has been released (whether or not the touch operation has ended) based on the input signal from the touch screen 15. If it is not determined that the touch has been released, the process proceeds to step S10, where the number of shots is increased by one after a predetermined time (e.g., 0.1 seconds) has elapsed, and the increased number of shots is notified. Therefore, if touch-on is continued after the display state of the locked-on character LC1 has transitioned to FIG. 4(C), the number of shots is increased from one to two, and the illumination state of the shot count indicator D1 transitions from level 1 to level 2 (see FIG. 4(D)). Note that in this embodiment, the upper limit of the number of shots is four. Therefore, after the number of shots has increased to four, the process of step S10 is not executed.

In step S11, processing is performed according to the touch position. For example, if a drag operation is performed while touching is on, processing is performed to move the position of the playable character PC1 according to the direction of the drag operation and the movement distance of the touch position.

In step S12, it is determined whether or not there are any sub-attack targets that are not targets for shots (sub-attack targets for which no notification of a shot target has been made, as described below). If it is determined that there are any sub-attack targets that are not targets for shots, the process proceeds to step S13, where it is determined whether or not there are three or fewer sub-attack targets that are targets for shots. If it is determined that there are three or fewer sub-attack targets that are targets for shots, the process proceeds to step S14, where one of the sub-attack targets that is not targets for shots is designated as a shot target, and the designated shot target is notified.

The shot target is notified by transitioning the display mode of the locked-on character LC2 from FIG. 4(E) to FIG. 4(F). The display mode of the locked-on character LC2 transitions from a rectangular frame and the character string ENEMY, as shown in FIG. 4(E), to a mode in which the shapes "(" and ")" are added to the left and right of the rectangular frame, and a check mark is added in the center of the rectangle, as shown in FIG. 4(F).

If it is not determined in step S12 that there are any sub-attack targets that are not the target of a shot, if it is not determined in step S13 that there are three or fewer sub-attack targets that are the target of a shot, or if the processing of step S14 is completed, the process returns to step S09.

If it is determined in step S09 that touch-off has occurred, it is determined in step S15 whether a predetermined grace period (e.g., one second) has elapsed since touch-off. If it is determined that the predetermined grace period has elapsed since touch-off, the charge completion notification is terminated in step S19. Specifically, the display mode of locked-on character LC1 is returned from FIG. 4(C) or FIG. 4(D) to FIG. 4(B), and the display mode of locked-on character LC2 is returned from FIG. 4(F) to FIG. 4(E). Furthermore, the number of shots for the charge shot is cleared. When the processing of step S19 is completed, the process returns to step S02.

If it is not determined in step S15 that the predetermined grace period has elapsed since the touch-off, it is determined in step S16 whether or not a touch-on has been performed again. If it is not determined that a touch-on has been performed again, the process returns to step S15, and if it is determined that a touch-on has been performed again, the process proceeds to step S17.

In step S17, it is determined whether the second touch-on constitutes a tap operation (whether the touch-off occurs quickly (within a predetermined time) after the second touch-on). If it is not determined that the second touch-on constitutes a tap operation, the process returns to step S02 via step S19. The process moves from step S17 to step S19 when the touch operation continues without being off until a predetermined time has elapsed since the second touch-on, which corresponds to, for example, the touch operation constituting a drag operation or a swipe operation. After returning to step S02, the processes of steps S03 to S07 are executed according to the operation determined not to constitute a tap operation, such as the drag operation or the swipe operation.

Therefore, if a drag operation, swipe operation, or the like is performed before the specified grace period has elapsed after a touch operation that lasted for a period equal to or longer than the charge completion time is released, the process will not proceed to step S18, and processing such as step S05 will be executed.

If it is determined in step S17 that the second touch-on constitutes a tap operation, a charge shot process is executed in step S18. Specifically, bullets of great destructive power are fired from the shot gear held by the playable character PC1. The number of bullets fired corresponds to the illuminated state of the shot count indicator D1. Since the number of shots increases the longer the touch time is, the effect of repelling the enemy character is determined by the duration of the touch operation as well as the destructive power of the bullets. In other words, the effect of repelling the enemy character is greater in the charge shot process than in the normal shot process, and further increases the longer the touch operation is continued.

If there is no sub-attack target, all fired bullets are directed at the main attack target. Even if there is a sub-attack target, if only one bullet is fired, that bullet is directed at the main attack target. Furthermore, if there is a sub-attack target that is the shot target, bullets are fired at both the main attack target and the sub-attack target that is the shot target. When the processing of step S18 is completed, the process returns to step S01.

<Effects of this embodiment>
According to this embodiment, the charge shot process is executed based on the active operation of tapping after the touch operation is released, so the user can play the game without feeling uncomfortable. More specifically, the user can fire a shot with great destructive power at the timing he or she desires. As a result, the interest of the game can be improved.

Furthermore, according to this embodiment, when a drag operation or a swipe operation is performed within a predetermined grace period after a touch operation that lasts for a period of time equal to or longer than the charge completion time is released, the charge shot process is not executed. A drag operation or a swipe operation is performed, for example, in a situation where a bullet is fired from an enemy character after a touch operation that lasts for a period of time equal to or longer than the charge completion time is released, and the bullet from the enemy character cannot be avoided by performing a tap operation. When an evasive action is performed by a drag operation or a swipe operation, the relative position between the enemy character and the operable character PC1 changes. In this embodiment, in order to perform a charge shot after an evasive action, another touch operation that lasts for a period of time equal to or longer than the charge completion time is required. This allows the user to progress through the game without feeling uncomfortable.

In addition, according to this embodiment, when the touch time is equal to or longer than the charge completion time, the user is notified that charging is complete. This allows the user to time the charge shot based on this notification.

Furthermore, according to this embodiment, if a drag operation is performed (moving the touch position while charging) while a touch operation before being released is still continuing, the playable character PC1 moves in the direction of the drag operation. This allows, for example, charging while avoiding bullets and attacks from enemy characters.

In addition, according to this embodiment, the number of bullets fired by the charge shot process increases the longer the touch operation is continued. As a result, the effect given to the user (the effect of repelling enemy characters) increases the longer the touch operation is continued. One example of a situation in which the duration of the touch operation is long is when fighting while avoiding attacks from multiple enemy characters. Increasing the number of bullets in the charge shot in such a case makes it possible to repel multiple enemy characters at once, allowing the user to fight in the way they wish.

<Modification>
Modifications of the above-described embodiment are listed below.

(1) In the above embodiment, an example was described in which the effect given to the user by the charge shot process is uniform regardless of the length of time between the release of the touch operation and the acceptance of the tap operation. However, the effect given to the user by the charge shot process may be made different depending on the length of time between the release of the touch operation and the acceptance of the tap operation. For example, the shorter the time between the release of the touch operation and the tap operation, the more powerful the destructive power of the bullets may be or the number of bullets may be increased, and conversely, the longer the time, the more powerful the destructive power of the bullets may be or the number of bullets may be increased. In this way, the effect given to the user can be made different depending on the timing of the re-tap operation, which can improve the interest of the game.

(2) In the above embodiment, the sizes of the locked-on characters LC1 and LC2 are fixed. However, the size of the locked-on character LC1 may be changed depending on the distance to the main attack target, and the size of the locked-on character LC2 may be changed depending on the distance to the sub-attack target. When changing the size, only the size of one of the locked-on characters LC1 and LC2 may be changed depending on the distance.

(3) In the above embodiment, when a drag operation is performed while a touch operation is continuing, the playable character PC1 is moved. However, in response to a drag operation while a touch operation is continuing, the viewpoint of the virtual camera may be changed to a viewpoint from the face of the playable character PC, the girl, or to a viewpoint from above or to the side of the playable character PC. Furthermore, such a change of viewpoint may be performed together with the movement of the playable character PC1.

(4) In the above embodiment, in response to a tap operation after a touch operation that lasts for a period of time equal to or longer than the charge completion time, a bullet of great destructive power is fired from the gear used by the playable character PC1. However, if the face image of another character displayed on the left side of the screen is touched by a drag operation while a touch operation is continuing, the character corresponding to the touched face image may be made to appear as the playable character PC1, and in response to a tap operation after the touch operation is released, a bullet of great destructive power may be fired from the gear used by the replaced character.

(5) In the above embodiment, the charge shot process is executed in response to a tap operation after the touch operation for a period of time equal to or longer than the charge completion time is released. However, instead of a tap operation, the charge shot process may be executed in response to a specific voice uttered by the user, an operation of shaking the user terminal 100, a gesture made to the camera 17 (for example, moving a finger or eye in a specific manner, or blinking an eye in a specific manner), or the like.

(6) In the above embodiment, the charge shot process is executed in response to a touch operation that lasts for a period of time equal to or longer than the charge completion time and a subsequent tap operation. However, the charge shot process may be made executable by performing a drag operation that draws a specific trajectory (e.g., "S"), and the charge shot process may be executed by a tap operation after the drag operation is released. In other words, a specific game control such as the charge shot process may be executed by accepting a specific operation, such as a touch operation that draws a specific trajectory, rather than the duration of the touch operation. In this case, the destructive power of the charged shot bullet may be made different depending on the trajectory that is drawn.

(7) In the above embodiment, in order to execute the charge shot process, it is necessary to perform a touch operation for a period of time equal to or longer than the charge completion time, and then perform a tap operation within a predetermined grace period after the touch operation is released. Here, the length of the charge completion time or grace period may be varied depending on the stage, the level of the enemy character, or the level of the gear used by the playable character PC1.

(8) In the above embodiment, the charge completion time and the grace period are fixed regardless of whether or not a charge shot process is performed. However, if the previous charge shot process is canceled (if a tap operation is not performed within the grace period after a touch operation lasting longer than the charge completion time is released), the length of the current charge completion time or grace period may be shortened.

(9) In the above embodiment, the length of the charge completion time and the grace period is fixed regardless of the type of enemy character or the type of gear used by the playable character PC1. However, the length of the charge completion time or the grace period may be varied depending on the type of enemy character or the type of gear used by the playable character PC1, for example, by shortening the length of the charge completion time or lengthening the length of the grace period the better the compatibility between the enemy character and the gear used by the playable character PC1.

(10) In the above embodiment, in the charge shot process, a bullet with great destructive power is fired from the shot gear held by the playable character PC1. However, if a touch operation lasts for a period of time equal to or longer than the charge completion time, and the UI object for the skill displayed at the bottom of the screen is touched by a tap operation, the skill may be made to exert even greater power.

(11) In the above embodiment, the length of the charge completion time and the grace period is fixed regardless of the number of normal shot processes performed before the long touch operation for the charge shot. However, the length of the charge completion time or the grace period may be varied depending on the number of normal shot processes performed between the previous charge shot process and the long touch operation for the current charge shot.

(12) In the above embodiment, the length of the charge completion time and the grace period is fixed regardless of the number of enemy characters that appear before the current stage is cleared. However, the length of the charge completion time or the grace period may be varied depending on the number of enemy characters that appear before the current stage is cleared. Also, if a time limit is set for clearing the current stage, the length of the charge completion time or the grace period may be varied depending on the length of the time limit or the remaining time.

(13) In the above embodiment, the length of the charge completion time and the grace period is fixed regardless of the rarity of the gear used by the playable character PC1. However, the length of the charge completion time or the grace period may be varied depending on the rarity of the gear.

(14) In the above embodiment, the charge shot process is executed in response to a touch operation that lasts for a period of time equal to or longer than the charge completion time and a subsequent tap operation, regardless of the type of gear used by the playable character PC1. However, depending on the type of gear used by the playable character PC1, the charge shot process may be executed at the time when a touch operation that lasts for the charge completion time is performed (i.e., without waiting for the release of the touch operation and the subsequent tap operation). In this case, for a certain gear, the charge shot process is executed in response to a tap operation within a predetermined grace period after the release of the touch operation that lasts for the charge completion time, and for another gear, the charge shot process is executed when the duration of the touch operation reaches the charge completion time.

(15) In the above embodiment, a charge shot process is given as an example of a specific game control. However, the specific game control is not limited to this, and may be, for example, a control for a player character to perform a special move in a game in which the player fights an enemy character, or a control for accelerating a car that is the player character in a racing game.

(16) In the above embodiment, even if a specific instruction is given after a predetermined grace period has elapsed since the touch operation spanning the charge completion time was released, the specific game control is not executed. However, the specific game control may be executed by giving a specific instruction regardless of the time that has elapsed since the touch operation was released.

(17) In the above embodiment, if an operation other than a tap operation (e.g., a drag operation, etc.) is performed after the touch operation for the charge completion time is released, the specific game control is not executed. However, by receiving some kind of instruction from the user (which may include, for example, a drag operation as long as it is a predetermined operation), the specific game control may be executed regardless of the type of the instruction.

<Additional Notes>
The matters described in the above embodiments will be supplemented below.

(Appendix 1)
According to one aspect of an embodiment disclosed herein, there is provided a game program executed on a computer (user terminal 100 of FIG. 1) having a processor, a memory, and a touch screen, the game program causing the processor to execute a first step (S04 of FIG. 3) of determining whether a touch operation on the touch screen has continued for a predetermined period of time, and a second step (S18 of FIG. 3) of executing a specific game control based on a specific instruction received from a user after the touch operation determined in the first step to have continued for the predetermined period of time is released.

(Appendix 2)
(Supplementary Note 1) In the second step, the specific game control is executed when the specific instruction is accepted before a predetermined time has elapsed since the release of the touch operation.

(Appendix 3)
In (Supplementary Note 1) or (Supplementary Note 2), the effect given to the user by the specific game control differs depending on the time from when the touch operation is released to when the specific instruction is accepted.

(Appendix 4)
In any of (Supplementary Note 1) to (Supplementary Note 3), the specific instruction is a tap operation on the touch screen, and the second step does not execute the specific game control when an operation other than the tap operation is performed within a predetermined time period after the touch operation is released.

(Appendix 5)
In any one of (Supplementary Note 1) to (Supplementary Note 4), the game program causes the processor to execute a third step (S08 in FIG. 3) of notifying, in accordance with the determination result of the first step, that a touch operation on the touch screen has continued for the predetermined time.

(Appendix 6)
In any one of (Supplementary Note 1) to (Supplementary Note 5), the game program causes the processor to execute a fourth step (S07 in FIG. 3) of executing a game control different from the specific game control when the touch operation is released before it is determined in the first step that the touch operation has continued for the predetermined time period.

(Appendix 7)
In (Supplementary Note 6), the specific game control executed in the second step is a control that provides a more advantageous effect to the user than the game control executed in the fourth step.

(Appendix 8)
In any one of (Supplementary Note 1) to (Supplementary Note 7), the second step does not execute game control when the touch operation determined to have continued for the predetermined time is released.

(Appendix 9)
In any one of (Supplementary Note 1) to (Supplementary Note 8), the game program causes the processor to execute a fifth step (S06, S11 in FIG. 3) of executing game control according to the manner of the touch operation on the touch screen while the touch operation is continuing.

(Appendix 10)
In any one of (Supplementary Note 1) to (Supplementary Note 9), the effect given to the user by the specific game control varies depending on the duration of the touch operation.

(Appendix 11)
According to one aspect of one embodiment, there is provided a gaming method executed by a computer (user terminal 100 of FIG. 1) having a processor, memory, and a touch screen, the gaming method including a first step (S04 of FIG. 3) of the computer determining whether a touch operation on the touch screen has continued for a predetermined period of time, and a second step (S18 of FIG. 3) of executing specific game control based on a specific instruction received from a user after the touch operation determined in the first step to have continued for the predetermined period of time is released.

(Appendix 12)
According to one aspect of one embodiment, an information processing device (user terminal 100 in FIG. 1) includes a touch screen (15 in FIG. 1), a memory unit (11 in FIG. 1) that stores a game program, and a control unit (110 in FIG. 2) that controls operation of the information processing device by executing the game program, wherein the control unit executes a first step (S04 in FIG. 3) of determining whether a touch operation on the touch screen has continued for a predetermined period of time, and a second step (S18 in FIG. 3) of executing specific game control based on a specific instruction received from a user after the touch operation determined in the first step to have continued for the predetermined period of time is released.

[Software implementation example]
The control blocks of the control unit 110 (in particular, the operation reception unit 111, the UI control unit 112, the animation generation unit 113, the display control unit 114, and the game progression unit 115) may be realized by a logic circuit (hardware) formed in an integrated circuit (IC chip) or the like, or may be realized by software using a CPU (Central Processing Unit).

In the latter case, the information processing device equipped with the control unit 110 includes a CPU that executes the commands of a program, which is software that realizes each function, a ROM (Read Only Memory) or storage device (these are referred to as "recording media") in which the program and various data are recorded so as to be readable by the computer (or CPU), and a RAM (Random Access Memory) in which the program is expanded. The object of the present invention is achieved by the computer (or CPU) reading and executing the program from the recording medium. As the recording medium, a "non-transient tangible medium" such as a tape, a disk, a card, a semiconductor memory, or a programmable logic circuit can be used. The program may also be supplied to the computer via any transmission medium (such as a communication network or a broadcast wave) capable of transmitting the program. One aspect of the present invention may also be realized in the form of a data signal embedded in a carrier wave in which the program is embodied by electronic transmission.

The embodiments disclosed herein should be considered in all respects as illustrative and not restrictive. The scope of the present invention is indicated by the claims, not the above description, and is intended to include all modifications within the meaning and scope of the claims.

1 Game system, 2 Network, 10, 20 Processor, 11, 21 Memory, 12, 22 Storage, 13, 23 Communication IF (operation unit), 14, 24 Input/output IF (operation unit), 15 Touch screen (display unit, operation unit), 17 Camera (operation unit), 18 Distance measurement sensor (operation unit), 100 User terminal (information processing device), 110, 210 Control unit, 111 Operation reception unit, 112 Display control unit, 113 UI control unit, 114 Animation generation unit, 115 Game progress unit, 120, 220 Storage unit, 121, 221 Game program, 122, 222 Game information, 123, 223 User information, 151 Input unit (operation unit), 152 Display unit, 200 Server, 1010 Object, 1020 Controller (operation unit), 1030 Storage medium

Claims (5)

Computer,
The control means functions as an execution means for executing control in response to an operation on the touch screen;
The execution means includes:
when a touch operation on the touch screen is continued for a predetermined time, a first control is executed in response to a tap operation on the touch screen being received after the touch operation is released;
In response to a specific operation on the touch screen that is different from the tap operation, a second control that is different from the first control and corresponds to the specific operation is executed, and even if the specific operation is accepted after the touch operation that has been continued for the predetermined time is released, the second control corresponding to the specific operation is executed without executing the first control;
The program executes a second control according to the specific operation after the touch operation that has been continued for the predetermined time is released and the specific operation is accepted, but does not execute the first control even if the tap operation is accepted after the second control has been executed and the touch operation that has been continued for the predetermined time is released again. The program according to claim 1, wherein the effect given to the user by the first control differs depending on the time from when the touch operation is released to when the tap operation is accepted. The program according to claim 1 or 2, wherein the effect given to the user by the first control varies depending on the duration of the touch operation. The program according to any one of claims 1 to 3, wherein the execution means executes a control different from the first control when a tap operation on the touch screen is received but the touch operation that has continued for the predetermined time has not been released. An information processing device equipped with a touch screen,
an execution means for executing a control in response to an operation on the touch screen,
The execution means includes:
when a touch operation on the touch screen is continued for a predetermined time, a first control is executed in response to a tap operation on the touch screen being received after the touch operation is released;
In response to a specific operation on the touch screen that is different from the tap operation, a second control that is different from the first control and corresponds to the specific operation is executed, and even if the specific operation is accepted after the touch operation that has been continued for the predetermined time is released, the second control corresponding to the specific operation is executed without executing the first control;
The information processing device executes a second control according to the specific operation after the touch operation that has been continued for the predetermined time is released and the specific operation is accepted, but does not execute the first control even if the tap operation is accepted after the second control has been executed and the touch operation that has been continued for the predetermined time is released again.

Images