Super Smash Quest is a tabletop roleplaying game that a friend of mine and I designed and hosted on IRC just around my transition from 8th grade to high school. Smash Bros. Melee was at the height of its popularity and he was an admin at a fairly popular freeform roleplaying forum where people would pit their own characters against one another in traditional Smash Bros. fashion. He told me he was interested in making a more concrete, rules-driven Smash Bros. role-playing game and asked me to help him with the rules. The premise of the plot was that the players were fans from the Melee stadium who had volunteered to protect it from the spiteful wrath of Bowser and Ganondorf, who, being the sore losers they were, made it their mission in life to destroy it and all Nintendo's heroes and--you guessed it--take over the world. The game became a purely accidental but spectacular success as our player base grew to well over 30 people and the story took on a surprisingly detailed and complex Saturday morning cartoon feel. Although it has gone through many rules permutations and proprietors over the years Super Smash Quest has endured for nearly a decade and continues to be played regularly in the same IRC channel we founded it in.
It had been many years since I'd been involved with Smash Quest myself. At the time I created this system Smash Bros. Brawl was soon to be released and tensions were mounting high, so I decided to drop in and see how the game was going. The system was completely broken by now, riddled with unnecessary gameplay artifacts like a Final Fantasy-based spellcasting system that superceded the Smash Bros. item system and a custom weapon system so out-of-control that many players developed weapons whose stats had more of an impact on a battle than their own traits. Being the obsessive-compulsive game design fanatic I am I offered my services in creating a new system. The one seen here is the result and it's the one I'm most proud of both because it most closely replicates the feel of Smash Bros. and because it demonstrates the knowledge I'd obtained from many years of experimenting with my own RPGs.
It unfortunately didn't last more than a couple of weeks before the GM scrapped it in favor of a new system. Many of the players enjoyed it, most especially older players who had been around during the time when I hosted sessions, but it didn't accommodate custom content, which was one of the features that the newer players were more accustomed to. Many of the core features from Smash Quest: Brawl have remained intact to this day, though, most specifically the dice pool system and the dynamic turn order, which were arguably its most successful and important features. They were derived from White Wolf's Exalted. The important change I made from their rules, though, was that every individual attack in a player's arsenal had its own speed value, changing speed from a simple balancing factor that made people using bigger weapons slower in the turn order to a strategic variable that players could manipulate as they chose which attacks to use. In the ideal situation they would treat the turn order as the board in a game of chess and plan around how to best balance it against the power of their attacks and use it to subvert enemies.
What you see here is the resurrected version of Super Smash Quest: Brawl, entitled SKIRMISH. I re-wrote it for this portfolio as the materials for Brawl were in the alpha stage and as such never reached either full completion or full consistency between the documents; IE verson Alpha 1.00 would have slightly different ability scores or skills than Alpha 1.05, and then 1.1 would TOTALLY overhaul the ability scores and attacks. It was such a mess I had to re-write it. This version is more condensed and polished, though not without balancing issues between the numbers. Below I will address some of the remaining issues:
As Smash Quest was built from the ground up for a specific audience in an IRC chatroom there's very little visual apparatus to deal with things like navigation. We tried a lot of different systems in the past for understanding where things are in relation to one another, including a grid that I had people update via MS Paint, but the only thing that remotely worked without slowing things down was a system of relative positioning that I tended to use. I'd essentially describe a location with a series of landmarks and say things like, "the Goomba by the tree attacks Dragoshi," and "he knocks you over by the waterfall." Other GMs would generalize further by saying a move attacks either single enemies or all of them, adopting a sort of pseudo-Final Fantasy battle system. This version of Smash Quest adds in the "movement unit" system, where relatively large areas of a battlefield are described as fitting in a square unit. Hyrule Temple's cave area would be described as two movement units below the surface, which is five units wide. I found that this works better than trying to describe Smash Bros. type gameplay in meters or feet, but at present it's still a little nebulous and a lot of movement-related additions haven't yet been added. At the very least this system allows players to draw and interact with a map fairly coherently as it's written.
Any time a traditional advancement system was incorporated into the old Smash Quests, which were based on d20 rather than d10 dice pools, it threw the game out of balance quickly. It was a rather odd game in that it ran really long, was projected to run indefinitely, ran extremely frequently, with the GM running sessions almost daily at the time I'd made this system, and frequently acquired new players and dropped old ones. Everybody always started by the same standards, and those standards were usually "level 1," which by the time I made Smash Quest Brawl was about a hundred levels behind the regular, die-hard players that never missed sessions. They tended to make up the first 50 quickly, but this seemed like a model that just did not fit well and tended to go beyond the GM's control, making it nearly impossible to draft up good obstacles or monsters without making serious on-the-spot alterations in the middle of a game.
Smash Quest Brawl's advancement system was scaled back for those reasons and now depends on players acquiring a greater variety and specialization in their abilities and items more than on sheer power. The primary rewards for beating enemies aren't EXP but coins, and each "mission," as this game does run on a mission-based format rather than a campaign-based format, was rewarded with a sum of coins as well as a new move. Most factors outside of the moves that players collected and their own stats were equipmentized for that reason. While players' stats aren't completely static they advance very slowly in increments of 1 per major plot point. Since 1 point in any stat meant one extra dice in any number of rolls or one extra increment of damage in any number of attacks this was a significant reward without being out-of-control or difficult to predict. It also meant that beginning players wouldn't be so far behind veterans that they couldn't participate in particular sessions or wouldn't have any significant impact on a fight. What this also means, though, is that enemies advance just as slowly as the players do and have to be thought of not at particular, arbitrarily set power levels to correspond with a group's current advancement over a spectrum of possible levels but rather in terms of relative power to a single player, role in a group of enemies, and overall versatility.
So what do players do when they aren't fighting things? Boy if that isn't the million dollar question. Although I always tried to incorporate some sort of skill system into this game to make what's happening outside of combat part of things I never quite seemed to nail it. One of the reasons for this is that it's just patently absurd to come up with a list of skills for characters in a Nintendo-themed universe centered especially around the Super Mario Bros. franchise. First, how do you make skills for the Mario games? What are Mario's skills, for that matter? Second, although some games like Metroid and Zelda have clear-cut room to base skills in, what happens when players are faced with a long string of sessions in settings where neither set of skills are remotely used? Frankly the Questers just never had a need to do any hacking, intimidating, translating foreign languages, or forgery; things like item creation just didn't have any place in this game; and it was more interesting to see them try and work up creative solutions to puzzles and traps with the items they had on hand than with a series of numbers on a sheet. So, simply put, beyond the combat statistics there are no more stats because there just don't have to be any. The combat is the game and it could just as easily be played for a quick Friday night session between several players who have all the Smash Bros. characters divided up between them and want a more strategically flavored game without the hassle of knowing how to wave-dash. After many years studying game design I realized that not everything has to fall in the realm of RPG tradition in order to call itself a good tabletop game and that role-playing is a matter of imagination and storytelling more than a matter of what ingredients you throw into the game design pot.