Cazadorsniper / PO3

Project Ozone 3
42 stars 14 forks source link

Body stone gets consumed in Chaos Singularity recipe #1676

Open lupatrick13 opened 2 years ago

lupatrick13 commented 2 years ago

Use the search function before reporting to see if the issue has been reported before.

3.4.9 Mythic Multiplayer

Title says it. The other 3 stones do not get consumed. It is pretty much impossible to automate chaos singularity.

Craft a single chaos singularity. The body stone will get consumed. It hsould either be all of it gets consumed or all of it get reused. Please fix chaos singularity automation i so close to finish modback :(

Crash log (use pastebin or issue will be closed):

Cazadorsniper commented 2 years ago

mods.extendedcrafting.TableCrafting.addShaped(0, , [[, , , , , , , , ], [, , , , , , , , ], [, , , , , , .reuse(), .reuse(), .reuse()], [.reuse(), , , , , , , , ], [, , , , , , , , ], [, , , , , , , , ], [, , , , , , , , ], [, , , , , null, null, null, null], [null, null, null, null, null, null, null, null, null]]);

This is the recipe for the chaos catalyst, each stone has the reuse function, I don't know why the body stone doesn't get reused. There is nothing i can do about it.

lupatrick13 commented 2 years ago

This is whats left: Screenshot

I thought the reuse function was used differently and it was just off by one index. But seeing how its a function of the items the bug is weird

bencimp commented 1 year ago

Seeing as the ethaxium ingot is reused, perhaps shifting the reuse call up one (i.e., onto the nocturnal powder or whatever precedes the body stone) and would resolve the issue. It may be that the unintended behavior can be fixed with yet more unintended behavior. @Cazadorsniper

bencimp commented 1 year ago

I have found a fix. If you change the recipe in mythic_9x9.zs (or your appropriate corresponding mode) to have a reuse() on the nocturnal powder and remove it from the life stone, it behaves as intended. I can either upload the fixed file or guide you through how to fix it, if you wish. That being said, I would simply change the recipe; since the ProjectE stones can't be inserted using the automation interface by any method I could find, and they are simply EMCable (and thus don't add any meaningful crafting complexity,) changing the recipe to instead use a different EMCable item that doesn't have issues with metadata preventing insertion into the table is probably a better option. You could also just drop the stones from the recipe. One way or another, though, they cause pretty big problems in the home stretch of the pack.

Esconomics commented 1 year ago

I have the same exact problem. The Body stone consumes and cannot be auto inserted into the table. This renders the pack basically unfinishable at this point because there is no way anyone will hand craft each chaos catalyst and many are needed.

dfduarte78 commented 10 months ago

Can you provide the fix for kappa @bencimp? I tried editing the file today but it didnt work. I set up all automation for it but that red stone prevents me from finishing the pack right now...

Edit: managed to automate somehow adding 20 3x compressed obsidian to the recipe. The output of the recipe is filtered so that this obsidian goes to an energy condenser mk2, the nk2 crafts 1 body stone that is extracted back to the input of the recipe.