I built a fun core mechanic that I love, but I'm struggling to turn it into a game
retained text
Over the past few months, I've build out a game mechanic that I think is really unique and fun. I've built a prototype game around the mechanic, but the further I go, the less the genre feels right. The prototype/vertical slice is currently built around 3rd person Open section areas with a main path, and winding optional paths along the way that usually lead to a puzzle or chest that awards the player with... something. It's a bit similar to Tunic in terms of level design & exploration. Now trying to have a look at the game's direction before going further. The mechanic is something I'm really proud of and leads to a lot of creative moments. # The mechanic: Our character is a Wizard who can Transfer properties between objects in the world. Everything in the world posses properties: * **Explosive barrel** \- Solid, Heavy, Gravity, explosive * **Lake** \- Liquid, Wet, Conductive * **Zombie** \- Alive, Dead, Solid, Gravity * **Torch** \- Solid, Wooden, Flammable, Burning, * **Locked Door** \- Solid, Wooden, Locked * **Old Table** \- Solid, Wooden, Buoyant, Flammable, Brittle The player is able to transfer a property from one object to another, and all things interact with physics and each other as you would expect. **Example 1** \- Finding a Locked Chest, but you also found a door with "Unlocked". You're able to transfer Unlocked from the door to the chest. You can now open it **Example 2** \- You encounter a Lava field, but find both a Sheep and a Metal table. You can transfer the "Alive" Property from the sheep (RIP) to the table. The table can now "Walk" around, and you could stand on it, while it walks across the Lava. **Example 3** \- A drawn Drawbridge blocks your path, you're able to Remove "Heavy" or "Gravity" from the counterweights, which would drop the bridge and let you cross. I currently have 26 fully implemented properties. The mechanic also introduces balancing issues, which 've implemented a solution to that don't remove the feeling of freedom. The experimentation and mechanic gives a really fun sense of "I bet the Dev didn't think I could do this". The feeling feels a bit similar to Noita's wand experimentation. How can I decide on a direction when building the game around the mechanic? Some genre I've played around with that could fit the mechanic are: * **Traditional Puzzle game** \- Like Portal Test chambers, go from one level to another, no story * **Exploration Adventure** \- Like Tunic's world, environmental puzzles, very light story * **Objective Based Sandbox** \- Like Besiege, level based, letting you experiment until you complete an objective An issue I'm having with the Exploration Adventure approach is that it seems to push my game in a more combat-oriented direction (We have a super basic combat system), but it's making the core mechanic feel secondary. # Questions: * What kind of game would you build around a mechanic like this? * Do you know of any similar games I could study? * If I stick to Adventure centered game, what would you feel the moment to moment could look like without emphasis on Combat? * Any advice on building a game around a mechanic?
document fetched 2026-10-11 00:25 · canonical https://reddit.com/r/gamedev/comments/1x2qh1t/i_built_a_fun_core_mechanic_that_i_love_but_im