redux-framework domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131workreap domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131customized-task-offer domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131workreap-hourly-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131| Management number | 211948609 | Release Date | 2026/04/06 | List Price | $28.80 | Model Number | 211948609 | ||
|---|---|---|---|---|---|---|---|---|---|
| Category | |||||||||
2001 saw the birth of a brand-new Mega Man series with the release of the first Mega Man Battle Network game. Set in a near-future world where advanced network technology has become the norm, the game captured the hearts of young children as they embarked on an adventure alongside the relatable protagonist. Complete with engaging game systems that combined elements of card battle and action games, the unique Data Action RPG went on to spawn a hit series. Accompanying comics and cartoons went even further to cement the legacy of the series. The year is 200X. The rapid growth of internet technology has given rise to Network Society. People carry with them PETs, mobile devices equipped with sentient programs called NetNavis, which they use in order to enjoy the many benefits the network provides. But even though the network has improved their way of life it has also brought with it new outlets for cybercrime. The protagonist, Lan Hikari, and his NetNavi, MegaMan.EXE, must work together to solve numerous incidents. Mega Man Battle Network Legacy Collection title included: - Mega Man Battle Network - Mega Man Battle Network 2 - Mega Man Battle Network 3 White - Mega Man Battle Network 3 Blue - Mega Man Battle Network 4 Red Sun - Mega Man Battle Network 4 Blue Moon - Mega Man Battle Network 5 Team Protoman - Mega Man Battle Network 5 Team Colonel - Mega Man Battle Network 6 Cybeast Gregar - Mega Man Battle Network 6 Cybeast Falzar
| Rated | Rating Pending |
|---|---|
| Language | Unknown |
| Item Weight | 1.9 ounces |
| Manufacturer | Capcom |
| Type of item | CD-ROM |
| Item model number | HAC-P-A8H2A |
| Package Dimensions | 6.65 x 4.06 x 0.47 inches; 1.9 ounces |
If you notice any omissions or errors in the product information on this page, please use the correction request form below.
Correction Request Form