JP2022078152A - Game program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a game program that has simple operability and can operate an object at will.

SOLUTION: A computer having a touch display is allowed to execute a method including a step of detecting optional position information on the touch display and acquiring touch position information repeatedly, a step of determining first operation information on the basis of a predetermined number of pieces of touch position information, a step of executing first operation to a moving body within a game space on the basis of the first operation information, a step of determining touch-off from the touch display and determining second operation information by using touch position information immediately before the touch-off, and a step of determining flick operation on the basis of the second operation information, and canceling first operation according to flick operation, and performing second operation to a moving body based on the second operation information, and the first operation operates the moving body so as to move within a game space along with characters and the second operation operates the moving body so as to travel a game space separately from characters.

SELECTED DRAWING: Figure 10

COPYRIGHT: (C)2022,JPO&INPIT

Description

The present invention relates to a game program that operates an object in a game space in response to a specific touch operation on a touch display.

Recently, game programs using mobile terminals (for example, smartphones) equipped with touch displays have been distributed to users via the Internet. Many game programs control the movement of objects in the game space through touch operations on the touch display. Patent Document 1 discloses a technique in a soccer game in which a user advances the game while designating a character or a position to be operated on a touch display each time. In particular, a technique for performing an action (pass, dribble, shoot, etc.) on a moving body according to a designation of a moving destination of the moving body (ball) by a touch operation and a touch operation type is disclosed.
Further, in Patent Document 2, when the touch operation is an operation in which the touch operation moves by a predetermined stroke distance at a predetermined speed or more from the touch down, the touch operation is determined as a flick operation, and the player character is set as a movement target. The technology to move towards is disclosed.

Japanese Unexamined Patent Publication No. 2014-76943 International Publication No. 2013-024771 Pamphlet

In a game application that requires many characters to move together with a moving body, such as a soccer game, it is required to provide a user with a simple and intuitive touch operability. An object of the present invention is to provide a game program capable of operating a game object at will while maintaining simple operability.

According to the present invention, when executed by a computer provided with a touch display, the computer detects arbitrary position information on the touch display and repeatedly acquires the touch position information at a predetermined frame rate, and a predetermined step. Based on the number of touch position information, the step of determining the first operation information, the step of performing the first operation on the moving body in the game space based on the first operation information, and the touch-off from the touch display are determined. A step to determine the second operation information using the touch position information in at least one frame immediately before the touch-off, a step to determine the flick operation based on the second operation information, and a step according to the flick operation. The method including the step of canceling the first operation and performing the second operation to the moving body based on the second operation information is executed, and the first operation moves the moving body together with the character in the game space. A game program is obtained in which the moving body is operated so that the second operation moves in the game space away from the character.

INDUSTRIAL APPLICABILITY According to the present invention, a game program capable of operating a game object at will while maintaining simple operability is provided.

It is a block diagram of the basic configuration of a computer in one embodiment. It is a block diagram of the detailed configuration of a computer in one embodiment. It is an example of a game screen generated by the game program of one embodiment. It is a schematic operation example for an object according to one embodiment. It is a flow chart which shows the outline of the whole processing by one Embodiment. It is a schematic arrangement diagram of the touch position information acquired by one Embodiment. It is a schematic arrangement diagram of the touch position information acquired by one Embodiment. It is a flow chart which shows the detailed processing example by one Embodiment. It is a flow chart which shows the detailed processing example by one Embodiment. It is a graph example of the slide operation information determined by one Embodiment. It is a flow chart which shows the detailed processing example by one Embodiment. It is a schematic diagram which shows the example of the area in the field of one Embodiment. It is a schematic diagram which shows the table composition example of one Embodiment. It is a schematic diagram which shows the table composition example of one Embodiment. It is an example of a UI image generated by one embodiment. It is a transition example of the UI image display displayed by one embodiment. It is a flow chart which shows the detailed processing example by one Embodiment.

[Explanation of Embodiment of the present invention]
First, the contents of the embodiments of the present invention will be listed and described. The game program according to the embodiment of the present invention has the following configurations.

(Item 1) When executed by a computer equipped with a touch display, the computer is subjected to.
A step of detecting arbitrary position information on the touch display and repeatedly acquiring touch position information at a predetermined frame rate, and
A step of determining the first operation information based on a predetermined number of the touch position information, and
Based on the first operation information, the step of performing the first operation on the moving body in the game space, and
The step of determining the touch-off from the touch display and
A step of determining the second operation information using the touch position information in at least one frame immediately before the touch-off.
A step of determining a flick operation based on the second operation information,
The first operation is released in response to the flick operation, and a method including a step of performing a second operation on the moving body based on the second operation information is executed.
The first movement causes the moving body to move in the game space together with the character.
A game program in which the second operation operates the moving body so as to move in the game space away from the character.

(Item 2) The game program according to item 1, which determines the touch-off when the touch position information cannot be continuously acquired over a plurality of frame rate units in the step of determining the touch-off. ..

