Tags
Creators
Details
3.14.2
Compatibility
Changes
This update fixes an issue where the plugin would crash when attempting to modify quest progress files for offline players. This also fixes events for the ecobosses_killing task type not registering, and fixes errors thrown from the ShopGUIPlus task type.
Commit log since v3.14.1
8a0e5d3 - Add null check for shop and de-duplicate common code <LMBishop>
325b78f - Add @EventHandler annotation to BossKillEvent <LMBishop>
8017642 - Fix some moddata commands blocking the main thread <LMBishop>
01c1457 - Fix broken links in documentation <LMBishop>
3345d07 - Bump version number <LMBishop>
More information
- Documentation: https://quests.leonardobishop.com
- Report a bug: https://github.com/LMBishop/Quests/issues
- Contribute to Quests: https://github.com/LMBishop/Quests/pulls
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:iU5kx4FN:xH5KL1E8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iU5kx4FN:xH5KL1E8"
}

