-
-
Notifications
You must be signed in to change notification settings - Fork 157
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
Added WrapperPlayServerSculkVibrationSignal #380
base: 2.0
Are you sure you want to change the base?
Added WrapperPlayServerSculkVibrationSignal #380
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of a string identifier, maybe see if the ResourceLocation can be used. PacketWrapper#readResourceLocation or readIdentifier, is what it might be called in the wrappers.
I will test it today or tomorrow. |
…estinationIdentifier`
Does it work on 1.8? |
No. Sculks were introduced on newer versions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On wiki.vg it says the "destination" (field after the destination identifier) can either be a VarInt ENTITY ID or a Long encoded block position. So this code might not always work? https://wiki.vg/Protocol#Sculk_Vibration_Signal
Yea but I don't know under which circumstances. I tested it for a few time and haven't received any errors or such. |
Have you checked minecraft's vanilla code? |
I'll check. |
Depends on the identifier. I think the identifier can either be "minecraft:entity" or "minecraft:block" according to vanilla code. |
But I'd say do some debugging too. |
Alright, will do it later |
https://wiki.vg/Protocol#Sculk_Vibration_Signal
Tested Server-Versions: 1.18.2