(Item 3) In the game program described in item 1 or 2,
The second operation information includes a flick direction in at least one frame immediately before the second operation information.
A game program in which the second operation is performed in the direction of the game space corresponding to the flick direction in the step of executing the second operation.

(Item 4) In the game program described in any one of items 1 to 3,
The second operation information includes a flick distance in at least one frame immediately before the second operation information.
In the step of determining the flick operation, the flick operation type is determined based on the flick distance.
A game program in which an operation associated with the flick operation type is executed in the step of executing the second operation.

(Item 5) In the game program described in item 4,
The flick operation type is a game program in which the maximum value of each flick distance in two or more consecutive frames immediately before is determined based on whether or not the maximum value is within a range defined by a predetermined threshold value.

(Item 6) In the game program according to item 4 or 5, the step of performing the second operation on the moving body is further further enhanced.
A step of determining whether the position of the character is included in a predetermined operation area in the game space, and
Including the step of associating the second action with a specific action type when the position of the character is included in the predetermined action area.
A game program in which an operation associated with the specific action type is executed in the step of executing the second operation.

(Item 7) In the game program according to item 6, the predetermined operation area is configured based on the characteristics of the character.

(Item 8) In the game program according to item 6 or 7, the game program is applied to a soccer game.
The first action is a "dribble" action by the character to the moving body.
The second movement is a "kick" movement by the character to the moving body.
A game program in which in the second action, the particular action type is associated with a "shoot" action.

(Item 9) The game program described in item 8 and
The flick operation type includes a "strong" flick operation and a "weak" flick operation.
In the second operation, the game program in which the "strong" flick operation is associated with a "high trajectory" and the "weak" flick operation is associated with a "low trajectory".

(Item 10) The game program according to any one of items 1 to 9, wherein the method is further described.
According to the step of repeatedly acquiring the touch position information, an image is generated and displayed in association with the first touch position information for which touch-on is detected and the second touch position information for which touch-on is currently detected for each frame rate. It ’s a step,
The image is an image of an elastic body having a base and a tip.
The base portion is associated with the first touch position information, and the tip portion is associated with the second touch position information for each frame, so that the elastic body changes with the change of the second touch position information through the slide operation. A game program in which the image is displayed so as to transform.

(Item 11) In the game program according to item 10, in the step of generating and displaying the image.
When the distance between the first touch position information and the second touch position information exceeds a predetermined upper limit value, the tip portion moves from the first touch position information toward the second touch position information. A game program that is associated with location information that is separated by the upper limit of.

(Item 12) In the game program according to item 10 or 11, the step of generating and displaying the image further further.
A game program comprising performing a visual process on an image of the elastic body, depending on the distance between the base and the tip.

(Item 13) In the game program according to any one of items 10 to 12, the step of generating and displaying the image further provides an index indicating a slide direction based on the current second touch position information at the tip portion. A game program comprising a step to display with the image in association with.

[Details of Embodiments of the present invention]
A specific example of the game program according to the embodiment of the present invention will be described below with reference to the drawings. It should be noted that the present invention is not limited to these examples, and is indicated by the scope of claims, and is intended to include all modifications within the meaning and scope equivalent to the scope of claims. In the following description, the same elements will be designated by the same reference numerals in the description of the drawings, and duplicate description will be omitted.

FIG. 1 shows a block diagram of a basic configuration of a computer 100 according to an embodiment of the present invention. The computer 100 is preferably a device including a touch display such as a smartphone or a tablet computer. It will be understood by those skilled in the art that the term "touch display" can be replaced herein with "touch panel" and "touch screen". As shown, the computer 100 includes a touch display 102, a processing unit 108, a storage unit 110, and a communication unit 112. The touch display 102 includes a display unit 104 for displaying various data stored in the storage unit 110, various images generated by the processing unit 108, and the like. The touch display 102 also touches the display unit 104 with an object such as a user's finger or a stylus (mainly a physical contact such as a touch operation, a swipe operation, a slide operation, a flick operation, a drag operation, and a tap operation). The contact detection unit 106 for detecting the operation) is provided. Due to the structure of the touch display 102, the contact detection unit 106 may be arranged on the upper layer of the display unit 104 such as a liquid crystal panel, an organic EL, or a plasma display. The contact detection unit 106 can adopt a pressure detection method, a resistance film method, a capacitance method, an electromagnetic induction method, or the like. When an input due to contact with an object such as a finger or a stylus is received on the contact detection unit 106, the amount of change in pressure, electrical resistance, electric capacity, elastic wave energy, etc. at the contact position is detected, and the correspondence on the display unit 104. The contact position coordinates to be used will be specified.

