[SPIGOT-1310] Burning furnace not working Created: 26/Nov/15  Updated: 11/Dec/17  Resolved: 06/Dec/15

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

Type: Bug Priority: Minor
Reporter: manuelgu Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: 1.8, 1.8.8, bug, spigot


 Description   

When you get yourself a LIT_FURNACE and place it down, it will automatically turn into a FURNACE. This only happens with Spigot and is not the case in Vanilla.



 Comments   
Comment by manuelgu [ 04/Aug/16 ]

@Zbob750 You are unable to get the item into your inventory in recent minecraft versions anway. It is still the case that `/setblock ~ ~ ~ lit_furnace` places a burning furnace at the location which also does not turn into a normal furnace when there are block updates around it in normal vanilla environment. Spigot however turns them directly into a normal furnace .

Comment by Z750 [ 10/Dec/15 ]

lit_furnace is a technical block. It isn't something you're ever meant to have in your inventory. The reason it switches to a normal furnace is because placing it is triggering a block update, at which point it realizes that it's not actually cooking anything and switches back to a normal furnace.

You can workaround this by disabling block updates on blocks you place (I think WorldEdit can do this) but it is just that, a work around. Eventually it will switch back to the correct furnace block, just as it eventually will on a vanilla server.

Comment by manuelgu [ 06/Dec/15 ]

How can it be a bug, when the block is actually called `lit_furnace`? It is intended to have a burning furnace then. I see absolutly no point in disabling that.

Comment by md_5 [ 06/Dec/15 ]
  1. You can't actually get a burning furnace legitimately
  2. If a furnace is empty then logically it should stop burning. The fact that in Vanilla this doesn't happen due to a block update is arguably a bug.
Comment by manuelgu [ 27/Nov/15 ]

I don't see a "won't fix" for 1115. I assume that it got closed by accident without really looking at the issue.

Comment by Black Hole [ 27/Nov/15 ]

It's clearly a duplicate of the first one. I agree that 1114 and 1115 don't refer to the same issue, so I used the term "marked".

Anyway 1115 is closed with "won't fix".

Comment by manuelgu [ 27/Nov/15 ]

If you read those other two reports you would see that it's not a duplicate. 1114 describes something else than 1115 and 1115 has been closed because somebody didnt read properly. That is why I created a new bug report.

Comment by Black Hole [ 27/Nov/15 ]

Duplicate of SPIGOT-1115 (which is marked as a duplicate of SPIGOT-1114)

Comment by SpigotMC [ 26/Nov/15 ]

Your build is not the latest and therefore may be the reason you are having this issue. Spigot is 1 version(s) behind. CraftBukkit is 0 version(s) behind. This message was automatically generated and is not guaranteed to be a solution to your issue.

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