[MC-2248] Night Vision & Beacon Blocks Created: 04/Nov/12  Updated: 30/Apr/17  Resolved: 21/Jan/14

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.2, Minecraft 1.4.7, Snapshot 13w05b, Snapshot 13w06a, Snapshot 13w10a, Minecraft 1.5.1, Minecraft 1.6.2
Fix Version/s: None

Type: Bug
Reporter: Yoann Petremann Assignee: Unassigned
Resolution: Invalid Votes: 6
Labels: None

Issue Links:
Relates
relates to MC-6223 Night Vision Potions that are edited ... Resolved
CHK:
Confirmation Status: Confirmed

 Description   

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



 Comments   
Comment by Galaxy_2Alex [ 21/Jan/14 ]

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

Comment by Nicholas Braden [ 03/Apr/13 ]

@Yoann most unused tags were created intentionally for mapmakers to use.

Comment by Yoann Petremann [ 03/Apr/13 ]

Nicholas Braden ... You're absolutely right, Mojang created unused potion properties for that, why don't they use it ... ?

Comment by Nicholas Braden [ 02/Apr/13 ]

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

Comment by FireHunterX [ 01/Apr/13 ]

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.

Comment by Yichen Cao [ 27/Mar/13 ]

@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

Comment by FireHunterX [ 27/Mar/13 ]

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

Comment by Yoann Petremann [ 27/Mar/13 ]

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

Comment by Yichen Cao [ 27/Mar/13 ]

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.

Comment by Yoann Petremann [ 05/Mar/13 ]

Confirmed in 13w10a

Comment by Anon Ymus [ 09/Feb/13 ]

Confirmed in 13w06a.

Comment by Yoann Petremann [ 06/Feb/13 ]

Concern 13w05b and before.

Comment by Tails [ 05/Feb/13 ]

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.

Comment by Nicholas Braden [ 04/Nov/12 ]

I have a video of this (not in 1.4.3, though):
http://www.youtube.com/watch?v=kP1VCxBPDwY

Generated at Sun Jan 12 11:57:13 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.