ВЕРСИИ (6)

Ported to 26.4 snapshot 4 as that version came with changes to DFU.

Registry-related codecs now mention the registry it's part of when it cannot find an element or tag with a specific id. If those codecs mentioned a registry before, they now no longer do to prevent duplicate mentions of registries. Changed messages: | Old | New | | - | - | | `Cannot get a holder with id {id}` | `Cannot get a holder with id {id} from registry {registry}` | | `Cannot get a registry tag with id {id}` | `Cannot get a tag with id {id} from registry {registry}` | | `Registry tag {tag} is not part of the current registry set` | `Tag {tag} is not part of the current registry set` |

- Support 26.3 snapshot 4

- Ported to 26.1 (preview 1 and above) - Changed a few error messages to mention 'holders' instead of 'registry entries'

# Codecium 1.1.0 for 1.21.5 - 1.21.11 Comes with a couple of improved messages and a single bug fix. ## Fixes - Input is now no longer duplicated for list-related errors. ## Changes - Updated to 1.21.5 - Data component and registry entry error messages are now indented and on a new line. Note that these surrounding messages are translated and may differ based on your language used in the game. It also means that strange occurences with the messages themselves, such as the data component error message being surrounded by `'`, is not viably fixable. - Resource locations now have an improved error message. As a side effect, this change also improves resource location exception messages as a whole in places where it is still used. Used commands: - `/give @s minecraft:stick[minecraft:food={nutrition: "text"}]` - `/loot give @s loot {pools: "text"}` - `/item modify entity @s weapon {function: "example:INVALID_PATH"}` 

Initial release.