Jump to content

Animefan8888

Forge Modder
  • Posts

    6157
  • Joined

  • Last visited

  • Days Won

    59

Everything posted by Animefan8888

  1. This sets the count of how many items are in the stack. So when this is called you know have -1 bottles. Use ItemStack#getCount
  2. You never instantiate it, so it is null. Basic Java.
  3. An ItemStack has a count of how many "items" are in it. So if you fill one you need to set the count to the count - 1.
  4. Yes. @ObjectHolder("modid:registryName") public static final Item ITEM = null; Or onRegistry() ModItems.ITEM = new Item().set... register(ModItems.ITEM)
  5. You can put it there yes. Use @ObjectHolder or initialize them in the registry event.
  6. @nov4e Do you have an Item with the registry name nex:clock.
  7. Stop doing this, dont use static initializers. This needs to be in it's own class otherwise it will crash the dedicated server. Dont use IHasModel. And could you post a picture of your directories.
  8. Well it will always be true at least as long as they use a List. And no one modifies the List. Does that answer your question?
  9. This section of the forum is for people who need help writing mods. The server thinks the entity is moving too fast or it moved in the wrong direction this could be caused by multiple things.
  10. Yes you can use .obj files and forge has an already in place system for it, you will still need a json file for your blockstate it just needs to point to the obj file and in your preInit method call OBJLoader.add or similar.
  11. First off this is a little repetitive you created a variable for this. This method sets the slots contents whereas you just want to decrease the stack size. Use ItemStack#setCount to set the count. Then call InventoryPlayer#addItemStackToInventory or similar
  12. Well if the level is 0 there cant be an enchantment can there?
  13. From what has been announced probably just the rendering engine. And if so theres only some things that will change like the patches mainly where to inject the byte code ect.
  14. You never use this variable, I assume you want to. Plus there aren't any if statements in that block of code so of course it always happens.
  15. Sounds like a desync issue you'll have to tell the client from the server what the variant is.
  16. Lex has a patreon, I dont know if anyone else does. But the reason 1.13 is taking so long is a combination of having other responsibilities and one of the devs became unresponsive and I think Lex just picked up the work did it and now its moving along steadily again. I would say if things keep going as they are it should be mostly done if not done before the end of December. But that is just speculation anything is subject to change.
  17. I wish I could thank him in person. That sucks, is he just kinda MIA or do you know that they are dealing with something? Fantastic, I'm gonna take a look at that once I have time. I'm sorry.
  18. No, the update for 1.14 probably won't take much, the only reason 1.13 is taking as long as it is, is because they decided to re-write the whole thing from the ground up. 1.14 won't be anything like that.
  19. Don't just copy-pasta code, read it, understand it, and use it. Assuming that his code is under a license that allows you to copy and distribute his code.
×
×
  • Create New...

Important Information

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