Closed Soyweiser closed 9 years ago
Yeah, fairly easy to fix, just a small JSON change.
Don't know if it is that easy. It should spoil if you remove it from the tin cans. But not if you keep it in the cans. Not sure how that works.
Really canned foods should have two different "states", one in which they are opened and will spoil, and the other where they aren't. The problem now is that since there is only one state we are either forced to assume that all times a particular food appears it never spoils (regardless of container type) or that all cans are open and will spoil eventually.
Basically, we need to make "can of X" work the same way as sealed plastic bags, jarred food, etc.
It's probably linked with #3596.
Basically, we need to make "can of X" work the same way as sealed plastic bags, jarred food, etc.
Pretty much.
I wouldn't object if someone were to make a "uncan" iuse and all that jazz, but the other thing I'd like to do is have a master iuse that handles transforming one item into another, and have the data for the transformation in the item definition. This would allow json only creation of canned and activatable items, and cut out a big chunk of redundant code from iuse.cpp The tricky bit is items with multiple actions and menus :/
Think we nailed this one.
Like terrible person said when I complained about it on IRC: