Tags
Creators
Details
2.0.0
Compatibility
Changes
Note
This release contains a great number of changes in data storage. Thus, you would be well-advised to backup your data before installing: both the /plugins/BeautyQuests directory AND your database (if using one).
2.0.0 took a full year to be made (first commit is dated 2024/10/04). All this time is not for nothing: it laid the foundation for more flexibility in how the player data is handled, making global quests or party progress sharing possible! See the "code-wise changes" section below for more information.
Changelog
Scoreboards
- Fixed a timing issue where quests did not stay long enough in the scoreboard
- No longer showing scoreboards-related errors when version is incompatible
- Added quests pinning to scoreboard
- Use Shift+Left Click on a quest in the
/questsmenu to pin it to the scoreboard. - When quests are pinned, they will be the only ones shown in the scoreboard and it will cycle among them only, without showing the non-pinned quests.
- Use Shift+Left Click on a quest in the
- Added an
auto hidesetting for the scoreboards (disabled by default).- When enabled, the scoreboard will automatically hide itself after the set amount of seconds when no progress has been done to the quests shown on it.
Miscellaneous
- 1.21.6 to 1.21.10 support
- Dropped support for versions < 1.17 and Java < 17
- Removed WorldGuard 6 support (useless since the it only supports MC up to 1.12.2)
- Added a new
mythicmobs.count kill for pet owneroption to make kill made by MythicMobs pets count for their owners - Added a tooltip for "smelt items" stage to help users understand which items to put in the editor
- Added a "custom ordering index" quest option to customize the order the quests appear in the
/questsmenu - Added the
questsMenu.keep menu openconfig.yml option- This option, enabled by default, makes the
/questsmenu stay open after the player starts or cancels a quest
- This option, enabled by default, makes the
- Fixed mobs or blocks editing causing "Cannot find object with UUID" errors
- Updated FR, HU, RU, TH, VI, ZH translations
- Renamed the
--overrideRequirementsoption of/quests startto--force(and made it working) - Removed the
--idflag of the/quests createcommand, now the quest ID is simply an optional parameter - Suppressed particles load message from the console (now only found in the log file)
- Fixed integration with ZNPCs 5.2
- Made plugin no longer remapped on Paper
- Updated IT and RU translations
Code-wise
- Refactored everything about the way player data is stored, for cleaner code and higher flexibility
- This also means the YAML format and SQL schema have been updated
- "Player Accounts" are now known as "Questers"
- Questers are the basic actors in BeautyQuests
- They hold data about the quests they do, and can have additional data
- They can be of different types: Player (by default), Server (in the Expansion), and maybe new ones in the future
- New API is present to create various types of Questers
- New API is present to choose which Questers gain progress when a player does an action related to a stage (e.g. killing a mob)
Full Changelog: https://github.com/SkytAsul/BeautyQuests/compare/1.0.5...2.0.0
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:ZbvwkXKZ:f5ZnXadS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZbvwkXKZ:f5ZnXadS"
}

