You can only get those from the end .Isn't there a bee that produces enderpearls? And a beealyzer peripheral?
*hides*
That's why I was thinking about a map. Get a few turtles, give 'em sand. Make em find a desert, and make 'em pick up anything in the desert that ain't sand. You'd get sandstone variants, sandstone slabs, bees, sand oils, cacti, wool... and blaze powder. Send everything home via enderchests (or something) (by the way, that's another problem, marking the enderchests up, setting frequencies on tesseracts is just as impossible) the rest should be just identifying.
As far as ender go, that's easy. Build a mobtrap. Pretty easy to build too, with great returns as well, once you mine out 128x. The problem is getting any monsters at all spawn without a player.
Too bad you can't give turtles water blocks so that they can detect water, that would make beach detection pretty simple.
There is an "easier" way to detect water (or oil, though), with a bucket, and trying to do a refuel on it to check if it is not lava.
But yeah, UU mater seems a fun route^^
Sounds great, got my own though. A neat little VPS which is using about 0,1% of the allocated resources xD.
The real problem would be the sheer amount of http requests. And I don't think that there's any way to mitigate that from our side. The best place to compress the packets would be the CC http api. And I dunno, this sounds like it could very costly very fast. God, I sure do love the idea though.
Yeah, but that means you'll have to build a big red-net network and will have to use turtle cripples. No crafty mining turtles, it's either wireless crafty or wireless mining.
I could start working on a back-end though. You could talk to the guy who did the http api.
Well, if that's the way it is, then I could theoretically move forward being okay with http spam. Cause I seriously don't want to use rednet. I ain't got that much time myself, got me own forums to run/develop.
But yeah, I might start workin' on a little back-end. Set up a database - that kinda thingie.
That's the problem, you can't really stack the requests. Mostly because if you stack them on the the turtle, then you're not saving anything, BUT you're risking losing some of the data. You need to stack the nearly simmulanteous requests from different turtles - a battery of turtles pretending to be a bore is a good example - which is why I'd like the guy who made the http api to add that to the api.I've got this vision of never playing MineCraft directly again because I'm too busy playing Turtle Played MineCraft. But that is entirely irrational.... Right? I hope so.
If we can avoid using rednet, yes, it will be a WHOLE lot more stable. Maybe we stack requests to every tenth of a second so we aren't polling the database every five milliseconds?
Mm, I'm going to toy around with networking turtles in game using rednet, to see if, perhaps, I can make it useful in any way at all.
I believe it's a bale.Swarm is just about the right collective noun for turtles, don't you think?