So I was working with writing a system to place redstone torches with the off state. Wasnt working, as soon as I placed them, they would light right back up. 

I know that is an issue in vanilla too.

So I decided to test with a furnace, furnace did the same thing. Yet, in vanilla (using a debug stick) you set a furnace's block state (lit) on and off, and it stays that way. 

To test:

I created a testing environment that consists of a fresh build of Spigot put on a fresh test server (no plugins, brand new world, default settings/config)

I also create a vanilla test server (Brand new world)

I created a little video to show you what is happening.

In the first part of the video, I hopped onto my new Spigot server, placed a furnace, gave myself a debug stick, clicked it, and it lit for about 1 tick and immediately it turned off again.

In the second part of the video, I hopped onto my vanilla server and repeated the same steps, place furnace, hit with debug stick. The difference is on the vanilla server the furnace stayed lit. I could then turn it off and on again. 

VIDEO: https://youtu.be/QXbLZVda0cQ

The main reason I came across this, was because I couldn't "turn off" a Redstone torch. Now I KNOW that on a vanilla server with a debug stick you cant do this either, it also relights, which is a total bummer.

MAYBE JUST MAYBE if/when this furnace/block state issue gets fixed, would it be possible to override the Redstone torch system to force a block state to stay unlit? I know I can do this with block state update event, but I was hoping this could be something fixed on server side?!?!