Releases: qixils/java-crowd-control
Releases · qixils/java-crowd-control
java-crowd-control v3.9.2
What's Changed
- 🧹 Prevented exceptions from being thrown when TimedEffect can't write to a valid socket
- 🧹 Marked
Request#getType
as@Nullable
to properly reflect the fact that new packet types may be added in the future which are unaccounted for
Full Changelog: v3.9.1...v3.9.2
java-crowd-control v3.9.1
What's Changed
- 🧹 Attempts to pause/resume timed effects will now fallback to the normal start/stop callbacks if custom callbacks are not supplied
- 🧹 Lowered the level of some logs
Full Changelog: v3.9.0...v3.9.1
java-crowd-control v3.9.0
What's Changed
- 💀 GitHub package publishing has been removed because it was never used. Thanks GitHub for requiring authentication to download from it 🙄
- 🧹 Various functions relating to IPs now deal with
InetAddress
es instead ofString
s. - ✨ When operating in server mode, you can now bind to a specific IP. Useful for owners of large server networks.
- ✨ Added
TimedEffect#stopAll
to stop all timed effects targeting the specified streamer. This is currently not used internally, though you can use it yourself when receiving a Request with anull
effect
andType.STOP
.
Full Changelog: v3.8.1...v3.9.0
java-crowd-control v3.8.1
This update adds a new method SocketManager#addLoginListener
. It functions similarly to #addConnectListener
but first waits for the client to successfully login to the server.
java-crowd-control v3.8.0
This is a hotfix release that temporarily removes Request#getParameters to allow games that don't use it to work with the CC 2.0.2 app update. A proper update for the method's new signature will arrive at a later date.
java-crowd-control v3.7.3
The prefix of log messages now all consistently begin with CrowdControl/
instead of some using just CC-
and others lacking a prefix entirely.
java-crowd-control v3.7.2
Restored some backwards compatibility with Crowd Control "1.0".
Full Changelog: v3.7.1...v3.7.2
java-crowd-control v3.7.1
Fixed an issue with the server forgetting what effect statuses it has reported on.
Full Changelog: v3.7.0...v3.7.1
java-crowd-control v3.7.0
What's Changed
- Effect status packets now take in multiple IDs and a type of ID (EFFECT, GROUP, or CATEGORY)
- Duplicate effect status packets are no longer sent (i.e. attempting to send
VISIBLE
before aNOT_VISIBLE
will be ignored) - Updated internals for CC2 API changes and improved compatibility
Full Changelog: v3.6.2...v3.7.0
java-crowd-control v3.6.2
What's Changed
- Added
Request.Target#equalsRoughly
for determining if two targets share the same non-null Service ID, CC ID, or otherwise pass#equals
. - Updated internals for CC2 API changes and improved compatibility