[1.15.2] Testing mod, Minecraft* will not start

[TheThorneCorporation]

Whenever I try to run runClient, I get past the Minecraft loading screen, only to be met by this error message:

 

"Users/neoskater/Desktop/ComputerScience/Java/MinecraftModding/1.15.2/ElementalMagic/bin/main has mods that were not found."

 

I went into the mods.toml file in main and it does appear to be set up correctly with the correct modid, but nothing is loading. Any idea what's going on?

 

(Note: For some reason the bin/main in this mod only contains a pack.mcmeta and a META-INF folder containing only mods.toml, while the one for the only mod I have successfully tested contains a full copy of the code. Maybe that has something to do with it?)

[Beethoven92]

Have you forgot to add the @Mod annotation on top of your mod main class? Without it basically Forge won't recognize your mod as a loadable mod

Edited July 28, 2020 by Beethoven92

[Draco18s]

Show your main mod class and your mods.toml file.

[TheThorneCorporation]

2 hours ago, Draco18s said:

Show your main mod class and your mods.toml file.

Here you go. (I should probably get to cleaning up the files – I changed the minimum amount required from the defaults to make the mod work.)

The mod class:

package com.thornecorporation.elementalmagic;

import net.minecraft.item.ItemGroup;
import net.minecraft.item.ItemStack;
import net.minecraft.item.Items;
import net.minecraftforge.common.MinecraftForge;
import net.minecraftforge.event.RegistryEvent;
import net.minecraftforge.eventbus.api.SubscribeEvent;
import net.minecraftforge.fml.InterModComms;
import net.minecraftforge.fml.common.Mod;
import net.minecraftforge.fml.event.lifecycle.FMLClientSetupEvent;
import net.minecraftforge.fml.event.lifecycle.FMLCommonSetupEvent;
import net.minecraftforge.fml.event.lifecycle.InterModEnqueueEvent;
import net.minecraftforge.fml.event.lifecycle.InterModProcessEvent;
import net.minecraftforge.fml.event.server.FMLServerStartingEvent;
import net.minecraftforge.fml.javafmlmod.FMLJavaModLoadingContext;
import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;

import java.util.stream.Collectors;

// The value here should match an entry in the META-INF/mods.toml file
@Mod(ElementalMagic.MOD_ID)
public class ElementalMagic
{
    // Directly reference a log4j logger.
	public static final String MOD_ID = "elementalmagic";
    private static final Logger LOGGER = LogManager.getLogger();
    public static final ItemGroup ITEM_GROUP = new ElementalMagicItemGroup("elemental_magic_group");

    public ElementalMagic() {
        // Register the setup method for modloading
        FMLJavaModLoadingContext.get().getModEventBus().addListener(this::setup);
        // Register the enqueueIMC method for modloading
        FMLJavaModLoadingContext.get().getModEventBus().addListener(this::enqueueIMC);
        // Register the processIMC method for modloading
        FMLJavaModLoadingContext.get().getModEventBus().addListener(this::processIMC);
        // Register the doClientStuff method for modloading
        FMLJavaModLoadingContext.get().getModEventBus().addListener(this::doClientStuff);

        // Register ourselves for server and other game events we are interested in
        MinecraftForge.EVENT_BUS.register(this);
    }

    private void setup(final FMLCommonSetupEvent event)
    {
        
    }

    private void doClientStuff(final FMLClientSetupEvent event) {
        // do something that can only be done on the client
        LOGGER.info("Got game settings {}", event.getMinecraftSupplier().get().gameSettings);
    }

    private void enqueueIMC(final InterModEnqueueEvent event)
    {
        // some example code to dispatch IMC to another mod
        InterModComms.sendTo("elementalmagic", "helloworld", () -> { LOGGER.info("Hello world from the MDK"); return "Hello world";});
    }

    private void processIMC(final InterModProcessEvent event)
    {
        // some example code to receive and process InterModComms from other mods
        LOGGER.info("Got IMC {}", event.getIMCStream().
                map(m->m.getMessageSupplier().get()).
                collect(Collectors.toList()));
    }
    // You can use SubscribeEvent and let the Event Bus discover methods to call
    @SubscribeEvent
    public void onServerStarting(FMLServerStartingEvent event) {
        
    }

