There is no code that exists that will get you turtles to not stop when you log off then back on. This is an absolute rule, no way of getting around it.
What you CAN do however, is store variables in you turtles so they know what position they were in when they shutdown, and then they can pick up where they left off.
This requires a fair bit of clever programming however, and is not something that you can just 'add' in to your programs to make them 'restart proof'. This is especially so if your program is complex to begin with.
Just to give you an idea of what is involved, I've just written a persistent movement API for my turtles which can be found here: http://pastebin.com/RbBiLkh3. When I use the API it saves the turtles locations to a file, which can then be read when the turtle boots up again when the server restarts. This API is the easiest and most basic part of writing a persistent program (at least it is for me anyway). The harder part is making my quarry program smart enough to be able to understand this information...
What you CAN do however, is store variables in you turtles so they know what position they were in when they shutdown, and then they can pick up where they left off.
This requires a fair bit of clever programming however, and is not something that you can just 'add' in to your programs to make them 'restart proof'. This is especially so if your program is complex to begin with.
Just to give you an idea of what is involved, I've just written a persistent movement API for my turtles which can be found here: http://pastebin.com/RbBiLkh3. When I use the API it saves the turtles locations to a file, which can then be read when the turtle boots up again when the server restarts. This API is the easiest and most basic part of writing a persistent program (at least it is for me anyway). The harder part is making my quarry program smart enough to be able to understand this information...