Terms of use
Rules for using work, docs, paid licenses, site content, and external channels.
Last updated: August 4, 2026. The effective date is the date this page is publicly published.
1. Scope and document priority
By accessing or using the LunaDeerMC website, docs, work, and related channels, you agree to follow applicable law, the relevant work license, product-page or order information, and these terms. “Work” includes plugins, server cores, tools, source code, build artifacts, docs, examples, and related assets.
These terms are general rules and do not replace a specific work license or an external platform’s rules. If they differ, applicable law takes priority; the license, copyright notices, and work page govern the use of work code and assets; the relevant product page, order information, and platform rules govern price, validity, payment, delivery, and refunds.
2. Work, docs, and intellectual property
Each work’s license is defined by its work page, included license, and the copyright or license files in its distribution package. Unless a license expressly grants the right, copying, modifying, republishing, distributing, commercial use, or creating a derivative work requires the relevant authorization. The ability to download a work, view its source, or read its docs does not imply that all rights are granted.
Docs help explain how to use a work; they do not replace the official rules for Minecraft, server cores, Java, third-party dependencies, or hosting platforms. Commands, configurations, examples, and compatibility notes may change between versions. Follow the current work page, release notes, and actual runtime environment.
Except for third-party content, material governed by a work license, or material stated otherwise, LunaDeerMC or the relevant rights holder retains rights in the site’s original text, page structure, graphics, and brand assets. When quoting, republishing, or adapting content, keep the required copyright and license information. Do not remove attribution, fabricate official endorsement, or make others believe the content is your original work.
3. Paid work and license rights
Unless a product page, order, or license states otherwise, a paid purchase grants a limited license to use the relevant paid work, not ownership of the work or its source code. The product scope, supported versions, validity period, update scope, download method, and other rights are determined by the product page shown at purchase and the order information.
During the license validity period, a paid license generally includes:
- access to the paid resource and the versions expressly included on its page;
- access to updates released within the scope of that license;
- one-on-one after-sales support submitted through the designated KeyAnchor platform.
One-on-one after-sales support is for installation, configuration, compatibility, and known-issue troubleshooting. It is not custom development, unlimited consultation, a guarantee of new features, or a guarantee that every issue will be fixed within a specified time. When reporting an issue, provide the work version, Minecraft/server-core version, Java version, relevant configuration, complete logs, and reproduction steps. Remove passwords, tokens, and license keys first.
License transfers
Unless a product page, order, or license states otherwise, a paid license may be transferred on a limited basis during its validity period. A transfer must be a complete transfer of the same license and all associated rights except refund rights. Do not split download, update, and after-sales rights or allow multiple people to use the same license. The specific number of transfers, procedure, and limitations are governed by the relevant product rules.
After a transfer, the original holder no longer has the download, update, refund, or after-sales rights associated with the license. A license that has been transferred, sold, gifted, or otherwise given to a third party is not eligible for a refund. Do not transfer, share, or sell a license beyond what the product rules allow.
4. User obligations and prohibited conduct
You must:
- make a backup before installation, upgrades, migrations, or operations that may affect data, and test on a small scale before using them in production;
- use work according to its license, product rules, platform rules, and applicable law;
- take responsibility for your servers, accounts, configuration, backups, keys, and files obtained from third-party platforms;
- remove personal information, passwords, access tokens, license keys, and other confidential material before asking questions or submitting feedback in public channels.
To the extent allowed by the relevant license and law, you must not:
- crack, bypass, or evade licensing, activation, download limits, or technical protection measures;
- copy, forward, mirror, sell, rent, share, or repackage paid resources without authorization;
- publish an unauthorized modified version as official, or use confusing names, Logos, pages, or domains that misrepresent its source;
- attack or abuse the site, work, or external channels, distribute malicious code, infringe others’ rights, or violate platform rules;
- remove or alter copyright, license, or attribution notices in work, distribution packages, or dependencies.
These restrictions do not exclude rights expressly granted by a work license or applicable law.
5. External platforms and account security
Payments, orders, delivery, license activation, refunds, and external-account matters are handled by the relevant third-party platform under its rules. This site does not directly store payment-card information and does not replace a platform’s decisions about order status, account ownership, or platform penalties. External platforms may change prices, interfaces, service scope, or availability; read their current rules before using them.
Keep external-platform accounts, license keys, and purchase records secure. If an account or license is misused, contact the relevant platform immediately and notify the maintenance team through a private channel. Do not post passwords, tokens, or complete license keys in public Issues, chats, or screenshots.
You are responsible for personal-information leaks, stolen keys, or loss of entitlements caused by malicious key sharing. If a key is exposed accidentally, log in to the platform promptly and use self-service key replacement.
6. Availability and responsibility boundaries
The website, docs, work, and support channels may become temporarily unavailable because of maintenance, version upgrades, third-party platform changes, network failures, or circumstances beyond our control. We maintain content within reason, but do not promise that the site or work will always be uninterrupted, error-free, completely secure, permanently compatible, or capable of achieving a particular result.
To the extent allowed by law, users bear the corresponding risk for losses caused by missing backups, incorrect configuration, version mismatch, third-party dependencies, hosting environments, network failures, or failure to follow the docs. See Trademark and disclaimer for specific disclaimers and production-use precautions.
7. Updates and contact
We may update these terms as work, platforms, support processes, or applicable rules change. An updated version applies to use after publication, except where a completed transaction, confirmed order, product page, or applicable law provides otherwise.
For questions about these terms, collaboration, or matters that should not be discussed publicly, contact zhangyuheng@lunadeer.cn. For technical issues, start with the support center and the relevant work docs. For refunds, follow Acquisition, refunds, and disclaimer.