Acquisition, refunds, and disclaimer
Free-work acquisition, paid licenses, refund procedures, sponsorship, and related responsibility boundaries.
Last updated: August 4, 2026. The effective date is the date this page is publicly published.
1. Scope and acquisition channels
This page explains the acquisition, delivery, refund, and responsibility boundaries for LunaDeerMC free work, paid work, and sponsorships. If a product page, order record, work license, third-party platform rule, or applicable law provides otherwise, the rule that applies to the specific matter takes priority.
This site is static and does not directly provide online payment, order management, or license activation. Payments, order records, license delivery, accounts, and platform-side refunds are handled by the relevant third-party platform; the maintenance team may help verify a request from order records but does not replace the platform’s payment-settlement system.
2. Free work
Obtain free work from the official repository, GitHub Releases, Modrinth, or another clearly marked channel listed on the relevant work page. Before downloading, check the work name, version, Minecraft version, server platform, and file name. Do not obtain work from unknown mirrors, modified packages, or so-called cracked versions.
Free work remains subject to its license, copyright notices, and third-party dependency licenses. Free acquisition does not waive attribution, license, trademark, or other usage restrictions.
3. Paid-work purchase and delivery
Paid work is generally purchased through the Afdian shop, then activated, extracted, or supported through KeyAnchor. Different products may use different delivery methods. Before purchasing, confirm the product name, price, supported versions, license validity period, update scope, and support scope.
Whether payment succeeded, an order was accepted, or a license was issued is determined by the page and records of Afdian or the actual transaction platform. Keep the order ID, purchasing account, payment time, and license information for later verification. Do not publicly share a license key, login credentials, or payment screenshots containing sensitive information.
A paid purchase grants the limited license described by the product page and license. It does not grant ownership of the work, ownership of its source code, or the right to redistribute the resources to others. The download, update, after-sales, and transfer scope of a paid license is governed by the Terms of use and the relevant product rules.
4. Paid-product refunds
4.1 Refund conditions
Unless a product page, platform rule, or applicable law provides otherwise, every paid product supports a refund without stating a reason within 7 calendar days after the order payment succeeds. The request must include valid proof of purchase, and the authorization must not have been transferred, sold, gifted, shared, or otherwise given to a third party.
The refund amount is generally the actual amount paid minus transaction or payment fees that were incurred and actually charged by the third-party platform. Any deduction and its amount must also comply with applicable law and the transaction platform’s rules. If applicable law imposes a mandatory refund amount, period, or method, follow the legal requirement.
Once an authorization is transferred, the original purchaser transfers all download, update, and after-sales rights with it and no longer has a right to a refund. However, the transferred rights do not include refund rights, and the recipient of a transfer is limited to the person who actually made the payment.
When none of the transfer circumstances above has occurred, downloading or normally activating the resource by itself does not affect a refund request made within the 7-day period. A product page, platform rule, or applicable law that expressly provides otherwise takes priority.
4.2 Request process
Contact the author through QQ at 2751268851 for manual handling. If QQ is unavailable, email zhangyuheng@lunadeer.cn with “Refund request” in the subject line. To help us verify the request, provide:
- the purchased service, work, or product name;
- the order ID, purchasing account, screenshot, or other verifiable proof of purchase;
- the payment time and a contact method for the request;
- a factual statement of whether the license has been activated, transferred, or given to another person.
Do not provide passwords, payment-card numbers, complete login credentials, or sensitive information unrelated to the refund. The maintenance team may request reasonable additional order-verification materials. Incomplete materials, an unverified purchase relationship, or a transferred authorization may extend the processing time or prevent approval.
4.3 Processing and settlement
The maintenance team manually verifies refund requests and reports the result through the original contact channel. Once approved, the refund is normally initiated through the original payment platform or payment method. The actual settlement time depends on Afdian, the payment institution, the bank, or another transaction platform, and this site cannot promise a specific arrival time.
If the order is managed directly by a third-party platform, that platform may require you to submit the request through its own page. You must also follow that platform’s refund rules. Do not use repeated submissions, malicious disputes, or public disclosure of order information to pressure the review.
5. Sponsorship and support
Sponsorship is voluntary support for project maintenance, infrastructure, and exploration of new work. It is not a purchase of paid work, a service purchase, or a license to a specific work. Unless a sponsorship page expressly promises otherwise, sponsorship does not guarantee new features, custom development, delivery of a specified version, or one-on-one service.
Sponsorship payments generally do not support refunds. If applicable law or the sponsorship platform’s rules impose a mandatory exception, follow those rules. Sponsorship and paid-work purchases are separate matters; a sponsorship record cannot replace proof of purchase for paid work.
6. Pre-use checks and disclaimer
Before installation or upgrade, confirm that your backups are usable. On a test server similar to production, verify the Minecraft version, Java version, server core, plugin/mod dependencies, configuration, and data-migration results. For tools that may modify, migrate, or delete worlds, databases, or configuration, make a complete backup and confirm the recovery plan first.
Work, docs, download channels, and support are provided as-is and as-available. To the extent allowed by law, we do not guarantee that:
- a work will fit every server, client, operating system, network environment, or third-party plugin combination;
- a work will always be error-free, uninterrupted, secure, or free from data loss;
- external-platform pages, interfaces, prices, delivery, accounts, and services will remain unchanged;
- one-on-one support will solve every environment issue, provide custom development, or deliver a result within a fixed period.
Problems caused by external platforms, third-party dependencies, the user’s environment, incorrect configuration, missing backups, or violations of licenses and platform rules should be handled through the correct channel for the relevant platform or work.