    // You can use EventBusSubscriber to automatically subscribe events on the contained class (this is subscribing to the MOD
    // Event bus for receiving Registry Events)
    @Mod.EventBusSubscriber(bus=Mod.EventBusSubscriber.Bus.MOD)
    public static class RegistryEvents {
        @SubscribeEvent
        public static void onNewRegistry(final RegistryEvent.NewRegistry event) {
            
        }
    }
    
    public static class ElementalMagicItemGroup extends ItemGroup {

		public ElementalMagicItemGroup(String name) {
			super(name);
		}

		@Override
		public ItemStack createIcon() {
			return new ItemStack(Items.COOKED_COD);
		}
        
    }
}

 

The mods.toml file at src/main/resources:

# This is an example mods.toml file. It contains the data relating to the loading mods.
# There are several mandatory fields (#mandatory), and many more that are optional (#optional).
# The overall format is standard TOML format, v0.5.0.
# Note that there are a couple of TOML lists in this file.
# Find more information on toml format here:  https://github.com/toml-lang/toml
# The name of the mod loader type to load - for regular FML @Mod mods it should be javafml
modLoader="javafml" #mandatory
# A version range to match for said mod loader - for regular FML @Mod it will be the forge version
loaderVersion="[31,)" #mandatory This is typically bumped every Minecraft version by Forge. See our download page for lists of versions.
# A URL to refer people to when problems occur with this mod
issueTrackerURL="http://my.issue.tracker/" #optional
# A list of mods - how many allowed here is determined by the individual mod loader
[[mods]] #mandatory
# The modid of the mod
modId="elementalmagic" #mandatory
# The version number of the mod - there's a few well known ${} variables useable here or just hardcode it
version="${file.jarVersion}" #mandatory
 # A display name for the mod
displayName="Example Mod" #mandatory
# A URL to query for updates for this mod. See the JSON update specification <here>
updateJSONURL="http://myurl.me/" #optional
# A URL for the "homepage" for this mod, displayed in the mod UI
displayURL="http://example.com/" #optional
# A file name (in the root of the mod JAR) containing a logo for display
logoFile="examplemod.png" #optional
# A text field displayed in the mod UI
credits="Thanks for this example mod goes to Java" #optional
# A text field displayed in the mod UI
authors="Love, Cheese and small house plants" #optional
# The description text for the mod (multi line!) (#mandatory)
description='''
This is a long form description of the mod. You can write whatever you want here

Have some lorem ipsum.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed mollis lacinia magna. Orci varius natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Sed sagittis luctus odio eu tempus. Interdum et malesuada fames ac ante ipsum primis in faucibus. Pellentesque volutpat ligula eget lacus auctor sagittis. In hac habitasse platea dictumst. Nunc gravida elit vitae sem vehicula efficitur. Donec mattis ipsum et arcu lobortis, eleifend sagittis sem rutrum. Cras pharetra quam eget posuere fermentum. Sed id tincidunt justo. Lorem ipsum dolor sit amet, consectetur adipiscing elit.
'''
# A dependency - use the . to indicate dependency for a specific modid. Dependencies are optional.
[[dependencies.examplemod]] #optional
    # the modid of the dependency
    modId="forge" #mandatory
    # Does this dependency have to exist - if not, ordering below must be specified
    mandatory=true #mandatory
    # The version range of the dependency
    versionRange="[31,)" #mandatory
    # An ordering relationship for the dependency - BEFORE or AFTER required if the relationship is not mandatory
    ordering="NONE"
    # Side this dependency is applied on - BOTH, CLIENT or SERVER
    side="BOTH"
# Here's another dependency
[[dependencies.examplemod]]
    modId="minecraft"
    mandatory=true
    versionRange="[1.15.2]"
    ordering="NONE"
    side="BOTH"

Hey, wait a minute. I forgot to change an appearance of "examplemod" in the toml files! Maybe that's it?

 

