The getBlockFace() method of this event always returns the block face that the player clicked on. Before the waterlogging mechanic was introduced this behavior was correct, since water was always placed relative to the block being clicked and never replaced the block itself. But with waterlogging, if the clicked block is a type that can be waterlogged (a fence post, slab, etc), and the block isn't currently waterlogged, the event actually fills the block that was clicked, not the one relative to it. Currently the event still returns the relative BlockFace, but I think in this case it should return BlockFace.SELF, since that's where the fill is actually taking place. This is consistent with how the PlayerBucketFillEvent works.

If the block is already waterlogged, water will be placed relative to the block, so the returned block face is correct in that case. It's only when clicking a block that would be waterlogged that the issue occurs.

This is important for block protection plugins, because they need to know which block was actually changed in order to do a permissions check. With my proposed solution, event.getClickedBlock.getRelative(event.getBlockFace()) would always correctly return the block that was modified by the event. While it is possible to work around this, as shown in the attached file, I don't think the current behavior of the event is correct.