Campfire smoke stops being produced 64 blocks away
The Bug
A campfire will stop producing smoke once the player is more than 64 blocks away from it. Adding a ticking area around the campfire changes nothing. The smoke produced prior to reaching that distance is still visible at any distance however
Steps to reproduce
- Place a campfire (preferably with a hay bale under it)
- Move 64 blocks away from it in any axis (including the Y-axis)
Linked Issues
is duplicated by6
- Unresolved
PC_Screen- 36
- 17
- Confirmed
- 224339
- Multiple
- Windows 10
1.17.40.20 Beta - 1.19.22 Hotfix
1.17.40.20 Beta 1.17.30.22 Beta 1.17.11 Hotfix 1.16.230.52 Beta 1.16.220 1.16.220.50 Beta 1.16.210.58 Beta 1.16.210.55 Beta 1.16.210.54 Beta 1.16.0.53 Beta 1.14.20 Hotfix 1.13.1 1.14.1 Hotfix 1.12.0.13 Beta 1.11.0.1 Beta 1.11.0.5 Beta 1.11.0.7 Beta 1.11.4 1.14.30 Hotfix 1.14.60 Hotfix 1.16.0 1.16.1 1.16.20 1.16.40 Hotfix 1.16.100 1.16.200 1.16.201 Hotfix 1.16.210 1.17.32 1.17.33 1.17.34 1.19.2 Hotfix 1.19.22 Hotfix
Created Issue:
Campfire smoke stops being produced 64 blocks away
The Bug
A campfire will stop producing smoke once the player is more than 64 blocks away from it. The smoke produced prior to that is still visible howeverSteps to reproduce
- Place a campfire (preferably with a hay bale under it)
- Move 64 blocks away from it in any axis)
The Bug
A campfire will stop producing smoke once the player is more than 64 blocks away from it.The smoke produced prior to that is still visible howeverSteps to reproduce
- Place a campfire (preferably with a hay bale under it)
- Move 64 blocks away from it in any axis)
The Bug
A campfire will stop producing smoke once the player is more than 64 blocks away from it. Adding a ticking area around the campfire changes nothing. The smoke produced prior to reaching that distance is still visible at any distance howeverSteps to reproduce
- Place a campfire (preferably with a hay bale under it)
- Move 64 blocks away from it in any axis (including the Y-axis)
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Thank you for your report!
We're actually already tracking this issue at MCPE-42512, so we will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature, to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Duplicate of MCPE-42512
Thank you for your report!
We're tracking this issue in MCPE-42512, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-42512, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-141737 and MCPE-42512, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Thank you for your report!
We're tracking this issue in MCPE-42512, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

You just moved out of the particle render distance.
Increase your particle render distance..
Does the smoke continue if the campfire is within a ticking radius, or if the particle render distance is increased?
Particle render distance is what affects the range of how far the smoke particles emitted from the campfire can be created. The max is 100, therefore, 64 blocks is the limit a player can be furthest away similar to Beacons. However, campfire particles can still be visible. I can't tell if this is a bug or supposed to be intentional.
The ticking radius is irrelevant to this issue, including ticking areas. The particles will stop being produced as soon as you are 64 blocks away from the campfire in any axis (including the y-axis). The smoke itself is visible at any distance. It's a different situation than the beacon ray, as that one stops being visible 64 blocks away
Actually @PC_Screen, the same does applies to beacons. After some testing, I've gathered a couple of frames when recording the beacon ray, and realized that it would disappear in parts from the down up much like a ray from an end portal gate disappears from the up down, and the opposite upside down. So if I'm not mistaken, this bug correlates to both of these reported issues. Where the particle will render, but stop producing from the block after a certain particle render distance. However, I have an idea on how they can fix this. Because I think that the smoke and the beacon ray is under the same category as a particle, instead have them become a unique object that will always render despite being far away from it. But make sure that it will stop rendering if it is out side of the chunk render distance.
I am playing on xbox one and also have experienced this.
It completely breaks one use of the campfire: You should be able to use it to find locations more easily and also if you are far away, but it is not possible.
comfirmed for 1.12, 1.12.1, 1.13, 1.13, 1.13.1, 1.14, 1.14.1, 1.14.20 and 1.14.30
Confirmed for 1.14.60
This bug breaks one use of the campfire: It should be able to be used to find the location where the campfire is from far away.
Confirmed for 1.16
This also affects soul campfires.
This needs to be fixed. One of the main purposes of the campfire is a smoke signal. I was puzzled why I could not find my base through the smoke the other day.
Also change platform to multiple. Happens on mobile too
On my Android, playing 1.16 on a server, campfires only produce smoke when I'm within a 32-block radius sphere around them.
A screenshot of it in java
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Is this still an issue in the latest version? If so, please add a comment or update the affected version field.
To make your bug report as effective as possible, please try and include the following steps to reproduce the problem:
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Still an issue
Affects 1.19.22
Smoke appears to stop being produced when the player is ~48 blocks away from the campfire.