FTB Quests: the quest says 100%, or the task refuses what you have

If it still has not ticked: the three mechanisms

These are read from FTB Quests' own source at a tag matching the shipped jar, so they are as solid as anything on this page. What they are not is evidence about you: no reporter in the collected corpus is recorded hitting any of them. They are here because they are true and checkable, not because they are common.

Where the game looks for your item

The scan reads your 36 main-inventory and hotbar slots, and nothing else. PlayerInventorySummary.build walks player.getInventory().items and stops there. So the following do not count, and none of them produces any message:

• Armour you are wearing. The listener skips armour slots deliberately, and the reason is written in the code: armour slots can hold items whose data changes constantly, especially powered modded armour, which would trigger a great many pointless scans.

• Your offhand.

• A Curios slot.

• The inside of a backpack — and this one is worth understanding, because the usual guess about why is wrong. A Sophisticated Backpack sitting in your inventory is one of those 36 stacks, and its contents are stored as data on that one stack rather than as separate stacks. Nothing walks inside it. So it is not that backpacks are excluded by a list somewhere; there is simply nothing there to find.

• An ME network or any other storage.

So the fix is literal: the items have to physically occupy main-inventory or hotbar slots. Empty the bag out, take the armour off, move it out of the offhand.

The three-second wait, and why crafting does not tick it

Nothing polls an item task on a timer. It is checked when something happens, and in this pack the most obvious trigger is the one that does not work.

Crafting the item does not complete the quest at the moment you craft it. In this pack it cannot. When a crafted item is handed to the detector, it checks a different, smaller list of tasks — the ones flagged as completable only from crafting. All the Mods 10 sets that flag on no task in the whole book, so that list is empty. The crafting and smelting events fire, find nothing to check, and do nothing.

What actually completes the task is the separate inventory-change path, and that one is deliberately delayed:

• About three seconds. The pack sets detection_delay to 60 ticks, and 60 ticks is three seconds. FTB Quests' own description of the setting says a longer delay means longer waits for quest auto-completion messages.

• It is measured in real time, not ticks. On a server that is struggling the wait is still about three real seconds, plus however long the server takes to reach its next tick.

• It starts from the first inventory change, and further changes do not push it back. So three seconds is the worst case, not a moving target, and a machine dumping items into your inventory cannot keep the check away for ever.

The player-facing version of all that: take the item out of the crafting grid, then wait about three seconds. Two things trigger the check sooner: opening any container other than your own inventory does it immediately, and logging out and back in re-checks every item task in this pack, because login re-checks any task that does not consume its items and no task here consumes anything.

Tasks that are not about items

These are polled on a timer rather than triggered by an event, so the fix is usually to give them a moment while you are in the right place.

• kill, 213 of them — completes on the kill itself.

• structure, 81 — checked once a second (every 20 ticks) while you are inside a piece of the structure.

• biome, 54 — checked once a second (every 20 ticks).

• advancement, 54 — checked four times a second (every 5 ticks).

• dimension, 28 — on changing dimension, and polled.

• observation, 16 — look at the target for a set time.

The login trap, and it is deliberate. Biome and structure tasks are the two that are not re-checked when you log in, and FTB Quests' code says why it skips them. So logging in while standing inside the right structure, and then standing still, can leave the task sitting there. Walking one block is enough — that is all the poll needs.

Structure tasks care about structure pieces, not the area. You have to be inside part of the structure itself, not merely in the region the map marks.

A kill task completes on the kill, and that is all the code says about it. When a kill does not register, the evidence points at what the task will actually accept rather than at anything here.

Sources: FTB Quests 2101.1.36 util/PlayerInventorySummary.java, util/FTBQuestsInventoryListener.java, FTBQuestsEventHandler.java, its deferred-detection helper and the task classes with their poll intervals, all read at tag v2101.1.36; All the Mods 10 8.2 config/ftbquests/quests/data.snbt and its 66 chapter files; the jar sweep across the pack's server files.

↑ Back to the steps

The 190 tasks only your own click will finish

This book contains 190 checkmark tasks, and nothing in the game completes one. A checkmark task is done when the player clicks it, and a quest with a checkmark among its tasks will sit unfinished for as long as you wait for it.

If a task has no stated requirement you can act on, look at whether it is simply asking you to tick it.

Sources: All the Mods 10 8.2's 66 chapter files, counted by task type; FTB Quests 2101.1.36 task definitions.

↑ Back to the steps

When the quest is locked rather than broken

A task that refuses to make any progress may be one of the six quests in this book that will not start until its dependency is done. It is a short list, so you can check it in a minute.

• Every chapter in this book is flexible, so a chapter never locks you out. Thirty-five chapters declare it and the other thirty-one inherit it from the file's own default. In a flexible chapter you can always make progress on a quest whose prerequisite is unfinished; you just cannot complete it until the prerequisite is done.

• Six individual quests are linear — two in Extreme Reactors, three in Mekanism and one in Occultism. In those six, and only those six, a quest cannot be started at all until its dependency is complete, and the only thing the game tells you is:

Locked: uncompleted dependencies

• Doing the tasks in the wrong order is not a cause here. The setting that would require tasks to be done in sequence appears exactly once in the entire book, and it is switched off.

• Some tasks are marked optional — 22 of them — and an optional task does not hold its quest back.

Sources: All the Mods 10 8.2 config/ftbquests/quests/data.snbt (progression_mode), the chapter-level declarations across all 66 chapter files and the six quest-level ones in extreme_reactors.snbt, mekanism.snbt and occultism.snbt, parsed by indent depth rather than by searching for the word; FTB Quests 2101.1.36 for the locked message and its own description of flexible progression.

↑ Back to the steps

Quest text that is wrong or missing is a different problem

Two-thirds of this pack's quest reports are about wording rather than detection — a typo, a description that states something the game does not do, or a description that should have warned you and did not. If the quest is working and the text is wrong, nothing on this page applies and the fix is the pack's, not yours.

A missing or wrongly-translated quest title or description is a third thing again. The pack ships a third-party mod that splits the quest book's language files, and it was read in full: all ten of its classes, every mixin targeting the translation system, and no reference anywhere in it to tasks, to teams or to the inventory listener. It cannot affect whether a quest completes — but if your quest text is missing or in the wrong language, that mod is the first place to look.

Sources: FTB Quests Lang Splitter 1.0.7, read class by class; the coding of the pack's 2026 quest issues described in Unresolved.

↑ Back to the steps