Skip to content

v1.7.4
Compare
Choose a tag to compare
@retrooper retrooper released this 08 Nov 14:25
· 799 commits to master since this release
1.7.4
a1c591a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Changelog

  • Direction enum cleaned up, unneeded enum constant values removed.
  • NullPointerException with the Player in PacketSendEvent FIXED.
  • WrappedPacketInBlockDig getX(), getY(), getZ() not working FIXED.
  • WrappedPacketInBlockDig.getDirection() optimized and now works on 1.7.10.
    FYI the direction is also known as the block face.
  • WrappedPacketInBlockPlace#getX(), getY(), getZ() not working FIXED.
  • WrappedPacketInBlockPlace#getItemStack() removed as the itemstack field doesn't exist in newer versions.
    Legacy packetevents was lazily coded and actually used a block iterator to find the block you are looking at.
    I now removed the field as we cannot have full cross version compatibility with the method.
    If you don't want to be supporting the newer versions, use my wrapper creation utilities to access it yourself.
  • WrappedPacketInBlockPlace#getDirection() added
  • WrappedPacketInUpdateSign#getX(), getY(), getZ() not working FIXED.
  • WrappedPacketInUpdateSign#getTextLines() errors FIXED.
  • WrappedPacketOutHeldItemSlot wrapper created.(Basically change player's current selected slot)
  • Incompatibility and errors with paper(1.16.x) fixed.
  • PacketEvents.getSettings().packetHandlingThreadCount(int) setting added.
    It lets you decide how many threads PacketEventsshould use when asynchronously injecting/ejecting players, processing packets(PacketEvents' end) and event calling(processing on your end).
    PacketEvents' current default settings are the most recommended settings.
    Having more than one thread doing all that processing might cause you (or PacketEvents, as that feature hasn't been tested that much) some concurrency issues where multiple threads are accessing/modifying the same data at the same time!
Assets 2
Loading