From bcc8891fb29be2ad66b263324f25511b1d786a26 Mon Sep 17 00:00:00 2001 From: themodernhakr Date: Tue, 25 Mar 2025 10:42:56 -0500 Subject: [PATCH] vault backup: 2025-03-25 10:42:56 --- Minecraft Datapacking/When Two Macros are Faster than One.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Minecraft Datapacking/When Two Macros are Faster than One.md b/Minecraft Datapacking/When Two Macros are Faster than One.md index ff3b97c..e089215 100644 --- a/Minecraft Datapacking/When Two Macros are Faster than One.md +++ b/Minecraft Datapacking/When Two Macros are Faster than One.md @@ -47,7 +47,7 @@ data remove storage test_namespace:test_namespace temp.keyword ``` Once the entry is found, it is stored in the `temp.result` storage, which can then be consumed by another function. -Now for the logic to do the actual array searching. Here, the performance hit of running macros is worth it as the alternative involves a massive number of commands to manually iterate over an array. As we'll see later when benchmarking functions, manual iteration is *really* slow. +Now for the logic to do the actual array searching. Here, the performance hit of running macros is worth it as the alternative involves a massive number of commands to manually iterate over an array. As we'll see later when benchmarking functions, manual iteration is *really* slow. Macros it is... # one macro Macros allow us to reach into our array and pick out an entry that matching value in the `string` property. This is something that I didn't realize (for some reason) and was pointed out by **PuckiSilver** and **amandin** on the Datapack Hub discord server. ```vb