I have a history of letting small commitments snowball into massive undertakings. OH JOES! was a 2-month project that took 2 years. My YouTube playthroughs of the NES Mega Man games were a 3-week project that took 3 years. More recently, Make a Good 48 Hour Mega Man Level (MaG48MML for short) was a 2-day project that has lasted over 3 years and counting.

MaG48HMML (48H for short) was conceived as a shakedown cruise for Megamix Engine, the game engine that would be the basis for the larger and more involved Make a Good Mega Man Level 3 (MaGMML3 for short). The plan was to hold a small level design contest during the summer of 2018, get the levels judged quickly, and crank out a simple game showcasing those levels. When submissions for MaGMML3 opened in the fall, the judge feedback and technical improvements from 48H would help participants make better levels. I was already a judge and devteam member for MaGMML3; I had no time or intention to get involved with 48H beyond submitting a level.

However, those plans fell apart. 48H attracted more contestants than MaGMML1 and 2 combined, the levels took years to judge (well overshooting the submission period for MaGMML3), and the final game was hardly simple. I became massively involved: I wrote ~75% of the non-cutscene dialogue; designed a weapon tutorial and a section of the fortress; provided extensive playtesting and proofreading; fixed (or attempted to fix) numerous glitches; made corrections or modifications to several art assets; programmed more things than I thought I was capable of, including what is arguably the biggest Easter egg of the game; conceived or helped plan countless major and minor aspects of the game; wrote copy, edited judge bios, commissioned artwork, and hosted downloads for the website; and helped revive the project when it was nearly dead—twice.

Also, I submitted a level.

Several weeks before the contest opened, I discovered that I had been added to the 48H devteam chat on Discord. I hadn't requested a devteam role, no one had asked me whether I was interested, and I knew basically nothing about the project. I didn't even have an official role; "any help you wanna offer would be appreciated" was the direction I got. I now appreciate what it's like to be a summoned monster in a Final Fantasy game. As long as I didn't have to do anything, I had no problem being on the devteam to discuss ideas. I spent enough time on Discord already; what difference would one more channel make?

The rapid-fire conversations that transpired over the next month were riotously funny, and they shaped the foundation of the game. Almost nothing had been planned at that point, aside from the premise of giving contestants mystery boxes full of randomized assets with which to build a level in 48 hours, and we had a field day shouting out ridiculous ideas that somehow stuck. Of course, several ideas didn't stick (aimable Spark Shock, a Wily Assist weapon that shoots out a flustered-looking Dr. Wily at a 90-degree angle, GIANT CARDBOARD BOX WILY MACHINE - FOR PHASE 2 HE UNFOLDS IT), but the ones that did stick were agreed upon quickly and amicably.

Mega Man wins a free cruise, but it's secretly a distraction so Dr. Wily can do evil deeds without Mega Man coming after him! (Unanimous agreement.) Let's name the ship the Elroy, after MaGMML community member Cruise Elroy! (Unanimous agreement.) Actually, forget Wily; the villain should be box-themed! (Dissenting suggestions of Crystal Man from Mega Man 5 embezzling money from Wily, then Clock Men from Challenger From the Future, then these characters as part of a series of fakeouts leading to the real villain). The single absolute worst level should be on some dingy old raft floating behind the cruise liner, circled by sharks! (This elicited a "lmao".) Even in their rawest state, our ideas weren't too far off from their final form.

Before long, we started discussing the contest rules. As a judge for MaGMML3, a soon-to-be contestant for 48H, and a professional editor, I felt a strong obligation to ensure the rules were as clear and comprehensive as possible. I volunteered to copyedit the rules document, which soon turned into me taking the lead on incorporating feedback and finalizing the rules. Once that was squared away, the contest opened and I got to work on my level. Regrettably, I forgot to pencil in a rule mandating that I win the contest, but that's hindsight for you.

To make the most of my 48 hours, I requested my mystery box on a Friday night after dinner. I had nothing planned for the weekend, I was in good health and good spirits, and I had a few friends on standby for playtesting. Conditions were perfect. My plan was to stick with the first box I was given (unless it was utterly unusable), wait to see what I got before starting work on the level (I felt like planning the architecture and aesthetics in advance was against the spirit of the contest), and craft a "normal" level that might feel at home in an official Mega Man game (not too long, not too wacky).

It was more like a 30-hour level, really. I slept at least 6 hours a night, lost 20-30 minutes every time I compiled a test build, was waylaid by a series of asset issues (eg, monkeys falling through floors) that required devteam intervention, and spent entirely too long futzing with a laser gimmick that was long on possibilities and short on documentation. I also didn't count on how long I'd spend trying to get Rain Flush to block lasers (to no avail); getting the volume balance and loop point right on the music; and fine-tuning so many precision-oriented puzzles that were fine on paper but messy in practice, due to the nature of the assets involved. Fortunately, the nature-themed enemies and military-themed gimmicks made it easy to decide on an overall visual theme; and it took no time at all to pick Dyna Man as the boss, given how well his vaguely military aesthetic, incessant hopping, and use of explosives fit with the rest of the level.

There's plenty more I could say here, but in light of everything else, my participation as a contestant is almost insignificant. Those 48 hours were fun and memorable for me, and I'm proud of what I accomplished in that time, but my level is 3 minutes of entertainment in a game that takes upward of 20 hours to complete. My level came in 18th place, neither anyone's favorite nor anyone's least favorite, not sufficiently noteworthy or contentious for people to ever bring it up in conversation—except to comment on the music. The real legacy of "Base in the Boondocks" is bringing "Portrait of a Ghost Ship" from Castlevania: Rondo of Blood to the 48H jukebox and inspiring one question for the music trivia sidequest.

After submitting my level, I stuck around the Discord server for another 8 months. I provided advice and playtesting for other entrants during the rest of the entry period, and I continued to weigh in on devteam matters, but planning discussions soon began to taper off. By the end of March 2019, I was so busy judging for MaGMML3 and so little was happening with 48H that I decided to leave the server, with a standing offer to return if anyone ever needed me for anything specific.

Ten months later, I reached out to ParmaJon, the contest host, to see if I could help out with anything for 48H—hub design, NPC dialogue, etc. I was nearly finished with judging for MaGMML3, so I figured I could spare some time to help push 48H along to the finish line. The answer was yes, so I rejoined the server and started skimming through devchat to get caught up.

48H was in almost exactly the same place I had left it.

Granted, one judge had almost finished judging, and another was relatively close behind. Planning had begun on the weapon tutorials, some important technical stuff had happened with the game engine, the map function was being developed, and a couple tier hubs were in the preliminary stage of design. There had been some changes to the composition of the devteam, too. But we're talking about a game whose main content was thrown together 18 months ago in the span of two days, and we still didn't have screenshots to put on the website. From the perspective of anyone on the outside, 48H was dead in the water.

Perhaps more accurately, 48H was rudderless and functioning with a skeleton crew. ParmaJon was a judge as well as the contest host, and judging was drawing focus from leading the project. Any planning that had been done was scattered across multiple Discord conversations and Google Docs. Several devteam members were simultaneously working on MaGMML: Episode Zero, which was nearing completion, and/or MaGMML3, which was still very much in progress. In short, hardly anyone was available to work on the game, and hardly anyone knew what to work on in the first place.

With ParmaJon's blessing, I started developing a master design document, pulling together everything that had already been planned or discussed and filling in any gaps with my own suggestions. (I've saved a copy here, if you're interested.) I also suggested that we designate someone to make day-to-day decisions in ParmaJon's stead. It took two weeks for us to iron out the design document and less than a day to get CSketch on board as game design lead.

Suddenly, 48H was back on course. Devchat was more active than it had been since the contest closed, and the project felt exciting and relevant again. Although a few of my favorite ideas from the design document didn't make it into the final game (namely, Mega Man's cabin being like the Sky Room from Command Mission, and BomBoy from the Battle Network games running a mystery box shop), I wasn't precious about my suggestions. The purpose of the design document was to organize past discussions, spark new discussions, and give us concrete tasks to work on, and that's exactly what it did.

Around that same time, I got a copy of the judge EXE and played through all the entry levels. If I was going to be involved in planning the game, it behooved me to know what the bulk of the game was going to be like.

It was going to be terrible.

In their submitted state, without Skip Teleporters or Beat or anything else that the final game offers to mitigate the difficulty, the entry levels were torturous. I could count on two, maybe three hands the number of levels I genuinely enjoyed. 48H's tight time limit amplified some of the pitfalls of amateur (and even professional) level design that annoy me most, and it didn't help that I was already pretty burned out on Mega Man after judging 170-odd levels for MaGMML3. Consequently, I was very vocal in devchat about introducing features that would sand off the rough edges and balance the difficulty of the entry levels.

One such feature, which we were already working on, was a series of weapon tutorials. What better way to give players an advantage than to help them fully understand the tools at their disposal? I called dibs on the tutorial for Homing Sniper—I had some ideas about how to elevate the training to something more than "mash the attack button to win"—and I made it a point to playtest all of the other tutorials as well. Aside from participating in all the usual devteam discussions (which now concerned the Box Cartel fights, possible postgame content, and whether to let players unlock extra checkpoints), my focus was entirely on the weapon tutorials during this period; everything else seemed to be under control and moving smoothly.

Once again, I decided to hang around the server for about 8 months (until mid-October 2020) before taking my leave. All the weapon tutorials were finished or just required finishing touches, and there wasn't really anything else I could help with. I was trying to cut back on Discord use and focus back on MaGMML3 as well. As before, I left an open invitation to call me back to the devteam if I could help with anything else in the future.

When I checked in with ParmaJon and CSketch a month later, it sounded like the game was almost finished, aside from judging. The devteam really only needed help with graphics and programming—two things that were best left to the experts. The only thing left that suited my skill set was NPC dialogue. It was still too early to start writing anything, but I could at least do some prep work.

Knowing that most of the NPCs were going to be regular stage enemies, I set up a sprawling spreadsheet so we could keep track of which NPCs were available, where in the game we wanted to put them, whether we needed to create custom sprites for them, and any notes or suggestions. By the time I was done trawling through the enemy/miniboss lists of every Mega Man game we were likely to pull from, there were well over 500 NPCs on the list, not to mention Duo, Reggae, and several other named characters who might show up. I even included Daidine, a spinning platform from Mega Man 5, because "The fact that this spinning platform has an actual name makes me want it to be able to talk".

Another month went by before I formally rejoined the team—not to write NPC dialogue, but to help design a section of the fortress at the end of the game. It's MaGMML tradition for each judge to make their own fortress level, but only ParmaJon was in a position to do so, and in a limited capacity at that. It fell to CSketch to design the first fortress level and co-design the second with ParmaJon. The third and final level was an independently collaborative effort involving the entire devteam, meaning that we all got to create our segments in isolation before smashing them together.

To start creating our segments, we selected one of the unused mystery boxes from the entry period—I picked mine at random from the master spreadsheet, but others chose the specific one they wanted. As development progressed, I started noticing a fair amount of overlap in the assets we all were using for our segments. In the interest of showcasing a wider variety of assets (and giving players a reprieve from too many segments where they were required to shoot the terrain), I set up a spreadsheet so we could keep track of our progress and which assets were used in which segments. I threw out my box and rerolled until I got something novel that I could work with.

First reroll: "Your choice of a destructible block". Pfft. I was trying to avoid shooting the terrain. Next.

Second reroll: Venus Waterfall Spawner. Ah yes. The janky gimmick that had become a running joke, on account of it showing up in an alarmingly high number of boxes and being the bane of the programmers' existence. NEXT.

Third reroll: Wave Man Jet Ski, Cricket, Bikky Bomb, Tamp, Nombrellan. I could work with this. And so I did.

Development of our so-called Final Box levels was slow but steady. I provided as much feedback on everyone else's levels as possible, going so far as to fire up Mega Man V for Game Boy and thoroughly examine the physics of the bubble floor gimmick, which was implemented differently in Megamix and causing playability issues. By the beginning of February 2021, my Final Box level was finalized. Two months later, I hadn't started any new projects, and I was having second thoughts about sticking around for that other thing I had offered to do.

"If we need dialogue for any of the weapon tutorials, I can help with that," I wrote. "If we reeeeeally need help with other NPC dialogue, I'll consider it, but I had previously mentioned the possibility of un-volunteering myself if we had enough people to cover everything. I'm not as confident in my ability to write snappy dialogue for random NPCs, and it's been very challenging lately to work up the energy to get back to my creative projects. But if it's the difference between the game launching on time and the game dragging on even longer, I can give it a shot."

After a little bit of discussion with the devteam and with my wife, I was persuaded to try my hand at NPC dialogue after all. Nothing had been written outside of the weapon tutorials, so I had my pick of every tier in the game. I started with Tier 5, the minigolf course—I enjoy minigolf and had been watching a lot of Holey Moley at the time, so that was the natural first choice. It took me all of four days to pick out and arrange the NPCs, write dialogue for them, and implement their sprites.

A little over a week later, I was ready to mute the 48H server and get back to working on MaGMML3 unless someone pinged me for something. Any last requests before I disappear again? Well...okay. I guess I can write a little more dialogue.

I gave the devteam a few options and let them decide which tier I should do next. They chose Tier 3, the dining hall, which was perfect because I love talking about food. This one took longer—slightly under a month—in part because I got a little more ambitious and asked for both programming help (for the Hologran gag) and custom NPC sprites for a few enemies from Mega Man 7 and 11 who needed to be redrawn in an 8-bit style.

Afterward, I announced that I had it in me to do one more tier. I went with Tier 9, the ice skating rink. I love ice and snow aesthetics; figure skating is one of my favorite sports to watch; and I thought it'd be good to break up my tier claims so that if someone didn't like my writing style, they weren't stuck with me for multiple tiers in a row. I started work toward the end of May but didn't finish until early July, due to life craziness and some unexpected graphical and programming needs.

As my work on Tier 9 was nearing completion, I realized I had finally hit my writing stride. I could probably manage one more tier, if not a few more tiers; despite how exhausted I was from multiple multi-year Mega Man projects, I was having fun. However, I wanted to balance "helping finish the game" with "hogging all the fun stuff," so I asked the devteam about who else actually had an inclination to write NPC dialogue. Half a dozen people were interested, but burnout and busyness were very apparent. Spade_Magnes was working on Tier 6 (ballroom) and had finished Tier 2 (cargo hold) after picking it up from snoruntpyro. The main deck and passenger cabins were at least partially reserved for CSketch and snoruntpyro. Otherwise, everything was up for grabs, and it really didn't matter who took what. We all just wanted to get the game out the door.

Spin Attaxx claimed Tier 10 (water park), and I put Tier 8 (library) and Tier 4 (engine room) in the queue for myself. My plan was to keep churning out NPCs until we ran out of tiers or someone told me to stop, whichever happened first. Tier 8 took me only three or four days, and I knocked out Tier 4 in a single weekend. I was bolstered by positive feedback from the team; they seemed to like what I was doing with the NPCs, and any critiques were basically always constructive and beneficial. This part of development was easily my favorite: the project had a sense of momentum; I was fully in my comfort zone; and I felt good about what I was doing, because of both personal satisfaction with my work and recognition from the devteam.

My next claim was Tier 1 (lifeboats), which was a one-day project. As with all the tiers, however, I would go back later to finesse the placement and creation code of the NPCs and polish the dialogue. Tier 1 was attached to the main hub, which was being updated frequently for one reason or another, so I had to make sure no one else was working on that Room file in GameMaker Studio when I was. The last thing I wanted was having my local changes overwritten in a dreaded merge conflict when pushing my work back to the master file, so I suggested we implement a system where anyone who wanted to work on the main hub had to announce it first, in case anyone had unpushed changes. This system mostly worked.

Now that I was mucking about in the main hub, I started thinking about what players' first impressions of 48H would be. After the intro cutscene, you step onto the deck of a gigantic cruise ship and have free reign to explore. Where do you start? Is the ship easy to navigate? What areas might you overlook? Player experience had already been on my mind (see: the Giant Telly in Tier 3 who checks in on your emotional state after playing "Megatroid", the Puyoyon in Tier 4 who subtly reminds you to visit the costume shop on your way out, all the NPCs in Tier 1 who try to prepare you for the disasters you're about to deal with), but this is where I started taking on focused projects to make the game more player-friendly.

We had discussed adding some info-oriented NPCs, so I created Iota to explain what 48H was all about, a Jamacy in Tier 2 to warn players about a level with broken ladders, and multiple NPCs to guide players around the ship. I created a Junk Golem NPC to provide hints about where to find new sidequests and how to complete them. To make the main deck less overwhelming to new players, I followed through on a plan to lock some of the cabin doors until later in the game.

Because ParmaJon didn't want a traditional shop, players needed ways to stock up on E/W/M-Tanks that didn't involve grinding in the entry levels. I added an emergency M-Tank dispenser to ensure players wouldn't get stuck on the Box Cartel fights, when the entry levels are blocked off. I also created a Mad Grinder who would supply free E-Tanks and W-Tanks based on sidequest progress and Energy Element collection, respectively. It's all too easy to chug E-Tanks instead of applying actual strategy, so I wanted to encourage players to try special weapons, pursue sidequests (and their rewards), and not get hung up on any one level in the early game, and then to shower them with tanks in time for the endgame and postgame.

Furthermore, I suggested we reinforce Joseph's explanation of Junk by stationing an NPC outside his cabin who would give you Junk to trade in. I also argued strongly against starting the game with a mandatory scavenger hunt to find Beat before accessing the levels; to me, that felt like a contrived and needlessly restrictive way of ensuring players would explore the ship and obtain a special weapon that the levels weren't designed around. Although I was overruled both times, I found other ways to influence the player experience. For the Beat search in particular, I moved the invisible barriers to more organic locations, and I revised the generic "I shouldn't go that way" message to a fairly blunt reminder/hint about what you should be doing.

I was more successful about suggesting changes to the sidequests, which were being developed relatively quietly—I didn't know they existed until May 2021, and there weren't any real opportunities to get involved with them until July. After I tried out the music quiz for Funky Fresh Beats, I pushed to include a screenshot with each question, to make the sidequest accessible to deaf players and to anyone playing with the volume off. Because screenshots were too much of a hassle to implement, we agreed on text hints, which I wrote. I also made a few suggestions that stuck for the Mutual Attraction and Poltergeist quests; for the latter, I even recolored the ghost sprite (being obligated to use a canonical color for the Rotom Pokémon it was based on) so that it wouldn't blend in with the background as much.

Love Survivor was the sidequest I influenced most. For a very long time, the cruise ship was going to have a casino, either as the location for Tier 7 or as a standalone area (in the space that the Kickboxing Club now occupies) with minigames to play. The original premise for sidequest, then dubbed "Red or Yellow", was to help fashion boutique co-proprietor Bol'o raise money to pay off an enormous debt to a mafioso called Don Loath (a tip of the hat to Lex Loath from The Misadventures of Tron Bonne). Doing so would require cheating at a casino game where the objective was to guess whether a light would turn red or yellow (an inside joke apparently inspired by a Vinesauce video poking fun at a game called Color Fun).

The casino was scrapped in January 2021 to reduce the devteam's workload, and it was several months before we discussed relocating and redesigning the sidequest. Tier 3 (dining hall) had some unused space that was inaccessible to the player, which could easily be remodeled to accommodate a quest. This inspired me to outline a new quest, which made it into the final game with only one change: Don Loath (who never even received a character design) became Master Reddorgold (whose name is not a reference to "Reddit Gold", but rather a nod to the sidequest's original title). A kitchen stealth mission wasn't my only suggestion, though; I also pitched a Donkey Kong Country–inspired level using dining carts in place of mine carts.

A week later, I formally committed to writing all remaining NPC dialogue in the game. I was the only person adding to the main hub, several passenger cabins were still vacant with nothing planned, and nobody else had claimed Tier 7 (art gallery) or Tier 11 (sky deck). I was least enthusiastic about Tier 7 and had been hoping someone else would take it, though. The tileset contained sculptures and paintings (by eviemaybe and Protty) that I wanted to acknowledge in the dialogue—except half of them referenced things I didn't recognize, and by that point it was taking all my brainpower to write what I knew, let alone what I didn't know. And there was a major deadline approaching: first test build of the whole game for our internal playtesters.

I had about one week to power through Tier 7 and add as many NPCs as possible to the main hub and cabins. Nothing said I had to rush, but the longer it took me to get my work loaded into a test build, the less likely it was that people would see it. This was especially relevant for the deck and cabin NPCs whose purpose was to guide the player. Tier 11 was still in the process of being tiled, so I didn't even bother with that one yet. I'm not entirely satisfied with the dialogue I produced during this time, but "not entirely satisfied" was to become my mantra for the duration of the crunch leading up to the game's initial public release.

By the beginning of August 2021, new playtesting builds were being released about once or twice a week (soon to become once a day), a release trailer was in development, and I was rapidly running out of time to finish everything on my to-do list. The team wanted to ensure a summer release, given the cruise ship theme. Summer, as I pointed out, would last until September 22. They wanted it by the end of August—when I would be unavailable for several days. Eventually we settled on end of August as our internal deadline, with a few days of buffer before the release date of September 4 that was ultimately announced to the public.

My eagerness to get this project out the door had finally caught up with me. Leading up to the crunch, I kept taking on small assignments to ease the burden of more specialized team members. The artists were busy, so I cleaned up the subtle color inconsistencies between the special weapon icons, and then loaded them into a tileset so I could add them above the weapon tutorial teleporters. The programmers were busy, so as much as possible, I tried to figure out how to code complex NPC behavior for myself. I was already spending all my free time on 48H before the deadline was announced; the only way I could crunch any harder was to start sacrificing sleep, aspirations, and quality—and I won't even go into the Big Life Stuff that started vying for my time. The weeks leading up to release were physically, mentally, and emotionally brutal, and they turned my experience with 48H extremely sour.

My key mistake was not communicating to the team just how much I actually had planned for the initial release. I wanted to bring my perspectives as a professional editor, MaGMML3 judge, and fangame designer to the parts of the game I hadn't yet seen. I kept coming back to seemingly finished projects to polish things up and incorporate playtester feedback. I was still working on NPCs for the main hub and cabins, but because I had added any NPCs in the first place, people assumed I was done already. I hadn't even started on Tier 11, which would end up taking over two weeks to finish. And that's to say nothing of all the Easter eggs I was working on, or the Butt Mode cheat that I got involved with at the last minute.

As we entered September, mere days away from release, show-stopping technical issues began to arise. A key devteam member's computer died at an incredibly inopportune time. We kept discovering game-breaking issues and applying fixes that we didn't have time to properly playtest. The only person who could set up the online leaderboards on our usual server was unexpectedly unavailable. On top of that, a couple sidequests and noteworthy cheats were still being developed, and I still had a lengthy to-do list. No way was this game getting done on time.

By September 1, the devteam was discussing the possibility of delaying the release. By September 3—late enough in the day that it was already release day in certain time zones—we came to an agreement that a delay was necessary; the question was, how long? A few devteam members—myself included—voted for "until it's ready", but the final decision was to not keep the public waiting, saving any nonessentials (which included most of my to-do list) for an eventual patch. Release was pushed from September 4 to September 6, just long enough to lock down the most pressing technical issues.

As the guy in charge of the MaGMML website, I did as much as I could to prepare in advance for release day, such as gradually adding screenshots to what would become the download page. As soon as the judge scores were finalized, I commissioned Phusion—who did website art for MaGMML1, 2, and 24H as well as intro cutscene art for OH JOES! and MaGMML1 Remastered—to once again create art celebrating the first-place level for the download page. Once the story was fully locked down and we knew exactly what features the game would have, I wrote copy for the download page for the devteam to review. By release day, all we really needed were download links and one final sanity check before going live.

Release day was hectic and exhausting, owing to miscellaneous setbacks and delays. After the download page went live, I waited just long enough to confirm that there were no immediate issues with the download links or the game itself, and then I dropped off the face of the planet for the rest of the day. While other devteam members were celebrating, I was taking all the time I could to decompress and recharge before getting back to work. For me, the crunch wasn't over.

Given the general public's tendency to quickly find ways to break a brand-new game, I correctly guessed that we'd need to release a patch to 1.01 almost immediately, and then another small patch to 1.02 within a few days. If I acted quickly enough, anything I had planned for initial release could still be a part of people's first experiences with the game. After that, there was no telling how often we'd release additional patches, if at all, so it behooved me to get everything done ASAP.

While I labored away at the rest of my to-do list, I checked in regularly to see what people in the MaGMML Discord server were saying about 48H. Compared with the initial public response to OH JOES!, it was a joy to discover that all my time and effort had apparently paid off. People were sharing screenshots of NPCs I made that they liked, posting video playthroughs containing positive feedback about my design contributions, and talking favorably about the game as a whole...at least, until they started discovering the sidequests.

"Where is Tomothy Daddy?" "What other level is spicy?" These kinds of questions started dominating the chat, and I had no idea what they meant. When I wrote the Junk Golem's sidequest hints, I often had to go off of secondhand information from the devteam and an outdated sidequest planning document; I had yet to play many of the quests for myself. A few days after release, I started playing through all 16 sidequests, and suddenly my priorities shifted. After playing Credit Where It's Due, a tricky scavenger hunt, it was clear to me that players needed more hints, better hints, and reminders of critical information that was given once and never repeated—and they needed them now.

Unbeknownst to me, the day I played Credit Where It's Due was the same day version 1.02 was slated to be released. After outlining my proposed changes to the devteam, I scrambled to implement them—the team wasn't expecting to address any scavenger hunt complaints until version 1.1, but they were happy to include my edits in this patch if I could finish in the next hour or two. The dialogue that I hammered out is serviceable, but there's minimal personality and no humor to it. The patch went live shortly after I pushed my changes, and I haven't heard a single question about Tomothy Daddy since.

Most of the team basically went on break after version 1.02. I kept crunching. I devoted almost every free minute of an entire weekend to Goody Two Shoes, a riddle-based scavenger hunt, first playing through it (which was exhausting) and then planning and implementing a complex network of hints and reminders about where to go next (which was beyond exhausting). I had to dig into the code to understand how each step of the quest was triggered, figure out which NPCs would supply hints, write appropriate hints for each step, program the hints to only show up at the right time, and then test all of that. I also tidied the existing dialogue for the quest and fixed up the black splotches that lead you to your destination—in "Running Down a Drain", for example, the trail inexplicably went cold for several screens, as though you overshot the target.

I pushed my changes on September 19, just over a week after 1.02 was released. Although I loosened my pace a little bit, I stayed focused on getting through the rest of my to-do list as fast as reasonably possible. I scrapped a few ideas that I was now too tired to bother with, touched up the weapon tutorials, added new NPCs and tinkered with old ones, implemented cabin numbers to help players navigate the main hub, and refined/expanded the Butt Mode script.

The farther we got from the release of 1.02, the more the 48H devteam server felt like a ghost ship. People were burned out, busy with other things, or no longer checking in because their obligations to the project had been fulfilled. A few others were working on updates alongside me, but by the end of November, it started to feel like the project was adrift again. I prodded CSketch for a time frame until the next patch, and that set into motion a flurry of activity, which ultimately led to me taking the lead on a couple rounds of targeted playtesting and getting the updated game ready for public release. Version 1.1 went live on December 18, 2021—which means we had been sitting on my changes to Goody Two Shoes for three months. I haven't heard a single question about any of the riddles since.

If you look back through my social media posts, you'll notice I didn't promote 48H until version 1.1 was released. As far as I'm concerned, 48H wasn't done until 1.1. I wasn't about to encourage the general public to play a game I was still actively helping to develop and beta test. It bothers me deeply that most people have experienced a version that was rushed and incomplete, and that the earliest iterations are the ones immortalized for future generations on YouTube and Twitch.

Now, though? I recommend 48H whenever there's an opportunity. I'm proud to share this game with others. I'm proud of the entire devteam for making this game happen in the first place, let alone making it look so professional and polished; proud of myself for the quantity, variety, and quality of work I contributed; and proud of my fellow entrants for pulling off over a hundred MaGMML-worthy levels within (or just barely over) the 48-hour time limit, even if I'm prone to complaining about them. I enjoy seeing people enjoy 48H.

As of this post, devteam discussions are infrequent and rarely pertain to the game itself, chatter about the game seems to have died down on Discord and YouTube, and bug reports have all but ceased. Effectively, this ship has sailed. Of course, no game is ever truly done, least of all one that can easily be patched. In fact, a modest number of changes have already been pushed to the GitHub repository in anticipation of another patch. I have one or two more Developer Diaries to follow this one, some updates I might like to add to the MaGMML wiki, and plans to start livestreaming the game once I can commit to a semi-regular streaming schedule. It's been a long voyage, and I expect it'll be awhile longer before I return to shore.

Story navigation: 1 | 2 | 3 | 4

On November 28, 2018, level submissions for Make a Good Mega Man Level Contest 3 (MaGMML3) came to a close. After a generous seven-day grace period for late entries, we had a total of 186 levels. That's almost twice the number of levels in MaGMML1 and 2 combined.

Our new contest motto was, "The judges are gonna die."

The devteam loaded the entry levels into a standalone executable "game" for the judges to play. This consisted of a small hub with a teleporter used to access the levels, a costume selector in case we didn't want to play as Mega Man (Flash Man was still in the works, so I picked Roll), NPCs of the judges for comic relief, and infinite E-/W-/M-Tank refills. To maintain blind judging, the levels were randomly numbered instead of identified by creator name, and any in-level material that obviously gave away the creator's identity (eg, self-insert NPCs) was temporarily redacted.

The devteam needed several weeks to load all the levels and test them for basic functionality. Two levels were cut before they even reached the judges, one for being irreparably broken in its construction and one for containing a note threatening the judges to give the level a good score. In an effort to get us judges playing and discussing as quickly as possible, the remaining levels were added to the judge EXE in batches of 30 or so, with each judge receiving a randomized playing order for each batch. Although I didn't argue it strongly, I was a proponent of waiting for all the levels to be loaded; I felt the benefits of playing in batches didn't outweigh the potential for bias inherent in all of us playing the levels in more or less the same order.

Still, I had a system in place to minimize bias on my end as much as possible. After playing all the levels in batches and seeing the best and worst the contest had to offer, I would go back and replay everything in a newly randomized order (ignoring batch divisions), scoring and reviewing as I went. Afterward, I'd compare scores to ensure everything felt correct and consistent, replaying individual levels again if necessary.

In terms of specific process, I knew I wanted to:

• Record my blind playthroughs for future reference and eventual upload to YouTube
• Approach my blind playthroughs as a regular player and any subsequent playthroughs as a playtester
• Jot down notes as I went, to supplement the observations captured in my recordings
• Go for 100% completion without asking for hints, unless I was hopelessly stumped

Playing as often as my schedule (and the batch release schedule) allowed, and taking breaks when I started feeling tired or cranky, it took me 50 hours and 48 minutes spread across 2 months to clear the first round of playthroughs. During that time, I continually fine-tuned my process.

In the beginning, I was recording multiple levels in a single video, being a little lax about revisiting levels right away to search for missed secrets, and playing mainly for my own enjoyment. By the end, I was recording each level separately (which made it MUCH easier to track down footage later), diligently verifying 100% completion before moving on, and playing with more critical intent—in addition to playing for fun, I was checking screen transitions and testing the feasibility of a buster-only run, saving myself the trouble of doing so on a replay.

Aiding my process were a couple quality-of-life improvements along the way. First, the implementation of a map feature in one of the later batches. Second, the realization that the cheat menu had an option to show invisible collision objects, saving me the trouble of leaping into every spike pit to determine whether the creator had pulled a Magnum Man and placed spike tiles but not spike objects. Third, the revelation that noclip mode had been accessible via a hotkey this whole time, which facilitated more efficient playtesting and relieved the burden of redoing sections I'd already played into the ground.

Despite my livestreaming, recording, and playtesting experience, going through these levels was unlike anything I'd ever done. It's one thing to play levels of varying quality and character in the context of a finalized MaGMML game—the level scores, tier placement, creator names, and nearby NPCs give you a sense of what you're in for, and it's fine to let your gut reactions define your opinions. It's another thing entirely to experience the levels completely blind, in a random order, relying solely on what the levels themselves tell you about their length, difficulty, stability, and so forth, all the while maintaining a consistent process to ensure fair and impartial judging.

I encountered plenty of difficulties. On more than one occasion, I set out to play "one more level" before taking a food or sleep break, only to discover 20 minutes later that the level was not going to end anytime soon. I'm not particularly photosensitive or subject to motion sickness, but a few levels made me queasy with their gimmicks and visual effects—not so much that I couldn't finish, but enough to make judging uncomfortable. Due to programming oversights in some of the contestants' custom objects, I triggered a handful of hard crashes and had to make up lost progress (usually before learning about noclip mode).

I had to switch my player avatar when I discovered at a most inopportune time that Roll didn't have any custom sprites created for Rush Bike, so she simply turned invisible. With the devteam making updates to the engine between batches, it wasn't always obvious which glitches were newly introduced and which should've been caught by the level creators, so I started a running list of issues to raise with the devteam so I could judge Functionality fairly. The FIRE button on my controller got progressively stickier as time went on, eventually spreading that stickiness to the JUMP button, effectively rendering the controller unusable.

Oh, and I was sick with an upper respiratory infection for almost the entire duration. I had already decided not to perform for an audience while recording my blind playthroughs—after all, these recordings were personal reference material first and public entertainment second—but I would've preferred not to sound like a plague beast when I talked. This didn't affect my playing ability, but there were a few mishaps early in the recording process where I muted my microphone in order to privately cough up a lung...and then forgot to unmute. I captured all the most important observations in my written notes, but I regret not having those initial audio reactions preserved for the level creators to hear.

Of course, my initial round of playthroughs wasn't all hardships. I actually had fun. Lots of fun. There's a reason why I'm so invested in this contest series, and a reason why I livestream Mega Man fangames: I am fascinated by the things people come up with when they set out to make a good (or deliberately mediocre, terrible, or ridiculous) Mega Man level.

I laughed at the sight gags and comedic dialogue. I marveled at the diversity of level concepts and the sheer amount of cleverness and creativity on display. I relished the sections that meaningfully put my platforming and problem-solving skills to the test. I lost myself in the immersive atmosphere created by the music and graphics. I was bemused by the zany, inexplicable design decisions and mind-bogglingly obvious playtesting oversights. I enjoyed trying to break people's levels—and sometimes, I enjoyed being denied that pleasure because the creators actually anticipated my nonsense.

Compared with any previous MaGMML, the highs were higher and the lows were much, much lower. I was proud of the levels that took to heart all the advice and feedback coming out of these contests, and I writhed in pain at the levels that clearly did not. Through it all, even when a play session wore me out, I remained excited to see what was next.

Of course, I knew what was next, in the "big picture" sense. Next was replaying, scoring, and reviewing these levels. This had been merely a warmup; the real judging was about to begin.

That's it for now! Once the contest results are announced, I'll upload my blind playthrough videos to YouTube and update this post with a link.

Story navigation: 1 | 2 | 3 | 4
​
​One of the first tasks that Mick Galbani, ACESpark (AKA Davwin), Shinryu, Pachy, and I undertook as a judge staff for Make a Good Mega Man Level Contest 3 (MaGMML3) was to test out the rubric we'd be using to rate the entries. This was the same rubric we'd used in the judge application process, but now the goal was to determine whether the categories were weighted properly. For this, a larger pool of levels would be needed.

The hosts (Mick and Davwin) selected two levels from each tier of MaGMML1, a game whose contest rubric is universally recognized as pants. If desired, we were allowed to play the MaGMML1 Remastered versions of those levels (same design; different game engine). Even though Remastered hadn't been released yet, the levels in question were in good enough shape to be loaded into a standalone executable. Five levels from MaGMML2's unrated Tier X (which sounds dirtier than it is) were also selected. To avoid bias, we opted to omit any levels made by one of us judges. We also excluded the entry levels from MaGMML2, given that Davwin was a judge for that contest and used a rubric that wasn't too far off from the new one.

We played and scored these levels according to the new rubric—but no reviews; just ratings. I shared my personal rubric breakdown (the one I used for the judge application) with the group, in case they found it useful. Together, we refined the subcategories as follows:
​
Design - X/35
Introductions - X/5
Challenge design (deliberate, clear, meaningful, fair) - X/5
Challenge progression (↑ complexity/difficulty, challenge arcs, climax) - X/5
Focus (coherent theme, manageable roster, nothing over/underused) - X/5
Architecture (logical, efficient, unobtrusive) - X/5
Player consideration (length, layout, checkpoints, power-ups) - X/5
Ability Balance (abilities shine without destroying the challenge) - X/2
Name (does the level reflect the title) - X/2
Perfectible (no damage w/ buster only, or else with acceptable forced weapon use) - X/1
 
Fun - X/25
Totally subjective rating - X/10
Recommendable (would you recommend this to someone else) - X/5
Highs (do the best parts boost the level) - X/5
Lows (are the shortcomings forgivable) - X/5
 
Creativity - X/15
Originality (have I seen anything exactly like this, i.e. sections copied from other levels) - X/5
Novelty (does this offer a new gameplay experience, or does it feel similar to other stages) - X/5
Impressiveness (am I surprised or wowed) - X/5
 
Aesthetics - X/15
Graphics - X/5
Music/Sound - X/5
Atmosphere/theming - X/5
 
Functionality - 9/10
Stability (flawless construction; no glitches) - X/5
Feasibility (can the player reliably complete each challenge) - X/5


Armed with this updated rubric breakdown, I came up with some scores that should cause anyone who's played these levels to raise an eyebrow. As before, the numbers in parentheses represent the individual subcategory scores. Feel free to skip ahead; I won't stop you.

