Last updated: July 29, 2026

Purpose

Route marketplace concerns to the smallest appropriate reporting path while keeping public forums free of evidence, accusations, and personal information.

Scope

Applies to listing accuracy, user conduct, reviews, transactions, copyright, security, malware, licensing abuse, and anti-leak concerns.

1. Choose the current path

1. Creator support: installation, configuration, or reproducible product problems.

2. Listing Report control: misleading content, impersonation, harassment, spam, prohibited products, suspected copyright issues, malware, licensing abuse, or other listing-specific concerns.

3. Contact Us: general routing, account, payment, delivery, or scope questions when the listing Report control is not the right fit. Use https://legionnetwork.org/index.php?/contact/.

Do not include payment credentials, license keys, passwords, malware files, exploit instructions, or unnecessary personal information in an initial report. Staff may request an appropriate private follow-up method when needed.

2. What to include

1. Public URL or stable listing/user reference.

2. Concise description of the issue.

3. Dates and version where relevant.

4. The specific rule or claim involved.

5. Minimal redacted evidence.

6. Steps already taken, if safe.

7. Requested review or outcome, without assuming entitlement.

3. What not to include

Do not submit or publish:

- account passwords, access tokens, recovery codes, cookies, or API secrets;

- full payment credentials or unnecessary transaction records;

- license keys or activation identifiers;

- personal information not strictly required;

- live malware in a generic attachment field;

- exploit instructions in a public topic;

- private messages unrelated to the issue;

- public accusations intended to pressure an outcome.

Do not send sensitive security or copyright evidence until staff provides an appropriate private method.

4. Public discussion rules

Marketplace Questions must not host:

1. private order information;

2. payment details;

3. license keys;

4. personal information;

5. security exploits or malware;

6. copyright evidence containing private information;

7. public scam accusations during a private investigation.

Staff may close or remove exposed material and direct the member to a private path. That action protects the case; it does not decide its merits.

5. Staff handling

When a report is accepted for staff review, handling may include:

1. acknowledge and classify the report without promising an outcome;

2. restrict access to need-to-know staff;

3. redact or isolate sensitive attachments;

4. preserve relevant marketplace state and audit references;

5. check conflicts of interest;

6. request only the missing evidence needed;

7. separate platform-rule decisions from payment or legal decisions;

8. give the affected user a fair opportunity to respond where safe and lawful;

9. record the outcome and appeal path;

10. escalate urgent security, safety, or legal matters.

No response-time guarantee is approved.

6. Abuse of reporting

Knowingly false reports, fabricated evidence, impersonation, repeat submission after a final decision without new information, threats, retaliation, and public pressure campaigns may result in action. Good-faith reports are not violations merely because staff cannot substantiate them.

Practical examples

- A wrong compatibility claim: Listing or User Report.

- A plugin crash after installation: creator support first.

- A promised deliverable not supplied: Transaction Dispute.

- A copied map owned by the reporter: Copyright or IP Notice.

- An undisclosed credential webhook: Security or Malware Report.

- A low rating with no rule issue: not a report merely because it is negative.

Possible enforcement outcomes

Possible outcomes may include routing guidance, a correction request, evidence preservation, privacy redaction, review action, listing restriction, release hold, account restriction, no action, or referral to an appropriate payment or legal process.

Appeal or review path

Ask for review through the same private contact path with the original reference, claimed error, and new or overlooked evidence.

Published guidance

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

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/

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

Marketplace Policy Questions: https://legionnetwork.org/index.php?/forums/topic/25-marketplace-policy-questions/

Last updated: July 29, 2026

Purpose

Help creators protect their work, accounts, customers, and reputation without using abusive licensing or retaliation.

Scope

Applies to listing preparation, release delivery, support, licensing, commissioned access, suspected leaks, reviews, and private report evidence.

1. Protect the creator account

1. Use a unique password and available account-security controls.

2. Do not share the owner account with team members.

3. Give collaborators only the access needed for their role.

4. Remove access when a collaboration ends.

5. Keep signing keys, upload credentials, payment credentials, and source repositories out of listing files and support messages.

2. Prepare releases safely

1. Build releases from a known source revision.

2. Remove secrets, customer data, internal logs, and development-only files.

3. Record version, file hashes, build inputs, dependencies, and a concise changelog privately.

4. Test installation and upgrade in a clean environment.

5. Keep a recoverable copy of each published release and its license terms.

6. Treat an unexpected binary, outbound connection, or dependency as a stop condition until explained.

3. Use licensing proportionately

1. Tell buyers what a license check does before purchase.

2. Collect only what is needed for the stated license purpose.

3. Provide a private method to resolve activation errors and false positives.

4. Do not harvest credentials, secretly administer a server, delete files, disable unrelated services, or punish players.

5. Do not publish a suspected leaker's identity, IP address, purchase record, server data, or personal information.

6. Support legitimate transfers when the published license permits them.

