-
-
Notifications
You must be signed in to change notification settings - Fork 375
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
Block sound expression ending loops #7289
Comments
you'll have a console stracktrace can we get that |
My best guess is, since they're running 2.10 beta-1, it doesn't contain the fix for Sound Utils/Sound Class. As both the patch PR and feature PR were merged after 2.10 beta-1 was released. |
I did try the thing in 1.20.1 iirc, it did function then |
That's because 1.21.3 is when Bukkit changed the Sound class from an enum to an interface. Thus causing the issue. |
Ah i see, that makes sense. Then they most likely don't have the patch for it, causing the problem. |
Well the patch is on Skript's end, on how it accesses the Sound class. The patch to fix the issue was completed after 2.10 beta-1 was released. So currently the only version that has the fix is 2.9.5 |
org.bukkit.command.CommandException.txt |
So i suppose i'll have to wait for 2.10 beta-2 or find some workaround using an addon such as skript-reflect? |
You can do whichever, if you need it now you can attempt Skript-Reflect. 2.10 prerelease is in like 2 weeks |
I think i can probably wait that long and just put a placeholder sound in the meantime |
To be more accurate |
Skript/Server Version
Bug Description
Upon use of the Block Sound expression in Skript 2.10.0 with the server version 1.21.3 it provides no error, yet stops loops it is used in.
Expected Behavior
Expected Behaviour of the block sound expression was to return the block sound of a block given in the line it is placed in.
Steps to Reproduce
Errors or Screenshots
The image attached shows a file being reloaded, then the command shown above used to reproduce the error being executed.
Other
No response
Agreement
The text was updated successfully, but these errors were encountered: