2.0.9.0 QF4
I don't see why this needs to be a thing, no one actually seems to use this functionality for its intended purpose. The only reason people were using this before was so they could cheese turbines and disassemble them but that has been patched so I see no need for this anymore.
All disassembly data does is create conflicts in AE where it cannot recognise an item because it has slightly different disassembly data.
The amount of useless data on items is truly staggering, say you are making an assembler this will take 2 robot arms and 2 conveyors. This this has to store the data for the recipes for each of those 2 robot arms and 2 conveyors which then also has to store the data for all the motors and pistons and subsequent motors inside those pistons... What I'm trying to say is it's really silly and no one uses it.
Was thinking of trying to get this in before the latest update so we can bundle barts changes to parts and this together in one update as they will both create the same issue.
You can just arc furnace or macerate anyway. Plus this is a nerf, that means it'll definitely go through!
removing all the disassembling data from nbt will wreck a lot of existing AE2 automating recipe. But i'm ok with that because after updating the pack, those disassembling data were the reason why the recipes broke so i suppose that if those do not exist anymore, there will be no more issue with that.
removing all the disassembling data from nbt will wreck a lot of existing AE2 automating recipe. But i'm ok with that because after updating the pack, those disassembling data were the reason why the recipes broke so i suppose that if those do not exist anymore, there will be no more issue with that.
Yea this was my thoughts as well, given that barts changes will break all exist parts NBT anyways under #6246 I thought packaging these two changes at once would try and prevent any further screw ups with updates and AE systems.
Yes please remove all that bloat. Might even help shift-clicking in crafting tables. It will force some people to redo their autocrafting but that's a sacrifice I'm willing to make.
yes please! disassembling is such a unimportant mechanic compared to all the problems disassembly data has caused over time and would cause in the future.
I am all for it, but do you remove the disassembler or patch it to work without the ingredients NBT data?
I am all for it, but do you remove the disassembler or patch it to work without the ingredients NBT data?
Keep the diassembler for now just to prevent other conflicts (Like stem cells from eggs) but there will be no replacement data on this to prevent exploits. The whole reason items keep track of this data is so you can't make something and disassemble it into something else (Like different tier circuits for example).
You can't craft the eggs anymore anyway, so it doesn't matter for that.
You can't craft the eggs anymore anyway, so it doesn't matter for that.
The eggs were never craftable, they dropped from large chickens.
And how do you get the chickens? From the eggs, which are now uncraftable.
Use the name remover. It strips the disassembly days.
@mitchej123 please reopen this. a name remover does not do anything to address this. (unless you mean 100+ name removers everywhere)
If it is a duplicate please point us to the other ticket.
Use the search feature
you mean this one https://github.com/GTNewHorizons/GT-New-Horizons-Modpack/issues/4782?
looks like the devs already ignored the issue back then. Since then it has only caused more problems.
Can you at least give a reasoning? I have not heard of a single player who is in favor of disassembly data.
I like it and utilise it for things.
@chochem It wasn't ignored, it was addressed with the name remover. Some people use it and it isn't a big deal. Please address any comments on that thread instead of spreading it across two threads.
Disassembler may theoretically use assembler recipe map and invert it.
Most helpful comment
Yea this was my thoughts as well, given that barts changes will break all exist parts NBT anyways under #6246 I thought packaging these two changes at once would try and prevent any further screw ups with updates and AE systems.