"Telltale" Signs

Posted by Daeity On Monday, November 21, 2011

Last week, Gamespot made a post about Telltale Game employees feeding perfect 10 scores into Metacritic.

Quite a bold statement. So, what exactly was their investigative technique to confirm this with 100% reliability?

The reviews had above-average grammar, and their aliases (e.g. "TANTRAD") happened to match the aliases of Telltale employees. Yep, that was it.

Between the reviewers' constant lionizing of Telltale Games, complete sentences, proper punctuation, and paucity of spelling errors, we began to suspect that the user reviews were not the product of actual players, but of Telltale representatives. Sure enough, a cursory Google search on the reviewers' user names backed up our suspicions. One of the reviewers was a user interface artist at Telltale; another was a cinematic artist. According to their LinkedIn profiles, both were relatively new to the studio, but they should have more than enough experience in the industry to understand this was a bad idea.
(Funny.. I didn't see a ton of other gaming blogs attacking and scrutinizing them for their investigation process.)

I really liked this part of their article:
But if the goal was to drag those individuals over the coals, you'd see their names and LinkedIn profiles here.
They said this after they gave all of their readers the means to find it out themselves:

1. A link to the Metacritic page
2. Told everyone it was a perfect 10 score
3. Told everyone it's the oldest score on the page (Nov 15, 2011)
4. You can use Metacritic to sort of by date on the positive reviews
5. Grammar is above average
6. A cursory Google search of their alias and "Telltale"
7. On his LinkedIn profile he's new and a User Interface Artist

This actually reminds me of that Facebook investigation. I'm showing you how they probably came to that conclusion, or how they most likely investigated, and I'm probably right. Maybe I'll be scrutinized for this post.. "you're jumping to conclusions", "LinkedIn Profiles are unreliable, I can't believe you use them to confirm if they work for companies", "FAKE NEWS!!"

The Point

What's most scary about this whole thing is that Gamespot is probably 100% correct and that they came to the conclusion through a very simple investigation.

This is a point I've been trying to make for a long time.. there is a ton of information on the internet that most people think are unreliable or useless, but they're not. For the most part, people are very open, honest, and not very careful about what they type on the internet.

In cases like this, though, look at what happened. Gamespot went by on online alias (unable to confirm who actually owned the alias), posted it as undisputed evidence, caused rage, which resulted in a substantial number of negative reviews from users who never actually played the game but were just angry about the situation.

Can you see how both users and media organizations (or internet "journalists") could have been easily manipulated in this situation?

This is why I show as many sources as I do, and proof to backup every claim. I see what happens on these other sites (like Gamespot, who just made the claim and did not provide their sources and proof that the Metacritic alias was indeed used by the employee), and I want to show how I came to a conclusion so that people can come to their own.. I may be right or wrong, and sometimes there is no way to be 100% positive. I can only guess that this case is probably correct given the evidence, probability, and past trends.

Let's go back to how just Gamespot investigated the incident:

If I was a competitor, and I really wanted to ruin the reputation of a game, why not just create multiple aliases of employees and give it a glowing review? And then, give negative reviews for my own games?

It wouldn't take long for blog/gaming sites to pick up on these, investigate (reverse alias search on Google), put 2 and 2 together, and report incorrect information resulting in sympathy for my own company and negative reviews for my competitor. I wouldn't be surprised if something like this has already happened.

A disgruntled employee could even do it to their own company, or targeting another employee they don't like. A disgruntled fan could do it.. anyone can do this and it would be perfectly legal to use your own alias (even if it happens to be used by another person) and make a review, but it would be the news sites or blogs that create the rumor or make the libel post in the end.

U4ia Games

Posted by Daeity On Sunday, November 20, 2011

Former Activision employees Dusty Welch and Chris Archer have created a new company called U4ia ("Euphoria") and their first game will be an "online-only, hardcore freemium, first-person social" game released in 2012.

Dusty was previously "SVP and Head of Publishing" at Activision for 13 years, and his last day on the job was during March 2011. That puts him at the same time of the 500 person layoff within Activision Blizzard on March 31 of this year. Apparently, that ~500 person layoff isn't considered a "mass layoff" by the WARN Act though. :)

They haven't released the game title yet, but they did register two trademarks (excluding their business name.) The first was the phrase "FIRST PERSON SOCIAL" and the other was "TW!TCH", which could be a game name or a protected phrase/process (e.g. mobile and social twitch based combat.)

First person social... eek.

Diablo News on November 30

Posted by Daeity On Saturday, November 19, 2011

I wanted to remind everyone that this coming November 30th is Diablo's 15th Anniversary which is a pretty big milestone for the franchise.

As you might have noticed, Blizzard has been doing a lot of "celebratory" activities recently. They've had a lot of interesting things prepared for their 20th Anniversary, and even though they have minor Anniversary activities within the World of Warcraft, they reserve special bonuses for more notable milestones.

We plan to reserve this sort of celebratory bonus for the most notable milestones or events in the future.
(FYI: World of Warcraft was released on November 23, 2004, which was the 10th Anniversary of the Warcraft franchise.)

I don't think that the game will be released (or the release date announced) on November 30th of course. They still haven't tested the RMAH yet and technical stress testing is far from completion. And, they still need a major ramp up of beta testers too due to the high attrition rates associated with the short beta gameplay.

The 15th is still a big deal though, and there will be something for all Diablo fans.. it won't just be limited to beta testers like how the WoW Anniversary is limited to WoW subscribers only.

There might be a minor announcement (a major beta wave sometime after Dec 12th), but I'm expecting some kind of information release like more lore, loot details, D3 art galleries, maybe a retrospective video, music, "making of" videos, etc. Simple stuff to keep Diablo fans busy until the release date.

(* UPDATE: There is a "Diablo 15th Anniversary Music CD" available in the Blizzard Store.)

The "Book of Cain" is also rumored to have moved it's arrival date up from Dec 15 to Nov 30 coincidentally as well. :)

November 30th would be a great time to announce the Diablo 3 release date though. It could be used as the "big bang" to finally close up the whole Blizzard 20th Anniversary celebration that has been going on over the past several months. After all, they had originally planned on a surprise D3 release announcement at Blizzcon 2011 which no one knew about (except one person/blog) and Nov 30 is awfully close to their originally planned release date (Nov 24).

Now that I mention it.. you know, it's funny that the individuals who scrutinized TOD's old March post conveniently forgot about something rather important. During the Q4 2010 (Feb 2011) Quarterly Earnings Call, Blizzard stated that they would not be releasing any games during 2011. It made the majority of gaming sites.. "no releases in 2011". That was the firm belief of everyone.

And then on March 23 2011, Daeity said that they were actually intending on releasing Diablo 3 in 2011 before Christmas, that there would be a surprise at Blizzcon, and there was a "mid-Jan backup date". Whether you originally read it in March, or in August when the site was brought back up, people were still saying no releases in 2011.. but TOD was saying the opposite.

Then suddenly, Blizzard announced on September 23 2011 that "'Soon' Was Too Soon -- Diablo III to Arrive in Early 2012" and D3 had been pushed back to 2012. They revealed publicly that they were fully intending on releasing D3 before Christmas. This is the first time Blizzard ever announced anything like this, and apologized.. that's just how big of a deal it really was. They had already announced "no releases in 2011" so there was absolutely no need to ever make this post since 2012 was already the target like everyone knew. That apology ended up confirming why TOD kept saying that it was going to be a "big surprise" at Blizzcon 2011.. they've never done anything like that before, it was a very big deal. No one else was reporting this, it was just one person, and it turned out to be true just like everything else.

On a side note, while I was looking over that old Q4 2010 post, there was also this interesting piece:
* UPDATE:

Confirmation regarding lay-offs. Both Vicarious Visions and Freestyle Games have been hit with notices shortly after the meeting. According to Activision Blizzard's 8-K, they'll be getting rid of approx. 500 employees. The decision was made Feb. 3, and will be taking place on March 31 for the staff.

This same time last year, they laid off approx. 200 people. Apparently, February is the time of month when the non-performing studios need to start worrying.
This further confirms what I was writing about earlier regarding the "mass layoff" WARN notification system. Apparently, the 200 employees were reported to the WARN system.. but there were another 500 employees who were laid off, but it wasn't reported in the WARN system. Interesting.. apparently a "mass layoff" can be 1 to 5 employees, but 500 employees isn't considered a "mass layoff". :)