Hello everyone and a warm welcome to this video. Today we are going to learn something new, although you might already be familiar with it. We will be discussing how to get the TPS in Minecraft. Okay, this is actually quite simple. The first thing you need to do is create a space for spectators. Good, now the problem is that due to the 1.192 or the 1.19 update, I can briefly show you the gaming screen. I’m not sure if Leon wants to intervene at some point, but he’ll have to bear with me.
So, in Minecraft, we have a system called TPS (Ticks Per Second). We can identify or retrieve the TPS using llamas. If I don’t have the right permissions, I can use the /TPS command. The normal command is /TPS colon AG. This shows us the TPS for the last minute, five minutes, and 15 minutes. The other command is /TPS from last one minute, five minutes, and 15 minutes. This is what is usually considered normal.
With llamas, we can check this. It works, but not perfectly. I will now activate the system and we can see a warning that the TPS is weak. However, it doesn’t bother us at the moment because we can perform a block update and let the technique work peacefully. But as you can see in the chat, the TPS is very weak. The TPS for one minute, five minutes, and 15 minutes is 15, 17, and 20. Sometimes, llamas refuse to rotate for unknown reasons. I have tried various things to solve this issue, but even block updates don’t help. This problem seems to be related to paper, as they likely have a certain limit. Minecraft has to calculate a lot, which may be the reason behind this issue. Currently, it is working fine, but we have experienced situations where llamas stop cooperating. However, with the new systems, this issue is completely resolved. The system is very compact and requires only two commands, theoretically.
Let’s go back to the test world. Here we can already see the observer block and how it slows down the redstone. This is the TPS. The TPS might have been affected by my low FPS, which is around 25. Even when I look up, the TPS delay is noticeable. But if I disable the system, we can see that the redstone blinks rapidly or not at all because I messed up. Anyway, we are back to the TPS 20, which is the usual default value.
Now comes the problem. Since version 1.12 or 1.13, we can use the debug buffer, which is crucial for this system. So, we only need two commands. First, we need to use /debug start and then wait. It doesn’t matter how long you wait, but I believe there should be at least a five-tick delay between the two commands. The next command is /execute nee execute as r=score_datas run debug_stop. Now we are back to the TPS 20.
If I turn on the state machine again and reset, start, and stop it, we can see that it lags. Minecraft was unable to execute the debug command in one second, but it took four seconds. This is very slow, resulting in a slow TPS. If we quickly manage to enable it again, it shows TPS 21. This number could even exceed 21, as I had experienced up to 100. This means that Minecraft is trying to catch up on the ticks it missed, and some ticks are lost while catching up. Those extra ticks are shown on the side, indicating that there are 21 ticks instead of the usual 20. If we execute the command again, it still shows TPS 21:120.
Now, if I enable it again, Minecraft will drop in FPS. Let’s see how much it drops. It can vary, but it depends on how bad the TPS is. If we speed up the TPS a bit and execute the debug command again, it still shows five. Let’s wait until Minecraft tries to catch up on the ticks it missed. It is now 40, then 21. Perfect!
Whether you execute this command every 20 ticks is up to you. It might help Minecraft catch up a bit faster, but I don’t think it makes a significant difference. Anyway, that’s it. This is the latest and improved TPS system. It does require commands, so you can’t build it in survival mode. However, you can use a data pack. The problem is that the starter pack likely doesn’t have the capability for this. In Minecraft, there is a rule that applies to open servers. If we execute /debug start, we can’t stop it with /debug stop. Normally, this debug command is specifically for Minecraft servers. Although we can try to switch to spectator mode, it doesn’t work. It seems that we failed to make it work because Minecraft has a permission limit. This limit applies to functions, and it needs to be set to at least three. In our case, it is set to three, which is crucial for everything to work properly. If it is set to two, you won’t be able to execute functions. So, if you want to try this, make sure your limit is set to at least three. That’s all from me. This is the newest and better TPS system, in my opinion. Although it requires commands, it cannot be built in survival mode. However, you can use a data pack. The issue is that the starter pack probably doesn’t have the necessary permissions for it. This is due to Minecraft’s permission limit, which I believe currently only applies to functions.