Add Armor Stats Documentation + fix up others

Author: Alexandra-Myers

docs/.vitepress/config.ts

@@ -41,6 +41,7 @@ export default defineConfig({
               collapsed: false,
               items: [
                 { text: 'Introduction to Patch Generators', link: '/defaulted/patch-gens/introducing-patch-gens' },
+                { text: `Armor Stats Generator`, link: '/defaulted/patch-gens/armor-stats'},
                 { text: `Vanilla Weapon Stats Generator`, link: '/defaulted/patch-gens/weapon-stats'},
                 { text: `Combat Test Weapon Stats Generator`, link: '/defaulted/patch-gens/combat-test-weapon-stats'}
               ]

docs/defaulted/patch-gens/armor-stats.md

@@ -0,0 +1,38 @@
+---
+name: Armor Stats Generator
+---
+
+# Armor Statistics Modification and You
+
+First off, let's define what this generator is, and does. 
+The primary purpose of this generator is for modifying armor stats in a vanilla-like manner, based on the equipment slot the item goes in.
+
+This will produce a `minecraft:attribute_modifiers` component, as well as `minecraft:max_damage`.
+This generator has the id `defaulted:armor_stats`.
+
+The following is an introduction to how to use it:
+
+First off, mark whether it should maintain the previous attribute modifiers on top of its new ones.
+
+This is defined with a boolean with the name `persist_previous`.
+
+In addition, there are four fields which this generator will take:
+1. `max_damage`: The durability of the item, taking the form of an [armor variable](#armor-variable) of type integer.
+2. `armor`: The armor of the item, taking the form of an [armor variable](#armor-variable) of type integer.
+3. `armor_toughness`: The armor toughness of the item, taking the form of an [armor variable](#armor-variable) of type double.
+4. `knockback_resistance`: The knockback resistance of the item, taking the form of an [armor variable](#armor-variable) of type double.
+
+<a id="armor-variable"></a>
+## Armor Variable Codecs
+
+The specific expected inputs for each field depends on where specifically it is used.
+Armor Variable values represent each possible armor slot and will choose a value based on what the armor they are being parsed for goes into.
+
+If in object form, is decoded as the following:
+1. `helmet`: The value for all armors which go in the head slot.
+2. `chestplate`: The value for all armors which go in the chest slot.
+3. `leggings`: The value for all armors which go in the leggings slot.
+4. `boots`: The value for all armors which go in the feet slot.
+5. `body`: The value for all armors which go in the body slot (typically used for non-humanoid mobs).
+6. `any`: The fallback value for the armor, can provide for any non-specified ones.
+All Armor Variables can be written as a singular form of their expected value, becoming only the fallback.

docs/defaulted/patch-gens/combat-test-weapon-stats.md

@@ -11,24 +11,10 @@ The primary purpose of this generator is for modifying weapon stats in a combat-
 > This patch generator ONLY EXISTS with Combatify installed.
 
 This will produce a `minecraft:attribute_modifiers` component.
+This generator has the id `defaulted:combat_test_weapon_stats`.
 
 The following is an introduction to how to use it:
 
-:::details Pseudocode 
-```json
-{
-    ...
-    "patch_generators": [
-        {
-            "generator": "defaulted:combat_test_weapon_stats",
-            ...
-        }
-    ]
-    ...
-}
-```
-:::
-
 First off, mark whether it should maintain the previous attribute modifiers on top of its new ones.
 
 This is defined with a boolean with the name `persist_previous`.

docs/defaulted/patch-gens/weapon-stats.md

@@ -8,24 +8,10 @@ First off, let's define what this generator is, and does.
 The primary purpose of this generator is for modifying weapon stats in a vanilla-expected manner.
 
 This will produce a `minecraft:attribute_modifiers` component.
+This generator has the id `defaulted:vanilla_weapon_stats`.
 
 The following is an introduction to how to use it:
 
-:::details Pseudocode 
-```json
-{
-    ...
-    "patch_generators": [
-        {
-            "generator": "defaulted:vanilla_weapon_stats",
-            ...
-        }
-    ]
-    ...
-}
-```
-:::
-
 First off, mark whether it should maintain the previous attribute modifiers on top of its new ones.
 
 This is defined with a boolean with the name `persist_previous`.
@@ -95,13 +81,13 @@ The ids for the damage and speed modifiers can be overridden with `damage_id_ove
 ## Weapon-Level-Based Values
 
 If in object form, requires field `type`. Can have the following values, `constant`, `lookup`, and `linear`
-    * Constant has the following fields:
-        1. `value`: A floating-point value.
-        2. `applies_additional`: Whether to apply a bonus provided to it, tier damage in the case of attack damage, 0 otherwise.
-    * Lookup has the following fields:
-        1. `values`: A list of level-matching conditions, which themselves are an object with two fields: a weapon-level-based value of name `value` (taking the same form seen here), and a level condition named `condition`, of a `type` either `clamped`, which takes an integer `min` and integer `max`, and will be satisfied for all numbers between the two (inclusive), or a type `list`, which is a list of accepted levels to match.
-        2. `fallback`: A weapon-level-based value which will be used in the case no value matches.
-    * Linear has the following fields:
-        1. `base`: A weapon-level-based value which will be the base.
-        2. `per_level_above_first`: The weapon-level-based value to add to the base for each level above the first.
+* Constant has the following fields:
+    1. `value`: A floating-point value.
+    2. `applies_additional`: Whether to apply a bonus provided to it, tier damage in the case of attack damage, 0 otherwise.
+* Lookup has the following fields:
+    1. `values`: A list of level-matching conditions, which themselves are an object with two fields: a weapon-level-based value of name `value` (taking the same form seen here), and a level condition named `condition`, of a `type` either `clamped`, which takes an integer `min` and integer `max`, and will be satisfied for all numbers between the two (inclusive), or a type `list`, which is a list of accepted levels to match.
+    2. `fallback`: A weapon-level-based value which will be used in the case no value matches.
+* Linear has the following fields:
+    1. `base`: A weapon-level-based value which will be the base.
+    2. `per_level_above_first`: The weapon-level-based value to add to the base for each level above the first.
 All weapon-level-based values mentioned above can either be in object form or as a single floating-point value resolving to a constant.