Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Properly implement registries #73

Open
psu-de opened this issue Aug 10, 2024 · 0 comments
Open

Properly implement registries #73

psu-de opened this issue Aug 10, 2024 · 0 comments
Assignees

Comments

@psu-de
Copy link
Owner

psu-de commented Aug 10, 2024

Registries contain version specific data and are used at a lot of places.

Registries contain a set of predefined data by default (the minecraft:vanilla datapack), but can be dynamically extended.
Currently, MinecraftData is our registry, it contains some (not all) data for the vanilla datapack and can't be extended.

Tasks:

  1. The new Registry should be able to query everything from a MinecraftData instance, but also add the ability to extend the data. A registry lookup should only be done using Identifier's.
  2. There is still a lot of data missing from MinecraftData. Mostly we require mappings from a minecraft version specific number used in the protocol, to a version independent identifier (for example at ParserRegistry). Minecraft-data doesn't provide most of this data, but mcmeta is looking very good for a new data source.
@psu-de psu-de self-assigned this Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant