Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nested dimensional bag (Magiclysm) is not filling first even when set as highest priority with auto pickup settings. #57675

Closed
ryeookin opened this issue May 13, 2022 · 0 comments · Fixed by #57700

Comments

@ryeookin
Copy link

Describe the bug

I have a lesser dimensional bag within highvolume rucksack and regardless of the priorities I set on the dimensional bag, when I go to pickup items, I can't get it to take/place items first in the dimensional bag using the pocket auto pickup settings.

In case it's helpful:
officer_dirtbag said the problem was that it was a nested soft container.

Steps to reproduce

1)Get a high volume rucksack (or presumably any backpack) and put it on.
2) Insert a lesser dimensional bag (likely a greater one would work too) in the rucksack.
3) Set the pickup priorities for the nested dimensional bag to have a higher priority then its parent bag.
4) Test picking up items (that could fit into a dimensional bag).
5) You should see them in the rucksack, not in the dimensional bag.

Expected behavior

After you follow the steps above 1-5, the items should fill the dimensional bag first, before filling the root of the rucksack.

Screenshots

No response

Versions and configuration

-Windows 11
-Experimental 633bd56
-Tiles MSXOTTO
-English
-Mods:
"dda",
"no_npc_food",
"package_bionic_professions",
"magiclysm",
"Graphical_Overmap",
"Graphical_Overmap_Magiclysm",
"MagiclysmUDP",
"blazemod",
"stats_through_kills",
"StatsThroughSkills",
"No_Portal_Storms"

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant