Game-development tool posting guide

• Explain the problem the tool solves and its intended users
• State supported operating systems, engines, versions, and dependencies
• Describe installation, required permissions, and external communication
• Make price, license, source availability, and redistribution terms clear
• Show the actual interface or representative output
• Keep support and issue-reporting links current

Development tools are software used to create or manage games. Images, audio, models, fonts, and other files intended to be incorporated into a game should be posted as game materials instead.

Use a title that identifies the tool and its main purpose. The introduction should explain the workflow it supports, primary functions, intended users, current maturity, known limitations, and what is included.

Use screenshots or videos of the actual interface and workflow. If sample output is shown, make clear what is generated by the tool and what is bundled with it.

• Supported operating systems and architectures
• Supported game engines, editors, and required versions
• Runtime, framework, plugin, or command-line dependencies
• Required permissions, accounts, network access, or external services
• Project formats the tool reads or writes

Do not claim broad compatibility that has not been tested. Separate confirmed environments from environments that may work.

Give enough information to choose the correct package and complete setup. Link to full documentation where appropriate. Explain update channels, breaking changes, migration steps, and whether older versions remain available.

• Whether the tool is free, paid, subscription-based, or unavailable
• License terms for the application, plugin, or source code
• Whether commercial projects may use output created with the tool
• Redistribution rules for the tool and any bundled runtime
• Required credit and exact wording where applicable

Keep the Gamine post consistent with the current distribution page. Gamine does not guarantee external purchases, downloads, files, or support.

State when the tool runs executable code, modifies project files, connects to external services, collects telemetry, or requires broad filesystem or network permissions. Provide backup guidance when an operation can overwrite or convert project data.

Disclose generated output that remains in what users create or distribute, including runtime or cloud-based generation. Explain where generation occurs, what information is sent externally, and any terms that affect the user’s output.

Provide a stable documentation, repository, release, or issue-reporting link. State the current development status and avoid implying guaranteed support where none is offered.

• The post is software for game-development work rather than reusable in-game material
• Purpose, intended users, maturity, and limitations are clear
• OS, engine, versions, dependencies, and permissions are accurate
• Installation and update information is sufficient
• Price, license, output rights, redistribution, and credit are unambiguous
• Warnings and generative-AI disclosure are accurate
• External links are correct and safe
• Documentation and support status are current