Ever tried to work with a bunch of different properties when making a complex system and just get completely overwhelmed? This guide can help you!
We’ve all had that time when you think you just finished creating a super cool system, and you test it, but it doesn’t work. Now you have to go through all of your system and check every single block and property. This guide will show you how you can speed up the process!
Option 1
Game stop checkpoint
When trying to find the glitch, you might only need this system. Just go through your system, and add a broadcast, whether it be using block code, or a trigger, that ends the game. You should only end the game if the system shows that it is working.
For example:
Let’s say my goal is to get “Variable 1” to 4 and “Variable 2” to 12. However, it doesn’t seem to be working. Let’s use an end game checkpoint to try to find where the issue is.
I’ll set up an “End Game” device that ends the game when receiving on “End game”.
Now let’s add in the checkpoint to see if we’re successfully setting “Variable 1” to 4.
When we run the block, the game ends, so we know that that’s not the problem. So now, lets see if “Variable 2” gets set to 12.
And when I run the block, the game doesn’t end. Now I can see my issue and fix it.
Now when I run the block, the game ends, which means I can remove the checkpoint!
You might be thinking, Wait, why will I ever need this for these types of blocks? It’s obvious what was wrong with the code. And you’re right! This code was meant to be simple to understand, but this is mainly designed to work better with more complicated systems, especially ones with a ton of different properties.
Option 2
Notification tests
Notification tests are a great way to visualize text, numbers, and properties. Here’s how to set it up:
Property:
Notification:
Now, this option, unlike the other one, requires [1] block code to function. This works best for when you’re working with a lot of data. I recently used this system trying to decode the new PlayerID block. Here’s how I did it:
I was attempting to see if id remained the same length at all times. Here’s what I got during the test:
I’ve also used this for more complicated systems with a bunch of different properties to see if everything was working properly.
If you use these 2 simple systems correctly, it will help you out a ton when squashing bugs!
You found the easter egg!
What you should do: reply with a nice response telling me what you love about this guide, or what could be improved, and leave an egg emoji at the end of your reply! Here’s a little secret. You know my player tracking guide? I’m finally fixing it! Shh, don’t tell! ↩︎