mistakes
Latest
Destiny dev: DLC mistakes won't be repeated
Destiny designer Luke Smith recently addressed concerns over Bungie's future updates for the game. Namely, Smith said "the mistakes [Bungie] made with the DLC1 reward economy will not be repeated," in a NeoGAF thread, admitting the developer's previous attempts at expanding the first-person shooter with add-on content resulted in a few problems for players. Smith claims the developer will avoid mistakes such as "vendor gear invalidating the effort of [Vault of Glass] Raiders" and exotic gear upgrades resulting in a talent reset. "Our philosophy about rewards/loot continue to evolve as we see how players play and react," Smith wrote. He noted that item drop rates appear to be "much improved" in the Crota's End DLC compared to Vault of Glass, and that Bungie plans to "improve acquisition stories and frequency" as well as "lessen the grind and get players to the fun parts of their arsenal faster." It issued a hot fix for Destiny in December to boost the drop rates for the Crota's End raid mission. [Image: Activision]
ArcheAge scrambles to fix disconnection issues after update
ArcheAge launched a big update yesterday filled with exciting new features -- chiefly, new territories that players can capture, build castles upon, lay siege to, and so forth. At least, you would be able to do any of these things if you were one of the lucky few players capable of logging into the game, which has not been the case for a great many players since the update went live yesterday thanks to serious disconnection issues. As of 7:45 a.m. EST this morning, the official Trion post on the subject says the studio has devised a new build to correct the issue, and the servers were brought down early this morning to apply the patch (they're back up now). However, that might not be enough to pacify the players who are agitating for a rollback under the perception that the update's new territory was claimed while significant portions of the playerbase were forced offline. We'll have more on this situation as it develops. [Thanks to everyone who sent this in! Our own AA players are in the same boat!]
Derek Smart responds to Line of Defense early access mishaps
So guess what happens when you flag a game as both early access and free-to-play on Steam? Apparently, everyone can get in and play with or without buying the founder's packs that your game is selling. That was the lesson that the Line of Defense crew learned last week when that exact scenario took place. Some players were a little miffed by that turn of events, which led to Derek Smart's penning an explanation and response to the situation. Smart lambastes those who peppered the game's store page with negative reviews based upon the unexpectedly revoked access, claiming that those who did not own the game but submitted negative reviews were violating the terms of service for Steam. He stresses that the game is currently still very much in testing and access is not being given away to any form of media simply because the game is far from feature-complete at this time. You can read the full update on the official site.
The Mog Log: Happy birthday, Final Fantasy XIV
Congratulations, Final Fantasy XIV! It's been a year and you're still going after the relaunch, much to the surprise and consternation of the many people who were hoping for the opposite outcome for... well, I'm not clear on that exit strategy. Bragging rights, I guess. The point is, you turned out to surprise pretty much everyone, you've been posting incredibly solid numbers for a while now, and you don't seem likely to go anywhere in the near future. You can take a load off, maybe take a nap. Now that I've gotten the congratulations out of the way, let's talk about Final Fantasy XIV and the many ways that the designers have screwed up so far. Sort of. I mean, over the past year I've been more than willing to fire with both barrels when a screwup was made, which has happened... about once every major patch. But here's the thing: I'm glad to see that happening, on some level. It gives me hope for the future.
Why WildStar's name reservations were screwed up
So WildStar's name reservation system didn't work quite right. It's working now, but when it went live it wasn't working at all, and for a first-come-first-served thing that's kind of a catastrophic problem. Compensation has been announced, but why did everything go wrong? Carbine's director of operations posted in the forums about how things went from bad to worse and where the breakdowns in communication took place. The short version is that it started when a big information drop introduced a lot of new assets to the site, causing even more load than was expected for the page when the name service went up. After that was handled, however, another problem surfaced with the site's feedback, leading to what is described as the server performing what amounts to a DDoS attack against itself. And once that was fixed, another problem surfaced. If you'd like to see the whole breakdown in detail to understand how everything got messed up, take a look at the full post on the official forums.
The mistakes of the World of Warcraft
It's been a long time, hasn't it? World of Warcraft has lasted ten years, and in that time things are bound to go wrong. It's inevitable. Things fall apart, the center cannot hold, I make references to William Butler Yeats and then talk about video games. No game lasts as long as World of Warcraft without making some bad steps along the way. Like Indiana Jones stepping on the wrong tile, all we can do is clamber back up. Some of these were completely unforeseen, others in retrospect were pretty obvious, but at the time not so much, and others you have to wonder how they managed to make it live in the first place. We're going to talk about them now. Vanilla WoW: The PvP ladder Before the ladder, there was mainly world PvP. Spots like the Crossroads in the Barrens (close to a convenient neutral port so Alliance could get there easily) and Tarren Mill/Southshore were hotly contended for almost no good reason at all besides simple factional hatred and a desire from players to kill players. All of that changed with the introduction of battleground and honor rewards, the best of which required a player to achieve a certain rank to attain. What happened next was simple - some players hit upon a means to achieve that high PvP rank, namely, play in shifts. The ladder was abused from the moment of its introduction. People formed groups who hit the BGs together, sure, but that wasn't the abuse part. The abuse came in the form of people sharing their account information and playing a specific character in shifts, literally keeping said character in the BGs for days at a time. If you were trying to play your character fairly, you simply couldn't compete with the five people who were playing that one warlock nonstop until it had all the high ranking PvP gear, and then shifting to the next player's warrior or paladin. I knew people who tried to stay awake for two solid days doing nothing but hitting up Alterac Valley and Warsong Gulch. It was painful to watch. The ladder ended up being removed before the end of vanilla, and it was the best change they could have made.
Storyboard: Nobody wants to play with you
You want to roleplay. Oh, boy, do you ever want to roleplay. You have pages and pages of character backstory, you have your character's voice down, and you can cycle through emotes like a champ. (There's no championship for that, I know. Bear with me.) Your only problem is that when you walk into the room, everyone quietly turns away and discusses how urgently he or she needs to get to the next dungeon, and well, it's late. Bye! It's just like at prom, except this time you can't assume that people were just turned off by your decision to wear Groucho Marx glasses. So why does no one want to roleplay with you? Obviously I can't tell you exactly why people don't want to roleplay with you. There are a lot of variables that I probably don't know about. But I can at least give you some ideas about why you might be encountering some problems and how you can fix them, since you deserve the same sort of fun that everyone else is having. Sit down and let's figure it out; there's no judgment here.
Storyboard: That was a poor decision
Having a new kitten in the house is sort of like watching a slideshow of poor choices. My kitten knows, for example, that the older cat of the house doesn't want to wrestle all the time because she's made this clear in the past. And he knows that right now she's not happy to see him, as evidenced by the fact that she moved somewhere else when he entered the room. Despite all of that information, he still runs right up to her and pounces on her, then acts completely shocked when she smacks him to the ground and hisses with anger -- as if this outcome was not only unexpected but somehow cruel. I've talked before about the importance of making bad decisions with a character, but it's hard to gain the necessary immersion in a character's mind to make decisions that are meant to be believable while still missing the forest for the trees. So instead of offering positive advice, I want to give advice on how to make dumb and short-sighted choices that will later explode in your character's face due to poor reasoning. Think of them as reverse life-hacks.
Ask Massively: You can't cover WoW because of reasons
When I took over Massively last fall, I made myself a little digital post-it note in Gmail Notes that read, "Remember: You work for Joystiq, not studios." Today, I've amended that to also read, "And not commenters." I love commenters, even the trolls sometimes when you make me laugh. You guys provide instant feedback and adoration but also entertainment and skepticism of our ideas. You're the much-maligned vocal minority of readers, and interacting with you guys and being enlightened by your mad and witty and insane posts is a highlight of my work day. But it has to be said that the most bizarre feature of working at Massively is that legions of commenters have deemed themselves better-equipped than we are to decide what we can cover.
Storyboard: Mistakes at the creation level
A lot of character mistakes come down to experimentation, essentially. You have what seems like a good idea, but it turns out in play that it's messy or annoying or unfun or whatever. There's nothing in the world wrong with that; you try something out and it either does or doesn't work. While good concept work does a lot to help you catch these things, sometimes good ideas won't work. But then there are problems that come up time and again based on a fundamentally bad assumption. Something goes wrong right from the point that you click "New Character" because you're making an assumption that can immediately be recognized as a bad idea. So I'm going to go ahead and list a handful of these problems that are bad ways to start off so that hopefully we can all stop making these mistakes in the future and make some exciting new ones.
The Daily Grind: What dumb death do your characters repeatedly suffer?
MMOs offer players many, many dumb ways to die. Personally, I tend to die by grossly misjudging the safe falling distance. I've learned more about how games handle falling deaths than would seem entirely healthy. Guild Wars 2 just kicks you to a waypoint for your idiocy, while Star Wars: The Old Republic is kind enough to let you treat it like any other death. Albeit a particularly dumb one. But falling is hardly the only way to kill yourself and feel like an idiot. You can jump into something harmful and not remember to move. You can pull when the tank, healer, or both are away from the keyboard. You can even go AFK yourself in an area filled with things due to respawn in the near future. And while some dumb deaths are accidents, today we want to know what dumb way you keep dying in your games of choice. Even if yours is also falling. Every morning, the Massively bloggers probe the minds of their readers with deep, thought-provoking questions about that most serious of topics: massively online gaming. We crave your opinions, so grab your caffeinated beverage of choice and chime in on today's Daily Grind!
The Soapbox: Own your game's mistakes
To the developers of the MMO industry, I say this to you: Your game has some pretty big issues. No, stop. Don't go consult the PR team. Don't talk with the community managers. Don't spend time explaining why those issues aren't really issues. Just say it with me. Your game has some pretty big issues. I don't care what game you call your own; it's still replete with issues, including ones that by all rights should have been fixed months ago. Just say that with me, and then possibly follow it with a "sorry." There. That wasn't so bad, was it? Kind of liberating, actually. There's a lot to be said for owning up to the failures of your game and admitting that some things are just plain wrong. I can think of great reasons to just take a deep breath, eat crow, and just say that part of your game is a mess.
Storyboard: When I was the problem
I do not claim to have any sort of superhuman intellect. If I understand how people are likely to make mistakes in roleplaying and how to fix those mistakes, it's a product of having made a lot of mistakes of my own. Sometimes it's a result of failing to fix them and realizing what would have worked after the fact. And while I'll write advice on how to fix the things that you're doing wrong, I never want to give the impression that I'm preaching rather than practicing. Last week's column was all about what happens when it turns out you're the problem, and there's a J'accuse-style rant if there ever was one. In light of that, I wanted to make it very clear that there have been situations in which my character was the problem rather than some hypothetical example. And so I pulled out three of the most notable examples of places where it turns out I was causing a world of disruption within the group.
The Care and Feeding of Warriors: Warrior mistakes to avoid
Every week, WoW Insider brings you The Care and Feeding of Warriors, the column dedicated to arms, fury and protection warriors. Despite repeated blows to the head from dragons, demons, Old Gods and whatever that thing over there was, Matthew Rossi will be your host. One of the interesting things about my current astonishing obsession with transmogrification and all things related to it has been seeing older itemization. You know, strength and agility plate. Warrior tier 6 is lousy with agility. That's a legacy of the past, of course, and as the design of the game moves ever onward, artifacts like that are left in its wake. After all, most level 70 warriors nowadays move straight to Northrend dungeons and are not likely to look at Black Temple until much later, when farming for transmog gear. The stats aren't important enough to go back and redesign the set. What I really find interesting about this is seeing where the class has been, not just visually but also in terms of design. It's kind of like archaeology (the actual field of inquiry, not the in-game profession) or paleontology, reconstructing the class and its roots from the remainders of what it wore. Granted, I was there, so to a degree it's like excavating Pompeii with an immortal who survived the volcanic eruption of Vesuvius and keeps grumping about how people in his day didn't complain when they were buried in pyroclastic material. Which is a complete lie, by the way, we did nothing but complain about it. But I digress. The warrior class has come a long way in seven years, and the artifacts of past design lie strewn about. New players and even old veterans can be forgiven for making a few mistakes based on the rubble. Let's go over a few.
MMO Family: Mind your massively multiplayer manners
MMO Family is your resource for leveling a gaming-specced family, from tips on balancing gaming with family life to finding age-appropriate online games for everyone in the family. Kids are like sponges, sure -- old saying is old. But are online manners something you really want to leave to chance? Are the interactions your kids so intently follow online the manners you want them soaking up and using themselves? As parents, we know that the habits and attitudes that kids pick up today are what we'll find coming right back at us tomorrow. Teens who are used to trolling in games and forums will have a hard time modulating to a less strident tone in a business meeting. Kids who excuse a lack of scruples with "whatever -- it's only the internet" are due for a big surprise when a thoughtless instant message or careless lack of response to an email slams doors in their faces later in life. As parents who game, we all have hot buttons that set us off: the guy who always shows up late to raids, beggars, you name it. The point is: Have you talked to your kids yet about these behaviors? Are you explicitly (by both word and example) helping them not to grow up to be That Guy? I'm pretty sure we don't need a primer in online etiquette here at Massively, but I don't think it would hurt to share some of the things we wish Those Other Parents had taught their kids before turning them loose in our games. I'll share my dirty dozen after the break -- won't you share your own in the comments?
Breakfast Topic: A crowning moment of noobishness
It seems like we've been playing World of Warcraft forever. Sure, we're all experts now (or at least we think we're experts), but we weren't always epic Kingslayers. We were all noobs once. And we all made ridiculous noob mistakes. As evidence, I shall recall for you a tale of a noobish Fox Van Allen. I had just made the leap from trial account to paid, and a friend of mine had sent me a small care package to get me started in the game. Nothing big, since he was just starting out too -- just a little bit of money. I was very eager to get it, but I had a problem: I couldn't access my in-game mail. That little mail icon in the upper right hand corner of the screen was taunting me. After several frustrating minutes of trying to get my not-so-phat loot, I decided to put in a GM ticket. I explained I had just upgraded from the trial and that WoW wouldn't let me access my mail. I was a little frustrated (no one has ever wanted one piece of gold so badly), but I tried not to let that show in my note. An hour or so later, I got a response from an exceptionally helpful GM. He researched my account and tried helping me best he could. He explained that since I had just paid, there may be some lag in that information reflecting my ability to get in-game mail. The GM then suggested that I should go to a mailbox and try to access my mail again so he could help troubleshoot while the chat window was open. "Holy hell," I thought. "You have to be at a mailbox to get your in-game mail?" Do you have any crowning moments of noobishness? What's the most noob thing you've ever done? Come on, we won't judge. (Too harshly, anyway.)
Fileplanet wants you to play Earth Eternal really badly
What's this taking up one of the center links on Fileplanet? Is it the upcoming MMO Earth Eternal? Why yes it is! Sparkplay Media's Earth Eternal has made it to the top of the free games listing... except for the fact that EE is still in closed beta.Fileplanet's link, while enticing, will not get you instant access into the closed beta. What it will do, however, is sign you up for an account that will let you be eligible to be selected for the closed beta. It will not let you play the game immediately, but it will certainly net you a chance at playing sooner rather than later.According to Sparkplay Media, Fileplanet will be involved with getting the game and the word out there, but it seems they've jumped the gun in releasing their link for the game. It's cool, we all make mistakes.As to what special in-game items Fileplanet members will be receiving for signing up and playing, well, that's still a secret to everybody.
GDC09: Spending time with the cruise director of Azeroth pt. 2
Mistakes of World of Warcraft Kaplan was quick to note that Warcraft was far from perfect, and he wanted to highlight some of his own mistakes inside of the design. The first mistake was the idea of the "Christmas tree effect," otherwise known as having so many quests in a quest hub that the minimap lights up with exclamation points like a Christmas tree. While players enjoy this, Kaplan wanted to say that the developer loses call control over the player at these points, as the player will not read any quest text in their clicking frenzy. There's no control over what quest leads into what or which order the player will do the quests in. The second was the internet adage of "too long, didn't read." Quest designers don't need to write a book to get their point across with the quests. He brought up that video games had a type of "medium envy," where sometimes they get too preachy with their topics. Games should be fun first, story second. Mystery also falls in this category. The story can provide mystery, but the quest log should never have any mystery to it. The quest log should always point where to go and what to do, but the overall story of those quests may provide some solution to some mystery. Also avoid poorly placed quest chains, like the Chains of Myzrael questline in Arathi Highlands. The Myzrael line was hard to find, ended up spanning 14 levels, and ended with killing an elite mob that was level 44. This quest line was a "brick wall" according to Kaplan, because most players never stuck with it. It's good to have quest chains that span content, but quest chains like this break down trust the player has with the developer. When the player runs into a chain that he can't finish with a monster he can't kill, the player loses trust in the developer's sense of guiding them to fun. He also emphasized to avoid inserting "gimmick quests." His example here was part of the Oculus dungeon where players ride on dragons. These types of quests center around doing something the client may not be able to properly handle. Warcraft was not designed to accommodate vehicles. When developers resort to putting in parts of the game that center around a gimmick, it can detract from the fun of the rest of the game. The horror of collection quests Kaplan's speech ended with an analysis of why people hate collection quests so much, and a few tips on how to make collection quests into a better experience. His problems with the quests stemmed from three areas -- dense creature population, too few of a creature to kill, and having a wide variety of items required for the quest. Having a dense creature population can put off people, especially when there's a lack of the monster required for the quest. If someone has to kill four lions for every one raptor required for the quest, then there's a problem. His other point was that collection quests shouldn't require an insane amount of items. To everyone's amusement, he brought up the Green Hills of Stranglethorn quest chain (a chain he wrote) as the exact thing a designer should never do. Collection quests should be an easily obtainable number of items, and not such a long grind fest with the hope that your required item might drop. Lastly, never have the player question why they're collecting the item required -- it should be clear from the onset. Kaplan brought up the infamous gnoll paw collecting quests, in which gnolls may or may not drop paws upon death, where obviously a gnoll has four paws and not a number between 0 and 1 (which everyone applauded at loudly). Quests should make sense and not become a gimmick in their own right. This causes the player to once again, lose trust. Most of these points that Kaplan has brought up pertain to Warcraft, but can easily be applied to any game on the market. With all of this in mind, perhaps we'll get to see some better design in our MMOs from other developers, now that we're all on the same page... of the Green Hills of Stranglethorn.
Molyneux: 'The industry is growing up,' wants to stay out later on weekends
Peter Molyneux has grown up. In fact, he told Develop this past week that he believes the whole industry has matured. "We're growing up ... when I first started in this industry we were like six year-olds," Molyneaux says, speaking to the enormous development team sizes for games like Lionhead Studios' most recent foray, Fable II, and lamenting the industry's past arrogance towards structure of, well, any kind. "My feeling is that if you're making mistakes when you've got 100 people, that's a really big mistake," Molyneux says, adding, "You'd better make sure that you're making the mistakes when you're a ten or 20 person team; If you're doing that with 100 people, you are throwing millions of pounds down the toilet."That being said, his position on what Lionhead Studios is doing other than Fable-related properties remains ... loose ... to say the least. "There are lots of things I would like to show you now; Within ten feet of you right now is possibly the most exciting thing I've ever seen," Molyneux teased Develop. What could it be?! We may never know, nor may you, as Molyneux remains surprisingly coy in his description. Lionhead has confirmed work on more Fable II DLC, so for the time being, we'll just have to be content with that.
Breakfast Topic: To bug or not to bug
We reported last night that some of the PvP gear was being shown as discounted or even free, and players were reportedly flooding the vendors, trying to pick up cheap gear. Of course, we also warned that taking bugged gear could be considered an exploit, even as some veteran players warned that taking free gear could result in a server rollback, suspended accounts, or even banning.Therein lies the question: did you bite? I can see arguments for both sides: maybe you stood your moral ground, said that that gear wasn't really supposed to be free, and didn't try to take advantage of a mistake one of Blizzard's coders made. Or maybe you said, "well, if it's on the live realms, it must be legit," and looted as much of the gear as you could (and maybe you're paying for it, too, either now or later this week).So what'd you do? This isn't the first time a game-changing exploit has made loot accessible to players when it shouldn't be, so if given a possible exploit in the game, do you grab away and let Blizzard worry about their own mistakes, or do you decide not to take advantage of mistakes Blizzard didn't mean to make and wait for them to fix it while you do things fairly?
