227 posts
Germany
Posted 27 December 2014 - 05:33 PM
Hey guys,
I'm currently working on a rebuild of the Maniac Sorter from gezepi - this time with autocrafting and such stuff. It'll basically be like Applied Energistics, but with ComputerCraft and much cooler :P/>
That would also mean that it's cheaper and crafting recipes would be easier to implement ( they are just tables with either items or item groups, which act like the forge ore dictionary ).
The user would also be able to manage all the items in the system - that means giving them certain display names etc.. I'm still kinda unsure about letting the user do everything manually, as it'd be a hell of a work to get all your custom item ID's in the system. The reason for that is the fact, that all items have their own internal names in the system, as some items, e.g. wooden planks, share the same item name, but have different damage values.
Enough of that now - if you're interested in this, just answer the question in this thread :)/>
Now for my question - do you have any better ideas for registering the item amounts in the central server? For explanation: the items are stored in adjacent chests of multiple turtles - each with 5 storage and 1 exchange chest. The whole system is going to be 'cloud-based' - meaning that most of the information is stored on the central server and e.g. the crafter, terminal or mobile terminal can gather all the data needed from just one server.
My idea for now would just be, that the server, on startup, creates a list with all the turtles in its network and then sends the command for getting the item values from the turtles ( I've created a custom modem protocol for this ).
This way the server can keep track of which turtle has actually already sent its item values and after a timeout throw all the turtles out, which haven't submitted their item values.
The protocol already deals with message duplication - basically the same way rednet does.
I'd also be interested in experienced programmers, who are willing to help with this ( probably ) huge project.
The fact, that server and client ( storage module, crafting module etc. ) rely on each other, makes cooperation even more important.
~wieselkatze
I'm currently working on a rebuild of the Maniac Sorter from gezepi - this time with autocrafting and such stuff. It'll basically be like Applied Energistics, but with ComputerCraft and much cooler :P/>
That would also mean that it's cheaper and crafting recipes would be easier to implement ( they are just tables with either items or item groups, which act like the forge ore dictionary ).
The user would also be able to manage all the items in the system - that means giving them certain display names etc.. I'm still kinda unsure about letting the user do everything manually, as it'd be a hell of a work to get all your custom item ID's in the system. The reason for that is the fact, that all items have their own internal names in the system, as some items, e.g. wooden planks, share the same item name, but have different damage values.
Enough of that now - if you're interested in this, just answer the question in this thread :)/>
Now for my question - do you have any better ideas for registering the item amounts in the central server? For explanation: the items are stored in adjacent chests of multiple turtles - each with 5 storage and 1 exchange chest. The whole system is going to be 'cloud-based' - meaning that most of the information is stored on the central server and e.g. the crafter, terminal or mobile terminal can gather all the data needed from just one server.
My idea for now would just be, that the server, on startup, creates a list with all the turtles in its network and then sends the command for getting the item values from the turtles ( I've created a custom modem protocol for this ).
This way the server can keep track of which turtle has actually already sent its item values and after a timeout throw all the turtles out, which haven't submitted their item values.
The protocol already deals with message duplication - basically the same way rednet does.
I'd also be interested in experienced programmers, who are willing to help with this ( probably ) huge project.
The fact, that server and client ( storage module, crafting module etc. ) rely on each other, makes cooperation even more important.
~wieselkatze
