-
Notifications
You must be signed in to change notification settings - Fork 22
RFTools peripheral support #158
Comments
I have some use ideas. |
@osmarks I have added your suggestions to the list |
Closing this for now, as it's rather become a "Here's every block in the mod" issue. If someone has a need for specific integrations, I'll happily add them, but as someone who doesn't use RFTools, it's rather hard to tell what actually needs to be added and how one'd expect to go about integrating with it. |
@SquidDev , could we re-open this one, since I think I will take a crack at it next? I'll start by looking over the various blocks and seeing what makes sense; basic meta like the 'infusion' level and owner for each block seems obvious, but some of the others, like programmatic control of the Composer and shape cards feels a bit over the top to me. I'll probably also contact McJty to get his input. On our end, how should I structure the packages for RFTools, RFTools Control, and RFTools Dimensions? |
I've reached out to McJty on Discord, though I haven't heard back yet. McJty has implemented OpenComputers drivers for the following machines, so I would imagine adding methods for them wouldn't be an issue:
Granted, some of that functionality may be redundant with our existing meta providers for power levels and fluids; we shall see. I will have to review the rest of the items, blocks, and TEs in the mods to determine what support makes sense. A side note, I dislike repeating lists for desired functionality, but I can't edit the OP, so 🤷♂️ I'll make due. |
Edited OP |
There are plenty of machines in RFTools that could be awesome peripherals, and I think to at least implement some of them a checklist could help with development:
The (no information yet) just says that I don't know how you could interact with these blocks via plethora.
I think especially modifying screens could be fun.
Stuff McJty already implemented in OC:
The text was updated successfully, but these errors were encountered: