IntegratedDynamics icon indicating copy to clipboard operation
IntegratedDynamics copied to clipboard

Vulpes library ore support

Open benserwa opened this issue 6 years ago • 6 comments

Issue type:

  • :heavy_plus_sign: Feature request

Short description:

The Squeezer and Mechanical Squeezer do not support Vulpes library's (Advanced Rocketry's) ores. I would ordinarily just add recipes using the XML system, but as the ores use metadata (or something like that) to differentiate between the ore blocks, rather than each one having its own item ID, that seems to be impossible.

benserwa avatar Apr 25 '19 05:04 benserwa

Is there a reason that the ore dict cannot be used?

zmaster587 avatar Apr 26 '19 02:04 zmaster587

I wasn't aware from the documentation that you could use ore dict. Is there an example of what that looks like?

benserwa avatar Apr 27 '19 05:04 benserwa

For example: <item type="oredict">treeSapling</item>

rubensworks avatar Apr 27 '19 06:04 rubensworks

OK, so, I've got this working for the regular Squeezer, but not the Mechanical Squeezer, which seems odd, I thought the recipes would just carry over automatically.

I've tried repeating the recipes with but the attempt crashed the pack. I'll try without the underscore here.

My XML:

<?xml version="1.0" encoding="utf-8"?>
<recipes>
    <recipe type="integrateddynamics:squeezer">
        <condition type="config">squeezer</condition>
        <input>
            <item type="oredict">oreAluminum</item>
        </input>
        <output>
            <item type="oredict">dustAluminum</item>
        </output>
    </recipe>
	
    <recipe type="integrateddynamics:squeezer">
        <condition type="config">squeezer</condition>
        <input>
            <item type="oredict">oreRutile</item>
        </input>
        <output>
            <item type="oredict">dustTitanium</item>
        </output>
    </recipe>
</recipes>

benserwa avatar Apr 29 '19 00:04 benserwa

So yeah, there's definitely a way of doing mechnical squeezer recipes in the XML correctly, I just don't know what it is. Searching through the issues to see if I'm repeating someone, it seems like the Mechanical Squeezer hasn't been around for very long, so I guess I'm asking for the Recipe XML documentation to be updated with info about the Mechanical Squeezer's recipe format.

benserwa avatar Apr 29 '19 00:04 benserwa

Right now I'm doing:

<?xml version="1.0" encoding="utf-8"?>
<recipes>
    <recipe type="integrateddynamics:squeezer">
        <condition type="config">squeezer</condition>
        <input>
            <item type="oredict">oreAluminum</item>
        </input>
        <output>
            <item type="oredict">dustAluminum</item>
        </output>
    </recipe>
	
    <recipe type="integrateddynamics:squeezer">
        <condition type="config">squeezer</condition>
        <input>
            <item type="oredict">oreRutile</item>
        </input>
        <output>
            <item type="oredict">dustTitanium</item>
        </output>
    </recipe>
	
    <recipe type="integrateddynamics:mechanical_squeezer">
        <condition type="config">mechanical_squeezer</condition>
        <input>
            <item type="oredict">oreAluminum</item>
        </input>
        <output>
            <item type="oredict">dustAluminum</item>
        </output>
    </recipe>
	
    <recipe type="integrateddynamics:mechanical_squeezer">
        <condition type="config">mechanical_squeezer</condition>
        <input>
            <item type="oredict">oreRutile</item>
        </input>
        <output>
            <item type="oredict">dustTitanium</item>
        </output>
    </recipe>
</recipes>

Which is crashing hard (null pointer). It seems from the code that I have to set a "duration", but I'm not sure exactly how to do that or what the effect of it would be.

benserwa avatar Apr 29 '19 00:04 benserwa