JP5427204B2 - Wireless communication game system, game device, game program, and game processing method - Google Patents

Description

The present invention relates to a game system , a game device, a game program, and a game processing method using wireless communication.

  An example of a conventional wireless communication game system is disclosed in, for example, Patent Document 1 (International Classification: A63F13 / 00, H04L12 / 28) published on May 16, 2000.

JP 2000-135380 A

The main object of the invention this is a novel, wireless communication game system, a game device, and to provide a game program and a game processing method.

One embodiment of the present invention is a wireless communication game system for playing a communication game using a plurality of portable game devices capable of short-range wireless communication with each other. The wireless communication game system includes a game device having communication means and another game device. The other game device includes first identification information for identifying the certain game device from the unspecified certain game device, and a game for identifying a communication game that is currently executable on the certain game device. A second receiving means for receiving identification information using communication means; and the certain game capable of executing the communication game with the other game device based on the information received by the second receiving means. For each of the extracted game devices, the second display control means outputs a display for identifying each game device on the screen, and the second display control means according to the user input by the input means. second selection means for selecting a desired game device from the display that identifies each game device to be displayed, and pairs game apparatus selected by said second selecting means Te comprises connection request means for performing a connection request for performing the communication game with the the game device.

According to the present invention, a novel wireless communication game system, game device, game program, and game processing method can be provided.

  The above object, other objects, features and advantages of the present invention will become more apparent from the following detailed description of embodiments with reference to the drawings.

