Assorted changes from Feb 2020 (Kopernicus#51)

* Add ModScatter templates

* Formatting

* Add template file to copy from

* Add more modularscatter

* Formatting

* LandControl content

* Move ModScatter to LandControl folder

* Formatting

* Cleanup, integrate changes

Author: democat3457

README.md

@@ -1,21 +1,22 @@
-This is the official wiki for the [Kopernicus](https://github.com/Kopernicus/Kopernicus) addon for Kerbal Space Program. 
+# Kopernicus Wiki
+This is the official wiki for the [Kopernicus](https://github.com/Kopernicus/Kopernicus) addon for Kerbal Space Program.  
 The current targeted version of Kopernicus is 1.7.3-1.
 
-# Contributing
+## Contributing
 It is preferred that all contributions be done via a text editor and a Git client, as opposed to authoring the changes on GitHub.
 This allows for consistent page formatting. If you wish to be able to test out changes before uploading, you must install Jekyll and its dependencies.
 
-## External Programs
+### External Programs
 
-### Installing Git
+#### Installing Git
 You may use whatever Git GUI/client you wish, although if you do not already have one we recommend GitKraken or Git itself. The latest version of Git can be downloaded from [https://git-scm.com/downloads](https://git-scm.com/downloads) and GitKraken can be found at [https://www.gitkraken.com/download](https://www.gitkraken.com/download)
 
-### Installing Jekyll (optional)
-Head to [https://jekyllrb.com/docs/installation/](https://jekyllrb.com/docs/installation/) and scroll to the bottom. 
+#### Installing Jekyll (optional)
+Head to [https://jekyllrb.com/docs/installation/](https://jekyllrb.com/docs/installation/) and scroll to the bottom.  
 Click the link that corresponds to your operating system and follow the directions on that page.
 
-## Authoring Changes
-Once you have installed all external programs, fork the wiki repository before cloning your fork to your computer. Create a new branch when making any changes whatsoever. Be sure that your changes follow the stylistic guidelines discussed below. 
+### Authoring Changes
+Once you have installed all external programs, fork the wiki repository before cloning your fork to your computer. Create a new branch when making any changes whatsoever. Be sure that your changes follow the stylistic guidelines discussed below.
 
 ### Page Format
 The format for every page should be as follows:
@@ -30,7 +31,7 @@ Description of the feature/node being discussed, plus an explanation of what it
 **Example**
 ```
 // Your example of the item should go here.
-// Comments should be inline like these unless the comment is for a node. 
+// Comments should be inline like these unless the comment is for a node.
 // If so, then the comments should go on the line above the node.
 
 // ForANode information
@@ -46,8 +47,7 @@ ForANode
 |Property|Format|Description|
 |--------|------|-----------|
 |The name of the property|[type of the property](main/datatypes.md)|The description of the property.|
-|(Example) order|Integer|The order the PQSMod should be applied in.| 
-
-**Links**
+|(Example) order|Integer|The order the PQSMod should be applied in.|
 
+### Links
 Intra-repository links are to be in the form `[text]({{ site.baseurl }}{% link <absolute path in repo> %})`

content/ConfigNodes.md

@@ -3,12 +3,11 @@ layout: default
 title: Config Nodes
 ---
 
-# What is a ConfigNode?
+***What is a ConfigNode?***
 ConfigNodes are a data storage / settings format that is used by KSP. They are most commonly used in `.cfg` files, but you can find them inside of `.craft` and `.sfs` files too.
 Whenever you want to modify anything in KSP, you will have to deal with ConfigNodes.
 
-A Config Node consists of three parts:
-
+A Config Node consists of three parts:  
 * header
 * values
 * subnodes
@@ -72,13 +71,13 @@ Kopernicus
 {
     // Naming the system
     name = My cool system
-    
+
     // Creating my first body
     Body
     {
         // I have heard this name before...
         name = Kerbin
-        
+
         // Access the properties of the body
         Properties
         {
@@ -107,21 +106,20 @@ Kopernicus
     {
         // I have heard this name before...
         name = Kerbin
-        
+
         // Access the properties of the body
         Properties
         {
             // Describing Kerbin
             description = That blue ball around the Sun
-        
+
         } // Properties
-    
+
     } // Body
 
 } // Kopernicus
 ```
 
-
 That way you can always tell where you actually added the node.
 
 # ModuleManager
@@ -232,5 +230,22 @@ Kopernicus
 ## Conditions
 All configs that were previously shown would apply themselves to the first node they can find that matches their name. This is undesired in most cases, since you want to be able to finetune the config of a specific body or part etc. ModuleManager can, instead of selecting the first matching one, select configs based on their values. To do this, you have to add `:HAS[#name[value]]` to the name of the node. `name` is the key of the value you want to select, and `value` it's value. If the value doesn't matter to you, you can use a wildcard, that will match everything: `:HAS[#name[*]]`. You can also negate the selection, `:HAS[~name[value]]` will select a config that doesn't have a property with the specified name.
 
-**TODO: :NEEDS, :FOR, :AFTER**
+### :NEEDS[]
+The `:NEEDS` condition allows a config to specify its dependencies. The config will not run if the specified mod is not installed. The name of the mod will most commonly be the folder name in GameData. Sometimes, the name of the mod will be the name of the `.dll` file, which can be found by right-clicking the file on Windows and selecting Properties. For nested mods in GameData, the name can be found in the config (the `:FOR` condition discussed later). For example, putting `:NEEDS[Fruits]` after the node name makes the config run *only if* the mod `Fruits` is installed.
+
+### :FOR[]
+`:FOR[]` specifies the mod that the config belongs to. It can be used if the mod is located in a nested folder inside GameData. Usually, not every config in a mod will need to include the `:FOR[]` condition.
+
+### Mod Order
+Module Manager loads mods in a certain order according to their conditions.
+1. `:FIRST`
+2. Configs with no condition
+3. `:BEFORE[]`
+4. `:FOR[]`
+5. `:AFTER[]`
+6. `:LAST[]`
+7. `:FINAL`
+
+Each of the conditions except for `:FINAL` accept a mod to go before/for/after/last. Mod names are discussed in the `:NEEDS[]` section.
 
+**TODO: :FOR, :AFTER**

content/Ocean.md

@@ -3,7 +3,7 @@ layout: default
 title: Ocean
 ---
 
-The `Ocean { }` subnode contains all of the information needed to produce an ocean for the specified body. Note that the ocean is one of two Procedural Quad Spheres on the body it is applied to. This means that some PQS Settings can be applied to Oceans.
+The `Ocean { }` subnode contains all of the information needed to produce an ocean for the specified body. Note that the ocean is one of the two Procedural Quad Spheres on the body it is applied to. This means that some PQS Settings can be applied to Oceans.
 
 **Subnodes**
 * Material { }

content/Orbit.md

@@ -24,8 +24,8 @@ Orbit
 
 |Property|Format|Description|
 |--------|------|-----------|
-|referenceBody|String|The `name` of the object the body orbits.|   
-|color|Color|The color of the orbit line. See [the DataTypes page]({{ site.baseurl }}{% link content/datatypes.md %}) for more info on colors.| 
+|referenceBody|String|The `name` of the object the body orbits.|
+|color|Color|The color of the orbit line. See [the DataTypes page]({{ site.baseurl }}{% link content/datatypes.md %}) for more info on colors.|
 |inclination|Double|The tilt of the orbit in degrees. 0 = normal, 90 = polar, 180 = retrograde, etc...|
 |eccentricity|Double|The difference between your body's apoapsis and periapsis. It is a value between 0 and 1, where 0 is a perfect circle, and 1 is a straight line. 0.5 would give an oval shape.|
 |period|Double|The custom orbital period in seconds. This can be used to set extreme orbital periods.|

content/PQSMods/LandControl/LandClasses.md

@@ -3,7 +3,7 @@ layout: default
 title: LandClasses
 ---
 
-`LandClasses` are regions defined by the LandControl PQSMod, in which several features can be customized including features which other PQSMods provide, such as HeightColorMap or noise PQSMods. LandControl regions can change terrain height, change terrain color, add color noise and height noise, and add ground scatters. LandClasses are defined via ranges of altitude, latitude, and longitude.
+`LandClasses` are regions specified by the LandControl PQSMod that can locally customize several features of the PQS, including features from other PQSMods like HeightColorMap or noise PQSMods. LandClasses can change terrain height, change terrain color, add color noise and height noise, and add ground scatters. LandClasses are defined via ranges of altitude, latitude, and longitude.
 
 **Subnodes** - Both are defined under the main table.
 * LerpRange { } = Defines range values
@@ -83,7 +83,7 @@ LandControl
 |name|String|The name of the LandClass.|
 |alterApparentHeight|Single|Supposedly adjusts the terrain's appearance. Only ever observed in the practice of forming icecaps.|
 |alterRealHeight|Double|Supposedly adjusts the terrain's actual height.|
-|minimumRealHeight|Double|The minimum height of the LandClass' terrain.|
+|minimumRealHeight|Double|The minimum height of the LandClass's terrain.|
 |color|Color|The color of the region.|
 |coverageBlend|Single|The blend of the coverage with surrounding LandClasses.|
 |coverageFrequency|Single|The size of the each feature of the LandClass coverage. As frequency gets bigger, size gets smaller.|

content/PQSMods/LandControl/LandControl.md

@@ -3,7 +3,7 @@ layout: default
 title: LandControl
 ---
 
-The `LandControl` PQSMod allows defining regions known as LandClasses, within which you can customize several features of the particular region. 
+The `LandControl` PQSMod allows defining regions known as LandClasses, within which you can customize several features of the particular region.
 
 **Subnodes**
 * [Scatters { }]({{ site.baseurl }}{% link content/PQSMods/LandControl/Scatters.md %}) = Defines used scatters
@@ -58,7 +58,6 @@ PQS
 }
 ```
 
-
 |Property|Format|Description|
 |--------|------|-----------|
 |createColors|Boolean|Whether to use/affect colors.|

content/PQSMods/LandControl/LandControlLanding.md

@@ -4,7 +4,8 @@ title: LandControl
 ---
 
 The `LandControl` PQSMod allows very detailed control over the coloration of terrain, creation of ground scatters, minimum terrain height, and much more.
-It is both verbose and complex with multiple key parts, so in the interest of ease of use and readability (as well as the sanity of the maintainers) LandControl will be split up into a series of pages.
+
+It is both verbose and complex with multiple key parts, so in the interest of ease of use and readability (as well as the sanity of the maintainers), LandControl will be split up into a series of pages.
 
 * [LandControl]({{ site.baseurl }}{% link content/PQSMods/LandControl/LandControl.md %})
 * [LandClasses]({{ site.baseurl }}{% link content/PQSMods/LandControl/LandClasses.md %})

content/PQSMods/LandControl/ModularScatter/ModularScatter.md

@@ -3,8 +3,9 @@ layout: default
 title: ModularScatter
 ---
 
-ModularScatter is a system for easily adding behaviour to ground scatters in much the same way that PartModules add behaviour to parts. 
-There are currently four ModularScatter components.
+ModularScatter is a PQS LandControl system for easily adding behavior to ground scatters in much the same way that PartModules add behavior to parts.
+
+There are currently four ModularScatter components that you can add to a scatter.
 
 * [HeatEmitter]({{ site.baseurl }}{% link content/PQSMods/LandControl/ModularScatter/HeatEmitter.md %})
 * [LightEmitter]({{ site.baseurl }}{% link content/PQSMods/LandControl/ModularScatter/LightEmitter.md %})

content/PQSMods/LandControl/ScatterMaterialType.md

@@ -132,4 +132,3 @@ Material
     ZWrite = Single, default is 0
 }
 ```
-

content/PQSMods/LandControl/Scatters.md

@@ -3,7 +3,7 @@ layout: default
 title: Scatters
 ---
 
-The `Scatters` node in the LandControl PQSMod defines the scatters to be used within the [LandClasses]({{ site.baseurl }}{% link content/PQSMods/LandControl/LandClasses.md %}) provided by LandControl.
+The `Scatters` node in the LandControl PQSMod defines the scatters to be used within the [LandClasses]({{ site.baseurl }}{% link content/PQSMods/LandControl/LandClasses.md %}) provided by LandControl. Scatters are 3D meshed objects that are generated on the surface and can have various configurable features added via the `Components` subnode.
 
 **Subnodes**
 * [Material { }]({{ site.baseurl }}{% link content/PQSMods/LandControl/ScatterMaterialType.md %})

content/PQSMods/PQS.md

@@ -7,8 +7,8 @@ The `PQS { }` node describes properties of the Procedural Quad Sphere that makes
 **Subnodes**
 * PhysicsMaterial { } (below)
 * Material { }
-  * [AtmosphericTriplanarZoomRotation]({{ site.baseurl }}{% link content/Material/PQSAtmosphericTriplanarZoomRotation.md %})
-  * [AtmosphericTriplanarZoomRotationTextureArray]({{ site.baseurl }}{% link content/Material/PQSAtmosphericTriplanarZoomRotationTextureArray.md %})
+  + [AtmosphericTriplanarZoomRotation]({{ site.baseurl }}{% link content/Material/PQSAtmosphericTriplanarZoomRotation.md %})
+  + [AtmosphericTriplanarZoomRotationTextureArray]({{ site.baseurl }}{% link content/Material/PQSAtmosphericTriplanarZoomRotationTextureArray.md %})
 * FallbackMaterial { }
 * [Mods { }]({{ site.baseurl }}{% link content/PQSMods/PQSMods.md%})
 

content/PQSMods/VertexHeightNoise.md

@@ -3,7 +3,7 @@ layout: default
 title: VertexHeightNoise
 ---
 
-The `VertexHeightNoise` PQSMod is a mod that adds height noise to the terrain. This makes the terrain bumpier, though the "style" of bumps/features change with the noise type. 
+The `VertexHeightNoise` PQSMod is a mod that adds height noise to the terrain. This makes the terrain bumpier, though the "style" of bumps/features change with the noise type.  
 The noise is also additive, meaning that instead of overwriting the terrain altitude, it simply adds or subtracts from it.
 
 <button data-toggle="collapse" data-target="#collapse-vhn-example">Show Example</button>
@@ -25,7 +25,7 @@ PQS
       noiseType = Perlin
       mode = High
       lacunarity = 0.7
-      
+
       enabled = true
       order = 25
     }
@@ -69,35 +69,35 @@ PQS
     {
         VertexHeightNoiseVertHeightCurve2
         {
-            // All blank fields can be whatever you want, see the VHNVHC2 page for more information on them. 
-            deformity = 
-            ridgedMode = 
+            // All blank fields can be whatever you want, see the VHNVHC2 page for more information on them.
+            deformity =
+            ridgedMode =
 
-            ridgedAddSeed = 
-            ridgedAddFrequency = 
-            ridgedAddLacunarity = 
-            ridgedAddOctaves = 
+            ridgedAddSeed =
+            ridgedAddFrequency =
+            ridgedAddLacunarity =
+            ridgedAddOctaves =
 
-            ridgedSubSeed = 
+            ridgedSubSeed =
             ridgedSubFrequency = 0
-            ridgedSubLacunarity = 
-            ridgedSubOctaves = 
+            ridgedSubLacunarity =
+            ridgedSubOctaves =
 
             simplexCurve
             {
                 key = 0 1
                 key = 1 0
             }
 
-            simplexHeightStart = 
-            simplexHeightEnd = 
-            simplexSeed = 
-            simplexOctaves = 
-            simplexPersistence = 
+            simplexHeightStart =
+            simplexHeightEnd =
+            simplexSeed =
+            simplexOctaves =
+            simplexPersistence =
             simplexFrequency = 0
 
             enabled = true
-            order = 
+            order =
         }
     }
 }

content/Properties/Properties.md

@@ -3,14 +3,13 @@ layout: default
 title: Properties
 ---
 
-The `Properties { }` node describes the body itself, and is a subnode of `Body { }`. Basic parameters like description, radius, gravity and biomes are specified here. 
+The `Properties { }` node describes the body itself, and is a subnode of `Body { }`. Basic parameters like description, radius, gravity and biomes are specified here.
 
-### Subnodes
-***
+**Subnodes**
 * [Biomes/Biome { }]({{ site.baseurl }}{% link content/Properties/Biome.md %})
 * [ScienceValues { }]({{ site.baseurl }}{% link content/Properties/ScienceValues.md %})
 
-## Example
+**Example**
 ```md
 Properties
 {

content/ScaledVersion/ScaledVersion.md

@@ -5,7 +5,6 @@ title: ScaledVersion
 
 The `ScaledVersion { }` node in a configuration file for Kopernicus describes a less-detailed model of your planet that appears in the map view and from large distances.
 
-
 **Subnodes**
 * [Material { }]({{ site.baseurl }}{% link content/ScaledVersion/Material.md %}) = Updates to textures and atmosphere rims.
 * [OnDemand { }]({{ site.baseurl }}{% link content/ScaledVersion/OnDemand.md %}) = Used for textures that should be loaded OnDemand.

content/kex/CometTails.md

@@ -60,4 +60,4 @@ Body
 |radius|Single|The radius of the teardrop that makes up the comet tail. Default is 2000.|
 |length|Single|The length of the comet tail. Default is 16000.|
 |opacityCurve|FloatCurve|A curve that associates a distance value with an opacity value from 0 to 1?|
-|brightnessCurve|FloatCurve|A curve that associates a distance value with a brightness value.|
+|brightnessCurve|FloatCurve|A curve that associates a distance value with a brightness value.|

index.md

@@ -51,7 +51,7 @@ title: Kopernicus Wiki
   + [Particles subnode (Post-1.8)]({{ site.baseurl }}{% link content/Particles.md %})
 
 ## KopernicusExpansion
-**WARNING: These pages are not intended for beginners, and a basic level of experience is assumed.**
+> **WARNING: These pages are not intended for beginners, and a basic level of experience is assumed.**
 * [Comet Tails]({{ site.baseurl }}{% link content/kex/CometTails.md %})
 * [Emissive FX]({{ site.baseurl }}{% link content/kex/EmissiveFX.md %})
 * [EVA Footprints]({{ site.baseurl }}{% link content/kex/EVAFootprints.md %})

template.txt

@@ -0,0 +1,15 @@
+// Template for new files - remove this line after copy
+---
+layout: default
+title: PageTitle
+---
+
+[Description]
+
+[Subnodes]
+
+[Example]
+
+|Property|Format|Description|
+|--------|------|-----------|
+[Table]