by youngneil1 » Thu Nov 03, 2016 7:18 am
And even stranger, worked flawlessly in two more tests with released beta. Alright, maybe I assumed the bug exists in released beta too fast and mistook the red warning message for low rations for last ration's damage message(?).
Regardless, you face the bug anyway. Hmmmm,...
I could imagine that it might be related somehow to item and itemRef difference (struggled with separating those proprely in my coding for rations). For example containers (chests) seem to store some select properties of the items (untechnical) in them, inter alia I did place isRation there, too. Assuming you had at first isRation set to false when creating your own ration item, then placed it in the chest and later on chnaged isRation to true, the (container) chest might still have set isRation to false for this item instance.
Long story short: please try to delete the "old" rations placed (e.g. remove from containers), then make sure isRation is set to true in the blueprint for your rations and then place them again (e.g. in a container's list).
Keeping fingers crossed, but it is a bit a shot in the dark...