It’s a bit old, but Chaz on Youtube has a great video explaining some weird facts about Earthbound, including mysterious crashes, when the game registers the effects of statuses like Sunstroke, and why there’s a small number of places in the game where you can find an early enemy, the Mole Playing Rough, in regions where you usually find much stronger enemies. It’s ten minutes long:
Here’s the gist:
Earthbound maintains a flag that the video calls the Overworld Status Supression Flag. If this flag is on then your characters can’t get a number of statuses like Sunstroke, or take environmental damage. If this flag is on, though, and your party loses to a scripted (not random) battle, then a bug is triggered that’s popularly called the Game Over Glitch: the battle loss cutscene music plays, but the screen turns black and nothing appears to work. In fact, the game has not crashed: entering the Town Map screen, or feeling around for and entering a door, will display graphics again, although glitched out. The Game Over Glitch is best known for happening if the player loses to one of the Shattered Man fights in the Museum after the game has been won: during the ending, the Overworld Status Supression Flag is set on permanently, so getting into any scripted fight and losing will result in the glitch happening.
As it turns out, random encounters disable the flag. So there is a hard-to-avoid Mole Playing Rough at the entrances to areas with environmental damage, to make sure the flag is turned off. But the mole is just hard to avoid, not impossible, so if you can avoid it, and all other random enemies of course, and then reach a place with a scripted fight, then lose to it, the glitch will still happen.
Displaced Gamers’ Behind the Code series is one of the best explainers of the quirks of NES games on Youtube. It’s not afraid to dive into the assembly code itself if need be, but its videos can often be understood by people without deep technical backgrounds.
Watch the video for the full spiel, but here’s a summary.
Once upon a time, in the waning days of the Famicom, Konami planned to release a game called Arc Hound in Japan. It was going to be another of their trademark run-and-gun shooters, along the lines of Contra. It even received coverage in enthusiast magazines in Japan, and it probably would have used one of Konami’s bespoke mapper chips like the VRC6 that the Japanese version of Castlevania III used.
Arc Hound was likely far into development when the decision was made to not release it in the Japanese market. Producing a game cartridge requires a substantial investment in parts and marketing, of course, and they must have judged that they couldn’t make enough of a profit off of it in their home territory: the Super Famicom was already out, as well as Contra III on that platform. But the NES still had a little bit of life left in it in the US, so they decided to give the game a shot over here, as a title in the Contra series
A big problem there was Nintendo’s policies towards manufacturing NES games. Nintendo demanded the right to build all the licensed software for the NES, and further restricted most (although not all) publishers to using Nintendo’s own family of mappers. Konami had been forced to revise their games to use Nintendo’s mappers in other games: Castlevania III famously used a different mapper in Japan, one that offered greatly expanded sound capabilities that worked through the Famicom’s sound channel pass-through, but was incompatible with the NES.
Extra sound channels are nice, but the primary use for most mapper chips is bank switching, swapping different sections of a cartridge’s data into the Famicom/NES’s 6502-workalike’s 64K address space, and also potentially making different sections of the game’s graphics data visible to the PPU graphics chip.
Behind the Code’s examination of the game program reveals that a large portion of the time of each frame is spent in setting up bank switches. Whether it was coded poorly, or just that Konami didn’t want to pay to include a mapper with more a more efficient bank switching mechanism, the game wastes a lot of time just pulling in different banks of data to be visible to the NES’s hardware. So it is that Contra Force could have run a lot better, but Konami either didn’t want to expend the coding effort, or pay for the the mapping hardware, to allow it to do so.
Presumably, somewhere in Konami’s archives, there is a version of Arc Hound that uses a VRC chip to handle mapping, and that runs much more smoothly. Maybe someday it’ll come to light, although I wouldn’t lay any bets on it. More likely perhaps is that someone will hack up the code and make such a version themselves. Who knows?
Kaze Emanuar on Youtube passes along the info that Rare’s terrific N64 platformer, Banjo-Kazooie, has been decompiled (7 minutes):
What does that mean? It’s that they’ve created source code (up on GitLab) that, when put through the same C compiler that originally generated Banjo-Kazooie’s object code, produces an exact binary image of the game. They can now rebuild Banjo-Kazooie. They don’t know the original variable names or any comments that were in the code, so it doesn’t mean that the code is perfectly understandable, but it is a major breakthrough in using the game engine for other things, including game improvements, mods, repurposings, and even compiling it for other platforms.
One result of this is that we now have a complete list of the codes that can be entered into the infamous Sandcastle Room, which are obfuscated in the original binary. The Sandcastle Room is a board of letters on the ground in the second level that can be used to spell things out, and if the proper text is entered it can unlock things in the game, or even enable the items in the abandoned “STOP N SWOP” feature that had been planned to allow players to transfer data between cartridges. If you decide to take a look yourself, the codes are listed out in the file named code_3E30.c.
Arcade Mermaid is our classic arcade weirdness and obscurity column! Frequently (no promises) we aim to bring you an interesting and odd arcade game to wonder at.
Yes! More Rampart! I’m still out of town at DragonCon so I’m repurposing an old strategy guide I wrote for Extended Play into a week of posts. Even I’m starting to get sick of Rampart by now, but please stick around. And if you’ve ever tried playing this infuriating game in the arcade, this might give you the advice you need to get through to levels you might not have thought possible! And this is even a fairly short post!
Level Strategies
Level One (“Recruit”)
Castles available: 6
It’s advised not to start on this level unless it’s your first game. You’ll not only miss out of 5,000 points by starting here, but it means the beginning of Level 2 will begin you with only two cannons instead of three, and you’ll face more ships.
This level is so easy that it barely rates mention. It has six castles, and only Gunships appear. Unless you’re purposely stalling, you’ll finish this map in two rounds. Even if you stall, the level auto-completes in three rounds, regardless of if you fire a single shot.
Another reason to avoid picking Beginner is that its selection is always the “J” map, which is one of the easier selections from the initial four boards. It’s better if you pick it later, when the opposition is harder, to balance out the difficulty.
Level Two (“Veteran”)
Castles available: 5
The Veteran level is randomly chosen from one of the other three basic maps, although it tends to be the “C” map most often. Ideally it won’t be the “Hat” map, it being the easiest, as you’ll want it to be your Level 4.
If you started on the board, the first round will always put you up against four ships, one of which may be a Lander. Later ships are frequently also Landers. As a result grunts may appear on this board, but even if some appear, so long as you focus on destroying enemy ships and don’t suffer major setbacks like losing your home castle, you’ll probably wipe out the attackers before they become a huge problem.
On a later round in this level you’ll probably encounter your first Red Ship. A Red Ship tends to get off two or three shots in a round, each producing flaming crater you must build around.
Level Three
Castles available: 5
You always get to pick this level yourself. I usually try to make it “C,” “J” or “Hat,” in that order. I usually avoid picking “N,” but it’s not really harder than “C,” so pick whatever is your preference.
Much of the fleet will be Landers here, so this is the first level where you must be diligent about thinning out their numbers. Especially try to take care of ships about to land; grunts are unwelcome visitors to deal with, and it’s best if they never show up at all. In the event of a landin, which is sometimes unavoidable, try to spare a few seconds to build a barrier to them, to wall them off from the rest of the board. If you can contain them in a small area around the landing, you can keep their numbers down that way and thus reduce the number of shots you must expend in cleaning them up. Don’t think you can just let them be! They will overwhelm you easily if you ignore them.
I try to pick a home castle that’s near another castle, so I can capture them both with one wall. If you can consistently get both each round, that’s three cannons each time. Use them to connect the space between the two castles, but try to keep that space as small as possible. Try to aim for the minimum-sized rectangle needed to save both of them, and then try to place all your cannons within that rectangle.
Level Four
Castles available: 4
Now the game starts to get serious. If you can get here on your first credit you’ve done very well, but your weak basic guns will become more and more of a liability for you. Dark ships start appearing on this level, and will continue to appear until the end of the game. They all take one extra hit to sink. That’s three hits for Gunships, four for Landers, and six for Red Ships.
Try to make Landers that have a chance of landing at a diagonal shore your top priority. If one makes it through, then at the start of the Building phase devote three seconds or so it blocking their progress with walls. If they get away from the shore and a significant number appear, then focus on surviving and shoot them with cannons during Battle. Red Ships start to be a significant threat here. Once all the potential landings are taken care of, try to pump six shots into a Red Ship.
Level Five (peninsula)
Castles available: 3
Regardless of how you got here, you have a choice between two new maps for this level, a diagonal peninsula going upper-right to lower-left, or one going from upper-left to lower-right. I call these the “slash” and “backslash” maps, respectively. I usually pick backslash, but both are about the same difficulty.
These maps have the property of having two seas, a small one at the top of the screen and a more typical larger one at the bottom. The small water region is both a blessing and a curse; the restricted movement makes it easier to destroy ships there, but landings are very likely unless you clear out the Landers arriving there. What is more, these maps are the only ones in the game that break the rule about landings only being possible on diagonal shores. Landers in the small sea are also counted as landed if they contact land at the very edge of the screen, even if there’s no diagonal shore nearby. This property doesn’t extend to screen-edge landings in the larger sea.
The worst thing about these levels is that the game takes off the limiter on the number of Red Ships that can be generated each round. Red Ships here are nearly as common as Double-Sailed ones! You’ll frequently see seven or more on-screen at a time. While you must remain vigilant to prevent and/or mitigate landings, you must also work towards reducing the number of Red Ships. The large number of flaming craters on these levels made adopting a “summer home” strategy imperative, where you switch off between castles when one gets too difficult, or even impossible, to save. It’s usually a good idea to try to capture two castles in the first round because of this; then you can station some or all of your cannons for that round at the other castle, so you’re not defenseless when you’re forced to turn to it for survival. From there, you can focus on getting cannons around the third castle for maximum safety.
This level is a strong test of your Rampart skills, and often is a barrier to progression until you’ve played many games. But it’s not invincible. On Easy difficulty, I’ve passed this level still on my first credit multiple times. The biggest thing you have to worry about is the high probability of impossible situations.
Consider: when any castle is adjacent to other objects, you must capture the whole collection as a set. Chains of objects like this increase the difficulty of getting the whole thing, and increases the odds of getting an impossible save. I’ve seen this happen after even the first round on a peninsula board, and I’ve seen it happen on all three castles on one of these maps at the same time. The only substantive thing you can do, besides rotating between castles, is to shoot some of the dangerous walls yourself. Red Cannonballs don’t leave craters if the wall is already destroyed, but that takes time and often makes for a difficult repair.
So, what if you manage to clear this map? What happens next? The game scrolls the FINAL BATTLE banner, and you get a one-way ticket to:
Level Six (island)
Castles available: 2
It all comes down to this. This level is a special kind of hell, only slightly mitigated by the fact that it seems you can get away with sinking fewer ships here, and, because you’re surrounded on all sides, your shots often don’t have that far to travel to reach a ship. There are four prime landing areas, each in one corner of the map, so landings can only be delayed, not prevented. And you only get two castles. Enjoy!
When you start looking more closely at the map, some slight advantages become apparent. There’s a lake in the bottom-left of the board, which gets in the way, somewhat, of grunts approaching from the bottom. Both castles have a good amount of land around them, although there are so many Red Ships here that the “summer home” strategy is essential to survival.
The continue limit eases up a little bit here. If you were at the maximum of four continues upon starting Level Six, the game will grant you an extra continue when you get here. (You still have to pay your coins for it though.) And also, if you were at that final credit, the game will actually downgrade your cannons one step when you get here, so get used to expending two/three/five shots for Gunships/Landers/Red Ships again. If (ha ha, “if”) you do expend that last continue, you go back to only needing one/two/four shots to sink ships. (There is more information on the effects of continues on cannon power in the notes, later on.)
This level is an ordeal, but it can be finished surprisingly quickly. I’ve seen it cleared in three rounds, although that was after several continues (it had been a pretty great game up to that point). This level is the big obstacle to one-credit clears, I’ve managed to finish everything up to it on one credit only to bang my head against it repeatedly. Using save states, I’ve managed to finish it with a single continue, so it is possible to finish it relatively cheaply, but making do with such weak cannons is a real challenge.
I just got back from DragonCon, and I’m pretty amazed that I didn’t get the connection that the Andrew Greenberg there, who created the classic TTRPG Vampire: The Masquerade, shared a name with Andrew Greenberg, co-creator of Wizardry. And how much of a coincidence it is that the later Greenberg passed away during DragonCon this year, while the former one was there and presenting panels.
Of course this post is about the Wizardry Greenberg. His passing was reported by the other major Wizardry creator, Robert Woodhead, on his Facebook page. It is nice that Digital Eclipse’s wonderful remake of Proving Grounds of the Mad Overlord made it out while he was still alive. The name of the evil wizard in that game, Werdna, is Andrew spelled backwards. (Spelling names backwards was a popular way to name fantasy characters in early CRPGs. Trebor, the Mad Overlord himself, is Robert, as in Robert Woodhead, reversed, and Yendor from Rogue is Rodney backwards.)
Andrew Greenberg and Robert Woodhead. Image from Woodhead’s Facebook page
Youtube channel Tea Leaves has an obit video (6 minutes) that fills in some of the context:
Arcade Mermaid is our classic arcade weirdness and obscurity column! Frequently (no promises) we aim to bring you an interesting and odd arcade game to wonder at.
Because I’m out of town for a few days, we’re continuing our week-long coverage of Atari Games’ brilliant, yet really hard classic arcade strategy game Rampart.
Each of Rampart’s phases has its own considerations, so let’s take them one at a time.
Battle Phase
Rampart’s most traditional mode is its Battle sequence, which plays a bit like Atari’s old hit Missile Command. For a limited amount of time, players use the trackball to move a crosshairs around the screen, and the Fire button launches a cannonball from one of their cannons aimed at that spot. Cannonballs have a set speed that they travel as they move through the air; nearby shots go directly towards the destination, but distant targets travel in a high arc. Thus, more distant shots take much more time to reach their targets, due to the fact that they have to be angled upward.
The speed of your shots matters for two important reasons. First, in single-player mode, enemy ships don’t always sit still and let your projectiles sink them, but move around at different speeds, and sometimes even try to dodge your shots. One of the most annoying events in Rampart is when you launch a volley towards a ship, and it decides to pull anchor and float elsewhere just as your shots launch, wasting those precious missiles. Firing at close-up ships means you don’t have to lead your targets by nearly as much, and reduces the chance that a ship will just sail out from under your projectiles.
The other important thing is, each cannon can only have one shot in the air at a time. Firing at nearby targets means you can get more shots off during a Battle phase. The combination of the two, being more accurate when shooting moving targets and getting more shots off, means that, absent other issues, you should prioritize firing at ships near your guns.
You cannot entirely erase the chance that a ship will decide to start, or stop, moving after you launch shots towards it, but there is some finesse that can be applied. Ships always sail in a straight line in one of the eight cardinal/diagonal directions, and ships cannot move through other ships. If a moving ship runs into another one, it will stop. They cannot turn around while in motion, but must wait until their invisible captain picks a new direction, which could be immediately or never. They also stop if they reach the shoreline, which for a Lander could be very bad for you. Once in a while a moving ship will just stop for no reason. The only constant is, all ships stop moving at the very end of the Battle phase, once all cannonballs have landed.
The rules of cannonfire, the ones concerning shot speed and there only being one shot in play at a time per weapon, they also apply to the enemy ships. Nearby ships are able to launch more shots at closer walls than distant ones, another reason to prioritize shooting nearby ships. But this must be balanced against those times when you need to prevent a landing, or take out some Red Ships to make the Build phase more survivable.
The game continues no matter how many ships you sink in Battle, but to progress to the next level, and eventually win the game, it’s advantageous to sink ships. The exact qualification for finishing a level is unknown, but it seems to happen after you wipe out most of the ships on-screen.
There is a maximum of 16 ships that can be in play at any time. If that number is reached, but there are some weakened or Single-Sailed Ships on-screen, Rampart is known to remove some of them so stronger ships may enter the fray.
Building Phase
This is the meat of the game. While shooting ships eventually clears levels, you can’t do that without cannons, and cannons are awarded from skill at building. Also, if you fail to capture at least one castle in a round, you lose.
The way it works is, the game hands you an assortment of building pieces of various shapes, one at a time. The pieces you’re given first exist as just a flashing outline that you can maneuver freely over the land with the trackball or joystick. You can move it anywhere while you’re getting it into position, or rotate it clockwise with a press of the “Rotate” button. (If you start out your first building phase without using the button, the game’s voice will suddenly intone, “Use ROTATE for a better fit!” Rampart doesn’t have nearly as much digitized speech as Gauntlet, but it sure is memorable when it does speak.)
The difficult bit is, you cannot place pieces anywhere there is something per-existing. A piece cannot be placed if any part of it overlaps with another wall, the shore, a castle, a cannon, a crater, a grunt, or the edge of the screen. Everything visible beneath the piece’s outline must be the clean, green checkerboard of countryside.
You must place the current piece before you get the next one. Intermediate Rampart players ruefully observe that the game tends to hand out just the wrong piece they need at a given time. A lot of this is observation bias, you don’t tend to notice the times when the game hands you just the right piece, but it’s true that the pieces the game has to hand get larger and more complex as the game continues.
When a piece is plopped down it turns into wall. If the wall adjoins wall pieces already extant, they’ll join together pleasingly into a solid-looking structure. Your task is to connect wall pieces together like this until you have a complete loop all the way around and enclosing at least one castle. Usually you want this castle will be the one you start with, called your “Home Castle.” It’s worth extra points and cannons if you capture it, but any castle will allow you to survive.
There are two particular hassles in the Building phase that deserve special mention. The first are those grunts the Landers sometimes drop off if they reach the shore, and that have the power to move around during Building. They look like tiny tanks, or little battering rams.
Grunts move during Building, meaning they can actually block pieces just as you’re trying to place them. They not only move, but slowly multiply as they go, tending to form lines between the shore and your castles. Worst of all, grunts that make it to your castles have the power to destroy them during the following Battle phase, the only thing in the game that can harm a castle itself.
Grunts are so dangerous that landings must quickly be dealt with or else your game will soon be over. You can shoot them during the Battle phase, or you can surround the territory they’re on, destroying them instantly with a satisfying crunching noise.
Keep Landers away from diagonal shorelines, or you’ll have a bad time!
One important thing to note about grunts is that they can’t be dropped off just anywhere. Landers (here circled) can only leave grunts on diagonal shorelines. Highlighted above are the landing sites on the “Hat” map. Guard them at all costs.
The other problem you must worry about during Building is craters, flaming pits in the very ground left when the red cannonballs launched by Red Ships strike your wall. A crater is an implacable obstacle; there is no way to remove a crater from the board other than time. Near the end of the game, depending on the randomized ship generation, you may end up with rounds where you must face six or more Red Ships at once, which is horrifying.
Caused by too many craters left by Red Ships, this situation cannot be survived. Can you see why?
When a crater is formed, it’s a full-strength pit of fire. Every Battle phase, each crater diminishes a bit. They all do this in lockstep: all the craters formed in one round will advance to the next state at once.
How does the game decide how quickly to make craters disappear? It’s a function of how recently you’ve put in money and continued the game! If you’ve recently continued, then for a while the game makes craters disappear in two rounds instead of three.
Cannon Phase
The Cannon phase is much less tense than the others. You get ten seconds to place additional cannons for subsequent Battles. But placement of cannons is one of the most important decisions of all. In a sense, the reason you’re capturing castles, beyond mere survival, is to support your artillery.
For the first Cannon phase of the whole game, the game gives you three cannons to get you started. On the first Cannon phase after continuing, you get four, as part of the “and more firepower” the game promises. On the first round of other levels, you start with just two.
Beyond that, on each successive Cannon phase, you get two more cannons to place for having captured your home castle, and one more for each other castle. But this only happens if you have room to place them. When surrounding castles in the Building phase, you must not only survive, but try to leave extra room for placing cannons, that is, if you want more artillery.
The more cannons you have, the more shots you can get off in the Battle phase, and thus the more of a dent you can put into the enemy navy and/or other players’ walls. This, in turn, decreases the shots coming in towards your walls, lets you do something about Landers before they drop off Grunts, lets you shoot at Grunts directly, allows you to sink more Red Ships before they set your whole countryside ablaze, and ultimately depletes the opposing navy faster.
Lots of cannons mean lots of shots! Shots can stop landings, clear out Red Ships, and hasten the end of the level.
But cannons are also a big problem. Each cannon you place is a 2×2 square of ground that cannot be otherwise built upon, which restricts the shapes of pieces that can fit on the ground. Having lots of cannons progresses you through the level, but increases the area you have to surround to survive. Practically, you must build at least some cannons directly adjacent to your castle, and other cannons adjacent to those, in a big sulfuric blob. Thus, to capture that castle, you’ll also have to capture all the cannons that adjoin it, a mass of guns that grows in size with each round. And in case you come up with the idea to build cannons away from castles to avoid this, you should know that cannons that aren’t “owned” during a battle phase sit idle, doing nothing.
A “summer home” is a secondary castle you turn to in order to survive, usually with cannons attached, when your home castle is too difficult to recover.
You must have cannons to survive through each level, to punch back against the enemy, to take care of threats and eventually to advance towards finishing it, but having them makes later Building phases harder. Once a cannon is placed, it cannot be removed except by losing and continuing the game. And not having any cannons is a counter to using the “summer home” strategy for every round: while you can often abandon your home castle and its armaments in favor of a small unadorned dwelling out in the sticks, unless you’ve built cannons there on previous rounds, you’ll have, at most, one gun to thwart landings. A lot of games have ended due to this.
One subtle aspect to Rampart strategy is the cannon firing order. Cannons fire in the order in which they were placed. Any uncaptured cannons, and also cannons with shots in the air, are ignored in the queue. The difference in lead time between a cannon near the shore, and one way back at the screen edge, is significant, and can result in a lot of missed shots. To thwart this, it helps to try to build cannons in one mass, instead of spread out, and to try to build in more centralized locations, but truthfully it’s difficult to consciously make use of this strategy during a game.
This is a danger spot, a location where, if a single Red Cannonball hits, it renders the whole castle and its cannons impossible to capture.
One thing that players cannot afford to ignore is the danger of building cannons too close to the water or the edge of the screen. This is a huge concern. Building cannons close to hard barriers like those greatly reduces the number of pieces that will fit between the gun and the obstacle, and increases the chance that a red cannonball will hit in a such a place as to create an impossible rescue. To the game’s credit, Red Ships do not appear to target these locations intentionally, but neither do they avoid them, so It’s important to try to leave at least two spaces between cannons and any hard barriers, and more if you can. Especially look out for one-space diagonal separation, because it isn’t as obviously dangerous as horizontal or vertical. The more free space around your installations, the easier it’ll be to build walls there later, and the better off you’ll be.
So what if you decide you have enough cannons and don’t want to place some or all this round, do you have to sit and wait out the clock? Why, no: if you make five consecutive illegal cannon placements in a row, the game will take that as a signal that you’re done placing them and end the Cannon phase immediately.
That’s three parts so far! Yes, there’s more to say about this diabolical game, but we’ll take a break for a couple of days, for other posts. See you soon!
Sundry Sunday is our weekly feature of fun gaming culture finds and videos, from across the years and even decades.
Taking a short break form gushing over Atari Games’ Rampart to bring you this fun, short animation, by Only Jerry, set to the battle theme of the Japan-only PC Engine version of Wizardry. It’s only a minute or so, so please enjoy!
