Turtle peripheral persistance

Adding persistant data to a normal peripheral is easy, as they simply extend the TileEntity class. However, turtle peripherals don't have that option. All data saved in them is lost when the turtle gets unloaded. Commands scheduled through the issueCommand method are lost, too. So, my suggestion would be to add readFromNBT and writeToNBT methods to the ITurtlePeripheral interface. The data would be saved in a sub-tag of the turtle's own nbt tag. When it's loaded again, the read method would be called on the new peripheral object.

If a named turtle gets destroyed, the nbt saving mechanism could even be used to persist the peripheral data, too.

You can already do this using an item to store the information.

Er.. yes, but that is a very dirty way of doing this, you know? It would not so difficult to support this properly.

Good idea. Will see if can implement it for 1.3 port (as will be an API breaking change!).