Gamine Documentation

Asset posting guide

How to describe an asset, its license, supported tools, and conditions of use.

Last updated: July 19, 2026

Start with usability information

  • Explain what the asset is and what it is intended for
  • State engines, tools, file formats, versions, and dependencies
  • Make commercial-use, modification, redistribution, and credit terms explicit
  • Show representative samples, previews, and included files
  • Apply necessary age restrictions and content warnings
  • Use tags for style and motifs—not for license or compatibility fields

Clarity of usage conditions is more important than promotional wording. Users should be able to decide quickly whether they may and can use the asset.

Title, description, and images

Use a specific title that identifies the asset type and theme. Explain intended use, included files, recommended workflow, file structure, known limitations, version, update history, and any license details that do not fit the structured fields.

Use a square thumbnail that remains recognizable in lists. Gallery images or previews should show the actual contents or representative use, not unrelated artwork.

Category and subcategories

Choose the category closest to the asset’s primary use. Add subcategories only where they materially help discovery. Visual style, mood, and motifs usually belong in tags.

Age restrictions and content warnings

Assets can require the same protections as games—for example explicit imagery, strong gore, horror audio, flashing effects, sudden loud sounds, or themes involving death, abuse, addiction, or crime. Gamine’s R18+ label is a self-disclosure, not an official rating.

Generative-AI content

Disclose generated output that remains in the distributed asset and explain where and how it was used. Asset authors must also confirm that the relevant AI service or model terms permit distribution, commercial use, modification, and licensing under the conditions offered.

License and rights

  • Whether commercial use is allowed
  • Whether modification is allowed
  • Whether credit is required and the exact copyable wording
  • Whether redistribution is allowed
  • Whether a game containing the asset may be distributed
  • Whether the asset itself may be redistributed in an asset pack or template
  • Any prohibited uses or possible future license changes

Only distribute material you own or have permission to redistribute. Listing on Gamine does not guarantee rights, license validity, quality, or safety.

Availability and distribution

Gamine does not host downloadable asset packages directly. Add a current external distribution, store, or information page and state whether the asset is free, paid, temporarily unavailable, or discontinued. Keep the link, availability, price context, and version information current.

Technical details

  • Target engines or tools and required versions
  • File formats
  • Intended uses such as UI, sprites, backgrounds, characters, tilesets, music, sound effects, or templates
  • Dependencies and prerequisites
  • Installation or import steps
  • Samples or use examples

Included files

Describe folders, file counts or variants, resolutions, audio length or loop information, model topology or rigging, documentation, sample projects, licenses, and other included material as appropriate. Explain what is not included when screenshots show a larger example scene.

Tags

Useful tags describe art style, mood, motif, audio character, or likely scene: for example pixel art, hand-drawn, low-poly, dark, retro, monster, icon, battle music, or dialogue scene. Do not repeat engines, file formats, license terms, distribution status, age restrictions, or subjective quality claims.

Before publishing

  • The title, profile URL ID, description, category, and subcategories match the asset
  • Restrictions, warnings, and generative-AI disclosure are accurate
  • Engine, format, and intended use use dedicated fields
  • Commercial use, modification, redistribution, and credit are unambiguous
  • You have the right to distribute every included item
  • External links are correct and safe
  • Included files, version, setup, and limitations are sufficiently described
  • Tags add style or motif information rather than duplicate structured fields