Moonvine Forge
Community Card Forge
Submit a card, relic, enemy action, resource, status, or complete turn-based mechanic. No code, artwork, or perfect balance is required. A clear idea is enough to challenge the engine.
Simple concepts are welcome. Complicated interactions are welcome. Dangerous edge cases are especially welcome.
Skill card
Choose a card in your discard pile. Resolve its first non-damage effect without paying its cost. If that effect would invoke Recursive Petition again, stop the chain and Exhaust both cards.
“Please refer to the request referring to this request.”
Start with the interaction you would enjoy seeing, not with what is easiest to implement.
Explain what triggers it, what it changes, who it targets, and what price or drawback keeps it interesting.
Text is enough. Numbers can be approximate, and unanswered details can remain open for interpretation.
Useful ideas reveal missing building blocks, awkward edge cases, and opportunities for more modular systems.
Need a spark?
Generate a prompt, twist it into something personal, or ignore it completely. The goal is to get from “I have no idea” to one mechanic worth explaining.
Current design prompt
Design a relic that remembers the order in which cards changed zones, then rewards one specific sequence.
Submit your idea
The form guides you from the broad concept to its effects, costs, targets, drawbacks, and intended role. Complete only the detail you actually have.
Compact community Forge: describe the mechanic in ordinary language, add only the detail you want, and submit it directly. Your unfinished entry exists only in this open tab and is not saved in persistent browser storage.
Your idea has entered the Forge. Keep the reference below if you want to identify it later.
Keep your reference. Save the MVF-... reference shown after submission if you may later want to identify an anonymous entry, request deletion, or withdraw public-credit consent.
What happens next?
Submissions can reveal recurring mechanic patterns, missing engine capabilities, balance risks, and interactions that deserve a more general solution.
Submission does not guarantee implementation or inclusion in a future game. An idea may instead be used as inspiration, balancing data, or an architectural test case.
The concept enters the community design collection.
Its trigger, cost, target, effect, and edge cases are examined.
The idea is reduced to reusable capabilities the core may need.
Selected concepts may inform tests, experiments, or future content.
The difficult ideas are useful
A small elegant interaction can be as valuable as a complicated system. What matters is that it creates a decision, a risk, a surprise, or a new way to build.