Creator and Listing Guidelines

Effective date: July 29, 2026

Last updated: July 29, 2026

Purpose

Help creators prepare listings that buyers can understand, install, license, and support safely.

Scope

Applies to ready-made digital products and, where noted, commissioned service offers.

1. Listing identity

1. Use one clear product name without fake rankings, unrelated keywords, pricing claims, version stuffing, or copied competitor marks.

2. Select the closest current category.

3. Explain the problem solved, the intended user, and what the package contains.

4. Identify whether the listing delivers files through Legion or uses an approved external-purchase route.

5. Do not create duplicate listings for trivial variants.

2. Required description checklist

Include:

1. exact files and major components;

2. supported and tested game/software versions;

3. required runtime, server type, library, plugin, account, or paid dependency;

4. optional dependencies and the feature each enables;

5. installation and upgrade prerequisites;

6. material limitations, conflicts, and known issues;

7. external services, analytics, update checks, webhooks, and licensing calls;

8. data collected, purpose, recipient, and approved privacy/retention summary;

9. support channel, included help, exclusions, and maintenance status;

10. license summary and link to the full approved terms.

3. Images and demonstrations

1. Use images from the delivered product or label mockups clearly.

2. Do not show premium assets, shaders, builds, UI, integrations, or performance that the buyer will not receive.

3. Redact private server details, player information, license keys, and credentials.

4. Generated media must not misrepresent the work, assets, or functionality included with the listing.

4. Compatibility and dependencies

1. State what was actually tested.

2. Separate “supported,” “expected to work,” and “not tested.”

3. Give lawful dependency links and state price/license requirements.

4. Do not bundle another product merely for convenience unless redistribution rights permit it.

5. For forks or server JARs, document the upstream project and comply with its license, source or patch obligations, and applicable platform terms.

5. Files and versions

1. Deliver the advertised files in an organized package.

2. Remove credentials, development secrets, private logs, personal data, unrelated build artifacts, and customer-specific configuration.

3. Use a consistent version scheme.

4. Changelogs must state added, changed, fixed, removed, security, dependency, and migration information where relevant.

5. A security update must not conceal the affected versions or required action.

6. Do not overwrite a release merely to hide material history.

6. Licensing systems

1. Disclose whether activation is required and what identifiers are used.

2. Explain external connections, failure behavior, offline behavior, use limits, reset handling, false-positive handling, and transfer rules.

3. Never collect account credentials or unrelated product license keys.

4. Never use remote deletion, secret administration, server shutdown, or destructive punishment.

5. Minimize data and follow the applicable Legion privacy and deletion requirements.

6. If Legion requests a safety review, provide a safe assessment method without publishing source code or license-bypass instructions.

7. Creator support

1. Choose the support-topic or alternative-URL option that will be maintained.

2. State supported topics and exclusions.

3. Keep troubleshooting separate from reviews.

4. Do not demand a better rating before helping.

5. If support ends, update the listing and preserve any obligations already approved in the applicable terms.

8. Service offers

Before starting a commissioned service, record:

1. deliverables and exclusions;

2. input requirements and access method;

3. milestones and deadlines;

4. revision count and change-order method;

5. acceptance tests;

6. ownership, license, and third-party asset treatment;

7. source/editable-file and documentation handoff;

8. cancellation, refund, and dispute terms the parties are authorized to offer.

Practical example

“Tested on Paper 1.21.4 with Java 21. Vault is required; PlaceholderAPI is optional. The plugin contacts the licensing endpoint at startup and once every 24 hours. It sends the license key and the server identifier chosen by the buyer. No player data is required. See the full privacy and license notice.”

The disclosure must match the product’s actual behavior and applicable privacy requirements.

How to report a listing problem

Use the Report control on the affected listing. For security, copyright, or account-routing help, use Contact Us at https://legionnetwork.org/index.php?/contact/ and do not include sensitive evidence in the initial message.

Possible enforcement outcomes

Possible outcomes may include a correction request, return to draft, visibility restriction, release hold, unsafe-file removal, submission restriction, listing removal, or account restriction, depending on available authority and the facts.

Appeal or review path

Ask for review through the same private contact path, identifying the listing, decision, relevant guidance, and corrected evidence. Do not submit a second listing to bypass a hold.

Published guidance

Start Here: https://legionnetwork.org/index.php?/forums/topic/19-start-here-how-legion-market-works/

Creator Safety Guide: https://legionnetwork.org/index.php?/forums/topic/23-creator-safety-guide/

Reporting Listings, Users, and Conduct: https://legionnetwork.org/index.php?/forums/topic/24-reporting-listings-users-and-conduct/