How to Optimize Your Datapack 

This is a very useful video, and a lot more in depth than I expected! Somehow I kind of overlooked the schedule command until now and forgot about its existence 😅

i thibk, this is the only video in youtube how to optimize ur datapack

mumbo: *sees tip 1* mumbo has left the chat

didn't know i should be using AEC's instead of armor stands... that explains why one of my maps with 250 armor stands was unplayable :P

Me: *makes a virtual computer using a datapack that runs extremely fast* Also me: *likes to use redstone in his adventure map*

Thank you for these! Immediately started noticing the performance improvements.

Amazing thank you so much. That AEC tip is priceless. Thanks again.

Great video! Something I learned that is useful when you need to check entities/items is to give them a specific tag, so they won't be checked again and this will improve performance, since the selectors checked every tick will decrease.

this saved me from a very laggy datapack. the 'chunking' of functions has helped me immensely, especially with bosses.

Function trees is basically how I made the MC64. The datapack is >90% function trees xD

Thanks for making this video :)

Wow I never thought of a self rescheduling function for a clock. Before, I would just give a fake player a score and keep resetting it every second while executing different parts of the datapack based on the score

Thank👏you👏so👏much👏!

Thanks for the useful tips :D

Thanks for this very informative video!

Thank you so much. It really helped me.

Underrated

Great points! A few things worth mentioning: Take care when using the /execute command to run functions. executing a function as multiple entities multiplies the number of commands the function uses by the number of entities executing it. This means that doing this could cause the chain length to grow beyond the limit, which could have unintended consequences. AECs have a maximum lifetime, so if you have entities that your datapack requires to be persistent, it is usually better to use armour stands (2,147,283,648 ticks is about 3.5 years, but it's always good to be prepared). Otherwise, AECs are indeed better.

One of your best videos I think

Thank you!

Wish I found this earlier, will recc to friends

There is a bunch of stuff I will definitely try. I think me letting all my timings scoreboards do their own thing falls in two of these categories.

Top 10 useful advices

To see AECs I normally use the "composter" particle on repeat, but it's just for debugging and stuff.

i would love to see an update to this. i know a few things has change such as the new entity for markers is the marker entity (witch will mark a posision)

just realized i'm gonna have to rewrite my ENTIRE datapack... oh shit...

How to Optimize Your Datapack? Learn Scarpet and use it!

I had a *Datapack* where [I was making "invulnerable blocks" (-This was not what it was about.) by putting *Falling Blocks* in the location of *Barriers* so these blocks are impossible to mine.], but I noticed the *TPS* slowly lowering if I got far away from these "invulnerable blocks". If I got close again after having low *TPS,* the *FPS* would spike to zero. Using *"say @e",* the *chat* would return "Falling Block, Falling Block, Falling Block ...". Using *"/kill @e[type=falling_block]",* the *chat* would return "Killed [A 5-digit number of] entities.". I thought *Falling Blocks* _always_ lasted 1 *tick* (-Or 0.05 seconds).

0:53 mumbo jumbo please look away.

The problem with the schedule command is that if the player quit during the delay between a function and another, the delay will reset. Idk if it's intended or it's a bug, but it's a serious problem. For exemple, i want a falling_block to not despawn after 30 seconds, so i could schedule a function every 25 or so seconds to optimize, but if the player just join the world for a few second the commend cannot run, and the falling_block will despawn the next time the palyer join. Also, now they added the marker entity which is really lag friendly, but it misses a lot of useful things like the possibility of having passengers, so area cloud effect could still be useful. The problem? It seems a spawned cloud area effect cannot be teleported, in any way

Due to the short circuiting of selector conditions, would you not need to place the type at the front instead of the back of the list in order to prevent the processing of tags or is this a special case based on the nature of the particular condition? What I wouldn't give for comprehensive documentation on details such as this.

I have stayed away from using schedule for repeating commands because I am concerned that if a tick goes wrong somehow, the whole repeating functionality is ruined. Never been able to really test its reliability, so my question is: have you ever had issues with the schedule not working? Thanks!!!

Could you please make a whole video on "how to check blocks" because I am tired of checking all different blocks in Minecraft to find out what block it is and I don't know how to do the method you told me in this video

Which sublime syntax highlighter are you using? I got one through the package manager called MCC or something, but it's outdated.

in 1.16 and over you can use marker entity instade of AEC

Really love your videos and your tips are very useful. But how can you summon area effect cloud that don't disappear like 8:14?

I got a quick question, I have a function for sound repition in my Dp which executes 20/s every tick. It's basically like: -execute playsound if score=1 -execute if score @s =1 put score @s 200(lenght of the sound) -scoreboard player remove @s score 1 Would Making a schelude for that be much more Performance efficient or negligible?

Do redstone blocks affect the proformance in my world, because i have a couple redstone blocks that appear/disapear once a player is in a zone?

So in essence, if I plan to have dozens of carrot on a stick items that will do abilities on right-clicks, just making a function with this long list of detections for all the various items and then adding a if entity @a[scores={active=1..}] (where "active" is the right-click detection) to my tick function, that will already help a lot yes? Since I'm only executing the long list of detections if a player right-clicked the carrot on a stick?

I remember mojang saying that selectors parse and interpret orderedly. So tag, then type @e[tag=x,type=y] would still test tag first then type, however @e[type=y, tag=x] would do type then tag. Is that true?

Hi! Thanks for the tips! I have a question, is there an easier way to make custom blocks than armor stands? Thanks!

How did you now always what i need?

Markers are another great solution instead of AECs

i'm completely new to making datapacks, like i've never touched a function how do i transfer command blocks to a data pack, like i'm making a kit, for example, if a player sneaks for five seconds, they become invisible but as soon as they stopped sneaking, or they moved an inch, the invisibility goes away and you have to sneak again for five seconds to be invisible

i need to know what are your plugins for Sublime text, i need that syntax highlighter

If I summon ~10000 *Area Effect Cloud entities,* it still lowers, the TPS _severely._

/schedule doesnt really seem to work, its weird but it doesnt execute the commands...

How to optimize loot tables for score based loot replacement

Why not use markers instead of area of affect clouds

Also with selectors i use this lines in tick.mcfunction: execute as @a at @s run function test:as2a execute as @e[type=!player] at @s run function test:as2e In as2a you run commands as players In as2e you run commands as entities So you dont must to do in tick: As @a[tag=1] run function 1 As @a[tag=2] run function 2 As @a[tag=3] run function 3 Etc... You just use if entity @s[...] run ... in all this files) CloudWolf, is this good?

