JP2001282953A - Game record input device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a game record input device where extra burden is not given to a person inputting record even if a plurality of game events are continuously generated in the input device of the game record of a soccer and the like or the game record input device where point-scoring can more minutely be recorded. SOLUTION: The game record input device is provided with a basic information input means inputting and recording basic information required for game record prior to the start of a game, an event recording means displaying a game record picture and inputting the various game events as game record, and an information storage means storing basic information and game record. The event record means is provided with a function for making a game event processing generated later interrupt the event when the other game event is generated during one game event processing so as to solve a problem. A field map-type input interface can more minutely and easily input point-scoring record.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a game record input device for efficiently recording the contents of a game such as a soccer game.

[0002]

2. Description of the Related Art As an input device for recording the contents of a soccer game, Japanese Patent Application Laid-Open No. HEI 8-222478 has been filed by the same applicant as the present invention. A soccer game recording device (conventional device) based on the present invention has been put to practical use, and has been used in games of the Japan Professional Soccer League (J-League) and the like.

The conventional device is a revolutionary device that can create an official record of a soccer game with a very simple operation using a portable small personal computer. That is, prior to the match, basic information necessary for the match record, such as a member table of both teams, is received as a data file, and basic information input means held inside the device, a shot, a corner kick, a score generated during the match, Player substitution,
Event recording means for inputting various competition events such as warnings and exits, a function to display a game record screen that displays at least the player name for each team and the occurrence and results of the competition event for each game stage, When entering,
A function of displaying a window for inputting a plurality of items to be input for a competition event by selecting a key from the game record screen, and displaying the input window sequentially for each item in a predetermined input order. It is provided with.

[0004]

However, the following inconveniences and points to be improved have been clarified during the practical use of the conventional apparatus for official recording of a soccer game. one,
In the conventional device, there is inconvenience when the next event occurs during the input of one competition event. During an actual game, competition events may occur at one time in a row. For example, when the event of the occurrence of a foul → warning → shoot occurs in succession, the conventional device performs the event processing of the foul, which team has committed what kind of foul, and which player gives a warning for what reason. Only after the input has been received can the event processing of the shoot be input. Therefore, for example, when the reason for the warning is not known, it is necessary to input "unknown" for the time being and immediately proceed to the event processing of the shoot. The fact that it is necessary to end the event processing during input quickly, and that the event record that has been completed for the time being must be repaired later, are burdens on the record input user.

[0005] Further, a score progress input is performed in order to record the progress of the score in a record. At this time, an expression of a position in the pitch at which a shot or a pass or dribble leading to the shot was performed is performed. However, since there are only three ways to express the pitch, right side, left side or center, it is not possible to express far or near to the opponent's goal, and there is an inconvenience that the score progress can be recorded only roughly. .

The present invention has been devised in order to solve the above-mentioned drawbacks of the conventional apparatus. In an apparatus for inputting a game record such as a soccer game, even when a plurality of competition events occur continuously, the recording is performed. It is an object of the present invention to provide a game record input device that does not put an extra burden on an input person and a game record input device that can describe a score progress record in more detail.

[0007]

According to a first aspect of the present invention, there is provided a basic information input means for inputting and recording basic information necessary for a game record prior to the start of a game. Event recording means for displaying a recording screen and inputting various competition events occurring during the game as a game record,
In the game record input device comprising the basic information and the information storage means for storing the game record, the event recording means may be generated later when another competition event occurs during one competition event recording process. By providing a function that can interrupt the competition event recording process that has been performed, it is possible for the record entry person to proceed to the processing of the event that occurred later without terminating the event being processed. The burden on people.

In a preferred embodiment of the present invention, in the game record input device, a game event record process interrupted by another game event record process and interrupted is iconified and displayed on a game record screen.
The event recording means may be configured to return to the process of recording the competition event by selecting the icon. By configuring the event recording means in this way, the burden on the record input person is further reduced.

A second invention for solving the above-mentioned second problem is a basic information input means for inputting and recording basic information necessary for a game record before starting a game, and displaying a game record screen to display a game record screen. A game record input device comprising: an event recording unit for inputting various competition events occurring therein as a game record; and an information storage unit for storing the basic information and the game record. At this time, a score progress input screen is displayed, and a panel imitating a field is divided into 3 to 20 sections on the screen, and a field map type input interface in which buttons representing each section are arranged on the panel is prepared. By selecting this button, it is possible to easily describe the detailed position of the shot or pass.

Further, as a preferred embodiment of the second invention, a button representing a corner kick is added to the four corners of the field map type input interface, and by selecting this button, which corner is inputted when the score progress is input. You may make it easy to describe whether it is a kick or not.

[0011]

Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a block diagram showing a configuration of a game record input device according to one embodiment of the present invention. In FIG. 1, a soccer game record input device 10 is shown.
Comprises an information storage means 11 and a computer main body 12. Information storage means 1 realized by a hard disk or the like
1, a format file 20 for storing a plurality of types of display and print formats for recording the contents of a soccer game, a game information file 21 for storing conditions for recording a game, a player name, a position, and a soccer game. Basic information file 22 that stores basic game information other than the content of the competition, an event record file 23 that records a competition event that occurs during a soccer game, and a logo mark file that stores a logo of a tournament sponsor, a team, and the like. 31 is provided.

Further, the computer main unit 12 has an input unit 24 for inputting basic information and a game record, an information read / write processing unit 25 for reading / writing a floppy (registered trademark) disk 50 and the like, and a graphical user interface (hereinafter referred to as GUI). ), Basic information input means 26 for receiving input of basic information, event recording means 27 for receiving input of a competition event that occurs during a game by the same GUI, and total calculation processing section 29 for performing total processing relating to the input game record. , A print control processing unit 28 that outputs a match record or a match member table or the like to the printer 60 in accordance with the selected format, and a communication processing unit 30 that exchanges data with the host computer.
The game machine includes a display section 40 for displaying basic information and a game record of a soccer game, and a printer 60 for printing and outputting the game record and the member table.

The basic information file 22 includes the name of the organizing organization of the soccer game, the names of registered players of each team, the names of officers,
Basic information necessary for making a competition record, such as the number of each player and the position of the player, is stored.

The game information file 21 stores conditions for recording a soccer game. Conditions for the match record by the organizing body or the tournament, such as match time, presence or absence of overtime, time display method, number of players that can be replaced, whether or not to record in detail the various competition events that occur during each match If the flag information and the like are different, the recording conditions for each sponsoring organization or each tournament are stored.

The format file 20 stores various display formats for recording basic information and details of a soccer game, and a print format for printing out a game record or a member table.

The event record file 23 includes information on competition events such as shots, direct / indirect free kicks (FKs), scores, and the like during a soccer game, as well as warnings / exits and substitutions (entrance times) for each player. The information is stored as a game record. These game events are input from the input unit 24 by the recorder after the start of the game.

The logo mark file 31 stores a tournament logo, an official sponsor of the tournament, or a team logo as image data. These are printed when the official record is printed out by the print control processing unit 28.
Output in the margin.

Next, an outline of processing when a soccer game record is performed by the game record input device 10 configured as described above will be described with reference to the flowchart of FIG.

(Basic Information Input) First, the recorder first prepares the basic information of the game (player names, uniform numbers, positions, etc. of the participating teams) and the game information (game time, extension) registered in the host computer in advance. The presence / absence of a battle, extended time in a certain case, presence / absence of a PK battle, etc.) are read via a communication line, a floppy disk 50, or the like, and the
And it is stored in the game information file 21 (S301).
Necessary logo marks are also read at this time and stored in the logo mark file 31.

(Input of Participating Members, etc.) Next, the person in charge of recording each game of the tournament activates the game record input device 10 at the match venue, and a main menu screen 400 as shown in FIG.
Is displayed. This main menu screen also shows the work flow of the recording staff. That is, before the game starts,
The starting team of the opponent team and the member reserve members are input, a member table is created and printed, and natural environment information and the like are input (S302).

(Match Content Input) After the game starts, the game record creation button 406 is selected from the main menu 400 and the game content is input (S303). The details of the game content input processing will be described later.

(Post-processing) After the game is over, the game result print key 407 is selected and the game result is printed (S304).
At this time, the tally calculation processing unit 29 tallies the game record data and creates a match record including the tally result according to a predetermined official record format. The game record is distributed to the tournament officials and the like via the print control processing unit 28 in FIG.
Print out as an official record sheet. In this official record sheet, if the data is stored in the logo mark file 31, the tournament logo, the tournament sponsor,
Or you can easily put your team logo. Then, the game record is written out to a floppy disk or the like (S
305) End one game record. When the game record of the same tournament is input, step S301 may be omitted next time. The processing steps other than step S303 are the same as those of the conventional apparatus (Japanese Patent Application Laid-Open No. H08-221478), and thus detailed description is omitted. Hereinafter, step S303 and the step of inputting the game content will be described in detail.

The game record creation key 4 of the main menu 400
By selecting 06, the kick-off team selection screen shown in FIG. 6 is displayed. This is a kick-off team setting window 600 appearing on the base screen 700 for inputting the game content in FIG. Here, the recording clerk sets the team that kicks off the match (the team that lost the toss) by watching the situation of the coin toss on the field.
At this time, the end may change. In this case, the end is changed by clicking the end change button 601 so as to match the situation viewed from the recording staff (from the main stand side). By pressing the confirmation button 602, the kick-off team setting window 600 disappears and the base screen 700 of FIG. 7 is displayed. When the first-half start button 701 is clicked with the referee's kick-off signal, the time display of the clock starts, and all the buttons of the event button group 1000 except for the change, warning / exit, and environment buttons that were originally inputtable are displayed. It becomes selectable, the main menu return button 1010 becomes unselectable, and the game content is input. This state is shown in FIG.

Hereinafter, the game content input processing after the start of the game will be described focusing on parts different from the conventional apparatus. First, a function that can hold an event input will be described.
First, the operation of the screen interface will be described, and then one implementation example will be described.

FIG. 11 shows a foul event recording screen 1100 that appears as a result of clicking the foul button 1005 from the base screen of FIG. 5 to input a foul generated at 5:28 in the first half (6 minutes in recording). Where
The team that committed the foul is selected by the team selection button 1101, and then the foul type is selected from a group of 1102 buttons. Finally, by clicking the confirmation button 1103, the screen returns to the base screen in FIG. 5, but before this series of input processing is completed, the next event, such as a warning or exit, may occur. In such a case, in the game record input device 10, before pressing the confirmation button 1103, the warning / exit button 1006 can be clicked from the lower event input button row to switch to the alarm / exit record input. FIG. 12 shows a warning / exit record input screen 1200 displayed at that time. Here, an object column 1201 displayed on the upper left of the screen indicates an event for which input has not been completed (pending event) and the presence of an event currently being input.

The object displaying the suspension event is displayed at the same position even when returning to the base screen. FIG.
Is a screen in which four events have been held back and returned to the base screen because events have occurred consecutively. The display label 1301 of the pending event displayed at the upper left position is actually a button, and when one of these buttons is clicked, it is possible to return to the input operation of the pending event displayed on the label.
In this apparatus, up to nine events can be held.

FIGS. 9 and 1 show a concrete example of the event recording means 27 capable of holding such an event input, that is, interrupting another event input during the event input.
0 and the flowchart of FIG. In these flowcharts, a graphical user interface (GUI) can be implemented using event-driven software components, such as forms in Visual Basic (such software components are also referred to as forms in the following description). It assumes a computer environment.

A form is a software component as described below. That is, it has properties of a display style (screen) describing the size and position of I / F parts such as buttons and character display boxes to be placed thereon, and recognizes an input event to those I / F parts. A software component having an event recognition function for identifying and having a function of calling and executing a corresponding processing routine when each input event occurs. However, when the form is not displayed, the above function does not work.

In step S303, a game record is prepared.
It has a display style of the GUI screen 700 and displays a game record main form F001 for executing various interactive processes.
Then, the initialization process defined in the match record form is executed, and then the kick-off setting process described above is performed (S900 in FIG. 9), and the process waits for the start button (S90).
1). When it is determined that the start button has been pressed, the time measurement of the clock starts (S902), and the screen waits for input of the screen (FIG. 5) (S903).

Here, the game record main form F001
When the upper object is selected and some screen input occurs, the game record main form F001 detects what the selected object (button) is (S904),
Call the corresponding processing routine. For example, when the foul button 1005 is clicked, processing of a foul event starts below. First, the call flag is set as a new event (S905), and the foul recording form F00
5 is displayed (S907). At this point, the screen is switched to the foul recording screen of FIG. 11 instead of the base screen.

