You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
If you do a Skript command which has a permission, it will show the no such command message and show Skript's no permission message.
Expected behavior
A clear and concise description of what you expected to happen.
You shouldn’t see skript’s permission message. To Reproduce
Steps to reproduce the behavior:
Download Skript from their GitHub.
Put Skript's .jar file into the plugins folder.
Restart the server.
Now make a file named test.sk in /plugins/Skript/scripts/.
Put this text into the file:
command /test:
permission: permission.test
trigger:
send "test" to player
Do the command /test. Make sure you do NOT have operator or the permission permission.test.
It will send the configured no such command but it also sends Skript's no permission message. Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
If this is the case, skript is ignoring the command cancellation state. You can use protocollib mode to stop the command before it's processed by the server. There's nothing other plugins can do when skript just decides to send their message anyway regardless of event cancellation.
Describe the bug
A clear and concise description of what the bug is.
If you do a Skript command which has a permission, it will show the no such command message and show Skript's no permission message.
Expected behavior
A clear and concise description of what you expected to happen.
You shouldn’t see skript’s permission message.
To Reproduce
Steps to reproduce the behavior:
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: