May Contain Nuts

This is probably the eighth time I’ve re-written this entry, so hopefully it hasn’t gotten too long in the tooth through the numerous re-writes. I’ve been trying to work out an effective format for addressing the three remaining lessons I’ve learned from MOUL’s year-long run, and doing so without turning out a novel-length post is a considerable challenge. These three lessons all center around involving players in the game without forcing them to become addicted to it, and cover story, repeatable content, and content formatting. So let’s dive in (again, and for the first time).

As I mentioned in a recent post on the MOUL forums, Cyan has faced an uphill battle against time, money, and manpower constraints when developing Uru since UbiSoft decided to muck up the game’s formula 8 months before release, and these battles were only further exacerbated by the brief timeframe that GameTap gave a somewhat understaffed Cyan for re-launching the title into public beta at the end of 2006. These constraints have resulted in additional changes to Uru’s original game plan (episodes, live-only story) which, while more subtle than UbiSoft’s single-player campaign mandate, had a similar impact on Uru’s ability to succeed at its own game. I firmly believe that Uru is a concept that can succeed, both artistically and commercially, but all of the pieces to Uru’s development puzzle have to be in place for it to work well at all. You can call me a blind optimist if you like, but I still don’t think Uru as it should be has been given a chance to work… so far we’ve only managed to prove that “Uru Live Lite” isn’t a good business proposal. Twice.

That said, Cyan’s more limited resources require some smart game design decisions that would probably take the game to places other than it was originally intended to go. Still, when given the option of an under-executed original vision and a well-executed alternative, I’d have to go with the alternative option. Here are a few ways that I think Cyan could create a successful “alternative” Uru; one that has all of the pieces in place, but executes them smartly on a tiny budget.

Content is obviously a huge issue for Uru. It is, after all, a content-driven MMO rather than a grind-driven or competition-driven MMO. However, Cyan simply cannot provide Uru with enough content to keep the rabid puzzle-solvers sated, especially with their limited staff. As a result, focusing on single-use Ages with solve-once puzzles is not the most optimal use of resources, because for most players, once they’re done solving those puzzles, there’s little motivation to return to those Ages again, and then they quickly get bored and leave. An alternative Uru needs to focus more on repeatable gameplay and smart re-use of existing content to keep players interested and keep production costs at a minimum.

Repeatable gameplay would most easily come in the form of in-game mini-games. There are already several examples of this sort of content in both Prologue and MOUL, but they seem more like ways to test the water than really well-developed concepts for getting players to kill time in-game.

Small table-top games like Ahyoheek are nice distractions, and with functional leader boards could even fuel more regular play (especially with a game-wide board for players to vie for spots on), but it’s not something that will hold attention for hours on end, and most players will get tired of the D’ni version of Rock, Paper, Scissors before too long anyway. Still, it’s a nice start, and something to fall back on when you’re out of other things to do.

More exploration-based games like the user-created Marker Missions fill another niche, but can only be played solo (which is good for the loner types but not as useful for making actual games). The original Ubi beta for Uru in 2003 had 2 additional game types: Capture and Hold, which were played with teams in a single Age, and had a set time limit. In Capture, you ran around collecting markers for your team, and everybody playing could see all of the game’s uncollected markers. In Hold, the markers you collected didn’t disappear, meaning the other team could steal markers away from you. In both games, whichever team had the most markers at the end of the timer was the winner. They were fun and fast-paced games, and I still don’t quite understand why the time wasn’t devoted to making them work in the final release; they disappeared shortly after Ages Beyond Myst’s announcement at E3 2003, never to be seen again.

Finally, we segue cleanly into strictly competitive mini-games. Typically quick and constrained to a game surface like a wall, a life-sized game board, or a track, these games wouldn’t appeal to everyone in Uru’s crowd, but would hopefully provide something to entice new players into the fold, as well as give those interested something more exciting to do with their time in-game when not out puzzle solving. These games are also typically great for spectating, but Uru has traditionally made getting to these games tedious at the best of times, and downright frustrating at worst, which I think has soured their appeal for most people. Beyond making them easier to get players and observers into, areas like Jalak and Gahreesen’s Wall need to provide places for spectators to gather, a solid way to determine scoring and victory, and ideally a set of leader boards in a public place to showcase your accomplishments and give you something to work toward, if you enjoy that sort of thing. The Wall has more of these requirements than Jalak, but I think that if both were tweaked to include this complete feature set, they would both be fairly popular hang-outs for the more energetic segments of the Uru community. Releasing planned content like the Kahlo creature races would only add to the number of possible things to do in the game during story down-time.

Beyond mini-games, though, content has to be recyclable for story and general gameplay purposes too. For instance, consider Er’cana - quite possibly the only real forray into repeatable gameplay that Cyan has made. Er’cana’s puzzles are almost all complete throw-aways that have nothing to do with actually operating the machinery in the Age. It’s a big set of “get around this broken pathway” puzzles with power switches at convenient intervals. The only really sustainable puzzle is figuring out a good pellet recipe, and that was generally short-cutted around through the communal efforts in the forums. After that, the Age became largely useless, and the machinery didn’t seem to have anything to do with the actual pellet-making process, which was a curious shift from Cyan’s typical attention to such details. I think that the concept of Er’cana can be seriously expounded upon by at the very least factoring in machine operation and supply management in basic forms. My ideal super-complicated implementation would call for a ‘hood-instanced mega-Age with weather patterns to learn and track over months or even years, and dynamic vegetation growth and harvesting that responded to changes in the weather (i.e. a long drought would cause plants to wither and the ground to become cracked mud). Creating and testing such a system would obviously require considerably more resources up-front than the far simpler infinite supply system and basic puzzle mechanics of Er’cana, but I think the Age would last a LOT longer as a result, and complex puzzles like tracking weather patterns seems like something right up the alley of some of the more obsessive Uru fans. As a launch Age, it would give players something to spend at least a few months pouring over obsessively, without putting a multi-month delay on other content drops while the beast went through development and testing.

As a final point on content, adding new material to existing Ages was another promise of the original Uru which never came to pass in MOUL, a fact I find most unfortunate. I think that part of this was related to the 4-year-old setpieces that Cyan had built versus the new direction in which they were moving the story. To that end, I think there is a need for a set of content that can be repurposed for pretty much anything, and I think that the Path to the surface could provide the perfect opportunity for such a set piece. It’s largely modular, and could be broken into discreet sections by strategic cave-ins; it runs through any conceivable section of the D’ni Empire you need it to; when tied into the GZ coordinate system, you can drop all kinds of subtle clues to players leading them to new content in already-explored areas; KI access restrictions could be integrated into the doors to keep players out until they’d completed any pre-requisite story arcs… the list of potential uses goes on and on. Especially for smaller story-related material, these sorts of simple expansions to existing areas could have a huge impact on the depth of the game world and provide a cheaper alternative to building new Ages from scratch every time you needed a new story element unveiled.

This leads us inevitably to the story. I think Uru suffered from the same fate that befell the new Star Wars trilogy: a good story poorly executed. However, while we only have Lucas’s inability to write his way out of a paper bag to blame for Episodes 1-3, Uru’s story failings have a myriad of causes that stem from a lack of time, money, and manpower.

Since I’m already adopting the viewpoint that a new Uru needs to be a complete reboot in terms of development anyway, with a lot of time being devoted to building large sustainable content chunks before release, I figure I might as well go whole-hog here. Uru’s storytelling technique is unique in the MMO genre because it abandons the notion of player-controlled, player-instanced story for that of a global tale being told in real time, concurrent with the progression of time outside the game. In Prologue, this was handled through regular, live, in-game events that moved the DRC plot along, with a parallel solo story arc involving Yeesha and the Bahro that could be explored at your leisure. MOUL abandoned this solo story arc concept for new development, focusing instead on the much cheaper-to-produce live events as the exclusive manner in which story was unveiled in the game. Unfortunately, this method didn’t work very well, and players more often than not became frustrated with their inability to watch the game’s story unfold first-hand, and instead resigned themselves to learning about the story through out-of-game means like the forums.

Hopefully, I don’t have to tell you that having players leave the game to learn about the story because it’s easier than trying to wring it out of the game itself is a bad thingâ„¢. Eventually, even the simpler methods of maintaining a permanent storytelling record in MOUL, like Sharper’s journal, stopped being updated entirely. Regardless of the fact that Sharper, as a fellow denizen of the Uru universe, probably stopped updating his journal once he found out it wasn’t exactly private anymore, some way to keep that information flowing was necessary, and it wasn’t maintained. Removing it cut off the only remaining source for catching up on events in-game without trying to find someone else who knew what was going on, and that was bad for the story’s delivery.

Beyond that, realtime events ended up cheapening some of the story, in my opinion, by turning them into second-hand recountings of really exciting stuff which, like vacation photos, are really only cool to the people who went with you. Story arc points like the unveiling of the Bahro civil war could have been handled much better, I think, through a player-controlled reveal much like the original Yeesha journey’s reveal of the Bahro’s very existence, rather than Sharper recounting That Time He Almost Died in Negilahn and That Time He Shot a Bahro in Noloben.

Not everything is suited to a real-time event in Uru, but not everything can be placed in the hands of player progress either. Wheely’s death and Watson’s return, for example, had to happen once and only once, as there was only one Wheely and only one Watson for these things to happen to. If someone joined in November and was able to witness Wheely’s death first-hand as if it was happening for the first time, it would certainly be more informative for that player, but it would also violate Uru’s premise that all of this is actually happening in the real world. Some things can even be a combination of real-time and player-time events (I like that term, I think I’ll keep it). For example, many many players were angry that they didn’t get to see Yeesha’s speech in the season finale, and so missed their only opportunity to see her again in person. As an alternative, let me propose the following: upon completing the Path of the Shell Ages, you arrive in a private instance of K’veer so as not to be disturbed. Yeesha appears before you in a triggered sequence that plays once for all players upon reaching this point. Yeesha reveals the salient points of her speech, but leaves out the “kthxbye” part. This gets used in her real-time appearance and speech in Exodus, which obviously only happens once. After her departure, the Yeesha in K’veer becomes a hologram for anyone else completing the Path of the Shell Ages, and an additional line or two detailing her departure could even be added for consistency and explanation. This way, everybody gets to see Yeesha regardless of when they complete PotS, and the real-time event where she departs to draw the Bahro away is preserved as an event for the history books. Provided MOUL’s sole animator hadn’t spent the entire development period animating all of those Bahro around Kerath’s Arch, Yeesha’s 2-minute speech could probably have been cranked out in a couple of days, plus maybe a little overtime (or minus a couple of dogfighting Bahro).

On one final note, I have thus far been very intentionally not mentioning user-created content beyond Marker and Jalak games because that’s a whole ‘nother bail of barbed wire that I’d rather be saving for another post that isn’t already several pages long :P.

This entry was posted on Thursday, April 17th, 2008 at 2:57 pm and is filed under Computing, Game Development, Myst, Myst Community, Uru Deconstruction. You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.