[GUIDE] How the priority system works #17
Locked
Lailloken
announced in
Announcements
Replies: 3 comments
|
sounds amazing :) |
0 replies
|
Thanks for your hard work! |
0 replies
|
you're my guy <3 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
WIP, a few details need to be updated to reflect the current state (v1.20.0)
General idea
The idea behind the prio-list is to set up a set of four archnemesis mods that you want to run "fully juiced," i.e. those big wombo-combos that you see on Reddit and such. The tool would then suggest a fast route to completing this list but would also suggest non-prioritized recipes and mods in case none of the prioritized recipes are ready.
Mechanics
The tool generally tries to suggest the shortest path to completing this prio-set, i.e. it will not suggest completing a sub-recipe if you have already reached the required number of that mod. As an example:
The order in which recipes are added to the list also has an effect on how the tool makes suggestions. The first item on the list has its chain checked for available sub-components first, then the second, etc. This is also why recipes that have at least one assembled version present in the inventory are put at the end of the list automatically.
Bottlenecking
Being set up like this has its drawbacks, namely bottleneck-situations where there is a surplus in one branch and a dry-streak in another, which can lead to running out of inventory space. As a first step to counter this, I have implemented a panel that shows your surplus in mods connected to the priority list which can be used as a last resort to free up space.
All reactions