Skip to content

fix: include lightning rod in copper oxide flag#4886

Open
florianreuth wants to merge 1 commit into
IntellectualSites:mainfrom
florianreuth:bugfix/include-lightning-rod
Open

fix: include lightning rod in copper oxide flag#4886
florianreuth wants to merge 1 commit into
IntellectualSites:mainfrom
florianreuth:bugfix/include-lightning-rod

Conversation

@florianreuth

Copy link
Copy Markdown
Contributor

Overview

Since Minecraft 1.21.11, they can oxide as well.

Description

Adds another check for lightning rods to the block form event for 1.17+ servers.

Submitter Checklist

  • Make sure you are opening from a topic branch (/feature/fix/docs/ branch (right side)) and not your main branch.
  • Ensure that the pull request title represents the desired changelog entry.
  • New public fields and methods are annotated with @since TODO.
  • I read and followed the contribution guidelines.

Since 1.21.11, they can oxide as well

Signed-off-by: Florian Reuth <git@florianreuth.de>
@florianreuth florianreuth requested a review from a team as a code owner June 8, 2026 20:42
Copilot AI review requested due to automatic review settings June 8, 2026 20:42

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates the copper oxidation block-form listener logic to also cover lightning rods by checking the new block type name once and matching multiple copper-related materials.

Changes:

  • Cache event.getNewState().getType().name() into a local variable.
  • Expand the block-type check from only *COPPER* to *COPPER* or *LIGHTNING_ROD*.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants