Start Here: How Legion Market Works

Effective date: July 29, 2026

Last updated: July 29, 2026

Purpose

Explain the difference between a listing, a service offer, creator support, a review, and a private case before someone buys, sells, or posts.

Scope

This guide applies to Legion Market listings and marketplace discussion areas. It does not replace a listing's license, creator terms, Legion's site terms, or payment-provider rules.

1. Know which part of Legion you are using

1. Software Marketplace listings are ready-made digital resources such as plugins, builds, setups, scripts, models, and website assets.

2. Marketplace service forums are for commissioned or custom work.

3. Legion Services is a separate service-package system. A link from a marketplace listing to Legion Services does not turn the listing into the same product or transaction.

4. A public discussion post is not proof that Legion endorses a seller, guarantees delivery, holds funds, or will issue a refund.

2. Before buying

1. Read the exact title, description, included files, supported versions, dependencies, installation steps, support channel, license, and update history.

2. Confirm whether the listing is a direct upload or uses an external purchase path. Review the delivery method on each listing.

3. Save the listing and license terms shown at the time of purchase without publishing order or payment details.

4. Ask the creator a clear pre-sale question if compatibility or scope is uncertain.

5. Do not assume “lifetime,” future-version access, installation, customization, or refunds unless the approved terms say so.

3. Before creating a listing

1. Use a clear name, correct category, accurate description, current version, representative screenshots, and complete delivery package.

2. Disclose required and optional dependencies, supported platforms and versions, installation requirements, external connections, license checks, data collection, and support limits.

3. Upload only work you own or have documented rights to distribute.

4. For services, define deliverables, exclusions, revisions, deadlines, communication, testing, and handoff before work begins.

5. Keep release notes truthful. A new version must describe real changes.

4. Downloads, licenses, and support

1. Legion currently exposes My Licenses, versioned releases, creator-selected support channels, and license-key settings.

2. The presence of those controls does not prove that a buyer may transfer a license, use it on unlimited projects, or receive every future update.

3. Use the creator's stated support path for installation or configuration help.

4. Use the listing Report control for a listing-specific concern, or Contact Us for routing help. Do not post transaction, copyright, malware, or other sensitive evidence publicly.

5. Reviews are not support tickets

1. A review should describe a genuine experience with the resource or service.

2. A reproducible bug or request for help belongs in the creator's support channel.

3. Misleading content or misconduct belongs in a report.

4. Copyright ownership concerns should use the listing Report control or Contact Us for private routing.

5. Payment, delivery, or agreed-scope concerns should go to the creator’s support channel first, then Contact Us for private routing if needed.

Practical examples

- Good pre-sale question: “Does version 1.4 support Paper 1.21.4 without ProtocolLib?”

- Support request: “The documented install command fails after step three; here is a redacted error excerpt.”

- Review: “The advertised Paper version worked, but the setup guide omitted one required restart.”

- Private report: “The download opens an undisclosed outbound connection; evidence is attached privately.”

How to report a problem

For a listing-specific concern, use the Report control on that listing. For general routing help, use Contact Us at https://legionnetwork.org/index.php?/contact/. Do not include payment details, license keys, credentials, or personal information in the initial message.

Possible enforcement outcomes

Depending on the issue and available authority, outcomes may include guidance, a request for more information, content correction, review moderation, listing restriction, temporary hiding, removal, account restriction, or referral to an appropriate payment or legal process. A report does not guarantee a particular outcome.

Appeal or review path

If you believe staff overlooked a factual detail, use the same private contact path with the existing reference and identify the specific error. Do not open repeated public topics about an active matter.

Published guidance

Creator and Listing Guidelines: https://legionnetwork.org/index.php?/forums/topic/20-creator-and-listing-guidelines/

Marketplace FAQ: https://legionnetwork.org/index.php?/forums/topic/21-marketplace-faq/

Buyer Safety Guide: https://legionnetwork.org/index.php?/forums/topic/22-buyer-safety-guide/

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