Links
Tags
Creators
Details
All versions
0.3.0
Release
LaunchGuard 0.3.04 months ago 16
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
Platform
Paper
Changes
LaunchGuard v0.3.0
Added:
- Optional startup preflight checks
- Saved plain text report files under plugins/LaunchGuard/reports/
- /launchguard history
- /launchguard history latest
- launchguard.history permission
- Report retention with settings.reportsToKeep
Startup Checks:
- LaunchGuard can run a preflight check automatically after server start
- Configurable with settings.runOnStartup and settings.startupDelayTicks
- Startup checks use the same configured checks as /launchguard run
Saved Reports:
- Reports can be saved as plain text files
- Manual reports and startup reports are supported
- Report files are stored under plugins/LaunchGuard/reports/
- Reports include timestamp, source, version, result, and pass/warn/fail counts
Report History:
- /launchguard history lists recent saved reports
- /launchguard history latest prints the latest saved report
- Large report output is truncated safely
Safety:
- LaunchGuard remains read-only
- LaunchGuard does not execute plugin commands
- LaunchGuard does not execute configured commands
- LaunchGuard does not install, download, enable, disable, or reload plugins
- LaunchGuard does not modify worlds, blocks, economy, permissions, whitelist, chunks, or players
- LaunchGuard does not send network requests
- Report retention deletes only .txt report files inside plugins/LaunchGuard/reports/
Compatibility:
- Tested on Paper 1.20.4
- Tested with Java 17
- Built with Java 17 target compatibility
- Use the Java version required by your Paper server version
Limitations:
- Startup checks use a configurable fixed delay
- Reports are plain text only
- Report history has no search or filter support
- Plugin inventory reports metadata, enabled state, and dependency visibility only
- LaunchGuard does not verify full plugin runtime behavior or plugin configuration 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:7GaDEC6B"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ImwvOaBz:7GaDEC6B"
}

