FACT: I'm going to sue the sh*t out of the Bit.Trip guys

1:30 PM on 01.04.2010

Anthony Burch

Contributor

A little while ago, Destructoid discovered that the next game in Gaijin Games' Bit.Trip series would be titled Bit.Trip RUNNER. Thanks to a low-res screenshot of the game in our most anticipated Wii Games of 2010 list yesterday, we also learned that the game will most likely be a sidescroller.

This is an outrage.

You may have heard of a little game that took the Internet by storm a few months back. A game that set the World Wide Web positively ablaze with buzz and critical acclaim, garnering over one hundred downloads and at least two links from places other than Destructoid and my own Twitter account. That game was made by myself, Jonathan Holmes, and Ashley Davis. It was, of course, called Runner. It can be downloaded here.

And now these pricks from Gaijin Games are releasing a game with the exact same name, belonging to the exact same gameplay genre. They want to latch onto the unbridled popularity and downright world-changing mechanics of Runner that were in no way ripped off from Battletoads or Passage. And I won't goddamn stand for it.

"But," you may be thinking, "but what if Gaijin Games had never heard of your game and the titles are just a coincidence?" Sure, I would reply. A reasonable question...were it not for the fact that Gaijin Games' very own Alex Neuse reviewed Runner a few weeks after its release. I demand vengeance.

For this reason, I have decided to turbo-sue Gaijin Games for a breach of some sort of law or contract or thing that I will determine at a later date. My lawyer and I will litigate Neuse and his cohorts into oblivion. When the dust and legalese have settled, you can be assured that only one Runner shall remain.

Get ready for war, Neuse.

 

Get comment replies by email.     settings



Unsavory comments? Please report harassment, spam, and hate speech to our comment moderators

Can't see comments? Anti-virus apps like Avast or some browser extensions can cause this. Easy fix: Add   [*].disqus.com   to your security software's whitelist.