The big toc update

ReWrite-Media · Oct 1, 2020 · 67952b7 · 67952b7
1 parent 7f5d172
commit 67952b7
Show file tree

Hide file tree

Showing 50 changed files with 452 additions and 1 deletion.
diff --git a/concepts/blocks.md b/concepts/blocks.md
@@ -6,6 +6,15 @@ parent: Concepts
 
 # Blocks [BETA]
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 Better documentation on the new block format introduced in the 1.16.100.56 Minecraft beta
 ## Block Properties
 

diff --git a/concepts/components-events-groups.md b/concepts/components-events-groups.md
@@ -6,6 +6,15 @@ parent: Concepts
 
 # Component Groups Vs. Components Vs. Events
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 There are three main structures that make up the base of a behavior-pack entity file. This doc will explain what each of them means, and how to use them.
 
 # Components

diff --git a/concepts/items.md b/concepts/items.md
@@ -6,6 +6,15 @@ parent: Concepts
 
 # Items [Beta]
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 Better documentation on the new item format introduced in the 1.16.100.56 Minecraft beta
 ## Item Events
 

diff --git a/concepts/lang.md b/concepts/lang.md
@@ -6,6 +6,15 @@ parent: Concepts
 
 # Understanding .lang 
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 Bedrock Minecraft allows us to write the text in our addons as codes: For example `action.hint.exit.pig`. Then in the language files, we define these codes: `action.hint.exit.pig=Tap sneak to dismount`.
 
 This workflow has two main advantages:

diff --git a/concepts/materials.md b/concepts/materials.md
@@ -6,6 +6,15 @@ parent: Concepts
 
 # Materials
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 Expert
 {: .label .label-red }
 

diff --git a/concepts/math-based-animations.md b/concepts/math-based-animations.md
@@ -6,6 +6,15 @@ parent: Concepts
 
 # Math-based Animations
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 Intermediate
 {: .label .label-yellow }
 

diff --git a/concepts/mcfunction.md b/concepts/mcfunction.md
@@ -6,6 +6,15 @@ parent: Knowledge
 
 # Understanding .mcfunction
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 `mcfunction` files are stored in your BP as `BP/functions/my_function.mcfunction`. You can add as many functions as you like. 
 
 Functions are used to group multiple Minecraft `commands` (such as `/say` or `/teleport`) into managable chunks (or functions). Function files do not begin with `/`.

diff --git a/concepts/namespaces.md b/concepts/namespaces.md
@@ -6,6 +6,15 @@ parent: Concepts
 
 # Namespaces
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 Namespaces are identifiers that marks content ownership. You can think of them as folders. Namespaces are useful, because they keep naming conflicts from happening.
 
 Namespaces in addon creation can essentially be thought of as "the part to the left of the colon". For example, `minecraft` is the namespace of `minecraft:zombie`. The general form is `namespace:name`.

diff --git a/concepts/render-controller.md b/concepts/render-controller.md
@@ -6,6 +6,15 @@ parent: Concepts
 
 # Render Controllers
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 Beginner
 {: .label .label-green }
 

diff --git a/concepts/shaders.md b/concepts/shaders.md
@@ -6,6 +6,15 @@ parent: Concepts
 
 # Shaders
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 ## Disclaimer
 
 The way to create shaders described in this page is not working on consoles (PS4, Xbox, Switch) and in new rendering 

diff --git a/concepts/sounds.md b/concepts/sounds.md
@@ -6,6 +6,15 @@ parent: Concepts
 
 # Sounds
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 Intermediate
 {: .label .label-yellow }
 

diff --git a/documentation/dummy-components.md b/documentation/dummy-components.md
@@ -6,6 +6,15 @@ parent: Documentation
 
 # Dummy Components
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 Dummy components are useless components that are only used for data storage. Dummy components don't **do** anything on their own. They need to be paired with secondary mechanics to have any function. Dummy components are useful because they allow us to store information on the entities, and use the information to drive graphics/gameplay mechanics.
 
 Good examples are `variant` and `mark_variant`. These components can be set with an Integer value. In the vanilla resource pack, this Integer is used to pick the textures for the Cat, and Horse. Another good example is `is_tamed`, which is used by the Horse to handle whether he is ridable or not.

diff --git a/documentation/molang.md b/documentation/molang.md
@@ -15,6 +15,7 @@ parent: Documentation
 {:toc}
 </details>
 
+
 The bedrock documentation for Molang is notoriously bad. This page will attempt to remedy this by providing additional details for individual queries, *where possible*. This page is intended to be searched, not read in full. Use the side-bar, or use `ctrl-f` to navigate.
 
 # query.armor_texture_slot

diff --git a/documentation/runtime-identifier.md b/documentation/runtime-identifier.md
@@ -6,6 +6,15 @@ parent: Documentation
 
 # Runtime Identifiers
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 `runtime_identifier` is an optional parameter that sits inside the description of the entity's behavior file, and is used to imitate a vanilla entity's hard-coded elements.
 It accepts Vanilla Minecraft identifiers, like `minecraft:shulker`.
 

diff --git a/documentation/subpacks.md b/documentation/subpacks.md
@@ -6,6 +6,15 @@ parent: Documentation
 
 # Subpacks
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 ## What are subpacks?
 
 Subpacks are what cause the gear icon to appear on packs. They were originally intended for texture resolutions to load on different memory capacities, but can also be use to create file variations in behavior and resource packs which can then be chosen by clicking the gear icon and adjusting the slider.

diff --git a/guide/custom-skin-packs.md b/guide/custom-skin-packs.md
@@ -5,6 +5,16 @@ parent: Beginners Guide
 nav_order: 13
 ---
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
+# Skin Packs
 - [Skin pack Manifest](#Skin pack Manifest)
 - [skins.json](#skins.json)
 - [texts/en_US.lang](#texts/en_US.lang)

diff --git a/guide/manifest-function-extension.md b/guide/manifest-function-extension.md
@@ -5,6 +5,16 @@ parent: Beginners Guide
 nav_order: 2
 ---
 
+# Getting Started
+
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
 ___
 ___
 <!-- #### **You will:**  -->

diff --git a/guide/software-preparation.md b/guide/software-preparation.md
@@ -5,6 +5,17 @@ parent: Beginners Guide
 nav_order: 1
 ---
 
+# Software and Preparation
+
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 ___
 ___
 <!-- #### **You will:**  -->

diff --git a/knowledge/1.16-changes.md b/knowledge/1.16-changes.md
@@ -6,6 +6,15 @@ parent: Knowledge
 
 # 1.16 Changes
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 What exactly changed in 1.16? This document will attempt an overview of the known breaking changes and new features.
 
 [Start by reading the change-log!](https://feedback.minecraft.net/hc/en-us/articles/360044928311-Minecraft-Nether-Update-1-16-0-Bedrock-)

diff --git a/knowledge/bedrock-modeling.md b/knowledge/bedrock-modeling.md
@@ -6,6 +6,15 @@ parent: Knowledge
 
 # Bedrock Modeling Introduction 
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 This will be a guide with tips, tricks, and things you should know when modeling for Minecraft Bedrock Edition.
 
 ## Texture Glitch

diff --git a/knowledge/can-place-on.md b/knowledge/can-place-on.md
@@ -6,6 +6,15 @@ parent: Knowledge
 
 # CanPlaceOn and CanDestroy
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 NBT data for Bedrock edition is very limited. Two of the only values we have access to is `CanPlaceOn` and `CanDestroy`. These are used as part of a `/give` command, and edit the place/break properties of players while in adventure mode.
 
 # Format

diff --git a/knowledge/faq.md b/knowledge/faq.md
@@ -4,7 +4,16 @@ title: FAQ
 parent: Knowledge
 ---
 
-### FAQ
+# FAQ
+
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
 
 This page contains a list of frequently asked questions in the technical-bedrock community that do not deserve a long-form wiki entry. Please contribute your own questions/answers, so we can grow this resource!
 

diff --git a/knowledge/style-guide.md b/knowledge/style-guide.md
@@ -6,6 +6,15 @@ parent: Knowledge
 
 # Style Guide
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 This document will present the officially supported Bedrock-Wiki style-guide for addon-creation. The goal of this guide is to promote best-practices while creating addons, and create a consistent format for everyone to follow.
 
 ## Structuring

diff --git a/knowledge/the-editor.md b/knowledge/the-editor.md
@@ -6,6 +6,15 @@ parent: Knowledge
 
 # The Editor
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 The coding world is filled with editors. Ranging from command-line tools like VIM or Emacs, all the way up to full IDEs such as InteliJ or Eclipse. 
 
 For editing JSON files, something in the middle is probably the best. Something that offers you a good amount of power, without the bloat of a full on IDE.

diff --git a/knowledge/useful-links.md b/knowledge/useful-links.md
@@ -6,6 +6,15 @@ parent: Knowledge
 
 # Useful Links 
 
+<details id="toc" open markdown="block">
+  <summary>
+    Table of contents
+  </summary>
+  {: .text-delta }
+1. TOC
+{:toc}
+</details>
+
 There is loads of useful information about Bedrock Development online, but sometimes it is hard to find! I will do my best to keep this list up to date as I continue to find useful content.
 
 ## Tutorials:
-Original file line number
+Diff line change
@@ Expand Up / @@ -15,6 +15,7 @@ parent: Documentation @@
     {:toc}
     </details>
     The bedrock documentation for Molang is notoriously bad. This page will attempt to remedy this by providing additional details for individual queries, *where possible*. This page is intended to be searched, not read in full. Use the side-bar, or use `ctrl-f` to navigate.
     # query.armor_texture_slot
@@ Expand Down @@