The LeavePulse Agent is distributed as a set of platform-specific .jar files. We recommend always downloading the Agent from official sources to ensure code integrity and security.
Official Sources
1. LeavePulse Dashboard
The easiest way for new servers. On your server's settings page, you'll find a direct link to the build that best fits your platform.
2. Modrinth
We use Modrinth as our primary public repository.
- Project ID:
fMoFcuJh - Link: modrinth.com/plugin/leavepulse-agent
Here you can find version history, detailed changelogs, and metadata for automated downloaders (like Ferium or Prism).
Artifact Types
Depending on your platform, the filename may vary:
| Platform | Artifact Name | Description |
|---|---|---|
| Bukkit / Paper | leavepulse-agent-bukkit.jar | Full "fat" build containing all necessary libraries. |
| Bukkit (Shared) | ...-bukkit-shared-magicutils.jar | Thin build for large networks. Requires the separate MagicUtils plugin. |
| Velocity | leavepulse-agent-velocity.jar | Optimized build for the Velocity proxy. |
| BungeeCord | leavepulse-agent-bungee.jar | For BungeeCord, Waterfall, and compatible proxies. |
| Fabric / NeoForge | leavepulse-agent-mod.jar | Universal mod for Fabric or NeoForge-based servers. |
Release Channels
You can select the system stability in your config file (auto_update.channel):
- Stable: Recommended for production servers. Thoroughly tested before release.
- Beta: New features undergoing final testing. Minor bugs may occur.
- Dev: Automated builds from every commit. For developers and local testing only.
Security & Verification
All official releases are digitally signed. During auto-updates, the Agent verifies:
- SHA-256 Checksum: Ensures the file wasn't altered during download.
- Manifest Signature (Ed25519): Confirms the update originated from the LeavePulse team.