(That last one's a picture of the rarely seen MaGMML1 Remastered rubric test hub, in case you were wondering.)

​Organizing the total scores from lowest to highest (giving more priority to the level with the higher Design score, in the case of a tie), here's where everything placed:

(34) City War
(48) The Quickening 2
(52) Wily Combo
(58) Level
(58) Napalm Forest & Caves
(59) Midnight Snow
(60) Coyote Man
(62) Mega Man World
(64) Wily Fortress VR
(64) Thunderclyffe Plant
(65) Glass Man
(71) So Good
(72) Chroma Key
(74) Metallic Ocean
(83) Research Facility

Some questionable scores, to be sure. But I've seen some bad fan-made levels, so the bar is set pretty low for getting at least a couple points in any given category. Also, I tend to focus more on the things that ruin my Mega Man experience than the things that go above and beyond to make it superb. There are other factors influencing my scores, but these are the ones that most concisely explain how I came up with these numbers.

I have a vague recollection of us judges comparing notes and averaging all our scores to see where these levels would've placed in MaGMML3. Oddly, I can't find any record of this discussion in the Discord logs, so maybe it happened over voice chat. Whatever the case, we did establish that the main rubric was solid enough to use for the contest. Whether we used the more detailed breakdown was up to us.
​
When it came time to start rating and reviewing MaGMML3 levels, it quickly became apparent to me that the more detailed breakdown needed more tweaking. I found myself agonizing over categories that were too specific to apply to less conventional levels, so broad that they overlapped unfairly with other categories, or simply no longer of great interest to me.

For one thing, my interpretation of Creativity inherently penalized levels such as Wily Combo and Napalm Forest & Caves, which are centered around callbacks to the official Mega Man games, and unfairly rewarded the likes of So Good and Mega Man World for using non–Mega Man assets. For another thing, the Recommendable subcategory of the Fun score was all too close to MaGMML1's wildly subjective Other Person Fun Factor score (ie, how much do you think other people would enjoy the level).

So, I tinkered with the subcategories until I had something that was (a) comfortably easy to fill out, (b) consistently applicable across all level types, and (c) more accurate to what I was actually looking for in these levels.

Design - X/35
Introductions (clear, appropriate) - X/5
Challenge design (deliberate, meaningful, fair, reasonably perfectible) - X/5
Challenge progression (↑ complexity/difficulty, challenge arcs, climax) - X/5
Focus (coherent vision, manageable roster, nothing over/underused) - X/5
Layout (logical/efficient architecture, obvious pits, safe transitions, sense of direction) - X/5
Player consideration (length, checkpoints, items, disability awareness, niceties) - X/5
Weapon consideration (balance of freedom and challenge, limitations inform the design) - X/3
Name (does the title fit the level) - X/2
 
Fun - X/25
Totally subjective rating - X/10
Highs (do the best parts boost the level) - X/5
Lows (are the shortcomings forgivable) - X/5
Contest appropriateness (should other people be expected to play this) - X/5
 
Creativity - X/15
Novelty (does the level offer new experiences, or present old experiences in new ways) - X/5
Potential (does the level adequately explore the potential of its various elements) - X/5
Impressiveness (am I surprised, charmed, impressed, or wowed) - X/5
 
Aesthetics - X/15
Audio (appropriate, enjoyable, tolerable, music looped and implemented properly) - X/5
Visuals (clear, legible, appealing, unobtrusive, polished) - X/5
Atmosphere (theming, story, overall feel) - X/5
 
Functionality - X/10
Construction (appropriate structural object use, polished programming, no surprises) - X/5
Feasibility (is the level beatable without risk of getting stuck or crashing the game) - X/5

​
This proved to be a much better breakdown. There were still some oddball levels that threw me for a loop, but the total scores I was assigning finally felt right.

I originally had level layout under Player Consideration, but I realized that all the structural elements should be together in the same category. Proceeding safely and confidently through a level is a function of the architecture, layout, screen transitions, and graphics working together to guide the player. Player Consideration should be reserved for questions such as, "Did you remember that players with color blindness, motion sickness, epilepsy, or a hearing impairment may want to enjoy this level?", not, "Did you remember that players prefer not to die instantly when attempting to exit a room?"

Whereas the old Ability Balance category required me to pick apart the individual usefulness of every single weapon in a roster full of redundancy, and Perfectible required me to determine if it was technically possible to do a no-damage buster-only run (ugh), Weapon Consideration allowed me to step back and compare overall experiences with and without special weapons. Is the player allowed to try different strategies without being excessively rewarded or punished? This was also a way to score the appropriateness and intentionality of what weapons were enabled, disabled, unlockable, or infinite.

Recommendable morphed into ​Contest Appropriateness—essentially, a measure of how much the level deserves a skip teleporter. My rationale is that if a level is skippable, it's obviously not fun enough for a general audience to put up with whatever problems warranted the skip. Whereas MaGMML1's Other Person Fun Factor was a haphazard guess at what other people might like, this was a safeguard against my personal preferences allowing a level to reach the top tiers without being fully accessible to the average player.

Originality was unsustainable; I was spending entirely too much time analyzing every screen, testing my memory for any identical setups across hundreds upon hundreds of other levels. What I really cared about for Creativity was the overall experience, what the designer created with elements old and new. I replaced Originality with Potential, something that is hugely important to me—it's one thing to come up with new ideas; it's another thing entirely to go anywhere with them.

I wanted Functionality to pertain solely to the technical aspects of level design. When I initially worked out the category breakdowns, the glitchy spring platforms of Magnum Man were foremost in my mind for Feasibility. Realistically, whether the player can reliably complete each challenge is usually more of a Design question—and a question that can only be answered by more repeat testing than my schedule and sanity would ever allow. Thus, I recalibrated the breakdown to focus on easily quantifiable items in the same vein as glitches and collision object mishaps. Does the architecture line up safely across screen transitions? Are boss projectiles destroyed along with the boss? Is the level free of any and all softlock potential? Etc.

I came to realize that some overlap was inevitable. A low Player Consideration score, for instance, goes hand-in-hand with a low Contest Appropriateness score, because a long level with no checkpoints or power-ups is a prime candidate for a skip teleporter. A high Creativity score is almost guaranteed to secure a good number of Fun points from me. Good screen transitions are highly important to me, and different aspects of their use are covered under both Design and Functionality. And that's okay. The purpose of the rubric is to help the judges translate their complex opinions into a simple, quantifiable, universally applicable format, not to force apart certain elements that are inherently intertwined.

Besides, reorganizing my subcategories was only one part of the scoring process. The plan was always to compare scores at the very end and adjust as necessary, with or without a more detailed breakdown. If there were still problems with my interpretation of the rubric after 170+ levels, I'd have a chance to resolve them.

Fun, right? And this was just the first step in the judge process. Wait until I tell you about playing and writing reviews—after the results are announced, of course.

Story navigation: 1 | 2 | 3 | 4

The Make a Good Mega Man Level Contest (MaGMML) 3 judge team was assembled a full year before judging began. We had plenty to keep us busy in that time, but I took on some non-judge work as well.

I spent a good chunk of 2018 helping to expand and test the game engine, making such contributions as assembling new tilesets (eg, the MM10 lab), reorganizing existing tilesets and creating slopes for some of them (eg, Skull Man; Charge Man; MM1 Wily 1, 2, and 4; MM2 Wily 1), and checking engine assets for fidelity to the original games (eg, all the Joes). For a time, I also was in charge of showcase development—that is, planning, building, and delegating the example levels that show off everything available in the engine.

I knew that contestants would be influenced to some degree by how the engine assets were presented to them. Without a showcase, many people would stick with the gimmicks and enemies they were familiar with, and overlook a lot of the engine's customization options. At the same time, any kind of showcase ran the risk of encouraging contestants to crib from the example levels—whether due to a lack of creativity, a false assumption that the example levels demonstrated the "right" way to use these assets, or a genuine inspiration to develop one of the sample challenges into a full level.

Before I took over showcase development, the team was grouping assets together by stage—here's everything from Cut Man, here's everything from Heat Man, and so forth. My main objection to this approach was that it would reinforce that certain assets need to go together, because that's how they appeared in the original games. After a lot of discussion, we agreed to rework everything and break up the assets by theme and/or function. I created a blank room in GameMaker; inserted one instance each of every enemy, gimmick, miniboss, and boss in the engine; and then started organizing these assets into categories (eg, water minibosses, moving platforms). Not unlike dumping out a basket of clothes and sorting them into piles.

With input from the devteam, I finessed the groups until everyone seemed to be happy with the distribution. Once things were finalized, I set up a tracking spreadsheet and requested volunteers to build example levels using the assets in each group. Tapping into my instincts as a judge and design critic, I also provided some guidelines for creating the showcase levels:

Of course, the showcase levels needed to be labeled to help players remember what they had and hadn't seen. You can blame me for all but one or two of these groan-inducing names:

• A Slog of Ice and Fire
• A Torrent of Turrets
• Airborne Assailants
• Brawl of the Wild
• Castle Castoffs
• Circuit Breaker
• Demolition Mission
• Extraordinary Ordinance
• Factory Fisticuffs
• Fan the Flame
• Fluidic Foes
• Ground Control
• Industrial Intrigue
• Invite Your Fiends
• Landlocked Leftovers
• Maniacal Manipulators
• Might As Well Jump
• Misfit Minibosses
• Modified Mobility
• Never Gonna Let You Joe
• Perilous Patrol
• Platform Swarm
• Pleased to Met You
• Razor-Sharp Rivals
• Respect the Unexpected
• Spectacular Spawners
• Submerged Scuffle
• Thug Zappers
• Water You Doing

I called dibs on Maniacal Manipulators (bosses with physics-altering attacks, one of whom is Flash Man, my judge avatar for the contest), Landlocked Leftovers (all the ground-based enemies that didn't fit anywhere else), and Never Gonna Let You Joe. After devoting two years of my life to OH JOES!, a game devoted to using this tired old enemy type in new and different ways, there was no way I wasn't going to claim the all-Joe showcase (Joecase?). Although I wouldn't consider it one of my strongest levels, I relished the self-imposed challenge of making the level beatable without destroying a single Joe (seriously, try it). Plus, I got to put some of my custom slope tiles to use.

I had wanted to take on more levels, but the stress of being a game designer (not just a level designer) finally got to me. For one thing, I was burned out from OH JOES! and needed a break from working on fangames. For another thing, I wasn't prepared for the logistical hurdles of this particular project.

The sheer size of the devkit meant absurd amounts of time spent loading and compiling in GameMaker. With OH JOES!, I could fire up the software, make a change, test it, tweak it, and test it again in a matter of minutes; with the MaGMML3 devkit, the same amount of work could easily take half an hour. Level design was suddenly an arduous, inefficient task that required me to plan my time differently and adjust how I approached playtesting.

Moreover, the showcase was being designed while the engine was still being expanded and tested. From a programming perspective, it's incredibly helpful to see how assets behave in normal gameplay situations. From a level design perspective, it's difficult to plan out challenges when the building blocks are still being finessed. I spent a lot of time logging issues on GitHub or, in rare cases, attempting to make programming changes myself. To push my changes to the rest of the devteam, I had to learn to use a command-based software called Git Bash. Even with a comprehensive guide from devteam member NaOH, I frequently ran into confusing, infuriating issues (read: merge conflicts). All I wanted to do was design some levels.

Recognizing that I needed to step back, I passed the torch to devteam member CWU01P, who did a terrific job of picking up the slack. Really, the whole devteam did some impressive work in pulling together the showcase.

If you'd like to take the showcase for a spin, it's packaged with Megamix Engine, which you can download here.

Story navigation: 1 | 2 | 3 | 4

I've been a part of the Make a Good Mega Man Level Contest (MaGMML) community since the beginning, back when it looked like MaGMML1 was the only chance I'd ever have to move my Mega Man level ideas from paper to pixels. What followed was an unexpected explosion of level design opportunities—Mega Man Endless, OH JOES! (A Proto Man Adventure), Mega Maker, and MaGMML2. I shifted my focus away from recording YouTube videos and threw myself into Mega Man fangames, becoming highly active as an archivist, livestreamer, playtester, and wiki contributor on top of being a level/game designer. When MaGMML3 was announced, I got to add another title to the list: judge. But it took some effort to get there.

From my videos and livestreams to the countless reviews I've written across the Web, I've been a game critic for something like 15 years. After participating in the first MaGMML, I expressed an interest in being a judge for the second one. I was briefly considered for the position...but then people remembered that I was the guy who made the love-it-or-more-likely-hate-it "Maze of Death" level for the first contest, so I was back to being a contestant. Recognizing good level design and creating good level design are not the same skill, so I had something to prove going into MaGMML2.

With "Guts Man's Asteroid," I attempted to address every complaint I'd heard about "Maze of Death." By all accounts, I was successful—despite some flaws (read: boulder droppers) that kept the level just barely out of the top ten, my submission was well received by the judges and remains a fan favorite. Hence, this was the level I chose to submit when applications opened to become a judge for MaGMML3.

Nineteen of us applied, but only three of us—Shinryu (creator of MaGMML2's first-place level), Pachy (creator of what might be MaGMML2's best-designed middle-tier level), and yours truly (creator of this blog post)—were offered a judge position. There were two phases to the application process. The first one consisted of playing, rating, and reviewing seven sample levels, which represented a typical spread for this type of contest: the thoroughly mediocre level, the obvious troll level, the level that looks great at first glance but secretly has some issues, and so forth. Eleven of us made it to the second phase, which had us sending the contest hosts an example of our level design ability, be it a new level or one that we'd already made.

During the whole process, I kept telling myself that I'd be happy no matter what the result was. However, the anxiety, excitement, and preemptive disappointment I felt at various points made it clear to my wife, if not to me, that I really would've been crushed if I didn't pass the test. I say "preemptive disappointment" because, for a while, it looked like I hadn't made the initial cut. I was watching for an e-mail or private message with a status update, but I didn't realize a new "Phase 2 Applicant" role (or something to that effect) had been added for me on Discord. Oops.

Because I'd already created the level I wanted to submit as a sample of my work, all I needed to worry about were the reviews. We were given a rubric: 35 points for design, 25 for fun, 15 for creativity, 15 for aesthetics, and 10 for functionality, adding up to 100 possible points. We were also asked to rate the difficulty on a scale of 1-5, indicate whether the level should be skippable (and if so, why), and designate a favorite and least favorite.

I can rate things on a scale of 1-5 or 1-10 just fine, but I had trouble determining what would separate, say, a 23 from a 24. I ended up breaking each category into more manageable subcategories, getting a second opinion from my wife and tinkering with the balance until I ended up with this:

Design - X/35
Learning curve - X/5
Challenge design (deliberate, clear, meaningful, fair) - X/5
Challenge progression (↑ complexity/difficulty, challenge arcs, climax) - X/5
Focus (coherent theme, manageable roster, nothing over/underused) - X/5
Architecture (logical, efficient, unobtrusive) - X/5
Level design (length, layout, pacing, checkpoints) - X/5
Capability consideration (abilities shine without destroying the challenge) - X/2
Name (does the level reflect the title) - X/2
Perfectible (no damage w/ buster only) - X/1

Fun - X/25
Totally subjective rating - X/10
Worth my time - X/5
Highs (do the best parts boost the level) - X/5
Lows (are the shortcomings forgivable) - X/5

Creativity - X/15
Originality (have I seen anything exactly like this) - X/5
Novelty (does this offer new experiences) - X/5
Impressiveness (am I surprised or wowed) - X/5

Aesthetics - X/15
Graphics - X/5
Music - X/5
Atmosphere/theming - X/5

Functionality - X/10
Stability (flawless construction; no glitches) - X/5
Feasibility (can the player reliably complete each challenge) - X/5


Now I was ready to judge some levels. I downloaded an executable file containing the sample levels (which you can download here, if you'd like to try them yourself) and got to work. I played everything once, jotted down some notes, then circled back and played everything again before finalizing my scores and writeups.

Preserved for posterity, and so that you can ask, "Wait, how did this guy get accepted as a judge?", here are the opinions I offered. Note that the numbers in parentheses correspond with the subcategory breakdowns listed above. Also note that this is the last time you'll see level reviews from me in excess of 500 words; no one should spend more time reading my review than I spent playing their level.

Midnight Man

Difficulty Rating: 1
Skippable: No

Design - 21/35 (3, 2, 2, 2, 4, 5, 1, 1, 1)
Fun - 12/25 (5, 2, 1, 4)
Creativity - 3/15 (2, 1, 0)
Aesthetics - 8/15 (3, 2, 3)
Functionality - 10/10 (5, 5)
TOTAL - 54/100

This is—and I think we can all agree on this—a level. The name “Midnight Man” conjures up images of what might be in store for the player—at the very least, a boss at the end named Midnight Man. Will there be werewolves to fight under a full moon at midnight? Some darkness- or shadow-oriented gimmick, given how dark it is at midnight? Perhaps a battle on a clock tower as the clock strikes midnight? The heart of a lion and the wings of a bat, BECAUSE IT’S MIDNITE? Why, the possibilities are...not really fleshed out here at all.
 
The background of the first half of the stage suggests that it is nighttime, and there are bats. This is a good start. In general, the graphics are pretty good; there’s some nice detail in the foregrounds, and the damage-ridden background for the indoors portion (despite being a bit too close in color to the foreground) suggests there might be an interesting story behind this level—especially on the last screen; I want to know what that cool-looking capsule thing is. Unfortunately, the challenges do nothing to bring that story to life.
 
I applaud that the enemy roster is a reasonable size and that the enemies aren’t placed all willy-nilly. I like the one screen where the dense starfield in the background makes it harder to see the Haehay’s bullets (I hope that was intentional), and I like that the Battons blend into the background for a similar sneakiness (which I also hope was intentional). But that’s about all that stands out as particularly positive about the challenges.
 
There’s no sense of theme to the enemies, and their placement is often less than ideal—the first Beak you meet should not be on top of the first ladder you find, nor should you hide Beaks behind the health bar. The Shotman guarding the entrance to the secret room (which is satisfyingly well hidden) is all well and good until you realize you’ll practically walk right into him on the way back out. Many enemies can be avoided or dispatched with no risk to the player whatsoever, like the useless Hot Dog near the halfway point. And I’m not sure it’s even possible to avoid damage while fighting the secret Hot Dog with the buster; that is a looooooong string of fireballs. The lack of gimmicks is a letdown, too. The level needs something to make it stand out, and the enemy challenges aren’t novel or complex enough to compensate.
 
The music is fine; I found it a bit abrasive at first and I’ve already forgotten what it actually sounds like, but it fills the noise void well enough. I didn’t find any technical issues; there was one screen transition at the top of a ladder that could’ve been a little smoother, but that’s a minor thing. Otherwise, there’s not much to say. This level needs a stronger theme and an actual MIDNIGHT MAN to live up to its name.

Coptar Man

Difficulty Rating: 4
Skippable: Yes (the graphics inconsistently and unreliably convey the actual level architecture)
LEAST FAVORITE

Design - 3/35 (0, 0, 1, 0, 0, 1, 1, 0, 0)
Fun - 2/25 (1, 0, 0, 1)
Creativity - 3/15 (2, 1, 0)
Aesthetics - 3/15 (0, 2, 1)
Functionality - 1/10
TOTAL - 12/100

What an exquisite level. While other developers waste their time on such outdated concepts as “learning curve” and “solid floors,” you have masterfully eschewed every so-called “good” game design principle in favor of something truly revolutionary. Like the Pirate’s Code, any graphical representations of spikes or solid objects are more like guidelines, really; they’re a cue to the player that spikes and solid blocks are in the vicinity, but not necessarily exactly where they appear to be. This generates a sense of paranoia that, previously, only the likes of Stephen King or, say, Baby Groot holding a detonator have ever achieved.
 
Amplifying the paranoia is the constant surprise of new enemy types assailing the player when they are least prepared to take them on. A sudden Apache Joe while the player is being launched uncontrollably off the ground by a powerful fan? Genius. Nevermind crafting cohesive challenges or giving the player a chance to understand the nature of each obstacle; tossing handfuls of miscellaneous robots onto each screen is a sure-fire way to create difficulty without expending any effort in the process. Imagine how many more Mega Man games we could have had if Capcom had taken that approach.
 
I’m glad to finally see a level that recognizes graphics for the scourge they are. All those differently colored pixels everywhere take too much of the focus away from the gameplay. A solid-color background, a few pipe tiles, and a handful of different spikes are really all anyone needs—and honestly, I think you even could’ve gotten away with ditching the pipe tiles.
 
I wholeheartedly support the music choice. The high-pitched noises of Tornado Man’s theme have captured fans’ attention for years, and the decision to loop the music in an unconventional way is a clever tie-in to the level’s overall theme of never knowing what to expect. Truly, this captures the essence of a “Coptar.”
 
I was so inspired by your masterful work that I decided to take a page from your book and score your level with numbers that don’t necessarily match up with anything I’ve said here. Hopefully you enjoy that as much as I enjoyed your level.

X Factory

Difficulty Rating: 3
Skippable: No

Design - 32/35 (5, 5, 4, 5, 4, 5, 2, 1, 1)
Fun - 21/25 (8, 5, 4, 4)
Creativity - 12/15 (5, 4, 3)
Aesthetics - 12/15 (4, 4, 4)
Functionality - 10/10 (5, 5)
TOTAL - 87/100

Good, good, good. This is a level that reflects both an understanding of good game design principles and the skill to do them justice. Although this level doesn’t elicit the same “Whoa, cool” reaction that I’ve had to other levels in this contest, I respect the heck out of the craftsmanship here.
 
From start to finish, there is a clear learning curve and steady difficulty progression, introducing new elements in relatively safe environments and gradually combining them for more and more interesting and challenging scenarios. There’s a perfect balance of focus and variety, with each enemy and gimmick having a chance to shine without overstaying its welcome. Challenges require a combination of observation, planning, and straight-up platforming skill to overcome, giving the level a bit of a puzzle slant that I appreciate. It took me a few tries to reach the end, but every death was entirely my fault—a mark of truly fair difficulty.
 
Aesthetically, the level is a unique combination of colorful and serious, and the energetic music compliments the visuals well. Highly detailed graphics like these always run the risk of being distractingly detailed and clashing with the simpler 8-bit Mega Man sprites, but for the most part, everything meshes well. The enemy and obstacle selection and coloration go a long way in creating a cohesive look. A couple screens are right on the edge of looking too busy, though; I had some trouble distinguishing between foreground and background on the screen with a Springer in the top and bottom half, for instance. Also, the architecture in one or two places makes the challenge at hand appear a little confusing at first; for example, there’s one screen with four X platforms leading you across spikes to an exit on the right, but the bottom-left corner of the screen has an irrelevant cavern of spikes that appears to be part of the challenge somehow.
 
The autoscrolling section at the end is a nice culmination to the level, yet not quite as satisfying as it could be. It’s tricky to nail the pacing of an autoscrolling section, and this one errs just a smidge too much on the slow side for my taste. I suspect most players will find it fine, but I got antsy a few times while standing around idly for the next challenge to appear. It’s mostly the very end that’s a bit disappointing—it’s extremely easy to wipe out that whole row of B Bitters before they become a problem, which makes it that much more anticlimactic to discover the Energy Element sitting around unguarded on the next screen. Swapping out one of the B Bitters for a Crystal Joe might’ve been sufficient to spice up the final challenge (and as a side note, the Crystal Joes don’t entirely function like they do in MM5, but they serve the challenges just fine). Adding even a simple gimmick challenge to the Energy Element screen would have been enough to remove that feeling of “Oh, it’s over already.”
 
These are relatively minor issues, however. This is a thoroughly solid level with very deliberate and well-thought-out design decisions, and I would love to see more levels like this one.

Space Crusade

Difficulty Rating: 3
Skippable: No
​FAVORITE

Design - 23/35 (2, 3, 3, 2, 3, 5, 2, 2, 1)
Fun - 21/25 (8, 5, 5, 3)
Creativity - 12/15 (4, 4, 4)
Aesthetics - 15/15 (5, 5, 4)
Functionality - 10/10 (5, 5)
TOTAL – 80/100

This was fun! I'm a sucker for outer space, and the stage lives up to its name. Between the groovy music, the eye-catching blend of space-themed tilesets, the reskinned enemies, and the story element provided by the NPCs, everything works together to create the atmosphere of an exciting space crusade. I could tell that the stage was referencing...something...(I looked it up afterward; it's Warhammer 40K) but the whole experience is crafted in such a way that you don't need to get the reference to appreciate the stage.
 
I like variety in a stage, and this one has plenty of it—too much for its own good, in fact. On the plus side, most enemies and obstacles are used at least twice, in situations where they have at least a partial opportunity to shine. There's a lot of creativity in the challenges, and nothing feels completely wasted. I love the screen where you're sliding into time bombs with the cannon firing at you, and the screen where you've got to slide under spikes on a Splash platform...and the screen where you're sliding past those dreaded Up'n'Downs is surprisingly not awful, further demonstrating that you have the chops to turn the familiar into something pleasantly different. The boss is a clever synthesis of different bosses and minibosses, and a satisfying end to the stage.
 
On the minus side, the “sampler platter” approach means that none of these challenges have the chance to be fully developed, which is a right shame. Cutting a handful of foes and hazards would allow more room to explore the potential of the remaining ones, bringing more focus to the level without sacrificing the feeling of variety. In particular, the reskinned falling platforms add nothing to the stage; you’ve already got Shadow platforms and indestructible blocks that could serve the exact same purpose.
 
Unfortunately, many of the rooms are fairly cramped. This isn’t inherently problematic, as claustrophobia-inducing architecture can allow for some tricky challenges and can add to the character of a stage. In this case, however, some rooms feel tight because the entrance and exit aren’t ideally positioned—take the room before the checkpoint, for example, where all the action is jammed into the top left corner of the screen. Moreover, it’s not uncommon to have a few too many objects on the screen at once, or a complex challenge concentrated into a very small space.
 
The learning curve on these challenges is fast, but standing perfectly still at the entrance to a screen will usually give enough time to figure out what’s going on. The few exceptions are brutal, however. The introduction to the reskinned falling platforms seems specifically designed as a beginner’s trap, with only the most agile players making it out alive on their first try. The following screen with the reskinned Sniper Joes and Shadow platforms over spikes demands even faster reflexes, and the screen after that surprises you with Up’n’Downs in a place where they’re totally unexpected and impossible to dodge if you’re caught off guard. Part of the problem is making every screen a self-contained challenge; occasional use of camera scrolling would go a long way in giving the player and these challenges enough space to breathe.
 
Nonetheless, I enjoyed this level. The shortcomings aren’t deal-breakers for me, and almost all of the challenges are individually satisfying, even if there are ways to improve them and the level as a whole. I was promised a space crusade, and by the Emperor, I did not leave disappointed.

Gate 303

Difficulty Rating: 2
Skippable: No

Design - 14/35 (2, 1, 1, 1, 3, 3, 1, 1, 1)
Fun - 9/25 (4, 1, 2, 2)
Creativity - 4/15 (2, 2, 0)
Aesthetics - 9/15 (4, 4, 1)
Functionality - 10/10 (5, 5)
TOTAL - 46/100*

This could have been a fun romp through a robot-ridden airport, with our hero on a scavenger hunt for the keys that unlock Gate 303, where an airplane or aviation-themed boss lies waiting. Instead, it's a well-meaning collection of rookie mistakes.
 
The stage starts out well enough: pleasantly backgroundy music, unremarkably but competently used vanilla graphics, and a few simple challenges with a very gentle learning curve. I like the use of the Elec beams as a less punishing alternative to floor spikes (though it looks odd to have the beams overlap with the floor; either give them more space or hide them behind a higher-priority floor tile). Combining them with Guts platforms is a decent idea, and WAIT THAT'S A SOLID WALL NOT A BACKGROUND TILE OH THE ELECTRICITY IT HURTS.
 
Suddenly, the exceedingly gentle learning curve is gone. It's never demonstrated that Guts platforms can pass through solid walls, so it's an even worse shock (literally and figuratively) when you're dumped off. It's not long before you're thrown into a tricky timing challenge involving sliding, falling a fair distance, and dodging Sniper Joe bullets—none of which has been required previously in the stage—while also avoiding an Elec beam trap. And I should mention that the Elec beams across the stage are inconsistent about whether they fire constantly or are on some kind of timer.
 
One enemy after another is introduced in a way that assumes the player already knows how to handle these foes. Never seen a Shield Attacker? Too late; you got hit. What's a Pandeeta? It's that thing you almost fell on, which is now shooting you at unnecessarily close range. Worse yet, these enemies are never seen again. I can easily imagine an inexperienced player getting smacked around the entire stage, never truly understanding how to deal with all this pain. Fortunately, the stage is a wholly appropriate length, and checkpoint placement is good.
 
The last area before the bosses is simultaneously the best and worst part of the level. On the one hand, it's a neat idea to have the player clear out every last bad guy in a large room to collect enough keys to proceed. On the other hand...the whole room is a mess, with enemies all over the place and no real structure to the challenges. Not to mention that the key doors come AFTER you get all the keys (a recurring theme here), which kind of defeats the purpose of having key doors. Although it is easy enough to avoid the enemies and then need to backtrack to get the keys, but that also feels like a waste. Tease the player with a locked door, THEN let them look for the key.
 
At least there's a boss fight behind all those locked doors...except it's the same Plant Man fight we got in MM6. Devkit bosses are fine, but do SOMETHING to set them apart. Bringing in those Elec beams or Guts platforms might have been good. Cutting the second boss fight also would have been good; Gemini Man is pure padding, and the lack of a checkpoint at the start of his battle is a bit of an oversight. There's no thematic connection between Plant Man, Gemini Man, and the rest of the stage...though the stage doesn't really have much theming to begin with.


*When I received my applicant feedback from the hosts, it was brought to my attention that I missed an exploit where you can grind for infinite keys, so Design and/or Functionality should've been a point or two lower. What I learned from that oversight is to play these levels like a playtester, not just a critic.

Universe City V

Difficulty Rating: 3
Skippable: No

Design - 27/35 (3, 4, 3, 5, 3, 4, 2, 2, 1)
Fun - 19/25 (7, 4, 5, 3)
Creativity - 14/15 (5, 4, 5)
Aesthetics - 13/15 (4, 4, 5)
Functionality - 9/10 (4, 5)
TOTAL - 82/100

It took me a while to warm up to this one, but once I did, it brought a smile to my face. Initially, I was a little bored with the stage. Lots of empty space, music that’s nice but far too sleepy for a Mega Man stage, and pretty basic challenges (except the one with the fork blocks, which is good but too exacting to be an introduction to the gimmick). Then there’s a joke boss (which gave me a chuckle) and the stage is over. OK, fine. Except...it’s not over. It’s only just begun.
 
I love that the first part of the stage simultaneously sets player expectations for one type of stage while subtly exposing the player to the normal enemies and gimmicks they’ll face once the main gimmick kicks in. When the music ramps up and you start seeing Volt Men everywhere, there’s this wonderful revelation that you’ve been fooled, and the stage can jump right into more complex challenges because all the basic elements have already been introduced. But I think the intro section could have been tighter and more efficient while accomplishing the same goal, leaving me saying “Oh, that was really clever” instead of “Oh, so that’s why the first part was kinda dull.”
 
The Volt Men challenges are totally worth it, though. I’m a big fan of seeing Robot Masters repurposed as stage enemies, and you got some terrific mileage out of this one—both in terms of gameplay and the fact that the “Volt Man is overused” joke could inspire an entire stage. The challenges are interesting, varied, and continually humorous, and the many flavors of Volt Man mix well with the other enemies and gimmicks in use. I might’ve liked some sort of subtle visual distinction between the different Volt Man types, or at least a shorter timer before the shield-launching ones decide to attack; I frequently sustained damage after (incorrectly) determining that the Volt Man in front of me was just going to hold his shield forever. A little caution is fine, but the stage requires a bit too much idle waiting if you truly want to play it safe.
 
The challenge progression is solid, with a smart blend of timing and speed as the core focus. Probably my favorite part is the screen where you’re riding Spark platforms past fork blocks while a Volt Man keeps shooting at you. Great stuff. That being said, a few spots could benefit from a bit of finessing; for example, I was a smidge disappointed by how easy it was to use Super Arrow to bypass every challenge in that long hallway toward the end.
 
I was thrilled to find that Sakugarne can bounce off the boss projectiles, and I laughed at the unexpected deterrent to using Slash Claw on the stationary, shielded Volt Men. The boss fight is a superb culmination to the stage, offering another good chuckle as well as a challenge that’s well in line with everything preceding it. I experienced a little wonkiness during the boss fight when using Flash Stopper, but otherwise the programming seemed pretty solid.
 
This is a stage that could be improved in places, but it doesn’t need to be. A fun premise coupled with good design instincts makes for a charming addition to the contest, and I’m very happy to have played this.

Magnum Man

Difficulty Rating: 3
Skippable: No

Design - 24/35 (4, 3, 3, 3, 3, 3, 2, 2, 1)
Fun - 17/25 (6, 4, 5, 2)
Creativity - 14/15 (5, 5, 4)
Aesthetics - 12/15 (4, 5, 3)
Functionality - 7/10 (3, 4)
TOTAL - 74/100

The Good: Custom assets that look professional, evocative music that fits the level well, several fun and clever challenges, generally smooth learning curve
 
The Bad: Inconsistent theming, lots of clutter, too many enemy types
 
The Ugly: Problematic level layout, some spikes aren’t even spikes, a deadly and easy-to-trigger glitch
 
From the very first screen, this looks and sounds like it could be an official Capcom level. I’m a sucker for Westerns, too, so this level started off at an advantage—which gradually slipped away as more and more problems became apparent.
 
At first glance, everything seems totally fine. All the custom enemies, gimmicks, and tiles look and feel perfectly at home in a Mega Man game, and they work together with the music to develop a strong sense of theme. New types of challenges are introduced fairly, with only a few mild exceptions (eg, the exploding bullet enemies are a bit of a surprise). The oversized revolvers and springboard platforms are really creative and used extremely well, and there’s a satisfying boss fight at the end. Level length feels a mite long but within acceptable parameters, and the frequency of checkpoints and power-ups is just right. If we left it at that, this would be a dynamite level.
 
Upon closer inspection, however, there’s a disappointing lack of focus in the enemy and gimmick selection. When I remember the Alamo, I certainly don’t remember Electric Gabyoalls. Tanks in the desert I can understand, but tanks in Tombstone? When did John Wayne ever ride into the sunset on a Tondeall? For a few dollars more, would Clint Eastwood have agreed to a shootout on bouncy platforms? This is Mega Man we’re talking about, and tradition dictates that it’s OK to include a few elements that don’t strictly fit the level theme, but Magnum Man takes it a little too far. Not only are these miscellaneous elements disruptive of the otherwise fantastic atmosphere created by the themed assets, but they clutter the enemy roster to the point where several enemies only appear once—or twice, if they don’t scroll themselves off the screen before you get to them.
 
This overabundance of different enemy types also contributes to a sense of clutter, which is amplified by the busy backgrounds. The graphics look very nice, yes, but there’s so much variety and fine detail that they tend to draw the focus away from the gameplay. There’s not quite enough of a gap between challenges to give the player a chance to properly appreciate the set pieces. The architecture is occasionally a contributing factor in that cluttered feel; for example, one screen toward the beginning has two random spikes underneath an oversized revolver for some reason (wouldn’t a regular wall have been enough of a deterrent to go that way?), and one screen toward the end has a gunman buried inside a wall above the screen entrance, which is pointless when the height advantage is already a deterrent to using any weapon that can’t pass through a wall.
 
I also got extremely confused about the level layout upon reaching the second Noble Nickel, which is sitting out in the open like it’s a perfunctory health refill. Special items like this are meant to be a reward for accomplishing something out of the ordinary, so I could only conclude that I had accidentally found a secret exit to the previous screen...but then I couldn’t backtrack out of the room, and the only way to progress was to walk through pillars that looked solid. This dropped me awkwardly into the middle of a scrolling section, but there was no indication whether I should go right or left. I arbitrarily went left (which is good, because right takes you to a pointless dead end), but it felt the whole time like I was backtracking through challenges I had inadvertently bypassed by choosing the path that led to the Nickel. As it turns out, the level is completely linear—and it’s a horrible feeling to be lost in a linear level.
 
That really soured the whole level for me, which is a shame, because there are so many parts that I adore. Individually, the majority of these challenges are well designed and highly memorable. Riding oversized bullets from place to place is a hoot, and combining that with sliding challenges is AWESOME. Likewise, bouncy gunfights (despite making no sense in the context of the level) are satisfyingly tricky, particularly when the gunmen’s bullets track you, and I approve of how the spike challenges take advantage of that momentarily delay between landing on the springboard and being launched into the air. All the Noble Nickels (save for the aforementioned second one) are exactly the right amount of difficult to obtain. The battle against Magnum Man is solid, and it’s neat to see him use a couple of the attacks you’ve been practicing against throughout the level. And like I said, this has the production values of a Capcom level.
 
Except...Capcom probably wouldn’t have left an entire floor of spikes as background decoration instead of actual spikes that cause you to explode on contact. And I suspect they would have playtested those springboard platforms more thoroughly—firing Super Arrow and especially Wheel Cutter at an extended platform leads to some interesting visual oddities, and it’s all too easy to get Mega Man stuck inside one...and then speedily shunted to the opposite end of the screen, where he explodes.
 
Other issues with the level may include the following: A few late-game challenges are decidedly easier than their earlier counterparts (eg, going from an unavoidably bouncy gunfight to a gunfight on the ground with a nearby springboard if you feel like using it). The background sometimes utilizes black rectangles (like on the checkpoint screen next to the boss chamber), which look less like holes or windows and more like...black rectangles. The fight with Magnum Man is aesthetically problematic; for one thing, his boss chamber is technically underground and shouldn’t have that desertscape in the background, and for another, his generic looks don’t help the inconsistent theming. Also, Flash Stopper freezes Magnum Man’s projectiles but not the boss himself, and Electric Gabyoalls don’t freeze when hit by a charge shot like they do in MM6, but those oddities may well be intentional. However, I will say that Magnum Man’s animations, especially the gun twirling, are pretty sweet.
 
There are the makings of a truly great level here, but the biggest shortcomings seriously belie the professionalism this level projects.