Links
Tags
Creators
Details
0.5.0
Compatibility
Changes
LaunchGuard v0.5.0
LaunchGuard v0.5.0 adds local JSON and HTML exports, plus configuration validation for LaunchGuard config files.
This release includes the export work developed after v0.3.0. There was no separate public v0.4.0 release.
Added
/launchguard export json/launchguard export html/launchguard validatelaunchguard.exportpermissionlaunchguard.validatepermission- JSON report files under
plugins/LaunchGuard/exports/ - Self-contained HTML report files under
plugins/LaunchGuard/exports/ - Export retention with
settings.exportsToKeep - Versioned JSON export schema with
schemaVersion: 1 - Configuration validation for
config.yml,checks.yml, andmessages.yml
JSON Export
Use:
/launchguard export json
JSON exports are saved under:
plugins/LaunchGuard/exports/
JSON exports include report metadata, server information, summary counts, result status, and individual check results.
HTML Export
Use:
/launchguard export html
HTML exports are saved under:
plugins/LaunchGuard/exports/
HTML reports are self-contained local files. They do not load external CSS, JavaScript, fonts, images, or CDN resources.
Configuration Validation
Use:
/launchguard validate
Validation checks:
config.ymlchecks.ymlmessages.yml
It can report YAML parse errors, invalid types, missing sections, unknown keys, duplicate entries, empty values, and common configuration mistakes.
Validation does not modify files and does not reload configuration automatically.
Safety
LaunchGuard remains read-only.
It does not:
- Execute plugin commands
- Execute configured commands
- Install plugins
- Download plugins
- Enable or disable plugins
- Reload plugins
- Teleport players
- Modify blocks
- Modify worlds
- Modify economy data
- Modify permission data
- Change whitelist state
- Send network requests
- Upload data
- Force-load chunks
Exports are written only under plugins/LaunchGuard/exports/.
Export retention deletes only .json and .html files inside the exports directory.
Validation reads LaunchGuard configuration files but does not modify them.
Compatibility
- Tested on Paper 1.20.4 with Java 17
- Tested on Paper 1.20.6 with Java 21
- Tested on Paper 1.21.1 with Java 21
- Tested on Paper 1.21.8 with Java 21
- Built with Java 17 target compatibility
- Use the Java version required by your Paper server version
Limitations
- Export is manual only.
- Validation does not perform cross-file validation.
- Validation does not check actual plugin runtime behavior.
- Validation does not replace
/launchguard run. - Message key validation uses a static expected-key list.
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:GYK7tR0Q"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ImwvOaBz:GYK7tR0Q"
}

