Step 6: Mechanic submission

Well, we're building this game from the ground up. Forget whatever themes have been discussed—they won't matter until we circle back to the subject. For now, I'd like some simple mechanical submission ideas. What I'm looking for is a one game mechanic that you think would be interesting to build-around. It could be broad, like "a deck building game," or it can be more specific, like "dice that you can improve through specific attachment upgrades." You have a week to submit your ideas. Limit two submissions per person.

Side note: I got SOOOOOOOO many table-top games for Christmas. Gonna break out Exploding Kittens later today.

1) You play the game by posting in a forum thread.

2) Your post can target a post earlier in the thread, changing the effects of that post on the game.

Wait did my idea win? Oh are we doing themes later now? I am confused.

We're doing themes later. Designing the game "bottom up" won the vote.

Wait a second..... why did you skip step 5?

Combining the cards/tokens/posts/whatever of multiple players to make awesome combo attacks/traps/defenses/whatever.
More clearly worded:
You and your team mates can do combo actions by comboing together your actions/ cards/ posts/ dice rolls /whatever we end up using.

Is this two nominations or two parts of one nomination?



1. Party or strategy
2. Individual or co-op
3. Symmetrical or asymmetrical
4. Theme submission
5. Theme vote

Two submissions. This is so that people can nominate the first but not the second if they choose.

Okay...... now I'm confused why only the part 4 vote got to be its own separate part.

Edit: Also, a large number of "subjects" on the previous page say "Re Step 4: Theme Vote", so.....

Mechanic 1: Players start in different "locations" (however that is represented in the game) and get bonuses once they "meet up" with other players.

Mechanic 2: Randomized events to throw twists into the game, generally to the detriment of the players.

Mechanic 1: Players have a character with a specific role or job that they can grow better at as the game progresses; a tiered level up system so that you make choices on how your character grows which impacts your ability in the late-end game.

Mechanic 2: Halfway through the game one player becomes the traitor. Nobody but the traitor knows who is the traitor. Traitor wins if the players lose.

I designed both mechanics to be used together or separately. My idea is basically a cooperative rpg board game with a mid-late Traitor twist. Think D&D mixed with Betrayer at the House on Haunted Hill.

I probably forgot to change the title for part five.

1) Co-op drafting game with traitor elements.
2) Relative positioning of non-unit pieces matter (e.g. worker placement game where you make patterns.)

I don't see much difference in making a mechanic then forcing a flavor onto and making a flavor and forcing mechanics into it.

They're dynamically different. Starting from flavor forces you to fit and consider mechanical ideas that express the story you're trying to tell. Mechanical design forces you toward building a fluid machine that you hopefully can attach a story onto. They're similar, sure, but they tend to yield different results.

Barely.

Bottom up games tend to be more balanced and have creative mechanics. TOP down games tend to be more flavourful but have a less efficient system.

My experience.

I just think it would be far better to do both at the same time.

Since I liked it as a suggestion, I'll add "dice you can upgrade" as a mechanical idea to approach.

I'll put a poll up over the weekend. You have until sometime then to finish your ideas.

The traitor should be called "the troll"