Added notes

source/behavior/features/cave carvers.md

@@ -0,0 +1,3 @@
+# Cave carvers
+
+`"width_modifier"` may also be a float/int. This will be true for the other 2 cave carvers, too.

source/behavior/features/growing_plant.md

@@ -0,0 +1,4 @@
+UP and DOWN can be lowercase or uppercase.  
+Head and body blocks must be arrays of arrays (see my code).  
+The first value of an array in the height distribution array or the value of the "age" property may be of the form `{"range_min": 1, "range_max": 13}`
+or an integer. In other words, the schema is terrible with this one. Again, see my code.

source/behavior/features/ore.md

@@ -0,0 +1,3 @@
+# ore
+
+All references are just block descriptors.

source/behavior/features/rect.md

@@ -0,0 +1,2 @@
+This feature is currently bugged and rather worthless. Presumably, ratio_of_empty_space will only be on [0, 1], but I can't promise this is true. The
+area dimensions may also be restricted by maximum logical sizes, but I can't verify that, either. Otherwise, the schema is probably correct.

source/behavior/features/scatter.md

@@ -0,0 +1,5 @@
+# Scatter features note
+
+The Mojang schema for these features is perfectly valid with a caveat: In scatter features, "x", "y", "z", "scatter_chance", and "iterations" can also
+be numbers, as can the "extents" of any of the coordinates. Well, the extents are arrays, but their bounds can be numbers. Finally, note that anywhere
+a block can be placed in features, a stateful notation can be used, as I describe here: https://wiki.bedrock.dev/concepts/biomes#block-types

source/behavior/features/vegeation.md

@@ -0,0 +1,15 @@
+"replaceable_blocks": array of block references or stateful objects, required even if empty (but useless if empty),  
+"ground_block": block reference, required  
+"waterlogged": boolean, opt, defaults to false,
+
+"surface": string: "floor"|"ceiling", opt, defaults to "floor"  
+"horizontal_radius": int (maybe floats work but are probably truncated), required, must be 0 or greater for feature to work, but no error is thrown if
+negative is given  
+"vertical_range": int >= 0, required, values below 0 clamped,  
+"depth": int, required, typically 1+, 0 acts like 1, negative values do have functionality, though: continue downward indefinitely until hitting an
+invalid block or world boundary,  
+"extra_deep_block_chance": float, [0, 1], values above or below clamped, opt, defaults to 0  
+"extra_edge_column_chance": float, [0, 1], values above or below clamped, opt, defaults to 0
+
+"vegetation_feature": feature reference, required, doesn't do anything when vegetation_chance is 0 or less,  
+"vegetation_chance": float, [0, 1], values above or below clamped, opt, defaults to 0