Night Vision & Beacon Blocks
Night vision potion effect has a blink effect some seconds before the potion ends.
When using beacons blocks edited by worlds editors with the night vision effect, when the effect is active, it will blink forever.
It could be fixed by having an undefinite duration ( long and hidden ) as you are in the effect zone of the beacon block, then it will back to 8 seconds if you are out of any beacon effect zone for that power ( with that it will warn the player that he's out of the area ).
Created Issue:
Night Vision & Beacon Blocks
Night vision potion effect has a blink effect some seconds before the potion ends.
When using beacons blocks edited by worlds editors with the night vision effect, when the effect is active, it will blink forever.
It could be fixed by having an undefinite duration ( long and hidden ) as you are in the effect zone of the beacon block, then it will back to 8 seconds if you are out of any beacon effect zone for that power ( with that it will warn the player that he's out of the area ).
Linked Issues
is cloned by1
TRASH-5740
is cloned by
MC-40677
is cloned by
TRASH-5740
I have a video of this (not in 1.4.3, though):
http://www.youtube.com/watch?v=kP1VCxBPDwY
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Concern 13w05b and before.
Confirmed in 13w06a.
Confirmed in 13w10a
Because beacons cannot have night vision by default, I can infer you are using creative with MCEdit. If you are using creative, the I can infer that you have the control over command blocks. Use the /effect instead of beacons, set range to whatever u want, and put a hopper timer or something.
Beacons blocks don't need a redstone clock to reactivate a potion effect if removed by milk since command blocks with /effect does ...
I think that simply diferent way to obtain things that looks the same ... but they affect the player in diferent way ...
"When using beacons blocks edited by worlds editors with the night vision effect, when the effect is active, it will blink forever."
... Okay, this is a little out of hand at this point. If you don't want to encounter bugs, then DON'T try to get the game to do things it is not normally supposed to do. Simple as that. By editing the game or your world contents, you fully accept the fact that somewhere, something can go wrong.
@FireHunterX
Its not really "out of hand", as Minecraft is designed to give editable NBT tags for MCEdit and 3rd party programs to add features into the game that are supported. Its just a feature request to remove the blinking when it is used on a beacon. Or use /effect
I didn't mean this report is out of hand, but I meant that this is about the 14th time I've seen reports caused by editing stuff like this.
If Mojang didn't do it, then there is a very high chance of something to work incorrectly. So, by editing the world, you kind of agreed to accept any damages to the worlds you edit.
The whole point of the NBT format was that map makers and modders could more easily customize the Minecraft experience for their players. Many features intentionally added by Notch, Jeb, Dinnerbone, etc. can only be accessed via NBT editors, and, again, are intended to be used. In this case, this bug is a simple oversight that can be fixed simply (e.g. don't do the blink effect if the effect is set to ambient, as set by beacons and other sources).
Nicholas Braden ... You're absolutely right, Mojang created unused potion properties for that, why don't they use it ... ?
@Yoann most unused tags were created intentionally for mapmakers to use.
...and after several months, a random new mod comes and says
Invalid
This issue does not meet the guideline to report a bug, and can only be reproduced if 3rd party programs are used.