We are experiencing duping on our server:
The recycler is able to produce infinite scrap from microblockcbe's saws. They will not consue or consume their usage while recycling and will end up in minus usages, creating scrap from nothing.

I tried to blacklist the items, but the recyclerBlacklist inside the ic2.cfg is not working well. I can exclude new saws by using their item ID and string annotation "microblockcbe:saw_stone", but covering differen durability values is not working. If the saw has any usage (lifetime bar appearing under the item) then the blacklist stops working and scrap is again generated out of thin air. I have no way to fix this and the blacklist doesn't work as expected / is not well documented (for example finding our item IDs work, was just a test from my side)

This bug is reproducible with other items as well, some examples:

• projectred-exploration:sapphire_saw
• chiselsandbits:bitsaw_diamond

Config won't work for microblocks too:

• microblockcbe:microblock

My config blacklist (be careful, whitespaces will break the config read): S:recyclerBlacklist=minecraft:stick,minecraft:snowball,microblockcbe:microblock,microblockcbe:saw_stone,microblockcbe:saw_iron,microblockcbe:saw_diamond,projectred-exploration:golden_saw,projectred-exploration:ruby_saw,chiselsandbits:bitsaw_diamond,projectred-exploration:sapphire_saw,projectred-exploration:peridot_saw

Thanks i will address this in the next patch.
Though it will take a bit since i am also aligning myself with the tekkit 2 update and that is at least 1 week away.

Cool, thanks for the quick reply! I updated the original post, I got the string annotation working for some reason, but the major issue (used items are not consumed and blacklisting them won't work) persists.

As a note, it would be great to be able to add whole mods to recyclerBlacklist.
For example:
microblockcbe:saw_stone -> prevents a new stone saw to be recycled
microblockcbe:saw_stone-* -> prevents all durability value saws to be used
microblockcbe:* -> prevents all microblockcbe items to be recycled (this would include cut microblocks)

I found a way to partly prevent this:
Add an entry for every saw with every durability value to prevent saws from being recycled

• microblockcbe:saw_stone
• microblockcbe:saw_stone-1
• microblockcbe:saw_stone-2
• microblockcbe:saw_stone-3
• ...
• microblockcbe:saw_stone-512

This will massively bloat the cfg file but maybe is a temp workaround for the duping.

On a wider scope:
We'd really need to blacklist whole subsets or categories, because we want to ban all kinds of microblocks, even worse is chiselsandbits which can cut a single block into 4096 single items. This also yields an infinite source of scrap and we can't ban them all, because every block has a high subset of bits with metadata.
We'd need a blacklist for chiselsandbits:*

Okay, I'll get busy with writing a script to create me a huge blacklist file, until then! :P

Okay cool! For anyone affected, here is a blacklist for Tekkit2, banning all affected saws:

OH god that spoiler flashed me xD
@xJon might want to look at this once you are back too xD

@Noblauch that is a great suggestion.
It really depends on how much i am willing to do with my current plans.
To explain: I am writing a new config library and think about integrating that into ic2c 1.12.2 which has a lot of features that would make ic2c 1.12 a lot better.

Now the thing is this library is weeks away from being finished,
so do i invest the time now or do i invest the time later.

But ignoring all that.
Your idea is sound and I think it should be a thing. Just give me a bit of time to find out a good implementation.

@Noblauch
ok here is the solution that i came up with. Would be nice if you can rate it to some degree that way i know if i need to throw in another pass or not.

New Format:

"ore:oredictname" => disables all ores.
"itemId" => disables that specific item with meta 0
"itemId-meta" => disables that item with that specific meta.
"itemId-minMeta-MaxMeta" => disables that specific meta range.
"#itemId" => disables all items with any metadata

This should help a lot.
(oredict was already supported)

@Speiger
Looks good except the # annotation in my opinion. Since .cfg file comments are generally started with a # my editor (VS Code) would also highlight this as a comment starting from there. I'd stick with the widely used convention and use a * for "all".
So "itemId-*" would make sense to me to disable an item with all meta combinations.

Not sure if min max range would be useful, but why not.

Please note that the general underlying problem (saws not being consumed by the recycler) is not fixed. But getting a blacklist improvement is the first step I guess ;)
Thanks for the reply!

@Noblauch
Thanks yeah that would be a dumb idea to make them comments on accident xD
So its now *itemId.
Its just simpler to parse this way. Since i can start with "just skip 1 character" insteadof string splitting etc.

Regarding the other bug that is fixed in the next patch too. Thanks for the reminder.
The next patch should come out tomorrow if everything is fine until then.

Tonight it is to late for me to do a release patch.