ВЕРСИИ (12)

## [0.10.3] - 2026-10-27 ### Fixed - **Plugins set up with the browser tool or the injector keep checking for updates after an update.** The update is the author's own jar, which has no PluginPulse in it, so the updater used to disappear after the first one. PluginPulse now adds itself to the new jar, with the same settings, before installing it. If that isn't possible (the author moved the main class, or the command-line tool changed a `final` main class in place), the console says so.

## [0.10.3] - 2026-10-27 ### Fixed - **Plugins set up with the browser tool or the injector keep checking for updates after an update.** The update is the author's own jar, which has no PluginPulse in it, so the updater used to disappear after the first one. PluginPulse now adds itself to the new jar, with the same settings, before installing it. If that isn't possible (the author moved the main class, or the command-line tool changed a `final` main class in place), the console says so.

## [0.10.3] - 2026-10-27 ### Fixed - **Plugins set up with the browser tool or the injector keep checking for updates after an update.** The update is the author's own jar, which has no PluginPulse in it, so the updater used to disappear after the first one. PluginPulse now adds itself to the new jar, with the same settings, before installing it. If that isn't possible (the author moved the main class, or the command-line tool changed a `final` main class in place), the console says so.

## [0.10.2] - 2026-10-26 ### Added - **BuiltByBit as an update source, for checking only.** Set `builtbybit:` to the resource id and `builtbybit-token:` to your own BuiltByBit API key, best as an environment variable (`"${BBB_TOKEN}"`) since the key belongs to your account. BuiltByBit doesn't let outside tools download files, so PluginPulse tells you a new version is out and links to the resource's updates page; you download it there yourself. - **The browser tool and the command-line injector now handle Velocity plugins.** They add the proxy version of the updater to a Velocity plugin jar, leaving its `velocity-plugin.json` as it is, and a jar made for both Paper and Velocity gets both. Updates are installed when the proxy shuts down; nothing restarts the proxy or reloads plugins on its own. ### Changed - **The guides now say plainly that PluginPulse never restarts or reloads anything on a Velocity proxy**, so a permissions plugin such as LuckPerms is never switched off underneath your players. ## [0.10.1] - 2026-10-26 ### Fixed - **Paper and Spigot servers no longer get offered a Fabric, NeoForge or Velocity file from Modrinth.** When a project publishes one version per platform, the newest one could be for another platform (LuckPerms' newest is a NeoForge build). PluginPulse now asks Modrinth only for files this server can run: Paper, Spigot, Bukkit, Purpur or Folia on a server, Velocity on a proxy. A source with its own loader list keeps it.

## [0.10.2] - 2026-10-26 ### Added - **BuiltByBit as an update source, for checking only.** Set `builtbybit:` to the resource id and `builtbybit-token:` to your own BuiltByBit API key, best as an environment variable (`"${BBB_TOKEN}"`) since the key belongs to your account. BuiltByBit doesn't let outside tools download files, so PluginPulse tells you a new version is out and links to the resource's updates page; you download it there yourself. - **The browser tool and the command-line injector now handle Velocity plugins.** They add the proxy version of the updater to a Velocity plugin jar, leaving its `velocity-plugin.json` as it is, and a jar made for both Paper and Velocity gets both. Updates are installed when the proxy shuts down; nothing restarts the proxy or reloads plugins on its own. ### Changed - **The guides now say plainly that PluginPulse never restarts or reloads anything on a Velocity proxy**, so a permissions plugin such as LuckPerms is never switched off underneath your players. ## [0.10.1] - 2026-10-26 ### Fixed - **Paper and Spigot servers no longer get offered a Fabric, NeoForge or Velocity file from Modrinth.** When a project publishes one version per platform, the newest one could be for another platform (LuckPerms' newest is a NeoForge build). PluginPulse now asks Modrinth only for files this server can run: Paper, Spigot, Bukkit, Purpur or Folia on a server, Velocity on a proxy. A source with its own loader list keeps it.

