Been a while since I’ve made a guide, right? Anyways, I found out how to make this while making a map before losing motivation in approximately 4.6 seconds. Jokes aside, it’s time for the guide.
Materials:
- Lifecycle x1
- Relay x1
- Trigger x4
- Property x1
- Game overlay x1
Before you start, read the notes or you will NOT get this guide right.
Notes
- You need to set the property to a number property and to some value. Example:
- The relay isn’t necessary if you’re making a singleplayer game like me. Why does it matter? You can force players not to play with others/other tabs and it saves 20 memory. Sure, 20 is a small number, but it’s a number (and it’s still some memory).
- Make sure all the triggers you place down are:
-
- Not visible in-game
-
- Not able to be triggered by stepping on it
Steps:
- Set the lifecycle to game start and wire it to the relay set to everyone (event occurs → trigger relay). Then, wire the relay to a trigger (relay triggered → trigger).
- With the trigger that was just wired to a relay, wire the trigger to another trigger with a delay of 1 second (triggered → trigger).[1] Then wire the trigger with a delay to a counter (triggered → increment counter).
- Wire the counter to a trigger (target value reached → trigger) and wire it back (triggered → reset counter). Also wire the counter to another trigger (same settings as above).
- Time for the fun part! For the trigger that wasn’t wired back to the counter, add some blocks like this:
This will update the property for every game day that passes. - In the game overlay’s blocks, set the blocks like this:
- Wire the property to the game overlay (property value changed → hide overlay). Wire the property to a wire repeater (property value changed → repeat the wire pulse) and wire it back to the overlay (wire repeater receives a pulse → show overlay).
There might be some unnecessary things in here because when I was testing this, I noticed that the overlay didn’t update when the property was updated. So, I hid, then showed the overlay, being the simplistic self I am :D
Anyways, if you want to make a month counter, you’re going to need one more property and realize that you can actually edit device block code instead of deleting them all in a rage (perfectly describes me). Also read the notes here. It’s different from the one above.
Notes
- The property this time has to be a text property. Here’s an example:
- Eh, maybe a small block code warning for this part.
Steps:
- Go to the trigger that you used to update the day property (the one with the block code). Add another block under it with this:
This will make the month value turn into the next one based on how many days are in that month and will make the day value of the next month to 1.[2] - Go back to the game overlay and create a “create text with” block. Then, add this:
(Notice: There is a spacebar in the text block in the middle. It’ll make it look good). - (This step is optional). If you want to make the day have something like “June 5th,” then you can do this in the block from the step above. You need to check whether or not the day number is 1, 2, 3, 21, 22, 23, or 31, and set the text for that.
So yeah, that’s it for the month counter. Here’s the final result:
So yeah, that’s the day and month counter. Luckily, duplicating blocks existed, which really helped with step 3 of the month counter. What also helped with step 3 of the month counter is a brain. I replaced the image for it 4 times because I got it wrong 3 times and finally got it right on the 4th try.
Anyways, one final thing: Merry (early) Christmas!!!
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
