-
Notifications
You must be signed in to change notification settings - Fork 29
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
Advancement Criteria Questions - Location & Inventory Change #12
Comments
Sorry for the late reply. Negative values work for me in the latest snapshot. Make sure you're setting NBT fields are just the same as you'd use in commands. For example: "nbt": "{Invulnerable:1b}" However, keep in mind that nested quotes will need to be escaped with a backslash, otherwise those un-escaped quotes will close the field early, causing a syntax error. For example, the following is incorrect is will throw an error: "nbt": "{SomeTag:"value"}" While the following is correct: "nbt": "{SomeTag:\"value\"}" |
Hi, thanks for the reply. I was using 1.12 when I opened the thread so I'll give 1.13 a try. For nbt, in the case of multiple tags would this be correct? |
You closed the root compound (indicated by curly brackets) and opened a new one. This will throw a syntax error (i.e. you have
|
Thanks for the correction, I appreciate it. |
I've just had another attempt in 1.13. The above doesn't work for me. |
https://github.com/skylinerw/guides/blob/master/java/advancements/triggers.md#location
For the Location criteria, it doesn't seem to allow negative coordinates - is there a way around this?
https://github.com/skylinerw/guides/blob/master/java/advancements/triggers.md#inventory_changed
Could you please do a guide on the nbt condition?
The text was updated successfully, but these errors were encountered: