pipeworks/depends.txt

default
basic_materials
mesecons
mesecons_mvps
digilines?
added .gitignore for temp Kate files, added depends.txt for "default" 2012-07-14 00:51:26 +02:00			`default`
use basic_materials mod where possible 2018-10-31 01:45:48 +01:00			`basic_materials`
hard dep on mesecons 2017-09-27 08:22:05 +02:00			`mesecons`
			`mesecons_mvps`
Add Digiline Filter-Injector This adds a new type of Filter-Injector that waits for a digiline message on its channel and then pulls the items described by the message out of the inventory. It is basically a Stackwise Injector that, on receiving a digiline message, sets its filter to the contents of the digiline message and then activates itself. Sending the message {name="default:brick", count=2} should do the same thing as setting the filter of a Stackwise Filter-Injector to two Brick Blocks and then punching it. If no count is specified, it defaults to 1. Since this is based off of the Stackwise Injector, it might make more sense if the default were an entire stack. I can change this trivially. You can also send requests like {{name="default:brick", count=1}, {name="default:dirt", count=1}}, which acts the same as setting the filter to one Brick Block and one Dirt Block and then punching it. If you send a string "default:dirt" instead of a table {name="default:dirt"}, the string is passed to ItemStack and the name and count are extracted from the resulting ItemStack. You can also send a list of strings instead of tables: {"default:dirt", "default:brick"}, and the first item found will be pulled. Punching this or activating it with Mesecons currently does nothing. I'm not really sure what would be the right thing to do in either of those two cases, so I made it do nothing. I guess I could make it use the previously-used filter, but I can't really see any usefulness in that. The recipe is probably too cheap. The darker of the two blue texture colors could probably be better. 2015-12-18 20:18:29 +01:00			`digilines?`