Tags
Creators
Details
0.2.5
Compatibility
Changes
LuaCord 0.2.5-BETA
Stability & Rebrand Update
Bug Fixes
- Fixed plugin loading so one broken
.lktplugin can no longer silently block every plugin listed after it from loading — each plugin now loads independently - Fixed a double-enable bug that could cause JAR-wrapped plugins to register their event listeners twice
- Fixed the JAR generator producing broken
plugin.ymlfiles when a plugin description contained a colon,#, quote, or line break
Changes
- Renamed the
/lukkitcommand to/luacordto match the project's actual name - Renamed permissions
lukkit.command/lukkit.runtoluacord.command/luacord.run - Connector template now declares
softdepend: [LuaCord]for reliable load ordering
Upgrade Notes
If you granted lukkit.command or lukkit.run explicitly on your server, you'll need to re-grant them as luacord.command / luacord.run — the old permission nodes no longer do anything.
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:pZ8ixbLD:a89IY3lA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pZ8ixbLD:a89IY3lA"
}

