Prototype Automated Spawner

Good Morning from my Robotics Lab! This is Shadow_8472, and today, I am going over my completed pure ComputerCraft prototype automated spawner. Let’s get started.

I now have a turtle program I’m mostly, but not completely happy with. The notepad++ doc I originally coded now has the bugfixes I missed while parallel coding, but there’s still a bug when the program is deployed across many turtles. As of this writing, I have yet to look into it, but it’s simple enough to repair for a functional prototype.

I’ve turned my attention to the other two programs. I have a program to attack the gathered mobs, and it works at about 98% for a pretty heavy load, but it’s sloppily coded. I will be reworking it before publishing. When will I publish? I honestly don’t know. Whenever it’s done. At this point, I doubt I have anyone waiting on it, but at the same time, if I did, I’d be asking for help.

Long story short, I’m focusing on a program to filter out matching items before the attack program. Already, I’m considering potential benefits of making a custom library. One function, itemOut(), should be useful for a lot of turtle programs. As long as I use the same variables it depends on, I can just copy it into each program. A library would let me just access it without having to have it in each program. With a little modification, I might even be able to write some code to read a comment in the header and get library version numbers… and with a little expansion, I could setup a software update system.

Unfortunately, that neat idea is unlikely to save me any time. I don’t think it’s likely to happen unless I come back to ComputerCraft in a while. I want to get back around into more real world applications some time here.

Getting back on topic: the sorting program. I’m trying to recycle as many of my ideas for the loot repair program as possible. I started with the getState-action structure. As mentioned earlier, itemOut() is exactly the same. I do have an evalItem() function in both programs, but I have no desire to try and reconcile the two. Even if there were a way to make a unified evalItem() function, getState() itself must be different; the two programs have different possible states. Of course, good programming gives you a “control panel” of variables to edit.

Final Question: For anyone who knows: What is the best tutorial for Gazebo?

Leave a Reply