- Joined
- Jun 28, 2013
- Messages
- 20
- Reaction score
- 1
I propose a new block:
Linked Item Transfer:
It has an inventory that is capable of filtered pulling like normal Storage blocks.
It is capable of being linked to other blocks just like normal Storage blocks, thus it can refill itself from a storage block (unless disabled via logic or so like with normal Storage blocks)
Two modes:
1) Would be slaved or bound somehow to a (turret) docking block with an inventory.
2) Would be placed anywhere on a ship itself that is *not* adjacent/slaved to a (turret) docking block.
Action
When slaved/adjacent/bound to a (turret) docking block then it 'links' to other Linked Item Transfer blocks on the docked ship that are not slaved/adjacent/bound to a (turret) docking block. This means that (potentially filtered) item transfer pulls from the remote blocks 'to' itself. Any of the Linked Item Transfer blocks that are not slaved/adjacent/bound to a (turret) docking block will pull from a Linked Item Transfer block that is slaved/adjacent/bound to the (turret) docking block that it is currently docked to.
This would allow you to transfer (filtered) items both ways and would be able to be hooked up to normal storage and logic systems for automated transfer and handling of all your normal products.
Of course this would have the greatest use with scavaging ships as the ships could unload their harvested products just by being docked, of which the products could then go through the normal expected processing steps.
This design would also allow for memory and access optimizations to keep game efficiency high.
Linked Item Transfer:
It has an inventory that is capable of filtered pulling like normal Storage blocks.
It is capable of being linked to other blocks just like normal Storage blocks, thus it can refill itself from a storage block (unless disabled via logic or so like with normal Storage blocks)
Two modes:
1) Would be slaved or bound somehow to a (turret) docking block with an inventory.
2) Would be placed anywhere on a ship itself that is *not* adjacent/slaved to a (turret) docking block.
Action
When slaved/adjacent/bound to a (turret) docking block then it 'links' to other Linked Item Transfer blocks on the docked ship that are not slaved/adjacent/bound to a (turret) docking block. This means that (potentially filtered) item transfer pulls from the remote blocks 'to' itself. Any of the Linked Item Transfer blocks that are not slaved/adjacent/bound to a (turret) docking block will pull from a Linked Item Transfer block that is slaved/adjacent/bound to the (turret) docking block that it is currently docked to.
This would allow you to transfer (filtered) items both ways and would be able to be hooked up to normal storage and logic systems for automated transfer and handling of all your normal products.
Of course this would have the greatest use with scavaging ships as the ships could unload their harvested products just by being docked, of which the products could then go through the normal expected processing steps.
This design would also allow for memory and access optimizations to keep game efficiency high.