JP6043448B1 - Game program - Google Patents

Abstract

To provide a game program capable of operating an object at will while maintaining simple operability. When executed by a computer having a touch display, the computer detects arbitrary position information on the touch display, and repeatedly acquires the touch position information for each predetermined frame rate; Determining the first operation information based on the touch position information; performing a first action on the moving body in the game space based on the first operation information; and determining a touch-off from the touch display. The step of determining the second operation information using the touch position information in at least one frame immediately before the touch-off, the step of determining the flick operation based on the second operation information, and the first action according to the flick operation And releasing the second action on the moving object based on the second operation information. To perform the method. [Selection] Figure 10

Description

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

  Nowadays, a game program by a mobile terminal (for example, a smartphone) provided with a touch display is distributed to users through the Internet. Many game programs control movement of objects in the game space through touch operations on a touch display. Patent Document 1 discloses a technique for advancing a game in a soccer game while a user designates an action target character and position each time on a touch display. In particular, a technique for performing an action (pass, dribble, shoot, etc.) on a moving body according to designation of a 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 that moves at a predetermined speed or more from the touchdown by a predetermined stroke distance, the touch operation is determined as a flick operation, and the player character is moved to the target of movement. Disclosed is a technique for moving toward the target.

JP 2014-79643 A International Publication No. 2013-024771 Pamphlet

  In a game application that requires many characters to move with a moving object, 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 having a touch display, the computer detects arbitrary position information on the touch display and repeatedly acquires the touch position information for each predetermined frame rate; Determining the first operation information based on the number of touch position information, performing the first action on the moving body in the game space based on the first operation information, and determining the touch-off from the touch display A step of determining second operation information using 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, and in response to the flick operation The step of performing the second operation on the moving body based on the second operation information after the first operation is released. The first action moves the moving body to move in the game space together with the character, and the second action moves the moving body to move in the game space away from the character. A game program is obtained.

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

It is a block diagram of the basic composition of the computer in one embodiment. It is a block diagram of the detailed structure of the computer in one Embodiment. It is an example of the game screen produced | generated by the game program of one Embodiment. It is an example of a schematic operation | movement to the object by one Embodiment. It is a flowchart which shows the whole process outline | summary by one Embodiment. It is a schematic arrangement | sequence diagram of the touch position information acquired by one Embodiment. It is a schematic arrangement | sequence diagram of the touch position information acquired by one Embodiment. It is a flowchart which shows the example of a detailed process by one Embodiment. It is a flowchart which shows the example of a detailed process by one Embodiment. It is an example of the graph of the slide operation information determined by one Embodiment. It is a flowchart which shows the example of a detailed process by one Embodiment. It is the schematic which shows the example of the field area | region of one Embodiment. It is the schematic which shows the table structural example of one Embodiment. It is the schematic which shows the table structural example of one Embodiment. It is an example of a UI image generated according to an embodiment. It is an example of a transition of UI image display displayed by one embodiment. It is a flowchart which shows the example of a detailed process by one Embodiment.

[Description of Embodiment of the Present Invention]
First, the contents of the embodiment of the present invention will be listed and described. A game program according to an embodiment of the present invention has the following configuration.

(Item 1) When executed by a computer having a touch display,
Detecting arbitrary position information on the touch display and repeatedly acquiring the touch position information for each predetermined frame rate;
Determining first operation information based on a predetermined number of the touch position information;
Performing a first action on a moving object in the game space based on the first operation information;
Determining a touch-off from the touch display;
Determining second operation information using the touch position information in at least one frame immediately before the touch-off;
Determining a flick operation based on the second operation information;
Executing the method including the step of releasing the first operation in response to the flick operation and performing the second operation on the moving body based on the second operation information;
The first action moves the moving body to move in the game space together with the character,
A game program in which the second action moves the moving body to move in the game space away from the character.

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

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

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

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

(Item 6) The game program according to item 4 or 5, wherein the step of performing the second operation on the moving body further includes:
Determining whether the position of the character is included in a predetermined motion area in the game space;
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) The game program according to item 6, wherein the predetermined motion area is configured based on 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 “dribbling” action to the moving body by the character;
The second action is a “kick” action to the moving body by the character;
In the second operation, the specific action type is associated with a “shoot” operation.

