1. Ownership and scope
Exclusive rights in the original LovsPlayer code and materials owned by webhm
(the Rightsholder) remain with the Rightsholder. Receiving a copy of the mod
does not transfer ownership of those rights. This agreement applies only to
the components for which the Rightsholder may grant such rights; third-party
components are governed by section 6.

2. Permitted use
The user receives a limited, non-exclusive permission to install and run an
officially obtained, unmodified copy of LovsPlayer in single-player games and
on servers that comply with this agreement. Copies necessary for permitted
installation, execution and personal backup are allowed. All other rights
are reserved unless expressly granted in writing or by mandatory law.

3. Copying and redistribution restrictions
Without the Rightsholder's prior express written permission, it is prohibited
to copy or reuse the original code, in whole or in part, in another project;
to distribute, republish, sell or supply the mod file, its source code or
modified versions to third parties; or to include the mod file in distributed
modpacks, launchers or server packages. Removing ownership notices or claiming
the mod or its original components as one's own work is prohibited.
Sharing a link to an official download source is allowed. Users and server
players must obtain their own copies from an authorized source.

4. Server audience limit
Without separate permission under section 5, the mod may be used only on a
server visited by no more than 20 unique player accounts in any rolling
24-hour period. This is a daily unique-account limit, not a concurrent-player
limit and not a calendar-day counter that resets at midnight.
All accounts that connect to the server count, including administrators,
whether or not they use the mod's features. Repeated connections by the same
account count once in that period; different accounts count separately.
Accounts are identified by their game UUIDs, without manipulating identifiers
to evade the limit. For connected servers under common management forming
one server network, count unique accounts across the entire network, without
double-counting the same account between its servers. Splitting that network
into instances to evade the limit is not permitted.

5. Permission for larger servers
Before using the mod on a server or network exceeding, or planned to exceed,
the limit in section 4, its operator must personally contact the Rightsholder
and obtain the Rightsholder's express written permission. Permission must
identify the server or network and the agreed conditions. It applies only
to the agreed recipient, server or network, scope and duration.
An inquiry, silence, a third party's statement, subscription or donation does
not by itself constitute permission. Without permission, the operator must
keep use within the limit or discontinue use before exceeding it.
Official Telegram channel: https://t.me/chubrik13
Official Boosty page: https://boosty.to/projectlovs
Use the contact options published on these official pages to reach webhm
personally; the channel link itself is not an authorization.

6. Third-party components and mandatory rights
Third-party libraries and materials remain the property of their respective
rightsholders and retain their own licenses. See THIRD-PARTY-NOTICES.txt and
META-INF/licenses/ in this JAR. This agreement does not restrict permissions
granted by those licenses or rights that mandatory applicable law preserves.
In particular, it does not prohibit replacing or modifying an LGPL library,
or modifying this work for the user's own use and reverse engineering for
debugging such modifications to the extent required by the LGPL.
Minecraft and other third-party products retain their own terms.

7. Breach
To the extent permitted by applicable law, permission under this agreement
terminates upon breach of its conditions. The user must cease unauthorized
use and distribution. The Rightsholder may pursue remedies provided by
applicable law. This agreement does not prescribe automatic fines or create
a technical player-count enforcement mechanism.

The Russian and English versions state the same permitted uses and limits.
Separate written permissions remain governed by their expressly agreed terms.