## [0.10.2] - 2026-10-26 ### Added - **BuiltByBit as an update source, for checking only.** Set `builtbybit:` to the resource id and `builtbybit-token:` to your own BuiltByBit API key, best as an environment variable (`"${BBB_TOKEN}"`) since the key belongs to your account. BuiltByBit doesn't let outside tools download files, so PluginPulse tells you a new version is out and links to the resource's updates page; you download it there yourself. - **The browser tool and the command-line injector now handle Velocity plugins.** They add the proxy version of the updater to a Velocity plugin jar, leaving its `velocity-plugin.json` as it is, and a jar made for both Paper and Velocity gets both. Updates are installed when the proxy shuts down; nothing restarts the proxy or reloads plugins on its own. ### Changed - **The guides now say plainly that PluginPulse never restarts or reloads anything on a Velocity proxy**, so a permissions plugin such as LuckPerms is never switched off underneath your players. ## [0.10.1] - 2026-10-26 ### Fixed - **Paper and Spigot servers no longer get offered a Fabric, NeoForge or Velocity file from Modrinth.** When a project publishes one version per platform, the newest one could be for another platform (LuckPerms' newest is a NeoForge build). PluginPulse now asks Modrinth only for files this server can run: Paper, Spigot, Bukkit, Purpur or Folia on a server, Velocity on a proxy. A source with its own loader list keeps it.

## [0.10.0] - 2026-10-26 ### Added - **Velocity support, for the library and the companion.** Plugins for Velocity proxies can shade `pluginpulse-velocity` and use the same `pluginpulse.yml`, and proxy owners get their own companion jar, run with `/pulseproxy` (or `/ppp`) so it never hides `/pluginpulse` on the servers behind it. Works on Velocity 3.4 up to 4.3. Downloaded updates are put in place when the proxy shuts down, since Velocity can't swap a running plugin. - **Picks the Velocity download** when a plugin publishes one file per platform: Modrinth and Hangar are asked for Velocity builds, and on GitHub a file with "velocity" in its name is preferred. ### Changed - **The platform-free part of the library now lives in `pluginpulse-common`.** `pluginpulse-core` pulls it in on its own, so a build that shades core keeps working with no change. The Paper API is untouched. - **Updated the build tools and libraries** to their current releases, including Gradle 9.8.2. ### Fixed - **The command-line injector reads plugins built for Java 25**, which most Minecraft 26.x plugins are. It used to stop with an "unsupported class file" error.

## [0.10.0] - 2026-10-26 ### Added - **Velocity support, for the library and the companion.** Plugins for Velocity proxies can shade `pluginpulse-velocity` and use the same `pluginpulse.yml`, and proxy owners get their own companion jar, run with `/pulseproxy` (or `/ppp`) so it never hides `/pluginpulse` on the servers behind it. Works on Velocity 3.4 up to 4.3. Downloaded updates are put in place when the proxy shuts down, since Velocity can't swap a running plugin. - **Picks the Velocity download** when a plugin publishes one file per platform: Modrinth and Hangar are asked for Velocity builds, and on GitHub a file with "velocity" in its name is preferred. ### Changed - **The platform-free part of the library now lives in `pluginpulse-common`.** `pluginpulse-core` pulls it in on its own, so a build that shades core keeps working with no change. The Paper API is untouched. - **Updated the build tools and libraries** to their current releases, including Gradle 9.8.2. ### Fixed - **The command-line injector reads plugins built for Java 25**, which most Minecraft 26.x plugins are. It used to stop with an "unsupported class file" error.

## [0.10.0] - 2026-10-26 ### Added - **Velocity support, for the library and the companion.** Plugins for Velocity proxies can shade `pluginpulse-velocity` and use the same `pluginpulse.yml`, and proxy owners get their own companion jar, run with `/pulseproxy` (or `/ppp`) so it never hides `/pluginpulse` on the servers behind it. Works on Velocity 3.4 up to 4.3. Downloaded updates are put in place when the proxy shuts down, since Velocity can't swap a running plugin. - **Picks the Velocity download** when a plugin publishes one file per platform: Modrinth and Hangar are asked for Velocity builds, and on GitHub a file with "velocity" in its name is preferred. ### Changed - **The platform-free part of the library now lives in `pluginpulse-common`.** `pluginpulse-core` pulls it in on its own, so a build that shades core keeps working with no change. The Paper API is untouched. - **Updated the build tools and libraries** to their current releases, including Gradle 9.8.2. ### Fixed - **The command-line injector reads plugins built for Java 25**, which most Minecraft 26.x plugins are. It used to stop with an "unsupported class file" error.

## [0.9.0] - 2026-09-23 Tested on Paper 26.3 (build 35) and Spigot 26.3: update checks, downloads, installs on restart, installs without a restart, and the companion plugin. ### Added - **Picks the download made for your server's Minecraft version.** When a plugin publishes separate jars (for example 1.21, 26.1 and 26.3), PluginPulse takes the one Modrinth or Hangar lists for your server, with no `track` needed. Turn it off with `match-server-version: false`. - **Releases are built and published automatically** when a version is tagged, with both companion jars attached. ### Fixed - **Stopping the server during an update check no longer prints errors.** It used to show a "nag the author" error, or a "zip file closed" error against the plugin that bundles PluginPulse. - **The companion plugin now manages plugins that start after it.** Before, it skipped them with "Managing 0 plugin(s)", depending on the order the server enabled plugins. - **After an install without a restart, the update command works again.** It kept talking to the old version and failed until the next restart. - **Installing without a restart works on Spigot.** It used to fail halfway, leaving the plugin switched off with no commands until a restart. - **Installing without a restart no longer runs the plugin's startup step twice** on Paper. - **Update notices on Spigot read cleanly.** Part of the button text used to show up as raw markup. - **Installing without a restart now respects plugins that depend on it** through `paper-plugin.yml`, not only `plugin.yml`. - **`update status` tells the truth before the first check and after a failed one.** It used to say "up to date" in both cases. - **The self-registered update command now tells players they lack permission** instead of saying nothing. - **A track that has no release never falls back to another track's jar** on Modrinth. A plain version with no suffix is still accepted. - **Servers with a Turkish system language get the right default permission** (`plugin.update`, not a dotless-i spelling). - **Version text from an update source can no longer change what a clickable message does.**

## [0.9.0] - 2026-09-23 Tested on Paper 26.3 (build 35) and Spigot 26.3: update checks, downloads, installs on restart, installs without a restart, and the companion plugin. ### Added - **Picks the download made for your server's Minecraft version.** When a plugin publishes separate jars (for example 1.21, 26.1 and 26.3), PluginPulse takes the one Modrinth or Hangar lists for your server, with no `track` needed. Turn it off with `match-server-version: false`. - **Releases are built and published automatically** when a version is tagged, with both companion jars attached. ### Fixed - **Stopping the server during an update check no longer prints errors.** It used to show a "nag the author" error, or a "zip file closed" error against the plugin that bundles PluginPulse. - **The companion plugin now manages plugins that start after it.** Before, it skipped them with "Managing 0 plugin(s)", depending on the order the server enabled plugins. - **After an install without a restart, the update command works again.** It kept talking to the old version and failed until the next restart. - **Installing without a restart works on Spigot.** It used to fail halfway, leaving the plugin switched off with no commands until a restart. - **Installing without a restart no longer runs the plugin's startup step twice** on Paper. - **Update notices on Spigot read cleanly.** Part of the button text used to show up as raw markup. - **Installing without a restart now respects plugins that depend on it** through `paper-plugin.yml`, not only `plugin.yml`. - **`update status` tells the truth before the first check and after a failed one.** It used to say "up to date" in both cases. - **The self-registered update command now tells players they lack permission** instead of saying nothing. - **A track that has no release never falls back to another track's jar** on Modrinth. A plain version with no suffix is still accepted. - **Servers with a Turkish system language get the right default permission** (`plugin.update`, not a dotless-i spelling). - **Version text from an update source can no longer change what a clickable message does.**

Jenkins CI as an update source: point `jenkins:` at a job page URL (e.g. FastAsyncWorldEdit on ci.athion.net) and PluginPulse follows the last successful build, with an optional `jenkins-artifact` regex to pick the right jar. Supported in the library, the companion plugin, and the web tool. **Full Changelog**: https://github.com/darkstarworks/PluginPulse/compare/v0.7.0...v0.8.0