All versions
1.5.1
Release
CobblemonQuests 1.5.16 months ago 13
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
[1.5.1] — 2026-04-18 — "Full Customization Update"
Everything in the player-facing GUI is now fully configurable from separate HOCON config files with detailed comments and examples. Default quest counts bumped to 7 dailies / 7 weeklies.
Added — GUI Config Files
gui/main_menu.conf— Customize every button in the main quest menu: item type, display name, lore text, glow. Supports placeholders like{daily_timer},{weekly_timer},{streak},{completed_today},{completed_week},{total_completed},{milestones_hit}. Configure quest display items (incomplete/complete dye) and progress bar toggle.gui/milestone_menu.conf— Customize the milestone GUI: title, background color, complete/incomplete items and name formats ({count}placeholder), back button. Also contains milestone reward thresholds with full reward type documentation and command examples.gui/leaderboard_menu.conf— Customize leaderboard colors (top-3, own rank, others), player entry lore ({quests_completed}), book button ({rank},{total_completed}), back button.rewards/streaks.conf— Separate streak reward config with command reward examples.- All config files include extensive comments explaining every option, supported placeholders, MiniMessage formatting, glass color reference, and reward type documentation with examples.
Added — Command Rewards for Milestones & Streaks
- Default milestone/streak rewards now use
commandtype with example:{ type = "command", command = "padmin givekey {player} 1 Rare Crate" } - All reward types documented in config:
command,stars,pokedollars,item,crate_key. - GUI configs override
config.confmilestones/streaks when present.
Changed — Quest Count Defaults
daily-quest-countdefault changed from 3 to 7.weekly-quest-countdefault changed from 3 to 7.- Note: existing
config.conffiles are not overwritten — delete and reload to regenerate with new defaults, or edit manually.
Changed — Config Architecture
- GUI customization split into dedicated files under
gui/folder. - Streak rewards split into
rewards/streaks.conf. config.confremains for schedule, pools, reroll, security settings.- Milestone/streak sections in
config.confact as fallback when the dedicated files are not present.
Changed — 100% Configurable Player GUIs
- Every single player-facing text string is now editable from config.
- Quest item lore — type tags (
[Elite],[Weekly],[Hidden]), status tags (★ READY ★,✔), progress format, claim messages, bonus section, rewards header/lines, click hint — all inmain_menu.confunderquest-text { }. - Quest Detail GUI — title, background, claim buttons (item/name/lore),
claimed displays, reroll button with cost format strings — all in
gui/detail_menu.conf. - Stats GUI — title, background, streak/milestone/stars items with
full lore and placeholder support — all in
gui/stats_menu.conf. - Milestone item lore — progress line, rewards header, reward line
format, completed text — all in
milestone_menu.conf. - Leaderboard name format —
{color}#{rank} {name}{end_color}inleaderboard_menu.conf.
Internal
GuiConfigexpanded withQuestText,DetailMenu,StatsMenuinner classes (total: 6 configurable menu sections).GuiConfigLoaderloads from 5 HOCON files:main_menu.conf,milestone_menu.conf,leaderboard_menu.conf,detail_menu.conf,stats_menu.conf.- All 5 player GUIs (
QuestsHubGui,QuestDetailGui,MilestoneGui,LeaderboardGui,StatsGui) read every text string fromGuiConfig. - Zero hardcoded player-facing strings remain in GUI code.
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:4ShL0DGz:pjkrAq33"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4ShL0DGz:pjkrAq33"
}
