Quick question before I update: What’s going to happen to clothing and armor from mods that don’t have pocket_data defined? Is it going to throw up errors that prevent loading?
Assuming I’m going to have to add the pocket_data manually to keep my non-packaged mods working, what are the guidelines for it? How do you know when to use multiple “pocket_types” and how many to use? And are there any other pocket_types than “container” I should be aware of?
Sorry if these seem like stupid questions; I just don’t want anything breaking.
I wonder if containers with liquids are intended to show their contents in separate line instead of former amount-in-brackets system, or it is just a glitch? I mean, you currently can’t put 2 different liquids in a container… right?
Gotta agree. Right now you could use a SECOND inventory management system just to shift items around your worn containers. Also the items just being in a big list is - as everyone probably already knows - a step down.
But I’m sure that they’ll improve it so I’m not stressin.
just testing it on latest experimental with 40 minute session, and because this is new feature and experimental, i understand that this feature is still unstable and feel “barely cooked” with bugs and all.
but still, i love it. the way the nested container show items inside every individual container is absolute fresh and has great potential too.
this give me that sense of sorting, where i can choose which container will hold this newly picked up items, and sorting it like this bag only holds weapon and this bag only holds food.
all it needs right now is fixing, improving and perfecting. and overall best feature for the game.
Yeah it’s a big step. I rememer back in 2013 on the old forums people suggesting it and I remember Kevin saying that this will take a long time if it happens at all and now it’s 2020 already and we got nested containers.
Yup, i agree. It is no biggie.
It is called “experimental” for a reason.
Also, probably best to merge and have the general population that likes to live dangerously bugtest, than not.
So far, i think the messy UI and crazy “autoput” (e.g. of a knife into a canteen) are the most important issues with this.
Both are nontrivial to sort out i think (though autoput should be fixable using blacklist/whitelist flags -eg. rigid/nonrigid/liquid- and priority lists). Priority lists should ideally be player tweakable (eg. always prefer backpack if possible, etc.)
Just to clarify something, Korg was spending a very significant amount of time just dealing with merge conflicts in the final week or so when he was wrapping this up. If the plan was to wait until merging the feature would cause zero regressions, it literally never would have happened. Yes we knew there were bugs and that the UI wasn’t where it needs to be, but there are just too many moving parts here to complete everything and merge it all at once. Korg is very dedicated to wrapping this all up as soon as possible.