Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Common mistakes made with textures.


Recommended Posts

There are many times when I browse the modder support forums and see a missing texture error where people's textures are present but they made a mistake with coding. Believe me, I know how that feels, I've made mistakes with texturing 3 times now. Some of these mistakes are not obvious, so I figured I might as well make a list of them.

 

1. Modids

You may be thinking, Modids? What does that have to do with textures? Well the answer in simple terms, it does have something to do with textures, all modids must be lower case for textures to work. I don't know why, but they do. This is the most common mistake I see on the forums with texturing.

 

2. build.gradle when using IntelliJ

If you using IntelliJ, you must put an extra line at the end of your build.gradle, and refresh. As diesieben07 pointed out in his tutorial:

If you are using Intellij 14 (which you should) you need to add the following to the end of your build.gradle before importing:

idea { module { inheritOutputDirs = true } }

If you don't do that, your assets will not work. (Thanks to SanAndreasP for finding this solution)

 

3. Coding Problem: Appears in inventory but not in world

If your block is appearing in your inventory but not when placed in the world, you have a problem with your block's coding. As pointed out here. To fix this error, check a few things in your code.

- Check your console. If you have something in there like, "The following texture errors were found." in there, the file may be missing.

    - Verify that if you do have this message in you console after running, that the files listed aren't missing.

    - If they aren't missing in your assets directory, you may have a typo in your code or your directories. Do not underestimate typos. Check everything!

- Verify that your block wasn't registered before the instance was initialized. This is a mistake that is easy to fix. Just put the registering line after the initializing line.

 

4. Coding Problem: Appears in the world but not in your hand

If it appears in the world but not in your hand, you have a problem with the item. If you have this problem, as this tutorial points out, there are two ways you can tell what's wrong.

 

Does it appear 3D but with no texture? If so you have a missing model.

 

Does it appear 2D, like an item? If so you have a missing texture.

 

If you have any suggestions for anything I've missed or anything I'm explaining wrong, reply and I will add suggestions and fix errors in my post.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



  • Recently Browsing

    No registered users viewing this page.

  • Posts

    • And also if u could help create a server with forge 
    • package com.example.examplemod; import java.util.Collection; import net.minecraft.client.Minecraft; import net.minecraft.client.network.NetworkPlayerInfo; import net.minecraft.command.CommandBase; import net.minecraft.command.CommandException; import net.minecraft.command.ICommand; import net.minecraft.command.ICommandSender; import net.minecraftforge.client.ClientCommandHandler; import net.minecraftforge.common.MinecraftForge; import net.minecraftforge.fml.common.Mod; import net.minecraftforge.fml.common.Mod.EventHandler; import net.minecraftforge.fml.common.event.FMLPostInitializationEvent; @Mod(modid = "PartyAll", name = "PartyAll", version = "1.0", acceptedMinecraftVersions = "[1.16.X]") public class ExampleMod extends CommandBase {   @EventHandler   public void init(FMLPostInitializationEvent event) {     MinecraftForge.EVENT_BUS.register(this);     ClientCommandHandler.instance.func_71560_a((ICommand)this);   }      public int func_82362_a() {     return 0;   }      public String func_71517_b() {     return "pall";   }      public String func_71518_a(ICommandSender sender) {     return null;   }      public void func_71515_b(ICommandSender sender, String[] args) throws CommandException {     (new Thread(() -> myRun(sender))).start();   }      public void myRun(ICommandSender sender) {     Collection<NetworkPlayerInfo> playersC = Minecraft.func_71410_x().func_147114_u().func_175106_d();     playersC.forEach(loadedPlayer -> {           String loadedPlayerName = loadedPlayer.func_178845_a().getName();           (Minecraft.func_71410_x()).field_71439_g.func_71165_d("/p " + loadedPlayerName);           try {             Thread.sleep(150L);           } catch (InterruptedException e) {             e.printStackTrace();           }          });   } @Override public String getCommandName() {     // TODO Auto-generated method stub     return null; } @Override public String getCommandUsage(ICommandSender sender) {     // TODO Auto-generated method stub     return null; } @Override public void processCommand(ICommandSender sender, String[] args) throws CommandException {     // TODO Auto-generated method stub      } }  
    • Now that i'm using 1.16 it still gives me errors with the func_ note: I'm not a professional
    • I am installing forge but then it changes it in WinRar version and then i cant do anything with it please help 😪
    • The darkness is associated with ambient occlusion, in your block class you can modify this with: @Override public float getAmbientOcclusionLightValue(BlockState state, IBlockReader worldIn, BlockPos pos) { return (some float); } I've found that small values (usually around 0.1F) reduce the dark. Alternatively in your block model json you can disable or enable occlusion with: "ambientocclusion": true/false  
  • Topics

  • Who's Online (See full list)

×
×
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.