Tags
Creators
Details
1.3
Compatibility
Changes
GeyserUpdater 1.3
This release improves updater reliability, platform detection, and automatic restart handling.
Added
- Added
postUpdate.restartDelaySeconds- Allows delaying the configured restart command after an update
- Default:
0seconds
- Delayed automatic restart support for:
- Paper / Spigot
- BungeeCord
- Velocity
- Added platform-aware Geyser and Floodgate JAR detection
- Added automatic detection to prevent GeyserUpdater itself from being mistaken for a Geyser JAR
- Added automated tests for updater JAR detection and restart delay configuration
Fixed
- Fixed overly broad Geyser/Floodgate JAR matching
- Fixed cases where unrelated or incorrectly named JAR files could be selected for replacement
- Fixed GeyserUpdater potentially being detected as the plugin it was supposed to update
- Fixed MCXboxBroadcast extension installation paths on proxy platforms
- MCXboxBroadcast is now installed into the correct platform-specific Geyser extensions folder
Examples:
Paper / Spigot:
plugins/Geyser-Spigot/extensions
BungeeCord:
plugins/Geyser-BungeeCord/extensions
Velocity:
plugins/Geyser-Velocity/extensions
Automatic restart delay
You can now configure a delay before the automatic restart command is executed:
postUpdate:
runRestartCommand: true
restartCommand: "restart"
restartDelaySeconds: 60
For BungeeCord, the restart command can for example be set to end.
Negative restart delay values are automatically treated as 0.
Changed
- Updated internal version information to
1.1.0 - Updated the HTTP User-Agent to
GeyserUpdater/1.1.0 - Improved resource handling while scanning plugin directories
- Updated English and Japanese documentation for the new restart delay and platform-specific extension paths
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:GOBGotbW:joSAnmev"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GOBGotbW:joSAnmev"
}

