free hit counter maxconsole.com share image
maxconsole
gateway
www.maxconsole.com - 1.11.2014
 
 
ModChipCentral
HOME - FORUM - MAXCONSOLE STORE - REVIEWS - $ SUBMIT NEWS $
nac3 nds
     
Double Fine imposes post-launch review embargo on Broken: Age's Kickstarter backers    

  Double Fine imposes post-launch review embargo on Broken: Age's Kickstarter backers
Added by Kaos2K on 15.01.2014

They seem to went crazy

Kickstarter backers can't talk or write about the game they have purchased until February 27

 

Like ... Dislike ..
Total Likes : 0
Total dislikes : 0

icon
  Discuss in our forums

line1

So this is it, welcome to the new age where a company who had received your money to fund a game forbids you to talk or review the game you have purchased. Check it out what VCG247 wrote about:

Broken Age developer Double Fine will get the game’s first-act into the hands of Kickstarter backers today, but there’s a catch: backers with blogs or who are members of the press can’t write about it until two weeks after launch.

In a Kickstarter update sent to VG247 today, Double Fine wrote, “Right now we’re working on a press release that will go out tomorrow morning. This will announce the public ship date of the game and a new trailer showing off Vella, the female protagonist!”

That date is today, January 14. Broken Age’s first act will release exclusively for backers, but the press and gamers have been placed under embargo until January 27. It’s an odd situation.

The post continues, “We’re also preparing to send out review codes to press, who will be under review embargo until January 27. This embargo also applies to any of you backers who are in the press or have blogs—we are requiring all formal reviews be held until January 27 at 10am Pacific time (6pm GMT). The same time limit applies to the press as to backers; everyone is in the same boat! We’re trying to be as fair as possible given that backers will have access to the game before everyone else.”

What do you make of the above? It essentially states that backers who have laid down money for the game are unable to write about a product that is already released. Typically, such embargoes come pre-launch, which is understandable, but we’re keen to see how many backers actually stick to these rules, and what he penalty will be for those who break the request.

To ask ordinary gamers “with blogs” to refrain from writing about their game is abnormal, but it’s unclear where the line sits. Should they also refrain from tweeting or posting about the title on Facebook? The rules are hazy at best.

So, what do you think? Will Double Fine retract or not?


Maxconsole:
All the gaming, all the news, updated all day

line2

text
Discuss this in our forums

Click here to discuss about this news in the forums


 

 
 
top posts



new

icon
Gateway 3DS releases v2.5 which adds 9.2 support
Nintendo just updated, and so did Gateway right away!
icon
Team Rebug releases amazing new PS3 Firmwares
The Team is back and with bang just in time for Halloween
icon
GovanifY leaks 3DS v7.x KeYs
Now you can with ease rip apart any of the very latest 3DS game ROMs!
icon
Sky3DS - Official website updated with FAQ and more videos
Out of the Blue, a new 3DS FlashCart has appeared with native v9.x firmware support
icon
K3DS - The King for your 3DS - Releasing Soon
Developed by European Team and Amazing Enough updating to support Sky3DS type native v9.x firmwares

review

icon
The Best Gaming Consoles That People Buy
Now that the new generation is out, the old console favourites still have alot of value in them.
icon
Cobra ODE Review
Senaxx over at PS3Crunch reviews the Cobra ODE device on his PlayStation 3
icon
REVIEW: JXD-S7300 Gamepad2
Another Exclusive In-Depth Hardware Review by Maxconsole
icon
In-depth review of the new Wolf Controller for 360
Talismoon latest accessory the 'Wolf Controller', is not just your average rapid fire mod!
icon
REVIEW: FireCore Passport
Another Exclusive MaxConsole Hardware Review

 


 


 

down1

SF

 

Contact us


Advertise on maxconsole.com





0 wallclock secs - 0.41 cpu secs