The main issue with ftb's reward tables is they interfere with ftbquests' loop when adding quest data, leading to quest data being lost.

FTB Quests loads a quest file in two passes.
Pass 1 - creates every chapter, quest, task and reward as a blank shell, stashes each one's real data in a cache.
Pass 2 - takes that list, counts the number of times it needs to run, and fills each shell with data from the cache. Sounds simple, right?

Problem: When the iterator (for-each loop) reaches reward tables, the table creates its rewards and adds them to the list already being iterated. The iterator's "budget" was locked in at a number, never updated, so it runs out with data still left in the cache from pass 1, untouched. The data is then lost when you save the quests.

It only triggers when a reward inside a reward table has no real ID (id: "0000000000000000") — that's what makes FTB Quests assign IDs and register them mid-loop.

FTB Quests	Minecraft	Affected
2001.4.x	1.20.1	No
2101.1.20 – 2101.1.28	1.21.1	Yes
2111.1.0 – 2111.1.5	1.21.11	Yes
26.1.2.1 – 26.1.2.2	26.1	Yes

FTB Quests Reset Patch