[SPIGOT-4493] Block State update issue (furnace) Created: 20/Nov/18  Updated: 22/Dec/18  Resolved: 22/Dec/18

Status: Resolved
Project: Spigot
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Shane Bee Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: BlockState, Furnace
Environment:

MacOS 10.14

Java: 

java version "1.8.0_191"

Java(TM) SE Runtime Environment (build 1.8.0_191-b12)

Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode)

Version: This server is running CraftBukkit version git-Spigot-9b4b0a2-e4183e7 (MC: 1.13.2) (Implementing API version 1.13.2-R0.1-SNAPSHOT)
Plugin: None used
Guidelines Read: Yes

 Description   

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?!?!

 Comments   
Comment by Shane Bee [ 20/Nov/18 ]

Okay duly noted.
And thank you
I will see if I can figure another way around it. My main goal was with the torches (redstone) anyways, I just noticed it when tested the furnaces, so figured I should report it!

Comment by md_5 [ 20/Nov/18 ]

Not really, it would have to be stored as part of the map etc
I will review the furnace change though.

Comment by Shane Bee [ 20/Nov/18 ]

Ohhhh, okay I didn't know that was something done on purpose.
That is odd someone would want that change.

Is it possible to add a method that maybe stops the block update for a certain block?
Im not sure if thats even possible, just thinking of ideas

Comment by md_5 [ 20/Nov/18 ]

You're basically asking us to undo what the user in SPIGOT-844 wanted

Generated at Sat Dec 13 15:18:11 UTC 2025 using Jira 10.3.13#10030013-sha1:56dd970ae30ebfeda3a697d25be1f6388b68a422.