diff options
author | electrodude <electrodude512@gmail.com> | 2016-05-27 15:31:45 -0400 |
---|---|---|
committer | Auke Kok <sofar+github@foo-projects.org> | 2016-10-10 14:15:44 -0700 |
commit | a3d2e69a42585ffc7f9f4295b716948a10bee8c2 (patch) | |
tree | 13138facec83db40ef3a468b448e10ccc0393029 /models/pipeworks_pipe_5.obj | |
parent | 36d9e1fc08b77a058454d4d9de1cde505e37806e (diff) | |
download | pipeworks-a3d2e69a42585ffc7f9f4295b716948a10bee8c2.tar pipeworks-a3d2e69a42585ffc7f9f4295b716948a10bee8c2.tar.gz pipeworks-a3d2e69a42585ffc7f9f4295b716948a10bee8c2.tar.bz2 pipeworks-a3d2e69a42585ffc7f9f4295b716948a10bee8c2.tar.xz pipeworks-a3d2e69a42585ffc7f9f4295b716948a10bee8c2.zip |
Allow Digiline Filter-Injector to match wear, metadata, and group
You can now make reqyests like `{group="stick"}`, `"default:pick_wood 1
30000"`, and `"mod:block <count> <exact wear> <meta>"` to match
items precisely.
If you don't specify a field, that field won't be checked. If you
specify a field in an invalid way, that rule will match nothing.
You can also specify wear as a table `wear={min, max}` to specify
a range `[min, max)` of acceptable wear values. For example,
`{name="default:pick_wood", wear={0, 32768}}` matches only wooden
pickaxes that have at least half of their life left.
You can even do things like `{count=2, metadata="whatever")}`, which
will match any item at all, as long as its metadata matches, and will
retrieve at most two of those items.
Diffstat (limited to 'models/pipeworks_pipe_5.obj')
0 files changed, 0 insertions, 0 deletions