You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on a mod pack that has multiple difficulty levels that have slightly different progression and some different recipes and processing paths.
We want to have different quests for the different difficulty levels, but 80-90% of the quests are the same between the different difficulties. We'd like to have all the quests be in the same quest book, but only show the quests for the current difficulty (and only consider those quests when determining completion and dependencies.
Describe the solution you'd like
I'd like a way to specify a mode for the pack to be in (in our case, the mode would be difficulty[1]). Then, there would be a way to annotate quests (or chapters) with which mode they are in (which could be one, some or all).
Only quests for the current mode would be visible.
Quests would only consider dependencies in the current mode for things like availability and visibility.
Chapters would complete once all quests for the current mode in it are complete (i.e. ignoring quests from other modes).
Some things that might be nice to have:
Ability to only show quests for one mode while editing.
There will likely be re-use of space in different modes, so being able to visualize each individually would be useful.
(This is probably the most important of the nice-to-haves).
The ability to switch modes of a world.
For the pack I am working on, this involves restarting the minecraft instance, as there are differences in configuration of other mods.
I'm not sure what the behavior here should be, other than it shouldn't break the world, and quest completion for quests that are in both modes should be preserved.
The ability to link equivalent quests between different modes.
For example, if there are different ways to get a resource, there might be different quest text and different tasks and rewards, but when switching modes, we might want completion to carry over.
[1] Note this does not correspond to minecraft difficulty, as our pack is meant to be played in peaceful (and is locked to that at higher difficulties).
Describe alternatives you've considered
This is currently implemented by having a hidden chapter with quests corresponding to the different modes (or combination of modes). Quests that should only be in one mode depend on the quest for that mode and are marked as optional and only visible when the dependencies are completed. We also have a couple of chapters that we replace wholesale (at the file level).
This has a number of rough edges though:
Most quests are always visible, but quests that are only in one mode are only visible after completing their dependencies.
Mod
FTB Quests
Description
I am working on a mod pack that has multiple difficulty levels that have slightly different progression and some different recipes and processing paths.
We want to have different quests for the different difficulty levels, but 80-90% of the quests are the same between the different difficulties. We'd like to have all the quests be in the same quest book, but only show the quests for the current difficulty (and only consider those quests when determining completion and dependencies.
Describe the solution you'd like
I'd like a way to specify a mode for the pack to be in (in our case, the mode would be difficulty[1]). Then, there would be a way to annotate quests (or chapters) with which mode they are in (which could be one, some or all).
Some things that might be nice to have:
[1] Note this does not correspond to minecraft difficulty, as our pack is meant to be played in peaceful (and is locked to that at higher difficulties).
Describe alternatives you've considered
This is currently implemented by having a hidden chapter with quests corresponding to the different modes (or combination of modes). Quests that should only be in one mode depend on the quest for that mode and are marked as optional and only visible when the dependencies are completed. We also have a couple of chapters that we replace wholesale (at the file level).
This has a number of rough edges though:
You can see the pack here.
The text was updated successfully, but these errors were encountered: