Support 1.19.4?
BySwiizen opened this issue ยท 24 comments
Yes all code is waiting to be pushed. There is one error right now related to dependency so I'm waiting for a fix.
Yes all code is waiting to be pushed. There is one error right now related to dependency so I'm waiting for a fix.
Are you also waiting for a ProtocolLib fix?
Yes all code is waiting to be pushed. There is one error right now related to dependency so I'm waiting for a fix.
Are you also waiting for a ProtocolLib fix?
antipopup is using packetevents
@KaspianDev, ProtocolLib has been updated for 1.19.4!
My plugin is not using protocollib
retrooper/packetevents#562
@KaspianDev, ProtocolLib has been updated for 1.19.4!
@KaspianDev, ProtocolLib has been updated for 1.19.4!
My plugin is not using protocollib retrooper/packetevents#562
The developer is currently working on it
Is there any update on this? if i install the version that it gives me though the plugin list on my server console, it gives me an internal exception, but need the plugin to protect members against random reports.
Is there any update on this? if i install the version that it gives me though the plugin list on my server console, it gives me an internal exception, but need the plugin to protect members against random reports.
if you dont mind the warnings check out 5.5 branch.
Is there any update on this? if i install the version that it gives me though the plugin list on my server console, it gives me an internal exception, but need the plugin to protect members against random reports.
if you dont mind the warnings check out 5.5 branch.
May i ask where i go to get this?
https://github.com/KaspianDev/AntiPopup/tree/5.5
you build it like any other gradle project. ./gradlew build
https://github.com/KaspianDev/AntiPopup/tree/5.5
you build it like any other gradle project.
./gradlew build
i aspect he cant compile itself and searched for a ready to download ;)
https://github.com/KaspianDev/AntiPopup/tree/5.5
you build it like any other gradle project../gradlew build
i aspect he cant compile itself and searched for a ready to download ;)
I have the same problem.
@BySwiizen @MrCrazyAndy @CloudeLecaw
Here's the latest release: https://github.com/KaspianDev/AntiPopup/releases/tag/764c2ad
Let me know if it works with no issues and confirm by either commenting or closing the issue.
@BySwiizen @MrCrazyAndy @CloudeLecaw
Here's the latest release: https://github.com/KaspianDev/AntiPopup/releases/tag/764c2ad Let me know if it works with no issues and confirm by either commenting or closing the issue.
It works for me but in the config file, it will be necessary to specify version 1.19.4 in "mode".
@BySwiizen @MrCrazyAndy @CloudeLecaw
Here's the latest release: https://github.com/KaspianDev/AntiPopup/releases/tag/764c2ad Let me know if it works with no issues and confirm by either commenting or closing the issue.I agree with Bywiizen. it works like a charm in lattest paper 1.19.4. i specified nothing... so what do you mean?
this is my current config. config-version: '28' # Should we collect anonymous data about your server? # false by default. bstats: false # Should we remove [Not Secure] from /say? # There is a very small chance of catching something # that should not be caught. If that happens report the # incident to Github issues of AntiPopup. filter-not-secure: true # Should we prevent messages from being reported? # Leave as true unless you have a different plugin stripping those. strip-signature: true # We dont need that packet if # we dont sign messages. dont-send-header: true # Should setup be ran on first start? # Useful for all kinds of setups or server hosts. auto-setup: false # NMS - Only for 1.19.3 # PACKET - Only up to 1.19.2 mode: NMS # Readd clickable URLs in messages. # Could cause incompabilities! clickable-urls: false # Do not touch ones below! first-run: false ask-bstats: false setup-mode: false
"# NMS - Only for 1.19.3 and 1.19.4"
@BySwiizen @MrCrazyAndy @CloudeLecaw
Here's the latest release: https://github.com/KaspianDev/AntiPopup/releases/tag/764c2ad Let me know if it works with no issues and confirm by either commenting or closing the issue.
I agree with Bywiizen. it works like a charm in lattest paper 1.19.4.
i specified nothing... so what do you mean?
this is my current config.
config-version: '28'
# Should we collect anonymous data about your server?
# false by default.
bstats: false
# Should we remove [Not Secure] from /say?
# There is a very small chance of catching something
# that should not be caught. If that happens report the
# incident to Github issues of AntiPopup.
filter-not-secure: true
# Should we prevent messages from being reported?
# Leave as true unless you have a different plugin stripping those.
strip-signature: true
# We dont need that packet if
# we dont sign messages.
dont-send-header: true
# Should setup be ran on first start?
# Useful for all kinds of setups or server hosts.
auto-setup: false
# NMS - Only for 1.19.3
# PACKET - Only up to 1.19.2
mode: NMS
# Readd clickable URLs in messages.
# Could cause incompabilities!
clickable-urls: false
# Do not touch ones below!
first-run: false
ask-bstats: false
setup-mode: false
i added it at the comentarty.. now in my config
# NMS - Only for 1.19.3 and above
# PACKET - Only up to 1.19.2
your right it might should be changed in default config for new users. else they will ask what they should use..even if the logic what shold be used is clear in this case
what about the old settings from cofnig 23?
# Give it a try if players get kicked
# with message about unsynced message time.
# UNTESTED
prevent-time-sync-kick: false
# Should we prevent messages from being reported?
# Leave as true unless you have a different plugin stripping those.
strip-signature: true
can they be removed? i saw these are no part of the default config anymore...
what about the old settings from cofnig 23?
# Give it a try if players get kicked # with message about unsynced message time. # UNTESTED prevent-time-sync-kick: false # Should we prevent messages from being reported? # Leave as true unless you have a different plugin stripping those. strip-signature: true
can they be removed? i saw these are no part of the default config anymore...
feel free to remove something if you know it isnt there by default anymore. if its needed it will just regenerate.
what about the old settings from cofnig 23?
# Give it a try if players get kicked # with message about unsynced message time. # UNTESTED prevent-time-sync-kick: false # Should we prevent messages from being reported? # Leave as true unless you have a different plugin stripping those. strip-signature: true
can they be removed? i saw these are no part of the default config anymore...
feel free to remove something if you know it isnt there by default anymore. if its needed it will just regenerate.
well i readded it from a backup of config 23. currently i see no difference with these settings in it. so i was not sure if its needed anymore or may not..