Skip to content

Conversation

@Cryptite
Copy link
Contributor

While this is a particularly niche event, the logic was already all there in the source.

Use case for us is status effects when touching (corrupted) water and applying damage, etc.

@Cryptite Cryptite requested a review from a team as a code owner January 15, 2026 03:15
@github-project-automation github-project-automation bot moved this to Awaiting review in Paper PR Queue Jan 15, 2026
* Event when an Entity starts touching water or not. This includes even small amounts of flowing water.
*/
@NullMarked
public class EntityTouchWaterEvent extends EntityEvent{
Copy link
Contributor

Choose a reason for hiding this comment

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

Naming feels very confusing.
EntityTouchWaterEvent for when an entity doesn't touch water feels kinda rough.
Formatting also also off here, missing space after EntityEvent.

What prevents us from just having two events for this?

@github-project-automation github-project-automation bot moved this from Awaiting review to Changes required in Paper PR Queue Jan 15, 2026
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