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

So I've been trying to update a mod (not mine, but for private use) from 1.10.2 to 1.11, and I've managed to resolve all of the error-generating problems, but now I can't figure out why the mod's localization .lang files aren't being parsed and injected.  This is happening both in Eclipse's debug and in an obfuscated runtime environment.  I've debugged the entire process down to the point of seeing that the mod is added to the resource pack, but the lang files are never parsed by the LanguageMap.  I've double checked the file and folder structure a dozen times at least, and it is proper ("assets/{MOD_ID}/lang" from the mod root) in both environments.  In the FMLClientHandler class, under addModAsResource, resourcePackType is not null, and obviously the mod is getting added to the active list and the modNames table (the items and blocks show up in the creative tabs).  Thus, when I load the game, I get tile.{MOD_ID}:{UL_NAME}.name for all of the tooltips over the blocks.  And when I look in the lang file, it's an exact match to whatever block or item may be in question.

 

I am thoroughly lost on this one.  Where can I look next to try to resolve this?

you have to transform all the assets to lower case, including the lang files. (For example: en_US -> en_us)

  • Author

Indeed, thank you.  Those were the only resources left that hadn't already been converted to all lower case.

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.