A problem that im sure someone knows how to solve.

[runeking31]

On my server i am constructing a parkour style course with 4 separate stages that all need to be completed to get the prize. The prize is a diamond. The problem is i don't have unlimited diamonds and i need to figure out a way so that when a person completes the course and receives the diamond they are no longer eligible to receive another diamond when they complete the course again. My only thought would be a turtle script but i have no idea where to go with that. Please help.

 

[Quesenek]

You could mess with the player detector from misc peripherals. That is the only way I could see it being locked to only allowing one diamond per person since you cannot change your username.

 

[Dravarden]

you can use the player detector as said above + the admin block of tubestuff that clones items.

 

[Heliomance]

I'd have thought this type of project is best left until you're far enough in the game that you essentially do have unlimited diamonds.

 

[TangentialThreat]

If they're willing to rip apart your machinery to get at the diamonds there's no easy solution.

One relatively simple solution would be adding a timer so the doors only open once per Minecraft day or something do nobody runs it over and over. Again, this assumes they won't just break down the door - which implies you have WorldGuard or unusually civilized players.

 

[MinePlayer]

In order to protect the chest of diamonds, or wherever you store them in, you could just use warded stone or force fields. The only breach would be the place where you put the player detector, which is just one block tall, so a player can't get through. If you put the chest far enough from the player detector, nobody would be able to get the diamonds even if they break the player detector.
And the program in order to do that would be very easy. Just create an empty table, and every time someone clicks the player detector, check if his name is in the table and, if he is not in the table, give him the reward and write his name in the table. The only problem would be if the server resets, in which case you would need to write the table to a file, and load the file each time the computer reboots. That's easy too, but requires a bit more coding.