Skip to content

Releases: TCPShield/RealIP

TCPShield 2.8.0

01 Jun 04:34
Compare
Choose a tag to compare

Changes

  • As of this version, the required Java version has been bumped from 8 to 17
  • Disable prefer-protocollib by default in favor of the Paper handler
  • Added a warning for users of 1.20.5/1.20.6 and ProtocolLib <= 5.2.1 of incompatibility issues and default back to Paper handler if prefer-protocollib is enabled

TCPShield 2.7.0

22 Jan 23:02
Compare
Choose a tag to compare

Fixes

  • Updated the Velocity packet handler to include support for the new class names in this this commit: PaperMC/Velocity@2ac8751

  • The release jar has been compiled as per usual with Java 8, however this will likely change for future versions.

TCPShield 2.6.1

19 Sep 19:44
bb7511d
Compare
Choose a tag to compare

Fixes

  • Changed the ProxyPingEvent listener to ignore the new ServerData packet and any event fired with the connection being an instance of ConnectedPlayer, this fixes the spam of errors specifically on 1.19 with newer Velocity builds.

  • The release jar has been compiled as per usual with Java 8, however this will likely change for future versions.

TCPShield 2.6.0

28 Jun 02:42
Compare
Choose a tag to compare

This release mainly fixes a few things regarding non-proxy users (raw Spigot/Paper).

Fixes

  • Updated ProtocolLib dependency to 5.x.x and refactor the implementation for 1.19 support.

Changes

  • Added a new config option: prefer-protocollib, this defaults to true so users with ProtocolLib will use that over the regular Paper integration, this is due to that implementation exposing MOTDs to direct connect users, this however does require version 5.x.x of ProtocolLib or it will throw an error, disable that config option if you're using Paper with an unsupported version of ProtocolLib.

  • This also includes a new config option from an unreleased 2.5.7 version which aimed to disable a specific event for Velocity users if they ran into a random error with said event passing erroneous data, unable to reproduce so added that as a hotfix.

Notes

  • Due to the new ProtocolLib changes, the ProtocolLib implementation should not work on versions below 5.x.x, so if you're running a server on 1.18.2 or below with ProtocolLib 4.x.x, refer to https://github.com/TCPShield/RealIP/releases/tag/2.5.6

  • The release jar has been compiled as per usual with Java 8, however this will likely change for future versions.

TCPShield 2.5.6

02 Feb 18:54
Compare
Choose a tag to compare

Changes

  • Re-introduce PreLoginEvent for Velocity.

Note: this update is old and just hasn't been released.

TCPShield 2.5.5

21 Nov 17:18
Compare
Choose a tag to compare

Changes

  • Support Velocity's new LoginInboundConnection class.

TCPShield 2.5.4

27 Oct 21:25
Compare
Choose a tag to compare

Changes

  • Actual Geyser support which isn't blocked without disabling only-allow-proxy-connections - this is a beta release so if you run into any issues with Geyser, create a ticket in the TCPShield Discord.
  • Added description to plugin.yml for 1.17 support.
  • Fixes an issue with hostnames that results in players being unable to join due to an erroneous Velocity event providing incorrect data.

TCPShield 2.5.3

02 Aug 03:38
Compare
Choose a tag to compare

Changes

  • Re-introduce support for java 8 due to high demand (however this is not recommended and will print a warning message)

TCPShield 2.5.2

28 Jul 19:34
Compare
Choose a tag to compare

Changes

  • Removed setting final fields via reflection due to Java 12+ having issues
  • Fixes issues with being unable to join if you were using Java 12+

TCPShield v2.5

12 May 09:25
17a28b1
Compare
Choose a tag to compare

Changes

  • Major refactor of the plugin (kudos to xPlumpOrange)
  • Fixes pre-login issues with Velocity
  • Deprecating CIDR based validation (see below)

Notes

  • Users running v2.4 are recommended to upgrade as we are deprecating CIDR based validation. This has unfortunately caused issues for customers where web requests to our /v4/ endpoint may fail resulting no valid entries being created in the corresponding folder.