mojira.dev
MC-11360

Toggling redstone-powerable light-emitting components from more than 10 chunks away doesn't update their light emission correctly

Update - I also created a bug demonstration video available here: http://www.youtube.com/watch?v=eQlSnJtLUNc

Steps to reproduce:

  1. Build a long redstone wire with repeaters far away from the spawn. ("long" = more than about 12 chunks; "far away" = teleport 1000 blocks away and you should be fine)

  2. Go to the beginning of the wire and power it (by placing a redstone torch in front of it).

  3. Follow the wire.

You'll notice something like in the screenshot "light-emission-bug.png": The light emission was correctly updated for all repeaters that have been located in loaded chunks when the wire got powered. (Like the right repeater in the screenshot.) It was not correctly updated for all repeaters further away. (Like the left repeater in the screenshot.)

This ticket relates to MC-1018. (Reason: If the lighting engine has to be rewritten anyway, this bug could be taken into consideration when designing the new version.)

Linked issues

Attachments

Comments 14

Daniel "Glampkoo"

Cannot reproduce.

The.Modificator

Here's a bug demonstration video: http://www.youtube.com/watch?v=eQlSnJtLUNc

No response in 4 months, assuming no longer an issue.

The.Modificator

Whoops - sorry. This bug still exists in 1.7.2.

Deleted account

Is this still a concern in the current Minecraft version 14w11b / Launcher version 1.3.11 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

4 more comments

Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w42a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time.

The.Modificator

Updated. Please reset ticket status.

[Mod] redstonehelper

Ticket was already resolved to MC-93132.

The.Modificator

Okay? Just curious: Why do newer ticket "win" over older tickets as being the duplicated (not: duplicat*ing*) ticket?
I mean, this ticket is from 2013 whereas MC-93132 is from 2015. Shouldn't the status on this issue rather be tracked here in this ticket?

Because that ticket provides better information.

The.Modificator

(Unassigned)

Community Consensus

Minecraft 1.5, Minecraft 1.5.1, Minecraft 1.7.2, Minecraft 1.7.4, Minecraft 14w11b, Minecraft 1.8.1-pre3, Minecraft 1.8.1, Minecraft 16w43a

Retrieved