Resource Identifiers Become Compatibility Contracts
A resource identifier that appears in packs, datapacks, saves, or another mod's configuration becomes a compatibility contract: changing its namespace or path can break references even when the mod still builds. When assets or recipes disappear after a rename, compare the identifier at the point it is produced with the one expected by each consumer, including serialized data and overrides. Keep established identifiers stable or provide a deliberate migration or compatibility mapping; exact validation and migration mechanisms depend on the Minecraft, loader, and mappings versions.
Vanilla resource paths allow only lowercase letters, digits,
_,-,., and/in the path, so an uppercase letter introduced by a rename fails validation. Check the identifier against those rules. Other platform gotchas welcome in the comments.