(Item 9) A game program according to item 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 “high trajectory” and the “weak” flick operation is associated with “low trajectory”.

(Item 10) The game program according to any one of items 1 to 9, wherein the method further includes:
In accordance with the step of repeatedly acquiring the touch position information, an image is generated and displayed in association with the first touch position information detected for touch-on and the second touch position information currently detected for each frame rate. Step,
The image is an image of an elastic body having a base and a tip;
The base is associated with the first touch position information, and the distal end is associated with the second touch position information for each frame, so that the elastic body is changed along with the change of the second touch position information through a slide operation. A game program in which the image is displayed so as to deform.

(Item 11) The game program according to item 10, wherein 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 associated with position information separated by an upper limit value.

(Item 12) The game program according to item 10 or 11, wherein the step of generating and displaying the image further includes:
A game program including a step of performing visual processing on an image of the elastic body according to a distance between the base and the tip.

    (Item 13) In the game program according to any one of Items 10 to 12, in the step of generating and displaying the image, an indicator indicating a slide direction based on the current second touch position information is further displayed. A game program comprising the step of displaying the image together with the image.

[Details of the embodiment 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. In addition, this invention is not limited to these illustrations, is shown by the claim, and intends that all the changes within the meaning and range equivalent to the claim are included. In the following description, the same reference numerals are given to the same elements in the description of the drawings, and redundant descriptions are 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” is interchangeable with “touch panel” and “touch screen” herein. As illustrated, 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 and various images generated by the processing unit 108. The touch display 102 also touches the display unit 104 with an object such as a user's finger or a stylus (mainly physical contact such as touch operation, swipe operation, slide operation, flick operation, drag operation, and tap operation). A contact detection unit 106 for detecting (operation). The contact detection unit 106 may be disposed in an upper layer of the display unit 104 such as a liquid crystal panel, an organic EL, or a plasma display due to the structure of the touch display 102. The contact detection unit 106 may employ a pressure detection method, a resistance film method, a capacitance method, an electromagnetic induction method, or the like. When an input by contact of an object such as a finger or a stylus is received on the contact detection unit 106, a change amount such as pressure, electrical resistance, electric capacity, elastic wave energy, etc. at the contact position is detected, and the display unit 104 responds. The contact position coordinates to be specified are specified.

  The processing unit 108 may be configured as a processor, and reads 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 and the like, and performs processing according to the computer program. To run. 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, etc., and can register, update, delete, etc. information in response to commands from the processing unit 108. Run. Examples of the storage unit 110 include, but are not limited to, a main storage such as a ROM (Read Only Memory) and a RAM (Random Access Memory), and an auxiliary storage such as a hard disk, a flash memory, and an optical disk. The communication unit 112 can be used to exchange game-related data 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 an embodiment of the present invention. As described with reference to FIG. 1, the computer 100 includes the touch display 102 including the display unit 104 and the contact detection unit 106, the processing unit 108, the storage unit 110, and the communication unit 112. The processing unit 108 includes 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. Details of processing executed by each component will be described later. In addition, although it includes a basic function unit such as an animation generation unit that generates an animation during game progress, the illustration is omitted. Each functional block is implemented by software, and is realized by reading and executing each program module stored in the memory 110 by the processor 108 shown in FIG.

  FIG. 3 is an example of a game screen when the game program of one embodiment is applied to a soccer game. On the touch display 102, a soccer field FD captured by a virtual camera (not shown) from the vertical direction of the space is displayed as a game space. Further, on the upper part of the touch display 102, the score “1-0” and the elapsed time “second half 01:12” are displayed as additional information. In the soccer field FD, various game objects that can be operated by the user are arranged. Examples of objects include a moving body (soccer ball) MO, own character CH11-12 of the own team, opponent character CH21-23 of the opponent team, goal GL, and the like. Each character is displayed with a position such as “FW”. In the center of the display, the ball MB is associated with the player character CH12, and an active mark MK marked with ▽ is displayed on the player character CH11. The own character CH12 on which the active mark MK is displayed can be operated through a user's touch operation. Examples of the action of the player character include dribbling and kicking the ball, and movement in the field (positioning). The kick includes various operations such as pass, clear, centering, and chute. Over the field FB, field coordinates are defined as game space coordinates. That is, each object such as a ball to be arranged, own character CH11-12, opponent character CH21-23 of the opponent team, and goal GL has coordinate information. A user interface image corresponding to a touch operation by the user (hereinafter referred to as “UI image”) is displayed at the bottom of the screen. The UI image is associated with a motion command to the player character CH12. According to one embodiment, the UI image may relate the sliding direction to the moving direction of the character in the game space and the sliding distance to the moving speed of the character in the slide operation. Thereby, it is possible to provide a UI image that can provide the user with intuitive operability.

  In this specification, the “game object” (also referred to simply as “object”) mainly includes a moving body (ball) and a character arranged in the game space, Can be operated remotely by the user. In this specification, the term “slide” operation means that the user touches the touch display 120 with an object such as a finger (touch on), maintains the contact while changing the position (touch now), and then releases the object ( It is a generic term for a series of touch operations (touch-off). In particular, in this specification, an 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, an operation of touching off after sliding an object on the touch display 120 at a predetermined speed is referred to as a “flick” operation. That is, in this specification, the concept of “slide” operation encompasses the concepts of “swipe” operation and “flick” operation.

(A) Overview of Overall Processing of Action on Object FIGS. 4 and 5 show an overview of information processing for operating an object in the game space. FIG. 4 shows a schematic operation example of an object on the two-dimensional field FD according to one 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 operated with the ball (or away from the ball). That is, in the state (a), the character CH12 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 along the character CH12 in the sliding direction (the lower right direction in the figure) on the two-dimensional field FD. That is, the ball MB is moved by the “dribbling” operation of the character CH12. In the state (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 “dribbling” operation is released. Then, the ball MB is moved away from the character CH12 in the flick direction (right direction in the figure) on the two-dimensional field FD. That is, only the ball MB is moved to the character CH12 by the “kick” operation to the ball MB. In this way, the user can perform a series of operations from “dribbling” to “kick” on the ball through a slide operation on the touch display, and can provide the user with a simple and intuitive touch operability. it can.

  In the flowchart of FIG. 5, at the time of starting the process by the slide operation, the character CH11 is associated with the ball MB automatically or with a predetermined user action. The information processing includes stages of a touch-on phase (S301 to S302), a touch now phase (S303 to S307), and a touch-off phase (S308 to S310). When the contact detection unit 106 detects contact at every predetermined frame rate, touch-on, touch-now, and touch-off are determined. In the touch-on phase, when the contact detection unit 106 first detects 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 an arbitrary position in the touch area on the touch display 102, and the user may touch a favorite position.

  The touch now phase corresponds to a swipe operation state in the slide operation by the user. The contact detection unit 106 continuously detects contact at every predetermined frame rate (for example, 30 fps) (S303). Then, the touch position information acquisition unit 201 repeatedly acquires touch position information for each frame rate as a 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 swipe operation information corresponding to each frame 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). In response to the swipe operation, the dribble motion execution unit 203 performs an operation on the object in the game space based on the swipe operation information (S307). In the example of FIG. 4A, the character CH12 is caused to perform a “dribbling” action 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 performed for each predetermined frame rate.

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

(B) Storage of touch position information (S302, S304, and S309)
FIGS. 6A and 6B show a storage example when the touch position information acquired by the touch position information acquisition unit 201 in S302, S304, and S309 is stored. Through the slide operation, a predetermined number of pieces of touch position information are stored in the array table fp in the storage unit 110 for each predetermined frame rate (for example, 30 fps). The initial position coordinates are stored in the table for each slide operation. The touch position information may be acquired as xy position coordinates of the touch area on the touch display 120. In general, the touch area (the size of the touch display 120) is different for each portable terminal 100 used by the user. The xy position coordinates are adjusted so that, for example, 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. The area range should be determined. As an example, in the case of a general portable terminal, the horizontal touch area range when the portable terminal is held vertically is approximately −0.6 (left end) to +0.6 (right end). Based on the touch position information, swipe operation information is determined in S305, and flick operation information is determined in S309.

  In the storage example of FIG. 6A, a storage area for storing 11 pieces of touch position information for each frame rate from fp [0] to fp [10] is provided as the array table fp. The number of pieces of touch position information is not limited and can be an arbitrary number. In the first touch-on state, the position coordinates (x0, y0) when touched 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 the position coordinates are sequentially stored for each frame rate as the touch now state progresses. For example, in the touch now state 1, five position coordinates are sequentially stored from fp [1] to fp [5], and in the touch now state 2, five position coordinates are sequentially stored from fp [6] to fp [10]. Stored. Since the array table fp stores only 11 data, it is necessary to delete old data sequentially as soon as the capacity becomes full. Note that the touch-on coordinate information (x0, y0) is separately stored as 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 until the next touch-off determination, the position coordinate data for each frame rate is sequentially overwritten again from fp [0], and the old position coordinate data is sequentially deleted. . The touch-off determination is performed when a position value is not physically acquired and a null value is stored. In FIG. 6A, at least fp [5] has been overwritten and updated with the null value, so the touch-off determination is performed. If it is determined as touch-off, the acquisition of touch position information for a series of slide operations is completed. In the touch-off determination, when the touch position information cannot be acquired only once (one null value), but cannot be continuously acquired over a plurality of frame rate units (the null value is continuously two or more), Determination logic may be configured to determine touch-off. The reason for this configuration is that it is sufficiently assumed that the finger is separated from the touch display for a moment when the slide operation is complicated. For example, in a “dribbling” action in a soccer game (for example, FIG. 4A), since a character turning action or the like is frequently performed, it is assumed that a complicated slide operation is performed.

  FIG. 6B shows the result of the touch-off determination shown in FIG. 6A. (1) When touch-off is determined and then the touch-on state is entered again. An example of storing two patterns in the case of In both (1) and (2), null values are stored in fp [5] and fp [6] instead of (x16, y16) and (x17, y17). When the next touch position coordinate (x18, y18) is received, the (x18, y18) is stored in fp [7]. Thereafter, 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). In addition to (2), it is preferable that the arrangement 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 separate processing. .

  Hereinafter, some of S301 to S311 will be individually described in more detail. FIG. 7 shows 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 details of the operation performed on the object in S311. 14 to 16 show 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, first, the association between the character and the ball so far is released (S401). As a result, the “dribbling” action involving the ball MB of the character is released, and the “kicking” action corresponding to the flick operation becomes possible (for example, FIG. 4B). Touch position information in at least one frame immediately before the touch-off is extracted from the storage unit (S402). Using the extracted touch position information, a slide direction and a slide distance are determined as flick operation information (S403).

  In the example of the touch-off state in (2) of FIG. 6B above, by referring to the latest 11 position coordinates, the slide operation information for the latest 10 frames (from the first frame to the 10th frame) is obtained. It is determined. Specifically, the flick operation information of the 10th frame immediately before the touch-off is determined using touch position information (position coordinates) of (x14, y14) of fp [3] and (x15, y15) of fp [4]. Is done. Further, the flick operation information of the ninth frame immediately before is determined using the position coordinates of (x13, y13) of fp [2] and (x14, y14) of fp [3]. As flick operation information, 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 is preferably calculated using the immediately preceding two or more frames. As an example, the flick direction is preferably used so as to correspond to the direction in which the object is operated in the game space, and the flick distance is preferably used so as to determine the speed of the action on the object. Thus, by obtaining a limited number of position coordinates, various operation parameters relating to the slide operation can be specified.

(D) Flick operation determination and flick operation type determination (S310)
With reference to FIGS. 8 and 9, the flick operation determination and flick operation type determination processing (S310) by the flick operation determination unit 204 will be further described. FIG. 8 shows the detailed processing flow of S310. FIG. 9 shows a graph example of flick (slide) operation information as an example. The horizontal axis of the graph indicates the frame F in a predetermined frame rate unit, and the vertical axis indicates 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-1) th 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 the slide distance in the flick operation information is greater than or equal to the threshold value TH1 (S501). Specifically, it is determined whether the slide (flick) distance plotted in the immediately preceding n-1 frame F [n-1] or the immediately preceding n-2 frame F [n-2] is greater than or equal to the threshold value TH1. Is done. In the case of “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, in the case of “No”, it is determined that the flick operation is not established, and the operation on the object is not executed, and the process ends with the swipe process. When two flick distances of F [n−1] and F [n−2] are used, it is preferable to determine whether the flick operation is established when both are equal to or greater than the threshold value TH1. That is, even if only the flick distance for one frame of F [n−1] is greater than or equal to 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 and up to 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 them from tap operations in which only the operation information of only the immediately preceding frame is determined. Note that not only the flick distance but also the flick direction may be determined using the frame used in the above determination. The direction in the latest frame may be determined as the flick direction, and when a plurality of frames are used for determination, the direction of the oldest frame may be determined as the flick direction. In addition, the average direction of each frame may be calculated and determined as the flick direction.

  If it is determined in step S501 that the flick operation is established, the flick operation type is further determined based on the flick distance. The flick operation type includes a “strong” flick operation and a “weak” flick operation. That is, it is determined whether the flick distance is greater than or equal to a 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 preferable that the maximum value among them is compared with the threshold value T2. That is, in FIG. 8, since the flick distance of F [n−1] is the maximum value and larger than TH2, the flick operation type is set to “strong” flick operation here. The flick operation type is associated with the operation to be performed.

(E) Implementation of operation on object (S311)
With reference to FIG. 10 to FIG. 12, the processing (S311) of performing the action on the object (that is, the action on the ball by the character) by the kick action 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 region (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 300 to 500 of action tables related to the action of the character on the ball. The table group shown in FIG. 12 and FIG. 13 is reflected on 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 motion area (S602). In the case of “Yes”, it is further determined whether the direction in the game space corresponding to the slide direction acquired in S403 is in the goal direction (S603). In the case of “Yes”, an operation of a specific action type of “shoot” in the flick direction is associated with the flick operation (S604). On the other hand, if “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 type action is associated with the flick operation, the actual action is performed according to the action type and the flick operation type set in S503 and S504 (S606). When the operation is performed, an animation related to the action in the flick direction of the character or the ball is reproduced according to the content.

  Position data of each object such as a character or a ball arranged on the field FD is managed by field coordinates (XY coordinates). S602 and S603 are also preferably determined in the XY coordinate system. The XY coordinate system may be any as long as it can define a two-dimensional plane in an orthogonal 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 in FIG. 11, the player character CH12 is arranged so as to be included in the shoot range SR. In the action region of the shoot range SR, the player character CH12 performs a “shoot” action in response to the flick operation. The shoot range SR includes the goal area GA and the penalty area PA, but is not necessarily limited to this. Further, the shape of the chute range SR is not limited to a rectangle. The shoot range SR is preferably configured to be different for each character according to the characteristics of the character (player). Character characteristics are managed by a character table 200 in the storage unit 110 as shown in FIG. Specifically, in addition to general character information such as the character ID, player name, belonging team (own team / partner team), and position, in one embodiment, the shooting power (for example, 60/100) is used. Parameters should also be managed as character characteristics. That is, the shooting range SR is preferably set for each character based on the shooting power. For example, a player who is good at middle shots 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 to these. In addition, the dominant hand (right-handed / left-handed) may be managed and reflected in the configuration of the shoot range SR. For example, in FIG. 11, the goal direction in S <b> 603 is a goal formed by providing an angle α (solid line) outward from the left / right direction of the goal (goal post directions gd <b> 1, gd <b> 2 (dotted line)) with respect to the position of the player character CH <b> 12. It is defined as a direction toward the direction area 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 a slide operation / motion table 300, a flick operation / motion table 400, and a flick operation / specific motion table 500, but is not necessarily limited thereto.

  The slide operation / motion table 300 defines a default motion corresponding to a slide operation type. In the case of a flick operation, a “kick” operation is associated. That is, in the case of the flick operation, the “kick” operation is determined as the default operation. In S307 of FIG. 5, the “dribbling” operation associated with the swipe operation is also determined by referring to the slide operation / operation table 300. The flick operation / action table 400 defines default actions according to the flick operation type. A “high trajectory” is associated with the “strong flick” operation whose flick operation type is “strong flick”, and a “low trajectory” is associated with the “weak lick” operation. Based on the slide operation / motion table 300 and the flick operation / motion table 400, for example, when the flick operation type is set to “strong flick” operation in S503 of FIG. Determined as action. Similarly, when the “weak lick” operation is set in step S504, “kick” of “low trajectory” is determined as an action. In addition, the flick operation / specific action table 500 defines a specific action type according to the target action area. As an example, a specific action type “shoot” is associated with the flick operation in the shoot range SR. In the own penalty area PA2, a 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 a partner corner area and associating “centering” as the specific action type. If the player character CH is not located in any of the motion areas defined in the flick operation / specific motion table 500, the “kick” that is the default motion in the slide operation / motion table 300 is performed as it is.

  In the example of FIG. 13, at least the following six operation patterns are assumed depending on the contents of “flick operation type” in the flick operation / operation table 400 and “specific action type” in the flick operation / specific operation table 500. . That is, “shoot” operation of “high trajectory”, “clear” operation of “high trajectory”, “kick” operation of “high trajectory”, “shoot” operation of “low trajectory”, “clear” of “low trajectory” Operation, “low trajectory” “kick” operation. In S606, one of these at least six operation patterns is performed in the direction in the space corresponding to the flick direction. In addition, the said example is only an example and is not necessarily limited to these.

  In this way, simple and intuitive touch operability can be provided to the user in the sense that various operations can be assigned to the user's flick operation. In addition, the game can smoothly proceed by allowing the character to perform a complex motion on the ball while maintaining simple operability.

(F) UI image generation processing (S306)
With reference to FIG. 14 and FIG. 15, the UI image generation unit 206 further generates a UI image and displays it on the touch display (S306). FIG. 14 shows a schematic diagram of a UI image generated according to an 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 waterdrop-shaped elastic body having a base BP, a tip TP, and a connecting portion CP between them. As shown in FIG. 15A, the initial shape of the elastic body is circular. It will be understood by those skilled in the art that the shape of the elastic body can be formed by a set (mesh) of a plurality of polygons made of a square or a triangle. That is, the water droplet shape of the elastic body can be reproduced by substituting each vertex coordinate of each polygon into a predetermined mathematical expression. As shown in FIGS. 15A to 15C, through a series of slide operations, the UI image has a base BP of the elastic body fixed at the touch start point and the tip TP of the elastic body follows the touch position of the finger. It is good to form like this. For each frame rate, a UI image in which the elastic body elastically deforms and expands and contracts is displayed. A predetermined upper limit value is provided for the length from the base BP to the tip TP. If the upper limit value is exceeded, the UI image is displayed so that the tip TP is separated from the finger position.

  In the UI image generation process of S306, touch position information (coordinates of touch start points) acquired in a touch-on state by the touch position information acquisition unit 201 is stored. Further, the touch position information (current coordinates of the touch point) currently acquired in the touch now state by the touch position information acquisition unit 201 is stored each time. First, a distance d between the touch start point and the current touch point is calculated (S701). It is determined whether the distance d is less than or equal to the upper limit value D (S702). In the case of “Yes” (for example, 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 part BP and the tip part TP are displayed and further displayed so as to be connected by the connecting part CP, and the UI image I of the elastic body is generated (S707 / (b) and (c) in FIG. 15). )). Thereby, the UI image is displayed through the slide operation in such a manner that the elastic body is deformed in accordance with the change of the current touch point. 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 now the touch start point. To the current touch point is associated with the position of the point separated by the upper limit distance D (S706). Then, similarly to the above, the elastic body UI image I is generated (S707). As shown in FIG. 15D, the current touch point and the tip portion TP are in a separated positional relationship. The upper limit D is set for the length from the base part BP to the tip part TP because the operation distance becomes longer due to a complicated slide operation particularly in a “dribbling” operation (for example, FIG. 4A) in a soccer game. is there. In soccer, there are many player characters in the field FD. Even if the operation distance is long, if the UI image of the elastic body that follows it is completely displayed, the player character is covered with the UI image and hidden on the game screen.

  Returning to FIG. 16, when a UI image is generated in S708, visual processing is further performed on the elastic UI image according to the distance d between the touch start point and the current touch point (S708). ). For example, in the state of FIG. 15B, the color processing is performed so that the UI image becomes white, and in the state where the distance d in FIG. 15D reaches the upper limit value D, the different color processing is performed so that the UI image becomes light blue. Is 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 two immediately preceding touch position coordinates as shown in FIG. 6A. The indicator IND (arrows in FIGS. 15B to 15D) regarding 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). Thus, the present invention provides a user with simple and intuitive touch operability. In addition, while maintaining simple operability, it is possible to perform a complex operation on the game object and smoothly advance the game.

  The above-described embodiments are merely examples for facilitating understanding of the present invention, and are not intended to limit the present invention. The present invention can be changed and improved without departing from the gist thereof, and it is needless to say that the present invention includes equivalents thereof.

Claims (13)

When executed by a computer comprising a touch display,
Detecting arbitrary position information on the touch display and repeatedly acquiring the touch position information for each predetermined frame rate;
Determining first operation information based on a predetermined number of the touch position information;
Performing a first action on a moving object in the game space based on the first operation information;
Determining a touch-off from the touch display;
Determining second operation information using the touch position information in at least one frame immediately before the touch-off;
Determining a flick operation based on the second operation information;
Executing the method including the step of releasing the first operation in response to the flick operation and performing the second operation on the moving body based on the second operation information;
The first action moves the moving body to move in the game space together with the character,
A game program in which the second action moves the moving body to move in the game space away from the character.   The game program according to claim 1, wherein in the step of determining the touch-off, the touch-off is determined when the touch position information cannot be continuously acquired over a plurality of frame rate units. The game program according to claim 1 or 2,
The second operation information includes a flick direction in the at least one previous frame,
A game program in which, in the step of executing the second action, the second action is executed in a direction of the game space corresponding to the flick direction. 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 previous frame,
In the step of determining the flick operation, a flick operation type is determined based on the flick distance,
A game program in which in the step of executing the second operation, an operation associated with the flick operation type is executed. The game program according to claim 4,
The game program in which the flick operation type is determined based on whether the maximum value of each flick distance in the immediately preceding two or more frames is within a range defined by a predetermined threshold. 6. The game program according to claim 4, wherein the step of performing the second operation on the moving body further includes:
Determining whether the position of the character is included in a predetermined motion area in the game space;
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 motion area is configured based on characteristics of the character. The game program according to claim 6 or 7, wherein the game program is applied to a soccer game,
The first action is a “dribbling” action to the moving body by the character;
The second action is a “kick” action to the moving body by the character;
In the second operation, the specific action type is associated with a “shoot” operation. A game program according to claim 8, wherein
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 “high trajectory” and the “weak” flick operation is associated with “low trajectory”. The game program according to any one of claims 1 to 9, wherein the method further includes:
In accordance with the step of repeatedly acquiring the touch position information, an image is generated and displayed in association with the first touch position information detected for touch-on and the second touch position information currently detected for each frame rate. Step,
The image is an image of an elastic body having a base and a tip;
The base is associated with the first touch position information, and the distal end is associated with the second touch position information for each frame, so that the elastic body is changed along with the change of the second touch position information through a slide operation. A game program in which the image is displayed so as to deform. The game program according to claim 10, wherein the step of generating and displaying the image includes:
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 associated with position information separated by an upper limit value. 12. The game program according to claim 10, wherein the step of generating and displaying the image further comprises:
A game program including a step of performing visual processing on an image of the elastic body according to a distance between the base and the tip.   The game program according to any one of claims 10 to 12, wherein the step of generating and displaying the image further associates an index indicating a slide direction based on current second touch position information with the tip portion. A game program comprising the step of displaying together with the image.