The processing unit 108 may be configured as a processor, reads out a computer program such as a user interface image display program and a game program according to the embodiment of the present invention from the storage unit 110 or the like, and performs processing according to the reading from the storage unit 110 or the like. To execute. The specific configuration and operation of the processing unit 108 will be described later. The storage unit 110 can temporarily or permanently store game programs, various data related to users and games, and registers, updates, deletes, and the like in response to commands from the processing unit 108. Run. Examples of the storage unit 110 include, but are not limited to, main storage such as ROM (Read Only Memory) and RAM (Random Access Memory), and auxiliary storage such as hard disk, flash memory, and optical disk. The communication unit 112 can be used to exchange data related to the game with an external server (not shown) or the like via a communication network such as the Internet.

FIG. 2 is a block diagram showing in detail the detailed configuration of the computer 100 according to the embodiment of the present invention. As described in connection with FIG. 1, the computer 100 includes a touch display 102 including a display unit 104 and a contact detection unit 106, a processing unit 108, a storage unit 110, and a communication unit 112. The processing unit 108 has a touch position information acquisition unit 201, an operation information determination unit 202, a dribble operation execution unit 203, a flick operation determination unit 204, a kick operation execution unit 205, and a UI image generation unit 206 as functional blocks. The details of the processing executed by each component will be described later. In addition, although it includes basic function parts such as an animation generation part that generates an animation as the game progresses, the illustration is omitted. Each functional block is implemented by software and is realized by the processor 108 shown in FIG. 1 reading and executing each program module stored in the memory 110.

FIG. 3 is an example of a game screen when the game program of one embodiment is applied to a soccer game. As a game space, the touch display 102 displays a soccer field FD imaged by a virtual camera (not shown) from the vertical direction of the space. Further, the score "1-0" and the elapsed time "second half 01:12" are displayed as additional information on the upper part of the touch display 102. Various game objects that can be operated by the user are arranged in the soccer field FD. Examples of objects include a moving body (soccer / ball) MO, own characters CH11 to 12 of the own team, opponent characters CH21 to 23 of the opponent team, goal GL, and the like. Positions such as "FW" are also displayed for each character. In the center of the display, the ball MB is associated with the own character CH12, and the activity mark MK marked with ▽ is displayed on the own character CH11. The own character CH12 on which the activity mark MK is displayed can be operated through a user's touch operation. Examples of the movement of the own character include dribbling and kicking to the ball, and in-field movement (positioning). Kicking includes various actions such as passing, clearing, centering, and shooting. Field coordinates are defined as game space coordinates across the field FB. That is, each object such as the ball to be arranged, the own character CH11 to 12, the opponent character CH21 to 23 of the opponent team, and the goal GL has coordinate information. At the bottom of the screen, a user interface image (hereinafter referred to as "UI image") corresponding to a touch operation by the user is displayed. The UI image is associated with an operation command to the own character CH12. According to one embodiment, in a slide operation, it is preferable that the slide direction is associated with the movement direction of the character in the game space, and the slide distance is associated with the movement speed of the character. This makes it possible to provide a UI image that can intuitively provide a user with excellent operability.

As used herein, a "game object" (sometimes referred to simply as an "object") primarily includes moving objects (balls) and characters that are placed in the game space, both together or together. It can be operated by the user at a distance. In the present specification, the term "slide" operation means that a user touches an object such as a finger on the touch display 120 (touch on), maintains the contact while changing the position (touch now), and then releases the object (touch now). It is a general term for a series of touch operations called (touch off). In particular, in the present specification, the operation of sliding an object on the touch display 120 for a certain period after touch-on is referred to as a "swipe" operation. Similarly, the operation of sliding an object on the touch display 120 at a predetermined speed and then touching it off is referred to as a "flick" operation. That is, in the present specification, the concept of "slide" operation includes the concept of "swipe" operation and "flick" operation.

(A) Overview of overall processing of actions on objects FIGS. 4 and 5 show an overview of information processing for operating objects in the game space. FIG. 4 shows a schematic operation example of an object on a two-dimensional field FD according to an embodiment, and FIG. 5 shows a flowchart of information processing corresponding to the object operation. In FIG. 4, the character CH12 of the own team is activated and operates with (or away from) the ball. That is, in the state of (a), the character CH 12 is associated with the ball MB. In response to the swipe operation by the user on the touch display 102, the ball MB is moved together with the character CH12 in the slide direction (lower right direction in the figure) on the two-dimensional field FD. That is, the ball MB is moved by the "dribble" operation of the character CH12. In the state of (b), the association of the character CH12 with the ball MB is released in response to the flick operation on the touch display. That is, the above-mentioned "dribble" operation is canceled. Then, the ball MB is moved in the flick direction (to the right in the figure) on the two-dimensional field FD apart from the character CH12. That is, only the ball MB is moved to the character CH 12 by the "kick" operation to the ball MB. In this way, the user can perform a series of actions from "dribbling" to "kicking" on the ball through the slide operation on the touch display, and can provide the user with a simple and intuitive touch operability. can.

