Community Variant Publishing #628
Closed
JorenC
started this conversation in
Feature Ideas
Replies: 1 comment 1 reply
|
One quick thing: If official variants are intended to be ideal for onboarding new players, what is to be said about the previously official variants (such as twenty twenty) which may be too niche or complex for newer players? I suggest that, while keeping the distinct categories already mentioned, there should be filters for certain aspects of maps, such as player count or estimated game time (there needn't be too many filter options). This would not only steer new players away from variants which may be too much for them to handle, but, more generally, it would allow players of any experience level to find games which suit their tastes, both inside and outside of the official roster. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
PRD: Variant Publishing MVP
Status
Draft
Background
The Variant Creator has generated significant community interest and early adoption. Players are already creating and testing custom variants, validating demand for user-generated content within Diplicity.
However, the current system lacks:
This PRD introduces a minimal publishing workflow that enables players to create and play custom variants while providing a path for high-quality variants to be promoted and recommended.
Goals
Enable Creative Freedom
Players should be able to create custom variants for personal use and private games.
The platform should not unnecessarily restrict variants based on gameplay quality, aesthetics, complexity, or niche appeal.
Support Community-Organized Games
Players should be able to use Diplicity as infrastructure for Discord-organized and community-organized games, including variants that may never become publicly promoted.
Curate the New Player Experience
New players should primarily encounter variants that have been reviewed and are considered high quality.
The platform should avoid overwhelming players with large numbers of unfinished, experimental, or highly specialized variants.
Create a Clear Promotion Path
Variant creators should understand how a variant moves from private experimentation to broader community visibility.
Non-Goals
This MVP does not attempt to:
These may be addressed in future iterations.
Variant Visibility Levels
Private
Private variants are visible only to their creator.
Characteristics:
Private status affects visibility only.
Content Restrictions
Private variants remain subject to platform moderation and legal requirements.
Variants may not contain:
The fact that a variant is private does not exempt it from these requirements.
Published
Published variants are discoverable by the community.
Characteristics:
Publishing may initially be a manual process.
Official
Official variants are a curated subset of published variants.
Characteristics:
Official status is a recommendation and promotion mechanism, not ownership or endorsement.
Promotion Criteria
The exact criteria remain subject to refinement.
Current expectations include:
No single criterion guarantees promotion.
Promotion decisions remain discretionary.
Intellectual Property Policy
The platform may not be used to distribute copyrighted or infringing content, regardless of visibility level.
This applies equally to:
Examples may include:
Specific enforcement processes will be developed separately.
GM Private Games
Overview
Introduce support for games managed by a Game Master (GM) who is not an active player.
This enables Discord-style community games where:
Motivation
This allows Diplicity to function as infrastructure for community-created variants without requiring those variants to become publicly visible.
MVP Scope
Required
1. GM Private Games
Allow creation of private games with a non-player GM.
2. Official Variant Category
Add support for three visibility levels:
Initial implementation may only require database support and administrative tooling.
3. Private → Published Workflow
Allow variants to move from private status to published status.
Initial implementation may be manual.
Examples:
Future Enhancements
Near-Term
Longer-Term
Open Questions
Official Promotion Process
TBD.
Discovery Experience
TBD.
Enforcement Processes
TBD.
Success Criteria
All reactions