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

I've seen multiple variations on how to name things in a mod regarding whether lowercase is mandatory or not. Are the following true?

- in the @mod or mcmod.info, modid should always be lower case (especially from MC1.11)

- in a ResourceLocation, resourceDomain should always be lower case

- in a ResourceLocation, resourcePath can be any case provided it match with the JAR content

- in a unlocalizedName, the string can be any case provided it match with the lang file content

- in a command, it's only 'recommended' to use lowercase command names

- in a DamageSource, according to vanilla 1.10.2, damageType can be camelCase

- in a sounds.json, the keys should be lower case

- in a PropertyEnum, the name should be lower case

- in a PropertyEnum, the values should be lower case

 

 

 

 

- in the @mod or mcmod.info, modid should always be lower case (especially from MC1.11)

This will be enforced in 1.11, at the moment it's only a recommendation.

 

- in a ResourceLocation, resourceDomain should always be lower case

The domain is already converted to lowercase when you create a

ResourceLocation

.

 

- in a ResourceLocation, resourcePath can be any case provided it match with the JAR content

As diesieben07 said, 1.11 will require all paths in a resource pack (which mod assets are added as) to be lowercase.

 

- in a unlocalizedName, the string can be any case provided it match with the lang file content

Correct.

 

- in a command, it's only 'recommended' to use lowercase command names

Correct.

 

- in a DamageSource, according to vanilla 1.10.2, damageType can be camelCase

Correct.

 

- in a sounds.json, the keys should be lower case

This isn't currently required, but it may be in 1.11 as

SoundEvent

s store their name as a

ResourceLocation

.

 

- in a PropertyEnum, the name should be lower case

- in a PropertyEnum, the values should be lower case

This isn't required, but the name and values will converted to lowercase when used in a

ModelResourceLocation

.

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.

  • Author

Since all assets paths needs to be lower case in MC1.11, and item models use registry name, I guess all registry name will also need to be lower case?

Since all assets paths needs to be lower case in MC1.11, and item models use registry name, I guess all registry name will also need to be lower case?

 

According to the wiki, registry names for blocks, items and entities will be case insensitive and autocomplete will use lowercase letters.

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.