aggregated updates

Author: ljm12914

docs/attributions.mdx

@@ -1,4 +1,4 @@
-# Attributions
+# Attributions for CherryGrove
 
 ## Third-party libraries
 

docs/cg/design/simulation.mdx

@@ -69,4 +69,10 @@ After a lot of thinking, I came up with a design like this:
 5. Execute player input functions from `InputHandler`
 6. Render current state
 
-Surprisingly it's not "read input, update state, render output" but "update state, read input, render output". This is because multiplayer fairness. If we read input at the beginning, players with low latency will be able to modify the world state one tick earlier than players with high latency. Yes we're actually caring for the future multiplayer era.
+Surprisingly it's not "read input, update state, render output" but "update state, read input, render output". This is because multiplayer fairness. If we read input at the beginning, players with low latency will be able to modify the world state one tick earlier than players with high latency. Yes we're actually caring for the future multiplayer era.
+
+## Adoptive Ticking
+
+The question for every video game is: which reference should we align the ticking system to? Some just use turn-based system where there is no concept like time in the game, some use real-time system where the game state is updated according to real-world time, and some use a fixed-tick system where the game state is updated at a fixed rate regardless of real-world time.
+
+CherryGrove uses a fixed-tick system just like Minecraft. But the tick rate is not fixed. It's meant to solve the biggest problem of fixed-tick system: time resolution.

docs/cg/developing.mdx

@@ -56,6 +56,10 @@ The logo also shows a tendency to converge towards the center, which we personal
 
 Some people might perceive the logo as a face, even a modified creeper face or a totem of undying. The logo has nothing to do with them.
 
+:::note
+Do you know that every logo for products within CherryRidge also has exactly 13 pixels in them? That's a tradition starting from CherryGrove's logo.
+:::
+
 ## Licensing
 
 ### What license is applicable for me to do `x`?

docs/cg/faq.mdx

@@ -48,7 +48,7 @@ Compressed CherryGrove content pack folder, similar to `.mcaddon` / `.mcpack`.
 
 ### [`.cgr`](format/cgr)
 
-Compresse CherryGrove relocatable game save, similar to schematic or `.mcstructure` but with `manifest.json` that indexes potentially multiple structures stored using `.cgb` files.
+Compressed CherryGrove relocatable game save, similar to schematic or `.mcstructure` but with `manifest.json` that indexes potentially multiple structures stored using `.cgb` files.
 
 ### `.zip`
 

docs/cg/references/format/index.mdx

@@ -4,22 +4,22 @@ sidebar_position: 2
 
 # Packing CherryGrove
 
-This tutorial will help you pack the installer of CherryGrove for each platform. All packing related resources are located under the `packing` directory.
+This tutorial will help you pack the files and generate the installer / package for each platform. All packing related resources are located under the `packing` directory.
 
 :::warning
