New Relics mod requires newer Curios version, breaking with the Curios Compat
brisingraerowing opened this issue · 8 comments
It is annoying they are constantly updating the dependency when they are not using any of the new features to the updates. Its not a good idea to force people to download the latest versions when not required as it may be the update could contain issues with recent changes and require another update to fix... Ill see what I can do to update such but frankly may be able to just get away with loader overrides on neoforge for the versioning if you know how to do such
I have no idea what loader overrides are. Is there documentation describing them?
EDIT: Found the option in the config file. Testing now.
I have no idea what loader overrides are. Is there documentation describing them?
EDIT: Found the option in the config file. Testing now.
can you explain where to find that?
I trierd searchin for it but I was too tired
It is annoying they are constantly updating the dependency when they are not using any of the new features to the updates. Its not a good idea to force people to download the latest versions when not required as it may be the update could contain issues with recent changes and require another update to fix... Ill see what I can do to update such but frankly may be able to just get away with loader overrides on neoforge for the versioning if you know how to do such
do you know if such a options excist in neoforge?
A article about such is unkown but this PR is what I am referring to: neoforged/FancyModLoader#214
I have no idea what loader overrides are. Is there documentation describing them?
EDIT: Found the option in the config file. Testing now.can you explain where to find that? I trierd searchin for it but I was too tired
for anyone needing the bandaid fix,
in config/fml.toml put
[dependencyOverrides]
relics = ["-curios"]
reliquified_twilight_forest = ["-curios"]ofc the reliquified_twilight_forest only if you have that mod installed