rjs232323

Ah, understood!  Thanks

Someone was talking about this on the IRC about the JS architect.  It has captured my interest.

Could you clarify more on the no memory/ cpu management?  Without it, server and client can't sync together properly?

I do belive this is a great idea! But what if the person making the robot decides to be "smart" and make a 1x1x1 Robot that is unrealistic? How will it render tools? How will it render parts that it has installed? Besides a couple flaws this idea would be great to add.

(With drones this might not be a good idea at all, because they are entities)

You make good points there. That would totally take lot of coding to implement rendering for tools and parts too.  I'm not sure what would be wrong with 1x1x1 robot?  It probably would be hard to see but its name would still show up on top of it, no?

Hm, perhaps instead of making custom shell, the shell could be simply painted on top of it instead? Or maybe disable the rendering of tool and parts completely when using custom shell.

This thought came to my mind and well I would like to share it since I think its really useful suggestion.  Here goes: by using 3d printer, you could enable the creation of custom shells for robot.  Imagine personalizing the robots by their duties.  A mining robot with the skin of cobblestone and farming robot would go with the appearance of tilled dirt or leaves for timber robot.  I dont know how hard to make this but it would enhance the use of 3d printer for robots (perhaps drone to, not sure.)

The assembler could have one more slot as shell/skin slot where you can insert 3d printed block there and it would assemble the robot with based on the shape of the 3d print blocks along with its parts.

While I'm still working on ironing out bugs and implementing new features: here are the usecases that are now possible for registered devices when they're online and chunkloaded:

1. Access to your registered device globally. You can terminal into them as if you're using Lua directly altho with tiny small changes.

2. Connect two or more different network together. Got multiple bases across many servers? make a group and select machines to join that group. Those machines in a group will be able to see each others as modem events regardless dimension, or server enviorments. Modem events stuff may change, I'm still tinkering around though. This means your machines could be able to communicate to any others machines across multiple minecraft servers, and beyond (imagine Opencomputers connecting to your smartwatch or your phone!)  ^{_{Imagine that kind of stress upon Jalopeno!}}

3. Opencomputers could render interactive webpages as if they're webhosting! You could log in and check on your reactor's health online with HTML5 or canvas drawing objects, and be able to interact with them that will relay back inputs to your OpenComputers machines real time. Your OpenComputers machines would have to be able to fetch Javascript files to make this possible.

4. Microcontroller are also supported. You will create a EEPROM and configure it and finally to be inserted into them. They will log in automatically on power.

5. Jalopeno notify you when your machines enter online/offline states.  This way you can see what's functional or not across your domain.

I'm guessing to release this program by next week or so, on github as source codes and also standalone nodeJS program to execute. 

Hello fellow OpenComputerians, today I want to tease you a little with my mouth-watering idea(or should I say soon-to-be-tangible toy?): Jalopeno.

Yes, indeed, you saw that misspelled word right. Blame it on the jalapeno I chewed! It sizzled my brizzle. Think of it as a central station to manage all of your devices in one place, specifically all connected devices in a single website. From website to your devices, you could remote access them. You could deliver Lua's codes directly to your devices. You could paint your tiny silly screens directly from the websites. You could track errors. Your devices could communicate among others. Perhaps so much more!  How, you say? Socket systems, powered by a single instance of Nodejs using Websockets, TCP sockets, and a HTTP protocol.

At this point, it is still in development and is in no shape to showcase it yet. I would like to share it when I'm done coding the backend as well as the frontend of Jalopeno. The idea is that you would install this special tiny program on your machines using internet card and pastebin command to register your device online. Once you do that, then you can hop on the website and log in to see all the contents it has to offers for your registered OpenComputers devices.

I plan to github it all for open source, for a ludicrous-deep cost of nothing. Good for those who want to host this website privately or publicly for themselves. _{I expect my codes to be dirty, engima-ish, and brain-rambling logics when I release Jalopeno to github *giggly*.}

-rjs232323 _{^{(also known as the developer of MineCanvas!)}}

_{^{Edit: Added Image}}