Jump to content

ChampionAsh5357

Forum Team
  • Posts

    1717
  • Joined

  • Last visited

  • Days Won

    28

ChampionAsh5357 last won the day on December 2

ChampionAsh5357 had the most liked content!

5 Followers

Converted

  • Personal Text
    *eats popcorn*

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

ChampionAsh5357's Achievements

World Shaper

World Shaper (7/8)

211

Reputation

  1. We generally don't support old versions, but as this error is probably related to the M1 chip, I will provide an answer. If you're saying that it works fine without mods then failed after a mod was added, then there is probably a mod which causes the error to which you need to remove one-by-one or in batches to find. If that's not the case, it could be with the early progress window, to which you would need to add `-Dfml.earlyprogresswindow=false` to your java arguments in your profile. If that doesn't fix the issue, then you're better off updating to a later minecraft version where the issue is fixed within GLFW. You can attempt to rebuild Forge with the updated library, but you will receive no support for that here.
  2. This seems like a packet issue with one of the mods, so you may need to remove them one-by-one or in batches to determine which is the erroring one.
  3. Make a resource pack? Or make a mod. Don't try to modify an existing jar.
  4. Looks like wherever that file is located has a bunch of illegal characters within it or is being read incorrectly. Best thing to do is to split the mods into two piles, load them up, repeat the situation that caused this error, and keep splitting the erroring pile until you find the mod in question.
  5. It says you need 43.1.52 or higher; you have 43.1.7. 43 == 43 1 == 1 52 > 7 You do not have a compatible version, update Forge.
  6. 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.2 (Latest) and 1.18.2 (LTS).
  7. 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.2 (Latest) and 1.18.2 (LTS).
  8. Provide the debug.log in the logs folder of wherever your game directory is (typically .minecraft).
  9. BlockEntity with renderer is probably the way to go. You can look at the campfire for an example of how an item is rendered on a block entity.
  10. Could you please show what you currently have and explain what is unclear about the documentation?
  11. You're missing the renderer through EntityRenderersEvent$RegisterRenderers, spawn placement through SpawnPlacements#register in the queue within FMLCommonSetupEvent, and attributes added through EntityAttributeCreationEvent. As for the `#build` method, that is for specifying the name of the entity to be referenced in the datafixer if things change across versions and the entity data needs to be adjusted; however, it currently is not supported by Forge.
  12. 1) Don't use @OnlyIn. You should never have a reason to use that annotation. 2) Most likely this comes down to your texture and the way you render the model/layers. What is transparent and what is opaque? The opaque parts should be rendered in the main model, followed by the translucent parts in the layers going from inner to outer.
  13. It's better to just use ogg; it is not worthwhile to reimplement an entire sound engine which will just conflict with the ingame one when determining what to output to the audio devices.
  14. RenderLivingEvent$Pre, cancel the render, render what you want.
  15. That's because items aren't part of the model, it is a layer. Unless you are doing it for an item you own, you would need to replace the layer to do your own rendering or rerender the model itself, both of which would probably cause incompatibilities. Alternatively, you could regenerate all the item models with what you want them to have.
×
×
  • Create New...

Important Information

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