-
-
Notifications
You must be signed in to change notification settings - Fork 373
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
Basic Function return <none> #4216
Comments
Location function requires a forth argument of world check this |
.. it should run even without it |
This comment has been minimized.
This comment has been minimized.
It is required unless you're using some event that has event-world.
Respect yourself so others respect you. |
it will give default world location which is |
This comment has been minimized.
This comment has been minimized.
You need to learn how to speak to others with respect first. This is the default behavior of Adding to that, I wasn't arguing, I was simply helping you but it turned out that you don't deserve it. |
I don't think it is necessary to become heated in a GitHub issue. Focusing on the actual problem here, a world should not be required as locations do not necessarily have a world (in that world is nullable). I'm not entirely sure how this functioned before, but if a world is not given, we can just create a location without a world or just provide the default world. |
that will settle this debate and create a [bug] label for these issues, |
There should be an error stating that there is no world event value. Since one did not appear this is classified as a bug. Maybe EventValueExpressions don't get init method called for default functions. Can you please provide your complete code as to where this function was used in for testing. Was it a command? |
from function |
Caused by #3841. |
Skript/Server Version
Bug Description
Basic Function from location(x, ,y, z) retrurn none
Expected Behavior
return location
Steps to Reproduce
set {_a} to location(1,100,1)
broadcast "%{_a}%"
Errors or Screenshots
Other
No response
Agreement
The text was updated successfully, but these errors were encountered: