Jump to content

ChampionAsh5357

Members
  • Posts

    3284
  • Joined

  • Last visited

  • Days Won

    62

Everything posted by ChampionAsh5357

  1. Post the new debug.log. It's difficult to figure out the error without one.
  2. You can just make an anonymous class and use the DeferredRegister to register the type the same way. Don't ever do static initialization. Look at the RecipeManager. Also, it has nothing to do with the difference of recipes. If your type doesn't have serializers for the recipe you want to handle, then no recipes of that type will be present. For example, shapeless recipes are tied to the crafting recipe type. The only way to get around that is to grab all the craft recipes and then check if the recipe is an instance of ShapelessRecipe.
  3. Extend the class and override getRecipeType to return your own. Everything else can be exactly the same as vanilla, even the serializer (though you will have to register a second one so it deserializes to your recipe).
  4. Yep, that's what Entity#hurtMarked calls. It's not necessary on the server as it's handled on the client. Delta movement doesn't need to be known on the server since it doesn't affect anything. When the delta movement is applied to the player on server, it is typically by setting the method I mentioned above which adds the movement to the player on the client.
  5. Why do you need a custom packet for this when vanilla already has something? You can probably just look at the SayCommand to see how to do this.
  6. Would you mind attempting to run the version in vanilla first and then doing so in Forge? I'm wondering if the timeout request always happens at the same spot or it keeps slowly progressing as it caches more information.
  7. Well, reading it, it says that it must be a https request, not an http one. Could you please provide the entire log of the original error? I'd imagine this is a fallback from the first attempt failing.
  8. The class is private, so you need to use the static constructors instead.
  9. What modifier is on the event that is not on the other two events?
  10. Ah, you're doing it on protected attributes. This is a problem as you cannot guarantee that any other mod (since vanilla doesn't luckily) will not extend those classes and keep the attributes as protected. I would use reflection or a mixin accessor instead since neither of those have the limitation of not ATing a protected type.
  11. SPEED is a blockstate property. You are setting data on the block, to which you don't have the block state in most cases. The best you can do is handle the methods which take in a function with a blockstate parameter or override the methods in a subclass.
  12. Remove OptiFine; that mod tends to cause numerous issues with anything rendering.
  13. Seems to be an issue with balm, try removing it and see what happens.
  14. Can you screenshot the crashing screen? I can't see any error in what you have provided unless it has to do with something during the config load. You could try deleting the config folder and see if that works.
  15. Well, it says you need curios since it's required by three mods.
  16. Remove OptiFine, it currently does not support Forge 1.19.3.
  17. That field syncs it from the server to the client. Makes sense since the delta movement is not necessary for syncing, only the position and rotation. You can't, lerping is not supposed to be done on the server anyways as it is meant for handling smoother animations on the client when rendering to the screen. You should just be using the raw position values if you want to use them. Once again, player movement is handled on the client. The only information synced to the server is those that need to be sent to all players, which in terms of movement can typically be boiled down to (as an oversimplification) position and rotation. If you want other values, you'll need to sync them yourself using a packet. Using Entity#hurtMarked will allow you to sync the values you set on the server back to the client afterward.
  18. The version you are using is no longer supported on this forum. Please update to a modern version of Minecraft to receive support. Currently supported versions are 1.19.3 (Latest), 1.19.2, and 1.18.2 (LTS).
  19. You don't have java installed on your machine, or in this case the launcher is not pointing to a valid JVM.
  20. You're gonna have to search for it on the internet since it is different depending on operating system and occasionally the router.
  21. If it's not on the official site of publishing (so CurseForge), it's a scam and probably will download a virus instead.
×
×
  • Create New...

Important Information

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