Links
Tags
Creators
Details
1.0.0
Compatibility
Changes
LaunchGuard v1.0.0 — Marketplace Changelog
LaunchGuard v1.0.0 is the first full stable release after the v0.5.0 marketplace build.
Added Since v0.5.0
- Baseline drift detection
- Baseline save, list, compare, and delete commands
- Baseline drift text reports
- Baseline report history
- Baseline JSON export
- Baseline HTML export
- Optional startup baseline comparison
- Startup baseline text report saving
- Config validation with
/launchguard validate - Local JSON preflight exports
- Local HTML preflight exports
- Plugin inventory overview
- Plugin dependency visibility
- Report and export retention settings
- Baseline report retention setting
Improved
- Clearer command coverage
- Better configuration diagnostics
- Safer baseline name validation
- Safer report filename handling
- More complete documentation
- v1.0 compatibility QA tracking
- Marketplace-safe compatibility wording
Compatibility
Fully smoke-tested:
Paper 1.20.1 through 1.20.6
Paper 1.21.1 through 1.21.10
Load-tested only:
Paper 1.21.11
Not available on PaperMC at QA time:
26.1
26.2
Not tested:
26.3
Safety
LaunchGuard remains read-only.
It does not execute configured commands, modify server state, send network calls, install plugins, download plugins, enable or disable plugins, reload other plugins, teleport players, modify worlds, modify blocks, modify economy data, modify permission data, change whitelist state, force-load chunks, stop the server, restart the server, or block startup.
Notes
LaunchGuard is a pre-launch diagnostic and reporting plugin. It does not fully test plugin behavior and does not verify plugin runtime correctness.
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:ImwvOaBz:UbVSdDa9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ImwvOaBz:UbVSdDa9"
}

