JP4357690B2 - Game record input device - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a game record input device that efficiently records game content such as soccer.
[0002]
[Prior art]
Japanese Patent Laid-Open No. 8-221478 has been filed by the same applicant as an input device for recording soccer game content. A soccer game recording device (conventional device) based on this invention has been put into practical use and operated in a game of the Japan Professional Soccer League (J League).
[0003]
The conventional apparatus is an epoch-making apparatus that can create an official record of a soccer game by a very simple work using a portable small personal computer. In other words, prior to the game, the basic information required for the game record, such as the member tables of both teams, is received as a data file, and the basic information input means that is held inside the device, shots, corner kicks, scores, A function for displaying event record means for inputting various competition events such as player substitution, warning / exit, and a game record screen for displaying at least the name of the player and the occurrence and result of the competition event for each game stage for both teams; When inputting a competition event, by selecting a key from the game record screen, an input window is displayed for each item for a plurality of items to be input regarding the competition event, and each item is sequentially input according to a predetermined input order. A function for displaying an input window is provided.
[0004]
[Problems to be solved by the invention]
However, the following inconveniences and points to be improved became clear when the conventional device was put to practical use in soccer game official records. For example, in the conventional apparatus, there is inconvenience when the next event occurs while one competition event is being input. During an actual game, competition events may occur continuously at a time. For example, when a foul occurrence → warning → shot event continues, the conventional device performs foul event processing, which team has committed what type of foul, and which player warns for what reason. The event processing of the shoot could not be input unless it was input whether or not it was received. Therefore, for example, when the reason for the warning is not known, it is necessary to input “unknown” for the time being and immediately move to the event processing of the shoot. It is necessary for the event processing being input to be completed quickly, and for the time being, it is necessary to revise the event record after it has been completed, and this has been a burden on the record input person.
[0005]
In addition, the score progress input is performed in order to record the progress until reaching the score. At this time, the expression of the position where the shot or the pass or dribble leading to the shot was performed is represented by the pitch. Since there are only three ways to express the right side, left side, or center, it was inconvenient that it was not possible to express whether the distance to the opponent's goal was far or near, and the score progress could be recorded only roughly.
[0006]
The present invention has been devised in order to eliminate such drawbacks of the conventional apparatus.
In a game record input device such as soccer, even if multiple competition events occur consecutively, a game record input device that does not place an extra burden on the record input person and the score progress record are described in more detail It is an object to provide a game record input device that can be used.
[0009]
[Means for Solving the Problems]
  In order to solve the above-described problems, the present invention provides basic information input means for inputting and recording basic information necessary for game recording prior to the start of the game, and various competition events that occur during the game by displaying a game recording screen. A game record input device comprising event recording means for inputting as a record, and information storage means for storing the basic information and the game record, wherein the event recording means simulates a field at the time of score progress input. A field map type input interface that divides the panel into a predetermined number of sections, and a button representing each section is arranged on the panel; a function for displaying a score progress input screen including a player selection button for identifying a player; Based on the selection instruction of the player selection button, the players related to the score progress are recorded, and based on the button selection instruction on the panel, the score is obtained. The location of the event occurrence during the course, a function of recording notation corresponding to the set attacking directionIn addition, when there is an instruction about another competition event during one competition event recording process, a function for saving the competition event being recorded to the pending event list and interrupting the recording process, and the interruption A function to delete the form for the competition event that has been made from the screen and a function to create an event button that iconizes the interrupted competition event recording process and display it on the game recording screenThis makes it possible to easily describe the detailed position of the chute and path.At the same time, it is possible to reduce the burden on the record input person by allowing the record input person to move to the processing of the event that occurred later without ending the event being processed.
[0010]
  As a preferred embodiment of the present invention, buttons representing corner kicks are provided at the four corners of the field map type input interface, and the positions of the corner kicks corresponding to the buttons are recorded based on selection instructions of the buttons. By executing the process, it may be possible to easily describe which corner kick when the score has elapsed.
[0011]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a block diagram showing a configuration of a game record input device according to an embodiment of the present invention. In FIG. 1, a soccer game record input device 10 includes an information storage means 11 and a computer main body 12. The information storage means 11 realized by a hard disk or the like includes a format file 20 for storing a plurality of types of display and print formats for recording soccer game content, and a game information file 21 for storing conditions for recording the game. A basic information file 22 for storing basic game information other than the game content related to the player name, position, and soccer game, an event record file 23 for recording a competition event that occurs during a soccer game, A logo mark file 31 for storing a logo mark and the like is provided.
[0012]
Further, the computer main body 12 is inputted with basic information and a game record input unit 24, an information read / write processing unit 25 for reading and writing a floppy disk 50 and the like, and a basic user interface (hereinafter referred to as GUI). Basic information input means 26 that accepts, event recording means 27 that similarly accepts input of competition events that occur during a game by GUI, a totaling calculation processing unit 29 that performs a tabulation process on the input game records, a game record or a game member table The print control processing unit 28 outputs to the printer 60 in accordance with the selected format, and the communication processing unit 30 exchanges data with the host computer. And the display part 40 which displays the basic information and game record of a soccer game, and the printer 60 which prints out a game record and a member table | surface printing are provided.
[0013]
The basic information file 22 stores basic information necessary for making a competition record such as the name of the host organization of the soccer game, the registered player name of each team, the officer name, the number of each player, and the position of the player. The
[0014]
The game information file 21 stores conditions for recording a soccer game. Conditions for game recording by the hosting organization or the competition, for example, the game time, presence / absence of extra game, 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 game When the flag information and the like are different, the recording conditions for each sponsoring organization or each tournament are stored.
[0015]
The format file 20 stores various display formats for recording the basic information of the soccer game and the content of the game, and a print format for printing out the game record or the member table.
[0016]
The event record file 23 contains information on competition events such as shots, direct / indirect free kicks (hereinafter referred to as “FK”), scores, etc., and information on warnings / exits and substitutions (participation times) for each player. Store as a record. These competition events are input from the input unit 24 by the recorder after the game starts.
[0017]
The logo mark file 31 stores the competition logo, the official sponsor of the competition, or the team logo as image data. These are output in the margin when the official record is printed out by the print control processing unit 28.
[0018]
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. 3.
[0019]
(Basic information input) First of all, the writer records the basic information (game name, spine number, position, etc. of the team participating in the tournament) and the game information (match time, whether or not there is an extra game) pre-created and registered in the host computer. (Extended time in some cases, presence / absence of PK battle, etc.) are read via the communication line, floppy disk 50, etc., and stored in the basic information file 22 and the game information file 21 (S301). Necessary logo marks are also read at this time and stored in the logo mark file 31.
[0020]
(Input of participating members, etc.) Next, the person in charge of recording each game of the tournament activates the game recording input device 10 at the game venue to display a main menu screen 400 as shown in FIG. This main menu screen also represents the work flow of the person in charge of recording. That is, prior to the start of the match, the starting team of the battle team and the member copy members are input, a member table is created and printed, and natural environment information and the like are input (S302).
[0021]
(Game content input) After the game starts, the game record creation button 406 is selected from the main menu 400 to input the game content (S303). Details of this game content input processing will be described later.
[0022]
(Post-processing) After the match is over, the match result print key 407 is selected and the match result is printed (S304). At this time, the total calculation processing unit 29 totals the game record data and creates a game record including the total result according to a predetermined official recording format. This game record is printed out as an official record sheet as shown in FIG. 2 via the print control processing unit 28 for distribution to the tournament officials. As long as data is stored in the logo mark file 31 on this official record sheet, a tournament logo, a tournament sponsor, or a team logo can be easily placed. Then, the game record is written on a floppy disk or the like (S305), and one game record is completed. When inputting the game record of the same tournament, step S301 may be omitted next time. Since the processing steps other than step S303 are the same as those of the conventional apparatus (Japanese Patent Laid-Open No. 8-212478), a detailed description thereof is omitted. Below, step S303 and the game content input step will be described in detail.
[0023]
By selecting the game record creation key 406 on the main menu 400, the kick-off team selection screen shown in FIG. 6 is displayed. This is a kick-off team setting window 600 that appears on the base screen 700 for game content input in FIG. Here, the person in charge of recording looks at the situation of the coin toss on the field, and sets the team (the team losing to the toss) that kicks off the game. 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 seen from the recording person (from the main stand side). When the confirmation button 602 is pressed, the kick-off team setting window 600 disappears and the base screen 700 of FIG. 7 is displayed. Clicking the first half start button 701 together with the referee's kick-off signal starts the time display on the clock, and all the buttons of the event button group 1000 except the replacement, warning / exit, and environment buttons that were available for input from the beginning are displayed. The selection can be made, the main menu return button 1010 cannot be selected, and the game content is entered. This state is shown in FIG.
[0024]
Hereinafter, the game content input process after the game is started will be described with a focus on differences from the conventional apparatus. First, a function that can hold an event input will be described. First, the movement of the screen interface will be described, and then one implementation example will be described.
[0025]
FIG. 11 is a foul event recording screen 1100 that appears as a result of clicking the foul button 1005 from the base screen of FIG. 5 in order to input a foul that occurred in the first half 5:28 (6 minutes on recording). Here, the team that committed the foul is usually selected by the team selection button 1101, and then the foul type is selected from the button group 1102. When the confirmation button 1103 is finally clicked, the screen returns to the base screen of FIG. 5, and a warning / exit, which is the next event, may occur before this series of input processing is completed. In such a case, the game record input device 10 can switch to the warning / exit record input by clicking the warning / exit button 1006 from the lower event input button row before pressing the confirmation button 1103. FIG. 12 shows a warning / exit record input screen 1200 displayed at that time. Here, an object column 1201 displayed at the upper left of the screen indicates the presence of an event for which input has not ended (pending event) and an event currently being input.
[0026]
The object that displays the hold event is displayed at the same position even if the object returns to the base screen. FIG. 8 is a screen in a state in which the event has occurred continuously and the screen has returned to the base screen in a state where the four events are held. The hold event display label 1301 displayed in the upper left position is actually a button, and when one of these is clicked, it is possible to return to the hold event input operation displayed on the label. This device can hold up to nine events.
[0027]
A specific implementation example of the event recording means 27 capable of holding such event input, that is, interrupting another event input during the event input will be described below with reference to the flowcharts of FIGS. 9, 10, and 13. . In these flowcharts, a graphical user interface (GUI) can be realized using event-driven software components such as Visual Basic forms (also referred to as forms in the following description). A computer environment is assumed.
[0028]
A form is a software component as described below. In other words, it has display appearance (screen) properties that describe the size and position of I / F components such as buttons and character display boxes placed on it, and is concerned with events input to those I / F components. A software component having an event recognition function for identifying and having a function for calling and executing a corresponding processing routine when each input event occurs. However, the above function does not work when the form is not displayed.
[0029]
In S303, a game record main form F001 that displays the GUI screen 700 and executes various interactive processes is displayed to create a game record. 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 start button is waited (S901). When it is detected that the start button has been pressed, the clock is started (S902), and the screen waits for input (FIG. 5) (S903).
[0030]
Here, when an object on the game record main form F001 is selected and some screen input occurs, the game record main form F001 detects what the selected object (button) is (S904), and the corresponding processing. Call the routine. For example, when the foul button 1005 is clicked, the foul event processing is started. First, the call flag is set as a new event (S905), and the foul recording form F005 is displayed (S907). At this point, the screen switches to the foul recording screen of FIG. 11 instead of the base screen.
[0031]
The initialization process 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 given from 1 are acquired in the order of event occurrence, and stored in a work memory that is a work storage area (S702). If the call flag is a hold event, the record of the event is copied from the hold event list to the work memory (S704). In the case of a new event, the call flag value is 0, and in the case of a hold event, the event identification number (positive integer) of the hold event is set as the call flag value, which is convenient for the processing of S700 and S704. Thereafter, the process waits for input (S706).
[0032]
Here, when an object on the foul recording form F005, that is, one of the buttons in FIG. 11 is selected, the foul recording form F005 detects what the selected object (button) is. (S708), the corresponding processing routine is called.
[0033]
The operation when there is no event interruption will be described first. In the normal case, the selection button 1101 of the team that committed the foul is clicked. The selected team is recorded in the work memory (S711), the team name 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 that case, first, it is checked whether the team name has been selected (S715), the selected foul type is recorded in the work memory (S717), a confirmation display is made (S719), and the process returns to S706. If the team name is not selected in S715, the process immediately returns to S706. The next event that normally occurs is the selection of the confirm button 1103. In this case, first, it is checked whether both the team name and the foul type have been recorded (S721). If it has been recorded, the foul event has been successfully recorded, and the contents of the work memory are moved to the event list (S723). ), The return flag is set to “normal” (S725), and the foul recording form F005 is erased (S727). Then, the game record main form F001 returns to the active state, and the base screen 700 is displayed. Since the foul recording form has been called in step S907 in FIG. 9, the return flag is checked in step S909. 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.
[0034]
Next, an operation when an interrupt of another event occurs during foul event recording will be described. If the received screen input is one of the event button strings at the bottom of the screen in S708, the contents recorded in the work memory in S729 of FIG. 10, that is, the event identification number, event type, occurrence time, Save other information to an area with an empty hold number in the hold event list. The hold event list is a memory buffer that temporarily records hold event information. The hold event list is composed of nine recording areas, and records the contents input until one hold event is saved in one of the areas. . The interrupted event type is stored in the common variable “interrupt event type record”, the return flag is set to “interrupt” (S731), and the foul recording form F005 is deleted (S733). 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 F005 in S907 of FIG. 9 is finished, the return flag is checked in S909. If “interrupt” ends, the process jumps to S980 in FIG. In S980, a button for the held event is created and placed on the game record main form F001. Actually, the game record form is prepared with nine buttons for the hold event from the beginning, but in the initial state, all buttons are hidden and input acceptance is disabled. When a hold event is made, input information can be accepted by setting the occurrence time and event type in the label property of the hold event button equal to the hold number of the hold event from the hold event information held in the hold event list. (In other words, display is ON). At this time, the hold event button row 1301 is displayed including the latest hold event. Next, it jumps to E1, E2,... According to the contents of the interrupt event type record (which is updated in S731) (S982), and thereafter, the interrupt event recording work can be started.
[0035]
Next, one of the hold event buttons was selected from the state of the screen of FIG. 8 (the screen in which four events were held on hold and the screen returned to the base screen because events occurred continuously). The operation in this case will be described. When any of the hold event buttons 1 to 9 is selected in S904, first, the hold button number is recorded in the common variable “hold number save” (S800). Next, “pending event” is set in the call flag (S802). Then, the type of the hold event is specified from the property of the hold button (S804), and the corresponding event recording form is displayed (S806,..., S886). In this way, the recording operation of the held event is resumed. In the case of foul event recording, the process jumps to S700 in FIG. Since the call flag is “pending event”, the data input from the recording area of the holding event list corresponding to the holding number previously saved in S800 to the middle of the holding event is returned to the work area (S704). Resume.
[0036]
In the above description, the relationship between the game record main form F001 and the foul record form F005 is shown. However, it is necessary to prepare an event record form for each button of the event button group 1000. The flowchart of FIG. 10 can be divided into three parts. The first is a part of S700, S702, and S704 that performs initial processing when a form is displayed (when called). The second part is a series of S729, S731, and S733 that perform processing when an interrupt event occurs. The third part is a part for performing processing peculiar to foul recording (the remaining part). Accordingly, each event recording form may have the same first and second portions as the foul recording form F005. Only the portion corresponding to the third portion may be created according to each event record. In addition, as a common variable for communicating between the game record form F001 and each event record form, a call flag, a return flag, an interrupt event type record, and a hold number need to be saved. Good.
[0037]
Next, the score progress recording process of the game record input device 10 will be described. First, the flow of screen operations will be described. FIG. 16 shows a first screen for score progress recording 1600 displayed first in step S917 of FIG. Here, the score events so far are displayed in the score list 1601. The worker selects a scoring event that has not been entered yet or that he / she wishes to re-enter. The cells of progress 1 to progress 7 of the selected scoring event are displayed in reverse video. The operator clicks the progress input button 1602 after confirming that the selection is correct in reverse video.
[0038]
Then, the screen changes to the score progress recording main screen 1400 of FIG. The score progress record main screen 1400 includes I / F objects such as a field map type interface 1401, a set play selection button group 1402, a player selection button group 1403, a play type button group 1404, and a score progress description column 1405. The operator selects a button corresponding to the position where the play was made from the field map type interface 1401, then selects a player's number number button handling the ball from the player selection button group 1403, and plays type button group 1404. Then, the contents of the play are selected, and a score progress description as shown in FIG. 17 is created in the score progress description column 1405. In FIG. 17, “No. 4” player enters “Center-2” with “Dribble” at “Left-3”, issues “Floating Ball Pass”, and “28” at “Right-1”. The player of No. returned “pass” (centering) and expressed that “No. 5” who ran to “center-1” was scored by “shooting with his right foot” to “direct”.
[0039]
As shown in FIG. 18, the play positions described in the score progress are, for example, right-1, right-2, right-3 in the order of the left side, right side, or center viewed from the attack direction, and the opponent goal. , Right-4 and expressed in 12 sections. The person in charge of recording may select the button at the field position as viewed from the person in charge of recording (main stand side) from 1401 as it is. In the field position button input processing, which team's score is related to the progress input is memorized, so it is automatically recognized whether it is “Right-1” or “Left-4”, and a progress description column 1405 is displayed.
[0040]
In the field map type interface 1401 of FIG. 14, a corner kick button is also arranged at the corner kick position. Since corner kick is a kind of resumption of play (set play), it may be placed in the 1402 button group, but it is better to place it in the field map as in the embodiment. This is convenient because it is not necessary to determine whether the right CK or the left CK from the attack direction.
[0041]
An implementation 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 processes corresponding to the call flag. In the case of a new event, after step S602, the form F0021 that handles the first screen 1600 is displayed, and the team name and event number are acquired. In step S608, the position N of the progress entry field is set. It is 1 for a new event and a continuation value for a pending event. If any of the position buttons on the field map type interface 1401 is clicked, in S620, the position display is reversed if necessary according to the team name, and the result is recorded in the cell of the progress column. Then, the entire progress field is displayed again, the cell position in the progress field is updated, and the process again returns to the input waiting state (S610). S620 in FIG. 19 shows only the case of the right-4 button, but there is actually a process for each of the 12 individual buttons. When one of the buttons 1402, 1403, and 1404 is clicked, the display content of the button is recorded in a cell in the progress column. The entire progress field is displayed again (S632), and the process returns to S609. If the confirmation button is clicked, the entire progress field is saved as an official record in another storage area (S640), the return flag is set to "normal" (S642), and the current form is deleted ( S644), the process returns to S919 in FIG.
[0042]
With the conventional device, when scoring progress, you only have to select from the three buttons "Right", "Left" or "Center", so you can describe in detail whether the position is near or far from the goal. There was no. By using the field map type interface 1401, the field position of the 12 sections can be correctly described by changing the direction by the team only by selecting the button at the position as seen by the recording staff.
[0043]
FIG. 20 summarizes the relationship between the forms described so far together with the pending event list.
[0044]
As described above, one example (implementation mode) has been described with respect to a function for holding an event and a function for recording the progress of a score in more detail by a field map type I / F, which are improvements from the conventional apparatus. These forms operate on the computer to implement the event recording means 27. However, the present invention is not necessarily limited to the above implementation. For example, the function of allowing interruption of other event entries during event recording may be implemented in a manner different from that described herein. Although the number of events that can be held is nine in this embodiment, it is not limited to nine.
[0045]
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 it is too fine, it will be a burden on the recorder, so the limit is 20 sections.
【The invention's effect】
[0046]
Since the competition event record is put on hold and the record of the competition event that occurred later can be interrupted, the burden on the record input person is remarkably reduced compared to the conventional device, and there is no need to forget to correct the record. It was. Further, since the field map type I / F is adopted, the score progress can be described in more detail as compared with the conventional apparatus. Moreover, since it is possible to input the image as it is viewed from the field, it is not a burden on the record input person.
[Brief description of the drawings]
FIG. 1 is a block diagram showing the overall configuration 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 a 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 game.
FIG. 6 is a kick-off setting screen.
FIG. 7 is a base screen just before the game 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 a field map type interface.
FIG. 16 is a first screen for score progress input.
FIG. 17 is an example of score progress description.
FIG. 18 is an explanatory diagram of a play position in a field map type interface.
FIG. 19 is a flowchart of a score progress input form.
FIG. 20 is a relationship diagram between forms.
[Explanation of symbols]
10 Game record input device
11 Information storage means
12 Computer body
20 format files
21 Game information file
22 Basic information file
23 Event record file
24 Input section
25 Information read / write processor
26 Basic information input means
27 Event recording means
28 Print control processor
29 Total calculation processing section
30 Communication processing unit
31 Logo mark file
40 Graphic monitor
50 FD etc.
60 Printer
600 kick-off setting window
700 game record base screen
1100 foul event recording screen
1600 score progress record screen

