Jump to content

Paint_Ninja

Community Manager
  • Posts

    766
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by Paint_Ninja

  1. Update to MC 1.19.4. Virtually all 1.19.3 mods work on 1.19.4 or have a version available for it. 1.19.3 is effectively abandoned by mod devs in favour of 1.19.4, the latter of which is much more stable and a bit better optimised, too.
  2. That log says you started the vanilla game then closed it. Please check the FAQ for instructions on how to get the right crash report, debug.log or launcher log.
  3. This has already been the de-facto standard for quite a while now, but figured it would be a good idea to properly formalise it and make it clear for everyone. TL;DR: You can ask and offer support for Forge on any MC version, as long as you're not demanding it from staff and can accept that older versions may receive less attention due to people moving on to newer, shinier things. Tiered support policy There are now essentially three tiers of support: full, legacy and minimal. Full support This tier has dedicated channels for help on the Discord, gets priority for documentation, new features and bugfixes, and is generally considered the main focus for Forge development and support. Triage actively ports and backports things as needed for versions within this tier where time allows. The MC versions covered by this follows the existing "LTS" system. In other words, the latest MC version and select versions before it are covered by this tier. We recommend people consider using the newest version possible, as it's likely to be fully supported for longer. Exact versions covered under the full support tier can be found near the top of the FAQ. Legacy support This tier is for older versions of MC that are no longer covered by the full support tier. This tier gets less attention, but is still supported to some extent. To be clear, this is not a "no support" tier, but it is not the main focus. You're welcome to ask for help, submit PRs and help out, but please be aware that you may not get a response as quickly as these versions are generally not as popular anymore and may not have as many people around to help. Staff may still choose to work on these legacy versions and help people, but please don't demand it from them. Please note that due to the nature of the old toolchains used for building legacy versions, developing mods using the default MDK may not work. We also cannot easily publish updates to some of these old versions without your help - if you're interested in fixing this, please reach out to us. Minimal support This is rare and usually only applies to versions of MC where there's no legitimate reason to be using them. A real-world example of this is 1.20.3, which had a data loss bug that was fixed in 1.20.4 shortly after. All mods made for 1.20.3 work on 1.20.4, so there's no reason to use 1.20.3. We will help you update to the fixed version instead, but that's about it.
  4. This is the Forge forums - Fabric isn't supported here. Read the FAQ before posting
  5. This is the Forge forums. We do not support Fabric here. Read the FAQ before posting.
  6. Spigot plugins and Forge mods are entirely different things. According to that tool, a modpack with 200 mods with no players online needs about 24GB of RAM to run, which is waaay out of the ballpark of reality. Worst case scenario you get bad performance allocating that much RAM to the game, best case you waste money and resources that could've been better spent on CPU. Vanilla 1.20 does not need "at least 4GB" to run well. It can run fine on half that. Please don't bump a year old post with an advert for something poorly researched.
  7. We need a link to your crash report, as explained in the FAQ
  8. Please do not dump crash logs directly into your post. Share a link to it on https://paste.ee instead
  9. We need a link to your crash report, as explained in the FAQ
  10. We need a link to your crash report, as explained in the FAQ
  11. Try updating to GML 1.2.1: https://www.curseforge.com/minecraft/mc-mods/gml/files/3995305
  12. Your post caused the anti-spam to trigger, causing slow support. Please share a link to your crash report, as explained in the FAQ.
  13. Your post caused the anti-spam to trigger, causing slow support. Please share a link to your crash report, as explained in the FAQ.
  14. Please share a link to your crash report or debug.log on paste.ee, as explained in the FAQ. Do not dump it directly in the forum
  15. https://forums.minecraftforge.net/topic/125488-rules-and-frequently-asked-questions-faq/#comment-541436:~:text=How do I update my drivers%3F
  16. Read the FAQ before posting. It has guides on where to find your crash report and debug.log and how to share the link to it
  17. 1) Run a memtest 2) Make sure your CPU isn't overclocked 3) Make sure you've setup DOCP/AMP/XMP/EXPO properly for your ram. Just increasing the frequency without changing anything else will cause instability
  18. You've posted in the buildscript/Gradle support forum but you appear to be asking about rendering code. I've moved your post accordingly.
  19. You posted in the buildscript support channel but you appear to be asking a mod code question. I've moved your post accordingly.
  20. Please read the FAQ before posting. We need your crash report
×
×
  • Create New...

Important Information

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