-
-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop syncing beacon effects #289
Labels
type: feature request
This issue is about a new feature or request
Comments
Hi. Are there any advancements regarding beacon effects? |
pull bot
added a commit
to erxson/HuskSync-build
that referenced
this issue
Aug 10, 2024
* refactor: disable potion effects & attributes by default * feat: deprecate Toast notifications * fix: Cancel outbound PacketEvents packets, close WiIIiam278#344 * fix: add boot warning to fabric * fix: stop syncing ambient effects, close WiIIiam278#289 Effects from beacons, conduits, and The Warden will no longer sync. * refactor: auto-reformat code * build: bump runtime dependencies * feat: improve server version status text * refactor: revert "disable attributes/potion effects by default" * docs: update config file --------- Co-authored-by: William <[email protected]>
pull bot
added a commit
to erxson/HuskSync-build
that referenced
this issue
Aug 11, 2024
* refactor: disable potion effects & attributes by default * feat: deprecate Toast notifications * fix: Cancel outbound PacketEvents packets, close WiIIiam278#344 * fix: add boot warning to fabric * fix: stop syncing ambient effects, close WiIIiam278#289 Effects from beacons, conduits, and The Warden will no longer sync. * refactor: auto-reformat code * build: bump runtime dependencies * feat: improve server version status text * refactor: revert "disable attributes/potion effects by default" * docs: update config file --------- Co-authored-by: William <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Because there seem to be countdown issues
The text was updated successfully, but these errors were encountered: