Jump to content

Recommended Posts

Posted (edited)

hi,

 

I have a litte question for block naming conventions. During early testing of a demomod I used "Examplemod" as the mod id, and encountered a minecraft forge warning that lower case modnames will be enforce at 1.12+.

Now I ask myself if this also belongs to block names?

In my tutorial demo they used "copperOre" for a demoblock. Now i have started to name my blocks, textures like with captital letters for every new word, so its good to read for me in the code: "StripeWhiteSideInnerCorner" can I keep that or should i take the vanilla way "stripe_white_side_inner_corner" (maybe to long? mcaadditions:stripe_white_side_inner_corner) or every thing together in small letters "stripewhitesideinnercorner" (Bad to read)?

Edited by GregoriMarow
Posted

do you know where the length limitation is? 

 limitation for block name, limitation for modid and maybe a max. limitation modid:blockname

e.g. block name max. 20, mod name max. 20  but all together max. 30?

Posted
10 minutes ago, GregoriMarow said:

During early testing of a demomod I used "Examplemod" as the mod id, and encountered a minecraft forge warning that lower case modnames will be enforce at 1.12+.

This has been enforced as long as I have been modding, and I have been modding since 1.7.10. It didn't just start now, just so you know.

Posted

Well, my resources wouldn't work when I had a capital in ModId once. So technically some functionality didn't work with not lower case even then.

Posted

I was just remembering that thing and it was an example. The real question belongs to the block names. Anyway I am sure its not enforced in 1.7.10 because before I started to learn how to program mods by hand I used MCreator. They enforce Captital Letters (nobody knows why) for modid and it worked. The first time i mentioned that warning was in 1.10.2.

Just for explanation.

My question with the block names was answered by kookie and it looks like there is no length limitation.

Posted

In 1.11+, all resource file names must be lowercase and ResourceLocation coerces both the domain and path to lowercase.

 

1.10.2 allows you to have mixed-case resource file names and ResourceLocations, though the domain is still coerced to lowercase. I recommend using lowercase names anyway, since it will be easier to update to 1.11.2.

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

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



×
×
  • Create New...

Important Information

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