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.

Featured Replies

Posted

Not sure if I'm posting this in the right place. Feel free to move it if not.

 

Correct me if I'm wrong, but I don't think much changed behind the scenes between 1.10 and 1.11. Seeing as there are some mods that claim to use the same jar for both versions, simple (or maybe even not simple) mods shouldn't need to be changed much or at all between 1.10 and 1.11.

 

The issue is that I can't just use the same jar for 1.10 as I use for 1.11, because forge rejects anything with the wrong version number. I assume that It doesn't reject forwards-compatible mods (using a 1.10.2 mod with 1.11.2 forge), but from my very quick tests it does reject backwards-compatible mods (using a 1.11.2 mod with 1.10.2 forge). Is there a way to resolve that issue (I'd like my 1.11.2 mod to be usable in 1.10.2 modpacks) without recreating the development environment for 1.10 forge, or do I need to re-generate my dev environment?

 

Note: I tried changing the minecraft version in build.gradle, but then it threw an error when I tried to build it, so I don't think it's that easy.

Edited by TheUnlocked

The major thing between 1.10 & 1.11 is that ItemStacks can no longer be null in 1.11. This means that whenever you call ItemStack.EMPTY in your 1.11 code, you need to switch to null-checking & setting in 1.10.

The 1.10<->1.11 compatability is almost exclusively for those that use the CompatLayer API, made by McJty.
Because of the nature, this means a hard dependency.
 

Edited by Matryoshika

Also previously known as eAndPi.

"Pi, is there a station coming up where we can board your train of thought?" -Kronnn

Published Mods: Underworld

Handy links: Vic_'s Forge events Own WIP Tutorials.

You can set the acceptedMinecraftVersions property of your @Mod annotation to change which versions of Minecraft are allowed to run your mod. If your mod isn't actually compatible with a Minecraft version, it will likely crash at runtime when it encounters an incompatibility.

 

Look at VersionRange.createFromVersionSpec for brief documentation of the version range format. Look at FMLModContainer#bindMetadata to see how FML replaces some specific version ranges with others (where multiple versions are compatible with each other).

Edited by Choonster

Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

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.