Claims (3)

Prior to the start of the game, basic information input means for inputting and recording basic information necessary for the game record, event recording means for displaying a game record screen and inputting various competition events occurring during the game as a game record, A game record input device comprising basic information and information storage means for storing the game record,
The event recording means includes
A score provided with a field map type input interface in which a panel simulating a field is divided into a predetermined number of sections and buttons representing each section are arranged on the panel and a player selection button for specifying a player when entering score progress Based on the function of displaying the progress input screen and the selection instruction of the player selection button, the player related to the score progress is recorded, and the position of the event occurrence during the scoring progress based on the button selection instruction on the panel and a function of recording notation corresponding to the set attacking direction Rutotomoni,
If there is an instruction for another competition event during one competition event recording process, the competition event during the recording process is saved to the pending event list and the recording process is interrupted, and the suspended competition A game record input device comprising a function for erasing an event form from the screen and a function for creating an event button that is an icon of the interrupted game event record process and displaying the event button on the game record screen .   2. The game record input device according to claim 1, wherein a button representing a corner kick is provided at four corners of the field map type input interface, and the position of the corner kick corresponding to the button is determined based on a selection instruction of the button. A game record input device for performing a process of recording. 3. The game record input device according to claim 1, wherein the event recording unit obtains the time of occurrence of the competition event and interrupts the competition event when there is an instruction for each competition event. In this case, the game record input device is configured to execute a process of displaying an occurrence time of a corresponding competition event on the event button.

Images