Burning furnace not working

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Minor
    • None
    • Affects Version/s: None

      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.

          [SPIGOT-1310] Burning furnace not working

          manuelgu added a comment - - edited

          @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 .

          manuelgu added a comment - - edited @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 .

          Z750 added a comment -

          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.

          Z750 added a comment - 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.

          manuelgu added a comment -

          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.

          manuelgu added a comment - 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.

          md_5 added a comment -
          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.

          md_5 added a comment - You can't actually get a burning furnace legitimately 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.

          manuelgu added a comment -

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

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

          Black Hole added a comment -

          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".

          Black Hole added a comment - 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".

          manuelgu added a comment -

          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.

          manuelgu added a comment - 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.

          Black Hole added a comment -

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

          Black Hole added a comment - Duplicate of SPIGOT-1115 (which is marked as a duplicate of SPIGOT-1114 )

          SpigotMC added a comment -

          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.

          SpigotMC added a comment - 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.

            Assignee:
            Unassigned
            Reporter:
            manuelgu
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: