Minecraft save-all timer

Question

I have recently found that my MC world does not auto-save (Don't answer on how to do that), so I have to /save-all every 5 minutes or so.

However, I have created a timer hooked up to a /save-all command block. Note that all repeaters are set to max delay.

Basically, what happens is, there is a redstone signal passing through the repeaters. When it reaches the end, it hits out a command block and loops around back to the starting which goes through the timer again.

I have timed this as 2:24.

Is there a much efficient design to the timer or any part of the structure?
Is there also a way to increase the time without changing a major part of it?

Please don't suggest any latchology as I am terrible at it.

Answer 1

You can vastly improve the performance of your times using MATHS.

You can see the principle outlined in another answer (this answer deals with redpower timers, but the principle is the same, you just need to do it with your vanilla timers instead). All you need to do is set up multiple timers, like the one you have there, but with coprime numbers of ticks (No common denominators).

AND the outputs of these timers and you can multiply the time your timers take very effectively.

Answer 2

Etho, SethBling, and MinecraftAddict have all demoed long period clocks using hoppers and comparators that were added in 1.5.

I'll explain Etho's design since it's fairly simple. Set up an RS-NOR latch using the new block of redstone: put down two pistons facing each other with a two block space in between, and then plop down a redstone block. Cap off the ends with just some redstone dust. These are the inputs for the latch.

One one side of the RS-NOR latch, put down two hoppers feeding into each other. Then place comparators coming out of the hoppers next to the pistons, and have them power a block.

When the hopper has items, it'll power the block, powering the redstone dust, powering the piston. When first starting, you'll put items into one hopper (H1), and the other will be empty (H2). Since H1 has items, its piston is powered, pushing the redstone block next to H2. H2 is now powered, so it can't empty its items into H1. H1 empties all of its items, causing its piston to become unpowered. The H2 piston extends, causing H2 to become unpowered and H1 to be powered. Items now flow back to H1.

You can pull your clock signal from one of the two spaces the redstone block will be to power your command block, or just put your command block right next to it.

In all, the clock is 6wx2dx1h, plus outputs. Much smaller and less expensive (although expense doesn't matter in creative) than your current setup.

There's also some details about this type of clock on the Minecraft Wiki.

Answer 3

there's an incredibly simple 5 minute timer. (If 5 minute is the real requirement.)

5 minutes is the time it takes for a dropped item to decay.

So, this timer below very nicely and exceptionally reliably. It does require "feeding" (note the hopper in the foreground...) but you could easily attach it to a item generator (sugar cane farm works nicely).

Answer 4

This is sethbling's video about command block timing.

What you need to do is copy this design exactly except:

1. Forget all about the "Timing" objective. This contraption will be running all the time.
2. In the two command blocks that handle the timing, make sure that there are no arguments that have to do with the "Timing" objective.
3. Add the following device to the clock:

Key:

Numbers = Command Blocks

-> = Repeaters

^ = Comparators

_ = The line from the clocks

This is the system:

_ -> 1 ^ -> 2 -> 3

1 = testfor @a[score_min_Time=(Your time in tenths of seconds)]

2 = save-all

3 = scoreboard players set @a Time 0

That should be good.