I've just recently learned the basics of rednet programming, and I'm encountering an annoying problem.
I want to do a simple thing: I press a button, EXACTLY 'N' minutes later a signal is emitted, being N a high value.
The Delay function is the reasonable one, but the problem is that it works on ticks, and can only count to 255 ticks, which is about 12 seconds. If I wanted a timer to count 9 minutes, I would need to have 45 Delays. Not only it is impractical but also because the number of operations is limited on the PRC, I wouldn't be able to put two or three long timers there due to the lack of 'space'.
Using the famous Wave trigger + Counter is impossible because the Wave function doesn't receive an input, therefore it is "always running", just like an invisible wave that runs the moment you select it on the interface.
That will certainly result in imprecise timings, after all you will always press the button somewhere in the middle of the wave curve, never on the start nor the finish, so the signal will always come sooner or later than expected.
The Wave + Counter method is able to send signals with the longest timing of 255*(255*2) ticks apart, which is ~108 minutes.... but because the wave doesn't start when I press the button, the signal may come at 1 minute or at 109 minutes, depending on where it was when I clicked.
Honestly, I don't understand why can't we trigger a Wave using redstone or variables.
So, does anyone has a solution for this, or a suggestion?
Am I missing something, or the only option is to use a ton of Delays?
I want to do a simple thing: I press a button, EXACTLY 'N' minutes later a signal is emitted, being N a high value.
The Delay function is the reasonable one, but the problem is that it works on ticks, and can only count to 255 ticks, which is about 12 seconds. If I wanted a timer to count 9 minutes, I would need to have 45 Delays. Not only it is impractical but also because the number of operations is limited on the PRC, I wouldn't be able to put two or three long timers there due to the lack of 'space'.
Using the famous Wave trigger + Counter is impossible because the Wave function doesn't receive an input, therefore it is "always running", just like an invisible wave that runs the moment you select it on the interface.
That will certainly result in imprecise timings, after all you will always press the button somewhere in the middle of the wave curve, never on the start nor the finish, so the signal will always come sooner or later than expected.
The Wave + Counter method is able to send signals with the longest timing of 255*(255*2) ticks apart, which is ~108 minutes.... but because the wave doesn't start when I press the button, the signal may come at 1 minute or at 109 minutes, depending on where it was when I clicked.
Honestly, I don't understand why can't we trigger a Wave using redstone or variables.
So, does anyone has a solution for this, or a suggestion?
Am I missing something, or the only option is to use a ton of Delays?
Last edited: