NES Party and SNES Party are sites that do a think that would have seemed like magic 10 years ago: they make it easy to pick out NES and SNES games, load them into the browser from the Internet Archive, and not only let you play them yourself but share a room link with another person and enable internet-based multiplayer. It’s all as simple as that.
Well, mostly. When I tried using it, emulation was much faster than normal. The game load screen suggests, if this happen, that you reduce the refresh rate of your display, which seems like kind of a kludgy solution. But on the plus side, snes.party has Rampart!
Adobe (formerly Shockwave) Flash had a good long reign on the web as the premier means of presenting snappy interactive content without requiring repeated trips to the server. For ages, Javascript wouldn’t cut it for many purposes. Being tied to a full authoring environment helped it gain in popularity. Whole careers were built off of creating Flash content for the web.
Flash was easy enough to work in that many companies would produce Flash applets, even games, merely as promotional content, intended to be cheap and quick to make and ultimately disposable. Many of these games were lost when the websites they were a part of were taken down.
The Flashpoint Archive project, headed (I think) by BlueMaxima, has as its mission the preservation of these ephemeral creations. A post on Flashpoint will be coming eventually, but in the meantime I’d like to point out a 2021 Youtube video by (adjusts glasses) “Goober13md,” although I suspect that he may not actually be a medical doctor.
Goober13md’s beat is all things Monkey Ball. He made a video about the search for, and ultimate rediscovery, of three Flash games commissioned by Sega to promote the first Super Monkey Ball titles, as well as one for Super Monkey Ball Adventure (which Goober13md is understandably reluctant to mention by name). It’s an informative story about the difficulty of content preservation in a time, which is still ongoing might I add, where companies don’t see their web presences as anything more than transitory. Look look, see see!
In my teens I got started coding on my old Commodore 64s. Learning to program was a much different process back then, there was no internet to answer basically any question you’d have almost on a whim, everything I picked up came from some written matter, mostly programmer’s guides (including the definitive guide to using the hardware, the Programmer’s Reference Guide) or periodicals like Compute’s Gazette, Ahoy! and Commodore Magazine.
The C64 had a lot of graphics features, made possible by the machine’s powerful VIC-II chip. All of the home computers of the time had tricks one could use to get extra mileage out of their bespoke graphics hardware. The Atari 8-bit computers had display lists, for instance. The VIC-II had a powerful raster interrupt facility, the ability to share memory with the processor (at the cost of delaying the whole machine while it did so), eight surprisingly large hardware sprites (in double-width mode they could fill a whole scanline, something the NES’ sprites could only dream of doing), and a collection of interesting and flexible graphics modes.
Most of the time the C64 was in character mode, which was the standard kind of tile-based mode that pretty much all home computers at the time used by default, suitable for displaying messages, coding and some graphics. The ’64 three such modes: the standard mode where each character had a single color along with the screen-wide background color; a multicolor mode that gave a character its own color, up to two colors shared throughout the screen and that background color, and (mumble mumble). Sorry, what’d I say? I’ll get to that later.
The system also had two bitmapped modes that worked similarly, just directly viewing a region of memory instead of using each byte as an index into a character set. One mode was like the standard character mode, where the 1s in the bitmap were colored and the 0s were the background color; the other was multicolor mode, which similarly worked like it did in multicolor character mode: one color per 8×8 region, two colors shared throughout the screen, and the background color.
The problem with multicolor mode was, you had to trade horizontal resolution to use it. The big limiting factor to many computers’ graphics then was memory use: finding a way to encode the graphics information so the chip could access it and convert it into a video signal quickly enough to meet the needs of the display. So, to fit an 8-pixel-wide section of screen into the single byte it needed to be squeezed into, it could either use a one-to-one dot to screen ratio, or sacrifice two bits for one extra-wide pixel of up to four possible colors.
UNLESS
The Commodore 64 had a fifth graphics mode. The one I mumbled over earlier. The much-ignored Extended Background Color mode.
It was another character based mode that, instead of forcing you to make use of one background color over the whole screen, gave you up to four such colors. Every cell on the screen could display a character using its full 8×8 resolution, but could also pick which of those background colors it could have. Useful!
Well… not as useful as you’d think. There’s always a tradeoff, and Extended Background Color’s tradeoff was a dire one. How does the VIC-II chip know which background color to use for each character cell? It uses the two high-order bits of each character byte. Meaning, while you could decide which of two colors would be used in each cell with a lot greater nuance, you only had 64 characters to work with! A full screen of 1,000 characters is a lot to fill with just 64 possible tiles. A lot of repetition would be unavoidable, which is probably why it was so little-used.
It essentially was either this:
or this
These images are a little misleading, because I used the Commodore 64’s default ROM character set to make them, and the second half of its characters are just mirror images of the first half. But if you define your own characters, which basically any game worth its salt will do, it greatly reduces the number of tiles at your disposal. There may be some sneaky ways around it, sure, but they all involve their own tradeoffs.
I explain all this because Extended Background Color Mode is my best guess as to how Trap Door and Popeye do their graphics.
Here’s video of a playthrough of Popeye. It’s about 21 minutes, but it shouldn’t take long to get what I mean. It’s not Nintendo’s Popeye, it’s a completely different game.
And here’s a playthrough of Trap Door, with graphics by the same person:
Look at those huge characters! How could this be possible, and with that color depth? The C64 can have huge sprites, but only at the cost of making all their dots twice as tall and/or wide. And the pixels aren’t even multicolor mode wide. I can’t quite make sense out of it! Unless, maybe the games are displaying their large characters using the character set, which explains why they jerk along the screen? And the colors are using Extended Background Mode? That might explain the simplicity of the backgrounds, with only 64 characters to work with that means a lot of reused tiles.
This would ordinarily go into a Sundry Sunday post, but it’s interesting for historical value. Unlike the Switch’s spartan interface, the WiiU took some of its UI design inspiration from the 3DS, which was a bit more playful. The 3DS supported theming the main menu, which is a feature that never came to the WiiU, but they both did support StreetPass, with the WiiU still having its little-noticed StreetPass server settings among its rainbow-colored settings menu options. And of course both systems supported the Miiverse, Nintendo’s failed attempt at its own gaming-focused social media service, which let users make text and drawing posts, tied in with their Mii feature (still in the Switch although much declined in prominence), and allowed Nintendo to send users information directly to players. Miiverse is gone now, has been for years, but some people I hear are working on a fan-led revival. I shudder to think of what will get posted there without Nintendo’s moderators.
Back to the interface. Probably the quirkiest of Nintendo’s UI creations was an animation that went with the tool, downloaded fro the Wii’s Shop Channel, that transferred system and shop data from the Wii into an SD card package to be transferred to a fresh WiiU system. It could have been a simple progress bar, but they had their developers create a charming (gee I use that word a lot) sequence where Pikmin, at that point only those from the Pikmin 2 game that had last been seen on Gamecube, visually bundle up all of the transferable software, use a walkway to carry it into a waiting rocketship, and jet off to a nearby sun marked with the WiiU logo. At that point, the user would be prompted to move the SD card to the WiiU, where after installing a corresponding tool from the WiiU’s eShop, the process could continue, with a matching unloading animation.
If you never had the chance to see this sequence (easily possible given the WiiU’s low sales), or just want to relive the process, here it is, both of the Wii to WiiU data transfer animations, at about eight minutes:
This video only shows the animation. If you’d rather relive the whole process, including system menus, instructions and warning messages, here is a 15 minute video that records it. It also seems to have a couple of scenes that aren’t in the above video, including the one depicted in the head image.
A brief personal story. When the WiiU came out I got one. The WiiU’s fate was already sealed by that point, and I got it pretty cheap from a local Target. By that time my much-played Wii had been suffering from some serious issues. It had been hacked many times, the Homebrew Channel installed and its boot software replaced.
People will tell you that doing this is only for the purposes of piracy, and that’s really not true. We put the Wii to use as a general media player. It lived mostly at a friend’s house, and whenever I would go over we would use it to watch movies and things from SD cards. We even watched a DVD or two that way; while the Wii had a DVD drive installed, Nintendo didn’t spring for the licenses to play DVD movies, so it was purely intended as a data drive. You could bypass that restriction with the right homebrew software, although it wasn’t great and didn’t seem able to do menus, so we almost never used it.
My Wii had put into heavy use for game and media playing, and I put on and removed a lot of software over time, in addition of course to hacking it several times. As a result, it had gotten quite glitchy. Sometimes it wouldn’t boot, sometimes it would boot okay but wait until getting some ways into a game and freezing, and sometimes, weirdly, it’d show the opening Health warning screen, but the letters in the font would glitch out, individually. It was really a sight to see.
As a result I was really glad to get the saveable data off of that system and onto hardware that was reliable. I had to go through the whole sequence more than once, as the console froze along the way a time or two, but fortunately I got it, and our large Mii collection, all off and onto the WiiU, where it still lives today.
Collecting and saving Miis, from friends and the nearly-forgotten Check Mii Out Channel, and the Mii Parade of random Miis sent from Nintendo, is an aspect of the Wii that has not survived to the Switch. I hope whatever successor the Switch gets has something like it. And bring back StreetPass too!
The World Wide Web is now over thirty years old. In that time, more content has vanished from it than remains now, but some of it can still be dredged up from the shadowy archives of the Wayback Machine. This is the latest chapter in our never-ending search to find the cool gaming stuff that time forgot….
DHTML means “Dynamic Hypertext Markup Language.” The term is little-used now; it later got renamed AJAX, and now is pretty much just how websites are made if they have any interactive aspects. It was originally presented as an alternative to Flash applets, which were threatening to crowd out actual web pages at that time.
Lemmings, of course, is Psygnosis’ classic puzzle game where you grant members of a horde of suicidal rodent people specific skills to guide them to an exit while losing as few of them as possible to the hazards of their ridiculously dangerous world.
Back in 2004, DHTML Lemmings was a brilliant example of how much could be done with Javascript. Original Lemmings was released in 1991; we’re now further away from DHTML Lemming’s release than the original game was when it was published.
Its first home went away, although the server and even its page still exist. It says that the Lemmings page was taken down (and implies they did it to dodge legal liability), but promises something called The Pumpkins to replace it. It never did, but the promise survives. The game itself has been preserved, relocated as-was to a subpage of the site of Elizium, a dark rock band from the Netherlands.
Only the first ten levels of each difficulty, about one quarter of the original Amiga game, are presented. And this version has not survived the years unaltered: the distinctive sound effects and music appear to be missing. Still though, what’s here is playable, and fun. Enjoy, if you have the inclination and deliberation. And check out those requirements: IE 5.5 or better, or recent Firefox or Opera. And a 500 Mhz processor, wow!
ZoomZike on Youtube has been working for years on a comprehensive series of videos going through all the Mario Party games, and breaking down what parts of each are a matter of luck, and how many are of skill. Along the way, they also serve as fine guides to winning at them, at least as far as you are able.
They’ve gone through the series, trending longer with each one, for each game from Mario Party 1 through 7 (with an April Fool’s stop over at Advance). Even the shortest is at least an hour, and the most recent one is over five hours. That might seem like a whole lot, but imagine how long it took to construct! These are really deep videos, often with odds figured out through exhaustive, and exhausting, trial and error.
Mario Party 7 is the last of the four Mario Party games that came out for the Gamecube, even beating out the N64 portion of the series by one game. The early MPs were notorious controller destroyers, often resulting in the dreaded white dust of death, a result of ground plastic, emerging from the controller after heavy play. The Gamecube had controllers that weren’t as susceptible to wearing out, and so were better suited for the demanding play that Mario Party provides.
Anyway, here is the video, all five hours and 25 minutes of it:
On Romhack Thursdays, we bring you interesting finds from the world of game modifications.
It’s not easy to find romhacks that measure up to our exacting standards, that strike me in just “that way,” but a conversion of the NES Legend of Zelda, one of the few mainline Zeldas never to have been really remade in any form (unless you count the abandoned Satellaview versions), fits the bill like a duck in well-made dentures.
This screenshot may look nearly exactly like The Legend of Zelda. In fact it is the Legend of Zelda, just converted, nearly exactly, to the SNES.
Link doesn’t wait for the transition to finish to start climbing out of caves.
The question has to be asked: why? I mean, to a degree it is kind of pointless. There’s been nearly exact (although always unofficial) re-implementations of The Original The Legend of Zelda since Zelda Classic (Set Side B). All of Nintendo’s own rereleases, from Virtual Console to Gamecube bonus disks to a stand-alone Game & Watch unit. But recreating it on SNES does have certain uses. First, it fixes a handful of issues with the earlier game, notably it doesn’t have flicker or slowdown. It also uses the L and R buttons to allow for quick inventory cycling without having to go into the subscreen.
The colors are slightly better as well. And the top of the screen display labels the buttons Y and B, instead of B and A.
It speeds up game transitions: it uses the Link to the Past-style iris in and out effects, using the SNES’ display masking feature, instead of the slower curtain closes and opens from the NES version. It allows you to use custom soundtracks via MSU-1 support. Health refills instantly instead of pausing the game for up to 15 seconds while all your hearts load up with red. And the sound is very slightly different: by default the low-health beep is less insistent, there’s an extra sound when you kill an enemy, and the candle sound is a little higher in pitch.
But perhaps the best reason to convert it to the SNES is, SNES emulators are nearly as common as NES emulators. You can play this modestly improves version of LoZ on anything with an SNES emulator, which isn’t something you can say of Zelda Classic.
Yes, I used this hack as an excuse to play completely through the first quest again. And yes, I did it without dying. I still got it.
I’m kind of an outspoken fan of the original LoZ, I still think it’s well worth playing today, although I think you should seek out its manual should you do so. (The opening demo even tells you to look there for details!) You’ll die a lot, it’s true, but there’s little penalty for it except for going back to start or the beginning of a dungeon, and having to go refill your health before you try again. It takes real skill to weave around its fast-moving enemies and projectiles, but it’s doable, and you don’t need speedrun skillz to do it.
It is rather difficult to find it through search. It’s not on romhacking.net. Creator infidelity’s announcement was on Twitter, where he offered only a direct download.
The Suck Fairy is a mischievous spirit who visits the beloved properties of our youths so that when we return to them they’re much worse than they were when we first found them. That is surely the explanation; it’s not that we’re much more knowledgeable and mature readers/viewers/players now than back then. It can’t be that our horizons have expanded. It can’t be that the thing we liked back then was never really as good as we thought it was.
The Suck Fairy as a concept has been with us for a while now. I think it was introduced to the world in a September 2010 article on Tor.com by Jo Walton. There’s lots of weird concepts like that that litter internet culture (my favorite is the “Crazification Factor,” from a post on Kung Fu Monkey in 2005, long enough ago that its mention of Obama’s election refers to his Senate run), and sometimes we don’t even know the first time it arose.
Gek is maybe an odd choice for a visit from the Suck Fairy; surely, all of its suck was predispensed? But it was still beloved by some, many of them purchasers of the failed 3DO system on which it originated, one of those consoles with few games, and even fewer that could be called good. (The best, probably? Star Control II.)
The writer of this Destructoid article, still liked it for itself, but finds that it’s one of those games where context given by its manual kind of ruins the game’s premise by giving it an adverse context.
If you just play the game, Gex is a fairly shallow game about a lizard mascot character, in sunglasses no less, romping through a series of worlds based on media properties, uttering trite digitized quotes at various times.
If you read the manual, you find out that Gex is wallowing in sorrow! His dad was an astrogecko working for NASA! He lost his life in a terrible accident! Gex, unable to face the world, retreated into television! It’s the only way he can handle living! And, although Gex thwarts the villain’s plot to use him as a mascot character (a thing he already is really), nothing at the end of the game indicates that his mental state has changed.
The first of six manual pages that lays out the reason for Gex’s media obsession.
I think the writer may be overthinking things a bit. Often manual stories were written as an afterthought by people who had nothing to do with the making of the game. Have you ever seen the manual for the NES release of Konami’s Life Force? It claims that the evil gigantic space creature Zelos, huge enough to devour planets, was the proud offspring of alien beings named “Ma and Pa Deltoid.” The manual for NES Metal Gear claims that the villain wasn’t Big Boss but instead “Colonel Vermon CaTaffy.”
From the recent trove of preserved video from Noclip Game History Archive, here’s a look through Nintendo Of America’s internal employee-only museum/store, circa 2006, on Youtube. There is very little sound in the footage, so you might want to increase the playback speed to double.
For context, it was near the end of the Gamecube’s life, immediately before the release of the Wii, and the early years of the Nintendo DS. Objects glimpsed during the stroll include various consoles, records of Nintendo’s collaboration with the Starlight Children’s Foundation, Pokemon merchandise, Nintendo awards, some arcade units (including a glitched Mario Bros. cabinet), a Virtual Boy, various character statuettes, old playing cards, a capsule timeline of Nintendo history, and various games for sale at the time. It seems that the museum also functions as a retail space for employees.
Sundry Sunday is our weekly feature of fun gaming culture finds and videos, from across the years and even decades.
I’ll admit it, there’s this cable that goes into my brain directly from Youtube, and I use it to cut the number of game-related things I have to post daily on this site by a full seventh. I know you all suspected it, I’m just confirmin’ it. I’m like a vermin, for confirmin’. I’m a squirmin’ vermin for confirmin’! In German! No, no let’s not write Shecks my language skills cannot kassieren.
Record scratch you know who does fun cartoons sometimes? Doobus Goobus. Like that other person, Pringus McDingus. I’d understand if you mixed them up from their names. But DooGoo posts more often, and longer things! Just a little less polished. Pringus has a really appealing art style, while Doobus traffics in the internet’s default art style: purposefully ugly. Nothing against that as a style, just calling a misshappen spade that thing that it is.
The requisite preamble now complete, please enjoy five Sonic the Hedgehog characters using profanity at each other in an entertaining manner.
Last year we put a spotlight on a Commodore 64 remake of possibly the most popular Odyssey2 game, K.C. Munchkin. Well, here’s another, of Space Monster, a.k.a. Alien Invaders – Plus! I assure you, the exclamation point there belongs to Magnavox.
The Odyssey has gotten more talk on this site than its much-more-powerful successor, which was still kinda weak compared to its competition. People still talk about the Atari VCS/2600 even now 45 years after its introduction; the Intellivision still gets some love; but who talks about the third place system, the Odyssey2? Fourth if you count the Colecovision, but that machine, released in August 1982, was only on the scene for a relative instant, the Crash already fomenting by that time.
Alien Invaders – Plus (I’m going to leave off the bang now thanks) was Magnavox’s attempt to capitalize on the gigantic success of Space Invaders. The box didn’t hide its inspiration, outright saying: A fiendish new dimension comes to one of the most popular arcade games of all time! By that time, the market had already determined that Atari’s miraculous licensed version of Space Invaders was probably the best, a game that, while subtly different, actually improved on the original in some ways. Similarly, while everyone now can play the original Space Invaders in MAME if they’re inclined, Alien Invaders – Plus (which Craig Kubey in The Winner’s Book of Video Games derided as Space Invaders – Minus!) is more interesting for the interesting departures from the arcade game, and the Commodore 64 remake mimics them faithfully.
At first it looks vaguely similar to Taito’s arcade hit. There’s rows of aliens in the sky, there’s a roundish alien going back and forth above them, you have a base at the bottom that can move back and forth and shoot up at the enemy, and there’s even shields above it that can be dodged behind for safety.
Loading screen for C64 version of Alien Invaders Plus.
The first difference comes from the aliens themselves. In Space Invaders, while they looked different and were worth different amounts of points, they all behaved exactly the same. Here, each of the three rows of foes plays by different rules. The bottom-most are just barriers, they can’t be destroyed but they don’t shoot at you either. Any shot that hopes to hit targets higher up on the screen must get through them. The middle row are yellow laser cannons, and they shoot down at you. The top row are red humanoid robots that operate the cannons. The wandering eye-like alien at the top is called the “Merciless Monstroth,” but I’m sure its mother loves it just the same.
Like Space Invaders, the alien formation rains down bombs on you, and it’s easy to get hit. Unlike Space Invaders, there’s a limit to how far the aliens can descend, right above the shields, and you’ve never in danger of being overrun. If you wait beneath a shield you cannot be shot, but neither can you shoot the enemies. Also, in each row, all you have to do is hit either the robot or the cannon in order to stop them from shooting down at you.
To finish a level, you have to shoot all the robots and cannons on the screen. This will cause the Merciless Monstroth to get serious about you, swoop down from the top of the screen and hover just above your shields, trying to bomb you. At that range dodging its shots is very difficult, and it’s evasive of your shots, but you can still zap it safely with a well-timed shot as it reaches your base’s horizontal position.
Your reward for doing all of that is one single point. Your score is just how many boards you’ve cleared. No bonus points or anything like that are awarded.
If your ship gets hit you don’t perish immediately. A little person is revealed to have been moving it. If you can move it to beneath one of your shields and press the fire button, you’ll be given a new base! This, however, costs you that shield. The shields are basically your lives; if you run out of them, and your base gets destroyed again leaving your guy, then you’re essentially screwed. Your little base-inhabiting person has no weapons of their own. If you get down to no shields left before destroying all the aliens, M.M. will sense its opportunity and swoop down at you early. Destroying it at this time, or while its at the top of the screen, before all the other aliens are obliterated doesn’t clear the wave; the game will just send another one out, again and again, until you’ve finished the job.
If your base person is shot while outside of a base, you don’t quite die. Instead, the enemy gets a point. While you’re trying to get to ten points yourself, the enemy is also trying to get to 10, and the side that gets there first “wins the game.”
Despite all the chances the game gives you, it’s really hard! You’ll find the green circles block most of your shots, and the cannons are really good at predicting where you’ll be and aiming a shot there, and the enemy shots move quickly. Since reforming your base costs you the shield you’re beneath, often you’ll get your base back and lose it again immediately as the barrier disappears.
The Commodore version was created by demo group Second Dimension. It’s worth playing in preference to the Odyssey2 version if only because C64 emulation is understood than Odyssey2 emulation. There’s multiple Commodore emulators, at least, while only one Odyssey2 emulator that I know of.
Here is the Commodore 64 version is action, from the channel C64 Masters on Youtube.
Displaced Gamers‘ Behind the Code series doesn’t get new videos often, but they’re always great. This one is more technical than usual, but I don’t think it’s really all that technical. It’s about how the NES processes and renders its sprites, particularly explains why there’s a eight sprite per scanline limit, and even reveals a couple of games that use that limit to produce special effects!
The gist: while each scanline is being prepared for display, the NES’ PPU looks through the entries for the machine’s 64 hardware sprites in order, finds the first eight that will display on the current line, and copies their attribute data to a small area of internal RAM. There is only space there for eight sprites, so, the NES cannot display more than eight sprites in a single scan line. Any later sprites in the primary attribute data won’t have room to be copied, and so the PPU won’t be able to display them.
One thing it notably doesn’t cover, however, is how games implement priority shuffling to cause sprites to flicker instead of not display at all. The video suggests that that might be coming in a future video….
