Skip to content
View in the app

A better way to browse. Learn more.

Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

warjort

Members
  • Joined

  • Last visited

Everything posted by warjort

  1. You need to posta link to your logs/debug.log and/or the crash report.
  2. That's a link to the gist website in general, not your file.
  3. Issue with the betterweather mod, check you have the latest version then contact the mod author.
  4. As I said above, look at how the BlockColors class uses it for vanilla leaves.
  5. Looks like some issue with Mekanism's MekaSuit. Check you have the latest version then contact the mod authors.
  6. The issue is with vivecraft trying to apply a mixin into the minecraft options. The error doesn't say what is conflicting. That version of optifine is not the latest version recommended by them for your version of forge, see their download page.
  7. Use java 17, mixin does not support java 20
  8. https://forge.gemwire.uk/wiki/Tinted_Textures For leaves you will want to use BiomeColors.getAverageFoliageColor() and FoliageColor.getDefaultColor(), see the BlockColors class for the vanilla implementation.
  9. The purpose of this forum is to answer questions about forge/minecraft. It's not here to give you free code reviews. Or to let you proxy the work of debugging your mod to us. Since the question looks like a trivial logic error, I will answer it. But in future your question should be about forge or minecraft, NOT your code. Otherwise, expect to just have your question ignored as off topic. Here you don't enter the loop that calls that method if spawnCustomParticles() returns false which is the default https://github.com/BluMasc/slimed/blob/e785fd4324a1559e220cb2cc4b8f55d60038053b/src/main/java/de/blumasc/slimed/entity/BaseSlime.java#L130 Your "broken" mob doesn't override that method so it too will return false and not spawn particles. https://github.com/BluMasc/slimed/blob/master/src/main/java/de/blumasc/slimed/entity/LovelySlime.java
  10. If it doesn't crash for you, but does for them, then there is clearly something wrong with their installation. The error message is uninformative, it just says "NullPointerException" so we can tell what is causing the issue from that. Get them to do a full reinstall of forge and the modpack from scratch. So you know for sure they are using what you think they should be using. Also tell them not to install any additional/optional client side mods like optifine. Those are always the first candidates for strange bugs.
  11. Please don't post logs in the forum use a file upload site. They are impossible to read/search in the forums, especially when there is more than 1 on a topic. I don't see an error in what you posted. The last thing in the log is some informational message from alexsmobs. If that really is the whole log and not just trunctated by the forum, post a link to your launcher_log.txt
  12. It's likely only your friend can see the block in question. Try teleporting to your friend's location and see if you crash. The problem block appears to be at:
  13. Some issue with divinerpg entity drops. Check you have the latest version then contact the mod author.
  14. Use java 17. Mixin does not support 19 or 20
  15. https://github.com/MinecraftForge/MinecraftForge/issues/9311
  16. You have a conflict caused two mods providing the same java module (com.llamalad7.mixinextras). Check you have the latest versions of these mods then contact the mod authors.
  17. There is no error in that log. If that really is the full/correct log (it is from 2 days ago?) post a link to your launcher_log.txt
  18. No. You are just wasting my time. Maybe deliberately? Compare what I wrote to what you wrote.
  19. "C:\Program Files (x86)\Common Files\Oracle\Java\javapath\java.exe" The quotation marks are important. The 32 bit version will have inferior performance and you will be limited to at most 2 gigabytes of heap of memory. Which is usually only enough to run small/lightweight modpacks.
  20. You edited your run.bat and now it contains invalid characters. Also that path doesn't specify java.exe at the end which is the whole point. If your java really is in the "c:\Program Files (x86)"; * You need to surround the whole path with quotation marks because the path contains spaces. * (x86) means you have the 32bit version of java which is unlikely to work well with modern minecraft, you need to download the 64 bit version which will be installed to "c:\Program Files"
  21. You are doing this wrong. I suggest you rebuild your modpack from scratch and do it by adding mods individually or in small groups. The important part is to test it as you go along so you know which mods are causing problems. Just installing a large number of random mods of varying quality isn't going to work.
  22. Please stop posting logs in the forum. Upload them to file sharing site. We cannot use search to find errors when they are posted in the forum, especially when there are multiple. Your last log contains many errors, just some: Missing kotlin libraries. Some issue with the sound physics configuration A broken shader provided by a mod?
  23. One of your mods has broken mixins. The classes are missing or can't be loaded for some reason. I have no idea which your many mods is net.diebuddies/cloth? A github search gives this: https://github.com/search?q=diebuddies&type=code Maybe you recognise one of these?

Important Information

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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.