The "Glow and Behold!" advancement is granted when interacting with empty signs while holding glow ink sacs, despite no glow ink sacs being consumed
The Bug:
The "Glow and Behold!" advancement is granted when interacting with empty signs while holding glow ink sacs, despite no glow ink sacs being consumed.
Steps to Reproduce:
- Place down a sign with no text on it.
- Obtain a glow ink sac and switch to survival mode.
- Interact with the sign while holding the glow ink sac.
- Take note as to whether or not the "Glow and Behold!" advancement is granted when interacting with empty signs while holding glow ink sacs, despite no glow ink sacs being consumed.
Observed Behavior:
The "Glow and Behold!" advancement is granted despite no glow ink sac being consumed.
Expected Behavior:
The "Glow and Behold!" advancement would not be granted.
Linked Issues
is duplicated by3
Created Issue:
The "Glow and Behold!" advancement is granted when interacting with empty signs while holding glow ink sacs, despite no glow ink sacs being consumed
The Bug:
The "Glow and Behold!" advancement is granted when interacting with empty signs while holding glow ink sacs, despite no glow ink sacs being consumed.
Steps to Reproduce:
- Place down a sign with no text on it.
- Obtain a glow ink sac and switch to survival mode.
- Interact with the sign while holding the glow ink sac.
- Take note as to whether or not the "Glow and Behold!" advancement is granted when interacting with empty signs while holding glow ink sacs, despite no glow ink sacs being consumed.
Observed Behavior:
The "Glow and Behold!" advancement is granted despite no glow ink sac being consumed.
Expected Behavior:
The "Glow and Behold!" advancement would not be granted.
is duplicated by
is duplicated by
For clarity, this issue is not a duplicate of MC-226445. MC-226445 talks about how glow ink sacs can be used on empty signs. This ticket (MC-261965) talks about how the "Glow and Behold!" advancement is granted despite no glow ink sac being consumed when interacting with empty signs while holding glow ink sacs. I also believe that MC-261322 was incorrectly resolved, hence why I created this ticket (MC-261965) which (I hope) clearly highlights the problem.
Thank you for your report!
We're tracking this issue in MC-261965, 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
Duplicate of MC-261965.
Thank you for your report!
We're tracking this issue in MC-261965, 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 MC-261965, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Fixed. Please check the Fix Version/s field in that ticket to see in which version this behavior was or will be fixed.
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

For clarity, this issue is not a duplicate of
MC-226445.MC-226445talks about how glow ink sacs can be used on empty signs. This ticket (MC-261965) talks about how the "Glow and Behold!" advancement is granted despite no glow ink sac being consumed when interacting with empty signs while holding glow ink sacs. I also believe thatMC-261322was incorrectly resolved, hence why I created this ticket (MC-261965) which (I hope) clearly highlights the problem.