Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/02/20 in all areas

  1. I fixed it, I've made a pull request on GitHub if you're interested. I did exactly as I said you should (made a static transaction list and resolved it in ServerTickEvent). A comprehensive explanation of what you did wrong can be found in the pull request.
    1 point
  2. Howdy Ah, my bad. It's actually in Item.Properties nested class Item.java: It's in the nested class Properties public Item.Properties setISTER(java.util.function.Supplier<java.util.concurrent.Callable<net.minecraft.client.renderer.tileentity.ItemStackTileEntityRenderer>> ister) { this.ister = ister; return this; } --> is Right at the very end of the class -TGG
    1 point
  3. There's nothing wrong here. Gradle does not generate the eclipse folder, it's only found in the MDK. The eclipse folder is completely unnecessary and in my opinion it is not a good way to manage a project. It only allows for one project in an Eclipse workspace and requires downloading/copying the MDK to create a new project. I would recommend using a multiproject workspace instead. Lex has made a video tutorial on this, it can be found here. He recommends using setupDevWorkspace, however I would strongly recommend setupDecompWorkspace as it allows you to look at the decompiled MC source. Additionally, I would not recommend targeting 1.8, target 1.9.4 at the very least, preferably 1.10.2 or 1.11.2. 1.8 had a lot of issues due the the massive changes to the rendering system, these issues were mostly remedied by Forge for MC 1.9.4.
    1 point
×
×
  • Create New...

Important Information

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