7. Licensing and customer-data practices must follow applicable Legion privacy requirements and law.

4. Handle commissioned access

1. Ask for a temporary account or scoped token, not a permanent owner password.

2. State what systems and data will be accessed.

3. Keep customer information out of local test fixtures and screenshots.

4. Record handoff, remove access, and return or delete customer material under the approved process.

5. Report an accidentally exposed credential privately and ask the customer to rotate it. Do not quote or test it.

5. Respond to support and reviews

1. Keep the support channel current.

2. Separate reproducible support issues from review moderation.

3. Do not pressure a buyer to change a rating.

4. Answer factual criticism with evidence and a fix where possible.

5. Report a review only for a policy reason such as fabricated experience, conflict, private information, threats, or irrelevant content.

6. Do not retaliate through license cancellation, service denial, or public accusations merely because feedback is negative.

6. Report suspected leaks privately

1. Preserve the minimum lawful evidence.

2. Do not download from a leak site when doing so creates additional risk or infringement.

3. Use the Report control on the affected listing or Contact Us at https://legionnetwork.org/index.php?/contact/ for private routing.

4. Identify the product/version, the location, why distribution appears unauthorized, and any non-sensitive matching evidence.

5. Allow staff to assess authorization, open-source rights, transfer claims, false positives, and privacy risk before action.

Practical example

A license server sees two activations after a hosting migration. The safe response is to pause only the disputed activation, contact the buyer privately, and offer a reset/review. Remotely deleting the server or posting the buyer's IP address is prohibited.

How to report a violation

Use the Report control on the affected listing or Contact Us at https://legionnetwork.org/index.php?/contact/ for routing. Do not place personal information, license keys, or sensitive leak evidence in a public post.

Possible enforcement outcomes

Possible outcomes may include a correction request, listing or release hold, licensing-practice review, support restriction, review moderation, account restriction, or legal escalation. Legion does not promise recovery of leaked copies.

Appeal or review path

Ask for review through the same private contact path with the existing reference and non-sensitive evidence.

Published guidance

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

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/

Marketplace Policy Questions: https://legionnetwork.org/index.php?/forums/topic/25-marketplace-policy-questions/

Last updated: July 29, 2026

Purpose

Help buyers evaluate digital products and commissioned services before sharing money, access, or server data.

Scope

Applies to Legion Market listings, service offers, creator support, downloads, license systems, and transaction evidence.

1. Check the listing before purchase

1. Match the resource to your exact platform, version, runtime, proxy, and dependencies.

2. Read what is included and excluded.

3. Compare screenshots and demonstrations with the promised files.

4. Check current version, last update, changelog, support route, license, and known limitations.

5. Confirm any external purchase, account, activation, or paid dependency.

6. Treat “lifetime,” “all versions,” “fully secure,” “guaranteed,” and urgent scarcity claims as questions to verify, not facts to assume.

2. Protect accounts and servers

1. Never send a password, recovery code, API secret, private key, payment credential, or unrelated license key.

2. Use temporary, least-privilege access for installation work.

3. Back up configuration and data before installing or updating.

4. Test unfamiliar code in an isolated environment appropriate to the file type.

5. Review documented outbound connections, licensing checks, analytics, webhooks, commands, permissions, and file changes.

6. Stop if the product requests unexplained administrator access or disables security tools.

3. Understand licensing

1. A purchase gives only the rights stated in the applicable license.

2. Do not share the download with friends, customers, public repositories, leak sites, or resale buyers unless the license permits it.

3. Confirm project/use limits, activation limits, transfer rules, and offline behavior before purchase.

4. If a legitimate activation is blocked, use the creator's private false-positive process and keep the license key out of public posts.

4. Commissioned service safety

1. Put scope, files, milestones, revisions, deadlines, acceptance checks, price, ownership, license, and handoff in writing.

2. Divide large work into reviewable milestones when the agreed payment arrangement supports it.

3. Confirm who supplies third-party assets and who pays for licenses.

4. Use a temporary role instead of a shared owner account.

5. Remove access and rotate exposed credentials after handoff.

5. Keep useful evidence privately

Keep:

- the listing and terms shown at purchase;

- approved scope and changes;

- redacted payment confirmation;

- delivery dates and file/version identifiers;

- support attempts and reproducible errors.

Do not post those records publicly. Provide only the minimum needed through the private follow-up method staff requests.

Warning signs

- pressure to move payment or discussion away from approved records;

- a dependency or activation fee revealed only after purchase;

- copied screenshots or ownership claims that cannot be explained;

- requests for full server, hosting, email, Discord, or payment credentials;

- unexplained outbound traffic, obfuscation, remote commands, or data upload;

- threats over reviews or refund questions;

- instructions to disable antivirus, logging, backups, or licensing checks for unrelated products.

Practical example

If a setup requires three premium plugins, the listing should name them and state that they are not included. Discovering those costs after purchase is a listing/report issue, not something a buyer should reveal through a one-star review containing order details.

