Improve links between Godot notes

exodrifter · exodrifter · commit 5da0712c2b23 · 2024-10-28T02:36:24.000-05:00
diff --git a/content/notes/gdshader.md b/content/notes/gdshader.md
@@ -0,0 +1,14 @@
+---
+title: GDShader
+created: 2024-10-28T05:16:43Z
+aliases:
+- GDShader
+tags:
+- godot
+---
+
+# GDShader
+
+- [GDShader doesn't pause](godot-gdshader-pausing.md)
+- [`gdshaderinc` files are not detected as a dependency](godot-export-dependencies-broken.md)
+- [How do you know if a face is a backface?](godot-gdshader-backface.md)
diff --git a/content/notes/godot-displayed-text.md b/content/notes/godot-displayed-text.md
@@ -1,6 +1,7 @@
 ---
 title: Godot Displayed Text
 created: 2024-10-23T17:45:14Z
+modified: 2024-10-28T04:50:15Z
 aliases:
 - Godot Displayed Text
 tags:
@@ -9,7 +10,7 @@ tags:
 
 # Godot Displayed Text
 
-`RichTextLabel` and `Label` both have a set of properties called "Displayed Text" that you can use to control how much of the text is shown on screen and how that text is displayed.[^1]
+[`RichTextLabel`](godot-rich-text-label.md) and `Label` both have a set of properties called "Displayed Text" that you can use to control how much of the text is shown on screen and how that text is displayed.[^1]
 
 `visible_characters` and `visible_ratio` allow you to define how much of the text you would like to show, allowing you to do animations that make the text appear like it is being typed out. `visible_characters` allows you to do this by defining how many characters to show while `visible_ratio` allows you to do this by defining a percentage (between the value of `0.0` and `1.0`) [^1]
 
diff --git a/content/notes/godot-export-dependencies-broken.md b/content/notes/godot-export-dependencies-broken.md
@@ -1,7 +1,7 @@
 ---
 title: Godot doesn't export dependencies
 created: 2024-10-17T16:42:00Z
-modified: 2024-10-18T21:02:55Z
+modified: 2024-10-28T05:21:06Z
 aliases:
 - "Godot doesn't export dependencies"
 tags:
@@ -12,7 +12,7 @@ tags:
 
 As of Godot 4.3, `Export selected scenes (and dependencies)` might make a non-working build because Godot doesn't make a complete dependency graph. The following dependencies will not be included: [^1]
 - Localization files referenced by the `Localization > Translations` setting.
-- `.gdshaderinc` files that another shader would `#include`.
+- `.gdshaderinc` files that another [GDShader](gdshader.md) would `#include`.
 - Resources that a script will `preload` and store in a `const`.
 - Custom classes only referenced by other scripts, such as classes that contain functions (static or not) that are referenced by other scripts and not used in a scene.
 - Bus layout files referenced by the `audio/buses/default_bus_layout` setting [^2]
@@ -23,4 +23,4 @@ These dependencies will also not be included, but I wouldn't expect Godot to han
 - `FileAccess` does not work for `res://` paths; use `ResourceLoader` instead. I'm guessing this is because when the game is built, the game resources are now in the `.pck` file and there is no file system to navigate. [^2]
 
 [^1]: [20241016143922](../entries/20241016143922.md)
-[^2]: [20241018194335](../entries/20241018194335.md)
+[^2]: [20241018194335](../entries/20241018194335.md)
diff --git a/content/notes/godot-export.md b/content/notes/godot-export.md
@@ -0,0 +1,13 @@
+---
+title: Godot Export
+created: 2024-10-28T05:27:32Z
+aliases:
+- Godot Export
+tags:
+- godot
+---
+
+# Godot Export
+
+- [Dependencies not exported](godot-export-dependencies-broken.md)
+- [Image decompression doesn't work in exported builds](godot-image-decompress-export.md)
diff --git a/content/notes/godot-font-missing-glyphs-on-some-systems.md b/content/notes/godot-font-missing-glyphs-on-some-systems.md
@@ -1,7 +1,7 @@
 ---
 title: Fonts are missing glyphs on some systems
 created: 2024-06-11T02:37:19Z
-modified: 2024-09-19T04:26:37Z
+modified: 2024-10-28T04:58:26Z
 aliases:
 - Fonts are missing glyphs on some systems
 tags:
@@ -10,7 +10,7 @@ tags:
 
 # Fonts are missing glyphs on some systems
 
- By default, Godot's fonts are imported with a setting that allows the use of system fonts as a fallback turned on by default. However, not everyone's machine might have a system font that has the glyph we want to render.
+ By default, [`Font`](godot-font.md) resources in Godot are imported with a setting that allows the use of system fonts as a fallback turned on by default. However, not everyone's machine might have a system font that has the glyph we want to render.
 
 Turning this setting off will ensure that the font will be rendered the same regardless of whose system it is running on.
 
diff --git a/content/notes/godot-font.md b/content/notes/godot-font.md
@@ -0,0 +1,17 @@
+---
+title: "Godot `Font`"
+created: 2024-10-28T04:52:46Z
+aliases:
+- "Godot `Font`"
+- "`Font`"
+tags:
+- godot
+---
+
+# Godot `Font`
+
+- [Missing glyphs on some systems](godot-font-missing-glyphs-on-some-systems.md)
+
+See also:
+
+- [`RichTextLabel`](godot-rich-text-label.md)
diff --git a/content/notes/godot-gdscript-aliased-variables.md b/content/notes/godot-gdscript-aliased-variables.md
@@ -1,7 +1,7 @@
 ---
 title: Exported variables of inherited scenes are aliased
 created: 2024-07-04T14:58:23Z
-modified: 2024-09-19T04:26:37Z
+modified: 2024-10-28T05:11:22Z
 aliases:
 - Exported variables of inherited scenes are aliased
 tags:
@@ -14,7 +14,7 @@ tags:
 >
 > This issue has been fixed for Godot 4.3 (see [godotengine/godot#88741](https://github.com/godotengine/godot/pull/88741)).
 
-In Godot 4.2 or earlier, GDScript variables marked as exported in inherited scenes are aliased.
+In Godot 4.2 or earlier, [GDScript](godot-gdscript.md) variables marked as exported in inherited scenes are aliased.
 
 For example, if you have a scene which inherits another and that scene exports a `Dictionary` variable, that variable will share the same `Dictionary` reference among all instances of that scene. You can get around this issue by manually duplicating the reference in the script.
 
diff --git a/content/notes/godot-gdscript-getter-setter.md b/content/notes/godot-gdscript-getter-setter.md
@@ -1,6 +1,7 @@
 ---
 title: How do I create a getter and setter for variables?
 created: 2023-05-29T21:19Z
+modified: 2024-10-28T05:09:30Z
 aliases:
 - How do I create a getter and setter for variables?
 tags:
@@ -10,7 +11,7 @@ tags:
 # How do I create a getter and setter for variables?
 
 > [!question]
-> How do I create getters and setters for my variables in GDScript so that I can ensure that some code always runs when the value is gotten or set?
+> How do I create getters and setters for my variables in [GDScript](godot-gdscript.md) so that I can ensure that some code always runs when the value is gotten or set?
 
 ```gdscript
 @export var foobar: Array = [] :
diff --git a/content/notes/godot-gdscript-lambdas-capture-by-value.md b/content/notes/godot-gdscript-lambdas-capture-by-value.md
@@ -1,7 +1,7 @@
 ---
 title: Lambdas capture local variables by value
 created: 2024-07-04T07:37:55Z
-modified: 2024-09-19T04:56:37Z
+modified: 2024-10-28T05:14:34Z
 aliases:
 - Lambdas capture local variables by value
 tags:
@@ -10,7 +10,7 @@ tags:
 
 # Lambdas capture local variables by value
 
-In Godot, GDScript lambdas only copy the _value_ of each variable it captures (by design; see [godotengine/godot#69014](https://github.com/godotengine/godot/issues/69014#issuecomment-1324017859)). However, since the value of a `Variant` is itself a reference, you can use a `Variant` to get around this problem if you want the lambda to mutate a capture.
+In Godot, [GDScript](godot-gdscript.md) lambdas only copy the _value_ of each variable it captures (by design; see [godotengine/godot#69014](https://github.com/godotengine/godot/issues/69014#issuecomment-1324017859)). However, since the value of a `Variant` is itself a reference, you can use a `Variant` to get around this problem if you want the lambda to mutate a capture.
 
 For example, this does not work:
 
diff --git a/content/notes/godot-gdscript.md b/content/notes/godot-gdscript.md
@@ -0,0 +1,17 @@
+---
+title: GDScript
+created: 2024-10-28T05:05:15Z
+aliases:
+- GDScript
+tags:
+- godot
+---
+
+# GDScript
+
+- [Exported variables of inherited scenes are aliased](godot-gdscript-aliased-variables.md)
+- [How do I create a getter and setter for variables?](godot-gdscript-getter-setter.md)
+- [Lambdas capture local variables by value](godot-gdscript-lambdas-capture-by-value.md)
+- [Singleton autoloads have an unknown type](godot-singletons-unknown-type.md)
+- [Scripts in deserialized resources are always executed](godot-runs-scripts-in-resources.md)
+- [`@tool` script says function does not exist when it does](godot-tool-script-function-does-not-exist.md)
diff --git a/content/notes/godot-gdshader-backface.md b/content/notes/godot-gdshader-backface.md
@@ -1,7 +1,7 @@
 ---
 title: How do you know if a face is a backface?
 created: 2024-08-02T03:38:38Z
-modified: 2024-09-19T04:26:37Z
+modified: 2024-10-28T05:20:22Z
 aliases:
 - How do you know if a face is a backface?
 tags:
@@ -10,8 +10,6 @@ tags:
 
 # How do you know if a face is a backface?
 
-To check if a face is a backface in a gdshader, you can use the built-in `FRONT_FACING`.
+To check if a face is a backface in a [GDShader](gdshader.md), you can use the built-in `FRONT_FACING`. [^1]
 
-# History
-
-- [20240802_190401](../entries/20240801222015.md)
+[^1]: [20240802_190401](../entries/20240801222015.md)
diff --git a/content/notes/godot-gdshader-pausing.md b/content/notes/godot-gdshader-pausing.md
@@ -1,7 +1,7 @@
 ---
 title: GDShader doesn't pause
 created: 2024-05-30T05:53:46Z
-modified: 2024-09-19T04:26:37Z
+modified: 2024-10-28T05:22:13Z
 aliases:
 - GDShader doesn't pause
 tags:
@@ -10,7 +10,7 @@ tags:
 
 # GDShader doesn't pause
 
-In Godot 4.0, shaders don't pause when the tree is paused as the time parameter continues to increase while the game is paused.
+In Godot 4.0, [GDShaders](gdshader.md) don't pause when the tree is paused as the time parameter continues to increase while the game is paused.
 
 Unfortunately, it doesn't appear like the Godot maintainers will fix this for 4.0, because they believe the canonical solution for this should be to add a new global uniform to the project that takes whether or not the tree is paused into account for use in a shader. 
 
diff --git a/content/notes/godot-json-round-trip.md b/content/notes/godot-json-round-trip.md
@@ -1,7 +1,7 @@
 ---
 title: "`JSON` does not round trip"
 created: 2024-06-18T00:37:16Z
-modified: 2024-09-19T04:26:37Z
+modified: 2024-10-28T04:40:46Z
 aliases:
 - "`JSON` does not round trip"
 tags:
@@ -35,7 +35,7 @@ Value is String? true
 Value is Vector2i? false
 ```
 
-Instead, consider using `store_var` and `get_var` in `FileAccess` (see also: [Arbitrary Code Execution in Godot serialization](godot-serialize-arbitrary-code-execution.md))
+Instead of storing data in JSON, consider using `store_var` and `get_var` in `FileAccess` instead (see: [Arbitrary Code Execution in Godot serialization](godot-serialize-arbitrary-code-execution.md)).
 
 # History
 
diff --git a/content/notes/godot-rich-text-label-first-draw-lag.md b/content/notes/godot-rich-text-label-first-draw-lag.md
@@ -1,7 +1,7 @@
 ---
 title: "`RichTextLabel` lags on first draw"
 created: 2024-06-07T22:04:45Z
-modified: 2024-09-19T04:26:37Z
+modified: 2024-10-28T04:59:24Z
 aliases:
 - "`RichTextLabel` lags on first draw"
 tags:
@@ -10,7 +10,7 @@ tags:
 
 # `RichTextLabel` lags on first draw
 
-`RichTextLabel` uses `TextParagraph` internally to draw text, but since `TextParagraph` caches some information lazily there can be a lag spike when drawing the `RichTextLabel` for the first time.
+[`RichTextLabel`](godot-rich-text-label.md) uses `TextParagraph` internally to draw text, but since `TextParagraph` caches some information lazily there can be a lag spike when drawing the `RichTextLabel` for the first time.
 
 To get around this issue, you can disable the use of system fonts as a fallback or use the `TextParagraph` class directly, and force it to cache the information it needs before the first draw call:
 
diff --git a/content/notes/godot-rich-text-label.md b/content/notes/godot-rich-text-label.md
@@ -0,0 +1,18 @@
+---
+title: "Godot `RichTextLabel`"
+created: 2024-10-28T04:43:13Z
+aliases:
+- "Godot `RichTextLabel`"
+- "`RichTextLabel`"
+tags:
+- godot
+---
+
+# Godot `RichTextLabel`
+
+- [Displayed Text](godot-displayed-text.md)
+- [Lag on first draw](godot-rich-text-label-first-draw-lag.md)
+
+See also:
+
+- [`Font`](godot-font.md)
diff --git a/content/notes/godot-runs-scripts-in-resources.md b/content/notes/godot-runs-scripts-in-resources.md
@@ -1,6 +1,7 @@
 ---
 title: Godot always runs scripts in deserialized resources
 created: 2024-10-10T21:42:27Z
+modified: 2024-10-28T04:35:27Z
 aliases:
 - Godot always runs scripts in deserialized resources
 tags:
@@ -17,6 +18,7 @@ In Godot, any resource that is deserialized by the engine will _also_ be execute
 
 With the `ConfigFile` API, loading this configuration file will also print `Hello, world!` to the console even if we don't try to read the `foobar` value. [^1]
 
-This issue may be addressed in the future by [godotengine/godot-proposals#4925](https://github.com/godotengine/godot-proposals/issues/4925). [^1]
+This issue may be addressed in the future by [godotengine/godot-proposals#4925](https://github.com/godotengine/godot-proposals/issues/4925). [^1] It can also be worked around by using `get_var` and `store_var` (see [Arbitrary Code Execution in Godot serialization](godot-serialize-arbitrary-code-execution.md)). [^2]
 
 [^1]: [202403262131](../entries/202403262131.md)
+[^2]: [20240620003315](../entries/20240620003315.md)
diff --git a/content/notes/godot-serialize-arbitrary-code-execution.md b/content/notes/godot-serialize-arbitrary-code-execution.md
@@ -1,7 +1,7 @@
 ---
 title: Arbitrary Code Execution in Godot serialization
 created: 2024-06-19T00:12:54Z
-modified: 2024-09-19T04:26:37Z
+modified: 2024-10-28T04:35:27Z
 alias:
 - Arbitrary Code Execution in Godot serialization
 tags:
@@ -10,8 +10,8 @@ tags:
 
 # Arbitrary Code Execution in Godot serialization
 
-Many Godot functions allow for arbitrary code execution when a file is loaded. To avoid this vulnerability, you can use `get_var` and `store_var` from `FileAccess`.
+Many Godot functions allow for arbitrary code execution when a file is deserialized due to the fact that [Godot always runs scripts in deserialized resources](godot-runs-scripts-in-resources.md). To avoid this vulnerability, you can use `get_var` and `store_var` from `FileAccess`. [^1]
 
 # History
 
-- [20240620003315](../entries/20240620003315.md)
+[^1]: [20240620003315](../entries/20240620003315.md)
diff --git a/content/notes/godot-singletons-unknown-type.md b/content/notes/godot-singletons-unknown-type.md
@@ -1,16 +1,16 @@
 ---
-title: Godot cannot determine the type of autoloads
+title: Singleton autoloads have an unknown type
 created: 2024-07-03T20:06:52Z
-modified: 2024-09-19T04:26:37Z
+modified: 2024-10-28T05:07:25Z
 aliases:
-- Godot cannot determine the type of autoloads
+- Singleton autoloads have an unknown type
 tags:
 - godot
 ---
 
-# Godot cannot determine the type of autoloads
+# Singleton autoloads have an unknown type
 
-In Godot, if you make a singleton autoload by autoloading a packed scene that has the script attached, the editor will not be able to determine the type of the autoload.
+In Godot, if you make a singleton autoload by autoloading a packed scene that has the script attached, the editor will not be able to determine the type of the autoload in [GDScript](godot-gdscript.md)
 
 To workaround this problem, you will need to tell Godot the type of the autoload.
 
diff --git a/content/notes/godot-tool-script-function-does-not-exist.md b/content/notes/godot-tool-script-function-does-not-exist.md
@@ -1,7 +1,7 @@
 ---
 title: "`@tool` script says function does not exist when it does"
 created: 2024-07-03T19:23:04Z
-modified: 2024-09-19T04:26:37Z
+modified: 2024-10-28T05:43:53Z
 aliases:
 - "`@tool` script says function does not exist when it does"
 tags:
@@ -10,7 +10,7 @@ tags:
 
 # `@tool` script says function does not exist when it does
 
-In Godot, if you try calling a function on a non-tool script from a tool script, you'll get the error that looks like this:
+In Godot [GDScripts](godot-gdscript.md), if you try calling a function on a non-tool script from a tool script, you'll get the error that looks like this:
 
 ```
 res://test.gd:8 - Invalid call. Nonexistent function 'get_color' in base 'Resource (SwatchRef)'.
