Vote! MangaGamer puts Go! Go! Nippon! on Steam Greenlight

My First Trip To Japan could make its first trip to Steam

11:41 AM on 09.01.2012

In case you haven't been keeping up with the wild world of videogame digital distribution, here's a quick news flash: Valve, the reigning poobahs of PC play have just launched Steam Greenlight, their new crowdsourced community game approval tool. Long story short, it's a way for them to augment (but not replace, thankfully) their standard approach to deciding which games get on Steam with a bit of community vetting.

Developers and publishers large and small (ideally small) can submit their games and projects for inclusion on the service, and users can view their pitch pages, then vote on whether or not they'd like to see the game on there. Once a certain number of positive votes is collected, Valve then takes the clearly popular new project into serious consideration. The rest is e-commerce history.

This brings us, of course, to the headline: MangaGamer has placed their OVERDRIVE-developed hybrid visual novel/travel guide, Go! Go! Nippon! ~My First Trip To Japan~ up for approval. Now it's up to YOU to decide whether or not it's worthy of being exposed to the wider PC gaming audience. Check out the game's Greenlight page, and if you like the idea of having more visual novels on Steam, click the "Rate" button underneath the screenshot window, the one with the thumbs-up icon. If you need more information, read my review. So far the tally reads at a discouraging 0% of the required votes, but there have been reports of bugs in the service, so that number could rise as Valve works out the kinks.

Personally, I'm voting yes on Proposition Put Go! Go! Nippon On Steam, since a successful run could open the door for more cool visual novels, MangaGamer-published and otherwise.

Get comment replies by email.   Settings.

Vile douchelords afoot? Please report harassment, spam, and hate speech to our comment moderators

Comments not appearing? Anti-virus apps like Avast or some browser extensions can cause this. Easy fix: Add   [*]   to your security software's whitelist.

Josh Tolentino

Managing Editor