From a70aa604a3452af9b70e62696b980d761d09aa53 Mon Sep 17 00:00:00 2001 From: Linnea Gräf Date: Sun, 4 May 2025 15:48:31 +0200 Subject: docs: Fix typo in nbt prism --- web/src/pages/docs/_texture-pack-format.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'web/src') diff --git a/web/src/pages/docs/_texture-pack-format.md b/web/src/pages/docs/_texture-pack-format.md index 89a16bb..182c413 100644 --- a/web/src/pages/docs/_texture-pack-format.md +++ b/web/src/pages/docs/_texture-pack-format.md @@ -362,7 +362,7 @@ An nbt prism (or path) is used to specify where in a complex nbt construct to lo like a dot-separated path (`parent.child.grandchild`), but more complex paths can be constructed. First the specified path is split into dot separated chunks: `"a.b.c"` -> `["a", "b", "c"]`. You can also directly -specify the list if you would like. Any entry in that list not starting with a `*` ist treated as an attribute name or +specify the list if you would like. Any entry in that list not starting with a `*` is treated as an attribute name or an index: ```json @@ -390,7 +390,7 @@ of the values of `[100, 1000]` to your match object. Sometimes values are encoded in a non-nbt format inside a string. For those you can use other star based directives like `*base64` or `*json` to decode those entries. -`*base64` turns a base64 encoded string into the base64 decoded counterpart. `*.json` decodes a string into the json +`*base64` turns a base64 encoded string into the base64 decoded counterpart. `*json` decodes a string into the json object represented by that string. Note that json to nbt conversion isn't always straightforwards and the types can end up being mangled (for example what could have been a byte ends up an int). -- cgit