hot  /  reviews  /  video  /  blogs  /  forum

Neverending Nightmares meets funding due to typo

Sep 30 // Jonathan Holmes

Fans swarm to support developer and other backers

Neverending Nightmares got a lot of press on Dtoid this week. It's also gotten a lot of support from other developers. Everything appeared to be coming together to help bring the game in close to its funding goals, but with a day left, it was still about 1/10 away from making it all the way. The developer was panicked, as were potential backers, all desperate for the game to succeed. 

Everything seemed suddenly fantastic when one backer threw $9,500 into the pot. Unfortunately, they had meant to type "$95.00". That's great for the game, not so great for the backer who just spent thousands of dollars they didn't have. What came next was even more panic, the rallying of even more backers to support both the game and the typo-prone backer alike, and a happy ending the likes of which you rarely see in the world of Kickstarter mistakes.

That recap barely doing justice to all the drama that unfolded. Check out the full story from former Dtoid contributor Sophie Prell for all the gory details


 Reblog (or) Blog Reply


Jonathan Holmes, Editor-in-Chief
 Follow Blog + disclosure Tips
"Where do dreams end and reality begin? Videogames, I suppose."- Gainax, FLCL Vol. 1 "The beach, the trees, even the clouds in the sky... everything is build from little tiny pieces of stuff. Ju... more   |   staff directory

Get more destructoid:   We're indie-run, blogging for the love of it, and our site will always be free. Optionally, you can support us and get: (1) Faster pages from our cloud server (3) Wide(r)screen (3) No big ads on Dtoid, Japanator, Tomopop, or Flixist (4) Auto contest entries, and (5) Dibs on betas & downloads. Try it out

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.

advertisement:




Back to Top