FIG. 1 is a block diagram showing an example of a portable game device used in a wireless transmission game system according to an embodiment of the present invention. FIG. 2 is an illustrative view for explaining an outline of a game system using the portable game apparatus of FIG. 1 embodiment. FIG. 3 is an illustrative view showing an example of a display screen in a case where an all display flag for displaying information of all the parent devices around the own device is turned on in the embodiment of FIG. FIG. 4 shows an example of a display screen that displays only the parent device that exists around the own device and is capable of a communication game with the own device when the all display flag is not turned on in the embodiment of FIG. FIG. FIG. 5 is an illustrative view showing an example of a display screen that displays only a parent device that exists around the own device and can play a game in the OC (one cartridge) mode in FIG. 2 embodiment. FIG. 6 is an illustrative view showing a display screen example of a base unit list in a certain situation in FIG. 2 embodiment. FIG. 7 is an illustrative view showing a display screen example of a parent device list when the portable game device with the user name “Shiro” enters the communication range in the situation of FIG. 6 in the embodiment of FIG. FIG. 8 is an illustrative view showing a display screen example of a parent device list when the portable game device with the user name “Ichiro” goes out of the communication range in the situation of FIG. 7 in the embodiment of FIG. FIG. 9 is an illustrative view showing an example of a display screen of a slave unit list in a state where the own device is the master unit and waiting for connection (entry) of the slave unit in the embodiment of FIG. FIG. 10 is an illustrative view showing one example of a data cycle in FIG. 2 embodiment. FIG. 11 is an illustrative view showing one example of a base unit packet sent to the base unit slot in the embodiment of FIG. FIG. 12 is an illustrative view showing the U slot in FIG. 11 in detail. FIG. 13 is an illustrative view showing one example of a handset packet sent to the handset slot in the embodiment of FIG. FIG. 14 is an illustrative view showing a specific example of communication data in a certain situation of FIG. 1 embodiment. FIG. 15 is an illustrative view showing one example of a memory map of a cartridge not corresponding to the OC mode. FIG. 16 is an illustrative view showing one example of a memory map of the cartridge corresponding to the OC mode. FIG. 17 is an illustrative view showing one example of a memory map of an EEPROM included in the wireless communication unit of FIG. 1 embodiment. FIG. 18 is an illustrative view showing one example of a memory map of an internal RAM of a portable game machine constituting the portable game device in FIG. 1 embodiment. FIG. 19 is a flowchart showing a part of the main flow showing the operation of the portable game machine of FIG. 1 embodiment. FIG. 20 is a flowchart showing the continuation of FIG. FIG. 21 is a flowchart showing the continuation of FIG. FIG. 22 is a flowchart showing the continuation of FIG. FIG. 23 is a flowchart showing the continuation of FIG. FIG. 24 is a flowchart showing the continuation of FIG. FIG. 25 is a flowchart showing the continuation of FIG. FIG. 26 is a flowchart showing the continuation of FIG. FIG. 27 is a flowchart showing a part of the operation of the base unit connection processing. FIG. 28 is a flowchart showing the continuation of FIG. FIG. 29 is a flowchart showing the operation of transmission / reception processing of the master unit. FIG. 30 is a flowchart showing a part of the operation of the slave unit connection process. FIG. 31 is a flowchart showing the continuation of FIG. FIG. 32 is a flowchart showing the operation of transmission / reception processing of the slave unit. FIG. 33 is a flowchart showing the operation of the slave unit return processing. FIG. 34 is a flowchart showing a main part of the embodiment in which the selection of whether the own device is a parent device or a child device is first performed.

  As an example, the wireless communication game system to which the present invention is applied uses a portable game apparatus 10 as shown in FIG. In this embodiment, the portable game apparatus 10 includes a portable game machine 12 such as Game Boy Advance (trade name), a wireless communication unit 14 and a cartridge connector connected to the communication connector 46 of the portable game machine 12. 40 includes a cartridge 16 connected. That is, in this embodiment, the portable game device 10 is constituted by the portable game machine 12, the wireless communication unit 14, and the cartridge 16.

  A portable game machine 12 shown in FIG. 1 includes a processor 20, which includes a CPU core 22, a boot ROM 24, an LCD controller 26, a WRAM (working RAM: hereinafter the same) 28, a VRAM 30 and a peripheral circuit 32. including. However, the peripheral circuit 32 includes a sound (sound) circuit, a DMA (Direct Memory Access) circuit, a timer circuit, an input / output interface (IO), and the like. The LCD 18 provided on the front surface of the portable game machine 12 is provided with a display signal from the processor 20, in this embodiment, an RGB signal, so that the game image is displayed in color on the LCD 18. Then, an audio signal is given from the processor 20 to the sound circuit 34, and sounds such as game music and sound effects are output from the speaker 36 by the audio signal. A cross key, a start key, a select key, an A button, and a B button provided on the front surface of the portable game machine 12 with the LCD 18 interposed therebetween are collectively shown as an operation switch 38, and an operation signal from the operation switch 38 is sent to the processor 20. Is input. Therefore, the processor 20 executes processing in accordance with the user instruction given through the operation switch 38.

  The portable game machine 16 has a cartridge connector 40, and the cartridge 16 is connected or inserted into the cartridge connector 40. The cartridge 16 includes a ROM 42 and a backup RAM 44, and a game program for a game to be executed on the portable game machine 12 is set in advance in the ROM 42 together with the game name. The backup RAM 44 stores mid-game data and game result data.

  The portable game machine 16 is further provided with a communication connector 46, and a connector 48 of the wireless communication unit 14 is connected to the communication connector 46. The portable game machine 12 used in the embodiment is, for example, Game Boy Advance (trade name). In this case, the above-described cartridge connector 40 is provided on the back side of the upper surface when the LCD 18 is the front surface (front surface). The communication connector 46 is a 6-pin connector provided on the front side of the upper surface.

  The wireless communication unit 14 includes a baseband IC 50, and the baseband IC 50 includes a ROM 52. The ROM 52 includes, for example, an OCD (One-Cartridge Download) program and other programs, and the baseband IC 50 operates according to these programs. The one-cartridge download program is an OC mode (one-cartridge mode: a mode in which a game cartridge is attached only to the master unit, and the slave unit operates upon receiving a slave unit program download from the master unit cartridge). The program for downloading the program to the handset.

  The wireless communication unit 14 is further provided with an EEPROM 54, and a user name is uniquely set in the EEPROM 54, for example. The base band IC 50 transmits data including the user name to an RF (Radio Frequency) -IC 56, and the RF-IC 56 modulates the data and transmits a radio wave from the antenna 58. However, the radio field intensity is very weak and is set to such a small value that it is not subject to regulations of the Radio Law. The wireless communication unit 14 is provided with a power supply circuit 60. The power supply circuit 60 is typically a battery and supplies direct current power to each component of the wireless communication unit 14.

  In the wireless communication unit 14, the radio wave transmitted from another portable game device is received by the antenna 58 and demodulated by the RF-IC 56, and the demodulated signal is input to the baseband IC 50. Therefore, the baseband IC 50 decodes the demodulated signal, restores the data, and transfers the data to the portable game machine 12 or the WRAM 28 via the connectors 48 and 46.

  In the wireless communication game system of the embodiment according to the present invention, a plurality of portable game apparatuses 10 as shown in FIG. 1 are used. A dotted line 64 in FIG. 2 indicates a communicable range of the own portable game device 62. Then, the portable game device 62 may be able to enter a portable game device that exists in the communicable range 64. The communicable range 64 is a range in which data communication between the parent device and the child device can be performed by the above-described weak radio wave, and any of the plurality of portable game devices existing in the communicable range 64 is Optionally, it can be a parent machine or a child machine. In the illustrated example, within the range 64, there are four master units, three slave units, and one own unit 62.

  When the own device 62 participates in the game, it is necessary to become a parent device or a child device. When your machine becomes a child machine, you need to find a parent machine that you can join. When searching for a parent machine, it is necessary to search for a different parent machine depending on whether or not the own machine has a cartridge.

  First, in the case where the own device 62 is a portable game device equipped with the cartridge 16 shown in FIG. 1, an all display flag (described later) indicating that all the parent devices around the own device 62 are displayed is “ When “1” is set, a parent machine list 18A as shown in FIG. 3 is displayed on the LCD 18 of the portable game machine 12 shown in FIG. In the parent device list 18A of FIG. 3, all parent devices existing in the communicable range 64 (FIG. 2), that is, three parent users whose user names are “Taro”, “Ichiro”, and “Jiro”, respectively. The machine is displayed. Therefore, when the user of his / her own device wants to operate or function his / her own device as a child device, he / she designates the parent device to which he / she wants to connect by moving the cursor with the cross key included in the operation key 38 (FIG. 1). The selection can be made by pressing the A button included in the operation key 38 later.

  However, when the user wants to use his / her own device as the parent device, the user may press the B button included in the operation key 38.

  In FIG. 2, although there are four parent devices in the range 64, only three parent devices are displayed in the parent device list 18A of FIG. 3 for the following reason. The base unit with the user name “Saburo” has the entry slot ESlot set to “ffh”. This entry slot ESlot is a flag indicating whether or not a new child device is desired. When this entry slot ESlot is set to “ffh”, the parent device refuses new participation of the child device. Therefore, such a master unit is not displayed. Since the master unit with the user name “Saburo” has reached the maximum number of slave units that can be entered, it does not want a new slave unit.

  Further, in the parent device list 18A of FIG. 3, a circle (O) is added to the parent device of the user name “Jiro”. This circle (O) indicates that the game in the OC mode can be played.

  Further, when the all display flag is OFF, the parent device list 18A shown in FIG. In this case, only the parent device that can communicate with its own game cartridge, for example, Mario Kart-1, (in this example, the parent device whose user name is “Taro”) is displayed. This is because a Mario Kart-2 cartridge is installed in the parent device of the user name “Taro”, and Mario Kart-1 and Mario Kart-2 can communicate with each other. . If there is a parent device in which the Mario Kart-1 cartridge is mounted in the communicable range 64, the parent device is naturally displayed.

  In the above example, the Mario Kart-1 cartridge is attached to the own device (slave device). However, if the player wants to play a game in the OC mode without attaching the cartridge to the own device, the LCD 18 displays, for example, FIG. 5 is displayed. In the parent machine list 18A of FIG. 5, only the parent machine that can support the OC mode, in this example, the parent machine with the user name “Jiro” is displayed (“F-ZERO” is a game that supports the OC mode). However, in this case, since the cartridge is not mounted in the own machine, the own machine cannot become the parent machine. Therefore, the message shown in FIG. 3 or FIG. 4 that “Please press the B button when you want to become the parent machine” is not displayed.

  Next, referring to FIG. 6 to FIG. 8, the master unit with the user name “Shiro” enters the communicable range 64 shown in FIG. 2, and then the master unit with the user name “Ichiro” goes out of the range 64. A change in the display of the own device 62 in the case of failure will be described. When the parent device of the user name “Shiro” is out of the range, as shown in FIG. 6, the same parent device list 18 </ b> A as FIG. 3 is displayed on the LCD 18 of the own device 62.

  Thereafter, when the parent device having the user name “Shiro” enters the range, the parent device list 18A shown in FIG. 7 is displayed. However, it is assumed that all display flags of the own device 62 are turned on. That is, the parent device having the user name “Shiro” is displayed in addition to the parent devices having the user names “Taro”, “Ichiro”, and “Jiro”, respectively.

  Then, when the parent device having the user name “Ichiro” moves out of the range 64, the parent device list 18A in FIG. 8 is displayed. The parent device with the user name “Ichiro” is not displayed in this parent device list.

  Further, when the own device is a parent device and is waiting for the participation of a new child device, the child device list 18B shown in FIG. Looking at this handset list 18B, it can be seen that handset devices whose user names are “Goro”, “Rokuro”, and “Nanaro” are currently connected to their own devices. Here, since the present embodiment is a wireless communication game system in which a game is progressed while wireless communication between the parent device and the child device is performed using weak radio waves, the term “connection” should not be used originally. However, the term “wired communication” is used as a term representing the link state in which communication is possible between the portable game device serving as the parent device and the portable game device serving as the child device, and expressed as “connection” for convenience. And

  Next, a data packet format when wireless communication is performed between a parent device and a child device in a connected state will be described with reference to FIGS. As shown in FIG. 10, one data cycle is 2 milliseconds, and the data cycle includes one master unit slot and a plurality of (four in this embodiment) slave unit slots. In the parent device slot, the parent device packet specifically shown in FIG. 11 is broadcast (broadcast), and in each of the four child device slots, the child device packet specifically shown in FIG. 13 is transmitted to the parent device. Is called.

  As shown in FIG. 11, the base unit packet has a field sync for storing synchronization data at its head, and stores the number (identification code) PID of the base unit following the synchronization data field sync. Field PID for Following the field PID, a user name field UserName and a game name field GameName are formed. In the user name field UserName, the user name read from the EEPROM 54 (FIG. 1), such as “Taro” and “Ichiro” in the above example, is registered, and in the game name field GameName, the game name, the above example In other words, Mario Kart-1, Mario Kart-2, F-Zero, Golf,... Are registered. However, if the cartridge 16 (FIG. 1) is mounted, the game name (68 in FIG. 16) read from the ROM 42 (FIG. 1) can be automatically registered in the game name field GameName.

  The parent device packet further includes a flag OC, and this flag OC is a flag indicating whether or not the one-cartridge (OC) mode described above can be supported. Specifically, when the flag OC is reset, that is, when OC = 0, the game machine of the parent machine at that time is not compatible with the OC mode, or can be compatible with the OC mode, but at present, Indicates that you are playing in normal mode. When the flag OC is set, that is, when OC = 1, it indicates that the OC mode can be supported and that the OC mode is currently being played. Therefore, a user who does not have a cartridge needs to search for a parent machine whose flag OC is “1”.

  Subsequent to the flag OC, the base unit packet includes fields ESlot, USlot, and Payload sequentially. The E slot field ESlot stores the number of the slave unit slot that can be entered (participated). That is, the slot number that can be used by the newly participating slave unit is stored. In the U slot field USlot, the usage status of the slave unit slot is stored. Specifically, it is shown in FIG. That is, U slot field USlot includes four areas, and each of the four areas corresponds to slave unit slot 0, slave unit slot 1, slave unit slot 2, and slave unit slot 3. In each area, the number (identification code) CID of the slave unit to which the corresponding slave unit slot is assigned is stored. When the handset number CID corresponding to the corresponding area is registered, it is understood that the handset slot is being used.

  The payload field Payload is a field for transmitting game data necessary for the game process, and is a field for storing game data transmitted from the parent device to the child device.

  FIG. 13 shows a handset packet sent from the handset to the handset slot assigned to the handset. That is, the child device packet includes a head field CID for storing or registering the child device number CID and a payload field Payload subsequent thereto. The payload field Payload is a field for storing game data transmitted from the child device to the parent device.

  FIG. 14 shows a specific example. In the example of FIG. 14, it is understood that “58” is stored in the parent device number field PID, and therefore, the parent device number PID is “58”. The user name of the parent device is “Taro”, the game name is Mario Kart, the flag OC is “0”, “2” is registered in the E slot field ESlot, and the U slot field Uslot , A slave unit having a slave unit number (CID) of “16” is connected to the slave unit slot 0, and a slave unit having “130” is connected to the slave unit slot 1, The slave slots 2 and 3 are both “0h”, so that it is understood that they are empty slots.

  When a new slave unit tries to connect (Entry) to the master unit in such a state, referring to the U slot field USlot of the master unit, “16” and “130” are used as the slave unit number CID. Therefore, the other handset number CID is determined by generating a random number, for example. As an example, assume that “86” is determined as the CID of the child device. Therefore, the slave unit transmits CID = 86 to the slave unit slot (slave unit slot 2) designated by ESlot.

  Then, by receiving “86” in the slave unit slot 2, the master unit knows that the slave unit having “86” as the slave unit number CID wants to enter. Then, whether or not to permit the entry is determined. When the entry is permitted, the master unit sets “86” in the area corresponding to the slave unit slot 2 of the Uslot. The parent device packet shown is broadcast, and it is notified that the participation of the child device having the child device number CID of “86” is newly permitted. At the same time, the newly joined child device confirms that CID = 86 exists as its own child device number in the area corresponding to the slave device slot 2 of Uslot, and can determine that the entry has succeeded.

  FIG. 15 shows a memory map of a cartridge that does not support the OC mode, and FIG. 16 shows a memory map of a cartridge that can support the OC mode.

  In the embodiment of FIG. 15, the ROM 42 (FIG. 1) included in the cartridge 16 includes a game program area 62 and a game name area 64. In the game program area 62, a common program 66, a parent device program 68, and a child device program 70 are stored in advance. The common program 66 is a program used regardless of whether the own device is a parent device or a child device. That is, when the own device is a parent device, a common program and a later-described parent device program are executed, and when the own device is a child device, a common program and a later-described child device program are executed. The parent device program 68 is a program that operates only when the own device functions as the parent device, and includes variables M and N and a flag OC set to “0” (that is, turned off). However, the variable M indicates the maximum number of slave units that can be simultaneously connected to the master unit, and the variable N indicates the maximum number of slots that can be used by one slave unit. Note that both these variables M and N vary from game to game. The child device program 70 is a program that operates only when the own device functions as a child device, and includes the variable N described above. In the game name area 64, the names of the game programs, for example, Mario Kart-1, Golf,.

  Also in the embodiment of FIG. 16, the ROM 44 of the cartridge 16 includes a game program area 62 and a game name area 64. In the game program area 62, the same common program 66, parent device program 68, and child device program 70 as those in FIG. 15 are set, and an OC mode game program 72 is set to correspond to the OC mode. The OC mode game program 72 includes a parent device program 74 and a transfer child device program 76. The base unit program 74 is the same as the previous base unit program 68 except that the flag OC is set to “1”. The transfer handset program 76 is a program for transferring to a handset that plays a game in the OC mode, and includes a variable N. A child device that enters in the OC mode can participate in the game by receiving the transfer child device program 76 transferred (downloaded) from the parent device.

  FIG. 17 shows a memory map of the EEPROM 54 of the wireless communication unit 14 shown in FIG. 1. As shown in FIG. 17, the EEPROM 54 includes a user name area 78, and the user name area 78 includes a user name. For example, “Taro”, “Ichiro”, etc. are registered.

  Referring to the memory map shown in FIG. 18, the WRAM 28 (FIG. 1) of the game machine 12 includes a parent machine list area 80, a parent machine list clear timer 82, a child machine list area 84, variable areas 86 and 88, and a game variable area 90. , A transmission buffer area 92 and a reception buffer area 94.

  The base unit list area 80 is data for displaying the base unit list 18A described above with reference to FIG. 3, for example, base unit number (PID), user name (UserName), game name (GameName), flags OC, E This is an area for temporarily storing and holding the slot field ESlot.

  The base unit list clear timer 82 is a timer for measuring the time until the data in the base unit list area 80 is cleared. As will be described later, when the timer 82 expires, the base unit list area 80 Is automatically cleared.

  The handset list area 84 temporarily stores data for displaying the handset list 18B described above with reference to FIG. 9, such as handset number (CID), user name (UserName), and game name (GameName). It is an area for holding.

  The WRAM 28 further stores a parent machine variable area 86 for storing variables used when the own machine operates (behaves) as a parent machine, and variables used when the own machine operates (behaves) as a child machine. It includes a handset variable area 88 for storing.

  In the base unit variable area 86, for example, data for each field PID, USlot, and ESlot shown in FIG. 11, a slave unit number (CID) of a slave unit to be connected, and variables n and m are set. Here, the variable n indicates the number of slots actually allocated to one slave unit, and the maximum number is given by the variable N described above. The variable m indicates the number of slave units that are actually connected to one master unit at the same time, and the maximum number is given by the variable M described above.

  In the cordless handset variable area 88, for example, data for the field CID shown in FIG. 12 is set, a variable indicating the connection result, a variable indicating the return result, a base number (PID) of the parent device of the connection destination, The acquired slot number (s), synchronization timer, variable n, and all display flags are set.

  The game variable area 90 is an area for storing game variables during game execution, for example, variables indicating the number of cleared stages and acquired items. The transmission buffer 92 and the reception buffer 94 are areas for temporarily storing transmission data and reception data, respectively.

  Two or more portable game apparatuses 10 each having such a configuration construct a game system. The operation of each portable game apparatus 10 in the game system will be described below with reference to a flowchart.

  Prior to the detailed description, when a cartridge that is not compatible with the OC mode is mounted on the own device and when the own device becomes the parent device, Step S29 (FIG. 21) to Step S69 (FIG. 23) described later. Perform a series of steps. Further, when a cartridge that is not compatible with the OC mode is mounted on the own device and when the own device is a slave device, a series of steps from Step S83 to Step S109 (FIG. 24) described later is executed. Become.

  Further, when a game is played in the normal mode (not the OC mode) although the cartridge capable of supporting the OC mode is attached to the own device, when the own device is set as the parent device, step S29 (FIG. 21). -When a series of steps of Step S69 (FIG. 23) is executed and the own machine is used as a slave machine, a series of steps of Step S83 to Step S109 (FIG. 24) is executed in the same manner as above.

  Further, when a cartridge capable of supporting the OC mode is mounted on the own device and the game is played in the OC mode, the own device can only function as the parent device. In this case, steps S75 and S77 (see FIG. 19), a series of steps from Step S29 shown in FIG. 21 to Step S69 shown in FIG.

  If the cartridge is not attached to the own device, the own device can only be a slave device in the OC mode. Therefore, in this case, a series of steps S111 (FIG. 19) to step S147 (FIG. 26) is performed. The steps will be executed.

  FIG. 19 shows the operation of the portable game machine 12. When the power (not shown) of the portable game machine 12 is turned on, the operation of FIG. 19 is started, and the operation set in the boot ROM 24 is executed first. That is, in the first step S1, the processor 20 detects whether or not the cartridge 16 is mounted based on a signal from the connector 40 (FIG. 1), for example. When it is determined in step S3 that there is a cartridge, the program shifts to the ROM 42 program of the cartridge 16, and in step S5, it is determined whether or not the cartridge is compatible with the OC mode. In this step S5, it is determined whether the cartridge of FIG. 15 (cartridge that is not compatible with the OC mode) or the cartridge of FIG. 16 (cartridge that is compatible with the OC mode) is mounted.

  When “NO” is determined in step S5, that is, when a cartridge is mounted in the own apparatus but the cartridge is not an OC mode compatible cartridge, the process proceeds to step S7 in FIG. 20, and the parent device list area shown in FIG. 18 is cleared, and the parent device list clear timer 82 shown in FIG. 18 is reset, and all display flags set in the child device variable area 88 of FIG. 18 are turned on (“1” is set). The parent device list clear timer 82 automatically starts counting after resetting.

  Thereafter, in step S9, an attempt is made to receive the parent device packet as shown in FIG. In step S11, it is determined whether the base unit packet has been successfully received. When “YES” is determined in step S11, in subsequent step S13, it is determined whether or not the parent device that broadcasts the parent device packet is a parent device that does not exist in the parent device list. Specifically, in step S13, the parent device PID and the user name in the received parent device packet data (data temporarily stored in the reception buffer 94 of the WRAM 28 shown in FIG. 18) It is determined whether the parent device is registered in the list 80 (FIG. 18). If “YES” is determined in this step S13, that is, if it is a new parent device, in the subsequent step S15, the processor 20 adds the parent device ID (included in the parent device packet) to the parent device list 80. PID), user name (UserName), game name (GameName), OC flag (OC), and entry slot (ESlot) are newly registered.

  When “NO” is determined in the previous step S11, or when the registration in step S15 is completed, in the next step S17, the value of the parent device list clear timer 82 (FIG. 18) reset in the previous step S7 is set. Judge whether it is more than 2 seconds. If “YES”, the parent device list 80 is cleared in step S19, and the parent device list clear timer 82 is reset. Here, the reason for resetting the parent device list clear timer 82 is as follows. That is, as described above with reference to FIG. 8, when a parent device (“Ichiro” in FIG. 8) is out of the communicable range, the parent device must be deleted from the parent device list 80. Therefore, by periodically clearing the parent device list 80 (every 2 seconds in this embodiment) and registering in the list of parent devices in the communicable range from the beginning, the parent device outside the communicable range Is not left in the parent machine list. When “NO” is determined in step S17 or after step S19, in next step S21, the processor 20 determines whether or not the above-described all display flag is on (“1”). In the embodiment, this all display flag is set to “1” or ON as a default. When the all display flag is on, in step S23, among the parent devices registered in the parent device list, all parent devices whose entry slot ESlot is not “ffh”, that is, all parent devices that allow entry of a new child device. Information (specifically, user name UserName and game name GameName) is displayed as shown in FIG. When the all display flag is off (“0”), in step S25, among the parent devices registered in the parent device list, the entry slot ESlot is not “ffh” and communication is possible (that is, the cartridge of the parent device). The parent machine information (user name UserName and game name GameName) is displayed as shown in FIG. 4.

  Thereafter, the process proceeds to step S27 in FIG. 21, and the processor 20 refers to the signal from the operation key 38 and determines whether or not the B button (not shown) is pressed. The fact that the B button has been pressed means that the user of the portable game device has decided to behave as the parent device. In this case, the child device is within the range of the variables M and N. In order to recruit, the base unit connection process of step S29 is executed. However, the variable N indicating the maximum number of slots given to one slave unit and the variable M indicating the maximum number of slave units that can participate can be changed by the game. For example, in order to increase the maximum number of participating slave units M, the maximum number of slots N may be decreased, and if importance is attached to the data rate, the maximum number of slots N may be increased and the maximum number of participating slave units M may be decreased.

  Here, with reference to FIG. 27 and FIG. 28, the parent device connection processing in step S29 for recruiting the child devices will be described in detail. In the first step S1001 in FIG. 27, the processor 20 clears the slave unit list area 84 shown in FIG. 18 and displays the initial screen. Step S1001 is an initial setting step. In addition to the above processing, in addition to setting the maximum number (N) of sub time slots allocated to one slave unit, the maximum number of slave units that allow entry is set. Set (M). However, these maximum numbers N and M can be determined according to the game program to be executed. In this way, if the maximum number N of sub time slots allocated to one slave unit and the maximum number M of slave units that can participate simultaneously are determined according to the game, the number of sub time slots is fixed. In this case, either the number assigned to one slave unit is reduced to increase the number of slave units that can participate, or the number assigned to one slave unit is increased to increase the data rate. Can be determined according to the content of the game. For example, in the case of a game where it is more interesting for many players to participate, the number of slots N is reduced and the number of participating slave units M is increased, and in the case of a game with a large amount of communication, the number of slots N is increased and the number of participating slave units M is increased. Should be reduced.

  In subsequent step S1003, the processor 20 writes a pseudo-random value in the area PID for setting the parent machine PID in the parent machine variable area 86 (FIG. 18). In the next step S1005, a variable m indicating the number of child devices actually connected to the parent device (own device) in the area 86 is set to zero (0), and in the subsequent step S1007, the connection target child device. “Null” is set in the area of the connection target CID indicating the number of “0”, and zero (0) is written in a variable n indicating the number of slots actually assigned to the child machine currently connected in the area 86. . Note that the connection target CID is the CID of the child device that is currently being connected. When a plurality of slots are assigned to a single child device in the entry process, a slot is continuously assigned to a certain child device a plurality of times. For this reason, when slot assignment to a certain child device is started, an entry request from a child device having a CID other than the connection target CID is ignored. In the next step S1009, one of the free slot numbers is assigned to the entry slot area ESlot in the area 86.

  Thereafter, in step S1011, the processor 20 verifies the signal from the operation key 38 (FIG. 1) and determines whether or not the A button (not shown) is pressed. If “YES” in the step S1011, it means that the user of the own device (parent device) has rejected the entry of the child device (see FIG. 9), so in the subsequent step S1013, the processor 20 displays the child device in FIG. From the machine list area 84, the data, USlot and CID of the selected slave machine are deleted. Thereafter, in step S1015, a new slave unit list 18B is displayed as shown in FIG.

  When “NO” is determined in step S 1011, that is, when the user of the parent device does not press the A button or after executing step S 1015, in step S 1017, the processor 20 uses the operation key 38. Based on the signal, it is determined whether a start key (not shown) has been operated. If “YES”, return directly. However, if “NO”, in the subsequent step S1021, the transmission / reception process of the master unit shown in detail in FIG. 29 is executed.

  The transmission / reception process of the master unit shown in step S1019 of FIG. 27 is shown in detail in FIG. In step S2001 in FIG. 29, the processor 20 determines whether there is untransmitted data in the transmission buffer 92 (FIG. 18). If “YES”, in the next step S2003, necessary data such as PID, user name, game name, OC flag, E slot, U slot and payload which is the above-mentioned untransmitted data are transmitted in the base unit slot of FIG. To do. Then, after receiving the slave unit packet in the next step S2005, the process returns.

  If “NO” is determined in the previous step S2001, in the next step S2007, the processor 20 determines whether data transmission has not been performed for the past 64 milliseconds. Note that the time of “64 milliseconds” is an example of a numerical value that can eliminate the timer shift, and is not limited to this numerical value.

  If “YES” is determined in step S2007, each data excluding the payload, for example, PID, user name, game name, OC flag, E slot, and U slot are transmitted using the parent machine slot in step S2009. This step S2009 is a step necessary for enabling entry from the slave unit, and even if there is no payload (data to be transmitted), data (PID, user name, game name, OC flag required for entry processing) , E slot, and U slot) are periodically transmitted, the slave unit can always perform entry processing. In step S2009, payload data is not transmitted. Then, after the end of step S2009 or when “NO” is determined in step S2007, the process returns through the previous step S2005.

  Returning to FIG. 27, in step S1021 following step S1019, the processor 20 determines whether or not the slave unit number CID has been received in the slot designated by the field ESlot of the master unit packet shown in FIG. Determine whether it has made an entry request using the entry slot). If “NO” in this step S1021, the process returns to the previous step S1011. If “YES”, in the next step S1023, it is determined whether or not the connection target child device CID in the child device variable area 86 of FIG. That is, it is determined whether there is another child device that is currently processing the entry). If “YES”, that is, if the connection target child device number (CID) is not registered, in step S1025, the child device CID received in step S1019 is set as the connection target child device number (CID) in the area 86 of FIG. Registered in the connection target child device CID.

  When “NO” in the previous step S1023 or when step S1025 is completed, in step S1027, the processor 20 determines whether or not the received CID is the same as the connection target CID (that is, the received CID is the current entry process). It is determined whether or not it is the CID of the slave unit in the middle). If “NO”, the process returns to the previous step S1011. If “YES”, in the next step S1029, the CID is stored in the portion indicating the entry slot of the U slot area USlot in the area 86 of FIG. In step S1031, the number n of actual connection slots is incremented (+1). In step S1033, whether n = N, that is, the maximum number of slots N given to one slave unit by the number n of actual connection slots (for each game). To determine whether or not If “YES”, since it is not allowed to give more slots to the slave unit, the process proceeds to the next step S1035 shown in FIG. However, if “NO”, since it is possible to give more slots to the slave unit, the process returns to step S1009.

  When the actual grant slot number n reaches the maximum grantable slot count N, the entry processing for the child device is terminated and the process proceeds to step S1035 in FIG. 28. In this step S1035, the portable game machine serving as the parent machine The processor 20 receives the user name, game name, and the like of the child device for which entry processing has been completed. The user name and game name of this child device are added to the child device list in step S1037, and in step S1039, the child device list 18B is displayed as shown in FIG.

  Thereafter, the processor 20 of the parent device increments (+1) the actual connected child device number m in step S1041, and in step S1043, the actual connected child device number m is the maximum connectable child device M (different for each game). To determine if they are equal. If “YES” is determined in the step S1043, that is, if it is determined that the slave unit cannot be connected any more, the process directly returns.

  Conversely, if one or more slave units are still connectable, that is, if “NO” is determined in the step S1043, the process returns to the step S1007 in FIG.

  In this way, the connection process in step S29 in FIG. 21 is executed. Further, in step S31 in FIG. 22, the entry slot ESlot is used to temporarily cancel the recruitment of the slave units and prohibit the participation of other slave units. Write "ffh" to Then, the connection target CID in the area 86 of FIG. 18 is set to Null and the number of actual connection slots n = 0 so that additional slave units can be recruited as needed during the game.

  Thereafter, in step S33, it is determined whether or not the game is started, that is, whether or not a start button (not shown) included in the operation key 38 is pressed. When the start button is pressed, in the next step S35, the processor 20 refers to the U slot area USlot of the parent machine variable area 86 shown in FIG. 18, and detects the number “m” of the currently connected child machines. . The number of areas that are not “0h” among the areas of the U slot is the number m of the currently connected slave units. In step S37, it is determined whether the number m of connected slave units is smaller than the maximum connectable number M. If “YES” is determined in this step S37, it means that the entry of the new child device can be permitted. Therefore, in this case, in the next step S39, the E slot of the parent device variable area 86 is obtained. One of the vacant slot numbers (slot number corresponding to the area of “0h” in the U slot) is set in the area ESlot. As a result, the state setting of “ffh” in the area ESlot is canceled.

  In step S41, the base unit packet shown in FIG. 11 is broadcast (transmitted) by executing the transmission / reception process of the base unit described above with reference to FIG. Receives handset data (packet).

  Thereafter, in step S43, the processor 20 determines whether or not data of a certain child device has not been received for a certain time t1 or more. If “YES” is determined in step S43, it means that the corresponding slave unit may have already left the communicable range 64 (FIG. 2). In this case, in step S45, The processor 20 deletes the child machine number CID of the corresponding child machine from the U slot area USlot of the parent machine variable area 86 (FIG. 18). As a result of this processing, the slave unit slot used by the detached slave unit becomes an empty slot, so that a new slave unit can be entered instead of the detached slave unit.

  When “NO” is determined in step S43 or when step S45 is completed, in the next step S47, the processor 20 determines whether “ffh” is set in the E slot area ESlot of the parent machine variable area 86 or not. to decide. If “YES”, in the next step S49, the processor 20 executes the game process according to the game program 62 (FIG. 15) of the cartridge 16.

  When “NO” is determined in step S47 of FIG. 22, the process proceeds to step S51 of FIG. 23 in order to allow the slave unit to join midway. In step S51, the processor 20 of the parent device determines whether or not the child device CID has been received in the slot designated by the E slot field ESlot. If “YES”, in the next step S 53, it is determined whether or not “Null” is written in the area of the connection target CID in the area 86 of FIG. If “YES”, that is, if the CID of the connection target slave unit is not registered, the slave unit CID received in the slot designated by the E slot is registered in the connection target CID area in step S55.

  When “NO” in the previous step S53 or when step S55 is completed, in step S57, the processor 20 determines whether or not the received slave unit number CID is the same as the connection target CID. If “YES”, in the next step S59, the slave unit number CID is stored in the portion indicating the entry slot of the U slot region USlot in the region 86 of FIG. In step S61, the actual connection slot number n is incremented (+1). In step S63, whether n = N, that is, the actual connection slot number n has reached the maximum slot number N given to one slave unit. Determine whether or not. If “YES”, no more slots can be given to the slave unit, and slot assignment to the slave unit is terminated. In step S65, “Null” is set in the area of the connection target CID in the area 86, and the variable Write zero (0) to n.

  Thereafter, in step S67, the processor 20 of the parent device determines whether or not the actual connection child device number m is equal to the maximum connectable child device number M. If “YES” is determined in this step S67, that is, if it is determined that the slave unit cannot be connected any more, “ffh” is written in the E slot area ESlot in step S69.

  Note that after step S69, or when “NO” is determined in steps S51, S57, S63, or S67, in any case, the mid-participation process of the slave is stopped and the process returns to the game process (step in FIG. 22). Return to S49).

  The above is the processing of the portable game device when a cartridge that is not compatible with the OC mode is mounted on the own device and when the own device becomes the parent device.

  Next, a description will be given of the processing of the portable game device when the OC mode compatible cartridge is attached to the own device.

  If “YES” is determined in step S5 of FIG. 19, that is, if the cartridge corresponding to the OC mode shown in FIG. 16 is installed in the own apparatus, the processor 20 selects the mode in the next step S71. A screen (not shown) is displayed. In step S73, it is determined whether the normal mode is selected. If “YES”, the process proceeds to step S7 in FIG. 20 in the same manner as when “NO” was determined in the previous step S5. That is, the process when a cartridge that is not compatible with the OC mode is mounted is the same as the process when a cartridge that is compatible with the OC mode is mounted but the normal mode is selected.

  When an OC mode compatible cartridge is attached to the player and an OC mode game is played, the player can only be a master. More specifically, if “NO” in the step S73, that is, if the OC mode is selected, in the next step S75, as in the previous step S29 (FIG. 21), refer to FIG. 27 and FIG. The base unit connection process described in detail above is executed. However, at this time, the number of usable slots N of one slave unit is set to “1” (N = 1), and the maximum allowable number M is set to a number allowed in the game. Thereafter, in step S77, the processor 20 transfers (downloads) the transfer handset program 76 shown in FIG. 16 to the handset. Thereafter, the process proceeds to step S31 in FIG. 22, and the subsequent steps are executed in the same manner as described above.

  The above is the processing of the portable game device when a cartridge compatible with the OC mode is attached to the own device.

  Next, a description will be given of processing of the portable game device when a cartridge that is not compatible with the OC mode is attached to the player and when the player becomes a slave.

  When “NO” is determined in step S27 of FIG. 21, that is, when the player has not selected to become the parent machine, in the subsequent step S79, the processor 20 of the portable game machine 12 uses the operation key 38. The operation signal is verified, and it is determined whether or not an A button (not shown) has been operated, that is, whether or not a parent device desired to be connected has been selected. When “YES” is determined in step S79, the processor 20 subsequently determines whether or not communication with the selected parent device is possible in step S81. That is, it is determined whether or not communication is possible because the cartridge of the parent device and the cartridge of the own device have a predetermined relationship. If communication is possible, then the process proceeds to step S83 in FIG. 24 to execute a slave connection process. Details of the connection processing of the slave units are shown in FIGS. 30 and 31. FIG.

  In the first step S3001 in FIG. 30, the processor 20 of the portable game machine serving as the child machine attempts to receive the parent machine packet (FIG. 11). Then, in the next step S3003, it is determined whether or not the frame synchronization data sync of the parent device selected on the menu screen (FIG. 3 etc.) has been received. Specifically, it is determined whether or not synchronization data sync of the parent device packet including the PID of the parent device selected on the menu screen has been received.

  If “NO” is determined in step S3003, that is, if the parent device packet of the selected parent device cannot be received, it is determined in step S3005 whether a timeout (timeout) has occurred. If “NO”, the process returns to the previous step S3001. If “YES”, in the step S3007, “failure” is written in the connection result variable (in the area 88 of FIG. 18) and the process returns.

  If “YES” is determined in step S3003, that is, if the synchronization signal of the target parent device can be received, in step S3009, the processor 20 of the child device resets the synchronization timer (area 88), and next The process proceeds to step S3011. In this step S3011, the processor 20 sets the pseudo random value as the ID number CID of the slave unit. In step S3013, it is determined whether or not a child device having the CID at this time already exists. That is, it is determined whether or not the same CID already exists with reference to the U slot of the received base unit packet. If “YES” in the step S3013, it is necessary to change the number once assigned. Therefore, in this case, the step S3011 is executed again, a new number CID is assigned, and the verification in the step S3013 is performed. Try again.

  These steps S3011 and S3013 are repeated until “NO” is obtained in step S3013. When “NO” is obtained, the process proceeds to the next step S3015. In step S3015, the number n of actual grant slots is set to zero (0). Further, in the next step S3017, the master unit packet is received, and in step S3019, the synchronization timer is reset again. In step S3021, the processor 20 determines whether or not the E slot ESlot (see FIG. 11) of the received parent device packet is “ffh”. If “YES” is determined in this step S3021, entry of the slave unit is prohibited, and the process returns to “failure” through the previous step S3007.

  If “NO” is determined in the step S3021, the slave unit entry is not prohibited, and the process advances to the step S3023 in FIG. In step S3023, the CPU core of the child device transmits the number CID obtained in step S3011 to the slot indicated by the E slot field ESlot of the parent device packet at that time. In step S3025, the base unit packet is received, and in step S3027, the synchronization timer is reset again.

  In subsequent step S3029, processor 20 of the slave unit checks whether or not its own number (CID) exists at the entry slot position in the U slot field of the received master unit packet. If “NO” is determined in the step S3029, the processor 20 determines whether or not a time-out occurs in a next step S3031. If it is not time-out, the process returns to the previous step S3017 (FIG. 30). If time-out occurs, “failure” is written in the connection result variable in step S3007 of FIG.

  When “YES” is determined in step S3029, that is, when the own slot number (CID) is in the entry slot position of the U slot of the received parent device packet, the number n of actually granted slots is incremented in the subsequent step S3033 ( In step S3035, the maximum number of slots N that can be granted to one slave unit (however, this N varies depending on the game, and is a value of 1-4, for example). Determine if they are equal. If “NO” is determined in this step S3035, that is, if the slot can still be assigned, the process returns to the previous step S3025 to receive the parent device packet.

  However, if “YES” is determined in step S3035, “success” is registered in the connection result variable in the next step S3037 on the assumption that all the possible number of slots have been allocated, and the process proceeds to the next step S3039. . In this step S3039, the base unit number PID of the connected base unit and the acquired slot number are stored in the area 88 of its own internal RAM 28 (FIG. 18). However, there may be a plurality of slots, and in this embodiment, it is a numerical value of “0”-“3”. Then, the process returns to step S85 in FIG.

  In step S85, the connection result variable in area 88 is referred to and it is determined whether or not the connection result is “success”. In the case of “NO”, in the next step S87, a message such as “Could not be connected” is displayed on the LCD 18 (FIG. 1) of the slave unit, and the process returns to step S7 in FIG.

  If the connection to the parent device is successful, in the next step S89, the processor 20 of the child device uses its own child device slot and the user name and game name for the parent device. Send. In step S91, it is determined whether or not the game is started, that is, whether or not the start button included in the operation key 38 is pressed. If it is detected in step S91 that the start button is turned on, in the next step S93, transmission / reception processing of the slave unit is executed.

  The slave transmission / reception process shown in step S93 in FIG. 24 is shown in detail in FIG. In step S4001 of FIG. 32, the base unit packet is received, and in the next step S4003, the synchronization timer (FIG. 18) is reset. In step S4005, the processor 20 of the slave unit determines whether there is untransmitted data in the transmission buffer 92 (FIG. 18). If “YES”, in the next step S4007, necessary data, for example, CID and payload are transmitted using the already assigned child device slot. If there is no untransmitted data or after step S4007, the process returns to step S95 in FIG.

  Returning to FIG. 24 again, in step S95, the processor 20 of the slave unit determines whether data from the master unit has not been received for a time t2 or more. This time t2 is shorter than the time t1 in step S43 of FIG. That is, t1> t2. This is because t1 is the time for the parent device to disconnect the slave device with abnormal communication, and t2 is the time for the child device to start the recovery process, so it is necessary for the parent device to disconnect after waiting for the recovery processing of the child device. Because there is. In the case of “NO”, in the next step S97, it is determined whether or not its own number CID is included in the U slot field of the received base unit packet. If “YES” in the step S97, the game process of FIG. 22 is executed in a step S99. However, if “NO” is determined in step S97, that is, if there is no own device number in the U slot field of the parent device packet, in step S101 a message such as “disconnected from parent device” Is displayed on the LCD, and the process returns to step S7 in FIG.

  When “YES” is determined in the previous step S95, that is, when data from the parent device cannot be received for a certain time t2 or longer, a message such as “Communication with the parent device is no longer possible. After "I will try" is displayed, a return process is executed in step S105.

  Details of the return processing are shown in FIG. 33. In the first step S5001 of FIG. 33, the processor 20 of the slave unit attempts to receive the parent unit packet to be returned. In step S5003, it is determined whether broadcast data from the parent device has been received. However, whether or not it is the parent machine to be restored can be determined by looking at the “connection destination PID” registered in the area 88 of FIG.

  If “NO” is determined in the step S5003, that is, if the data of the parent packet to be recovered cannot be received, it is determined whether or not a time-out has occurred in the next step S5005. If “NO”, the process returns to the previous step S5003, but if time-out occurs, in the next step S5007, “failure” is written in the return result variable included in the area 88 shown in FIG. 18 and the process returns.

  If “YES” is determined in the previous step S5003, that is, if a parent device packet from the target parent device can be received, the synchronization timer is reset in the next step S5009, and further, in step S5011, the parent device is reset. Receive the packet. In step S5013, it is determined whether or not its own number CID exists in the U slot field of the parent device packet. The fact that the received parent device packet has its own device number means that the cause of the communication failure state over time t2 is not intentional disconnection by the parent device, and therefore, in the next step S5015, the region Register “success” in the return result variable 88 (FIG. 18) and return. By performing the return processing in this way, for example, when the parent device and the child device are out of the communication range by mistake, when the communication state is bad and communication is not possible, or the child device is operated. When a player can use the device and the slave player needs to be out of the communication range for a while, the communication state can be restored after those factors are resolved and the communication state can be restored. It becomes possible.

  However, even if “YES” is determined in step S5003, if “NO” is determined in step S5013, it is determined that the communication failure is caused by the disconnection of the parent device, and the process returns through the previous step S5007. .

  When returning from the subroutine of FIG. 33 to step S107 of FIG. 24, in this step S107, it is determined whether or not the return is “successful” with reference to the return result variable in the area 88. If “YES”, the process proceeds to step S99 to execute the game process. However, if “NO”, a message such as “Could not be restored” is displayed in step S109, and the process returns to step S7 in FIG.

  The above is the processing of the portable game device when a cartridge that is not compatible with the OC mode is attached to the player and when the player becomes a child device.

  Next, the processing of the portable game device when the cartridge is not attached to the own device will be described. However, in this case, the own device can only operate as a child device of the OC mode compatible game.

  Returning to FIG. 19, when “NO” is determined in step S3, that is, when it is detected that there is no cartridge in the slave unit, wireless communication is performed in step S111 which is a program in the boot ROM (24 in FIG. 1). The OCD program (program for downloading the slave program from the parent device) set in the ROM 52 of the unit 14 (FIG. 1) is expanded in the WRAM 28 included in the processor 20 of the portable game machine 12, and then in step S113. The slave processor 20 activates the OCD program developed on the WRAM 28.

  Thereafter, in step S115 in FIG. 25, the processor 20 of the child device clears the parent device list area 80 as shown in FIG. 18 and resets the parent device list clear timer 82. Next, in step S117, an attempt is made to receive the parent device packet. Then, in step S119, it is determined whether or not reception of the parent device packet is successful. If “NO”, the process proceeds to step S125, and if “YES”, the process proceeds to step S121. In step S121, the parent device number PID included in the received parent device packet is compared with the number PID registered in the parent device list area 80 shown in FIG. Judge whether it exists in the machine list. If “YES” is determined in step S121, the parent device number PID, user name, and game name read from the parent device packet so as to register a new parent device in the parent device list in step S123. , OC flag and E slot are added to the parent device list area 80. Thereafter, the process proceeds to step S125.

  In step S125, it is determined whether or not the value of base unit list clear timer 82 reset in step S115 is equal to or greater than “2 seconds”. If “YES”, in step S127, the parent device list, that is, the parent device list area 80 is cleared, and the parent device list clear timer 82 is reset. Thereafter, similarly to the case where “NO” is determined in step S125, the process proceeds to step S127.

  In step S127, the parent device in which the E slot is not “ffh” and the OC flag is “1” in the parent device list, that is, the game in the OC mode can be played and the participation (entry) of the child device is rejected. The information (user name, game name) of the parent device that has not been displayed is displayed. Accordingly, the parent device list 18A as shown in FIG. 5 is created for the user of the child device, and the parent device to which the own device wants to connect is selected. In step S131, it is determined whether an A button (not shown) has been operated. That is, it is determined whether any one parent device is selected. If “NO” in the step S127, that is, if the parent device is not selected, it is determined whether or not a cross key (not shown) included in the operation key 38 is operated in a next step S133. The operation of the cross key is to move the cursor to select the parent machine that desires entry. Therefore, if “YES” in this step S133, the cursor is moved in the next step S135, and the process returns to the step S113. .

  If “YES” is determined in the step S131, the process proceeds to a step S139 to execute a connection process (FIGS. 30 and 31) of the slave unit.

  In step S137, the slave unit connection process is executed according to the method already described in detail, and in the next step S139, it is determined whether or not the connection is successful by referring to the connection result variable in the area 88 of FIG. If “NO”, a message such as “Could not connect” is displayed in step S141, and the process returns to step S111.

  If “YES” is determined in step S139, the processor 20 transmits the user name and game name of the own device to the parent device that has been successfully connected to the child device. Thereafter, the process proceeds to step S145 in FIG. 26, and in order to play the game in the OC mode, the transfer slave unit program is received from the master unit and expanded in the RAM 28 (FIG. 1) of the host unit, and the program is started. Let And after that, in step S147, each step similar to FIG. 24 step S91-S109 demonstrated previously is performed.

  The above is the processing of the portable game device when the cartridge is not attached to the own device.

  When “NO” is determined in step S81 in FIG. 21, that is, when an attempt has been made to select a parent device but communication has failed, a message such as “The parent device cannot be selected” is displayed in step S149. Then, the process returns to step S9 in FIG.

  When “NO” is determined in step S79 in FIG. 21, that is, when neither the B button nor the A button is operated, whether or not a cross key (not shown) is operated in the next step S151, to decide. If “NO”, it is determined in a next step S153 whether or not a start key (not shown) is further operated. When the select key is not operated, the process returns to step S9 in FIG. If "YES" is determined in the step S153, the whole display flag is switched on / off in a step S153, and then the process similarly returns to the step S9 (that is, the select key is used to turn on / off the all display flag). used). However, if “YES” is determined in the step S151, the cursor is moved in accordance with the instruction of the cross key, and then the process returns to the step S9.

  In the above-described embodiment, it is selected whether the own device is a parent device or a child device in accordance with the progress of the program. However, such a selection may be made immediately. In this case, as shown in FIG. 34, a selection screen (not shown) for a parent device or a child device is displayed in the first step S201 immediately after the start, and the user selects the parent device or the child device according to the display. . Therefore, the processor 20 determines whether or not the user has selected the parent device in the next step S203. If “YES” in the step S203, thereafter, the steps after the step S29 in FIG. 21 are executed. If “NO”, that is, if a slave is selected, steps S7-S25, S79, S151-S157, and S81-S109 shown in FIG. 21 are executed.

DESCRIPTION OF SYMBOLS 10 ... Portable game device 12 ... Portable game machine 14 ... Wireless communication unit 16 ... Cartridge 18 ... LCD
20 ... Processor 22 ... CPU core 24 ... Boot ROM
28 ... WRAM
38 ... operation keys 42 ... ROM
54 ・ ・ ・ EEPROM

Claims (11)

A wireless communication game system for playing a communication game using a plurality of portable game devices capable of short-range wireless communication with each other,
The wireless communication game system includes a game device having communication means and another game device,
Said other Gate beam apparatus,
First communication information for identifying the certain game device from the unspecified certain game device, and game identification information for identifying a communication game that can be currently executed on the certain game device. Second receiving means for receiving using,
Based on the information received by the second receiving means, the certain game device that can execute the communication game with the other game device is extracted, and each of the extracted certain game devices A second display control means for outputting a display for identifying each game device on the screen;
In accordance with user input by the input means, second selection means for selecting a desired game device from among the displays for identifying each game device displayed by the second display control means, and selected by the second selection means A wireless communication game system comprising connection request means for making a connection request to a game device for executing the communication game with the game device.   The wireless communication game system according to claim 1, wherein each of the plurality of portable game devices has functions of both the certain game device and the other game device. Game equipment the certain is a game program for executing a communication game in the one game device during startup, the other gate information for identifying the game program in the boot as the game identification information The wireless communication game system according to claim 1, wherein the wireless communication game system is transmitted to a game device. Game equipment the certain, during execution of the communication game with another game apparatus, to the other Gate beam apparatus information for identifying the communication game in the running as the game identification information The wireless communication game system according to claim 1, wherein the game is transmitted. Game equipment the certain, in addition to the game identification information and the first identification information, transmits the connection permission information indicating whether or not to permit a connection to the one game device to the other Gate arm device And
The second display control means of the other Gate beam device, on the basis of the first identification information, the game identification and the connection permission information received from unspecified the certain game device, the other game The wireless communication game system according to claim 1, wherein the certain game device that can execute the communication game with a device and permits connection is extracted. The certain game device includes:
First receiving means for receiving the connection request from the unspecified other game device;
First display control means for outputting, on a screen, a display indicating the other game device that has transmitted the connection request, based on the connection request received from the unspecified other game device;
First selection means for selecting a desired game device from among the other game devices that have transmitted the connection request according to a user input by the input means, and a connection request from the game device selected by the first selection means The wireless communication game system according to claim 1, further comprising a rejecting unit that rejects the request. A game device used in a wireless communication game system for playing a communication game using a plurality of portable game devices capable of short-range wireless communication with each other,
First identification information for identifying the game device and game identification information for identifying a communication game that can be currently executed on the game device in a state where the user has not selected a partner to play the communication game. Transmitting means for transmitting to other unspecified game devices using communication means;
Second receiving means for receiving the first identification information and the game identification information from another unspecified game device using a communication means;
Based on the information received by the second receiving means, other game devices capable of executing the communication game with the own device are extracted, and for each of the extracted other game devices, each game device is A second display control means for outputting an identification display on the screen;
In accordance with user input by the input means, second selection means for selecting a desired game device from among the displays for identifying each game device displayed by the second display control means, and selected by the second selection means A game device comprising connection request means for making a connection request to the game device for executing the communication game with the game device. A game device used in a wireless communication game system for playing a communication game using a plurality of portable game devices capable of short-range wireless communication with each other,
Using communication means, first identification information for identifying the other game device from unspecified other game devices and game identification information for identifying a communication game currently executable on the other game device are received. Second receiving means,
Based on the information received by the second receiving means, other game devices capable of executing the communication game with the own device are extracted, and for each of the extracted other game devices, each game device is A second display control means for outputting an identification display on the screen;
In accordance with user input by the input means, second selection means for selecting a desired game device from among the displays for identifying each game device displayed by the second display control means, and selected by the second selection means A game device comprising connection request means for making a connection request to the game device for executing the communication game with the game device. A computer of a game device used in a wireless communication game system for playing a communication game using a plurality of portable game devices capable of short-range wireless communication with each other,
First identification information for identifying the game device and game identification information for identifying a communication game that can be currently executed on the game device in a state where the user has not selected a partner to play the communication game. Transmitting means for transmitting to other unspecified game devices using communication means;
Second receiving means for receiving the first identification information and the game identification information from another unspecified game device using a communication means;
Based on the information received by the second receiving means, other game devices capable of executing the communication game with the own device are extracted, and for each of the extracted other game devices, each game device is A second display control means for outputting an identification display on the screen;
In accordance with user input by the input means, second selection means for selecting a desired game device from among the displays for identifying each game device displayed by the second display control means, and selected by the second selection means A game program that causes a game device to function as a connection request unit that issues a connection request for executing the communication game with the game device. A computer of a game device used in a wireless communication game system for playing a communication game using a plurality of portable game devices capable of short-range wireless communication with each other,
Using communication means, first identification information for identifying the other game device from unspecified other game devices and game identification information for identifying a communication game currently executable on the other game device are received. Second receiving means,
Based on the information received by the second receiving means, other game devices capable of executing the communication game with the own device are extracted, and for each of the extracted other game devices, each game device is A second display control means for outputting an identification display on the screen;
In accordance with user input by the input means, second selection means for selecting a desired game device from among the displays for identifying each game device displayed by the second display control means, and selected by the second selection means A game program that causes a game device to function as a connection request unit that issues a connection request for executing the communication game with the game device. A game processing method in a wireless communication game system for playing a communication game using a plurality of portable game devices capable of short-range wireless communication with each other,
The wireless communication game system includes a game device having communication means and another game device,
Said other Gate beam apparatus,
First communication information for identifying the certain game device from the unspecified certain game device, and game identification information for identifying a communication game that can be currently executed on the certain game device. Received using
Based on the first identification information and the game identification information received from the unspecified game device, the game device capable of executing the communication game with the other game device is extracted. For each of the extracted game devices, a display for identifying each game device is output to the screen,
According to the user input by the input means, a desired game device is selected from a display for identifying each game device displayed on the screen,
A game processing method for making a connection request for executing the communication game with a selected game device.

Images