Revival System [🟨]

[Bardy_2913]

@recalledMemories

Overall: 6.7/10
Add some more jokes and most importantly an explanation and your guide will be pretty good

The explanation may not have been the most obvious but

@Bardy_2913

The distance variable carries the distance. Then, if the distance was in between -1.5 and 1.5, and the true/false property was true, then set the true/false property as false, broadcast message on revival. Then, whatever you want to happen to the player when revived, is done when receiving on “revival.”

This is for the distance calculation

@Bardy_2913

So, now we want the property for revival coordinates to be updated upon the whole team [1] So for that, we’ll use a relay. All players in specific team. That same team.

Player Moves → Trigger Relay

And this is for the updating of the revival coords.

@Bardy_2913

So now we need some blocks to run upon that. All it does is set the current x and y values to the revival ones.

And this is the blocks for the coords

Some of the explanation things were before the actual step explaining what I was going to do. I still have to add some though.

---

@recalledMemories

Fun: 0/10
Add some humor! People don’t want to read something that’s as dry as a saltine cracker.

i was not in the mood for humor that day lol

---

@recalledMemories

Rarity: 8/10
Surprisingly this is a system that has only been done once before even though it seems common.

I saw one by leahciM but it didn’t make sense because you can’t tag people on your team.

'83 is tasty

---

---

@Here_to_help

One suggestion: instead of using a true/false property, you can just use a number property and use counters so you don’t have to use 500 memory just to make it true.
1 - true
0 - false
Make true by increasing.
Make false my restarting.

I’ll change it but for my system it’s better just because of organization + it’s with other blocks

@Here_to_help

@Bardy_2913

'83 is tasty

Woah woah woah buddy that’s a bit far.

I AM A PROUD EATER OF '83