Skip to content

Commit ac490f3

Browse files
Defaulted gets its own segment
1 parent 35ecb04 commit ac490f3

File tree

2 files changed

+16
-8
lines changed

2 files changed

+16
-8
lines changed

Diff for: docs/.vitepress/config.ts

+9-1
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ export default defineConfig({
1515
{
1616
text: 'Mods',
1717
items: [
18-
{ text: 'Defaulted', link: '/defaulted' },
18+
{ text: 'Defaulted', link: '/defaulted/intro' },
1919
{ text: 'Atlas Core', link: '/core/intro' }
2020
]
2121
}
@@ -29,6 +29,14 @@ export default defineConfig({
2929
{ text: 'Introduction', link: '/core/intro' }
3030
]
3131
}
32+
],
33+
'/defaulted/': [
34+
{
35+
text: "Defaulted",
36+
items: [
37+
{ text: 'Introduction', link: '/defaulted/intro' }
38+
]
39+
}
3240
]
3341
}
3442
}

Diff for: docs/defaulted.md renamed to docs/defaulted/intro.md

+7-7
Original file line numberDiff line numberDiff line change
@@ -74,24 +74,24 @@ This component patch will apply to every single item that exists.
7474
That is fine if you want to make a global change, but remember that in this exemple we wanted to only apply it to certain items.
7575

7676
From this point, I will introduce the next element:
77-
The `items` and `tag` fields.
77+
The `items` and `tags` fields.
7878

7979
1. `items` defines a set of registered, existing items to apply the patch to.
80-
2. `tag` defines a list of item tags to apply the patch to.
80+
2. `tags` defines a list of item tags to apply the patch to.
8181

8282
:::details {open}
8383
If both are absent, the patch is global, or rather, applies to every item that exists.
8484

85-
Either `items` or `tag` can be absent, items which are patched depend solely on if the item is in the `items` set or is within a tag in the `tag` list.
85+
Either `items` or `tags` can be absent, items which are patched depend solely on if the item is in the `items` set or is within a tag in the `tags` list.
8686

87-
If both are present, then any item within either `items` or `tag` will be patched, so including items which are within a tag which is defined, is generally redundant.
87+
If both are present, then any item within either `items` or `tags` will be patched, so including items which are within a tag which is defined, is generally redundant.
8888
:::
8989

9090
For our example, let's say we want every sword to get this blocking component:
9191

9292
```json{2-4}
9393
{
94-
"tag": [
94+
"tags": [
9595
"minecraft:swords"
9696
],
9797
"patch": {
@@ -127,7 +127,7 @@ The addition to make this occur, is as follows:
127127
"items": [
128128
"minecraft:totem_of_undying"
129129
],
130-
"tag": [
130+
"tags": [
131131
"minecraft:swords"
132132
],
133133
"patch": {
@@ -161,7 +161,7 @@ Ignoring the frivolity of such an idea, here is how you would do that:
161161
"items": [
162162
"minecraft:wooden_axe"
163163
],
164-
"tag": [
164+
"tags": [
165165
"minecraft:pickaxes"
166166
],
167167
"patch": {

0 commit comments

Comments
 (0)