ehrumsey/isuckatcode-pages
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vault backup: 2025-03-25 10:42:56
All checks were successful
Update pages on webserver / Update (push) Successful in 5s
Details

Browse Source
This commit is contained in:
themodernhakr 2025-03-25 10:42:56 -05:00
parent 723cb5723c
commit bcc8891fb2
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Minecraft Datapacking/When Two Macros are Faster than One.md
View File

@ -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. 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 # 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. 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 ```vb