Yesterday I noticed that when we enable first start and then enable droptransfer to a chest, it works fine but as soon as you try to disable it, it shows that it has been disabled yet the droptransfer is still active (Drop goes to chests, /lwc mode droptransfer status - shows its active) we had to disable the droptransfer by unlocking the chest which would prove a false statement to the code and thus it would shut down.
Here are my logs: (GMT +5.5)
22:33:21] [Client thread/INFO]: [CHAT] Lock type: Private
[22:33:21] [Client thread/INFO]: [CHAT] Please left click your block to lock it.
[22:33:21] [Client thread/INFO]: [CHAT] Created the protection successfully.
[22:33:28] [Client thread/INFO]: [CHAT] Please select a chest before toggling drop transferring.
[22:33:45] [Client thread/INFO]: [CHAT] Please left click a registered chest to set it as your transfer target.
[22:33:45] [Client thread/INFO]: [CHAT] Successfully registered chest as drop transfer target.
[22:33:50] [Client thread/INFO]: [CHAT] Drop transferring is now on.
[22:33:50] [Client thread/INFO]: [CHAT] Any items dropped will be transferred to your chest.
[22:34:09] [Client thread/INFO]: [CHAT] Drop transferring is now off.
(Woudn't turn off so I had to unlock the chest).
[22:34:33] [Client thread/INFO]: [CHAT] Punch your protection to remove the lock
[22:34:34] [Client thread/INFO]: [CHAT] Removed lock on the Chest successfully.
[22:34:38] [Client thread/INFO]: [CHAT] The protection no longer exists!
[22:35:01] [Client thread/INFO]: [CHAT] You have not registered a drop transfer target.
