I placed a lightning rod at an altitude of about Y:20 on a superflat world, connected to a tower of glass blocks to transmit the redstone signal downwards. On starting a thunderstorm, the lighting rod was struck within minutes.
I extended the redstone tower upwards to Y:>128, with repeaters to boost the redstone signal. Testing with a lever resulted in the tower operating as expected, but when I replaced the lever with an upward-facing lighting rod (as in the successful test), the lighting rod was not struck by lightning even after an hour.
Reducing the tower to Y: between 100 and 127 also failed to result in lightning striking the rod.
Attachments
Comments 7
I can confirm that this issue still exists in 1.17.11.
I have a bell in the y:~120 tower, as well as a repeater loop that will lock on in the event of a lighning strike.
I also set up a similar arrangement at y:~6 in an adjacent chunk.
In the time that I had to reset the repeater loop roughly 10 times in the y:~6 tower after lighning strikes, I did not have to reset the loop at the base of the y:~120 tower even once.
Either lightning was not striking the y:~120 tower, or for some reason, the lightning rod was not activating the redstone ladder assembly as the lever attached to the block supporting the lightning rod does.
Yes, this is still an issue in 1.18.2.
No change in behavior since 1.17.11
I have confirmed that the redstone ladder/repeater circuit is operational by using a lever on the block to which the lightning rod is attached, however lightning does not appear to strike this high-placed lightning rod in the time that the ground-level lightning rod is struck 10 times or more.
Is this still an issue in the latest version? If yes, can you please add it to the affected versions (or mention it if you are not the reporter)?
This ticket will automatically reopen when you reply.
Lightning still doesn't hit the high lightning rod, even when all lower lightning rods in the same and nearby chunks broken. Low rod struck within seconds of being placed.
Cleaning up old tickets: This ticket has not been updated recently (~3 months+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the [Issue Guidelines|https://aka.ms/MCBugTrackerHelp].
Is this still an issue in the latest version (1.17.11)? If so, can you please add it to the affected versions (or mention it if you are not the reporter).
This ticket will automatically reopen when you reply.