Archive
End-Game Primacy: Part 3
Part 3: Squaring the Circle
If you’re reading this you probably either came straight from the Introduction or were patient enough to work through Part 1 and Part 2. For simplicity, here is the short form of my theory on the ideal MMO content:
End-game primacy is the idea that the bulk of any MMO development time needs to be spent on maximizing end-game content and that this goal is best achieved by embracing complex systems driven by player interaction, rather than static content. Or put a different way: an MMO’s real story begins after the scripted story ends.
As I discussed in part 2, complex systems can be consumed by players longer than static content, but they are also significantly harder to create well. What works in a single player game may not work in an MMO, and vice versa. It is a lot easier to account for a few players’ actions than it is to predict the impact of millions. Millions of players is millions of opportunities to undo any work developers put into the game. Structured static content offers a lot more control for developers. Instancing, phasing, personal stories, and other tools isolate players from the larger game population, while simultaneously making it easier to tell a story to the player. It lets developers preserve the narrative format of single-player games. In contrast, unstructured simulations take control away from a development team. The simulation elements are built into the game world and then left to the players’ whims on what to do with them. This is a frightening prospect because systems not designed to scale particularly well can tend to spiral well out of control, at the detriment of other aspects of the game. For instance, if players can build structures on game landscape, the game world will almost definitely end up suburban. If players can build in a particular spot, they will if for no other reason than they can. Expecting that it would not happen is betting against the odds.
Qualities of Good End-Game Content:
End-game content systems needs to ebb and flow organically, self-regulating through internal feedback mechanisms. In the above example of players building on the terrain, physical game space is limited while the numbers of players who can (and will) build houses has no theoretical limit. Instancing off the construction projects or expanding the physical land mass using some kind of terrain generator are two ways you can address the finite space. I’m not stupid enough to think that the second of those two options is exactly feasible. In many cases, it may be impossible. The alternative of instancing off construction projects or imposing artificial limits on where players can build to control the urban boom misses the point of building a game with lots of players in the first place. To make the system work, there needs to be a natural feedback mechanism in place. For housing, if players can create them – they must also be able to destroy them. Determining the ratio between building and destroying would require a fair amount of find tuning, however. If it’s hard too build and easy too destroy, no one will bother building. On the other hand, if it is to easy to build and to hard to destroy, you still end up with a sprawl.
Going back to Part 2, auction houses have natural self-regulation through the invisible hand of supply / demand, but they lack a mechanism to contribute to player narrative. Systems that have ways to report activity and interactions back out to players are another hallmark of a good end-game system. Players can buy and trade all day on the auction house, but if there is no mechanism to report major fluctuation in trade, players will likely feel isolated in their game experience. Even if such a mechanism exists, it probably does not tie into other systems. Ideally, if a market change occurs, it should be in response to in-game events. Knowledge of these events provides players immersion, rather than just leaving them staring at a user interface spreadsheet tracking their purchases. A good end-game content system will let developers track and aggregate player interactions within and across systems to facilitate narrative development. In the housing example above, a mechanism to monitor and encourage players to cluster buildings together facilitates the construction of towns instead of haphazard sprawl. For instance, perhaps building in close proximity to one another increases their natural defense. Two houses have the defense of three; three the defense of five; and so on. A shack in the woods could be torn down in a few minutes, where several dozen buildings together takes over a day. Several towns merge to form a city which takes a week to siege. And each of these units (e.g. town, city) provides an entity that developers can track and use as a piece to a personal player narrative that is not separate from all other player narratives.
An Opportunity in Player Social Landscape:
These are simplistic examples, to be sure, but it gets to the point of what I’m trying to explain. I cannot suggest an end-game system that will work in every MMO. Each game has its own limitations based on engine, design philosophy, resources and a host of other factors. However, there is one area in many MMOs today that I believe remains underdeveloped, but which also has great potential to add depth to end-game experience and help developers create quality evolving narratives in the process. While most developers spend plenty of time shaping their landscapes and dungeons and are loathe to let players ruin that art, social terrain is an area that does not currently have structure and therefore cannot be destroyed.
The fact that I can often only be the member of one guild and my relationships to other players are defined as “friend” or “not friend” is fairly simplistic. This flat and binary social structure is surprising given that large numbers of players are a feature of MMOs. Certainly, social terrain is difficult to communicate meaningfully – even Facebook struggles with it – but games need more than a few binary associations to link players. In life, we play many roles and in games we do as well. Is there a particular reason that a player can and should only belong to one guild in a game? I would argue no. Further, guilds are generally the only mechanism to permanently join players in games. This is an artificiality that misses the point. Letting players create different kinds of associations among themselves and build on the quality of those relationships through game play would be a fantastic way to add depth to a relatively one dimensional system.
Imagine if player organizations came in many different forms, which were not binding to individual players. Guilds might still exist as the highest form of player grouping, offering resources like shared banks and chat channels. Others might exist for circles of friends to communicate. These circles could extend between guilds and offer benefits like being able to travel immediately to your friends’ location. Still others might exist for trade groups: players who regularly share crafting resources to each others’ benefit. Being a member of this group may offer additional crafting benefits. Player organizations like this only come into existence when the game recognizes a cluster of individual player associations strong enough to warrant it. When players “friend” one another they select the kind of relationship they want to build. Small groups of friendship-linked players might warrant a “friend circle,” clusters of adventuring-linked players might warrant a “guild circle,” and clusters of trade-linked players might warrant a “trade circle,” and so on.
Natural player clusters provide the basis for player groups of all types.
These interlocking social circles would create an inherently organic system that already lies on top of almost any game’s existing game play. Anchoring these circles into less organic game systems could vastly improve and regulate end-game play. For instance, if a game allows players to fight for control of game regions, a map which only has guilds will be one dimensional. Add in trade organizations that may operate across regions and suddenly you have two dimensions with the same players. This in itself is a story, and one that with the right tools can be communicated back out to the players. Using the housing example above, anchoring the ability to build houses to player associations may be a way to organically limit the growth rate of construction in a game. Player groups may be the unit to build (instead of players) and they may only be eligible while the quality of relationships between members remains high enough. Social pressure does the rest. Capture that narrative and push it back out to the affected players and perhaps one or two tiers out (using the same association network). Players would learn about attacks on towns that their friends live in or where their trading partners do business. The game tells a story that people care about. By necessity, this needs to occur in near-real time, a challenge in itself, but done right could absolutely change the face of MMOs today.
Conclusion:
As you can guess, there are a lot of things to consider in anything as complex as a virtual world, so these theories are as much a work in progress as anything else. I hope that they were, at least, somewhat thought provoking. There are plenty of technical limitations preventing much of this from happening in the near future, but adding one new end game system to new MMOs should not be out of the realm of possibility. Hopefully over time some of those will be captured as best practices and replicated out, leaving room for newcomers to add even more dimensions to virtual world game play.
End-Game Primacy: Part 2
If you don’t know how you got here, head back to the Introduction or Part 1. Otherwise, read on:
Part 2: Building the Theory
In a perfect world, developers would just make content all the time to keep players of all kinds entertained by the game world, but that is not possible. Developer resource constraints limit how much content a team can produce in any given amount of time. As a result, there is a natural design triage where teams must choose to implement new features that can most positively impact the game. I have seen people suggest before on forums that this problem can be solved by hiring more programmers, designers, and artists. That is not a real solution because the numbers you would need to hire to eliminate the problem are probably staggering. Further, that many people would bring a host of of organizational issues that would probably impact quality in unintended ways. Given these issues, I am not even considering that avenue an acceptable solution to the problem.
Further, resource constraints are not a problem unique to the gaming industry. In the military, people who didn’t understand the principles were described as “good idea fairies” because their decisions resulted in ineffectual changes that only served to drain resources in time, money, and manpower without actually effectively improving a situation or organization. Unfortunately, the military has been so awash with resources over the past decade, much of this behavior isn’t penalized the way it should be. That is not an option for a gaming business. So I’m going to assume that, at present, the average developer produces content at a mostly fixed rate thanks to effective resource allocation. The way to improve the output of the equation is to find ways to make the content created last longer when faced with players’ content avarice. This is no small feat, given that even veteran game companies sometimes fail to retain players. I cannot claim that it is fool proof, but I think it is possible.
The Theory:
Accepting the reality of resource constraints leads to the first half of end-game primacy: the bulk of any MMO development time should be spent on maximizing end-game content. Most MMOs embrace some form of individual progression system where players consume static content until they finally hit a hard cap on player development. Any content consumed along that progression track essentially comes with an expiration date. It is only consumed for a very small portion of a players overall game experience. In contrast, content at the end-game can be–and is–consumed for much longer, even when it is static. If enough static content exists at the end-game, developers can eventually issue an expansion, pushing the progression wall a little further and starting the cycle over. The most successful games already embrace this half of end-game primacy. Others spend too much time on the initial progression, expecting to have time to expand later only to realize their players did not feel like waiting around. While even this strategy can work, pushing static content to players is still limited. Players still consume it and content themselves with repetition and brand loyalty as the glue that keeps them around long enough to see the next cycle.
Arguably the method of pushing static content is more in line with standard software development practices like object oriented design and agile development. If that was the only way to build content, I think it would be the best way given those advantages, but there is another option. Going back to Ralph Koster‘s quote from Part 1, I want to highlight a particular portion:
You can try a sim-style game which doesn’t supply stories but instead supplies freedom to make them. This is a lot harder and arguably has never been done successfully.
There have been a few attempts at more sim-style content over the past few years, but it is definitely the harder model to do right. That is probably why so many companies choose the safer route. The second half of end-game primacy is that complex systems driven by player interaction provide more longevity than static content. These systems differ from static content in that they allow players to pull content on-demand. An example found in many current games is an auction house. An auction house is always there for players to engage in when they want it. Some players will use it some times, others will use it never, and a rare few will use it as if it is the game itself. It provides a constant stream of content that becomes more dynamic and interesting the more players interact, improving the game play experience for everyone. It can go for years without ever losing player interest, providing maximum impact for developer resources spent. Even if player progression is expanded, the auction house grows with that new bound, while older static content like dungeons generally get left behind.
Limitations:
On paper, dynamic systems like auction houses are superior to static content because they offer players new experiences over longer periods of time. I recognize, however, that they are not all quite so easy to make in practice. Economic models are fairly well developed, so predicting player economic behavior is substantially easier than say, predicting how a player will respond to a powerful monster or even another player. These models make it easier for developers to build tools and mechanisms to govern that behavior (like the auction house) but modeling social behavior is a different animal. Implementing many player versus player systems, for instance, end up being a lot like trying to make a communist economy. It is great in theory, but horrible in practice. There are few games that successfully implement player versus player mechanics and end up with a lot of digital pacifists running around cooperating.
Given these challenges, the end-game systems need to be designed in such a way that they do not cause more harm than good — no small task, to be sure. If this can be accomplished, I feel the amount of development time that these systems entail far outweighs the benefits of spending that same development time creating static content. The initial upfront investment might be higher, but over the long run they end up costing far less in terms of resources. Taking in total, these ideas all left me with the conclusion that bulk of any MMO development time needs to be spent on maximizing end-game content and that this goal is best achieved by embracing complex systems driven by player interaction, rather than static content.
But a principle is only useful if you can make good on it, so in Part 3 I will give a few of my ideas on building meaningful simulations at the end-game of an MMO.
End-Game Primacy: Part 1
Part 1: Exploring Principles:
To suggest that I have a better way to build an MMO is to suggest that there is a problem with the current model. That’s not being entirely fair because there are plenty of good MMOs out there right now. However, it has been my experience as a player that innovation seems to have slowed as more developers choose to replicate the same MMO models across new franchises rather than take big risks of new kinds of MMO game play. My theory is meant to be an alternative, and I hope justification for someone to build this concept. I’m going to start with what I believe needs to be the ultimate goal of any MMO and then work backwards on how I think there is a better way to reach that goal that not only makes a better game for players, but also meets the business needs of developers and producers.
1) Successful MMOs need player volume to make money. Massively multi-player online games are inherently expensive to produce and maintain. From a business model standpoint, this means that the game needs to attract enough players for a long enough period of time to recoup initial development costs, provide future maintenance and development costs, and also make a reasonable profit for the developer and producer. It doesn’t matter if the business model is free to play with micro-transactions or subscription based. A consistent player volume is required for both. This need for money is a hard truth to swallow for those most passionate about these games (myself include) because we tend to idealize the art form. But a healthy player population is not only good for business, it’s also good for game play too (more on that in a moment), which is a goal even the most doe-eyed idealist gamer can get behind.
2) A stable population is a function of player retention . To reach the idealized population sweet spot where the game world is bringing in enough money to meet the above objectives, players need to be retained over a period of time. In an ideal world, which I’m going to refer to as “Boom-town” (figure 1), players will opt into the game world and choose to never opt out. This would result in near continuous growth as more and more players try the game. The second scenario, which I’m calling “Bust-ville” (figure 2), shows what happens with many MMOs these days. Players flock to the new game, but their average retention time isn’t long enough to let new players replenish their ranks. The population falls below the theoretical “healthy population” line and fails to make enough money or keep game play interesting enough to attract new players. The last scenario, or “Just-right-shire” (figure 3), is the most realistic goal. The initial spike of players is high enough to get above the healthy population line, and average player retention time is long enough that the population never drops below that line. The game reaches a state of equilibrium or steady sustainable growth.
3) Player retention is tied to content relevant to a players interest. If content is relevant to a players interest, it should theoretically be fun for the player. As long as that content exists, the player should be retained. It sounds simple, but it’s honestly where this gets wildly complicated. Not surprisingly, fun is different for different people. Some players will be attracted to story, others to exploration, others to combat with other players. Most will move back and forth between all of these elements at various times during their retention. There simply is not enough time and resources to make content to appeal to everyone at all times. Even if a game developer decides to focus on appealing to a narrow population group, players consume this content far faster than developers can make it. Consider the quote below from Ralph Koster:
If you write a static story (or indeed include any static element) in your game, everyone in the world will know how it ends in a matter of days. Mathematically, it is not possible for a design team to create stories fast enough to supply everyone playing. This is the traditional approach to this sort of game nonetheless. You can try a sim-style game which doesn’t supply stories but instead supplies freedom to make them. This is a lot harder and arguably has never been done successfully.
Koster is specifically talking about stories, but this holds true for if you substitute any kind of content for stories. Even the most successful MMO development teams today struggle content fast enough to keep their players from consuming it too quickly. At best, they skirt keeping their populations above the healthy line with injections of content as expansions. At worst, they experience Bust-ville, where their initial content release and subsequent content production is too slow to keep player retention up long enough to see population stability. Repetition and pseudo-random elements in the static content can alleviate this somewhat, but these are band-aids to the larger issue. Other variables like brand loyalty or lack of competitors can also extend the life of this content, but they still cannot compete with new content. Even the best roller coaster in the world gets boring after the one hundred forty-seventh time for all but the most extreme roller coaster enthusiasts.
Continue reading more Part 2: Building the Theory or head back to the Introduction to navigate from there.
End-Game Primacy: Introduction
This month’s posts are going to go a bit more abstract and theoretical than the last few I’ve written. This is intentional. While talking about popular upcoming games might draw more traffic to the site, I feel that recently I have not put enough of myself into this blog. I love talking about other games because I love playing them, but those other games were never meant to be the centerpoint (at least not until I’m making them). So today I want to share a working theory I have about how to improve the quality of MMOs today. This theory has developed over time based on reading, personal observation and experience, and many conversations with friends patient enough to listen to me. Here is is up front:
End-game primacy is the idea that the bulk of any MMO development time needs to be spent on maximizing end-game content and that this goal is best achieved by embracing complex systems driven by player interaction, rather than static content. Or put a different way: an MMO’s real story begins after the scripted story ends.
To keep this manageable, I broke my ideas down into three sections. Publishing each part on different days might drive more traffic to the site, but I decided I would rather put this all out at once since it needs to stand together. If you already agree with end-game primacy after reading the short version above, free free to skip to part 3 where I offer some ideas on how to implement it. If you want to see how I came to the theory, go onto part 2. Or if you want to see me talk about some basic concepts related to MMO business models, head to part 1. I hope that this breakdown will also make it easier for people to comment on various sections. Since this is the first time I’m posting this way, please provide feedback if you prefer this format for longer posts. And with that out of the way, I give you my opus:
- Part 1: Exploring Concepts. Development of principles leading up to end-game primacy.
- Part 2: Building the Theory. Construction of the end-game primacy theory.
- Part 3: Squaring the Circle. Ideas on how to build meaningful end-game content.
The Quest
Today’s post is a bit significantly less about game development and the game community, and a bit significantly more about me. If you’ve taken the time to read the About section, you may have seen that I aspire to be a game developer. I’ve undertaken a personal quest to eventually break into the game industry and I’ve decided to chronicle that journey. Periodically, I will make posts like today’s categorized under “The Quest,” which will highlight my progress and hopefully celebrate milestones on the journey, though they may be few and far between since I have a sneaking suspicion that that this is going to be slightly more difficult than killing 10 boars for a little bit of gold and experience.
My educational background is – shall we say – less than ideal for making a transition into the gaming industry. I have yet to see a single job listing for someone with a bachelor’s in history (if anyone reading this finds one – let me know). I’m not without hope, however. While most job listings call for an educational background in computer science, graphic design, web design, networking, public affairs, or marketing, every now and again a very successful developer sneaks into the mix with a much more colorful background. For instance, Greg Street, a lead systems designer for Blizzard Entertainment, has undergraduate degrees in biology and philosophy and a PhD in marine science.
While I don’t have a PhD, my master’s degree in intelligence studies at least has the potential to be as useful as marine science. Being able to do analysis and understand complex problems definitely would be an asset to a game designer. But these are soft skills that can only augment existing knowledge. They don’t stand up well on their own. To that end, I’ve recently enrolled in a local information technology retraining program. I’ve been focusing my time and attention on software development and programming languages. While the course has me working on some programs with more business and commercial applications, I am also working on some simple games.
The current short term goal is that in a few weeks/months you may see some of my early attempts at game development hosted here on the site, and maybe eventually on your own mobile device. We’re still a long way off from that, but there you go – quest accepted.
questproquo 