It is breaking one of my maps though. I want to limit a players ability to see (distance wise) but light up he area around said player i.e. Holding a torch. It makes no sense that a torch could light up areas 160 m away. Instead, they are completely blinded. Bug still in 1.9
Possible fix:
Blindness has 256 levels, but only one effect. Why not allow blindness II create complete blindness and blindness I created normal blindness. Night vision + blindness 1 creates the lighted limited area. Blindness II under any circumstances is complete darkness.
Everybody wins.
Updated the description in an effort to make it more readable. (Deleted information about how it is not acting like the old system r^=r and assumed intentional results should be r^=r-1)
I don't mean to sound impatient, but I am currently working on a map and am stopped until this bug is fixed, either to the old system or the new system, or is going to be around for a while? Basically, where is this bug in the list of to-do, and how is it planned be fixed?
Just making sure, making an adventure map and I don't want the same issue to occur to those who use it... Thanks for the help!
So basically, this only effects those of us with outdated machines?
I saw that bug. This is different. This creates complete whiteness. Also, this does not occur on a Windows 7 machine. The desired effect of the forced limited vision of the blindness but having the brightness of night vision works.
If nothing else, why the inconstancy, and/or how do I get the blank whiteness to be either complete darkness, as MC 10480 says is intended, or get the same result that the Windows 7 machine has?
However, the new r=2 is picking up entities further than 1 block away.
Oops. Typed it right in Minecraft. Guess I was too hasty here.
It appears that this bug has been fixed in Minecraft 1.9.4. The radius selector finds all entities at a radius of <r. It works almost as it did before the change; I don't know if this is intended or not.