Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 4 months ago
Updated last week
All versions
neoforge-26.2-0.4.0
Release
JustQuests neoforge-26.2-0.4.0last week 16
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Singleplayer only
Changes
Added
- Team quests: a quest with
"team": truebelongs to a whole team - any member takes it, everyone's actions count, the quest book and tracker show the shared progress, and when it is done every member gets the rewards like for their own quests (members who were offline when they come back). A team is made with/quest team create <name>(theninvite,accept,leave,kick,info; up to 8 players), or a player's scoreboard team (/team) counts. Mod and plugin alike; a world moving to the plugin brings its teams along. - Server plugin for Spigot, Paper and Purpur (1.19 – 1.21.11 and 26.1 – 26.3, on the plain
Spigot API; one jar each for 1.19 – 1.20.6, 1.21 – 1.21.11 and 26.1 – 26.3): players join with a
vanilla client. The quest book is a chest menu (opened with the
quest book item new players get, or
/quest,/quests,/jq), the quest tracker a boss bar. It reads the same quests as the mod (built-in, datapacks,custom-quests.json, one file per quest inplugins/JustQuests/quests/), has all objective and reward types, claiming, reward choices, the commands and permission nodes, and the five languages; item, block and mob names are translated by each player's game. A world played with the mod keeps its progress, custom quests and generated board when it moves to a plugin server. - The server generator (plugin): the board of generated quests grows with the players of the last 7 days; every player gets personal daily quests; harder weekly quests for everyone; a weekly server goal everyone works on together, with the same reward for every helper; and better rewards: a choice of three, a lucky bonus, a streak bonus for personal quests, loot on weekly quests and goals, a reward multiplier, and money through an economy plugin's command.
- Plugin extras: announcements for a new board, new weekly quests and a new server goal, with
harmless fireworks when the goal is reached; quest givers (
/quest npc set [name]: the mob, villager or armor stand you look at opens the quest book); and PlaceholderAPI placeholders (%justquests_completed%,%justquests_tracked%,%justquests_goal_percent%and more). - Minecraft 26.1 – 26.3: Fabric builds for 26.1, 26.1.1, 26.1.2, 26.2 and 26.3, and NeoForge builds for 26.1.2 and 26.2 (NeoForge 26.3 follows once it leaves beta). JustQuests now has 43 builds. Minecraft 26.x needs Java 25.
- Claim button: a finished quest now waits with its rewards until you claim them, with the
Claim button in the quest book, the
[Claim rewards]button in chat, or/quest claim <id>(/quest claimalone takes every waiting reward). The quest book shows these quests on top under "Rewards ready", the HUD reminds you of them, and/quest progressand/quest listmark them too. On Minecraft 1.18–1.19 (no quest book) the chat button and the command do it. Server owners who prefer the old way set"claimRewards": falseinsettings.json; then rewards arrive the moment a quest is finished, as before. A finished generated quest stays until its rewards are claimed, also when the generator puts up a new set in the meantime. - Choice rewards (
justquests:choice): a quest can offer several rewards of which the player picks one when claiming: in the quest book by clicking an option, in chat with the[1][2]buttons, or with/quest claim <id> <number>. Quests with a choice always wait to be claimed. The example datapack hasex_choice. - HUD position button in the quest book's title bar: each click moves the tracker to the next corner (clockwise). While you point at the button, the book shows the tracker in its corner.
- Permissions (LuckPerms & co.): every command has a node,
justquests.command.<name>for the player commands (everyone by default) andjustquests.admin.<name>for the operator commands (operators by default). Quests can name apermission; players without it don't see the quest. NeoForge and Forge use their permission API, the Fabric builds bundle fabric-permissions-api. - Six more mods for the quest generator: Applied Energistics 2, Immersive Engineering, Biomes O' Plenty, Alex's Mobs, Tinkers' Construct and Ars Nouveau. Botania, Mekanism and the Twilight Forest got more quests (more flowers and gear, metal blocks and steel machines, more wood, beetles and meef). Every new target was checked against the mods' released jars.
settings.jsongets new options added by itself, so owners see them without deleting the file.- Generated quests in five languages: quests from the generator now have their title, description and reward message in English, German, French, Spanish and Japanese, and each player reads their own game language. Item, block and mob names use the official translations of Minecraft and of the supported mods. The built-in quests got Japanese as well.
Changed
- Every text is translatable: the quest book, the HUD, goal and reward names, and all chat
messages of the commands now come from language files (
assets/justquests/lang/), with English, German, French, Spanish and Japanese included. Each player sees their own game language, also on Minecraft 1.18–1.20.1. On 1.19.4 and newer, players without the mod see the English text. - The German, French and Spanish texts of the built-in quests have proper accents and use the game's own names (for example the "Acquire Hardware" advancement).
- Loot rewards read "Loot: simple dungeon" instead of the full loot table id; tag goals read "any logs"; dimension goals name the vanilla dimensions ("Visit the Nether").
- The Discord welcome no longer talks about voting on the v0.2 GUI.
Fixed
- NeoForge 1.20.4: the mod did not load at all. Its jar only had the newer
neoforge.mods.toml, which NeoForge 20.4 does not read, and it needed Java 21. It now hasmods.tomland runs on Java 17 like Minecraft 1.20.4. /quest generator statusnamed the wrong Minecraft version on 1.21.11 and 26.x.
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:dHVehhni:xisAHIwF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dHVehhni:xisAHIwF"
}

