Additional Placements

Additional Placements

517k Downloads

Inventory Actions & Additional Placements

dadoirie opened this issue ยท 2 comments

commented

any idea why Inventory Actions (https://www.curseforge.com/minecraft/mc-mods/inventory-actions) and Additional Placements conflicting here and if this can be fixed without limiting either of both mods capabilities?
I assume blacklisting the copper slabs & stairs for additional placement might be doing the trick here, but then this has to be done with any item I'm creating possible inventory action ... or could a compat fix be made between them?

https://mclo.gs/eAYTgZa

starting at Line 217: https://mclo.gs/eAYTgZa#L217

took me quite a few hours finding this conflict from a 243 mods list (and growing) and I really hope a compat is possible, because both mods are very desired

it doesn't crash, just makes any material additional placement is using inventory actions can't do nothing with it

commented

As this issue affects only one built-in inventory action while other built-in actions work just fine and as well custom made actions don't cause issues either.
2 solutions are present:
Solution 1 would be disabling this copper action or solution 2 would be simply fixing them with a custom action overwriting the built-in action which works the exact same way and if there is a built-in support for copper from other mods then those need to be included in that custom action

how to disable a built-in action is explained here: https://github.com/High-Fox/InventoryActions/wiki

here are the 2 actions which work with additional placements
place them in data/inventoryactions/inventory_actions/ - NOTE: files need to be renamed after downloading by removing the .txt extension otherwise it won't work
copper_remove_wax.json.txt
copper_scrape.json.txt

how data packs work is beyond scope of this post and can be found here: https://minecraft.fandom.com/wiki/Data_pack
as well there are mods which do load data packs upon world creation automatically

commented

This is an issue on InventoryAction's end - they are converting <Block, Block> pairings to <Item, Item> pairings without accounting for the possibility of multiple pairings using the same item form. I will forward this issue to them.