-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
This is a known issue, but not much can be done to solve it. When there are so many turtles running, sometimes the turtles do not detect eachother properly and thus think they are at position 1,1. This is a problem with Minecraft (or CC:Tweaked) itself, and is not something I can fix.
However, there are some things that can help mitigate this issue:
Sometimes this issue can be a one-off, and resetting the turtles then retrying the initialization can fix the issue.
If the issue persists, try initializing with the --reset and --slow flags.
This will slow down the initialization process significantly, which can help
with server lag, which I believe is a contributing factor to this issue.
Note
Usually the only problematic turtle are the ones that are erroneously labelled
1,1. The turtles below and to the right of that turtle will pick up the
problematic turtle's position and set their position ("correctly") based off
of that turtle. You do not need to manually set up all of them.
Caution
This method does not work with horizontal Turmitors, do not use this method for them.
If the issue still persists, mark the problematic turtles however you want, and note down what position they should be at in the array. Then, reset the turtles using the initialization program with the following flags:
initialize --reset --stop
This will reset the turtles, then stop them from running the full initialization process. You can then manually set up the problematic turtles by running the following command on each problematic turtle:
disk/set_position.lua x y
Where x and y are the position of the turtle in the array. For example, if
the turtle should be at position 3,5, you would run:
disk/set_position.lua 3 5
After you have set up all the problematic turtles, you can then run the
initialization command on the controller again, without the --reset and
--stop flags.
Open the UI of one of the turtles and check if it is actually running Turmitor, and is not just at the shell "homepage", i.e:
CraftOS 1.9
This is a message of the day!
> _
If the turtle is not running Turmitor, try just rebooting it (hold ctrl+r or press the power button on the left side of the UI twice). If it loads into Turmitor now, have your server computer restart all the turtles.
If they still are not running Turmitor, it is likely that they are not connected to the disk drive. Ensure the network cables you have set up run to a disk drive, and the modem on the disk drive has been right-clicked (it should have a red ring in the center).
If the turtles are running Turmitor, but are not responding to commands, it is likely that the network cables are not connected properly. Ensure that the network cables are connected from the turtles to the server.
If the turtles are running Turmitor, and the network cables are connected
properly, but the turtles are still not responding to commands, it is likely
that the turtles are throwing errors when they receive commands. Check the
server's log for any errors that the turtles are throwing (and ensure you are
running TurmitorServer.listen_for_errors in parallel with your main program).
If you are getting an error and you don't believe it is your fault, please report it as a bug on the issue tracker and I will try to fix it as soon as possible. Please ensure you are logging both turtle errors, and that you are logging in debug mode, then include all relevant log files.