Why are texture pack files null?

[AimwareDotCom]

So I've been trying to get into modding minecraft, and so far my experiences have been utterly garbage.

Even though the game's source code looks like it has been put through a hashing algorithm 500 times, and that it is way too complex than what it should be-- I'm willing to learn.

After switching over to the forge API, I'm stuck on an issue where the client cannot load resource packs because the file passed in the function turns out to be null.

I have no idea what is causing this, nor am I patient enough to sit for hours trying to go from function to function of the unreadable nonsense.

So, the great forge modders of this forum, could you please suggest any solutions to this problem?

Logs:

java.lang.ExceptionInInitializerError
	at net.minecraftforge.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:212)
	at net.minecraft.client.Minecraft.init(Minecraft.java:508)
	at net.minecraft.client.Minecraft.run(Minecraft.java:416)
	at net.minecraft.client.main.Main.main(Main.java:118)
Caused by: java.lang.NullPointerException
	at net.minecraftforge.fml.client.SplashProgress.createResourcePack(SplashProgress.java:726)
	at net.minecraftforge.fml.client.SplashProgress.<clinit>(SplashProgress.java:94)
	... 4 more

That log is created because of this function in the class SplashProgress:

private static IResourcePack createResourcePack(File file)
    {
        // This is where the exception is thrown,
        // the file passed in as the parameter is
        // null.
        if(file.isDirectory())
        {
            return new FolderResourcePack(file);
        }
        else
        {
            return new FileResourcePack(file);
        }
    }

 

[Choonster]

It looks like FML wasn't launched properly, so FMLSanityChecker.fmlLocation was null.

 

How did you set up your workspace and run the game? If you follow these instructions, the workspace should be set up properly and your IDE run configurations should use GradleStart and GradleStartServer, which ensure that FML is launched properly.

[Draco18s]

14 hours ago, AimwareDotCom said:

Even though the game's source code looks like it has been put through a hashing algorithm 500 times, and that it is way too complex than what it should be-- I'm willing to learn.

It looks like it's been through a hash algorithm because Mojang obfuscates the source code. All field names, class names, and method names get replaced with single-letter abbreviations, then two-letter, then three-letter, and so on until there aren't any more to replace.

 

As for complex...well yeah, it has to be. Minecraft as a game is complex and incredibly flexible.