The initialization processing described in the foul recording form F005 is executed. First, the call flag is checked (S700 in FIG. 10). If the call flag is a new event, an event identification number and an occurrence time assigned from 1 in the order of occurrence of the event are acquired and stored in a work memory, which is a work storage area (S702). If the call flag is a hold event, the record of the event is copied to the work memory from the hold event list (S70).
4). If the value of the call flag in the case of a new event is 0, and in the case of a hold event, the event identification number (positive integer) of the hold event is the value of the call flag, S700, S700
This is convenient for the process of 704. After that, it is in a state of waiting for input (S706).

Here, foul recording form F005
When the above object, that is, any button on FIG. 11 is selected, foul recording form F005
Detects what the selected object (button) is (S708), and calls the corresponding processing routine.

The operation in the event that there is no event interruption will be described first. In a normal case, the selection button 1101 of the team that committed the foul is clicked. Then, the selected team is recorded in the work memory (S71).
1) The name of the team selected for confirmation is displayed on the screen (S713), and the process returns to S706. The next event that normally occurs is the selection of the foul type button group 1102. In this case, first, it is checked whether the team name has been selected (S715), the selected foul type is recorded in the work memory (S717), and a confirmation display is performed (S717).
719), and return to S706. If a team name has not been selected in S715, the process immediately returns to S706. The next event that normally occurs is the selection of the confirm button 1103. In that case, first, it is checked whether both the team name and the foul type have been recorded (S721). If the team name and foul type have already been recorded, the recording of the foul event has been completed successfully, and the contents of the work memory are transferred to the event list (S7).
23), and sets the return flag to “normal” (S72)
5), delete foul recording form F005 (S
727). Then, the game record main form F001 returns to the active state, and the base screen 700 is displayed.
Since the calling of the foul recording form in step S907 of FIG. 9 has been completed, in step S909, the return flag is checked. In the case of "normal" end, the process returns to S903 and waits for screen input again. The above is the flow of processing when there is no event interruption.

Next, an operation when an interruption of another event occurs during the recording of a foul event will be described. S7
If the received screen input is one of the event button rows at the bottom of the screen at 08, the contents recorded in the work memory, that is, the event identification number, the event type, the occurrence time, The other information is saved in the area of the available hold number in the hold event list. The pending event list is a memory buffer for temporarily recording information of the pending event, is composed of nine recording areas, and records the contents inputted until one pending event is saved in one of the recording areas. . The interrupted event type is stored in the common variable “interrupt event type record”, and the return flag is set to “interrupt” (S7).
31), the foul recording form F005 is deleted (S733). Then, the game record main form F00
1 returns to the active state, and the base screen 700 is displayed. Foul recording form F00 in S907 of FIG.
Since the calling of No. 5 has been completed, in step S909, the return flag is checked. If the "interrupt" is completed, the process jumps to S980 in FIG. In S980, a button of the suspended event is created and put on the game record main form F001. Actually, the game record form is provided with nine buttons for the hold event from the beginning, but in the initial state, all buttons are hidden and input is not accepted. When a pending event is created, the time and event type are set in the label properties of the pending event button equal to the pending number of the pending event from the information of the pending event held in the pending event list, and the input can be accepted. (That is, display ON). At this point, a pending event button column 1301 is displayed including the latest pending event. Next, an interrupt event type record (this is S
71, updated at 731), E1, E2,
.. (S982), and thereafter, the recording work of the interrupt event can be started.

Next, from the state of the screen shown in FIG. 8 (a screen in which four events have been suspended and the state has returned to the base screen while retaining the four events), one of the suspended event buttons is displayed. The operation in the case where is selected will be described. When any one of the hold event buttons 1 to 9 is selected in S904, the hold button number is first recorded in a common variable “save number save” (S800). Next, the "hold event" is set in the call flag (S80).
2). Then, the type of the hold event is specified from the properties of the hold button (S804), and the corresponding event recording form is displayed (S806,..., S88).
6). Thus, the recording of the suspended event is resumed. S in FIG. 10 for foul event recording
Fly to 700. Since the call flag is "hold event", the data input up to the middle of the hold event from the recording area of the hold event list corresponding to the hold number previously saved in S800 is returned to the work area (S800).
704), input is restarted.