In the flowchart of FIG. 5, at the start of processing by the slide operation, the character CH 11 is associated with the ball MB by a predetermined user action or automatically. Information processing includes touch-on phases (S301 to S302), touch-now phases (S303 to S307), and touch-off phases (S308 to S310). Touch-on, touch-now, and touch-off are determined through the contact detection unit 106 detecting contact at a predetermined frame rate. In the touch-on phase, when the contact detection unit 106 first detects a contact (S301), the touch position information acquisition unit 201 acquires the touch position information as a touch-on state and stores it in the storage unit 110 (S302). The touch position information in the touch-on state can be any position in the touch area on the touch display 102, and the user may touch any position.

The touch now phase corresponds to the swipe operation state in the slide operation by the user. The contact detection unit 106 continuously detects contact at predetermined frame rates (for example, 30 fbps) (S303). Then, the touch position information acquisition unit 201 repeatedly acquires the touch position information for each frame rate in the touch now state (S304). In particular, among the acquired touch position information in the touch now state, the latest predetermined number of touch position information is stored in the storage unit 110. The operation information determination unit 202 determines the swipe operation information corresponding to each frame by using the stored touch position information (S305). The UI image generation unit 206 continuously generates UI images for each frame rate and displays them on the touch display 102 (S306). The dribble operation executing unit 203 causes an operation on an object in the game space to be executed based on the swipe operation information in response to the swipe operation (S307). In the example of FIG. 4A, the character CH12 is made to perform a “dribble” operation in the swipe direction (lower right direction in the figure) with the ball MB. In the touch now phase, the processes of S304 to S307 are repeatedly executed at predetermined frame rates.

In the touch-off phase, when the contact detection unit 106 does not detect contact (S308), the touch position information acquisition unit 201 cannot specify the touch position information, so that the touch-off state is determined. At that time, the UI image disappears (not shown). The operation information determination unit 202 determines flick (slide) operation information using the touch position information in at least one frame immediately before the stored touch-off (S309). The flick operation determination unit 204 determines whether the immediately preceding operation is a flick operation and the flick operation type in that case based on the flick operation information (S310). In the case of a flick operation, the kick operation executing unit 205 causes an operation on an object in the game space to be performed based on the flick operation information (S311). In the above example of FIG. 4B, the character CH12 is made to perform a “kick” operation on the ball MB, and the ball MB is moved in the flick direction.

(B) Storage of touch position information (S302, S304 and S309)
6 (a) and 6 (b) show storage examples when the touch position information acquired by the touch position information acquisition unit 201 in the above S302, S304 and S309 is stored. Through the slide operation, a predetermined number of touch position information is stored in the array table fp in the storage unit 110 at a predetermined frame rate (for example, 30 fbps). In addition, the initial position coordinates are stored in the table for each slide operation. The touch position information is preferably acquired as xy position coordinates of the touch area on the touch display 120. Generally, the touch area (the size of the touch display 120) is different for each mobile terminal 100 used by the user. For example, the xy position coordinates are adjusted so that the center of the touch area is the origin (0,0), the upper end in the vertical direction is +1.0 and the lower end in the vertical direction is -1.0, and the horizontal touch is adjusted accordingly. It is better to determine the area range. As an example, in the case of a general mobile terminal, the horizontal touch area range when the terminal is held vertically is approximately −0.6 (left end) to +0.6 (right end).
Based on the touch position information, the swipe operation information is determined in S305, and the flick operation information is determined in S309.

In the storage example of FIG. 6A, as the array table fp, a storage area for storing 11 touch position information for each frame rate is provided from fp [0] to fp [10]. The number of touch position information is not limited and may be any number. In the first touch-on state, the position coordinates (x0, y0) at the time of touching on the touch area are stored in fp [0]. In the touch-on state, fp [1] to fp [10] are still null (empty) values, but as the touch-now state progresses, the position coordinates are sequentially stored for each frame rate. For example, in the touch now state 1, five position coordinates are stored in order from fp [1] to fp [5], and in the touch now state 2, five position coordinates are further stored in order from fp [6] to fp [10]. It is stored. Since the array table fp stores only 11 pieces of data, it is necessary to sequentially delete old data as soon as the capacity is full. The touch-on coordinate information (x0, y0) is separately saved as the initial position coordinates so that the swipe direction can always be detected. It is preferable that the initial position coordinates are not deleted through the slide operation until the touch-off state is reached.

From the touch now state 2 to the next touch-off determination after the touch now state progresses, the data of the position coordinates for each frame rate is sequentially overwritten from fp [0] and the data of the old position coordinates is sequentially deleted. .. The touch-off determination is performed when the position coordinates are not physically acquired and the null value is stored. In FIG. 6A, at least fp [5] is overwritten and updated with the null value, so that the touch-off determination is performed. If it is determined to be touch-off, the acquisition of touch position information for a series of slide operations is completed. In the touch-off judgment, not when the touch position information cannot be acquired only once (one null value) but when it cannot be continuously acquired over a plurality of frame rate units (two or more null values are continuously obtained). The determination logic may be configured to determine the touch-off. The reason for this configuration is that it is fully assumed that the finger will be separated from the touch display for a moment when the slide operation is complicated. For example, in a “dribble” operation (for example, FIG. 4A) in a soccer game, it is assumed that a complicated slide operation is performed because the character's turning operation or the like is frequently performed.

