Compacting Drawer problem

Question

Compacting Drawer problem

BakermanLP opened this issue 10 years ago · 13 comments

BakermanLP commented 10 years ago

Hello,
I have a small issue about the compacting drawers. But I think it is the easiest way to see a picture of my problem:

Iron nuggets out of copper ingots seems like "magic" :) That works for vanilla ingots, but not for mod ingots.

Can you fix that

jaquadro · Answer 1 · 2015-04-13T14:12:41.000Z

I need to know all your mods providing copper materials and iron nuggets. Could you also try inserting each of those 3 items into an empty drawer and seeing if it changes the tiers you get?

I'd also check the usage and recipe on the ingot and nugget just to be sure there's nothing unexpected happening there either.

jaquadro · Answer 2 · 2015-04-14T02:43:30.000Z

I noticed that you've got a pretty big pack that includes IC2. I've seen ore dictionary problems with this drawer before with IC2 implicated, but I couldn't reproduce it locally with the few other ore providers I have.

Could you install this mod (https://github.com/EXTER7/recipedumper) and use it to dump the ore dictionary and provide that to me? That will probably be key to seeing what's going on and coming up with any kind of a fix.

Note: I haven't actually tried using that tool, but it's the only thing I've found that looks capable of dumping the ore dictionary data.

BakermanLP · Answer 3 · 2015-04-14T07:00:09.000Z

There would be another way using minetweaker, but never mind, wasn't a big problem. Here are the requested files:
http://solder.projectret.de/vsdump-2015-04-14T082538-oredict.log
http://solder.projectret.de/vsdump-2015-04-14T082540-items.log

If you need more informations, logs or dumps just say something.

jaquadro · Answer 4 · 2015-04-14T12:12:49.000Z

Completely forgot that MineTweaker might be capable of providing that (my first place to look was NEI).

Last night I published a new build with MineTweaker support to update the conversion blacklist. (https://github.com/jaquadro/StorageDrawers/releases/tag/sd-1.3.8). Try adding "ingotAny" and "nuggetAny" as prefixes to the blacklist, and see if it makes any difference.

If not, then I may need a shaped and shapeless recipe log instead.

BakermanLP · Answer 5 · 2015-04-14T14:59:10.000Z

I'll give it a shoot. But that will be tomorrow. I give you some feedback then

BakermanLP · Answer 6 · 2015-04-15T06:02:06.000Z

And here is the screenshot after adding ingotAny and nuggetAny to the blacklist via minetweaker:

For documentation purpose here is the minetweaker script:
mods.storagedrawers.OreDictionaryBlacklist.addPrefix("ingotAny");
mods.storagedrawers.OreDictionaryBlacklist.addPrefix("nuggetAny");

Thank you for the help!

Michael

jaquadro · Answer 7 · 2015-04-15T12:34:51.000Z

Cool. I'm actually a little surprised it worked (so keep an eye on it). I always heard GT did crazy things to the ore dictionary table, and now I know why.

BakermanLP · Answer 8 · 2015-04-15T15:30:27.000Z

I know @GregoriusT and most parts oft bis mod makes sense. Sometimes there
are problematic things in corporation with other mods. In most cases he did
it right. But not always ;-)

Justin Aquadro [email protected] schrieb am Mi., 15. Apr. 2015
14:34:

Cool. I'm actually a little surprised it worked (so keep an eye on it). I
always heard GT did crazy things to the ore dictionary table, and now I
know why.

—
Reply to this email directly or view it on GitHub
#59 (comment)
.

GregoriusT · Answer 9 · 2015-04-15T15:54:20.000Z

Ahem, I am not the first one to do that. I saw TerrafirmaCraft do it and thought that "AnyCopper" and "AnyIron" would be a good Idea to add in order to make Annealed Copper exchangeable with regular Copper in most of my Recipes. Same for Iron and Wrought Iron (what later extended to Meteoric Iron, Deep Iron and Shadow Iron, basically anything that is considered to be some kind of direct Iron). My Material System parses pretty much everything inside the OreDict and doesn't accept technical Names, such as that one, as Component of an Item, so I don't get problems since I don't have such a simple Parser, but instead I have to check for every single Name to be properly registered before I can handle it. Note that "block[Something]" doesn't work at all for most Names. It works only for Gold, Iron, Lead, Platinum, Copper, Tin, Steel and Silver, the rest is guesswork thanks to many Mods registering random junk as "block[Something]" to the OreDict. That is why I added the "blockIngot[Something]" Prefix (and some others for Dusts, Gems and Stuff) in order to have Storage Blocks and their Recipes sorted properly. I do so many things with the OreDict (and all of them are even within the terms of its proper usage), that other people with simpler Parsers get slightly incompatible.

jaquadro · Answer 10 · 2015-04-15T16:37:44.000Z

Thanks for taking the time to explain some of the reason for those entries. An 88,000 line ore dictionary log is still quite something to behold.

HarvestCraft was the first one to give me trouble with those kinds of broad categorical entries. I've since written heuristics that are able to weed out most of those without me needing to blacklist them, but I'll need to revisit them again.

jaquadro · Answer 11 · 2015-04-16T05:48:03.000Z

@BakermanLP could you give the 1.3.9 release a spin and see if it works without the explicit blacklist entries? I overhauled the dictionary heuristics to be a lot more aggressive about identifying categorical entries. It should be much more GT-friendly now.

Of course, something careless like an item registered to both ingotIron and ingotWroughtIron, rather than a parent category like ingotAnyIron, would cause both of those keys to be shut down, but better to be more conservative in this case.

GregoriusT · Answer 12 · 2015-04-16T06:19:41.000Z

If someone would do that, then even GT would fuck up things, and in this particular case it would do the following: 1. Thanks to that double registration using two valid Materials rather than just one valid Material it would choose one of them and ignore the other completely. 2. Because it is an Iron Ingot, and I have set the explicit unification Target to be the vanilla Iron Ingot, any Wrought Iron registered as "ingotIron" would unificate towards the vanilla Iron Ingot, resulting in that Wrought Iron Ingot Item being effectively deleted from the Game (since it almost always gets replaced with an Iron Ingot)

BakermanLP · Answer 13 · 2015-04-16T06:58:05.000Z

After having some popcorn and reading through this thread, I have tried to remove the minetweaker commands. And ... yes, it works also now.

Share to