Update documentations

Brilliance Datapack/TODO.md

@@ -4,6 +4,9 @@
 - Config Info "booklet" needs to be updated with the new force saturation level
   - Go into more detail on the Fresh Runs & Balance Changes in the config book.
 - Randomly determine TIME of day, instead of just day/night
+- Update Brilliance's main readme.
+- Add a config to LIMIT people from receiving logs. (atm it's freely available from the /trigger cmd)
+- Fix on_crown_acquired to not log EVERY crown but instead a total of crowns, once. 
 - Track embers DROPPED in dungeon
 - Track embers ATTEMPTED to be RELEASED.
 - Track treasure DROPPED in dungeon

JSON/scoreboards.json

@@ -3142,5 +3142,11 @@
         "target": "$dungeon",
         "category": "utility",
         "description": "Used to count how many names are inside a list of names."
+    },
+    "do2.config.mc.controlSummons": {
+        "auto": 0,
+        "target": "unknown",
+        "category": "unknown",
+        "description": "unknown"
     }
 }

docs/logging.md

@@ -1,4 +1,10 @@
 # Logging
+Brilliance logs almost all interactions with the game, and nearly everything that Brilliance does.
+<br>As you can imagine, this is extremely useful for debugging the game. It's easily accessible from the config room inside the dungeon. Alternatively running the command `/trigger do2.trigger.logs` can enable your logs.
+
+Since there is a very **large** amount of availible logs, the menu allows you to customize which logs you want to receive, split into categories and then additionally split into levels of priority. You can choose which categories and priority of logs you wish to receive. `1` being highest priority logs  and `0` disabling all logs.
+
+The menu in-game has it's own description of what level of priority will log, but the full completed list is accessible from this table below.<br><br>
 
 |  Log Category  | Level | Description |
 |:--------------:|:-----:|-------------|