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.

Jinxed

Members
  • Joined

  • Last visited

Everything posted by Jinxed

  1. As fun as making up version numbers would be. I mean a fix by letting the jarhandler somehow ignore the mod altogether, or give the user a better idea which mod caused the crash by catching the IllegalArgumentException and let JarMetadata.fromFileName output the filename. As it is ModuleDescriptor.Version parse throws an uncaught exception and itself only reports back the string that was being evaluated. (In this case, "1.0-1.19+" (example: https://pastebin.com/B7s0Td13) Not sure why I care so much, other than keeping people from constantly asking about the crashes in future modpacks, all because some author flunked their semver comprehension.
  2. Could this be fixed on the forge end since it just started popping up between 43.1.64 -> 43.1.65? I hate the idea of adding dummy checks for all sorts of strings, but you know some mod developer down the road is going to make the same mistake in naming convention at some point.

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.