Merge pull request #378 from Luracasmus/main

Add missing API items & details and fix broken links

Author: jbritain

src/content/docs/current/Guides/Your First Shaderpack/4_shadows.mdx

@@ -323,7 +323,7 @@ float shadow = step(shadowScreenPos.z, texture(shadowtex0, shadowScreenPos.xy).r
 
 with
 
-```
+```glsl
 vec3 shadow = getShadow(shadowScreenPos);
 ```
 

src/content/docs/current/How To/coordinate_spaces.mdx

@@ -49,4 +49,4 @@ It is also worth noting that in third person mode, view bobbing is disabled, and
 ## Shadow Space
 "Shadow Space" can refer to a number of different coordinate spaces, all of which are used for the [shadow pass](/current/reference/programs/shadow/). As such, the "shadow" versions of coordinate spaces are generally equivalent to their normal versions but from the perspective of the shadow camera (the sun/moon). The shadow spaces include **shadow view space**, **shadow clip space**, **shadow NDC space**, and **shadow screen space**.
 
-In the [shadow pass](/current/reference/programs/shadow/), the same base matrices are used ([`modelViewMatrix`](/current/reference/uniforms/matrices/#modelviewmatrix), [`projectionMatrix`](/current/reference/uniforms/matrices/#projectionmatrix), etc), or the `shadow` matrix uniforms (e.g. [`shadowModelView`](/current/reference/uniforms/matrices/#shadowmodelview), [`shadowProjection`](/current/reference/uniforms/matrices/#shadowprojection)) can be used from any program. When sampling the shadow map, positions can be transformed into **player space**, and from there back into *shadow screen space*.
+In the [shadow pass](/current/reference/programs/shadow/), the same base matrices are used ([`gl_ModelViewMatrix`](/current/reference/uniforms/matrices/#gl_modelviewmatrix), [`gl_ProjectionMatrix`](/current/reference/uniforms/matrices/#gl_projectionmatrix), etc), or the `shadow` matrix uniforms (e.g. [`shadowModelView`](/current/reference/uniforms/matrices/#shadowmodelview), [`shadowProjection`](/current/reference/uniforms/matrices/#shadowprojection)) can be used from any program. When sampling the shadow map, positions can be transformed into **player space**, and from there back into *shadow screen space*.

src/content/docs/current/Reference/Attributes/ftransform.mdx

@@ -0,0 +1,27 @@
+---
+title: ftransform
+description: The vertex position in clip space.
+sidebar:
+  label: ftransform
+  order: 2
+---
+
+### `ftransform`
+
+**Valid Programs**: `*.vsh`
+
+---
+
+Function returning the vertex position in clip space.
+
+```glsl
+/*
+	vec3 model_pos = gl_Vertex.xyz;
+	vec4 view_pos = gl_ModelViewMatrix * vec4(model_pos, 1.0);
+	vec4 clip_pos = gl_ProjectionMatrix * view_pos;
+*/
+
+vec4 clip_pos = ftransform(); // Equivalent to the above, not accounting for possible rounding differences.
+
+gl_Position = clip_pos;
+```

src/content/docs/current/Reference/Attributes/gl_Color.mdx

@@ -16,12 +16,14 @@ The vertex color attribute.
 
 The color attribute is often used to apply tints to colored blocks such as leaves, grass, water, etc. It also contains the [vanilla ambient occlusion](/current/reference/constants/ambientocclusionlevel/) and, if enabled, the [old lighting](/current/reference/shadersproperties/features/#oldlighting).
 
-Enabling [`separateAo`](/current/reference/shadersproperties/features/#separateao) will move the ambient occlusion from the `rgb` components of `gl_Color` to the `a` component, which can be applied later like this:
+Enabling [`separateAo`](/current/reference/shadersproperties/features/#separateao) will move the ambient occlusion from the `rgb` components of `gl_Color` to the `a` component in terrain programs, which can be applied later like this:
 
 ```glsl
 vec3 color = gl_Color.rgb * gl_Color.a;
 ```
 
+The `a` component includes tint for alpha in some non-terrain programs.
+
 ### `in vec4 vaColor;`
 
 :::danger

src/content/docs/current/Reference/Attributes/mc_chunkFade.mdx

@@ -21,4 +21,4 @@ The fade-in progress of the geometry. This value is a `float` automatically decl
 
 In `gbuffers_terrain.vsh`, the value will be a float in the range 0-1. In all other gbuffers programs, it will be declared as `const float mc_chunkFade = -1.0;`.
 
-The variable will not be declared if the `FADE_VARIABLE` [feature flag](/current/reference/shadersproperties/flags/) is not available. You should check if the feature is available when using the variable.
+The variable will not be declared if the `FADE_VARIABLE` [feature flag](/current/reference/shadersproperties/flags/) is not available. You should check if the feature is available when using the variable.

src/content/docs/current/Reference/Buffers/ssbo.mdx

@@ -25,14 +25,14 @@ SSBOs require OpenGL 4.3 support, which macOS does not have. For more informatio
 ### Fixed Size SSBOs
 To define the SSBO with a fixed size, put the following in [`shaders.properties`](/current/reference/shadersproperties/overview/) and replace `<totalByteSize>` with the total size of the SSBO in bytes and replace `<index>` with a unique value from 0 to 8.
 
-```
+```properties
 bufferObject.<index> = <byteSize>
 ```
 
 ### Screen-Sized SSBOs
 SSBOs can also be defined as screen-sized (Iris 1.6.6 and later), where their size is relative to the screen dimensions. This is useful for storing data per-pixel. To use this, put the following in [`shaders.properties`](/current/reference/shadersproperties/overview/).
 
-```
+```properties
 bufferObject.<index> = <byteSize> <isRelative> <scaleX> <scaleY>
 ```
 
@@ -73,4 +73,4 @@ void main() {
 
 ## Initialization Data File (Iris 1.8+)
 ### `bufferObject.<index> = <byteSize> <filePath>`
-Iris 1.8 adds support for initializing an SSBO with data from a binary file. Simply append the file path to the end of the SSBO declaration in [`shaders.properties`](/current/reference/shadersproperties/overview/). The value is be initialized at on shader load/reload. This works with only fixed sized SSBOs, and if the size of the file is bigger than the SSBO Iris will throw an error. If the file is smaller than the SSBO, the remaining data in the SSBO will be uninitialized (and is likely to be garbage data).
+Iris 1.8 adds support for initializing an SSBO with data from a binary file. Simply append the file path to the end of the SSBO declaration in [`shaders.properties`](/current/reference/shadersproperties/overview/). The value is be initialized at on shader load/reload. This works with only fixed sized SSBOs, and if the size of the file is bigger than the SSBO Iris will throw an error. If the file is smaller than the SSBO, the remaining data in the SSBO will be uninitialized (and is likely to be garbage data).

src/content/docs/current/Reference/Macros/MAX_COLOR_BUFFERS.mdx

@@ -0,0 +1,14 @@
+---
+title: MAX_COLOR_BUFFERS
+description: Maximum colortex texture count.
+sidebar:
+  label: MAX_COLOR_BUFFERS
+  order: 2
+  badge:
+    text: Iris Only (1.10.5+)
+    variant: tip
+---
+
+### `MAX_COLOR_BUFFERS`
+
+The maximum number of [colortex](/current/reference/buffers/colortex/) textures that a shader pack can use.

src/content/docs/current/Reference/Macros/MC_GLSL_VERSION.mdx

@@ -8,4 +8,4 @@ sidebar:
 
 ### `MC_GLSL_VERSION`
 
-The maximum GLSL version supported by the system. For example: 120, 330, 460, etc.
+The maximum GLSL version supported by the system. For example: 120, 330, 460, etc.

src/content/docs/current/Reference/Macros/MC_GL_VERSION.mdx

@@ -13,4 +13,4 @@ The maximum OpenGL version supported by the system, encoded in an integer format
 For example:
 - OpenGL 2.1 -> 210
 - OpenGL 3.3 -> 330
-- OpenGL 4.6 -> 460
+- OpenGL 4.6 -> 460

src/content/docs/current/Reference/Macros/MC_HAND_DEPTH.mdx

@@ -10,9 +10,9 @@ sidebar:
 
 The clip space depth multiplier applied to geometry in [`gbuffers_hand`](/current/reference/programs/gbuffers/) and [`gbuffers_hand_water`](/current/reference/programs/gbuffers/).
 
-The multiplier is applied in clip space automatically through the [projection matrix](/current/reference/uniforms/matrices/#projectionMatrix). When working backwards from the depth buffer, the multiplier should be applied in NDC space rather than screen space to produce the correct result, for example:
+The multiplier is applied in clip space automatically through the [projection matrix](/current/reference/uniforms/matrices/#gl_projectionMatrix). When working backwards from the depth buffer, the multiplier should be applied in NDC space rather than screen space to produce the correct result, for example:
 
 ```glsl
 float screenDepth = textureLod(depthtex0, texcoord, 0.0).r;
 float ndcDepth = (screenDepth * 2.0 - 1.0) / MC_HAND_DEPTH;
-```
+```