In the above description, the relationship between the game record main form F001 and the foul recording form F005 has been described, but it is necessary to prepare an event recording form for each button of the event button group 1000. The flowchart of FIG. 10 can be considered in three parts. The first part is S700, S702, and S704 for performing initial processing when displaying a form (when called). The second part is a series of steps S729, S731, and S733 for performing processing when an interrupt event occurs. Third, a part that performs a process specific to foul recording (the rest of the rest). Accordingly, in each event recording form, the first and second portions are foul recording forms F0.
05. Only the portion corresponding to the third portion may be created according to each event record. Also, as common variables for communicating between the game record form F001 and each event record form, a call flag,
Since a return flag, an interrupt event type record, and a hold number save are required, their storage areas may be secured.

Next, the score progress recording process of the game record input device 10 will be described. First, the flow of the screen operation will be described. FIG. 16 shows the score progress recording first screen 1600 displayed first in step S917 of FIG. Here, the score event up to that point is the score list 1601
Is displayed in. The operator selects a scoring event that has not yet been entered or that he wishes to re-enter. The cells from progress 1 to progress 7 of the selected scoring event are highlighted. The operator clicks the progress input button 1602 after confirming that the selection has been correctly made in reverse video.

Then, the score progress record main screen 14 of FIG.
Switch to 00. The score progress record main screen 1400 includes:
Field map type interface 1401, set play selection button group 1402, player selection button group 140
3, play type button group 1404, score progress description field 14
05 and the like. The worker
From the field map type interface 1401, a button corresponding to the position where the play has been performed is selected, then the player's number button of the player who handled the ball is selected from the player selection button group 1403, and the content of the play is selected from the play type button group 1404. Is selected, and in the score progress description field 1405,
A score progress description as shown in FIG. 17 is created. FIG.
At "Left-3", the "No.4" player enters "Center-2" with "Dribbling" and gives a "Floating Ball Pass".
The "28th" player at the "right-1" point returned the "pass" (centering) and ran at the "center-1" point.
This expresses that the "Ban" scored by "Shooting with the right foot" in "Direct".

The play position described in the score progress is shown in FIG.
As shown in the figure, the left side, right side,
Or, in the order of the center and the closest to the opponent's goal, for example,
1, right-2, right-3, right-4 are represented by 12 sections. The recording technician may select the field position button viewed from the recording technician side (main stand side) from 1401 as it is. In the field position button input processing, which of the teams has the progress input related to the score is memorized, so that it is automatically recognized as "right -1" or "left -4" and the progress description field Displayed at 1405.

In the field map type interface 1401 shown in FIG. 14, a corner kick button is also arranged at the corner kick position. A corner kick is a kind of resuming play (set play).
Although it may be arranged in the button group of 1402, it is not necessary to determine whether the button is a right CK or a left CK when viewed from the attack direction by arranging the buttons in the field map as in the embodiment. So convenient.

An example of the score progress recording process described above will be described with reference to the flowchart of FIG. FIG. 19 is an operation flow of the score progress recording form F002. Steps S600, S602, and S604 are routine processing according to the call flag. In the case of a new event, after step S602, form F handling the first screen 1600
0021 is displayed, and the team name and the event number are obtained. In step S608, the position N of the progress input column is set. The value is 1 for a new event, and the subsequent value for a pending event. If any one of the position buttons on the field map type interface 1401 is clicked, the position display is inverted if necessary according to the team name in S620, and the result is recorded in the cell of the progress column. Then, the entire progress column is displayed again, the cell position in the progress column is updated, and the process returns to the input waiting state (S610). FIG.
S620 of FIG. 7 shows only the case of the right -4 button,
There is actually a respective process for each of the twelve individual buttons. When any of the buttons 1402, 1403, and 1404 is clicked, the display content of the button is recorded in the cell of the progress column. The entire progress column is displayed again (S632), and the process returns to S609. If the confirmation button is clicked, the entire progress column is saved as an official record in another storage area (S640), the return flag is set to "normal" (S642), and the current form is erased (S640). (S644), and returns to S919 of FIG.

In the conventional device, when describing the progress of the score,
I just had to select from the three buttons "Right", "Left" or "Center", so I couldn't describe in detail whether it was near or far from the goal. With the use of the field map type interface 1401, the recording staff can correctly describe the field positions of the twelve sections by changing the direction by the team simply by selecting the button at the position as seen by the recording person.

FIG. 20 shows the relationship between the forms described above together with the pending event list.

