I understand Mojang changed ResourceLocation to force lowercase. That has been a minor irritation. The AttachCapabilitiesEvent#addCapability uses a ResourceLocation too. As a result this new behavior has broke loading a 1.10.x. and earlier world data IF you used a mixed or uppercase resource name. Fortunately you only lose data since the saved capability is simply recreated with defaults again using the lowercased identifier. I was curious if there is a way I can dynamically fix world data.

 

event.addCapability(new ResourceLocation(MXTuneMain.MODID, "IPlayerMusicOptions"), new ICapabilitySerializable<NBTTagCompound>()

 

The result for pre 1.11 is what I would expect.

 

The result for 1.11 was not surprising once I looked at my code and saw the ResourceLocation parameter.

 

I've seen examples to fix your registry renames using the FMLMissingMappingsEvent. But that's for Items and Blocks.

 

At this point I need to do more research. Does anyone have any ideas or suggestions?

After reviewing some NBT specs I'd would say it would be better to allow mixed case in the resource path portion of a ResourceLocation. NBT is case sensitive. Should capabilities respect the case of the name you choose? In my opinion it should. A CapResourcePath could be created that extends ResourcePath.

 

 

it would be better to allow mixed case in the resource path portion of a ResourceLocation

 

Not going to happen.  Mojang already made the change.

Oh I understand what Mojang did. I'm fine with it, but since hindsight is 20/20, using a ResourceLocation for the capability tag is less than ideal. World save data and resources/assets live in two different worlds.

True, they do.

This sounds like a moment for a PR.