So
miningWorkerCode.lua and
odo.lua. I also see a
miningWorkerStarter.lua and
hutBuild.lua, which I link here in case they come up later.
My bet is on missed rednet messages. I've coded a similar sort of client/server setup, and I've found that sometimes, for reasons unknown, a message will either fail to get sent or fail to be received. The transmitting computer ticks along as usual but the receiving machine just doesn't get the message (even if I force the server to wait at least a second before replying). If using rednet.receive() without a timeout, as you are doing in minerWorkingCode, it'll eventually result in turtles simply halting with no errors in the terminal (which I assume
is what you're seeing - you haven't elaborated on that).
My solution was to set a time out for about five seconds and then attempt to message the server again if I hadn't received anything back. In short, you need to account for dropped packets.
Eg, rewrite something like this:
rednet.send(serverID,"mining_getTourchChest")
id,message = rednet.receive()
values = split(message,":")
for i=1,4 do
tourchChest[i] = values[i+1]
end
To this:
message = nil
while not message do
rednet.send(serverID,"mining_getTourchChest")
id,message = rednet.receive(5)
end
values = split(message,":")
for i=1,4 do
tourchChest[i] = values[i+1]
end
I don't think odo is affected by this, as you only use rednet for GPS positioning there. Would have to read a bit more of it. Again, knowing exactly what you mean by your turtles "shutting down" would be helpful. Do they give errors? Reboot? Or simply halt?