This is my intellij structure: 

 

 

and when I do

    private static final ResourceLocation CAST_TEXTURES = new ResourceLocation("assets/textures/entity/CastingCircle-texturemap.png");

 

it fails to load. Where should I be looking?

Edited April 14, 20205 yr by Turtledove

31 minutes ago, Turtledove said:

I'm attempting to register a simple entity that extends entity:

1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support. For more information read the LTS at the top of the page.

3 minutes ago, Animefan8888 said:

1.12 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support. For more information read the LTS at the top of the page.

edited the post to a different question on a 1.15 version of the mod.

2 minutes ago, Turtledove said:

edited the post to a different question on a 1.15 version of the mod.

That post shows no proof of a switch, but I'll give you a hint check out the other ResourceLocations you have made and the ones made by Minecraft for the same purpose.

38 minutes ago, Animefan8888 said:

That post shows no proof of a switch, but I'll give you a hint check out the other ResourceLocations you have made and the ones made by Minecraft for the same purpose.

Alright, my directory is now:

 

src

    |_main

             |_resources

                        |_assets

                               |_ModID (in this case necropolisofnostalgia)

                                    |_blah blah path to texture

 

and I've done MODID + "blah blah path to texture", and still nothing. Ready to tear my hair out at this point lol

Inside the definition for your entity renderer, did you @Override getEntityTexture() method in order to return your own ResourceLocation?

 

2 minutes ago, chubel10 said:

Inside the definition for your entity renderer, did you @Override getEntityTexture() method in order to return your own ResourceLocation?

 

Yup. I also made sure it wasn't an issue with IntelliJ since I remember I had a similar issue in version 1.10 when it built and ran using Gradle. But in this version that shouldn't be an issue...