As described above, one embodiment (embodiment) will be described with respect to the function of holding the event and the function of recording the progress of the score in more detail by the field map type I / F, which are improvements from the conventional apparatus. explained. These forms operate on a computer to implement the event recording unit 27. However, the invention is not necessarily limited to the implementation. For example, the ability to allow interruption of other event entries during event recording may be implemented in other ways than described herein. Although the number of events that can be held is nine in the present embodiment, the number is not limited to nine.

The field map type I / F is not limited to the case where the number of sections representing the field position is 12, and may be divided into 15 sections as shown in FIG. 15, for example. However, if the size is too small, the burden on the recording person is imposed.

【The invention's effect】

Since the recording of the competition event can be suspended and the recording of the competition event generated later can be interrupted, the burden on the record input person is remarkably reduced as compared with the conventional apparatus, and the recording mistake and the correction can be made. I have not forgotten. Also,
Since the field map type I / F is adopted, the progress of the score can be described in more detail as compared with the conventional device. Moreover, since the image can be input as viewed from the field, there is no burden on the record inputting person.

[Brief description of the drawings]

FIG. 1 is an overall configuration block diagram of a game record input device.

FIG. 2 is an example of a game record output sheet.

FIG. 3 is a schematic flowchart of a game record creation operation by the game record input device.

FIG. 4 is a main menu screen of the game record input device.

FIG. 5 is a base screen during a match.

FIG. 6 is a kick-off setting screen.

FIG. 7 is a base screen immediately before a match starts.

FIG. 8 is a base screen with a pending event display.

FIG. 9 is a flowchart of a game record creation form.

FIG. 10 is a flowchart of a foul event recording form.

FIG. 11 is a foul event recording screen.

FIG. 12 is a warning / exit event recording screen.

FIG. 13 is a flowchart (part) of a game record creation form.

FIG. 14 is a score progress recording screen.

FIG. 15 is another field division example of the field map type interface.

FIG. 16 is a first screen of a score progress input.

FIG. 17 is an example of a score progress description.

FIG. 18 is an explanatory diagram of a play position in the field map type interface.

FIG. 19 is a flowchart of a score progress input form.

FIG. 20 is a diagram showing relationships between forms.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 10 Game record input device 11 Information storage means 12 Computer main body 20 Format file 21 Game information file 22 Basic information file 23 Event record file 24 Input part 25 Information read / write processing part 26 Basic information input means 27 Event recording means 28 Print control processing part 29 Total calculation processing unit 30 Communication processing unit 31 Logo mark file 40 Graphic monitor 50 FD, etc. 60 Printer 600 Kickoff setting window 700 Game record base screen 1100 foul event record screen 1600 score progress record screen

Continued on the front page F term (reference) 5B049 AA01 BB61 DD01 DD05 FF02 FF03 5E501 AA17 AC35 BA05 CA02 CB02 CB09 EA05 EA11 EB05 EB15 EB18 FA23 FA44 FB03 FB28 FB32 FB43

Claims (4)

[Claims] 1. A basic information input means for inputting and recording basic information necessary for a game record prior to the start of a game, and an event for displaying a game record screen and inputting various competition events occurring during the game as the game record. A game record input device comprising a recording means and an information storage means for storing the basic information and the game record, wherein the event recording means generates another competition event during one competition event recording process. A game record input device having a function of interrupting a game event recording process that has occurred later. 2. The game record input device according to claim 1, wherein the game event recording process in which the recording process is interrupted due to being interrupted by another game event process is iconified,
A game record input device, wherein the event recording means is configured to be displayed on a game record screen and to return to the process of recording the event by selecting the icon. 3. A basic information input means for inputting and recording basic information necessary for a game record prior to the start of a game, and an event for displaying a game record screen and inputting various competition events occurring during the game as a game record. A game record input device including a recording unit and an information storage unit that stores the basic information and the game record, wherein the event recording unit displays a score progress input screen when a score progress input is performed,
On the screen, the panel imitating the field is 3 to 20
A field map type input interface is provided which is divided into sections and buttons representing each section are arranged on the panel, and a shot or pass position can be described by selecting this button. apparatus. 4. The game record input device according to claim 3, wherein a button representing a corner kick is added to each of the four corners of the field map type input interface, and by selecting this button, a score progress input is performed. A game record input device capable of easily describing a corner kick.