-
Notifications
You must be signed in to change notification settings - Fork 14
Mod Support
This page gives an overview of some special mods that are either unsupported or need special treatment in order to work with the mod.
Note:
Not all configs are located inside the config directory of your Minecraft instance. If you can't find the mentioned configs, make sure to search the subdirectories as well.
When there is a server config being mentioned, those are usually located inside the world's config directory: YOUR_INSTANCE/saves/YOUR_WORLD/serverconfig
Almost Unified configs are always located in config/almostunified
.
Most recipes work fine. Only the OreChid flower needs a bit of tweaking to generate the right ores.
Since Almost Unified isn't tweaking ore generation, it's your choice what you put there. If you disabled all ore generation except from a mod like Thermal, make sure the mod with the highest priority will be Thermal as well.
Open the botania-common.toml
and adjust the orechidPriorityMods
list.
The mod adds the storage_blocks/copper
tag to the Cut Copper block. This results in the Cut Copper being picked as the priority item and also introduces a dupe bug in the Stonecutter. In order to fix it, remove the tag from the Cut Copper block.
The issue is tracked here.
The Fabric version of Create follows the Forge tag conventions which breaks the unification of Create's materials. In order to fix this, you have to properly tag Create resources e.g. their ingots so they follow the Fabric convention.
If you don't want to mess with tags, you can also use CreatePlus as an alternative which is available on CurseForge and Modrinth.
The mod works very well as long as you have a version installed that has this pull request included.
Since Geolosys overhauls the ore generation and adds its own ores and raw materials, the best way to integrate it is to set it higher than Minecraft in the priority list. That way, the chunks from Geolosys will replace the vanilla chunks.
While the majority of the recipes work fine, the config needs a bit of tweaking to work as intended.
Open the immersiveengineering-common.toml
and make sure the preferredOres
list has the same order as the modPriorities
list in the unify.json
config from Almost Unified.
This ensures that the ores dug by the excavator use the correct mod.
For making the recycling feature of the Arc Furnace work with the resource list you want, open the immersiveengineering-server.toml
and use the search function of your editor to find immersiveengineering/recipes/arc_recycling_list.json
.
Read the instructions and make the changes as you wish.
The mod is using the library Titanium to specify some recipe-related resources.
In order to make it work properly with Almost Unified, open the titanium-tags.toml
and make sure the ITEM_PREFERENCE
list has the same order as the modPriorities
list in the unify.json
config from Almost Unified.
The mod is using the wrong recipe JSON key for smelting and blasting recipes. It uses cookingTime
instead of cookingtime
which is also ignored by Mojang so it isn't taken into account.
Due to the incorrect JSON key, recipes from the mod are not properly detected as duplicates. To fix this, you have to ignore the cookingTime
key inside your duplicates.json
config.
The mod is using the Cucumber Library to specify some recipe-related resources.
In order to make it work properly with Almost Unified, open the cucumber-common.toml
and make sure the modTagPriorities
list has the same order as the modPriorities
list in the unify.json
config from Almost Unified.
Since the tag entries are generated while the game is running and cached inside the cucumber-tags.json
, remove the file after you changed the config file. More about the tag config system of Cucumber, can be found here.
If you are getting errors in your latest.log
about a ShapedTagRecipe
, make sure that the recipe type cucumber:shaped_tag
is added to the ignoredRecipeTypes
list inside the unify.json
config.
To make bees give the preferred output, open the productivebees-server.toml
and make sure the preferredTagSource
list has the same order as the modPriorities
list in the unify.json
config from Almost Unified.
Additionally, you should add the mod id productivebees
to the list.
If your pack has Refined Storage and Applied Energistics installed, you probably want to unify the use of Silicon. However, for some reason, Refined Storage decided to tag their Silicon with the proper tag and a custom mod-internal tag. And for their own recipes, they use the mod-internal tag.
So adding something like forge:silicon
to your unify.json
config will have no effect. You have to adjust the Refined Storage recipes manually so they make use of the shared tag.
We are working on a config solution for this at the moment.
The mod is using the library Mantle to specify some recipe-related resources.
In order to make it work properly with Almost Unified, open the mantle-server.toml
and make sure the tagPreferences
list has the same order as the modPriorities
list in the unify.json
config from Almost Unified.
Somewhat unsupported. The mod developer refuses to follow JSON serialization conventions and also doesn't accept any pull requests to fix this. They use separate recipe types for the same recipes just to have tag-based outputs (which are fine) but then serialize them to a primitive so we can't replace anything. As of right now, they are also not interested in a pull request adding Almost Unified integration to their mod directly.
Completely unsupported. The mod bypasses the vanilla systems for recipes and loot. It's closed source and licensed all rights reserved. The authors show no interest in being compatible with other mods. There is nothing we can do about that.
Most of the recipes are unified but the author sadly decided to hardcode the Cauldron recipes so Almost Unified can't modify them. If you want to use the mod, this is fine but you probably need to give it priority so their materials are used which are compatible with the Cauldron.
It's not fully unsupported but since is one of the major features of the mod, it is a huge disadvantage.