Skip to content

Conversation

@Axyss
Copy link
Contributor

@Axyss Axyss commented Oct 29, 2025

Adds the feature described in #13200. Hate the way i'm transforming WeatheringCopper.WeatherState values into WeatheringCopperState ones, but I haven't found a cleaner way.

@Axyss Axyss requested a review from a team as a code owner October 29, 2025 18:44
@github-project-automation github-project-automation bot moved this to Awaiting review in Paper PR Queue Oct 29, 2025
@Axyss Axyss force-pushed the feat/copper-golem-state-event branch from b1ebdf5 to 8d216ec Compare October 29, 2025 18:48
Copy link
Contributor

@lynxplay lynxplay left a comment

Choose a reason for hiding this comment

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

There are two other ways a copper golem might change its weathering state, one through lightning hit, the other through a player using an axe.

The event definitely needs to be called for these two usecases too.
How we'd expose the lightning or player entity is a bit up in the air.
We could not expose much for now probably tho and down the line (if required and asked for) think about some sealed Cause interface.

@github-project-automation github-project-automation bot moved this from Awaiting review to Changes required in Paper PR Queue Nov 1, 2025
@Axyss Axyss force-pushed the feat/copper-golem-state-event branch from 86ee573 to 4723e34 Compare November 2, 2025 18:46
@Axyss Axyss force-pushed the feat/copper-golem-state-event branch from 4723e34 to c54aa9d Compare November 2, 2025 20:12
@Axyss
Copy link
Contributor Author

Axyss commented Nov 2, 2025

A Cause interface sounds good. But yeah, it's probably better to wait.

Perhaps a nullable method that exposes the player that triggers the event would suffice for now?

@Axyss Axyss requested a review from lynxplay November 2, 2025 20:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Changes required

Development

Successfully merging this pull request may close these issues.

2 participants