Gotham City Impostors Going F2P?

Wed, Aug 29, 2012

Console, Free-to-Play, MMOG, PC

Looks like Gotham City Impostors is heading for a free-to-play model, if the Open Steamworks Content Description Record Database is to be believed. Valve’s unofficial record of games reveals an entry titled “Gotham City Impostors F2P Trailer.”

While this certainly doesn’t constitute an official announcement, a move to F2P for the comical first-person-shooter multiplayer title wouldn’t be all that surprising. Its publisher Warner Bros. Interactive Entertainment recently moved another one of its multiplayer titles, The Lord of the Rings Online to F2P. Gotham City Impostors was released last February for PlayStation 3, Xbox 360 and PC players and received slightly above-average reviews from media outlets.

The game features two warring factions of lunatics. One side dresses up like Batman and the other side dresses up as his nemesis Joker. When a bunch of nutjobs dress up like comic book characters (and seem to genuinely invest in the personality), hilarity is bound to ensue. Matches cap out at 6v6, and players battle it out with crazy unlockable items like grappling hooks, glider wings, roller skates, explosives and a variety of weird guns that make Borderlands look like a traditional war game.

Are you a GCI player? Are you interested in seeing this title move to the F2P model? Let us know your thoughts in the comments. Also, are you Batman or Joker?

Be Sociable, Share!

Related posts:

  1. Ghost Recon Online Opens Public Beta; Ubisoft Joins F2P Crowd
  2. Ultima Forever F2P Online RPG Heading to PC and iPad
  3. Refunding a Free Admission: Taking Care of Customers in F2P
  4. Will World of Warcraft Ever Go Free-to-Play?
  5. PlayStation Set to Launch F2P Mercia: Fractured Realms
,

This post was written by:

- who has written 58 posts on Frisky Mongoose.


Contact the author


Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0