Licensing / MxF Factions
MxF Factions checks its MxF Labs license before loading factions, players, claims, commands, listeners, or gameplay services.
Docs version
v1.0.0
Product version
1.0.0-dev
Last updated
Jul 21, 2026
# Runtime Licensing
MxF Factions checks its MxF Labs license before loading factions, players, claims, commands, listeners, or gameplay services.
1. Install the latest MxF-Factions.jar.
2. Start the server once.
3. Open plugins/Factions/config.yml.
4. Set the single customer-editable license value:
license-key: "MXF-XXXX-XXXX-XXXX-XXXX"5. Restart the server.
6. Confirm the console reports MxF license valid before faction data loads.
The API URL, product slug, request timeouts, device identity, install identity, and enforcement rules are internal and are not configurable by resource owners.
The plugin starts only when the live activation response is valid for MxF Factions. It fails closed for:
missing or invalid keys
wrong product
expired, revoked, suspended, or blacklisted licenses
HWID/device mismatch
strict IP mismatch
activation limit reached
blocked plugin version
suspicious account activity
malformed API responses
an unavailable license API
The API denial code and safe message are printed to console. The full license key is never logged.
plugins/Factions/mxf-license-instance.id is generated automatically and is not configuration. It gives the server installation a stable identity for activation and HWID checks.
Moving the installation to another machine may require an activation reset through MxF Labs. Do not copy one plugin data folder to several active servers.
Keep config.yml private because it contains the customer key.
Do not paste the full key into public tickets, screenshots, or logs.
The API endpoint uses HTTPS and is pinned in the plugin.
Product and version policy is decided by the MxF Labs license record.
A key change takes effect on the next full server restart, before gameplay initialization.