I would like to address the various game blogs that have reported on this whole PokeBeach / Nintendo situation. At first supporting us, many of these blogs have recently updated their news stories to state that we posted images from roms of the games, which, according to their theorizing, is why Nintendo reacted so strongly to our news coverage. This is absolutely not true, and a number of these blogs have not responded to our e-mail requests to correct this information or have completely misinterpreted our comments. Furthermore, most of these blogs have never even spoken with us, relying rather unprofessionally on their website’s user comments, posts from even more uninformed forum users, and news stories posted on other misinformed blogs.

PokéBeach: Nintendo Follow-Up [September 21st, 2010]

Hoorah for game blogs.

I’m still not entirely convinced of the veracity of this story, but it seems a little more believable than it did the other day. On that subject, PokéBeach’s “Water Pokemon master” write the following, which I present without comment:

And as for the people saying this is all fake, please stop. You don’t know everything we know. You haven’t seen the documents we’ve seen. You haven’t talked to the lawyer we have. You don’t have the capacity to look into anything - you don’t even have the lawyer’s name or other information we’ve been sent. You don’t have the right to claim this is fake when you don’t have access to the most basic information. The lawyer is real and so is the cease and desist order - we have confirmed it through various indisputable means as I have said until I’m blue in the face on various message boards. So please accept it and stop derailing the issue with “lol its fake grammer errors.”

  1. nhaler said: If they were transparent, they’d be revealing those sources. The only instant where obfuscation of a source is justified, is for that source’s safety.
  2. servbot42 reblogged this from gamejournos
  3. gamejournos posted this
Short URL for this post: http://tmblr.co/Zj0eQy177hU3
blog comments powered by Disqus