EDIT: Nope, that's not it. I fixed the mistake and it still gives me the same problem. I attached the latest.log for the mod, but here's the most relevant section (the first FATAL thing logged):

[28Jul2020 20:40:10.728] [Render thread/INFO] [net.minecraft.client.Minecraft/]: Setting user: Dev
[28Jul2020 20:40:26.227] [Render thread/INFO] [net.minecraft.client.Minecraft/]: Backend library: LWJGL version 3.2.1 build 12
[28Jul2020 20:40:29.655] [Render thread/FATAL] [net.minecraftforge.fml.ModLoader/LOADING]: File /Users/neoskater/Desktop/ComputerScience/Java/MinecraftModding/1.15.2/ElementalMagic/bin/main constructed 0 mods: [], but had 1 mods specified: [elementalmagic]
[28Jul2020 20:40:29.655] [Render thread/FATAL] [net.minecraftforge.fml.ModLoader/CORE]: Failed to initialize mod containers
net.minecraftforge.fml.ModLoadingException: The Mod File /Users/neoskater/Desktop/ComputerScience/Java/MinecraftModding/1.15.2/ElementalMagic/bin/main has mods that were not found

 

and the new and improved mods.toml:

modLoader="javafml" #mandatory
loaderVersion="[31,)" #mandatory This is typically bumped every Minecraft version by Forge. See our download page for lists of versions.
issueTrackerURL="http://my.issue.tracker/" #optional
[[mods]] #mandatory
modId="elementalmagic" #mandatory
version="${file.jarVersion}" #mandatory
displayName="Elemental Magic" #mandatory
updateJSONURL="http://myurl.me/" #optional
displayURL="http://example.com/" #optional
logoFile="examplemod.png" #optional
credits="Damian Thorne - the mod maker" #optional
authors="Damian Thorne, CEO of the Thorne Corporation" #optional
description='''A way to utilize the power of fire, water, air, earth, and ether in Minecraft.'''
[[dependencies.elementalmagic]] #optional
    modId="forge" #mandatory
    mandatory=true #mandatory
    versionRange="[31,)" #mandatory
    ordering="NONE"
    side="BOTH"
[[dependencies.elementalmagic]]
    modId="minecraft"
    mandatory=true
    versionRange="[1.15.2]"
    ordering="NONE"
    side="BOTH"

 

latest.log

Edited July 29, 2020 by TheThorneCorporation

[Beethoven92]

The mod.toml file looks fine, and so your mod main class... "examplemod.png" doesn't really matter, and as far as i know you can leave [dependencies.examplemod] as it is and your mod should run without problems. I tested this on 1.16.1 and the mod is loading correctly, but you can try to change "examplemod" in the dependencies to your mod ID and see if it loads, i doubt this is the issue though.

[DaemonUmbra]

No, don't leave dependencies.examplemod, that declares dependencies for a mod that doesn't exist

The logo does matter if you plan to open the mod list

All values in mods.toml marked #Optional should be set or removed entirely, do not leave them blank

[TheThorneCorporation]

36 minutes ago, DaemonUmbra said:

No, don't leave dependencies.examplemod, that declares dependencies for a mod that doesn't exist

The logo does matter if you plan to open the mod list

All values in mods.toml marked #Optional should be set or removed entirely, do not leave them blank

I did that, but it still doesn't work, giving the same error.

[DaemonUmbra]

Have you re-run genIDERuns after your changes?

[TheThorneCorporation]

1 minute ago, DaemonUmbra said:

Have you re-run genIDERuns after your changes?

You were supposed to do that?

Edit: And it still doesn't work.

Edited July 29, 2020 by TheThorneCorporation

[DaemonUmbra]

Honestly it's a shot in the dark

[TheThorneCorporation]

Just now, DaemonUmbra said:

Honestly it's a shot in the dark

Is this how it feels to work in computer science?

[DaemonUmbra]

Sometimes

[Beethoven92]

You could try to run 'clean' in your gradle tasks, and then run genIDERuns again. If that doesn't work maybe your best bet at this point is to start a new fresh project and see if you still run into this issue

Edited July 29, 2020 by Beethoven92