Jump to content

zSkell

Members
  • Posts

    35
  • Joined

  • Last visited

Everything posted by zSkell

  1. Thank you so much , you saved me
  2. Yesterday, I created one with a block and tools. But when I start the client, it closes after a few seconds. There's the log: And eclipse gives me this error: Could not run build action using connection to Gradle distribution 'https://services.gradle.org/distributions/gradle-4.10.3-bin.zip'. Unable to get mutable Windows environment variable map Unable to make field private static final java.util.Map java.lang.ProcessEnvironment.theCaseInsensitiveEnvironment accessible: module java.base does not "opens java.lang" to unnamed module @3c5a99da
  3. So what i'm supposed to do now ? If you can help me i'll appreciate It.
  4. I created a biome using eclipse, in minecraft version 1.18.2. I made it following a tutorial of version 1.16.5, but at the end a command who does not work. This is the code: https://imgur.com/Qgh1qeP
  5. Oh, i think i fixed it , I was wrong to write ...
  6. Oh ok sorry , : https://imgur.com/v4q7XRR I did the same thing for every tools but changing the layer name.
  7. That's it : https://imgur.com/SseRTk8
  8. II found a part where it says : Unable to resolve texture reference: missingno in blackmamba: item / ash_sword Unable to resolve texture reference: #missingno in blackmamba: item / ash_pickaxe Unable to resolve texture reference: #missingno in blackmamba: item / ash_axe Unable to resolve texture reference: #missingno in blackmamba: item / ash_shovel. But I can't understand what I did wrong.
  9. Should I post the contents of the log here?
  10. I have a problem with the tools of the mod I am creating, the game starts without errors, the tools also work correctly, the only problem is that these objects have no textures. I tried to check that all the names matched or that they were all lowercase but I didn't find any problems. I would like you to help me, thank you.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.