QuestBridge

[2.0.1] - 2026-10-14

Added

• A one-time progress reset per world, for a pack that wants its existing worlds to start the quest book and the story again after an update. It is off by default. A pack switches it on with "progress_reset": { "id": "<id>" } in config/questbridge/settings.json (the flat spelling "progress_reset.id" works too). The id is 1 to 64 characters of letters, digits and _ - . : +, and blanks around it are ignored. An empty, null or absent id means off; an invalid value is a settings finding, logged as a warning at server start, and the feature stays off.
• A world whose stamp does not hold the id is reset once. A world with no progress at all (no QuestBridge story state and no FTB team with progress) is only stamped. Any other world is backed up first into <world>/questbridge/reset_backups/<id>_<yyyyMMdd-HHmmss>/ (the story state folders, questbridge/runtime_progress.json, the files of <world>/ftbquests/ and the old stamp, each under its path relative to the world). If the backup fails, nothing changes and nothing is stamped. Then all QuestBridge story state of every player, team and story is removed, the FTB Quests progress of every team is reset (task progress, started and completed, claimed rewards of all players, repeatable counts and cooldowns) and QuestBridge's own counts for bound FTB tasks are reset.
• The stamp <world>/questbridge/progress_reset.json is written last, so a failure before it leaves the world unstamped and the next start tries again with a new backup. The story part runs at server starting, before the story reads its state; the FTB part runs at server started, after FTB Quests has loaded. Without FTB Quests only the story part runs. A stamp file that cannot be read means nothing happens and an error is logged.
• Players: every player the world has saved or has story state for is listed as pending. At their next log-in their story items are taken back (stacks with a QuestBridge story marker and needles, from inventory, armour, off hand, cursor and ender chest; the quest-book marker items of the ftb_ kinds stay), they get one chat line (language key message.questbridge.progress_reset.done) and are taken off the list, and the fresh story state hands out the prologue leaf again as usual.
• The command /questbridge progress_reset (also /questbridge progress_reset status, permission level 2) shows the configured id, the world stamp, what this start did and up to 10 players still pending. No command triggers a reset. A new id in a later update resets once more; the same id never resets again.
• Not reset: old journal-site blocks, clearing terrain and lamps, placed ward lanterns and story lamps, story items inside chests, shulker boxes, bundles and frames or on the ground, FTB Teams parties, FTB per-player pins, config/questbridge/client_memory.json on clients, and questbridge/story/sign_reverts.json and questbridge/carried_lights.json (kept on purpose, they are what the mod still owes the world). See docs/wiki/Progress-Reset.md.