Game posting guide

• Explain what kind of game it is in a few sentences
• State where, on what systems, and for roughly how long it can be played
• Do not hide material that needs an age restriction or content warning
• Clarify whether you accept reviews, bug reports, streaming, or recruitment
• Organize credits for assets and collaborators
• Use tags for mood, themes, and visual style—not for structured platform fields

The post may be read by players, reviewers, testers, applicants, and moderators. It does not need to be long, but it should contain what each audience needs to make a decision.

Use a recognizable title rather than a generic label such as “test” or only a version number. The introduction should cover the premise, core activity, current release state, expected play time, controls, important limitations, and the kind of feedback you want.

Use the header for a wide key visual, a square thumbnail for lists, and gallery images for representative screenshots. Do not use unrelated promotional images.

Choose the primary genre that best describes the central play experience. Use subgenres only for meaningful additional structure. Themes such as fantasy, horror, cute, or pixel art usually belong in tags rather than the genre field.

Use R18+ for content unsuitable for minors and content-warning labels for material people may want to know about before viewing. R18+ is Gamine’s own self-disclosure, not an ESRB, PEGI, CERO, or other official rating. Add both age restriction and a specific warning when both apply.

Disclose generated output that remains in the published game, including art, music, voice, text, translation, 3D models, or runtime generation. Ideation, proofreading, or ordinary code completion generally does not count when generated expression does not remain in the game.

• Current availability and development status
• A working browser, download, store, or information link
• Price or availability notes
• Supported platforms, languages, controls, player modes, and expected play time
• Setup steps, accounts, network access, or other prerequisites

Keep external links safe, current, and consistent with the description. If availability changes, update the post.

Use dedicated fields for engine, development status, supported systems, language, controls, and play modes so search and filters work correctly. Tags should supplement—not duplicate—these fields.

State whether streaming, recorded videos, monetization, spoiler-heavy coverage, and use of game audio are allowed. If third-party music or assets impose separate restrictions, describe them clearly.

Useful tags describe mood, setting, experience, visual style, or production context: for example cozy, dark, science fiction, exploration, narrative, pixel art, low-poly, game jam, or solo development. Do not repeat platforms, controls, languages, release status, age restrictions, or subjective quality claims as tags.

Register Gamine assets used in the game where practical, and follow all external credit requirements. If you accept reviews, choose the topics on which creator-requested feedback would be useful; reviewers remain free to express their experience in their own words. Clearly state whether you accept play logs, reviews, bug reports, or recruitment activity.

• The title, profile URL ID, and introduction match the game
• Age restrictions, warnings, and generative-AI disclosure are accurate
• Platform, play mode, controls, language, play time, and engine use their dedicated fields
• Availability and development status are current
• External links are correct and safe
• Streaming, review, bug-report, and recruitment settings are clear
• Required credits are present
• Tags add theme or style information rather than duplicate other fields