I'll post my idea that I mailed to
@JamieSinn in-game.
Why not rework how cookpots work? I've done a bit of java scripting in the past, so with the limited knowledge that I have of java, I believe this should work.
Instead of having the cookpot constantly checking the contents of the chest, and the blocks that the sign is on and all that... Simply make a cookpot a chest and a sign. Nothing more. Slap a sign on a chest with [cook] on the 2nd line, and you have a cookpot.
This new style of cookpot would also behave differently. Instead of doing constant checks on the contents of the chest, it will ONLY check when the chest is opened.
The chest is opened, changing the state of the chest (the trigger).
30 second delay.
The sign checks if there are any smeltable items in the chest.
If yes, the sign checks if there is fuel in the sign.
If yes, begin cooking.
Like this, there should be minimal lag caused by cookpots, as a cookpot not in use causes as much lag as a normal chest and sign. Obviously, there would have to be a lock-out script during the 30 second delay to prevent someone from spamming a cookpot to cause lag.
I'm very curious as to how feasible something like this is, so feedback from those who have more experience with java, and minecraft plugins.
Click to expand...