One subtle thing that would bring a little more convenience to structuring entry relations. It may go something like this: in the .json file of the entry optional parameter can be defined, specifying "parent" entry for this one. The entry itself will then only be unlocked if parent entry is unlocked. It may not have it's own advancement requirement, in which case it will be unlocked instantly along with it's parent; or it may have it's own independent advancement lock, in which case it will require both parent entry to be unlocked, and it's own advancement requirement to be obtained before showing up.

Furthermore, parents would be able to have their own parents, and parents of parents can have their own, and parents of parents of pare... I guess you got it. That would allow more complex dependency structuring if required.

For developers there actually are better ways to implement functionality with similar effect, of course. But having such system would expand possibilities of modpack makers, and spare mod developers the burden of having to mess around with custom triggers.

This issue is stale because it has been open for a while with no activity. Please bump if this is still an issue, or this ticket will be closed soon.