Page MenuHomeFeedback Tracker

.50 version has can openers not working on canned goods.
Closed, ResolvedPublic


Can opener with a condition of badly damaged, damaged, worn, or pristine does not open all canned food. Periodically will open some, but in most cases when dragged over a canned good, will be highlighted in blue and will swap out, versus given the choice to open.


Legacy ID
Steps To Reproduce
  1. Player finds can opener and puts in any inventory slot.
  2. Player drags can opener in inventory to a canned good in inventory to open.
  3. Player confirms that instead of tan highlighted color and options to open, it is instead highlighted in blue and the only option presented to player to is swap inventory slots between canned good and can opener.
Additional Information

I played with a friend who was experiencing the same issues. Not sure if desyncing issue or not.

Event Timeline

Otto edited Steps To Reproduce. (Show Details)Oct 14 2014, 7:28 PM
Otto edited Additional Information. (Show Details)
Otto set Category to Inventory.
Otto set Reproducibility to Sometimes.
Otto set Severity to None.
Otto set Resolution to Fixed.
Otto set Legacy ID to 1084586868.May 8 2016, 8:18 PM
cabbage added a subscriber: cabbage.May 8 2016, 8:18 PM

Can (excuse the pun) confirm this with Pristine can-opener

Darcion added a subscriber: Darcion.May 8 2016, 8:18 PM

its already known by devs, because the system is under rewrite. Later you can open cans with all items but with greater loss.

andy added a comment.Oct 16 2014, 12:20 PM

Hello otto,
thank you for your report. Is this still an issue after yesterday Experimental update?

Otto added a subscriber: Otto.May 8 2016, 8:18 PM
Otto added a comment.Oct 16 2014, 7:55 PM


Sorry for the late response. I am not able to test the can opener on experimental right now, game keeps crashing for me after a few minutes of playing. Will try to test again once game is more stable (I know this is currently an issue with .50 crashing for players and being worked on).



andy added a comment.Nov 5 2014, 1:19 PM

we believe this has been fixed.
Please submit a new ticket if the issue persists.