You know your game is terrible when...

[Faladorian]

You know your game is terrible when it came from Japan, and it isn't Silent Hill... Seriously everything from Kingdom Hearts to Final Fantasy is a big heap of useless over-estrogenized garbage

Katamari Damacy? maybe the soundtrack could get annoying, but it's still good. What about Mother 3? That is not like most JRPG's.

Oh yeah haha the Katamari games were one hell of an acid trip... XD

 

[Irony's Acolyte]

You know your game sucks when it moves air into it in a very quick manner.
[sub]Eh that could have worked out better.[/sub]

OT: You know your game sucks when you have to pay people to play it. And they still don't feel like doing so.

 

[SixWingedAsura]

You know your game sucks when the only good comment people can come up with (and out of pity) is that the menu looks...not eye-gougingly terrible.

 

[Ninemanec]

when M. Night Shamylan (sp?) thinks that the plot is too confusing and stupid

 

[Tdc2182]

You know your game is terrible when Reaver shoots the last boss for you

So much agreed.

Ruined what little potential the final boss could have had.

 

[justnotcricket]

You know your game is terrible when the player uses it to put themselves to sleep.

 

[archvile93]

WHen its main selling point is a gimmick, and a useless one at that.

 

[RandallJohn]

...when you really wish someone would go and shoot the main character in the head.

 

[Tdc2182]

Spoiler: You know a game is terrible when the main game mechanic is shooting portals.

Good luck.

 

[Snake Plissken]

You know your game is terrible when it has Spyro in it. Man, I hate that franchise.

 

[guntotingtomcat]

You know a game is terrible when you start naming your furniture and talking to it.

 

[fgdfgdgd]

When you have to swap to a grenade to throw one

when a speech tree only has three options but all lead to the same thing

When magic does little or nothing, range attacks do the same and melee is by far the best option (ala Oblivion)

When the counter button is stacked on the block button and is the easiest way to win a battle (sorry assassins creed, as much as i love you, that can get old fast)

 

[Sixties Spidey]

You know your game sucks when Sonic Team was involved in any part of developing it.

 

[Tron-tonian]

You know your game is bad when refuse the briefcase of money you offer in return for a positive review.

 

[omicron1]

You know your movie tie-in game is extra terrible when the makers of the film tell you that publishing it will hurt film sales.

 

[The Night Shade]

You know your game is terrible when you can't play it

 

[Something Amyss]

You guys know what to do


You know your game is terrible when unskippable can make a series of videos on it...

When even Jack Thompson can't be bothered to protest.

When an online petition is circulated to prevent a sequel.

When Yahtzee's ZP review of your game is five minutes of sobbing.

When the publisher offers pay DLC to remove content from the game.

Uwe Boll demands his name be taken off the movie tie-in.

When Microsoft and Sony guarantee it will not be compatible with future consoles.

When your PC intentionally causes BSOD just to avoid installing.

When your 360 intentionally RRODs just to avoid loading the title. Continue for YLOD and whatever errors Wii has.

When the manual contains a five page apology.

 

[TheLiham]

You know your game is terrible when it came from Japan, and it isn't Silent Hill... Seriously everything from Kingdom Hearts to Final Fantasy is a big heap of useless over-estrogenized garbage

Or You know your game is terrible when it is Silent Hill but it wasn't made in japan

 

[Twaddlefish]

You know your game is terrible when the original Doom has better plot devices.

 

[endnuen]

You know your game is bad when haven't made physical contact after 20 minutes.

Oh.. Not that kind of game