This contest is complete, and the winner has been chosen.
Game Ad | Game Name | Crafter Point Votes | Status |
---|---|---|---|
{{entry.properties.game.name}} {{entry.properties.game.short_description}} |
{{entry.properties.crafter_points}} | Winner! Finalist Semi-Finalist |
Contest start date: {{wing.format_datetime(contest.properties.date_created)}}
Letiman Games presents The Worker Placement Challenge
We want you to design a game that uses worker placement as the driving mechanic. You can consider using 1 worker per player like in Harbour, many workers like in Lords of Waterdeep, or even consider using dice as workers like in Kingsburg. It is completely up to you how you create your workers, how many you have, and what the workers are doing for you.
So what types of games does Letiman Games really like? We typically like all-inclusive games that work with gamers and non-gamers, children, adults, timid gamers, alpha gamers, EVERYONE. We like to keep our games simple and quick to act as great gateways or fillers during a heavy game night, so please keep the games 60 minutes or less. We want the games to be medium sized or smaller, so your entry must come in either a Small Pro or Medium Pro box.
Dan Letzring of Letiman Games will be personally judging all entries.
To qualify, your game must comply with all of the following rules:
You retain all rights to your game and are welcome to sell it in our shop before, during, and after the contest, regardless of the outcome of the contest.
The first round of judging is handled by a community voting process. The final two rounds are handled by the judge. See complete details.
* Consideration for publication is open for discussion. Commitment to publishing the winner automatically is not fair to the designer or the publisher. If there is a good turnout for this contest and an entry fits the bill, then I will certainly give the winner a hard look. Who knows, maybe more than one contract could be handed out.
Contact Dan if you have any questions:
http://www.letimangames.comContest start date: {{wing.format_datetime(contest.properties.date_created)}}