-Remember to abide by the [terms](../../legal) when you want to distribute your builds.
+Remember to abide by the [Terms of Use](../../legal#terms-of-use) when you want to distribute your builds.
 :::
 
 ## Microsoft Windows
 
-CherryGrove currently uses NSIS (Nullsoft Scriptable Install System) to pack for installer on Microsoft Windows. Download and install it at: https://nsis.sourceforge.io/Download.
+CherryGrove currently uses Inno Setup to pack for installer on Microsoft Windows. Download and install it at https://jrsoftware.org/isdl.php.
 
-NSIS uses `.nsi` script files to build the installer, which can be found at `packing/windows`. If you want to do a standard packing procedure, follow these steps:
+Inno Setup uses `.iss` script files to build the installer, which can be found at `packing/windows`. If you want to do a standard packing procedure, follow these steps:
 
-1. Build the **release** version of CherryGrove.
-2. Run `packing/windows/pack.bat` and wait for all language varieties to be built.
+1. Build the **release** version of CherryGrove, and check if it works properly and locates **exactly** at `out/windows-x64-release` directory.
+2. Run `packing/windows/pack.bat`. You should see an installer file `CherryGrove_setup_win64.exe` generated inside the same directory.
 
-Adjust the code in the scripts to create your custom procedures.
+Adjust the code in the script to create your custom procedure.
 
 ## Linux
 

docs/cg/releasing/building.mdx

@@ -1,5 +1,7 @@
 # Legal
 
+**To see the terms, please refer to [Terms of Use](#terms-of-use). The [Introduction](#introduction) section does not form part of the terms.**
+
 ## Introduction
 
 The founder of CherryGrove, [LJM12914](https://github.com/ljm12914#:~:text=It%27s%20a%20shame%20of%20open%20source%20to%20allow%20unrewarded%20commercial%20use.), don't like the situation and the definition of open source projects being used for commercial purposes without any compensation to the original developers:
@@ -8,12 +10,18 @@ The founder of CherryGrove, [LJM12914](https://github.com/ljm12914#:~:text=It%27
 >
 > LJM12914
 
-#### So CherryGrove is a source available project. CherryGrove is NOT an open source project, and LJM12914 thinks this is NOT the fault of CherryGrove but the fault of open source definition's high expectations of human society.
+#### So CherryGrove is a source available project. CherryGrove is NOT an open source project, and LJM12914 thinks this is NOT the fault of CherryGrove but the fault of open source definition's unrealistic expectations of humans and human society.
 
 CherryGrove is dual-licensed under [PolyForm Noncommercial License 1.0.0](https://polyformproject.org/licenses/noncommercial/1.0.0) and a commercial license. The PolyForm Noncommercial License 1.0.0 is a source-available license that allows you to use CherryGrove for non-commercial purposes, but requires you to purchase the commercial license for commercial use. The commercial license allows you to use CherryGrove for commercial purposes, including selling your own content packs and modified versions of CherryGrove.
 
 For more information about the explanation of the license, please refer to [FAQ](cg/faq#licensing).
 
+NOT AN OFFICIAL MINECRAFT PRODUCT. NOT APPROVED (and probably won't be approved) BY OR ASSOCIATED WITH MOJANG OR MICROSOFT. :)
+
+Minecraft® is a trademark of Microsoft Corporation.
+
+Every use of any trademark in this documentation is for identification purposes only and does not imply any affiliation with or endorsement by the trademark holder.
+
 ## Terms of Use
 
 CherryGrove copyright (c) 2025 CherryGrove Contributors.
@@ -84,21 +92,21 @@ You must not use the CherryGrove name, logo, or any other trademarked material i
 
 Notwithstanding the project's PolyForm Noncommercial License 1.0.0, the licensor grants you an irrevocable, worldwide, non-exclusive, and royalty-free permission to record, capture, store, copy, modify, transmit, distribute, and publish screenshots, videos, logs, journals, live streams, and world data produced by CherryGrove and to monetize them through any means, provided that the content is not used to create a commercial product or service that competes with any products or services offered by the licensor.
 
-This exception does not grant you any rights to use the CherryGrove name, logo, or any other trademarked material in a way that suggests an endorsement or affiliation of you with CherryGrove without prior written permission from the licensor.
+This exception DOES NOT grant you any rights to use the CherryGrove name, logo, or any other trademarked material in a way that suggests an endorsement or affiliation of you with CherryGrove without prior written permission from the licensor.
 
-This exception does not grant you any rights to use any data, code, or other materials that are part of, or produced by a content pack. Content packs are subject to their own licenses. You need to follow the corresponding license if you want to use, copy, modify, distribute, or publish any data, code, or other materials that are part of, or produced by a content pack.
+This exception DOES NOT grant you any rights to use, copy, modify, record, distribute, or publish any data, code, or other materials that are part of, or produced by a content pack. Content packs are subject to their own licenses. You need to follow the corresponding license if you want to use, copy, modify, record, distribute, or publish any data, code, or other materials that are part of, or produced by a content pack.
 
 ### User-Generated Content, Liability and Takedown
 
 By transmitting, distributing, or publishing any content pack, or other user-generated content through CherryGrove or related services, you represent and warrant that:
 
 - You have all rights needed to use, publish, and distribute the content;
-- The content does not infringe IP, privacy, or publicity rights; does not contain malware; and complies with our Acceptable Use rules;
+- The content does not infringe intellectual property, privacy, or publicity rights; does not contain malware; and complies with our Acceptable Use rules;
 - You will comply with all applicable laws and marketplace rules where you take actions related to the content.
 
 You fully understand that you are solely responsible for any content you transmit, distribute, or publish for CherryGrove. CherryGrove contributors are not the publisher of any user-generated content and have no obligation nor ability to review or monitor any user-generated content.
 
-TO THE FULLEST EXTENT PERMITTED BY LAW, CherryGrove contributors AND ITS AFFILIATES **WILL NOT BE LIABLE** FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, PUNITIVE, OR EXEMPLARY DAMAGES; OR FOR LOSS OF PROFITS, REVENUE, DATA, GOODWILL, OR BUSINESS INTERRUPTION, **ARISING FROM OR RELATED TO USER-GENERATED CONTENT FOR CherryGrove**, EVEN IF ADVISED OF THE POSSIBILITY.
+To the fullest extent permitted by law, CherryGrove contributors and its affiliates **WILL NOT BE LIABLE** FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, PUNITIVE, OR EXEMPLARY DAMAGES; OR FOR LOSS OF PROFITS, REVENUE, DATA, GOODWILL, OR BUSINESS INTERRUPTION, **ARISING FROM OR RELATED TO USER-GENERATED CONTENT FOR CherryGrove**, EVEN IF ADVISED OF THE POSSIBILITY.
 
 We may preserve and share information with authorities if we believe it is necessary to comply with the law, protect our rights or property, or prevent harm to others.
 

docs/cg/releasing/packing.mdx

@@ -0,0 +1,8 @@
+# Events
+
+Contrary to direct-call functions, events are "events" that:
+
+1. Happens sporadically and may not happen at all. You cannot predict when or whether they will happen.
+2. Are globally recognized.
+
+These two properties make events very different, especially the second. We need to 

docs/legal.mdx

@@ -1,2 +1,28 @@
 # Getting Started
 
+## Execution Flow
+
+CherryGrove uses two paradigms in pack system: direct-call, and event-driven. Direct-call is for things that will happen deterministically, like loading pack, generating terrain and periodic events. Event-driven is for things that may happen but are not guaranteed, like player actions, block events, and network events.
+
+Every pack will has the following lifecycle:
+
+1. When a world is opened, CherryGrove will read `world.cgb` to get the list of packs used in the world, then build a dependency graph. Then, each pack's `onFirstLoad()` function will be called once.
+    - Pack should finish initialization in this function. This is expected to be a big operation.
+    - Not all packs in the world will be firstloaded in this phase. CherryGrove will try to load as few packs as possible that can satisfy player's vicinity. Please set `config.alwaysLoad` to `true` if you want a pack to always be loaded.
+2. When a player joins the world, each loaded pack's `onPlayerJoin(player)` function will be called once for that player.
+3. When a player finished join operation, each loaded pack's `onPlayerReady(player)` function will be called once for that player.
+4. When a player leaves the world, each loaded pack's `onPlayerLeave(player)` function will be called once for that player.
+
+```mermaid
+graph LR
+    A[Join World Operation]-->B[Read \`world.cgb\`]
+    B-->C[Get Pack List]
+    C-->D[Search for Pack Position]
+```
+```mermaid
+graph LR
+    -->E[Load Pack Manifest]
+    E-->F[Check Dependencies & Incompatibilities]
+    F-->G[Build Dependency Graph]
+    G-->H[Load Packs]
+```