I'm not sure if that makes any difference, but it's worth a shot. The only difference I can see between mine and yours is the format of the mods.toml file. So what could possibly cause this? Because all explanations I saw so far target the file being at the wrong location however this doesn't seem to be the case. # Side this dependency is applied on - BOTH, CLIENT or SERVER # An ordering relationship for the dependency - BEFORE or AFTER required if the relationship is not mandatory # Does this dependency have to exist - if not, ordering below must be specified # The description text for the mod (multi line!) (#mandatory)ĭescription='"A The Legend of Zelda Mod"' # The version number of the mod - there's a few well known $ variables useable here or just hardcode itĭisplayName="Cruelars Triforcemod" #mandatory # A list of mods - how many allowed here is determined by the individual mod loader LoaderVersion="[28,)" #mandatory (28 is current forge version) # A version range to match for said mod loader - for regular FML it will be the forge version # The name of the mod loader type to load - for regular FML mods it should be javafml However my mods.toml is in src\main\resources\META-INF\mods.toml : Failed to find exploded resource mods.toml
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |