I have not yet been able to reproduce this bug but the only way I could recover from it was to break the safe from creative mode.

I crafted a Carpenter's Safe in 1.6.4 with Carpenter's Blocks 2.1.2. Then I put some items in it. Then I upgraded the capacity using a gold bar. I used the hammer to lock the safe and had no issues for several days, then today I noticed the safe's graphic had the door stuck in the open position, and that I couldn't access the contents of the safe. I received the "block is locked" error message. There have been no unclean server shutdowns and I'm the only one using the server, so I am not sure what may have gone wrong.

Will have fix in next release.

I've received the same issue on 1.7.10/3.3.8. Optifine crashed my game while I had a safe open, so I went, updated that, and came back to see the safe stuck open. I have cheats disabled in my world, so is there any way of fixing it?

I'll look into it, should have an answer within 24h.

That's unusual. I rewrote a lot of the safe code in the new dev version 3.2.5, so you might give that a shot. It's receiving very few bug reports now so I would consider it stable, but always exercise caution when updating versions regardless.

Tile entities exhibit strange bugs sometimes, but they're fairly rare.

I can confirm this in CB 2.0.8 (Tekkit 1.2.9e, MC 1.6.4). This same thing happened to one of the players on my server. As an admin, I can still "lock" and unlock" the safe using the hammer, but whenever I try to right-click it, I get the error "CONTROL: This block is locked," no matter what state it's in.

The block is still present, if there are any logs or data that I can provide to help troubleshoot the cause.

Unfortunately logs wouldn't identify the cause. The "owner" of the block must have gotten corrupted somehow, in which case only server ops can access or destroy the safe. I'm not certain why safes would do this unexpectedly, but I have improved the code in the recent 3.2.5 release. That's the best solution I can offer at this time.

Alright, thanks.
On Aug 4, 2014 9:38 PM, "Mineshopper" [email protected] wrote:

Unfortunately logs wouldn't identify the cause. The "owner" of the block
must have gotten corrupted somehow, in which case only server ops can
access or destroy the safe. I'm not certain why safes would do this
unexpectedly, but I have improved the code in the recent 3.2.5 release.
That's the best solution I can offer at this time.

—
Reply to this email directly or view it on GitHub
#81 (comment)
.

If this issue persists with the latest builds let me know and I will reopen this and look into it more closely. My only "what if" scenario is if the safe never closes before quitting a game, but I don't think that would have this type of effect.