33 replies to this topic
#21
Posted 04 January 2013 - 03:51 PM
The sleep() function works by setting a timer event and then pulling it, so you can just use sleep for a clock (you shouldn't, though, you should use os.time() to get the world time). Pretty much all the turtle functions yield so they can pull their success events, rednet messages pull events to both send and receive...usually the problem that people have is how to avoid using a function that will pull a specific event type while discarding others they wanted to get.
#22
Posted 04 January 2013 - 06:09 PM
Thanks. I've been testing some more and it turns out sleep(x) is also a valid replacement for os.pullevent for things like static displays not to time out and halt. I had been using pullevent all along.
So a clock would be basically a loop with os.time() and sleep(x) (after all, the time changes only after a second or so) and that would do the trick.
So a clock would be basically a loop with os.time() and sleep(x) (after all, the time changes only after a second or so) and that would do the trick.
#23
Posted 05 January 2013 - 02:12 AM
Yes. But for an actually static display, you'd want to just run it once and have a startup file that ran the program in case the chunk got reloaded.
#24
Posted 06 January 2013 - 06:15 PM
The only problem is that computers seem to turn off when their chunks get unloaded and need to be manually turned on afterwards.
#25
Posted 07 January 2013 - 08:53 PM
They reboot, if they were on when they were unloaded. As long as you have a startup program that gets them back on task, they'll be fine.
There was a problem in older versions where monitors, once already placed in a large screen, didn't update themselves on reloading, so the monitor wouldn't work until a block was broken and replaced.
There was a problem in older versions where monitors, once already placed in a large screen, didn't update themselves on reloading, so the monitor wouldn't work until a block was broken and replaced.
#26
Posted 07 January 2013 - 10:58 PM
Been testing with the latest version and they do reboot if they were on when unloaded. Fantastic. It's just what I need
#28
#29
Posted 08 January 2013 - 07:06 AM
And Intel took so much flack for the early Pentium. Not that they didn't deserve it.
#30
Posted 08 January 2013 - 09:03 AM
I'd say WorldEdit would help, but the real challenge is to do it by hand.
In survival mode.
...Challenge accepted.
In survival mode.
...Challenge accepted.
#31
Posted 08 January 2013 - 10:56 AM
I think the real challenge is not crashing your game by doing it. And that's after taking into consideration that you'll need about 35.7 million chunks worth of redstone (depending on your luck) in order to make all those computers.
#32
Posted 08 January 2013 - 12:19 PM
This doesn't sound easy.
#33
Posted 08 January 2013 - 12:53 PM
Well the computer shouldn't crash as long as he doesn't turn them on. If he turns them on they will start ticking and lagging like crazy...
#34
Posted 08 January 2013 - 12:57 PM
Yeah, but you need to turn them on to generate the IDs, right?
If you just start with the making and placing, and keep that up for a couple of decades, computers and interfaces might evolve to the point where it would only take you another few years to get all the computers placed, and then you can turn them all on in a cascade using peripheral methods.
If you just start with the making and placing, and keep that up for a couple of decades, computers and interfaces might evolve to the point where it would only take you another few years to get all the computers placed, and then you can turn them all on in a cascade using peripheral methods.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users