6 (b) shows that (1) the touch-off determination is made as a result of the touch-off determination in FIG. An example of storing two patterns is shown. In both (1) and (2), null values are stored in fp [5] and fp [6] instead of (x16, y16) and (x17, y17). Further, when the input of the next touch position coordinates (x18, y18) is received, the (x18, y18) is stored in fp [7]. After that, the position coordinates are sequentially stored from fp [8] for each frame rate (arrow). On the other hand, in the case of (1), the initial position coordinates are newly overwritten and updated with (x18, y18), whereas in the case of (2), the initial position coordinates are maintained as (x0, y0). Not limited to (2), it is preferable that the sequence table fp is not initialized even after the touch-off determination is made in (1).
That is, it is preferable to maintain the latest touch position information (x14, y14), (x15, y15), etc. in the previous slide operation so that they can be used in a separate process. ..

Hereinafter, some of the above S301 to S311 will be described in more detail individually. FIG. 7 shows the details of the determination of the flick operation information in S309. 8 and 9 show details of the flick operation determination in S310. 10 to 13 show the details of the operation on the object in S311. 14 to 16 show the details of UI image generation in S306.

(C) Determination of flick operation information (S309)
FIG. 7 shows a detailed flowchart of the flick operation information determination process (S309) by the operation information determination unit 202. When the touch-off state is specified, the association between the character and the ball so far is first released (S401). As a result, the "dribble" operation accompanied by the character's ball MB is canceled, and the "kick" operation corresponding to the flick operation becomes possible (for example, FIG. 4B). Touch position information in at least one frame immediately before touch-off is extracted from the storage unit (S402). Using the extracted touch position information, the slide direction and the slide distance are determined as flick operation information (S403).

In the example of the touch-off state in (2) of FIG. 6 (b) above, by referring to the latest 11 position coordinates, the slide operation information for the latest 10 frames (1st frame to 10th frame) can be obtained. It is determined. Specifically, the flick operation information of the 10th frame immediately before touch-off is determined by using the touch position information (position coordinates) of (x14, y14) of fp [3] and (x15, y15) of fp [4]. Will be done. Further, the flick operation information of the ninth frame immediately before that is determined using the position coordinates of (x13, y13) of fp [2] and (x14, y14) of fp [3]. The flick operation information includes, for example, the xy coordinate movement direction (that is, the flick direction), the xy coordinate movement amount (that is, the flick distance), and the xy coordinate movement speed (that is, the flick speed calculated by the coordinate movement amount / frame rate). Is calculated. The flick operation information should be calculated using two or more consecutive frames immediately before. As an example, the flick direction may be used to correspond to the direction in which the object is manipulated in the game space, and the flick distance may be used to determine the speed of movement to the object. In this way, by acquiring a limited number of position coordinates, various operation parameters related to the slide operation can be specified.

(D) Flick operation determination and flick operation type determination (S310)
The process of flick operation determination and flick operation type determination (S310) by the flick operation determination unit 204 will be further described with reference to FIGS. 8 and 9. FIG. 8 shows a detailed processing flow of S310. Further, FIG. 9 shows a graph example of flick (slide) operation information as an example. The horizontal axis of the graph shows the frame F in a predetermined frame rate unit, and the vertical axis shows the slide distance (swipe distance or flick distance). The touch-on state is detected in the first frame F [1], and the slide (swipe) distance is plotted as the touch-now state up to the n-1th frame F [n-1]. Since the touch position information is not specified in the nth frame F [n], the slide distance cannot be calculated (N / A). As a result, the distance touch-off is detected.

In response to the determination of the flick operation information in at least one frame immediately before in S309, it is determined whether or not the threshold TH1 or more is set for the slide distance in the flick operation information (S501). Specifically, it is determined whether the slide (flick) distance plotted in the immediately preceding n-1th frame F [n-1] or the immediately preceding n-2th frame F [n-2] is the threshold value TH1 or more. Will be done. If "Yes", it is determined that the flick operation has been established, and the operation on the object is executed through the subsequent processing. On the other hand, if "No", it is determined that the flick operation is not established, and the operation on the object is not executed and the swipe process ends. When two flick distances F [n-1] and F [n-2] are used, it is preferable that the establishment of the flick operation is determined when both of them are at least the threshold value TH1. That is, even if only the flick distance for one frame of F [n-1] is equal to or greater than the threshold value TH1, the establishment of the flick operation is not determined. The plurality of immediately preceding frames used for the determination may be any number up to 2 or more and a number that can be traced back (10 in the example of FIGS. 6A and 6B). The reason for using a plurality of immediately preceding frames is to distinguish it from a tap operation in which only the operation information of only one immediately preceding frame is determined. It is preferable to determine not only the flick distance but also the flick direction by using the frame used in the above determination. The direction of the latest frame may be determined as the flick direction, or when a plurality of frames are used for determination, the direction of the oldest frame may be determined as the flick direction. In addition to this, the average direction of each frame may be calculated and determined as the flick direction.

As a result of S501, when it is determined that the flick operation is established, the flick operation type is further determined based on the flick distance. Flick operation types include "strong" flick operation and "weak" flick operation. That is, it is determined whether the flick distance is equal to or greater than the further threshold value T2 (> T1) (S502). If "Yes", the flick operation type is set to "strong" flick operation (S503), and if "No", the flick operation type is set to "weak" flick operation (S504). When the flick distances of a plurality of consecutive frames are used, it is better to judge by comparing the maximum value among them with the threshold value T2. That is, in FIG. 8, since the flick distance of F [n-1] is the maximum value and is larger than TH2, the flick operation type is set to “strong” flick operation here. The flick operation type is associated with the action to be performed.

(E) Implementation of operation on the object (S311)
With reference to FIGS. 10 to 12, the process (S311) of executing the action on the object (that is, the action on the ball by the character) by the kick motion executing unit 203 in the soccer game program will be further described. FIG. 10 shows a detailed processing flow of S311. FIG. 11 shows an outline of an operation area (shoot range SR) related to determination of a specific action type. FIG. 12 shows a character table 200 that defines character characteristics, and FIG. 13 shows a list of operation tables 300 to 500 relating to the movement of a character on a ball. The table group shown in FIGS. 12 and 13 is reflected in the mobile terminal 100 by downloading from the game server together with the game program through the communication unit 112 of the mobile terminal.

First, the character position in the game space at the time of touch-off is determined (S601). It is determined whether the character position is included in the operation area (S602). In the case of "Yes", it is further determined whether or not the direction in the game space corresponding to the slide direction acquired in S403 is facing the goal direction (S603). In the case of "Yes", the action of a specific action type "shoot" in the flick direction is associated with the flick operation (S604). On the other hand, when "No" in S602 or S603, the action of the default action type "kick" in the flick direction is associated with the flick operation (S605). When the action of the action type is associated with the flick operation, the actual operation is executed according to the action type and the flick operation type set in S503 and S504 (S606). At the time of performing the motion, an animation related to the action in the flick direction of the character or the ball is played according to the content.

The position data of each object such as a character or a ball arranged on the field FD is managed by the field coordinates (XY coordinates). S602 and S603 should also be determined in the XY coordinate system. The XY coordinate system may be any as long as it can define a two-dimensional plane in the Cartesian coordinate system, such as using the center of the field or the goal of the own team as the origin. In relation to S602, in the example of the field FD of FIG. 11, the own character CH12 is arranged so as to be included in the shoot range SR. In the operation area of the shoot range SR, the own character CH12 performs a “shoot” operation in response to a flick operation. The shoot range SR includes, but is not necessarily limited to, the goal area GA and the penalty area PA. Further, the shape of the shoot range SR is not limited to a rectangle. The shoot range SR may be configured to be different for each character according to the characteristics of the character (player). The character characteristics are managed by the character table 200 in the storage unit 110, as shown in FIG. 12, as an example. Specifically, in addition to general character information such as character ID, player name, team (own team / opponent team), and position, in one embodiment, shooting power (for example, 60/100). Parameters should also be managed as character characteristics. That is, the shoot range SR should be set for each character based on the shoot force. For example, a player who is good at middle shooting should have a high shooting power and a wide shooting range SR. The items in the character table 200 are merely examples and are not limited thereto. Alternatively, the dominant foot (right-handed / left-handed) may be managed and reflected in the configuration of the shoot range SR. The goal direction in S603 is, for example, in FIG. 11, a goal formed by providing an angle α (solid line) outward from the left-right direction (goal post direction gd1, gd2 (dotted line)) of the goal with respect to the position of the own character CH12. Directional region is defined as the direction toward the GDA.

Regarding S606, the operation according to the flick operation type and the action type is determined from the operation table group of FIG. 13 stored in the storage unit 110 as an example. The table group includes, but is not limited to, a slide operation / operation table 300, a flick operation / operation table 400, and a flick operation / specific operation table 500.