whats your outro? its fire

How do I create a permanent invisible AEC?

Well I've been using this thing for a while. And I wanted to ask if it was a good idea or not. I run a scoreboard on a fake player that goes from 1-20 Then I run any command(that i don't need to be instantly checked) if it matches 1. Then for my next command i check if it matches 2 Then for my next command I check if it matches 3 and so on... Until I reach 20 (I use way more than 20 commands so it cycles over a few times) This way, the work done per tick is not super intensive. Each task done is different per tick every 20 ticks pretty much what is done in this video ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-Jrps_3_dufQ.html

Mhhhh.... welll let’s just restart....

Spooky 666 likes

1st and 4th

third

Totally first.

My opinion: That "programming language" of DataPacks is terrible and unnecessarily chews up lot of performance by its nature. You have to constantly hack the system to get more than a "another 10 useless crafting recipes"-pack out of it. - The execute command, which is some kind of a for loop expensively iterating through the entity array most of time, checking each entity against a given condition. - No proper if...else command (you have to abuse the execute command for that, probably two times if you need an else branch) - No { and no }. The only way to have blocks with multiple comands is cramming them into another mcfunction file (which leads to lots of them with more or less unnameable subroutines) - No feasible way to have function parameters, making Interacting between two different entities sometimes is a nightmare. - No proper variables. You have to run execute again and again or abuse the scoreboard or the nbt data for that. - The code becomes unreadable quickly. Using brainfuck is easier. I prefer the good old redstone way over this whereever possible. Mojang, please add at least these features, even the first computers had at least these: if/else, goto/gosub, variables and block statements ({} or python-like indentation)... and please: custom nbt for the crafting result and a way to add custom blocks without sacrificing existing blocks or abusing amor stands and mobspawners (which increases the entity array where the execute command frequently queries from).