Jump to content

Draco18s

Members
  • Posts

    16559
  • Joined

  • Last visited

  • Days Won

    156

Everything posted by Draco18s

  1. Gosh, I opened the file and what do I find? https://github.com/MinecraftForge/MinecraftForge/blob/1.15.x/src/main/java/net/minecraftforge/registries/DeferredRegister.java#L93 A deprecated annotation and a fucking comment about what to do instead.
  2. Code Style #4 Won't solve your problem, but you should still fix it. Per your problem, my guess is that 1.16 is not ready yet.
  3. Why would you have to? It literally makes no sense that the game would have to ask you to serialize something to a given format and not have a working implementation of that format to serialize to. I'm not even sure the game would know how to serialize and deserialize your custom NBT classes properly.
  4. That's not how that works.
  5. ...did you implement your own NBT class?
  6. Vanilla has code to handle that, but that doesn't mean you can hook into it and make it do what you want.
  7. I've never dug into the rendering system more than I need to, which means I've never messed with the things you're messing with.
  8. Oops, you're right.
  9. Complain to the author of the mod, not Forge. Forge didn't write the code that is causing the problem so what do you think we can do about it?
  10. Learn to lead your error logs. I have highlighted the class, method, and line where the error occurred. You have not shown this code.
  11. Yes. Transparent things and opaque things need to be drawn in different passes as they have different sorting orders. (The HUD is also a separate pass) "Impl" is an abbreviation of "implementation." Use your IDE to find implementations of IRenderTypeBuffer. Because you need several transformation matrices applied one after the other to handle certain types of rendering. Think about an item that lays flat on the top surface of a block (campfires do this). The item renderer assumes that the item sticks up vertically but the campfire wants to render it horizontally. We already have a transformation matrix to counteract the player's position away from 0,0,0 but now we need another one to rotate the item to lay flat...
  12. Yes. Preferably as a clonable git repo.
  13. I did find the git branch, my eyes probably skipped over it. But I did check. Either way, the earliest change on the branch/build isn't even 24 hours old yet. It was committed at near-midnight last night.
  14. You could read the text of the sign, but you can't change it, because of this pesky thing called "server authoritative model." That is, the server is the absolute authority on the state of the game, and that state includes the text on signs. Without code on the server to change that text, you can't.
  15. I don't know what its stability state is. Just because there's a build doesn't mean its ready. The branch has only existed for a day. The oldest change in the change log isn't even 24 hours old yet.
  16. Forge doesn't even have a 1.16 branch on Github yet. So....
  17. Forge is not ready for 1.16
  18. This is client side only. Either: Your mod needs to be client side only (in which case, it can't make changes). You need to access the TE via a server world.
  19. I'm not sure how you managed this, honestly. You should probably fix these. Not the cause of your crash, that appears to have been a null pointer exception in the networking thread, but I can't discern why. You also haven't posted your code either. Soo...
  20. BooleanProperty
  21. 18 shelf slots as booleans results in 262,144 total states for your block. While the game does not enforce a maximum, this is still a lot. I would suggest using an IDynamicBakedModel instead of the blockstate system.
  22. The method doesn't implement anything. Methods return things. You want the thing the method returns to implement that interface.
  23. Data and Assets should be siblings: https://github.com/Draco18s/ReasonableRealism/tree/1.14.4/src/main/resources
  24. I wonder if this has to do with blocks' position is the lower North West corner (not the center).
  25. This seems pretty self explanatory.
×
×
  • Create New...

Important Information

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