Jump 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.

Leaderboard

Popular Content

Showing content with the highest reputation since 01/10/26 in all areas

  1. Thanks to your help, i spotted the problem. It was a version mismatch, i just solved the mess. Thanks a lot XD
  2. After much trial and error I also checked in with the COFH Discord and was able to find out that "DupeFix Project" was responsible for the crash (java.lang.NoClassDefFoundError: cofh/thermalexpansion/gui/container/storage/ContainerSatchel). After removing that mod everything worked.
  3. This isn’t about features or content size, but polish. From a player and developer perspective, here’s what consistently separates good mods from great ones. Performance awarenessHigh-quality mods avoid ticking when unnecessary, cache results, and respect server performance. Consistent behaviorItems behave predictably, configs work as expected, and nothing breaks silently. Clean UI/UXMenus don’t lag, text is readable, tooltips explain behavior without external documentation. Compatibility mindsetGood mods avoid hard conflicts, use proper tags, and integrate with existing systems instead of overriding them. DocumentationEven minimal README files or in-game descriptions dramatically improve user experience. None of these are flashy, but together they’re what make a mod feel professional. Interested to hear what others prioritize.
  4. Posting this because I spent more time on it than I’d like to admit, and I’ve seen others hit the same wall. The problemMy custom block registered correctly, appeared in the creative tab, but rendered as a missing texture cube. No errors at runtime, just a purple-black block. What I checked firstRegistry name was correct Blockstate JSON existed Model JSON paths looked fine Textures were in the right folder Everything looked correct. The actual issueThe problem was a mismatch between the blockstate JSON and model file names. Example mistake: blockstates/my_block.json models/block/myblock.json Forge does not warn you when these names don’t match exactly. The fixMake sure naming is consistent everywhere: blockstates models/block models/item registry name Also ensure that: JSON files are lowercase no extra underscores or hyphens exist resource reload cache is cleared Restarting the client after fixing resource paths helped immediately. TakeawayIf your block exists but renders wrong, the issue is almost always: naming mismatch resource path typo cached resource reload Hopefully this saves someone else an hour.
  5. i deleted it and it works now tysm!!
  6. Delete the curios-server.toml file in your config folder If there is no such file, check your worldsave, serverconfig folder
  7. Okay after changing to Eclipse and talking with the people in the server, I have solved the issue. Not only was I referencing the mod in my dependencies (build.gradle and mods.toml) but I also had the .jar in my /run/mods directory. It was the second causing the issue. We figured this out as I was able to build my mod and run it together with BW in a regular forge 1.20.1 instance. I believe it was also necessary to add the previously mentioned MixinGradle Plugin to the build.gradle file. Thanks to everyone for your help!
  8. At a cursory glance on the website, that product does not work with MinecraftForge as a mod. Neoforge is a different mod loader, they have their own support. People may have looked at your post, but not know an answer, so asking for replies from viewers as you did is probably not very useful. If you're looking for a chat room vs a forum, you should join the discord.

Important Information

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

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.