0.1.1
Compatibility
Changes
Changelog All notable changes to this project are documented in this file. The format is based on Keep a Changelog, and this project follows Semantic Versioning.
[0.1.1-BETA] - 2026-10-16 Fixed Quest creation: creating a quest from the admin menu saved its name and its internal code in the wrong columns, so the quest could not be stored correctly. Quest editing: editing a quest no longer wipes the progress of players who have it active. Objectives are now updated in place instead of being deleted and recreated. Existing databases: servers upgrading from an earlier version no longer fail on startup because of the missing task_code column. Changed Editing a quest now keeps player progress and applies the change: If an objective's required amount changes, progress is recalculated. A completed objective stops being completed if its amount increases, and an objective completes if its amount drops to or below the current progress. If an objective is added, players who have the quest active must complete it too (starting at 0). Players who already finished the quest are not affected. If an objective is removed, only its own progress is deleted. Players who are online and have the edited quest active see the changes immediately. The database schema is now created and migrated during startup, before commands and listeners are registered. If this step fails, the plugin disables itself and logs the error instead of running with an inconsistent database. Added Automatic database migration with a schema version stored in the database (PRAGMA user_version): A backup of the database is created in plugins/<plugin folder>/backups/ before migrating. If the backup fails, the migration is not performed. The migration runs in a single transaction and is rolled back on failure. Default quests that were seeded by earlier versions are linked to their internal code, in Spanish or English, so they are not duplicated and keep their dynamic translation. The migration runs only once; later startups skip it. Automated tests running against a real SQLite database, covering quest creation, the migration (including a copy of a real database) and quest editing with active player progress. Notes Back up your database before upgrading, even though the plugin makes its own copy. No configuration changes are required.
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:Uhe8RN30:IMxrcrtI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Uhe8RN30:IMxrcrtI"
}

