Why would the `mineblock` packet not be clamped to at least the render distance or more realistic the chunk the sender is in and the 8 adjacent chunks. I know i'm learning about this in hindsight and it's obvious.
Im actually reminded to the latest log4j exploit (main reason i aint actually gonna run Minecraft for a while) and even the Heartbleed exploit a few years back.
Did yall assume the patch to Paper would just return if the chunk was player loaded, and they wouldn't add any other sane bounds checks?
If the story from the FitMC guy is true, yall guessed/hoped that patch would be what it was. Giving yall a new leak of information without actually fixing the problem because if it was loaded you could still get all the block info in that chunk.
Pretty awesome from where i'm sitting. \(ᵔᵕᵔ)/
I wasn't around for when the patch was engineered into Paper, but from what I'm told, yes that was the idea. :)