1.3.0-BETA
Compatibility
Required content
Changes
[1.3.0] — 2026-04-17 — "Flow Update"
Complete UX overhaul: every menu now uses a hub-to-sub-page multi-step flow (like the reward wizard). No more cramming dailies + weeklies + controls + elite into one chaotic chest. Also adds the in-game GUI Layout Editor.
Changed — Player /quests flow
- New QuestsHubGui — clean 3-row hub with four tiles:
- Daily Quests — shows progress (2/3 completed), reset timer. Click opens DailyQuestsGui.
- Weekly Quests — same, opens WeeklyQuestsGui.
- Your Stats — streak, total, stars. Opens StatsGui.
- Claim All — only visible when rewards are ready.
- Admin shortcut for admins.
- DailyQuestsGui — dedicated 3-row page showing ONLY dailies, dynamically centered. Timer + back button.
- WeeklyQuestsGui — regular weeklies centered on row 1, elite quest highlighted on row 0 center. Timer + back button.
- /quests now opens QuestsHubGui instead of the old monolithic GUI.
Changed — Config Editor flow
- ConfigEditorGui is now a 3-row hub with four category tiles:
- Reroll Prices → dedicated ConfigRerollGui
- Pool Weights → dedicated ConfigWeightsGui
- Toggles (claim mode, progress bar, streaks) → ConfigTogglesGui
- GUI Layout → ConfigGuiLayoutGui (NEW)
- Each sub-page has focused controls, Save button, and Back.
Added — In-Game GUI Layout Editor
- ConfigGuiLayoutGui — visual 6-row editor showing the full 54-slot grid. Each slot displays its current role as a labeled item (lime glass = daily quest, light blue = weekly, yellow = elite, sign = label, button = stone button, black glass = border).
- Click any slot to cycle through all available roles.
- Reset to Default restores the stock layout.
- Save writes directly to gui/player_main.conf and auto-reloads.
- Admins can now rearrange the player quest GUI entirely in-game.
Internal
- New files: QuestsHubGui, DailyQuestsGui, WeeklyQuestsGui, ConfigRerollGui, ConfigWeightsGui, ConfigTogglesGui, ConfigGuiLayoutGui.
- All back-buttons route to the correct hub.
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:2NMDmTRl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4ShL0DGz:2NMDmTRl"
}
