Dylan T.
Dylan T.
why is that change exclusive to bleeding-edge?
New network architecture in 4.0 addresses problems with receiving packets at the wrong time, and also sending packets in the wrong direction. The issue of the server sending packets at...
If nothing else, enchantment levels need to be restricted to `Limits::INT16_MAX`, as that's the largest value that can be stored in enchantment NBT currently.
This turned out to be problematic because there's no requirement to centrally register `Permission` objects, leading to the type being useless for registration enforcement. This is much the same problem...
The proposed solution is too techy and it's too difficult to understand wtf it's doing. I'd be more inclined to go with #6704 to allow people to implement this themselves.
#6837 will obviate the need for this by allowing `Parameter`s to decide how to consume tokens from a command string. We won't be doing the whole `string[] $args` thing going...
I don't see any bug. It's doing exactly what it's supposed to do.
"Session expires" is not a PocketMine disconnect message. I'm not sure you're looking in the right place for the cause.
Not sure what I can do about this. I can make the logs less noisy, but if this isn't a LogDOS attack then there's not much else I can do.