mistakes
Latest
You break it, you bought it
Larisa over at The Pink Pigtail Inn mused on an interesting question the other day: Should you pay for the wipes you cause? Her feeling is not only that you shouldn't, but that the mere fact of offering to pay is offensive to her, like offering hush-money or a bribe. Instead, she says, apologize quickly and confess what you did so that others can learn from your mistakes.I agree with the idea of the mistake-maker apologizing and confessing immediately. This technique also works in real life situations. (I wish it was heeded more often in politics, too.) Further, I vigorously disapprove of ham-fisted reactions from over-zealous raid leaders or guild leaders. Overreacting by /gkicking people (as one of the commenters related) in normal guilds is completely ridiculous. (If you joined a guild who wants to make world's firsts or server-firsts, then you know what you're getting into.) If you are the raid leader then you need to take responsibility for the team you put on the floor. In life, work, politics, and gaming, the buck stops with leadership. Leaders need to pick the right team and remind people who they know are not as experienced or strong in the particular raid situation about tactics, strategy, and common mistakes. Or else they need to chill the heck out. In fact, from a certain point of view, it's not the person who caused the wipe who should pay repair bills: it's the raid leader.Other commenters on Larisa's post offered different payment plan ideas. One suggested a tax on all the loot acquired in the raid. Another suggested that before the raid even begins, raiders should pay an ante to participate, thereby socializing the costs of what might happen. Of course, there is the ever-popular solution of letting the guild pay for repairs afterwards, too. But as another commenter pointed out, repair bills and buff flasks for a 25-man raid can run a guild nearly 400G per run. My feeling is that as long as everyone goes into the raid knowing those taxes are being imposed, it sounds like a fine idea. Or, realizing that mistakes are going to be made, even by the most experienced and savvy players, we could all act like we realize that raising gold is as much a part of the game as raiding, questing, or grinding, and suck up our own repair bills, regardless of who caused the wipe.[Via The Pink Pigtail Inn]
Death Knight class page slip-up
Remember a little while back, when someone accidentally added the Death Knight to the Classes page on the official site? Now the DK class description page is there, although it seems that this too is probably an accident (the DK entry is still gone from the Classes page). As expected, it contains nothing in the way of new information, aside from a fetching misspelling of "Alternative" and a frankly terrifying picture of what looks like a Dwarf Rogue (obviously faked; everyone knows there's no such thing). Still nothing mentioned in "standard bars" about runes or runic power. Also the "Allowable Weapons" (listed as Axes, Defenses, Polearms, Swords, Two-Handed Axes, Two-Handed Swords) still doesn't match up with what we expected (one- and two-handed Axes, Swords, and Maces are what we've been told before). And Blizz doesn't usually call it "Plate Mail;" typically it's just "Plate." Anyway, I vote "slip-up" on this one as well – anyone want to take bets on how long it'll stay up? [Thanks, Hasseo]
Forum post of the day: Rookie Mistakes
Kemmeua of Emerald Dream decided to share some WoWhead love on the official forums. (And by the look of the WoWhead main page it needs a little love.) He shared some rookie mistakes that players have made. For example: Didn't know there were different Zeppelins, thought it was a triflight system so that if I stayed on long enough it would take me to Tirisfall then to Grom and back to Durotar was on there a long time. Didn't know they people were yelling at me to TANK better, I thought tanks plowed things and that's what I was doing Saw alliance in crossroads and thought, "OMG," so I go an whack 'em and get camped for a day yelling for help. Didn't know how to talk to people. Saw a hunter with dual weapons on a Kodo and thought "WOW!" Saw a raid group forming in Kargath for MC, asked them if I can join, getting told I cant roll with the big dawgs at 43. where do u get liferoot if you can't herb? stupid quest giver.
Breakfast Topic: Stupid mistakes
Last night in Heroic Magister's Terrace, I accidentally ninjaed a Cudgel of Consecration. I'm not sure what was going through my head -- I'm currently a Holy priest, and clearly need it much less than the Prot pally tank I was grouped with. Somehow I'd gotten under the impression that it was a healing item, or something. I was, understandably, promptly called a noob and yelled at by several members of the group, and there are a couple hunters out there who may well never group with me again. I profusely apologized to the tank, and we both opened tickets and sat around in the instance waiting for them to get answered. (The response, un-helpfully enough, was "your ticket has been escalated; this may take several days to be resolved.") I gave him the mats for a Major Spellpower enchant, to put on the Cudgel once he gets it, to help make up for my stupidity. We parted on pretty good terms; we're hopeful that the GMs will sort this out. But picking up that item may well have been the biggest "d'oh" moment I've had in the game thus far. Either that, or accidentally taking a point in Throwing Weapon Specialization one time while respeccing my rogue. What's the most boneheaded mistake you've made in your WoW career?
You know you work for a company destined for failure when...
In a recent blog post, Elder Game's Eric Heimburg takes a sardonic look at some of the more heavily worn bumps on the road that is MMO development. Without naming any names, Heimburg suggests developers conduct an intervention if their company meets a certain number of the criteria, lest their game join the cavalcade of mediocre to crappy MMO releases on the market.Among the more prescient of the criteria in this blogger's mind is the one where instead of having a lead designer, companies design by committee, or the one where the publisher imposes changes to the core game from outside. If only fans had a clearer picture of the way their favorite developers were structured, they could apply these criteria beforehand and weigh the odds of a stinker before sinking their hard-earned cash on it. Makes you wonder how many of these criteria Auran met before Fury fell flat on its face.
Player vs. Everything: The importance of morale
We've all been there. Any little thing can start it. Maybe the tank messes up and pulls two groups when he meant to pull one. Maybe the healer was distracted by his cat and some people die. Maybe the mage doesn't watch her aggro and the mobs take out the DPS. Something happens, and the group wipes. The seed of doubt is planted: Can this group really pull this dungeon off? Am I grouped with a bunch of idiots? How big is my repair bill going to be tonight? It's like watching a chain of dominoes. Sometimes, the group can laugh off a wipe or two. But if a simple mistake turns into a pattern of someone screwing up, or if luck goes against you and you have a few simple mistakes in a row, people start losing their morale. Suddenly, people aren't using their consumables (why bother when you're just going to die again?). The tanks and healers get frustrated and start getting sloppy. The DPS gets angry and starts getting cocky. Everyone thinks everyone else is a moron, and each pull is a little less likely to succeed than the last. Each wipe spirals you further down. Finally, people start having mysterious "emergencies" and have to leave the group (do a /who check to see them farming somewhere in 30 minutes). You might not realize it, but your group's morale is hugely important to your success.
Breakfast Topic: When they are not prepared
It is very rewarding to help new players adjust to World of Warcraft. It can also be extremely frustrating. In some cases, I wonder if we may ruin players by giving them too much help, like helping a butterfly from its chrysalis. I remember when I first started playing WoW, I made some serious rookie mistakes. For example I didn't know how to repair my gear until I was level 17 and had no idea that one should train all three talent schools. I got a lot of advice along the way, but I kept more or less to my IRL companions even in game. I never really experienced the MM part of MMORPG until I was level 60 and running Zul'Gurrub. It was exciting and exhausting, but for the first time I really felt like I was experiencing the entirety of the game.
Nobody's perfect
If you play WoW long enough, you're bound to make mistakes. Whether it's accidentally picking up the wrong piece of loot off of a boss or pulling a bunch of elites before your group is ready, everyone messes up once in awhile. While I normally make a habit of doing research in order to avoid such things, the other day I made a mistake that only affected myself, but it was pretty annoying nonetheless.I had been spending a lot of money power-leveling professions for a few of my alts when I got lucky and picked up a couple upgrades for my main character. I was low on funds and needed to grab some enchants and gems quickly so that I'd be prepared for an upcoming raid. With little time to farm, I hit the auction house and looked for some deals. When I noticed the low price of Nexus Crystals, I was reminded that my enchanter alt could transform those into Small Prismatic Shards and then again into Large Prismatic Shards. After double-checking the prices for the various materials, I concluded that I would not only save a good deal of money, but I'd make a bundle by selling extra shards. I bought all of the Nexus Crystals on the auction house and shipped them off to my enchanter. Gleefully imagining the piles of money I'd soon be raking into my coffers, I switched characters and converted the first crystal into a shard. My schemes where short-lived, sadly, when the realization that the conversion of Nexus Crystals has a cooldown, much like an alchemist's transmutes. Oh well, at least I'll have a nice stockpile of shards after about a month or so.What are the biggest mistakes you've made?
South Park WoW episode nominated for an Emmy
Emmy nominations got released the other day, and there was a familiar face in the Animation category-- the World of Warcraft South Park episode "Make Love, not Warcraft" has been nominated as an Outstanding Animated Program. Strangely enough, while South Park has been nominated six times before, they've only won the category once, and that was for an episode based around a PSP game.Robot Chicken, The Simpsons, Spongebob Squarepants, and the Avatar (which is actually an amazing show-- it was recommended to me by WoW Insider's own Dan O'Halloran) are its competitors this time around, but I'm sure the various WoW mistakes in the episode (Kenny played a Hunter, among other tiny slipups) won't hurt its chances too much.The Emmy Awards will be given away in Los Angeles on September 16th. We'll keep an eye out for a WoW-inspired South Park win.
Ubisoft admits to over-porting Wii
While EA was caught off guard by the Wii, Ubisoft ended up over-saturating. Ubisoft CEO Yves Guillemot now admits that "mistakes" were made in just porting games with tacked-on controls. Although many can debate the quality of original titles like Rayman Raving Rabbids and Red Steel (both reached the million sold mark), it's not so easy to be kind about sloppy ports FarCry: Vengeance and Prince of Persia: Rival Swords. Speaking with German über magazine Spiegel, Guillemot admits that they sacrificed quality in their haste to capitalize on the Wii.Well, hopefully Ubisoft learned its lesson and got enough cash from the Wii to put some effort behind the next crop of games. They've already announced a sequel for the Rabbids at their UbiDays event, but there really isn't too much else announced in the Ubisoft Wii pipeline. Maybe they'll save the Wii announcements for E3, despite Guillemot's feelings about the event.[Via WiiFanboy]
The Top 7 Nintendo Mistakes are sure to offend somebody
GamesRadar has just put up their list of historical Nintendo blunders, and ... wow. We hope they're wearing flame-retardant clothing. The list has seemingly noble enough intentions: to analyze how Nintendo went from the absolute biggest name in video games to pretty much third place. Ultimately, it's probably meant to incite arguments, and they'll get plenty of them.But if there's anything we've learned from years of being on the Internet and from specializing in Nintendo discussion, it's that any negative word about Nintendo will summon a cacophony of fanboy hate. Never mind that a lot of the things on the list (with one very notable exception) are definitely huge mistakes and probably did contribute to Nintendo's semi-downfall in the pre-DS days. Let's try to buck the trend here. Let's have an open discussion about Nintendo's missteps, instead of screaming at naysayers and trying to spin the Virtual Boy as a good thing.
The best video game blunders of 2006
Have you been wondering what the biggest screwups in the video game industry were in 2006? Well, you can quit worrying and start reading. This is the sort of stuff we'd like to see covered at things like the Video Game Awards. For an industry that is so good at congratulating itself, they sure don't like to admit their mistakes. So, it's up to someone else to do it for them.Check out this list of the top ten video game blunders, boners, mistakes and gaffes of 2006 from next-gen.biz, and laugh along at some of the highlights from the past year. The Gizmondo story should have totally been number one, though, as Stefan Eriksson has become the official poster-boy for video game idiocy in action after single-handedly killing a company. And a gorgeous Ferrari.[Thanks, Joe]
Target selling pre-bricked 360s?
Target markets the red ring of death for the "low price" $399.99. Presumably, this is an amusing error on their part and not a new, doorstop-ready SKU.[Thanks Steve]
11 Xbox 360 mistakes to consider
Another day, another list of things that are wrong with the Xbox 360. This one's from Firing Squad, and enumerates eleven different "mistakes" present in the 360. Most of them seem like fairly minor niggles that don't have much impact--the lack of DivX playback, for example, is annoying but nowhere near a showstopper. Similarly, the lack of a bundled web browser isn't going to make us take our consoles back to the store and demand a refund. It seems that when one has to look so closely for errors, maybe Microsoft got the overall design just right.[via /.]