The slide operation / operation table 300 defines a default operation according to the slide operation type. In the case of a flick operation, a "kick" action is associated. That is, in the case of a flick operation, the "kick" operation is determined as the default operation. In S307 of FIG. 5, the "dribble" operation associated with the swipe operation is also determined by referring to the slide operation / operation table 300. In the flick operation / operation table 400, the default operation according to the flick operation type is defined. A "high trajectory" is associated with an operation whose flick operation type is "strong flick", and a "low trajectory" is associated with a "weak flick" operation. Based on these slide operation / operation table 300 and flick operation / operation table 400, for example, when the flick operation type is set to "strong flick" operation in S503 of FIG. 8, the "kick" of "high trajectory" is set. Determined as an action. Similarly, when the "weak lick" operation is set in S504, the "kick" of the "low trajectory" is determined as the operation. In addition, the flick operation / specific operation table 500 defines a specific action type according to the target operation area. As an example, the specific action type "shoot" is associated with the flick operation in the shoot range SR. In the self-penalty area PA2, the specific action type "clear" is associated with the flick operation. In addition to this, various specific action types can be associated, for example, by defining an opponent's corner area and associating "centering" as a specific action type. If the own character CH is not located in any of the operation areas specified in the flick operation / specific operation table 500, the “kick” which is the default operation in the slide operation / operation table 300 is executed as it is.

In the example of FIG. 13, at least the following six operation patterns are assumed depending on the contents of the "flick operation type" in the flick operation / operation table 400 and the "specific action type" in the flick operation / specific operation table 500. .. That is, "shoot" motion of "high trajectory", "clear" motion of "high trajectory", "kick" motion of "high trajectory", "shoot" motion of "low trajectory", "clear" of "low trajectory". The motion is a "kick" motion with a "low trajectory". In S606, one of these at least six motion patterns is performed toward the direction in the space corresponding to the flick direction. It should be noted that the above example is only an example and is not necessarily limited to these.

In this way, it is possible to provide the user with a simple and intuitive touch operability in the sense that various actions can be assigned to the flick operation of the user. In addition, while maintaining simple operability, the character makes the ball perform complicated movements, so that the game can proceed smoothly.

(F) UI image generation process (S306)
With reference to FIGS. 14 and 15, the process (S306) in which the UI image is generated by the UI image generation unit 206 and displayed on the touch display will be further described. FIG. 14 shows a schematic diagram of the UI image generated by one embodiment. FIG. 15 shows a transition example of a UI image displayed on the touch display 102 through a series of slide operations from touch-on to touch-off. FIG. 16 shows a detailed processing flow of S306. As shown in FIG. 14, the UI image is formed as an image I of a water droplet shaped elastic body having a base BP, a tip TP and a connection CP between them. As shown in FIG. 15A, the initial shape of the elastic body is a circular shape. It will be understood by those skilled in the art that the shape of an elastic body can be formed by a set (mesh) of a plurality of polygons consisting of a square or a triangular shape. That is, by substituting the coordinates of each vertex of each polygon into a predetermined mathematical formula, the shape of a water droplet of an elastic body can be reproduced. As shown in FIGS. 15A to 15C, in the UI image, the base BP of the elastic body is fixed to the touch start point and the tip TP of the elastic body follows the touch position of the finger through a series of slide operations. It is better to form it like this. For each frame rate, a UI image is displayed in which the elastic body elastically deforms and expands and contracts. A predetermined upper limit is set for the length from the base BP to the tip TP. If the upper limit is exceeded, the UI image is displayed so that the tip TP is separated from the position of the finger.

In the UI image generation process of S306, the touch position information (coordinates of the touch start point) acquired in the touch-on state by the touch position information acquisition unit 201 is stored. Further, the touch position information (coordinates of the current touch point) currently acquired by the touch position information acquisition unit 201 in the touch now state is stored each time. First, the distance d between the touch start point and the current touch point is calculated (S701). It is determined whether the distance d is equal to or less than the upper limit value D (S702). In the case of "yes" (eg, FIG. 15B), the base BP of the elastic body is associated with the touch start point (S703) and the tip TP of the elastic body is associated with the current touch point (S705). .. That is, the base BP of the elastic body is aligned with the touch start point, and the tip TP is aligned with the current touch point. Then, the base BP and the tip TP are displayed, and further, they are displayed so as to be connected by the connecting portion CP, and the UI image I of the elastic body is generated (S707 / FIG. 15 (b) (c). )). As a result, the UI image is displayed in such a manner that the elastic body is deformed with the change of the current touch point through the slide operation. On the other hand, in the case of "No" in S702 (for example, FIG. 15D), the base BP of the elastic body is associated with the touch start point (S704), but the tip TP of the elastic body is in turn the touch start point. It is associated with the position of a point separated from the current touch point by the upper limit distance D (S706). Then, similarly to the above, the UI image I of the elastic body is generated (S707). As shown in FIG. 15D, the current touch point and the tip portion TP have a separated positional relationship. The upper limit D is set for the length from the base BP to the tip TP because the operation distance becomes long due to the complicated slide operation, especially in the "dribble" operation (for example, FIG. 4A) in a soccer game. be. In soccer, there are many player characters in the field FD. This is because even if the operation distance is long, if the UI image of the elastic body that follows the UI image is completely displayed, the player character is covered with the UI image and hidden on the game screen.