How to report a problem

- Support/installation: creator's stated support route.

- Misleading listing or conduct: use the Report control on the affected listing.

- Payment, delivery, or scope conflict: contact the creator through the stated support channel, then use Contact Us for routing if needed.

- Copyright or security concern: use the listing Report control and Contact Us for routing; do not include sensitive evidence or malware in the initial message.

- General routing help: https://legionnetwork.org/index.php?/contact/

Possible enforcement outcomes

Depending on the issue and available authority, staff may ask for redacted evidence, request a listing correction, restrict content, or take account action. Refund, chargeback, and payment outcomes depend on approved terms and the actual processor.

Appeal or review path

Ask for review through the same private contact path. Do not threaten the creator, publish personal information, or recruit public pressure around an active matter.

Published guidance

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

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

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/

Last updated: July 29, 2026

Purpose

Answer common marketplace questions without promising unverified commerce, support, or legal outcomes.

Scope

Applies to Legion Market catalog, listings, services discussions, licensing, support, reviews, and private reports.

1. What is Legion Market?

Legion Market is the LegionNetwork.org marketplace for ready-made digital resources. The live catalog currently shows plugins, server setups, builds, scripts, models, website assets, and related categories.

2. Are services and products the same?

No. Product listings are ready-made resources. Service forums cover custom or commissioned work. Legion Services is a separate package/request system.

3. Does Legion verify every creator or file?

Do not assume that. This audit did not verify identity checks, source review, malware scanning, seller approval, or a complete moderation standard.

4. Are purchases held in escrow?

Legion has not published an escrow or merchant-of-record claim. Do not assume Legion holds funds in escrow.

5. Can I get a refund?

Eligibility, authority, deadlines, and payment-provider effects are unresolved. No dedicated refund or transaction-dispute route was verified when this guide was published. Contact the creator through the stated support channel first. If routing help is needed, use Contact Us at https://legionnetwork.org/index.php?/contact/ without including sensitive payment details. A request does not guarantee a refund.

6. Where are my downloads and licenses?

The current navigation exposes My Licenses and listing downloads. Access depends on the listing, account, purchase, release, and license terms. Refund/chargeback effects were not verified.

7. Are future updates included?

Only if the listing and approved license say so. A current version and update history do not guarantee every future release.

8. What if a resource needs another plugin or account?

The creator must disclose required and optional dependencies, lawful source, price or license requirement, and purpose. Ask before purchase if anything is unclear.

9. Where do I ask for installation help?

Use the support topic or external support URL stated by the creator. for creator-selected channels. Do not place license keys or credentials in a public topic.

10. Where do I report a misleading or unsafe listing?

Use the Report control on the affected listing.

11. Where do I report malware or a security problem?

Use the listing Report control and Contact Us at https://legionnetwork.org/index.php?/contact/ for routing. Do not upload a live sample to a public forum or post exploit instructions.

12. How do copyright complaints work?

Use the listing Report control and Contact Us at https://legionnetwork.org/index.php?/contact/ for routing. Do not use reviews or public accusations as copyright notices, and do not include unnecessary private evidence in the initial message.

13. Can I leave a review?

Listings have a Reviews tab. This audit did not verify whether only purchasers or downloaders can post. Reviews must be truthful, relevant, independent, and free of private information.

14. Can a creator reward a positive review?

No. A reward, discount, free product, payment, or support benefit may not be conditioned on positive sentiment. Any neutral feedback program must be clearly disclosed and may not condition a benefit on positive or negative sentiment.

15. Can I resell or share a download?

Only if the license expressly allows it. Access to a file is not permission to leak, resell, sublicense, or redistribute it.

16. Can a creator remotely disable a leaked copy?

Reasonable disclosed license checks may be allowed. Secret remote administration, destructive punishment, unrelated service disruption, and credential collection are prohibited. False positives need a private review path.

17. Are AI-generated products allowed?

A final AI and generated-content policy has not yet been published. Creators must not use generated content to mislead buyers, impersonate others, or violate third-party rights.

18. Is VIP or Ultimate required?

The current site shows a VIP subscription. No Ultimate plan was observed, and another marketplace's Ultimate terminology does not apply.

Practical example

A bug that appears only after installation belongs in creator support. A false compatibility claim belongs in a listing report. A payment or delivery conflict belongs in creator support first, followed by Contact Us for routing if needed. The same issue should not be copied into all three places.

How to report a violation

Use the Report control on the affected listing, or Contact Us at https://legionnetwork.org/index.php?/contact/ for routing.

Possible enforcement outcomes

Possible outcomes may include an explanation, content correction, review moderation, listing restriction, or account action. Refunds, payment reversals, and legal remedies are not promised here.

Appeal or review path

Ask for review through the same private contact path and include the existing reference.

Published guidance

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

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/

Marketplace Policy Questions: https://legionnetwork.org/index.php?/forums/topic/25-marketplace-policy-questions/

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/

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/