Returning to FIG. 16, when the UI image is generated in S708, the UI image of the elastic body is further visually processed according to the distance d between the touch start point and the current touch point (S708). ). For example, in the state of FIG. 15 (b), the UI image is color-processed so as to be white, while when the distance d in FIG. 15 (d) reaches the upper limit value D, the UI image is color-processed so as to be light blue. Will be done. The slide direction of the current slide operation is determined based on at least the coordinates of the current touch point (S709). More specifically, the slide direction of the current slide operation is determined by using at least the two touch position coordinates immediately before the continuation as shown in FIG. 6 (a). An index IND (arrows in FIGS. 15B to 15D) with respect to the determined slide direction is associated with the tip TP. That is, the index IND is aligned with the tip TP of the elastic body and displayed together with the UI image (S710). As described above, the present invention provides the user with a simple and intuitive touch operability. In addition, while maintaining simple operability, it is possible to carry out complicated operations on game objects and smoothly proceed with the game.

The above-described embodiments are merely examples for facilitating the understanding of the present invention, and are not intended to limit the interpretation of the present invention. It goes without saying that the present invention can be modified and improved without departing from the spirit thereof, and the present invention includes its equivalents.

Claims (13)

When run by a computer with a touch display, the computer
A step of detecting arbitrary position information on the touch display and repeatedly acquiring touch position information at a predetermined frame rate, and
A step of determining the first operation information based on a predetermined number of the touch position information, and
Based on the first operation information, the step of performing the first operation on the moving body in the game space, and
The step of determining the touch-off from the touch display and
A step of determining the second operation information using the touch position information in at least one frame immediately before the touch-off.
A step of determining a flick operation based on the second operation information,
The first operation is released in response to the flick operation, and a method including a step of performing a second operation on the moving body based on the second operation information is executed.
The first movement causes the moving body to move in the game space together with the character.
A game program in which the second operation operates the moving body so as to move in the game space away from the character. The game program according to claim 1, wherein the touch-off is determined when the touch position information cannot be continuously acquired over a plurality of frame rate units in the step of determining the touch-off. In the game program according to claim 1 or 2.
The second operation information includes a flick direction in at least one frame immediately before the second operation information.
A game program in which the second operation is performed in the direction of the game space corresponding to the flick direction in the step of executing the second operation. In the game program according to any one of claims 1 to 3,
The second operation information includes a flick distance in at least one frame immediately before the second operation information.
In the step of determining the flick operation, the flick operation type is determined based on the flick distance.
A game program in which an operation associated with the flick operation type is executed in the step of executing the second operation. In the game program according to claim 4,
The flick operation type is a game program in which the maximum value of each flick distance in two or more consecutive frames immediately before is determined based on whether or not the maximum value is within a range defined by a predetermined threshold value. In the game program according to claim 4 or 5, the step of performing the second operation on the moving body is further further described.
A step of determining whether the position of the character is included in a predetermined operation area in the game space, and
Including the step of associating the second action with a specific action type when the position of the character is included in the predetermined action area.
A game program in which an operation associated with the specific action type is executed in the step of executing the second operation. The game program according to claim 6, wherein the predetermined operation area is configured based on the characteristics of the character. In the game program according to claim 6 or 7, the game program is applied to a soccer game.
The first action is a "dribble" action by the character to the moving body.
The second movement is a "kick" movement by the character to the moving body.
A game program in which in the second action, the particular action type is associated with a "shoot" action. The game program according to claim 8.
The flick operation type includes a "strong" flick operation and a "weak" flick operation.
In the second operation, the game program in which the "strong" flick operation is associated with a "high trajectory" and the "weak" flick operation is associated with a "low trajectory". The game program according to any one of claims 1 to 9, wherein the method is further described.
According to the step of repeatedly acquiring the touch position information, an image is generated and displayed in association with the first touch position information for which touch-on is detected and the second touch position information for which touch-on is currently detected for each frame rate. It ’s a step,
The image is an image of an elastic body having a base and a tip.
The base portion is associated with the first touch position information, and the tip portion is associated with the second touch position information for each frame, so that the elastic body changes with the change of the second touch position information through the slide operation. A game program in which the image is displayed so as to transform. In the game program according to claim 10, in the step of generating and displaying the image.
When the distance between the first touch position information and the second touch position information exceeds a predetermined upper limit value, the tip portion moves from the first touch position information toward the second touch position information. A game program that is associated with location information that is separated by the upper limit of. The game program according to claim 10 or 11, wherein the step of generating and displaying the image further comprises.
A game program comprising performing a visual process on an image of the elastic body, depending on the distance between the base and the tip. In the game program according to any one of claims 10 to 12, the step of generating and displaying the image further associates an index indicating a slide direction based on the current second touch position information with the tip portion. , A game program comprising a step to display with the image.

Images